Method and WTRU for positioning with reduced latency in wireless communication systems

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 Mar. 30, 2021; U.S. Provisional Patent Application No. 63 / 228,787, filed Aug. 3, 2021; U.S. Provisional Patent Application No. 63 / 249,168, filed Sep.  28, 2021; U.S. Provisional Patent Application No. 63 / 257,414, filed Oct. 19, 2021; and U.S. Provisional Patent Application No. 63 / 275,175, filed Nov. 3, 2021, the contents of each of which are incorporated herein by reference.

[0002] This disclosure relates to methods and apparatuses for performing positioning of wireless transmit and / or receive units (WTRUs) in a wireless communication system.

Background Art

[0003] This disclosure relates to wireless and / or wired communication networks, including, but not limited to, methods, apparatuses, systems, etc. for positioning in a wireless communication system.

Brief Description of the Drawings

[0004] A more detailed understanding can be obtained from the following detailed description, given in conjunction with the drawings attached hereto as examples. The figures of such drawings are, like the detailed description, exemplary. Therefore, the figures and the detailed description should not be regarded as limiting, and other equally effective examples are possible and likely. Further, like reference numerals (reference numeral, "ref") within the figures (Figure, "FIG") indicate like elements. [Figure 1A] A system diagram showing an exemplary communication system. [Figure 1B] A system diagram showing an exemplary wireless transmit / receive unit (WTRU) that can be used within the communication system shown in FIG. 1A. [Figure 1C]Figure 1A is a system diagram showing exemplary radio access networks (RAN) and exemplary core networks (CN) that may be used within the communication system shown. [Figure 1D] Figure 1A is a system diagram showing further exemplary RAN and further exemplary CN that may be used within the communication system shown. [Figure 2] This is a timing diagram showing various parameters related to the measurement gap. [Figure 3] This is a signaling flow diagram illustrating an example of signal exchange between WTRU, gNB, and Location Management Function (LMF). [Figure 4] This timing diagram shows an example of the difference between the initial measurement gap pattern and the newly requested measurement gap pattern. [Figure 5] This is a set of three timing diagrams showing possible measurement gap patterns according to the embodiment. [Figure 6] This is a set of three timing diagrams showing three examples of measurement gap patterns. [Figure 7] This timing diagram shows examples of initial measurement gap patterns and newly requested measurement gap patterns. [Figure 8] This timing diagram shows another example of the initial measurement gap pattern and another example of the newly requested measurement gap pattern. [Figure 9] This is a signal flow diagram illustrating an example of signal exchange between WTRU, gNB, and LMF to request a new positioning reference signal (PRS) configuration. [Figure 10] This timing diagram shows an example of the duration of the PRS prioritization window. [Figure 11] This figure shows an example of a method for constructing a measurement gap for WTRU positioning determination. [Figure 12] This figure shows another example of a method for constructing a measurement gap for WTRU positioning determination. [Figure 13]This figure shows another example of a method for constructing a measurement gap for WTRU positioning determination. [Figure 14] This figure shows another example of a method for constructing a measurement gap for WTRU positioning determination. [Figure 15] This figure shows an example of a method for requesting a measurement gap configuration. [Figure 16] This figure shows another example of a method for requesting a measurement gap configuration. [Figure 17] This figure shows another example of a method for requesting a measurement gap configuration. [Modes for carrying out the invention]

[0005] 1. Introduction The following detailed description includes numerous specific details to provide a complete understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details described herein. In other examples, well-known methods, procedures, components and circuits are not 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 essentially (collectively "provided") herein, disclosed, or otherwise provided.

[0006] 1.1 Exemplary Network for Implementation of Embodiments Figure 1A shows an exemplary 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, message transmission, and broadcast to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique-word OFDM (UW-OFDM), resource block filtering OFDM, and filter bank multicarrier (FBMC).

[0007] As shown in Figure 1A, the communication system 100 may include radio transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, but it will be understood that the disclosed embodiments intend any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a radio environment. For example, WTRU102a, 102b, 102c, and 102d, any of which may be referred to as “station” and / or “STA”, may be configured to transmit and / or receive radio signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscriber-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, radio 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 radio devices operating in an industrial and / or automated processing chain context), consumer electronics devices, and devices operating in commercial and / or industrial radio networks. Any of WTRU102a, 102b, 102c, and 102d may interchangeably be referred to as UE.

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

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

[0010] Base stations 114a and 114b may communicate with one or more WTRUs 102a, 102b, 102c, and 102d via an air interface 116, which may be any suitable radio 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 described above, the communication system 100 can be a multiple access system and can use one or more channel access schemes such as, for example, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a within RAN 104 / 113, and the WTRUs 102a, 102b, 102c can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish air interfaces 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

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

[0013] In one embodiment, the base stations 114a and the WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish 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, for example, using the dual connectivity (DC) principle. Accordingly, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies transmitted to / from multiple types of base stations (e.g., eNBs and gNBs) and / or transmissions.

[0015] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), 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), etc.

[0016] The base station 114b in Figure 1A may be, for example, a wireless router, Home Node B, Home eNode B, or access point, and any suitable RAT may be used to facilitate wireless connectivity in local areas such as offices, homes, vehicles, campuses, industrial facilities, aerial corridors (for use by drones), roads, etc. In one embodiment, the base station 114b and WTRU 102c, 102d may implement wireless technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and WTRU 102c, 102d may implement wireless technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base stations 114b and WTRUs 102c, 102d may establish picocells or femtocells using cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in Figure 1A, base station 114b may have a direct connection to the internet 110. Therefore, base station 114b may not need to access the internet 110 via CN 106 / 115.

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

[0018] CN106 / 115 may also function as a gateway for WTRU102a, 102b, 102c, 102d to access PSTN108, the Internet 110, and / or other networks 112. PSTN108 may include a public switched telephone network providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices, where these networks and devices use common communication protocols such as the transmission control protocol (TCP), the user datagram protocol (UDP), and / or the Internet protocol (IP) of the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may employ the same RAT as RAN104 / 113 or a different RAT.

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

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

[0021] The processor 118 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 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 a transceiver 120 which may be coupled to a transmit / receive element 122. Figure 1B shows the processor 118 and transceiver 120 as separate components, but it will be understood that the processor 118 and 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) via 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, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF signals and optical signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of radio signals.

[0023] Although the transmit / receive element 122 is shown as a single element in Figure 1B, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may utilize 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 radio signals via the air interface 116.

[0024] The transceiver 120 may be configured to modulate the signal transmitted by the transmit / receive element 122 and demodulate the signal received by the transmit / receive element 122. As described above, the WTRU 102 may have multimode capability. Therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0025] The processor 118 of the WTRU102 may be coupled to 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) and may receive user input from these. 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 any type of suitable memory, such as non-removable memory 130 and / or removable memory 132, and store data in such memory. 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, and the like. In other embodiments, the processor 118 may access information from memory not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data in such memory.

[0026] The processor 118 may receive power from the power supply 134, but may also be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for supplying power to the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), a solar cell, a fuel cell, 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) about the current location of the WTRU 102. In addition to or instead of the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may acquire location information by any preferred location determination method while maintaining consistency with one embodiment.

[0028] The processor 118 may be further coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, 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 peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, compass sensor, proximity sensor, temperature sensor, time sensor, geolocation sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, and / or humidity sensor.

[0029] WTRU102 may include a full-duplex radio in which the transmission and reception of some or all of the signals (e.g., associated with specific subframes for both UL (e.g., transmission) and downlink (e.g., reception)) may be in parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 for reducing and / or substantially eliminating self-interference via either hardware (e.g., chokes) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, WTRU102 may include a half-duplex radio for the transmission and reception of any of the signals (e.g., associated with specific subframes for either UL (e.g., transmission) or downlink (e.g., reception)).

[0030] Figure 1C is a system diagram illustrating RAN104 and CN106 according to one embodiment. As described above, RAN104 can communicate with WTRU102a, 102b, and 102c via the air interface 116 using E-UTRA wireless technology. RAN104 can also communicate with CN106.

[0031] RAN104 may include eNode-B160a, 160b, and 160c, but it will be understood that RAN104 may include any number of eNode-B while maintaining consistency with one embodiment. Each of eNode-B160a, 160b, and 160c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, eNode-B160a, 160b, and 160c may implement MIMO technology. Thus, eNode-B160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU102a.

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

[0033] The CN106 shown in Figure 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 aforementioned elements is shown as part of CN106, 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 MME162 can be connected to each of the eNode-B162a, 162b, and 162c in RAN104 via the S1 interface and can function as a control node. For example, the MME162 may perform roles such as authenticating users of WTRU102a, 102b, and 102c, activating / deactivating bearers, and selecting gateways for specific services during the initial attachment of WTRU102a, 102b, and 102c. The MME162 may provide control plane functionality for switching between RAN104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0035] The SGW164 can be connected to each of the eNode-B160a, 160b, and 160c in RAN104 via the S1 interface. The SGW164 can generally route and forward user data packets to and from WTRU102a, 102b, and 102c. The SGW164 can also perform other functions, such as anchoring the user plane during eNode B handovers, triggering paging when DL data is available to WTRU102a, 102b, and 102c, and managing and remembering the context of WTRU102a, 102b, and 102c.

[0036] SGW164 may be connected to PGW166, which may provide WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices.

[0037] CN106 can facilitate communication with other networks. For example, CN106 can provide WTRU102a, 102b, and 102c with access to a circuit-switched network such as PSTN108 to facilitate communication between WTRU102a, 102b, and 102c and conventional terrestrial line communication devices. For example, CN106 may include, or communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that functions as an interface between CN106 and PSTN108. In addition, CN106 may provide WTRU102a, 102b, and 102c with access to another network 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0038] Although the WTRU is shown as a wireless terminal in Figures 1A to 1D, in certain representative embodiments, such a terminal is intended to be able to use a wired communication interface (e.g., temporary or permanent) with a communication network.

[0039] In a typical 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 to or interfaces with another type of wired / wireless network that carries traffic entering and / or leaving the Distribution System (DS) or BSS. Traffic originating outside the BSS and destined for the STA may reach and be delivered to the STA via the AP. Traffic originating from the STA to destinations outside the BSS may be sent to the AP and then delivered to their respective destinations. Traffic between STAs within the BSS may be transmitted, for example, via the AP; a source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between a source STA and a destination STA (for example, 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 Independent BSS (IBSS) mode may not have APs, and STAs within or using IBSS (e.g., all STAs) may communicate directly with each other. The IBSS mode of communication may be referred to herein as “ad hoc” communication mode.

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

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

[0044] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidth and carrier 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 the TV White Space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using the non-TVWS spectrum. According to a typical embodiment, 802.11ah may support meter-type control / machine-type communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, including support for specific and / or limited bandwidths (e.g., support only for that). MTC devices may include batteries with battery life exceeding a threshold (e.g., to maintain very long battery life).

[0045] A WLAN system capable of supporting multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah includes a channel that can be designated as the 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 set and / or limited by an STA from among all STAs operating in a BSS that support the minimum bandwidth operating mode. In the 802.11ah example, the primary channel may be 1 MHz wide for an STA (e.g., an MTC type device) that supports (e.g., only) the 1 MHz mode, even if other STAs in the AP and 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 an STA (which only supports 1MHz operating mode) transmitting to the AP, a large portion of the frequency band may remain idle and could be considered busy, even if it were available.

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

[0047] Figure 1D is a system diagram showing RAN113 and CN115 according to an embodiment. As described above, RAN113 can communicate with WTRU102a, 102b, and 102c via air interface 116 using NR radio technology. RAN113 can also communicate with CN115.

[0048] RAN113 may include gNB180a, 180b, and 180c, but it will be understood that RAN113 may include any number of gNBs while maintaining consistency with the embodiment. Each of gNB180a, 180b, and 180c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, gNB180a, 180b, and 180c may implement MIMO technology. For example, gNB180a and 180b may transmit and / or receive signals to and from gNB180a, 180b, and 180c using beamforming. Thus, gNB180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU102a. In one embodiment, gNB180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB180a may transmit multiple component carriers to WTRU102a (not shown). A subset of these component carriers may be on the unauthorized spectrum, and the remaining component carriers may be on the authorized spectrum. In one embodiment, gNB180a, 180b, and 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU102a may receive coordinated transmissions from gNB180a and gNB180b (and / or gNB180c).

[0049] WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using transmissions associated with scalable numerology. For example, OFDM symbol intervals and / or OFDM subcarrier intervals may vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or having varying absolute time durations).

[0050] gNB180a, 180b, and 180c can be configured to communicate with WTRU102a, 102b, and 102c in standalone and / or non-standalone configurations. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c without accessing other RANs (e.g., eNode-B160a, 160b, and 160c). In a standalone configuration, WTRU102a, 102b, and 102c can utilize one or more of gNB180a, 180b, and 180c as mobility anchor points. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using signals in unlicensed bands. In a non-standalone configuration, WTRU102a, 102b, and 102c can communicate with and connect to gNB180a, 180b, and 180c, while also communicating with and connecting to other RANs such as eNode-B160a, 160b, and 160c. For example, WTRU102a, 102b, and 102c can implement DC principles for substantially simultaneous communication with one or more gNB180a, 180b, and 180c and one or more eNode-B160a, 160b, and 160c. In a non-standalone configuration, eNode-B160a, 160b, and 160c can function as mobility anchors for WTRU102a, 102b, and 102c, while gNB180a, 180b, and 180c can provide additional coverage and / or throughput to service WTRU102a, 102b, and 102c.

[0051] Each of the gNB180a, 180b, and 180c may be associated with a specific cell (not shown) and may be configured to handle wireless resource management decisions, handover decisions, user scheduling in UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a and 182b, and so on. As shown in Figure 1D, the gNB180a, 180b, and 180c may communicate with each other via the Xn interface.

[0052] The CN115 shown in Figure 1D may include at least one AMF182a, 182b, at least one UPF184a, 184b, at least one Session Management Function (SMF)183a, 183b, and optionally a Data Network (DN)185a, 185b. Although each of the aforementioned elements is shown as part of the CN115, it will be understood that any of these elements may be owned and / or operated by entities other than the CN operator.

[0053] AMF182a and 182b can be connected to one or more gNB180a, 180b, and 180c in RAN113 via the N2 interface and can function as control nodes. For example, AMF182a and 182b may perform roles such as authenticating users of WTRU102a, 102b, and 102c, supporting network slices (e.g., handling different PDU sessions with different requirements), selecting specific SMF183a and 183b, managing registration areas, terminating non-access stratum (NAS) signaling, and mobility management. Network slices can be used by AMF182a and 182b to customize CN support for WTRU102a, 102b, and 102c based on the type of service utilizing WTRU102a, 102b, and 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 similar. The AMF162 may provide control plane functionality for switching between RAN113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

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

[0055] UPF184a and 184b may be connected via the N3 interface to one or more gNB180a, 180b, and 180c in RAN113, thereby providing WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices. UPF184 and 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, and providing mobility anchoring.

[0056] CN115 can facilitate communication with other networks. For example, CN115 may include, or communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that functions as an interface between CN115 and PSTN108. Furthermore, CN115 may provide WTRU102a, 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 one embodiment, WTRU102a, 102b, 102c may be connected to local data networks (DN) 185a, 185b via UPF184a, 184b through an N3 interface to UPF184a, 184b, and an N6 interface between UPF184a, 184b and DN185a, 185b.

[0057] In view of Figures 1A to 1D and their corresponding descriptions, one or more of the functions described herein with respect to one or more of the WTRU102a to d, base stations 114a to b, e-nodes B160a to c, MME162, SGW164, PGW166, gNB180a to c, AMF182a to b, UPF184a to b, SMF183a to b, DN185a to b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0058] Emulation devices may be designed to implement testing of one or more other devices in a laboratory and / or 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 network to test other devices in a communications 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 network. Emulation devices may be directly coupled to another device for testing purposes and / or may perform testing using terrestrial radio communication. One or more emulation devices may perform one or more functions, including all of the above, while not implemented / deployed as part of a wired and / or wireless communication network. For example, an emulation device may be used in a test laboratory test scenario, and / or in a wired and / or wireless communication network that is not deployed (e.g., for testing purposes), to implement testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation device to transmit and / or receive data.

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

[0060] In downlink positioning methods, positioning reference signals (PRS) may be transmitted to the WTRU from multiple transmit / receive points (TRPs) of the radio 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 the measured reference signal time difference (RSTD) to the location management function (LMF) (e.g., send information indicating this). For example, the WTRU may return the measured reference signal received power (RSRP) for each PRS (e.g., send information indicating this). Based on the returned measurements, the LMF may position the WTRU. In another example, the WTRU may report the RSRP for a downlink (DL) angle-based positioning method (e.g., send information indicating this).

[0061] In uplink positioning methods, the WTRU may transmit a sounding reference signal (SRS) for positioning, configured, for example, by Radio Resource Control (RRC), to either the receiving point (RP) or the TRP. In timing-based methods, the TRP may measure the relative time of arrival (RTOA) of the received SRS signal and report the measurement to the LMF (e.g., send information indicating this). In angle-based uplink positioning methods, either the RP or TRP may measure the angle of arrival and report it to the LMF (e.g., send information indicating this).

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

[0063] In this specification, a “DL positioning method” may be referred to as any positioning method that can be based on a downlink reference signal, such as PRS. In such a positioning technique, the WTRU may receive multiple reference signals from the TP and measure either DL RSTD or RSRP. Examples of DL positioning methods may include either downlink-departure angle (DL-AoD) or downlink-arrival time difference (DL-TDoA) positioning.

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

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

[0066] DL-based positioning (and, for example, DL and UL positioning) may be either WTRU-based (e.g., a WTRU can perform positioning) or WTRU-assisted (e.g., a network can perform positioning operations using measurement reports transmitted from a WTRU).

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

[0068] The terms “pre-configuration” and “configuration” may be used interchangeably throughout the embodiments described herein.

[0069] The terms “non-serving gNB” and “adjacent 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 terms “PRS” and “PRS Resource” as described above may belong to different sets of PRS resources.

[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 by 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 by 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 respect to any communication network (e.g., at least one connection to a 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 described above may include parameters such as, for example, the measurement gap duration, the measurement gap repetition period, and the measurement gap periodicity.

[0078] The term "PRS resource" may be used to indicate time and / or frequency resources (e.g., OFDM symbols, resource elements) occupied by the PRS.

[0079] 1.2 Positioning Measurement in Networks A WTRU may, for example, transmit a request to initiate a measurement for positioning (e.g., information indicating such a request), and a WTRU may receive the configuration (e.g., information indicating such a configuration) of one or more measurement gaps (e.g., a measurement gap pattern). A WTRU may use measurement gaps to perform PRS measurements. For example, a WTRU may perform PRS measurements between one or more measurement gaps (e.g., configured measurement gaps).

[0080] PRS may be transmitted by one or more gNBs, or received by one or more gNBs. A gNB may be a serving gNB, or another gNB such as a neighboring gNB.

[0081] PRS can be transmitted by or received from a TRP in one or more cells. A cell can be a serving cell or another cell, such as an adjacent cell.

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

[0083] The WTRU may send a request (e.g., information indicating it) to the gNB to stop the measurement. The request (e.g., information) may include (e.g., indicate) a request to release the 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, network entity, or network element) that can be used for or to support positioning. Any other network element may be used instead of an LMF and may be applicable to the embodiments described herein.

[0085] The configuration of (one or more) measurement gaps via RRC may be semi-static and may lack support for dynamic configuration. The (one or more) measurement gaps can interfere with the transmission and reception of data in the active bandwidth portion (BWP), potentially leading to inefficiencies.

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

[0087] 2. Improvement of positioning procedures A method for dynamic reconstruction of a measurement gap based on conditions is described herein. A WTRU may transmit a request for reconstruction of the measurement gap (e.g., a message indicating the request), which may be signaled or indicated, for example, by either a MAC control element (MAC-CE) or uplink control information (UCI). A WTRU may decide to transmit a request based on any of the following types of conditions: ●Measurement based on conditions ● Scheduling request from gNB.

[0088] 2.1 Example of measurement gap configuration based on measurement status Example of a WTRU that sends a request based on measurements For example, a WTRU may send a request (e.g., information indicating it) to a gNB (e.g., a serving gNB) to change the measurement gap configuration, for example, via either a media access control-control element (MAC-CE) or uplink control information (UCI). A MAC-CE is sometimes referred to herein as an information element that can be inserted into a transport block to be transported over any type of transport channel of a radio network. A WTRU may send (e.g., decide to send) a request based on the measurement status (e.g., quality or value) of one or more PRS resources. A WTRU may receive information indicating the PRS configuration from, for example, an LMF. Information indicating the PRS configuration may be received via signaling such as LTE positioning protocol (LPP) signaling (e.g., LPP messages). A WTRU may, for example, initially send (e.g., to a gNB) a request (e.g., information indicating it) to configure a measurement gap. The configuration of (one or more) measurement gaps may comprise a configuration of measurement gap parameters, which may include any of the following: measurement gap length, measurement gap periodicity, and measurement gap offset. A WTRU may request (e.g., transmit) that it perform measurements on PRS from one or more serving gNBs and non-serving gNBs. Parameters related to the measurement gap, such as the measurement gap length, measurement gap periodicity, and measurement gap offset, are shown in Figure 2. During the measurement gap, the length of which is shown as the measurement gap length in Figure 2, the WTRU may not be expected to transmit or receive data. Outside the measurement gap, the WTRU may be expected to perform measurements on (one or more) PRSs.

[0089] A WTRU may consist of one or more thresholds, one or more time windows, and one or more durations that the WTRU can use to decide whether to request either a measurement gap configuration (e.g., a pattern) or a measurement gap configuration (e.g., a pattern) update, e.g., a change (e.g., it may receive configuration information indicating this). 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 (e.g., information indicating it) for either a measurement gap pattern or a measurement gap pattern update if the quality of one or more PRS or PRS-related measurements meets a criterion (e.g., above (or below) a pre-configured threshold). For clarity, meeting a criterion (e.g., condition) (e.g., intensity, quality, stability) is described throughout the embodiments described herein in comparison to a threshold value (e.g., greater than or less than a threshold). The embodiments described herein are not limited to threshold-based criteria (e.g., conditions). Any other kind of conditions and parameters (e.g., whether or not a value falls within a range) 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) or 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 or the linear mean of the RSRP of the PRS (for example, over a configured time window) is greater than or equal to (or less than) a configured threshold. ● Either the RSRP of the PRS or the linear mean of the RSRP of the PRS (e.g., over a configured time window) is greater than (or less than) a configured threshold for the configured duration. ● Either the variance or standard deviation of the WTRU location estimate (for example, in the case of WTRU-based positioning) is less than (or greater than) a configured threshold that the WTRU can receive (for example, from a gNB or LMF).

[0091] For example, a PRS may be transmitted from a TRP in either a serving gNB / cell or a non-serving gNB / cell. Information indicating measurements performed in the PRS and related measurement reports may include information indicating one or more of the following, so that LMF or gNB can 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] Requests for measurement gap patterns (or pattern updates) can be sent by the WTRU to the serving gNB.

[0093] Based on the received PRS measurements, WTRU can determine (for example, calculate) the linear mean, variance, and standard deviation of RSRP.

[0094] The WTRU may transmit a request for a new measurement gap configuration pattern (e.g., information indicating it) when the WTRU is performing either WTRU-assisted positioning or WTRU-based positioning.

[0095] For example, if a WTRU determines that the RSRP of a PRS received from a serving gNB meets a criterion (e.g., exceeds a threshold), the WTRU may send a request for a measurement gap pattern to the gNB (e.g., via either MAC-CE or UCI). The WTRU may request a measurement gap pattern that does not (e.g., exactly) coincide with the PRS duration (e.g., the measurement gap pattern may be configured for a portion of the PRS duration so that the WTRU can perform a partial measurement of the PRS to which it was sent). As will be described in more detail below, the WTRU may include in its request information indicating one or more of the following indicators: ●Measurement gap pattern index (e.g., identifier), ● Number of symbols or slots to include in the measurement gap, ● For example, the start and end positions of the requested measurement gap, indicated by a symbol, slot, or frame number.

[0096] In another example, a WTRU may send a request to the gNB for the configuration of a measurement gap pattern if the PRS's RSRP meets the criteria over a configured duration (e.g., remains above, above, or below a configured threshold). For example, if a WTRU performs WTRU-based positioning, it may obtain its location estimate. In one example, a WTRU may send a request to the gNB for a measurement gap pattern if the measurements taken on the PRS are stable (e.g., meet the stability criteria). Based on the determination that one or more PRS measurements are stable, the WTRU may determine that some PRS measurements may be skipped and stopped. A WTRU may request that all or part of a measurement gap or measurement gap pattern be invalidated (e.g., it may send information to make such a request). Requests for either a measurement gap pattern or a measurement gap pattern update may include, or correspond to, a request to invalidate all or part of a measurement gap or gap pattern.

[0097] WTRU may determine the stability of a measurement based on whether a stability metric (e.g., either the variance or standard deviation of the WTRU's location estimate) satisfies the stability conditions (e.g., is at, above, or below a pre-configured threshold). For example, WTRU may determine that a PRS measurement is stable (e.g., meets the stability criteria) if either the variance or standard deviation of the WTRU's location estimate is below a configured threshold.

[0098] In another example, a WTRU may stop measuring PRS if an RSRP above a pre-configured threshold is obtained. In yet another example, a WTRU may stop measuring PRS (e.g., all) (e.g., used for WTRU-based positioning) if the WTRU determines that the location estimate meets stability conditions (e.g., is stable). A WTRU may send a request (e.g., to a gNB) to disable all or part of any measurement gaps and measurement gap patterns so that the WTRU can transmit or receive data in an active BWP.

[0099] For example, WTRU can be determined to satisfy the stability condition (e.g., it is stable) if either the variance or standard deviation of the location estimate is below a configured threshold.

[0100] A WTRU may, for example, send a request via MAC-CE or UCI to turn off, disable, or modify either the measurement gap or the measurement gap pattern. The request may include information indicating in the gNB or LMF that the WTRU may stop performing measurements for any of the indicated PRS and all PRS.

[0101] Figure 3 is a signaling flow diagram showing an example of signal exchange between WTRU 301, gNBs 303, 305, 307, and LMF 309. As an example, Figure 3 shows a serving gNB 303 and two non-serving gNBs, namely Neighbor_A gNB 305 and Neighbor_B gNB 307. In 312, the WTRU may receive PRS configuration information from LMF 309, for example via LPP. For example, the WTRU may send a location measurement instruction 314 to the serving gNB via RRC, which may include information indicating the configuration for the measurement gap. For example, the WTRU may receive a measurement configuration 316 from the network (e.g., RRC), for example via RRC.

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

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

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

[0105] A WTRU may send a request for a semi-persistent PRS to the network. The request may include information indicating a start time, end time, and duration. The request may be sent to the network using one of the following: UCI, MAC-CE, RRC, or LPP messages. Either the start time or end time may be indicated relative to a reference time (e.g., when the WTRU can send an on-demand request).

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

[0107] 2.2 Example of a measurement gap configuration based on scheduling Examples of measurement gap patterns and types For example, the measurement gap pattern may be determined, predefined, and configured (e.g., by receiving configuration information from either the serving gNB or LMF) using one or more parameters, but is not limited to: ● The duration of the measurement gap (e.g., length) can be determined based on the number of slots, the number of symbols, or the unit of milliseconds. ● Periodicity of the measurement gap duration, which can be expressed in units of slots, symbols, or time (e.g., ms). ● Offset (for example, either slot or symbol)

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

[0109] Regarding priority levels, for example, a first priority level and a second priority level for the measurement gap may be used, and the priority level of the measurement gap may be used by the WTRU to determine WTRU behavior when one or more (e.g., predefined) conditions are met. For example, if the measurement gap overlaps with one or more physical downlink control channel (PDCCH) search spaces, and 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 not measure the PRS (e.g., it may skip the measurement associated with the measurement gap, or measure the reference signal within the time available after monitoring the PDCCH search space). Otherwise, the WTRU may perform the measurement and 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 the 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, the PDCCH search space priority may be configured via higher-layer signaling for the associated search space or control resource set (CORESET) (by receiving configuration information).

[0111] For example, the priority level of the 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 the DCIs being monitored in the search space. For instance, if a priority index exists for DCI formats within a search space, that search space may be determined to have a higher priority than a search space where 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 instance, a search space with a lower search space id may have a higher priority than a search space with a higher search space id, and a search space id may be constructed for each search space.

[0114] With respect to time-domain behavior (e.g., periodic, aperiodic, and semi-persistent), aperiodic measurement gaps may have higher priority than periodic or semi-persistent measurement gaps. For example, if an aperiodic measurement gap overlaps with the PDCCH search space, the WTRU may perform the aperiodic measurement gap; if it overlaps with a periodic measurement gap, the WTRU may monitor the PDCCH search space. The time-domain behavior of a measurement gap may be associated with the time-domain behavior of a 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 determining the measurement gap pattern In embodiments, a WTRU may transmit information indicating a request for one or more measurement gap patterns, and each measurement gap pattern may be associated with a priority level (or type). A WTRU may, for example, receive configuration information indicating one or more measurement gap patterns in response to a request from a WTRU. A WTRU may receive configuration information from a serving gNB, for example. Measurement gap patterns may be selected and used based on one or more of the measurement gap pattern determination criteria. Measurement gap patterns within a configured measurement gap pattern may be determined based on one or more of the following exemplary measurement gap pattern determination criteria: ● A traffic type (e.g., URLLC) can be either configured or supported. For example, a first traffic type (e.g., URLLC) can be either configured or supported if one or more of the following conditions are met: Either a Short TTI Physical Downlink Shared Channel (PDSCH) reception or a Short TTI Physical Uplink Shared Channel (PUSCH) may be configured and supported, and a Short TTI PDSCH or PUSCH may be a PDSCH or PUSCH transmission that occupies fewer symbols in the slot than the symbols available for DL ​​or UL. ○Priority indications may be configured in DCI format. ● The PDCCH search space can be composed of priority levels higher than the threshold. ●PRS can be composed of priority levels higher than the threshold. ● Bandwidth portion ID (BWP-id), ● Carrier index or cell index, ● Bandwidth and / or subcarrier spacing.

[0116] In embodiments, the 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 measurement gap patterns from the LMF (e.g., or gNB) from that set.

[0117] In embodiments, the set may be determined as a function of the measurement gap duration. For example, a first set of measurement gap patterns may have measurement gap durations within a first threshold, and a second set of measurement gap patterns may have measurement gap durations 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 subsequent WTRU behavior where higher priority traffic may be allowed. In an embodiment, the WTRU may request (or decide to request) a measurement gap pattern that allows the WTRU to receive any of the downlink signals (e.g., channel status reference signals (CSI-RS), SSB), data channels (e.g., PDSCH), and control channels (e.g., PDCCH) if the WTRU is scheduled to receive downlink signals and / or channels with a higher priority than the initial (e.g., default) measurement gap pattern.

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

[0120] Examples of measurement gap interruptions In the embodiment, the WTRU may monitor the PDCCH search space during the measurement gap period if one or more of the following conditions are met (otherwise, the WTRU may skip monitoring the PDCCH search space during the measurement gap period): ●WTRU may receive a first type of data within a first time window prior to the measurement gap, and the first type of data may be a PDSCH scheduled by DCI having a priority index (e.g., priority index = 1). ○ The first time window may begin with x1 slots from the first slot of the associated measurement gap and end with x2 slots. ■x1 may be determined based on at least one of the following: ● Upper layer configuration ● Predetermined value ●As a function of the duration of the measurement gap ●As a function of the priority level associated with either the PDCCH search space or the measurement gap ● Subcarrier spacing ● Bandwidth partial identity (e.g., identifier) ■x2 may be determined based on at least one of the following: ●WTRU processing time (e.g., WTRU capacity) ● Subcarrier spacing ● Bandwidth partial identity (e.g., identifier) ●The WTRU may transmit a NACK within the first time window, and its associated PDCCH search space for retransmission may be located within the measurement gap. ●WTRU may receive instructions from gNB via DCI, for example.

[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, and the second time window may be located within the measurement gap, equal to or shorter than the measurement gap. One or more of the following behaviors may apply: ● The second time window may begin from the first slot of the measurement gap. ● The second time window length can be determined based on any one or more of the following: ○ Upper layer configuration ○ Predetermined value ○ Function of measurement gap duration ○ A function of priority level associated with either the PDCCH search space or the measurement gap. ○ Subcarrier spacing ○ Bandwidth partial identity ○ Length of the first time window

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

[0123] A WTRU can measure a portion of a PRS resource using a measurement gap pattern configured by a gNB. For example, if the duration of a PRS resource is 2 milliseconds and the measurement gap pattern is applied to the last 1 millisecond of the PRS resource, the WTRU can perform a measurement on the first 1 millisecond and report the measurement to the LMF (e.g., send information indicating it).

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

[0125] In another example, a WTRU might report to the LMF the number of resources on which it could potentially perform a measurement (for example, by sending information indicating this).

[0126] In another example, a WTRU may report quality indicators to the LMF for measurements of PRS for which the WTRU has performed partial measurements (for example, by sending information indicating this).

[0127] 2.3 Details regarding the measurement gap pattern Examples of measurement gap patterns Figure 4 shows an example of the difference between the initial measurement gap (e.g., one of the configured initial default gaps, or any other configured gap in use prior to the request for a new measurement gap configuration) and the requested measurement gap pattern. 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] For example, a measurement gap pattern may comprise several units, and the duration of each unit may be indicated. For instance, there may be multiple values ​​for the duration of a measurement gap. The duration of a unit may be represented, for example, in seconds, symbols, and slots. For instance, a unit may comprise one or more subunits, and the location of each subunit within the group in the measurement gap may be indicated. For instance, a unit may include either adjacent or non-adjacent subunits in the time domain.

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

[0130] In another example, a measurement gap pattern may be a set of periods of duration (e.g., length) that can be repeated with periodicity. A measurement gap pattern may be represented (e.g., associated with) the periodicity and duration of a time pattern. A measurement gap pattern may be assigned (e.g., associated with) an index (e.g., 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. A WTRU may include an index indication in either MAC-CE or UCI if a measurement gap is required.

[0131] Another example of a set is shown in Figure 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 with a duration of 2T. Measurement gap pattern (e.g., assigned) index 1 may correspond to a measurement gap with a duration of 1T, where the first half of the duration (e.g., only the first half) may be activated. Measurement gap pattern (e.g., assigned) index 2 may correspond to a measurement gap with a duration of 1T, where the second half of the duration (e.g., only the second half) may be activated. Although not shown in Figure 5, other measurement gap patterns (e.g., index 3) may correspond to the case where no measurement gap is formed.

[0132] In another example, the WTRU may represent the measurement gap pattern by a bitmap, as shown in Figure 5. For example, the measurement gap pattern associated with index 0 may correspond to a bitmap pattern of "11", where (for example) each bit may correspond to a time unit of 1T, the first bit may correspond to the first half of a 2T-length measurement gap, and the second bit may correspond to the second half of a 2T-length 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 Figure 5, the WTRU may perform measurements on PRS transmitted from either the serving gNB or TRP within 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 either the neighboring gNB or TRP within the neighboring cell. For example, if a measurement performed on a PRS transmitted from either the serving gNB or TRP within the serving cell, such as an RSRP, meets a condition (e.g., exceeds a pre-configured threshold), the WTRU may send a request to the serving gNB for the measurement gap pattern or bitmap pattern "01" associated with index 2.

[0134] The embodiments described herein are not limited to measurement gap patterns with a duration of 2T, as shown in the example 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 Figure 6. In this example, a unit of measurement gap may consist of four subunits, where (for example, each) subunit may have a duration of T / 2. Different patterns of subunit location relative to the pattern may exist. For example, in a measurement gap pattern associated with index 1, the subunits may be located at t=0 and t=T. For example, (for example, each) measurement gap pattern may be represented by a bitmap pattern (for example, it may be associated with a bitmap pattern). For example, a measurement gap pattern associated with index 1 may be represented as "1010" as shown in Figure 6.

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

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

[0138] For example, during a shorter duration of the measurement gap, the WTRU may measure (e.g., decide to measure) fewer measurement samples. For example, the WTRU may measure and / or process (e.g., decide to measure) half of the PRS resources configured by the network. The WTRU may decide to request a measurement gap (e.g., send requested information) via UCI, MAC-CE, and RRC based on at least one of the following conditions: ● For example, a quality metric representing the measured quality of the PRS (e.g., either the RSRP of the PRS or the linear mean of the RSRP of the PRS) that meets a first criterion (e.g., exceeds a configured threshold) over a configured time window. ● For example, a quality metric representing the measured quality of the PRS (e.g., either the RSRP of the PRS or the linear mean of the RSRP of the PRS), where the second criterion is met (e.g., exceeds the (e.g., configured) threshold) for only the duration (e.g., configured) over the (e.g., configured) time window. ●For example, a stability metric such as the variance and standard deviation of the location estimate of a WTRU (e.g., in the case of WTRU-based positioning) that satisfies a third criterion (e.g., the WTRU is below a threshold that it can receive (e.g., from gNB or LMF) (e.g., configured), ●Explicit instructions from the network (e.g., gNB, LMF).

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

[0140] Example of a PRS configuration to accommodate the updated measurement gap In one embodiment, the WTRU may determine that a PRS can be configured in the LMF after the gNB may have acknowledged a configuration request for a measurement gap, and as a result, 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 can configure the PRS such that the WTRU cannot receive the PRS during the portion of the measurement gap indicated by "0" in the bitmap pattern. The gNB may send the measurement gap configuration request generated by the WTRU to the LMF, for example, so that the LMF can update the PRS configuration using the measurement gap configuration information.

[0141] Examples of activating or deactivating measurement gaps: semi-permanent measurement gap patterns For example, a WTRU may send a request (e.g., information indicating such a request) to the gNB (e.g., via either MAC-CE or UCI) to activate a measurement gap pattern. 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 to the WTRU indicating any of the accepted measurement gap configuration parameters (e.g., measurement gap pattern, measurement gap index, measurement gap length, and measurement gap periodicity). For example, an acceptance instruction from the gNB may include information indicating explicit acceptance of the request.

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

[0143] For example, a WTRU may send a request to a gNB, which includes information indicating the requested pattern by other means, such as a bitmap, as previously shown in 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 a request (for example, in response to a 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 can be received from the gNB. For example, a gap pattern that can be activated may be the same as the pattern that may be requested (e.g., it may contain the requested pattern) (e.g., gaps in the requested pattern may be contained in the gaps of the activated pattern), or it may be a different pattern.

[0145] In another example, a measurement gap pattern may be activated for a pre-configured duration (e.g., only that duration). For example, a WTRU may send a request containing information indicating the (e.g., requested) duration of the measurement gap activation. For example, a 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., when it is determined that a time amount (e.g., corresponding to the timer) has elapsed since receiving information indicating gap pattern activation).

[0146] In another example, the measurement gap pattern does not need to 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 that 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 described above, a measurement gap pattern may be assigned a unique index (e.g., an identifier that can be used to identify the measurement gap pattern) (e.g., may be associated with a unique index). Both WTRUs and gNBs may indicate a gap pattern by a configured or associated index. Information indicating a gap pattern (e.g., an index) may be included in any of the following: measurement gap pattern requests, measurement gap pattern configurations, measurement gap pattern activations, and measurement gap pattern deactivations. For example, if a WTRU sends information indicating a request for either a measurement gap pattern or a measurement gap pattern modification, the WTRU may indicate the requested measurement gap pattern using the corresponding measurement gap pattern index (e.g., by including it in the information).

[0148] In another example, a measurement gap pattern may be configured with or associated with a bitmap pattern. Both WTRUs and gNBs can indicate a gap pattern by a configured or associated bitmap pattern. Information indicating a gap pattern (e.g., a bitmap) may be included in any of the following: a measurement gap pattern request, a measurement gap pattern configuration, a measurement gap pattern activation, and a measurement gap pattern deactivation. For example, if a WTRU transmits information indicating a request for either a measurement gap pattern or a measurement gap pattern modification, the WTRU may indicate the requested measurement gap pattern using (e.g., by including) a bitmap pattern (e.g., within the information).

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

[0150] In the requirements, the WTRU may include parameters (e.g., only those parameters) that may differ from the parameters initially (previously) configured for the measurement gap. For example, using the example shown in Figure 7, where the initial 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 a parameter (e.g., only) that may differ from the initially configured parameters.

[0151] In one example, a WTRU may send a request to the gNB via MAC-CE, UCI, PUSCH, or PUCCH that includes information indicating whether to activate or deactivate a measurement gap. In response to the request from the WTRU, the WTRU may receive information via DCI, MAC-CE, PDCCH, or PDSCH indicating an activation or deactivation command for the requested measurement gap. In another example, the WTRU may receive information from the network via MAC-CE indicating a deactivation command without a request to deactivate a measurement gap, for example. For example, the WTRU may determine that the requested measurement gap can be deactivated after a duration (e.g., the length of the measurement gap in terms of a number of slots, symbols, frames, subframes, or seconds) has been reached. In yet another example, the WTRU may receive information from the network via MAC-CE indicating a deactivation command to deactivate the requested measurement gap, i.e., a first measurement gap. The deactivation command may activate a second measurement gap (e.g., simultaneously). The second measurement gap may be the same as the first measurement gap in terms of its configuration (e.g., "on" and / or "off" duration, length, periodicity). Such (e.g., simultaneous) activation / deactivation schemes may allow for reduced signaling overhead for either activation or deactivation, if (e.g., each) measurement gap has (e.g., the same) duration. In another example, the WTRU may send requests to the network for two measurement gaps (e.g., a first and a second measurement gap), which may have different configurations. In one example, the WTRU may send requests to the network via either the UCI or MAC-CE, containing information indicating whether to activate or deactivate a measurement gap, provided 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 measurement gaps (e.g., pre-configured) is not available to either the WTRU or the network (e.g., gNB, LMF), the WTRU may send a request for measurement gaps to the network using either a fallback or default method, for example, by sending a request to configure measurement gaps via RRC. In another example, the WTRU may receive an indication from the network (e.g., LMF, gNB) that measurement gaps may have already been requested by the network. For example, an LMF may send a request to the serving gNB to configure measurement gaps based on (one or more) PRS configurations provided by the LMF to the serving gNB. The WTRU may receive information such as the measurement gaps associated with the configured PRS via DCI, MAC-CE, RRC, and LPP messages, for example, DCI, MAC-CE, RRC, and the network (e.g., LMF or gNB). For example, if a WTRU receives a signal from the network indicating that a measurement gap may already be configured so that the WTRU can perform and process measurements on a configured PRS, it may decide to either cancel or skip sending a request for a measurement gap to the network.

[0152] Example of triggering a measurement gap: Aperiodic measurement gap pattern For example, a WTRU might transmit information indicating a request for a measurement gap pattern by a UCI. For instance, via a UCI, a WTRU might transmit information indicating a specific time when a measurement gap pattern may be triggered. For example, the timing of activating an active measurement gap pattern may be pre-configured by the gNB. A WTRU may be pre-configured by the trigger timing for the measurement gap (for example, it may have received configuration information indicating this). For example, a WTRU may be configured to begin using a requested measurement gap pattern after X slots, after which the WTRU may have sent a UCI requesting the measurement gap pattern to the gNB.

[0153] Example of requirements for measurement gap patterns For example, information indicating a requirement for a measurement gap may include one or more of the following: ●Measurement gap pattern index (e.g., identifier), ● Duration of the measurement gap pattern for semi-permanent measurement gaps ● Timing when the measurement gap may be activated

[0154] Information indicating a request for either a measurement gap pattern or a measurement gap pattern update may be transmitted via MAC-CE, as well as via physical layer signaling, such as UCI, PUCCH, and RRC signaling. UCI may include fields that may be reserved for measurement gap pattern requests.

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

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

[0157] In the embodiment, the measurement gap may be configured by the WTRU as required by the bitmap pattern. For example, it may be determined that different measurement gaps can be configured by either the gNB or the LMF if at least one of the following conditions is met: ●For example, a first quality metric, such as either the RSRP of the PRS corresponding to a "1" in the bitmap pattern within the measurement gap, or the linear mean of the RSRP, satisfies a first condition (e.g., it is below a (pre-configured) threshold for a (pre-configured) duration). ●For example, a first stability metric, such as the standard deviation, range, or variance of the RSRP corresponding to a "1" in the bitmap pattern within the measurement gap, satisfies the second condition (e.g., it is greater than or equal to a (pre-)configured threshold over a pre-configured duration). ●In the case of WTRU-based positioning, a second stability metric, such as the standard deviation, range, or variance of the estimated position of the WTRU, satisfies a third condition (e.g., exceeds a threshold).

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

[0159] In embodiments, 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 containing only "1") can be configured. In such cases, the WTRU may receive a PRS within the initial (e.g., default) measurement gap. For example, the WTRU may receive a PRS after a duration (e.g., any of the pre-configured slots, symbols, frames, time, etc.).

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

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

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

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

[0164] gNB may include a requirement for LMF in one or more of the following (for example, via NR Positioning Protocol A (NRPPa)): ●Requirements for a new PRS configuration based on measurement gap configuration requests received from WTRU. ● Additional length of measurement gap that WTRU can provide, ● Changes in the period of the measurement gap, ● PRS measurement reports that may be associated with measurement gap configuration requirements from WTRU.

[0165] The measurement gap length may allow multiple PRSs to fit within its window. Different PRSs may have the same or different durations and may be transmitted from different TRPs. The LMF may configure new PRSs that can be transmitted through the requested measurement gap. For example, in the example shown in the timing diagram of Figure 8, the WTRU may send information to the gNB requesting (e.g., requesting) that the gNB increase the current length L of its measurement gap by length L'' so that the WTRU can receive additional PRSs within the gap. The gNB may send the requested measurement gap (or a change in the measurement gap configuration) to the LMF, and the LMF may configure new PRSs that can be transmitted within a duration of L''-L. The new (or additional) PRS configuration may be transmitted from any of the different TRPs and one of the existing TRPs having a duration of L''-L.

[0166] An example of signal exchange between WTRU901, gNB903, 905, 907, 909, and LMF911 is shown in Figure 9. As an example, Figure 9 shows a serving gNB903 and three non-serving gNBs, namely Neighbor_A gNB905, Neighbor_B gNB907, and Neighbor_C gNB909.

[0167] For example, WTRU901 may receive PRS configuration information from the network (e.g., from LMF911 via LPP) (920). For example, WTRU may send location measurement instructions, which may include configuration for measurement gaps, to serving gNB909 via RRC922.

[0168] For example, WTRU901 may receive (e.g., RRC) information indicating the measurement configuration from the network via RRC924, for example. WTRU901 may also receive PRS926, 928, and 930 transmitted from serving gNB909 and two non-serving gNBs, namely Neighbor_B gNB905 and Neighbor_A gNB907.

[0169] For example, WTRU901 may perform a measurement on the received PRS in 934. For example, WTRU901 may return a measurement report 936 to LMF911 (for example, via gNB) (for example, it may send information indicating this). For example, the measurement may be in NAS format and may be sent to serving gNB909 in PUSCH, and then from serving gNB909 to LMF911.

[0170] For example, WTRU901 may send a request for a measurement gap (e.g., configuration) 938 to serving gNB909 (e.g., via either MAC-CE or UCI) based on configured measurement conditions.

[0171] Serving gNB909 may send a request for a new PRS configuration 940 to LMF911 based on the measurement gap request (938) from WTRU901.

[0172] Although not shown in the diagram, LMF911 may send an acknowledgment message to serving gNB909 about the new / requested PRS configuration. For example, LMF911 may send information to WTRU901 indicating the new PRS configuration, including the PRS configuration that may have been configured in step 920.

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

[0174] In this example, the new measurement gap can be longer than the previous length L (for example, it may include an additional length L'' relative to the total length L+L'') so that the WTRU can receive additional PRS from, for example, a third neighboring cell Neighbor_C gNB903 and perform the measurement. For example, WTRU901 can use the new measurement gap pattern configuration to begin receiving PRS944, 946, 948, and 950 from serving cell 909 and three neighboring gNB903, 905, and 907.

[0175] An example of how WTRU can determine the duration of the measurement gap. In an embodiment, the WTRU may be pre-configured with one or more measurement gaps from the gNB (e.g., it may receive configuration information indicating a list thereof). The WTRU may receive instructions to request measurement gaps having a longer duration than the initial (e.g., default) measurement gap if one or more (e.g., (pre-)configured) conditions are met. For example, each measurement gap may have a length longer than the length of the initial (e.g., default) measurement gap. For each length, the WTRU may receive (information indicating) an association with a PRS configuration from the LMF, for example. In such an embodiment, if the duration of the default measurement gap is 10 ms, then the duration of 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 from the serving gNB indicating measurement gaps having durations of 12 ms and 14 ms (e.g., a list thereof). From the LMF, the WTRU may receive TRP IDs (e.g., TRP6 and TRP7) along with instructions that the TRP IDs may be associated with an additional length of measurement gap provided by the gNB. The WTRU may determine that during a 12 ms measurement gap, it may receive a PRS with a duration of 2 ms from TRP6, in addition to the PRS transmitted from the five TRPs. The WTRU may determine that during a 14 ms measurement gap, it may receive a PRS with a duration of 2 ms from TRP6 and TRP7, in addition to the PRS transmitted from the five TRPs.

[0176] In an embodiment, the WTRU may receive from the LMF information including parameters 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 below 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: ● For example, a quality metric such as RSRP and a linear average of RSRP over time for at least one PRS satisfies the first condition (e.g., is below a threshold). ●For example, a stability metric such as the standard deviation, range, or variance of the estimated location of the WTRU satisfies the second condition (e.g., it is above a threshold). ●The remaining time until the latency (e.g., value, characteristic) satisfies a third condition (e.g., is below a threshold).

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

[0180] In the embodiment, the WTRU may not (and should not) receive any non-PRS signals and / or channels in the PRS-BWP. In the embodiment, the WTRU may receive information from the LMF indicating the PRS configuration associated with the PRS-BWP. The PRS-BWP may have (and may be associated with) a specific ID, center frequency, and frequency layer ID, which may be transmitted to the WTRU by either the LMF or the gNB. In the 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 DCI, MAC-CE, and RRC.

[0181] In the 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 the time at which the WTRU can find the PRS-BWP and the sequence of center frequency / bandwidth / BWP. Such a hopping pattern may exist within the BWP. For example, the WTRU may consist of subbands within the BWP, or it may consist of a hopping pattern of subbands.

[0182] In the embodiment, the WTRU may receive instructions from the gNB to switch to PRS-BWP. The WTRU may receive instructions from the gNB via DCI, MAC-CE, or RRC. In the embodiment, such instructions may be transmitted after the WTRU has received information from the LMF indicating PRS-BWP and PRS configuration.

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

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

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

[0186] If a window is explicitly configured (for example, by receiving configuration information that explicitly indicates a window), the WTRU may receive information from the network (e.g., either the gNB or LMF) indicating the window's start position, duration, or end position. If a window is implicitly configured, the WTRU may determine the window's start as either the first transmit or receive opportunity of the PRS, and the window's end as either the last transmit or receive opportunity of the PRS.

[0187] For example, WTRU may determine the start position, end position, and duration of a window based on at least one or a combination of the following factors (e.g., criteria): ● The start of the window for the first send or receive opportunity in PRS, and the end of the window for the last send or receive opportunity in PRS. ● The start of the window as the first transmit or receive opportunity of the PRS and the end of the window as a time (e.g., represented by the number of symbols, slots, frames, and seconds from the first transmit / receive of the PRS) WTRU may transmit the last measurement report (e.g., any of the RSRP report, RSTD report, or Rx-Tx time difference). ● The start of the window as the first opportunity to transmit or receive a PRS and the end of the window as a time (e.g., represented by a number of symbols, slots, frames, and seconds since the last transmit / receive of a PRS). The WTRU can process the measurement (e.g., any of the RSRP report, RSTD report, or Rx-Tx time difference). An example is shown in Figure 10 where the window may start when WTRU 1001 can receive the first PRS (e.g., thereafter) (t1) and end when the WTRU can finish processing the measurement (e.g., thereafter) (t2). ● The window starts as the beginning of the preparation time to receive a PRS before the first opportunity to transmit or receive a PRS, and ends as the time it takes for the WTRU to complete processing of the PRS measurement (e.g., RSTD, RSRP, or Rx-Tx time difference) (e.g., expressed as a number of symbols, slots, frames, or seconds from the first transmit / receive of the PRS).

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

[0189] Example of determining window priority levels For example, WTRU may determine either the priority level of the window or the priority level of the PRS within the window based on at least one of the following: ● Receipt of information including explicit instructions from the network regarding priority levels. For example, instructions may be received in any of the LPP messages (e.g., either an LPP support data message or an LPP location request message) and in Access Layer (AS) layer messages (e.g., any of RRC, MAC CE, and DCI). ● The time from the first reception of the PRS to reporting the first measurement (for example, a shorter time limit may indicate higher priority, and a longer time limit may indicate lower priority). ● The PRS type configured for the window (e.g., periodic, semi-permanent, or aperiodic). For example, WTRU may determine that either aperiodic PRS or semi-permanent PRS can be associated with a higher (e.g., highest) priority level. ● Priority level associated with the logical channel. The WTRU may decide to set either the PDSCH or PDCCH to the same priority level as the associated logical channel. For example, if the priority level of the logical channel associated with the PDSCH is level 1 (e.g., "High"), the WTRU may decide that the priority level of the PDSCH may also be level 1 (e.g., "High"). ●Configuration related to PRS (e.g., time density, frequency density, duration, repetition coefficient, comb pattern). ● Decoding time for either PDCCH or PDSCH. For example, WTRU may be configured by the network (e.g., from the network) using a threshold (e.g., configuration information indicating the threshold may be received). If the decoding time for PDCCH exceeds the threshold, WTRU may determine that the priority level associated with PDCCH may be higher than the priority level associated with PRS (e.g., the priority level associated with PRS).

[0190] In the example, the WTRU may consist of one or more PRS configurations that may be associated with a window (e.g., it may receive information indicating this). Different PRS configurations may be assigned (e.g., configured) with different priority values, which may be pre-configured in the WTRU along with the PRS configurations. The priority of both the window and the PRS configuration may be determined by the WTRU based on either explicit or implicit indications (e.g., information containing such indications). The WTRU may receive one or more PRS associated with different PRS configurations when (e.g., after) a window may be configured. If the WTRU receives one or more PRS (e.g., after the window may be configured), it may determine which PRS to measure and / or process the measurement based on the priority values ​​associated with the PRS configuration and the window. For example, the WTRU may select PRS for either measurement and / or processing according to the priority order (from higher to lower) of the priority values, which may be less than or equal to the window's priority. In such cases, WTRU may select a PRS with a high (e.g., best) priority value that may be below the window priority, and then select a PRS with the next highest (e.g., best) priority level. WTRU may select a second PRS, for example, if the measurement performed using the first PRS does not meet the criteria (e.g., the RSRP measurement of the first PRS falls below the RSRP threshold).

[0191] (i) If the WTRU is unable to determine a PRS configuration with a priority level lower than or equal to the window priority, and / or (ii) if the WTRU determines the availability of at least one PRS configuration with a priority level higher than or equal to the window priority, and no other PRS with a lower priority is available, the WTRU may do one or more of the following: ● For example, send information to the network that includes an indication to change the window priority to match the priority of the PRS that can be determined by the WTRU to be available. ● Send information to the network, including instructions to release the window. ● For example, information is sent to the network that includes an indication requesting the configuration of a measurement gap in order to enable the measurement to be performed using an available PRS.

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

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

[0194] Example of WTRU behavior when a window is interrupted A window may be interrupted, for example, by either a DL reception or UL transmission having a higher priority than the window's priority level. A WTRU may suspend the window before either a DL reception or UL transmission and resume the window after either of them may be completed.

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

[0196] In the embodiment, the decision to stop the window, for example, to stop measuring the PRS and, for example, to stop processing the PRS measurement, may depend on the duration of the interruption, for example, the duration of either a DL reception or UL transmission having a higher priority.

[0197] For example, after a WTRU may suspend a window, it may decide to resume the window at another time. A WTRU may receive informational configurations from the network using one or more windows. A WTRU may decide to resume PRS measurements and, for example, PRS processing at the next (e.g., earliest) opportunity of the window. A WTRU may receive configurational information from the network (e.g., gNB, 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, ● Window time offset.

[0198] Examples of WTRU behavior during the window for DL ​​and UL positioning For DL ​​and UL positioning (e.g., multi-RTT), the WTRU may receive a PRS, transmit an SRS for positioning (SRSp), and report to the network the difference between the transmission time of the SRSp and the reception time of the PRS (e.g., the Rx-Tx time difference) (e.g., it may transmit information indicating this). During a time window, the WTRU may associate the window's priority level with the SRSp. For example, the WTRU may decide to prioritize the transmission of the SRSp over other UL transmissions (e.g., any of PUSCH, PUCCH, or SRS) that may be scheduled before or after the window may be configured, and may transmit the SRSp during the window. An exemplary embodiment of this is described below. 1. The WTRU may be configured from the LMF using a multi-RTT positioning method (for example, configuration information indicating this may be received). 2. The WTRU may receive information (e.g., the first) from the LMF indicating the configuration for the semi-persistent PRS. 3. The WTRU may receive information (e.g., a second) from the gNB indicating the SRSp configuration. 4. The WTRU may determine either the window duration or the start time based on the configuration for the PRS received from the LMF (e.g., the start time of the PRS transmission, the duration of the PRS transmission). 5. Based on the type of PRS (e.g., semi-persistent PRS), the WTRU may determine that window and SRSp transmissions can be associated with high (e.g., best) priority. 6. The WTRU may receive information (e.g., a third) from the gNB associated with the PRS indicating permission for SRSp transmission in order to determine the Rx-Tx time difference. 7. The WTRU may receive information from the gNB indicating a request for an uplink transmission that may overlap with the SRSp transmission (e.g., a fourth one). 8. The WTRU may decide to prioritize SRSp transmissions. 9. WTRU may receive PRS. 10. The WTRU may transmit an SRSp, determine the Rx-Tx time difference, and report the determined Rx-Tx time difference to the LMF (for example, by transmitting information indicating this). 11. Steps 6-10 may be repeated. The WTRU may decide to end the window after the WTRU has received its last PRS opportunity. The WTRU may send a corresponding SRSp and report the Rx-Tx time difference after the end of the window (for example, it may send information indicating this).

[0199] The WTRU may request (e.g., determine, decide) a measurement gap based on the 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 both the serving gNB and the non-serving gNB can 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 can be received from either the serving gNB or the non-serving gNB within the measurement gap.

[0200] Exemplary embodiments are described below. 1. The WTRU may receive information from the LMF indicating the PRS configuration. 2. If the WTRU receives information indicating a PRS priority level from a serving gNB set to a first level (e.g., "High"), steps 3-5 may be performed. If the received (e.g., indicated) priority level is set to a second level (e.g., "Low") which is lower than the first level, steps 6-7 may be performed. 3. The WTRU may receive information indicating the activation command for the prioritized window via MAC-CE or timer for the window. 4. A WTRU may receive a PRS from either a serving or non-serving gNB. 5. The WTRU may receive information via MAC-CE indicating the deactivation of a prioritization window command, or the timer may expire. 6. WTRU may request a measurement gap from gNB via MAC-CE (e.g., send information indicating the request) (provided that pre-configured MGs are available and they meet the quality requirements for PRS (e.g., they are sufficiently good)). 7. If no priority instruction is given by gNB, WTRU may make a request for measurement gaps via either RRC and MAC-CE (e.g., send information indicating the request) (provided that pre-configured MGs are available and they meet the quality requirements for PRS (e.g., they are sufficiently good)).

[0201] In another example, if the priority level of a PRS is at the second level (e.g., "low"), the WTRU may receive (e.g., decide, determine) any channel and signal with a higher priority than the second level associated with the PRS from the serving gNB. For example, the WTRU may receive (e.g., decide to receive) a PDSCH containing a URLLC over the PRS. The WTRU may schedule to receive a PDSCH containing both a URLLC and a PRS in the same OFDM symbol. In such a case, if the priority level of the PDSCH containing a URLLC is higher than the priority level of the PRS, the WTRU may receive (e.g., decide to receive) the PDSCH containing a URLLC, but may not receive the PRS. For example, the WTRU may receive (e.g., decide to receive) (e.g., both) a PRS transmitted from a non-serving gNB and a higher priority channel / signal from the serving gNB (e.g., any of PDCCH, PDSCH, or CSI-RS). In such cases, the WTRU may treat the PRS transmitted from the non-serving gNB as interference and, for example, may perform an interference rejection method to remove the PRS transmitted from the non-serving gNB from the received signal.

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

[0203] Depending on the configuration, the WTRU may receive information indicating either the priority (e.g., level) of a window or the location of PRS symbols. For example, if the WTRU receives information indicating the priority (e.g., level) of a window, the WTRU may associate the priority level with the PRS received within the window. For example, if the priority level of a window is the first level (e.g., "high"), the WTRU may decide to receive PRS (e.g., PRS only) 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) the PRS within the window and process it, or it may not receive (e.g., decide not to receive) any of the other channels and signals and not process them, based on at least one of the following conditions: ● In the event of a collision between a PRS and any other channel or signal with a lower priority level in the same symbol. For example, a WTRU may receive (or decide to receive) any of the other signals and channels in a symbol where a PRS may not be scheduled; ● In the case of any other channel and other signal with a lower priority level that is scheduled within the window for a symbol that cannot be scheduled for PRS. For example, the WTRU may consist of the following slots, PPPPPPBBBBBBBB, where "P" and "B" may represent a PRS symbol and an unscheduled symbol, respectively. For example, a prioritization window may be associated with the slots. If the priority level of the window is at the first level (e.g., "high"), the WTRU may perform a measurement on the PRS and process any other channel and signal with a lower priority level than the first level, whether for the PRS symbol or an unscheduled symbol, in order to process any measurement taken from the PRS during the duration of the window.

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

[0206] In another embodiment, the WTRU may receive muting patterns (e.g., information indicating them) from the network. For example, (for example, the WTRU may assume that the muting pattern can be applied to the PRS if the priority level of the PRS is indicated as a second level (e.g., "low") which is lower than the first level). In such a case, the WTRU may receive (e.g., decide to receive) any of the channels and signals having a higher priority (e.g., the second level) than the PRS in a symbol that the WTRU might expect to receive the PRS.

[0207] 3. Examples of reducing upper-layer latency Examples of latency reduction techniques for higher layers In one embodiment, the WTRU may proactively perform one or more positioning procedures, for example, before receiving a higher layer positioning information request, based on one or more (e.g., configured) conditions and one or more events as described herein.

[0208] For example, in proactive behavior, a WTRU may take action based on one or more (e.g., configured) conditions and one or more events.

[0209] In this case, the positioning information request may relate to either a mobile outgoing location request (MO-LR) or a mobile incoming location request (e.g., either MT-LR or delayed MT-LR). Positioning procedures proactively performed by the WTRU may result in information associated with supporting the positioning method (e.g., WTRU capability, support data) being pre-identified, delivered, or stored so that either the positioning measurement or calculation can be performed with low (e.g., reduced) latency after the positioning information request is received.

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

[0211] The positioning procedures proactively performed by the WTRU may include one or more of the following: - Ability Transfer Procedure: For example, a WTRU may transmit capability information associated with positioning to the network based on the detection of either a trigger condition or an event trigger. A WTRU may transmit capability information (e.g., proactively) as part of an LPP procedure. Capability information transmitted by a WTRU may be stored in either an LMF / AMF in the CN or RAN as context information associated with positioning. For example, capability information transmitted by a WTRU may be associated with either an identifier and a version ID for storage in context information. Stored capability information in the positioning context may be retrieved by the LMF when a positioning information request (e.g., MO-LR, MT-LR) is received. -Support data transfer procedure: For example, in a WTRU-initiated example, the WTRU may proactively send a request for support data (e.g., an information request) to request one or more PRS configurations, for example, when the WTRU is triggered by either a condition or an event trigger. In a network-initiated example, the WTRU may proactively receive information from the network indicating support data (e.g., including PRS configurations), which can be applied by the WTRU to perform measurements on the PRS after receiving a positioning information request (e.g., information indicating it). The support information received by the WTRU may be pre-stored in the WTRU as positioning context information and retrieved, for example, after receiving a positioning information request. -Location request transfer procedure: For example, a WTRU may proactively receive location request messages (e.g., LPP) from the network and, after receiving a positioning information request (e.g., MO-LR, MT-LT), may use the received location request to transmit positioning information (e.g., either measurement data or location information). Location requests received by a WTRU may be stored in the WTRU as positioning context information, for example. - Measurement gap configuration: For example, a WTRU may proactively send requests (e.g., information requests) for one or more measurement gap configurations to the network when triggered conditions are met. In such cases, the WTRU may send requests for measurement gap configurations before receiving a positioning information request from the network. One or more measurement gap configurations received by the WTRU may be stored in the WTRU as positioning context information, for example. - Positioning information report: For example, a WTRU may proactively transmit positioning information, including either a measurement report or location information, when triggered by conditions (e.g., configured) that trigger the WTRU.

[0212] For example, received information indicating one or more positioning configurations (e.g., support data, measurement gap configurations), which may be stored as positioning context information in a WTRU, may be associated with an effectiveness metric. For example, the effectiveness metric may be associated with either a duration and area (e.g., a set of one or more cell IDs) that can be used after the stored positioning information is valid and a positioning information request (e.g., MO-LR, MT-LR) has been received. In such a case, the WTRU may use the context information for positioning if the criteria associated with the effectiveness metric are met (e.g., the context information is within either the effectiveness duration and the effectiveness area). The WTRU may, for example, after detecting the expiration of the effectiveness metric, trigger one or more positioning procedures (e.g., their execution) to update the context information.

[0213] Any of the conditions and event triggers configured in the WTRU to perform any of the positioning procedures (for example, proactively) may include one or more of the following: - Changes in WTRU capabilities associated with positioning ○In the example, WTRU capability information associated with positioning may include either static capability information (e.g., the type of positioning method supported) or dynamic capability information (e.g., the total bandwidth available to perform positioning measurements). In such cases, the WTRU may transmit capability information to the network after detecting a change in either the static or dynamic capability information (e.g., it may be triggered to transmit it). For example, the WTRU may transmit information indicating an update to the dynamic capability information if the bandwidth available to perform positioning measurements meets either an increase or decrease condition, e.g., a threshold (e.g., which may be configured by an LMF). - Timer / Periodic ○For example, a WTRU may execute one or more positioning procedures (e.g., request support data) if a certain duration (e.g., either a minimum duration or a maximum duration) has elapsed since the last identical / correlated positioning procedure could have been executed. In this example, the WTRU may set a timer after sending a first request for support information and send a second request for support information after the timer expires (e.g., the second request for support information may be sent if it is determined that the amount of time corresponding to the timer has elapsed since the first request for support information was sent). The timer duration may be configured by the LMF. In another example, the WTRU may periodically (e.g., repeatedly) execute positioning procedures (e.g., trigger them) based on a configured periodicity (e.g., configured by the LMF). - Changes in RRC state For example, if the WTRU RRC state in either the RAN or CN changes (e.g., a CM connected to CM IDLE and vice versa, or an RRC connected to RRC INACTIVE and vice versa), the WTRU may perform one or more positioning procedures (e.g., be triggered). - Area changes For example, a WTRU may perform positioning procedures when entering, leaving, or remaining in an area defined within the WTRU. For example, a defined area, which is comprised of either an LMF or a gNB, may be represented as a tracking area, for example, in the form of one or more cell IDs. - Detection of new TRP / gNBs For example, 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 TRP / gNBs / satellites / other entities (e.g., high-altitude platform stations) associated with the currently active support information (e.g., PRS configuration), the WTRU may perform (e.g., trigger) a positioning procedure. - Changes in WTRU movement For example, a WTRU may (e.g., proactively) perform a positioning procedure (e.g., be triggered) after detecting that it may have moved a certain distance from its previous position. In another example, a WTRU may (e.g., be triggered) perform a procedure if the speed at which it may be moving satisfies a speed condition (e.g., the speed has either increased or decreased by a threshold (e.g., which may be configured by the LMF)). - Changes in the WTRU wireless environment For example, after detecting an increase or decrease in either multipath or interference, the WTRU may (for example, proactively) perform a positioning procedure if, for example, the increase / decrease meets a condition, for example, if it exceeds a configured threshold (for example, configured by the LMF).

[0214] Example procedure for on-demand PRS initiated by WTRU for MO-LR positioning service For example, a WTRU may send an on-demand PRS request to the network (e.g., either LMF or gNB) based on either the receipt or detection of an MO-LR instruction. For example, an on-demand PRS request message to request either a change or update of the PRS configuration may be sent by the WTRU together with (e.g., together with) an MO-LR location service request by encapsulating it, for example, within the same MO-LR message (e.g., within a NAS PDU). In another example, an on-demand PRS request message may be sent by the WTRU separately from the MO-LR message (e.g., in a separate NAS PDU or a separate LPP message), containing information that allows the MO-LR request message to be referenced, for example (e.g., by including the MO-LR ID in the on-demand PRS message).

[0215] For example, the MO-LR positioning service may comprise either a Location Service (LCS) client or application functionality that can be hosted within the WTRU. The MO-LR positioning service may also 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 transmitted to either the LCS client or application. The information contained within an MO-LR location service request may include (e.g., show) one or more of the following: - An identifier associated with either a service request (e.g., MO-LR service ID) or a service entity (e.g., LCS client ID, application ID, WTRU ID). - Requests regarding WTRU location estimation ○An MO-LR request may or may not include instructions to establish an LPP session with the network if no ongoing (e.g., existing) LPP sessions exist. ○An MO-LR request may include information indicating that a location request is being sent via an LPP session, for example, if there is at least one ongoing (e.g., existing) LPP session, including updates to a previous request for location estimation or a new request for location estimation. - Requests regarding measurements associated with WTRU location estimates. - Positioning QoS information associated with the location estimate (e.g., any of the positioning accuracy, latency, reliability, or integrity properties). - Either the intended destination and routing information (e.g., LMF ID, WTRU ID, Application Function ID, or LCS Client ID) for sending the WTRU location estimate. - Requests for supporting data (e.g., one or more PRS configurations).

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

[0217] The WTRU may receive support information from the LMF (e.g., shown) that includes one or more pre-configured PRS configurations and PRS parameters. In the example, one or more PRS configurations (e.g., parameters) received by the WTRU may be associated with one or more non-on-demand PRS configurations and one or more on-demand PRS configurations. A non-on-demand PRS (e.g., pre-configured) configuration may be used by the WTRU, for example, to perform (e.g., conventional) positioning measurements. An on-demand PRS configuration (e.g., pre-configured) may be associated with a PRS configuration (e.g., parameters such as PRS period or bandwidth) that can be supported (e.g., permitted) by the network 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, if a non-on-demand PRS configuration does not meet the conditions associated with MO-LR. The WTRU may transmit information to the network indicating the determined (e.g., selected) PRS configuration (e.g., parameters), such as the ID of the PRS configuration / parameter in the on-demand PRS request. In another example, the supporting information (e.g., indicating) one or more PRS configurations (e.g., parameters) received by the WTRU may not be associated with any (one or more) non-on-demand PRS configurations or (one or more) on-demand PRS configurations. 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 include information indicating the determined (e.g., selected) PRS configurations (e.g., parameters) in the on-demand PRS request.

[0218] Supporting information received by the WTRU, including (e.g., indicating) PRS configuration (e.g., parameters), may be determined by the LMF based on, for example, interaction involving request / response signaling between the LMF and RAN nodes (e.g., gNB / TRP) via the NRPPa procedure. Supporting information received by the WTRU may include (e.g., indicating) either trigger conditions and validity conditions for determining when to send an on-demand PRS request message and any information that should be included in the on-demand PRS request message. For example, either trigger conditions and validity conditions may indicate one or more conditions that can be monitored (e.g., detected) by the WTRU (e.g., RSRP of the 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 supporting information may also include mapping (e.g., association) relationships / functions for mapping (e.g., associating) one or more PRS configurations or parameters that the WTRU can identify and include in the on-demand PRS request from the detected trigger / validity conditions.

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

[0220] When a message (e.g., an indication) indicating that the WTRU is to perform new measurements using different PRS configurations (e.g., parameters) and / or determine a new positioning estimate of the WTRU is received from either the LCS client and the application, for example, in either a new MO-LR or an update to an existing MO-LR, the WTRU may send an on-demand PRS request to the network. The WTRU may determine a PRS configuration (e.g., parameters) for the new measurements based on additional information (e.g., an increase / decrease in the periodicity of the measurements to be performed, an increase / decrease in the 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 the application may be used as a trigger for either sending an on-demand PRS request to the network or determining an on-demand PRS configuration (e.g., parameters) to indicate (e.g., include) in the on-demand PRS request.

[0221] After receiving from the network either an explicit or implicit indication (e.g., information) indicating whether the sent on-demand PRS request has been satisfied, the WTRU may perform a new set of measurements and either send the measurements to the LMF (for WTRU-assisted positioning) or 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 the application.

[0222] Example of a WTRU Sending an On-Demand PRS Request Outside of an Active LPP Session In one embodiment, the WTRU may send an on-demand PRS request to the network (e.g., either the LMF or the gNB) when it is outside an LPP session and / or when either an active LPP session is not configured and not available. In an example, the WTRU may receive an indication from either, for example, an LCS client or an application, in a MO-LR location service request, to provide either a location estimate or positioning measurements. When 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 use the received PRS configuration (e.g., parameters) to perform measurements on the PRS and may send a location estimate to either an LCS client or an application. For example, the WTRU may perform measurements on the PRS and may determine a location estimate using, for example, a pre-configured PRS configuration (e.g., parameters) that is determined by the WTRU to be valid before performing the measurements. In these examples, positioning measurements may be performed by the WTRU in the following scenarios: - Without the need to establish an LPP session during either the duration of positioning measurements or location determination (e.g., estimation), - Before establishing an LPP session, - Outside an active LPP session.

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

[0224] In the example, a WTRU that can receive information indicating a PRS configuration (e.g., parameters) from posSIB, or that can 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 to 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 MO-LR location service requests: For example, a WTRU may transmit an on-demand PRS if an MO-LR request is received, and / or if the WTRU determines that the available PRS configuration (e.g., parameters) is insufficient / unsuitable to meet the MO-LR positioning QoS criteria (e.g., accuracy, latency). In such cases, the WTRU may transmit an on-demand PRS, for example, before or after performing a measurement using the available PRS configuration (e.g., parameters). ○The WTRU may, for example, send an on-demand PRS to the network along with an MO-LR request message for WTRU-assisted positioning. In the 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., a NAS message), which may include, for example, an instruction indicating support for WTRU-based positioning, or an instruction not to establish an LPP session by supporting WTRU-based positioning. ● Receiving information in posSIB: For example, a WTRU may transmit an on-demand PRS if the posSIB does not include a PRS configuration (e.g., parameters) that would be suitable for the WTRU to perform (e.g., allow) positioning measurements. For example, a WTRU may perform measurements on a non-positioning RS (e.g., any of CSI-RS, SSB, or RRM measurement configurations) that may be in a quasi-collocation (QCL) relationship with a PRS configuration (e.g., parameters) received via posSIB. The WTRU may, for example, send an on-demand PRS request for either updating or changing the PRS configuration (e.g., parameters) if the measurements performed on a non-positioning RS that may be in a QCL relationship do not meet the criteria. For example, a WTRU may receive one or more trigger conditions associated with the PRS configuration (e.g., parameters) received in the posSIB (e.g., the RSRP of a measurement made to the PRS may be below / above the RSRP threshold, the number of variations in a measurement over a period of time may be above / below the threshold, non-line-of-sight (NLOS) detection, the number of detected multipaths may be above / below the threshold) (e.g., information indicating this). In this case, the trigger conditions (e.g., information indicating this) may be received in the posSIB, or the trigger conditions may be pre-configured in the WTRU by the network (e.g., via RRC, LPP). The WTRU may, for example, transmit an on-demand PRS if one or more of the trigger conditions are detected (e.g., met). ● Detection of validity conditions: For example, a WTRU may send an on-demand PRS if a PRS configuration (e.g., parameters) received via posSIB or pre-configured in the WTRU is determined to be invalid with respect to one or more validity conditions (e.g., determined to have failed). Information indicating the validity conditions associated with the PRS configuration (e.g., parameters) (e.g., any of the cell IDs in area validity conditions, duration in time validity conditions) may be received by the WTRU, at least partially, from the network (via posSIB, LPP signaling, or RRC signaling) or from any of the LCS clients, applications, and higher-layer functions.

[0225] If a WTRU does not have at least one existing or active LPP session, it may send an on-demand PRS to the network via one or more of the following network elements: ● To Serving gNB: For example, a WTRU may send an on-demand PRS (e.g., information) to a serving gNB in ​​access layer (AS) layer signaling, indicating that it will update the PRS configuration (e.g., parameters) available in the WTRU, including one of the following: an RRC message, a MAC CE, an on-demand SIB message, and a UCI. The WTRU may also send information to the serving gNB indicating the identifier (e.g., ID) 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 either the AMF or LMF to update (one or more) PRS configurations (e.g., parameters). ● To AMF / LMF: For example, a WTRU may send an on-demand PRS (e.g., information) to either the AMF or LMF without including an LPP session ID indicating, for example, a change in PRS configuration (e.g., parameters) (if the LMF's routing ID is known to the WTRU). In another example, if a WTRU decides (e.g., intends) to establish an LPP session (e.g., based on any of the following: unavailability of an existing (e.g., active) LPP session, triggered by a higher layer location service request, and receipt of an LPP message from the network), the WTRU may send an on-demand PRS (e.g., information) to the AMF / LMF by sending the message with a capability information message (e.g., within an LPP capability offering message) or with a support information request message (e.g., an LPP support data request message) (e.g., piggybacking). In such a case, the WTRU may include in the on-demand PRS any of the flags and indicators (e.g., information) indicating, for example, whether an LPP session should be established. For example, if a WTRU has one or more deactivated (e.g., suspended) LPP sessions, the WTRU may send an on-demand PRS (e.g., information) to the AMF / LMF along with an LPP message (e.g., including the ID of the deactivated (e.g., suspended) LPP session). The WTRU may also include in the on-demand PRS any flags and indicators (e.g., information) indicating whether to reactivate the deactivated (e.g., suspended) LPP session and / or establish a new LPP session.

[0226] If a 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 establish and activate an LPP session (e.g., using either a flag or indicator along with the on-demand PRS (e.g., information)) based on the detection of one or more of the following conditions: ●Types of MO-LR service requests: For example, a WTRU may transmit an on-demand PRS (e.g., information) containing either a flag or an indicator when it receives an MO-LR message containing instructions to establish an LPP session. In another example, a WTRU may include either a flag or an indicator for establishing and activating an LPP session when the positioning QoS information provided with the MO-LR request indicates parameter values. In such a case, the WTRU may include either a flag or an indicator if either the indicated positioning accuracy and latency meets a condition (e.g., above / below an accuracy / latency threshold). ●Types of PRS configurations (e.g., parameters) accessible via posSIB: For example, a WTRU may include either a flag or an indicator along with on-demand PRS (e.g., information) for either establishing and activating an LPP session if it is determined that the PRS configuration (e.g., parameters) available via posSIB for measurement does not meet the criteria (e.g., positioning QoS criteria associated with an MO-LR service request). In such cases, the WTRU may include either a flag or an indicator if the measurement duration for performing the measurement using the PRS configuration (e.g., parameters) available via posSIB does not allow for determining a location estimate.

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

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

[0229] Implicit information may be received in one or more of the following ways: ●posSIB: For example, a 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 the on-demand PRS includes the requested PRS configuration (e.g., parameters), the WTRU may consider the request to be fulfilled (e.g., accepted). For example, receiving an updated posSIB containing the requested (one or more) PRS configuration (e.g., parameters) could be an example of implicit information indicating acceptance of the request. ●PRS measurement: For example, a WTRU may perform a PRS measurement using one or more PRS configurations (e.g., parameters) indicated in the on-demand PRS request message, after a configured duration following the transmission of the on-demand PRS to the network. If the WTRU performs a PRS measurement that is consistent with the requested PRS configurations (e.g., parameters) (e.g., satisfies the associated conditions), the WTRU may consider, for example, that the request is satisfied (e.g., accepted). An example of a condition associated with the requested (one or more) PRS configurations (e.g., parameters) might be that the RSRP of the PRS measurement is above or below the RSRP threshold. For example, performing a PRS measurement that is consistent with the requested (one or more) PRS configurations (e.g., parameters) (e.g., satisfies the associated conditions) might be an example of implicit information indicating acceptance of the request.

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

[0231] Example of a WTRU that performs PRS parameter / configuration grouping for sending on-demand PRS. In one example, the WTRU may either select and perform grouping of one or more PRS parameters when it is determined that PRS parameters should be updated (e.g., changed), and when an on-demand PRS request message is sent, for example. For example, an on-demand PRS request message may contain information indicating to the network (e.g., either LMF or gNB) a selected (e.g., determined) group (e.g., set) of PRS parameters. In another example, the PRS parameters (e.g., that may be grouped) may be pre-configured in the WTRU separately from any PRS configurations that may be configured in the WTRU, for example. In yet another example, the PRS parameters (that may be grouped) may be part of or a subset of one or more PRS configurations (e.g., within one or more PRS configurations) that are pre-configured in the WTRU, which may be made possible to group them differently from the PRS configurations.

[0232] In an example, the PRS parameters that can be either selected or grouped by the WTRU to send an on-demand PRS request message can be parameters that can be supported or permitted by the network for the WTRU to group (e.g., flexibly). In such a case, the WTRU can receive information indicating one or more PRS parameters from the network (e.g., either the LMF or the gNB), along with, for example, either the properties and types of parameters that are permitted to be grouped. The information can be included, for example, in the on-demand PRS. The WTRU can also receive information indicating rules (e.g., restrictions) on how the PRS parameters can be grouped by the WTRU. For example, the WTRU can receive information indicating conditions (e.g., criteria) that can be monitored by the WTRU to determine which of the parameters and rules (e.g., restrictions) should be applied to group the parameters. For example, the WTRU can receive information for grouping that includes, for example, either the PRS parameters, the conditions for triggering the grouping, and the rules for the grouping from the network, for example, in an LPP message (e.g., LPP assistance information). 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 may be received from the gNB (e.g., in any of RRC, MAC CE, DCI).

[0233] The information indicating the PRS parameters that can be received by the WTRU for grouping in on-demand PRS can include one or more of the following (e.g., indications): ● Any of the following: PRS periodicity, PRS resource bandwidth, PRS resource density, start time, stop time, time offset, repetition, muting bandwidth, comb pattern, or number of symbols per PRS resource. For example, a request from a WTRU for a specific value among PRS periodicity, PRS resource bandwidth, PRS resource density, start time, stop time, time offset, repetition, muting bandwidth, comb pattern, or number of symbols per PRS resource may be applicable to a specific (e.g., some of) PRS resource, resource set, TRP resource, resource set, TRP, or frequency layer. For example, if a WTRU requests any specific start and stop times for a PRS, the request may be applicable to PRS transmitted from a configured TRP. In another example, if a WTRU requests a specific number of PRS symbols, the request may be applicable to (e.g., all) PRS transmitted from a TRP that the WTRU may indicate in the request. ● For example, either the TX power indication and frequency of the PRS for measuring low RSRP on the PRS. ●PRS QCL information, e.g., other RS ​​or Channels that may have a QCL relationship with DL PRS. ● Change the number of beams, turn beams on / off, or change the beams transmitted from the TRP / cell. ● The number of TRP / gNBs that send PRS, or the IDs of TRP / gNBs. ●For example, to measure high interference, turn the PRS on / off or mute it from the TRP / cell. ●For example, measurement gap configuration parameters associated with the updated PRS configuration.

[0234] The conditions that can be configured and monitored (e.g., 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 measured RSRP of a PRS or non-positioning RS / channel (e.g., CSI-RS, SSB, or any other channel) is below / above the (e.g., configured) RSRP threshold, and / or if the RSRP remains above / below the RSRP threshold over (e.g., the configured) duration. ●WTRU's wireless environment: ○For example, the condition may be met if the number of detected paths exceeds the number of multipaths. ○For example, the condition may be met if the NLOS condition is detected. ●WTRU's mobility: ○For example, the condition may be met when WTRU mobility / movement increases / decreases by a mobility threshold.

[0235] The following is an example set of properties, rules, and conditions that may be associated with grouping PRS parameters, which may illustrate how grouping can be performed by WTRU: ● A set of PRS parameters (for example, those allowed to be grouped) 1 ○{Parameter 1_1, Parameter 2_1, Parameter 3_1, ..., Parameter N_1} ● A set of K PRS parameters (for example, allowed to be grouped together) ○{Parameter 1_K, Parameter 2_K, Parameter 3_K, ..., Parameter N_K} ● Properties of Set 1, Set 2, ... Set K: ○Property 1: Set 1, Set 2...Set K may contain PRS parameters that are common to multiple sets (for example, one or more parameters in Set 1 may be the same as parameters in Set 2). ○Property 2: Sets 1, 2, ..., K may contain PRS parameters that are mutually exclusive (for example, all parameters in Set 1 may differ from their corresponding parameters in Set 2). ○Property 3: Set 1, Set 2, ..., Set K (for example, each) can be associated with different PRS configurations (for example, 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 parameters from set 1 (e.g., all or a subset of set 1) can be grouped with one or more parameters from set 2 (e.g., all or a subset of set 2) when a new set (e.g., set {1+2}) is realized (e.g., determined). Rule 2: One or more parameters in set 1 do not need to be grouped with parameters in set 2 when a new set (e.g., set {2-1}) is realized (e.g., determined). ●Conditions associated with either properties or rules: Property 1 and Rule 1 may be applied when a condition from Condition Set 1 is detected (e.g., met). ○Property 1 and Rule 2 may be applied when a condition from Condition Set 2 is detected (e.g., met). ○Property 2 and Rule 1 may be applied when a condition from Condition Set 3 is detected (e.g., met). ○Property 2 and Rule 2 may be applied when a condition from Condition Set 4 is detected (e.g., met).

[0236] For example, after performing PRS parameter grouping, the WTRU may send an on-demand PRS request message to the network containing information indicating the determined group. The determined grouping of PRS parameters may, for example, be grouped into a new PRS configuration with a new ID. The information related to the PRS parameter grouping included in the on-demand PRS request message may include (for example, indicate): ●IDs of the individual grouped parameters, ●ID of the parameter set used for grouping, ●ID of the condition detected for grouping, ● The ID of the rule applied for grouping.

[0237] A WTRU may, for example, transmit an on-demand PRS to the network in an LPP message (e.g., any of LPP request support data, LPP provision capability information, or LPP provision location information) or an AS layer message (e.g., any of RRC signaling, MAC CE, or UCI), which may include information related to PRS parameter grouping.

[0238] If a WTRU is not pre-configured with one or more PRS parameters and / or does not have information about valid PRS parameters that may be allowed to be selected for display in on-demand PRS, the WTRU may perform one or more of the following: ● Send a message to the network indicating a request for support data messages. For example, a WTRU may send either an LPP message (e.g., LPP request support data) or an AS layer message (e.g., any of RRC, MAC CE, on-demand SIB, or UCI) to request support data. In such cases, the WTRU may request PRS parameters by including, for example, an indication (e.g., a flag) that a valid PRS parameter for selection is unavailable. ● Determine from available (e.g., existing) PRS configurations. For example, a WTRU may select (e.g., determine) PRS parameters to indicate that will be updated / modified in an on-demand PRS from one or more valid PRS configurations pre-configured in the WTRU (e.g., via LPP-assisted data) and / or accessible via posSIB. A WTRU may identify PRS configurations that may be marked (e.g., indicated) by the network, and from those PRS configurations, it may select (e.g., determine) PRS parameters that will be updated and indicated in an on-demand PRS.

[0239] Example of a WTRU using validity conditions to determine PRS / SRSp configuration (e.g., parameters). In an example, a WTRU may use validity conditions associated with one or more pre-configured PRS configurations (e.g., parameters) to determine which configurations (e.g., parameters) to select and / or use to perform a DL PRS measurement. For example, in the case of a UL SRSp transmission, a WTRU may use validity conditions associated with one or more pre-configured SRSp configurations (e.g., parameters) to determine which configurations (e.g., parameters) to select and / or use. Information indicating validity conditions may be received by the WTRU from the network (e.g., either LMF or gNB) in any of the following: LPP messages (e.g., either LPP provision support data or LPP request location information), positioning service request messages (e.g., any of MT-LR, delayed MT-LR, or MO-LR), and AS layer messages (e.g., via RRC signaling, MAC CE, or DCI). Validity conditions received by the WTRU (e.g., indicated to the WTRU) may be associated with the type of event (e.g., area, periodic location) configured when the WTRU supports delayed MT-LR services (e.g., procedures). Information indicating the validity conditions associated with (one or more) PRS / SRSp configurations (e.g., parameters) may include one or more combinations of the following: ● Area effectiveness: ○For example, any of the following, which may be available for use: a pre-configured PRS / SRSp configuration and / or parameters: cell ID, RAN notification area (RNA), and CN area. ●Time effectiveness: ○For example, the duration for which a PRS / SRSp configuration may be valid for use (e.g., from the start time to the expiration time). The WTRU may start the timer upon receiving a PRS / SRSp configuration (e.g., in the supporting data), and may use the configuration for PRS measurement or SRSp transmission, for example, as long as the timer is valid within the configured duration (e.g., if the amount of time corresponding to the timer has not elapsed). ●WTRU mobility requirements: For example, a WTRU may use a pre-configured PRS / SRSp configuration (e.g., parameters) when the WTRU speed falls below / exceeds a configured speed threshold. For example, a WTRU may use a pre-configured PRS / SRSp configuration when the amount and / or rate of the WTRU's movement / direction increases / decreases by a threshold. ●WTRU's wireless environment: For example, the WTRU may change from a first set to a second set, which includes one or more pre-configured PRS / SRSp configurations, if either the RSRP of the measurements performed on the PRS and non-positioning RS / channel (e.g., CSI-RS, SSB) associated with the first set meets a criterion (e.g., is above / below the RSRP threshold). ○WTRU may change from a first set to a second set, which includes one or more pre-configured PRS / SRSp configurations, if, for example, the number of multipaths meets a criterion (e.g., above / below a threshold) and / or if an NLOS condition is detected. ●WTRU RRC status (e.g., CONNECTED, INACTIVE, IDLE): For example, a WTRU may change from using a first set of PRS / SRSp configurations, which may include one or more PRS / SRSp configurations, to a second set, depending on the RRC state the WTRU is operating in. For example, a WTRU may use a first set of PRS / SRSp configurations when the WTRU is operating in the RRC_CONNECTED state, a second set of PRS / SRSp configurations when the WTRU is operating in the RRC_INACTIVE state, and a third set of PRS / SRSp configurations when the WTRU is operating in the RRC_Idle state. In such cases, the first, second, and third sets associated with different RRC states may include, for example, subsets of PRS configurations that may be common across the sets. In another example, PRS / SRSp configurations may be mutually exclusive across different sets associated with different RRC states.

[0240] One or more validity conditions received by a WTRU (e.g., indicated in the WTRU) may apply to all or a subset of the PRS / SRSp configurations (e.g., parameters) pre-configured in the WTRU. For example, in one example, the first validity condition may apply to the first PRS / SRSp configuration, and the second validity condition may apply to the 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 a subset (e.g., only a subset) of the PRS / SRSp configurations received by the WTRU (e.g., indicated in the WTRU). In such cases, 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 the second validity condition applies (e.g., if it applies). For example, if time-based validity conditions are used, the WTRU may provide different PRS / SRSp configurations (e.g., information indicating them) along with different validity condition parameters associated with each PRS / SRSp configuration (e.g., start time, validity duration, or expiration time). For example, the WTRU may select a PRS / SRSp configuration based on the parameters of the time-based validity condition. Information indicating the mapping (e.g., association) between validity conditions and applicable PRS / SRSp configurations (e.g., parameters) may be received by the WTRU in the support data, for example, along with information indicating either the validity condition or the PRS / SRSp configuration (e.g., via LPP messages, RRC signaling, or posSIB).

[0241] In the example, a WTRU may use validity conditions, along with, for example, priority values ​​associated with PRS / SRSp configurations pre-configured in the WTRU. For example, if there are multiple PRS / SRSp configurations that satisfy the validity conditions, the WTRU may use a PRS / SRSp configuration that is assigned (e.g., associated with) a high (e.g., best) priority value, followed by a PRS / SRSp configuration with the next highest (e.g., best) priority value, if, for example, the validity conditions associated with a previous PRS / SRSp configuration have expired or are determined to no longer be valid. Selecting a PRS / SRSp configuration based on either assigned priority or validity conditions may, for example, reduce the number of times a PRS / SRSp configuration needs to be changed (e.g., updated) during use.

[0242] If the WTRU determines that one or more of the PRS / SRSp configurations are no longer valid (for example, the validity condition indicates the expiration of the PRS / SRSp configuration) or are not met, the WTRU may do one or more of the following: ● Send information (e.g., instructions) to the network: For example, a WTRU may transmit information to the network indicating either a PRS / SRSp configuration identifier (e.g., ID) or the configuration's expiration status. The information may indicate, for example, that the PRS / SRSp configuration and any of the (one or more) validity conditions associated with the indicated PRS / SRSp configuration are being updated. The information may be transmitted to the network as, for example, an LPP message, an on-demand PRS message (e.g., to either LMF or gNB), or an AS layer message (via either RRC, MAC CE, or UCI). ● Change to a valid PRS / SRSp configuration (for example, an alternative): For example, if the WTRU determines that the first PRS / SRSp configuration is no longer valid, it may use a second PRS / SRSp configuration that may be determined to satisfy its validity conditions. If there are multiple PRS / SRSp configurations (which may be determined to be valid), the WTRU may select, for example, the configuration that has been assigned a high (e.g., best) priority (e.g., associated) as the second PRS / SRSp configuration. ● PRS / SRSp configuration update (e.g., forwarding) validity conditions: For example, if the WTRU determines that a PRS / SRSp configuration is no longer valid based on its validity conditions, the WTRU may update (e.g., forward) its validity conditions based on the validity conditions of another PRS / SRSp configuration that has been determined to be valid. In such a case, the WTRU may change the first validity condition (e.g., associated with the first PRS / SRSp configuration) to be the same as that of the second validity condition (e.g., associated with the second PRS / SRSp configuration) if the first validity condition has expired and the second validity condition is active (e.g., determined to be active) during the expiration of the first validity condition (e.g., at or after expiration). The WTRU may transmit information to the network indicating the status of the validity condition update (e.g., forwarding) from one PRS / SRSp configuration to another.

[0243] After receiving information indicating a pre-configured PRS / SRSp configuration and associated validity conditions, the WTRU may, based on the receipt of a trigger instruction, perform a PRS measurement or SRSp transmission using the configuration determined to be valid. In such cases, the trigger instruction may be received in, for example, an LPP message (e.g., an LPP request for location information), a positioning service request (e.g., MO-LR, MT-LR, delayed MT-LT), or an AS layer message (e.g., RRC signaling, MAC CE, or 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 of (e.g., multiple) PRS parameters. When used in relation to 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 the following: (1) start and end times for DL ​​PRS transmission, (2) DL PRS resource bandwidth, (3) DL PRS resource set ID, (4) DL PRS resource ID, (5) DL PRS transmission period and offset, (6) DL PRS resource repetition coefficient, (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, start PRB, point A, and (15) DL PRS on / off indicator.

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

[0246] For example, a WTRU may receive configuration information from the network that indicates one or more PRS configurations and parameters associated with the PRS configuration (e.g., PRS bandwidth, PRS periodicity, TRP associated with the PRS (e.g., gNB)). A WTRU may receive configuration information indicating a PRS configuration (e.g., PRS configuration ID, parameters, or parameter ID) via, for example, a System Information Block (SIB) such as a posSIB, support data (e.g., LPP support data), or pre-configured information in the WTRU (e.g., pre-configured PRS configurations (e.g., parameters) that may have been received either within or outside a previous LPP session). For example, a WTRU may receive information indicating validity conditions (e.g., parameters) associated with the PRS. For example, validity conditions may be received implicitly (e.g., via an SIB indicating either the time and area (e.g., cell ID) in which the PRS configuration (e.g., parameters) may be considered valid). In another example, information indicating validity conditions may be received explicitly (e.g., via LPP support data). The WTRU may determine that any of the PRS configurations and PRS parameters accessible by the WTRU (e.g., via one of the SIBs), and any of the pre-configured PRS configurations (e.g., parameters), may be invalid with respect to validity conditions, for example. In such cases, the WTRU may send request information indicating either an on-demand request or a request for support data. For example, the request information may include a reference to one or more PRS configurations and parameters that may be determined to be invalid. In another example, the request information may include a reference to 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 be pre-configured in the WTRU (e.g., either in a previous LPP session or outside of an LPP session).

[0247] For example, the PRS configuration (e.g., parameters) received by the WTRU may be determined to be invalid, unavailable, or 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) ●For example, a change in area (e.g., cell ID) due to either WTRU mobility or cell (re)selection, where either an accessible or pre-configured PRS configuration (e.g., parameters) may be determined to be either available or unavailable for use. ● Changes in WTRU mobility attributes (e.g., WTRU may use different mobility routes (e.g., trajectories)), where pre-configured PRS configurations (e.g., parameters) may be determined to be either enabled or disabled.

[0248] For example, PRS configurations (e.g., parameters) accessible by a WTRU (e.g., via SIB, support data, and pre-configuration) may correspond to a subset (e.g., only) of PRS configurations (e.g., parameters) that are supported and available for use in the network. In another example, further PRS configurations (e.g., parameters) may be available in the network and supported by the network, but not necessarily accessible by the WTRU or available in the WTRU.

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

[0250] In the example, the WTRU may have access to one or more sets of PRS configurations (e.g., parameters), 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 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: ● Inaccessible via WTRU through SIB (e.g., posSIB). ● In the WTRU, one or more of the pre-configured PRS configurations (e.g., parameters) may be determined to be insufficient to meet the validity criteria (e.g., the time-validation event has expired, the WTRU is located outside the validity area or outside the valid cell ID, the RSRP of the PRS measurement is above / below the RSRP threshold, or the number of multipaths is below / above the multipath threshold). ●Received by a WTRU outside of an ongoing LPP session (for example, via LPP support data), it may be determined to be active, and received by a WTRU in a previous LPP session, it may be determined to be inactive, released, or expired. ● The WTRU receives either implicit or explicit instructions from the network indicating that one or more PRS configurations (e.g., one or more parameters) may not be valid, available, or supported.

[0251] For example, a WTRU may select a PRS configuration (e.g., parameters) as indicated in an on-demand PRS request by first identifying (determining) a suitable (e.g., candidate) PRS configuration (e.g., parameters) from a set determined to be valid (e.g., having a higher priority), such as a set of positioning QoS parameters (e.g., requirements, objectives), based on mapping relationships, for example. If a WTRU cannot determine a suitable (e.g., candidate) PRS configuration (e.g., parameters) from a set determined to be valid, the WTRU may select a suitable (e.g., candidate) PRS configuration (e.g., parameters) from a set determined to be either invalid or unavailable. To assist the WTRU in determining a PRS configuration (e.g., parameters), the WTRU may receive information from the network (e.g., in supporting data) indicating one of the following: ● Validity status indicating that any of the PRS configurations and parameters may be enabled or disabled. ● Priority information associated with either the priority of (one or more) PRS configurations (e.g., (one or more) parameters) or the priority of the effectiveness status may be associated with different effectiveness conditions. For example, a PRS configuration (e.g., a parameter) that can satisfy an area effectiveness condition may be assigned (e.g., associated with) a priority value of p1, a PRS configuration (e.g., a parameter) that can satisfy a time effectiveness condition may be assigned (e.g., associated with) a priority value of p2, and a PRS configuration (e.g., a parameter) that may not satisfy an area effectiveness condition may be assigned (e.g., associated with) a priority value of p3. For example, a WTRU may determine which PRS configurations (e.g., parameters) to indicate in an on-demand request based on priority order, where, for example, a first priority p1 may have a higher priority than a second priority p2, and a second priority p2 may have a higher priority than a third priority p3 (e.g., p1 > p2 > p3). Other methods of mapping priorities to effectiveness conditions may be applicable to the embodiments described herein.

[0252] In another example, a WTRU may select (e.g., determine) a PRS configuration (e.g., parameters) to indicate an on-demand PRS request, which may be suitable for and / or satisfy a positioning QoS objective, regardless of whether the PRS configuration (e.g., parameters) can be determined to be valid or invalid. In yet another example, a WTRU may determine a PRS configuration (e.g., parameters) 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 or invalid. For example, a WTRU may determine one or more PRS configurations or groups of PRS parameters to indicate in an on-demand PRS request, where a first PRS configuration (e.g., parameters) may be determined from a valid set, and a second PRS configuration (e.g., parameters) may be determined from an invalid set.

[0253] For example, after selecting an appropriate PRS configuration (e.g., parameters), the WTRU may send either an on-demand PRS request and a request for supporting data containing information that may indicate any of the following: ● For example, an identifier (e.g., ID) associated with either (one or more) selected PRS configurations and selected PRS parameters, along with the status of selection. PRS configurations (e.g., parameters) may be selected by the WTRU from a set of PRS configurations (e.g., parameters) that may be determined to be, for example, i) valid (e.g., accessible via SIB or pre-configured in the WTRU), ii) invalid (e.g., inaccessible from the SIB or a pre-configured configuration whose validity has expired), and iii) a combination of valid and invalid. ● Identifiers and flags that indicate the validity status of the selection, for example, whether the selected PRS configuration (e.g., parameters) can be selected from a set that has been determined to be valid or invalid (e.g., unavailable). For example, WTRU may indicate an ID (e.g., a flag) associated with an invalid set if any of the selected, determined, and indicated PRS configurations (e.g., parameters) are from outside either the posSIB or LPP session. ● Events (e.g., conditions) associated with validity conditions that can be determined to be either valid or invalid, associated with either the indicated selected PRS configuration (e.g., parameters) and the indicated status of the selection. For example, a WTRU may include information in the on-demand request indicating which of the validity conditions (e.g., time validity, area validity) are determined to be met and / or not met. ● Timing information (e.g., timestamp) indicating the time associated with the on-demand request. For example, the time may indicate when the specified PRS configuration (e.g., parameters) within the one-demand request may be requested by the WTRU. ● Information indicating whether the indicated PRS configuration (e.g., parameters) (enabled / disabled) can be used by the WTRU on a best-effort basis or on a required (e.g., guaranteed) basis. For example, the WTRU may indicate a disabled PRS configuration 1, the first PRS configuration which can be determined from the disabled set and can be used by the WTRU on a best-effort basis. For example, the WTRU may indicate a second PRS configuration which can be determined from the enabled set and can be requested by the WTRU. For example, the information may indicate that both the first and second PRS configurations can be used to satisfy positioning QoS parameters (e.g., requirements, objectives). For example, instructions transmitted 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, if there may be no ongoing LPP sessions 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 base station) along with (e.g., included within) the MO-LR location service request message. In such a case, the information indicating 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, an on-demand PRS request sent by the WTRU along with (e.g., included within) 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., along with the MO-LR service request) that includes 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 support 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 PRS configurations (e.g., parameters) that may be selected (e.g., determined) from a valid set.

[0255] Example of a WTRU performing UL SRSp transmission in an inactive state to support delayed MT-LR In embodiments, a WTRU that 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 MT-LR or delayed MT-LR positioning services. A delayed MT-LR positioning service may be referred to herein as a procedure that can cause (e.g., transmit) one or more instructions to either establish and configure a location service session (e.g., an LPP session) between, for example, an LCS client located in the network, and a WTRU, etc. In such a case, for example, after receiving a delayed MT-LR service request from the network (e.g., either the LMF or a base station), the WTRU may receive information from the network indicating one or more SRSp configurations (e.g., periodic, semi-persistent, and aperiodic) for performing a UL SRSp transmission for UL-based positioning. For example, the WTRU may also receive one or more trigger events (e.g., information indicating it) that may be associated with the delayed MT-LR, for example, if at least one of the configured trigger events is detected, the WTRU may either monitor and perform a UL-SRSp transmission. The triggers described herein may include one or more of the following: ●Time event: A periodic time event in which a WTRU may periodically transmit SRSp based on the periodicity which can be configured by receiving configuration information indicating the configuration of a time event (e.g., a trigger event). ● Area Events: For example, an area event may be associated with one or more cells (e.g., cell IDs) to which the WTRU can send an SRSp when a cell (e.g., cell ID) associated with the configured area event is detected. ● Mobility Events: For example, mobility events may be related to the mobility attributes of a WTRU (e.g., WTRU velocity, direction of movement, and trajectory (e.g., route)), and a WTRU may send an SRSp when it detects a change in one or more mobility attributes (e.g., WTRU velocity exceeds / falls below a threshold, WTRU trajectory changes by a threshold, ...).

[0256] For example, a WTRU may continue transmitting SRSp until a stop event (e.g., a condition) associated with stopping SRSp transmission (e.g., interruption) can be detected by the WTRU. SRSp transmitted by the WTRU can be measured by a base station, and the measurement can be reported to the LMF, which can then determine (e.g., estimate) the location of the WTRU based on the measurement. 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, a delayed MT-LR procedure (e.g., a method) may be performed by a WTRU operating in one of the RRC_CONNECTED, RRC_INACTIVE, or RRC_IDLE states. For example, 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 is operating in one of the (e.g., RRC) states. For example, both a trigger event to start SRSp transmission and a stop event to stop transmission (e.g., pause, terminate) may also be used by the WTRU regardless of the (e.g., RRC) state. In another example, a delayed MT-LR procedure (e.g., a method) may be performed knowing which (e.g., RRC) state the WTRU is operating in. In such a case, the WTRU may receive information indicating different SRSp configurations depending on the WTRU's (e.g., RRC) state. For example, a WTRU may use different SRSp configurations depending on its (e.g., RRC) state (e.g., different SRSp configurations may be used for different (e.g., RRC) states). For example, both the trigger event for starting SRSp transmission and the stop event for stopping SRSp transmission (e.g., pausing, terminating) may depend on (e.g., be associated with) the (e.g., RRC) state in which the WTRU can operate.

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

[0259] If a WTRU detects one or more trigger events, and for example the WTRU may be operating in an INACTIVE state, the WTRU may send instructions (e.g., either an LMF or a gNB) to the network to indicate either an event instruction or an event report regarding the detection of the trigger events. For example, information may be sent to the network by the WTRU, indicating that a trigger event may have been detected. For example, a WTRU may transmit information (e.g., indications) in a Small Data Transmission (SDT) using resources associated with the SDT (e.g., either a random access SDT or a configured grant SDT).

[0260] For example, a WTRU may request an SRSp configuration. If a WTRU determines that a pre-configured SRSp configuration is ineffective (for example, with respect to one or more validity conditions described herein) and / or requests an update to the validity conditions (for example, by sending information indicating the request), the WTRU may send an instruction (for example, information indicating the request) requesting the activation of the pre-configured SRSp configuration (for example, periodic, semi-permanent, or aperiodic). The WTRU may send one instruction (for example, an information fragment) or two instructions (for example, multiple information fragments) containing either first information indicating an event instruction and / or event report, and second information indicating a request for an SRSp configuration (for example, activation of the SRSp configuration). If the WTRU is operating in an INACTIVE state, for example, it may send one or more instructions (for example, information fragments) with the SDT (for example, included in the SDT) (for example, using an SDT resource).

[0261] In one example, the first instruction that may be sent by the WTRU may include information indicating either an event instruction, an event report, or a request for SRSp configuration, and the second instruction that may be sent by the WTRU may include information indicating either a request for SRSp configuration or activation of SRSp configuration. In another example, the WTRU may send the first instruction indicating either an event instruction or a request for SRSp configuration, and the WTRU may send the second instruction indicating an event report, for example, the second instruction may be sent after performing a UL SRSp transmission using the received SRSp configuration.

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

[0263] For example, after transmitting either an event instruction or an event report instruction (e.g., information indicating such an instruction), the WTRU may receive information from the network indicating an SRSp configuration. For example, after transmitting an instruction to the network, the WTRU may receive activation instructions (e.g., information indicating activation) to activate one or more pre-configured SRSp configurations, for example, in either MAC CE or DCI (for example, further). For example, the WTRU may receive activation instructions (e.g., information indicating activation of the transmission) to activate a semi-persistent SRSp transmission. For example, the configuration for a semi-persistent SRSp may be pre-configured in the WTRU. For example, the configuration for a semi-persistent SRSp may be received by the WTRU from the network in an activation instruction. For example, the WTRU may receive similar activation instructions (e.g., in DCI) to activate a non-periodic SRSp transmission (for example, similarly).

[0264] For example, a WTRU may stop (e.g., pause) SRSp transmission in the INACTIVE state based on one or more of the following stop events (e.g., conditions): ● Receiving instructions (e.g., information) from the network: For example, a WTRU may stop (e.g., pause) SRSp transmission if it receives one or more instructions (e.g., information fragments) indicating any of the following: deactivation, suspension, termination, and release of an SRSp configuration available to the WTRU. For example, a WTRU performing periodic SRSp transmission (using an SRSp configuration for periodic SRSp) may stop (e.g., interrupt) SRSp transmission if it receives information from the network indicating a stop (e.g., interruption). For example, a WTRU may receive information about an INACTIVE state via either an LPP message or an Access Layer (AS) layer message (e.g., RRC message, MAC CE, and DCI). ● Expiration of validity conditions: For example, a WTRU may stop (e.g., suspend) SRSp transmission if it is determined that an SRSp configuration used for SRSp transmission is invalid with respect to one or more associated validity conditions. In the example, an SRSp configuration may be associated with a timing advance (TA) timer as a validity condition (as described herein) for performing 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., suspend) SRSp transmission and release the SRSp configuration. ● Per parameter of the SRSp configuration: For example, a WTRU may stop (e.g., pause) SRSp transmissions based on the parameters of the SRSp configuration. For example, parameters may include SRSp duration, periodicity, resource set, frequency layer, etc. In such cases, a WTRU may stop transmitting a semi-persistent SRSp, for example, at the end of the duration associated with the semi-persistent SRSp.

[0265] Examples of validity conditions for using SRSp configuration during inactive operation The WTRU may receive from the network (e.g., either LMF or gNB) one or more validity conditions (e.g., criteria) (e.g., information indicating them) associated with the SRSp configuration, for example, for use in an 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 pre-configured SRSp configurations and parameters that may be valid for use include the cell ID, RAN notification area (RNA), and CN area. ●Time validity: For example, the duration for which an SRSp configuration may be valid for use (e.g., from the first (e.g., start) time instance to the second (e.g., expiration) time instance). A 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, a WTRU may use an SRSp configuration for SRSp transmission for the duration following the receipt of the SRSp configuration information. ●WTRU mobility conditions: For example, a WTRU may use a pre-configured SRSp configuration when the WTRU speed is below / above a configured speed threshold. Similarly, a WTRU may use a pre-configured SRSp configuration when either the amount of motion or the speed (e.g., direction) of the WTRU increases / decreases by a threshold. ● Timing Advance (TA) Validity: For example, TA validity for using an SRSp configuration may be associated with a Timing Advance (TA) configured in the WTRU (for example, TA configuration information may be received by the WTRU from the network). For example, TA validity for using 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 where the WTRU may be mobile, and the validity of the TA may be determined based on, for example, a TA timer. For example, a 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 Wireless Environment For example, a WTRU that may be pre-configured with one or more SRSp configurations may switch from using the first SRSp configuration to the second SRSp configuration if the RSRP of a measurement made on either the PRS or a non-positioning RS / channel (e.g., either CSI-RS or SSB) is above or below the RSRP threshold. For example, WTRU may change from the first SRSp configuration to the second SRSp configuration if the number of multipaths exceeds / falls above / below a threshold (e.g., is detected) and / or if an NLOS condition is detected. ●Instructions from the network: For example, a WTRU may determine that an SRSp configuration is valid if it receives instructions (e.g., information) from the network (e.g., either LMF or gNB) indicating that the SRSp configuration (e.g., the ID of the SRSP configuration) can be used for SRSp transmission. For example, instructions (e.g., information) may be received by the WTRU in an LPP message, an RRC message, a MAC CE, or a DCI. ● WTRU RRC states (e.g., CONNECTED, INACTIVE, IDLE): For example, a 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., pause, 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) can be enabled or disabled for use, for example, to initiate SRSp transmission when one or more trigger events (e.g., associated with delayed MT-LR) are detected. Different types of SRSp configurations (e.g., periodic, semi-permanent, 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-permanent SRSp transmission may be associated with a second set of one or more validity conditions (e.g., time validity). For example, the validity conditions may be associated with one or more SRSp configurations and any other UL configurations (e.g., CG, RACH, SDT configurations). For example, the WTRU may receive a common set (e.g., information indicating it) of one or more validity conditions that may apply to a first SRSp / UL configuration and a second SRSp / UL configuration.

[0267] In one example, information indicating the validity conditions may be explicitly received by the WTRU in one or more instructions (e.g., messages) (e.g., via LPP messages, SIBs, RRC messages, MAC CEs, and DCIs) if information indicating either an SRSp configuration or a trigger event is received. In another example, information indicating the validity conditions may be received implicitly, and this implicit reception may indicate that the SRSp configuration may be valid for use (e.g., only in that case) if the WTRU remains in any of the cells and coverage areas of the gNB where information indicating the SRSp configuration can be received. In yet another example, the implicit validity condition indication may be based on associations between different SRSp / UL configurations. In such a case, if the WTRU receives a first SRSp / UL configuration and 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 if it is determined that the first SRSp / UL configuration is associated with the second SRSp / UL configuration.

[0268] In the example, the validity conditions (e.g., for determining whether an available (e.g., stored) SRSp configuration in the WTRU is valid or invalid for use) may be associated with either a delayed MT-LR positioning service (e.g., a procedure) or a trigger event used to initiate an SRSp transmission. For example, a WTRU may initiate (e.g., execute) an SRSp transmission using a pre-configured SRSp configuration if one or more trigger events (e.g., either a time event or an area event) are detected. For example, a WTRU may initiate (e.g., execute) an SRSp transmission using a pre-configured SRSp configuration if it is determined that a pre-configured SRSp configuration is valid (e.g., one of the TA timers is valid and it is possible that no TA timer has expired).

[0269] For example, information indicating one or more validity conditions may be received by the WTRU in any of the following examples: ●When a trigger event (for example, information indicating it) is received: For example, if the WTRU receives information indicating either a delayed MT-LR service request or a trigger event, it may receive information indicating validity conditions from the LMF. For example, information indicating validity conditions may be included in the information indicating either a delayed MT-LR service request or a trigger event. ●If information indicating SRSp settings is received: For example, if information indicating an SRSp configuration is received, the WTRU may receive information indicating one or more validity conditions from a network in the RRC_CONNECTED state (e.g., either a gNB or an LMF). For example, information indicating validity conditions may be included in the information indicating the SRSp configuration. For example, the WTRU may store validity conditions along with the SRSp configuration, and if a trigger event is detected, the WTRU may determine whether the stored configured SRSp is valid for use based on whether the associated validity conditions are met. ○In another example, if information indicating an SRSp configuration is received, the WTRU may receive information indicating one or more validity conditions (e.g., TA timers) from a network in an RRC inactive state (e.g., either a gNB or an LMF). For example, the information indicating 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 it is determined that the SRSp configuration is valid (e.g., the TA timer may be valid or not expired). The WTRU may suspend (e.g., release) the SRSp configuration if the validity conditions are not met (e.g., if it is determined that the TA time associated with the TA timer has elapsed). ○In another example, a WTRU may receive information indicating validity conditions separately from receiving information indicating the SRSp configuration. For example, a WTRU may receive information indicating validity conditions before or after receiving information indicating the SRSp configuration. For example, a WTRU may receive first information indicating validity conditions and second information indicating the SRSp configuration in separate (e.g., different) messages (e.g., signaling) from the network. For example, validity conditions may be associated with an SRSp configuration via a mapping relationship that shows a mapping (e.g., association) between the validity conditions and the ID of the SRSp configuration. ●When instructions are sent over the network: For example, a WTRU may, after sending instructions to a network (e.g., either gNB or LMF), receive information indicating one or more validity conditions, for example, together with an SDT and / or using an SDT resource (e.g., RA-SDT, CG-SDT). For example, a WTRU, which may consist of either a trigger event (for delayed MT-LR) and be operating in an INACTIVE state, may send instructions (e.g., information indicating either a location event instruction and a location event report) if one or more trigger events are detected. For example, a WTRU may receive from the network either information indicating an SRSp configuration and instructions to use a pre-configured SRSp configuration for use in an INACTIVE state (e.g., a configuration ID). A WTRU may also receive information indicating one or more validity conditions to help determine, for example, whether to use or deactivate an SRSp configuration for UL SRSp transmission after sending instructions to the network.

[0270] If a pre-configured SRSp configuration is determined to be invalid, for example, after detecting one or more trigger events, the WTRU may perform one of the following actions: ● Sending instructions to the network: For example, a WTRU may transmit instructions (e.g., information) to the network indicating either the detection of a trigger event or an SRSp configuration identifier (e.g., ID). For example, the information transmitted by the WTRU may indicate the expiration status of an SRSp configuration. For example, the information transmitted by the WTRU may indicate a request to update an SRSp configuration and any of the validity conditions associated with the indicated SRSp configuration. For example, instructions (e.g., information) may be transmitted to the network in any of the following: an LPP message, an on-demand PRS message (e.g., to either LMF or gNB), and an AS layer message (via either RRC, MAC CE, or UCI). ● Changes to alternative and effective SRSp configurations: For example, if the WTRU determines that the first SRSp configuration is no longer valid, it may use a second SRSp configuration that may be determined to satisfy its validity conditions. If there are multiple (e.g., two or more) SRSp configurations that are determined to be valid, and 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 priority (e.g., it may be assigned the highest priority). If all available SRSp configurations are determined to be invalid, and / or if no SRSp configurations that could be valid are available, the WTRU may select a second SRSp configuration from the invalid set of SRSp configurations, for example, based on priority (e.g., the selected SRSp configuration may be assigned the highest priority). ● Either update the SRSp settings or enable forwarding: ○For example, if WTRU determines that an SRSp configuration is no longer valid based on validity conditions (e.g., TA timer), WTRU may update and transfer its validity conditions based on validity conditions associated with either another SRSp configuration or another UL configuration that may be determined to be valid. In such a case, WTRU may change the first validity condition (e.g., associated with the first SRSp configuration) to be the same as that of the second validity condition (e.g., associated with either the second SRSp configuration or UL configuration) if, for example, the first validity condition has expired and the second validity condition is found to be active (e.g., valid) during the expiration of the first validity condition (e.g., after the expiration). For example, if it is determined that the validity conditions (e.g., TA timer) for either the associated second SRSp configuration or the associated UL configuration (e.g., either CG or SDT) are valid, the WTRU may update the validity conditions for the first SRSp configuration (e.g., by extending the TA timer) before or after it is determined that the validity conditions for the first SRSp configuration are either invalid or not similar to either the second SRSp or UL configuration. For example, the WTRU may send instructions (e.g., information) to the network indicating (e.g., requesting) either to update and transfer the validity conditions from the first SRSp / UL configuration to the second SRSp configuration.

[0271] Figure 11 shows an example of method 1100 for configuring a measurement gap (e.g., dynamically) for WTRU positioning determination. For example, method 1100 may be implemented in a WTRU. For example, in step 1110, the WTRU may determine the status of a PRS resource. For example, in step 1120, the WTRU may send a request to the radio network for measurement gap reconstruction. For example, in step 1130, the WTRU may receive a measurement gap configuration (e.g., information indicating it) from the network in response to the request.

[0272] For example, a request may be sent via either MAC-CE or UCI.

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

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

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

[0276] For example, the measurement gap configuration (e.g., information indicating it) may represent the measurement gap length, measurement gap periodicity, and measurement gap offset.

[0277] For example, the requirements may include the parameters (e.g., requested) of the measurement gap.

[0278] For example, the requirements may include requirements that invalidate all or part of the measurement gap (e.g., information indicating this).

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

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

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

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

[0283] For example, the condition could be that the RSRP of the PRS exceeds a threshold.

[0284] For example, the condition could be receiving explicit instructions from the network to reduce the number of measurement samples.

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

[0286] For example, method 1100 may further include sending configuration information about the PRS sent from a non-serving gNB to the serving gNB.

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

[0288] Figure 12 shows another example of method 1200 for configuring a measurement gap for WTRU positioning determination. For example, method 1200 may be implemented in a WTRU. For example, in step 1210, the WTRU may determine that a PRS may be configured in the LMF so that the WTRU can receive a PRS from either the serving base station or an adjacent base station within the configured measurement gap, provided that the WTRU determines that the base station has acknowledged a configuration request for a 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 pre-configured conditions are met. For example, in step 1230, the WTRU may (1) receive a PRS from either the serving base station or an adjacent base station without a measurement gap, and (2) receive an information configuration from the LMF indicating either time resources or frequency resources for receiving a PRS.

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

[0290] Figure 14 shows another example of method 1400 for configuring a measurement gap for WTRU positioning determination. For example, method 1400 may be implemented in a WTRU. For example, in step 1410, a mobile outgoing location request (MO-LR) may be received from a location service (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 the establishment of an LPP session. For example, in step 1430, the support information may be received in response to the capability information transmission indicating at least one PRS configuration. For example, in step 1440, a PRS measurement may be performed using the indicated at least one PRS configuration.

[0291] Figure 15 shows an example of method 1500 for requesting a measurement gap configuration. For example, 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 sent, for example, to a network.

[0292] For example, the WTRU may determine whether at least one of the PRS configurations shown can be either valid or invalid.

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

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

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

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

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

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

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

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

[0301] For example, the transmitted information may further indicate whether the selected first PRS configuration can be associated with a best-effort operating mode or a guaranteed operating mode.

[0302] Figure 16 shows another example of method 1600 for requesting a measurement gap configuration. For example, 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, the measurement gap patterns may be associated with a measurement gap length, measurement gap periodicity, and a measurement gap identifier. For example, in step 1620, the WTRU may measure a first positioning reference signal transmission during a first measurement gap period (e.g., perform a first positioning reference signal measurement), the first measurement gap period may be determined based on an initial measurement gap length and an initial measurement gap periodicity. For example, in step 1630, based on the measured first positioning reference signal transmission (e.g., first positioning reference signal measurement), the WTRU may send a request for a first measurement gap pattern among the indicated one or more measurement gap patterns, the request may include first information indicating a first measurement gap identifier associated with the first measurement gap pattern. For example, in step 1640, the WTRU may receive second information indicating the activation of a second measurement gap pattern among the one or more indicated measurement gap patterns, the second information may indicate a second measurement gap identifier associated with the second measurement gap pattern. For example, in step 1650, the WTRU may measure a second positioning reference signal transmission during a second measurement gap period (e.g., perform a second positioning reference signal measurement), the second measurement gap period may be determined based on a second measurement gap length and a second measurement gap periodicity that may be associated with the second measurement gap pattern.

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

[0304] For example, a 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 the initial measured gap length or the initial measured gap periodicity.

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

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

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

[0309] For example, the second measurement gap period may be the same 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, one or more first metrics may include quality metrics that represent the quality of a measured first positioning reference signal transmission (e.g., a first positioning reference signal measurement performed).

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

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

[0315] For example, the stability variability metric may include either the variance or standard deviation of the WTRU location.

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

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

[0318] For example, the criteria may include quality metrics that exceed a threshold over a second duration.

[0319] For example, one or more first metrics that meet the criteria may include stability variability metrics that fall 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 indicating one or more downlink transmissions is received, and one or more downlink transmissions may be associated with a priority higher than the initial priority associated with the initial measurement gap length and the initial measurement gap periodicity.

[0322] For example, one or more downlink transmissions may include channel status 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, if it is determined that a period of time may have elapsed since receiving second information indicating the activation of a second measurement gap pattern, the transmission of a third positioning reference signal 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, one or more first metrics that meet the criteria may include quality metrics that fall below the threshold.

[0327] For example, the criteria may include quality metrics that fall below a threshold over a second duration.

[0328] For example, one or more first metrics that meet the criteria may include stability variability metrics that exceed 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 the activated second measurement gap pattern.

[0331] Figure 17 shows another example of method 1700 for requesting a measurement gap configuration. For example, method 1700 may be implemented in a WTRU. For example, in step 1710, the WTRU may receive configuration information indicating a first positioning configuration associated with, for example, an effectiveness metric. For example, in step 1710, the WTRU may determine, based on the effectiveness metric, that the first positioning configuration may be invalid. For example, in step 1720, the WTRU may transmit first information requesting support 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 positioning configuration shown may be activated.

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

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

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

[0336] For example, area effectiveness instructions may be associated with tracking areas.

[0337] For example, an area effectiveness instruction may include one or more cell identifiers.

[0338] For example, the first positioning configuration may be further determined to be invalid if the WTRU has moved to a second area different from the first area indicated by the area validity instruction.

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

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

[0341] Throughout the embodiments described, the terms “configurable parameter,” “pre-configured parameter,” and “configuration parameter” may be referred to herein as a configurable parameter of a WTRU by receiving configuration information associated with that parameter and indicating the values ​​to which the parameter can be configured.

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

[0343] Any feature, variation, or embodiment described in the Method is compatible with apparatus devices having means for processing the disclosed Method, devices having circuits including any of a transmitter, receiver, processor, and memory configured to process the disclosed Method, computer program products including program code instructions, and non-temporary computer-readable storage media storing program instructions.

[0344] 4. Conclusion While features and elements are described above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. In addition, the methods described herein can be implemented in computer programs, software, or firmware embedded in computer-readable media for execution by a computer or processor. Examples of non-temporary 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 multipurpose disks (DVDs). A radio frequency transceiver can be implemented using a processor associated with software for use in a WTRU102, WTRU, terminal, base station, RNC, or any host computer.

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

[0346] Those with ordinary art in the art will understand that operations and symbolically represented arithmetic or instructions involve the manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause a resulting transformation or reduction of electrical signals, and maintains these data bits in memory locations of the memory system, thereby reconfiguring or otherwise modifying the CPU's operations and processing of other signals. The memory locations where the data bits are maintained are physical locations having specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that exemplary embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the methods provided.

[0347] Data bits may also be maintained on computer-readable media, including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory ("RAM")) or CPU-readable non-volatile (e.g., Read-Only Memory ("ROM")) mass storage systems. The computer-readable media may include cooperative or interconnected computer-readable media distributed among multiple interconnected processing systems, which may reside exclusively on a processing system or be local or remote to the processing system. Typical embodiments are not limited to the memory described above, and it is understood that other platforms and memories may support the methods described.

[0348] In exemplary embodiments, any of the operations, processes, etc., described herein may be implemented as computer-readable instructions stored on a computer-readable medium. These computer-readable instructions may be executed by processors in mobile devices, network elements, and / or any other computing devices.

[0349] There is little distinction between hardware and software implementations of a system configuration. The use of hardware or software is generally (though not always, in certain situations the choice between hardware and software can be significant) a design choice involving a cost-effectiveness trade-off. Various vehicles (e.g., hardware, software, and / or firmware) may exist in which the processes and / or systems and / or other technologies 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 technologies are deployed. For example, if the implementer determines that speed and accuracy are paramount, the implementer may choose primarily hardware and / or firmware vehicles. If flexibility is paramount, the implementer may choose primarily software implementations. Alternatively, the implementer may choose any combination of hardware, software, and / or firmware.

[0350] The detailed description above illustrates various embodiments of devices and / or processes through the use of block diagrams, flowcharts, and / or examples. Those skilled in the art will understand that, insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, each function and / or operation in such block diagrams, flowcharts, or examples may be implemented individually and / or collectively by a wide range of hardware, software, firmware, or substantially any combination thereof. Suitable processors include, by example, general-purpose processors, dedicated processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), field-programmable gate array (FPGA) circuits, any other type of integrated circuit (IC), and / or state machines.

[0351] While the features and elements are provided above in specific combinations, it will be understood by those with ordinary art in the art that each feature or element can be used individually or in any combination with other features and elements. This disclosure is not limited in terms of the specific embodiments described in this application, which are intended to be illustrative 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 invention. Any elements, actions, or instructions used in the description of this application should not be construed as important or essential to the invention unless expressly presented as such. In addition to those enumerated herein, functionally equivalent methods and apparatus within the scope of this disclosure will be apparent to those skilled in the art from the above description. Such modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only by the terms of the appended claims, and together with the full scope of the equivalents to which such claims are entitled. It should be understood that this disclosure is not limited to any particular method or system.

[0352] It should also be understood that the terms used herein are for the purpose of describing only specific embodiments and are not intended to limit them. Where used herein, and referred to herein, “Station” and its abbreviation “STA,” “User Equipment” and its abbreviation “UE” may mean (i) a radio transmit and / or receive unit (WTRU) such as the infrastructure described herein, (ii) any of several embodiments of a WTRU such as the infrastructure described herein, (iii) a radio-enabled and / or wired (e.g., tetherable) device configured to have some or all of the structure and functions of a WTRU such as the infrastructure described herein, (iii) a radio-enabled and / or wired device configured to have less than all of the structure and functions of a WTRU such as the infrastructure described herein, or (iv) other. Details of exemplary WTRUs that may represent any WTRU enumerated herein are provided below with respect to Figures 1A to 1E.

[0353] In certain representative embodiments, some parts 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, it will be recognized by those skilled in the art that some aspects of the embodiments disclosed herein may be equivalently implemented in an integrated circuit as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or substantially any combination thereof, and that designing circuits and / or writing software and / or firmware code is within the scope of the art of those skilled in the art in light of this disclosure. In addition, it will be understood by those skilled in the art that the mechanisms of the subject matter described herein may be distributed as various forms of program products, and that the exemplary embodiments of the subject matter described herein are applicable regardless of the particular type of signal-carrying medium used to actually carry out the distribution. Examples of signal-carrying media include, but are not limited to, recordable media such as floppy disks, hard disk drives, CDs, DVDs, digital tapes, and computer memory, as well as transmitting media such as digital and / or analog communication media (e.g., optical fiber cables, waveguides, wired communication links, wireless communication links, etc.).

[0354] The subject matter described herein may, in some cases, depict different components that are contained within or connected to other different components. Such illustrated architectures are merely examples, and it should be understood that in practice, many other architectures can be implemented to achieve the same function. Conceptually, any arrangement of components to achieve the same function is effectively “associated” in such a way that the desired function can be achieved. Therefore, any two components combined herein to achieve a particular function, regardless of architecture or intermediate components, can be seen as “associated” with each other in such a way that the desired function can be achieved. Similarly, any two components thus associated can be seen as “operably connected” or “operably coupled” with each other to achieve the desired function, and any two components that can be associated in such a way can be seen as “operably coupled” with each other to achieve the desired function. Specific examples of operably coupled components include, but are not limited to, physically matable and / or physically interacting components, and / or wirelessly interactable and / or wirelessly interacting components, and / or logically interacting and / or logically interactable components.

[0355] With regard to the use of substantially any plural and / or singular terms herein, those skilled in the art can convert from plural to singular and / or singular to plural as appropriate to the context and / or use. For clarity purposes, various singular / plural rearrangements may be explicitly described herein.

[0356] In general, it will be understood by those skilled in the art that the terms used herein, and especially in the appended claims (e.g., in the body of the appended claims), are generally intended to be “non-limiting” terms (for example, the term “contains” should be interpreted as “contains but not limited to,” the term “has” should be interpreted as “has at least,” and the term “contains” should be interpreted as “contains but not limited to.”). Furthermore, it will be understood by those skilled in the art that if a particular number of claims introduced are intended to be described, such intent is explicitly stated in the claim, and if such statement is not present, such intent does not exist. For example, if only one item is intended, the term “single” or similar word may be used. To aid understanding, the following appended claims and / or descriptions herein may include the use of the introductory phrases “at least one” and “one or more” to introduce the description of the claims. However, the use of such phrases should not be interpreted as meaning that the introduction of a claim description by the indefinite article "a" or "an" limits any particular claim containing such introduced description to embodiments containing only one such description, even if the same claim contains the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (for example, "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce a claim description. In addition, it will be recognized by those skilled in the art that even if a particular number of descriptions in an introduced claim are explicitly stated, such description should be interpreted as meaning at least the number stated (for example, the simple statement "two descriptions" without other modifiers means at least two descriptions or two or more descriptions).Furthermore, when a notation similar to "at least one of A, B, and C" is used, such a structure is generally intended to mean what a person skilled in the art would understand (for example, "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 a notation similar to "at least one of A, B, or C" is used, such a structure is generally intended to mean what a person skilled in the art would understand (for example, "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). It will be further understood by those skilled in the art that any substantially any disjunct word and / or phrase presenting two or more alternative terms in the specification, claims, or drawings should be understood as construed to include the possibility of including one of the terms, either of the terms, or both of the terms. For example, the phrase “A or B” should be understood to include the possibility of “A” or “B” or “A and B.” Furthermore, as used herein, the term “any of ~” followed by a list of multiple items and / or a list of categories of multiple items is intended to include “any of,” “any combination of,” “any number of,” and / or “any number of combinations of,” of the items and / or categories of items, individually or in combination with other items and / or categories of other items. Furthermore, as used herein, the term “set / group” is intended to include any number of items, including zero. In addition, as used herein, the term “number” is intended to include any number, including zero.

[0357] In addition, if any feature or aspect of the present disclosure is described from the perspective of the Markush group, a person skilled in the art will recognize that the present disclosure is also described from the perspective of any individual member or subgroup of a member of the Markush group.

[0358] For all purposes, including providing written explanations, as will be understood by those skilled in the art, all scopes disclosed herein also encompass any possible sub-scopes and combinations of sub-scopes. Any enumerated scope can be readily recognized as sufficiently explainable and enable that the same scope can be broken down into at least equal 1 / 2, 1 / 3, 1 / 4, 1 / 5, 1 / 10, etc. As a non-limiting example, each scope described herein can readily be broken down into the lower third, the middle third, the upper third, etc. Also, as will be understood by those skilled in the art, all words such as “up to,” “at least,” “greater than,” and “less than” include the number mentioned and mean a scope that can be further broken down into sub-scopes as described above. Finally, as will be understood by those skilled in the art, a scope includes 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] Furthermore, unless otherwise specifically stated, the claims should not be read as being limited to the order or elements provided. In addition, in any claim, the use of the term “means for” is intended to appeal to Section 112, paragraph 6 of the U.S. Patent Act, or the means-plus-function claim format, and no claim without the term “means for” is intended to appeal in that way.

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

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

[0362] While features and elements are described above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. In addition, the methods described herein can be implemented in computer programs, software, or firmware embedded on computer-readable media for execution by a computer or processor. Examples of non-temporary 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 multi-purpose disks (DVDs). A processor associated with software can be used to implement a radio frequency transceiver for use in a UE, WTRU, terminal, base station, RNC, or any host computer.

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

[0364] Those with ordinary art in the relevant field will understand that operations and symbolically represented arithmetic or instructions involve the manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause a resulting transformation or reduction of electrical signals, and maintains these data bits in memory locations of the memory system, thereby reconfiguring or otherwise altering the CPU's operations and processing of other signals. The memory locations where the data bits are maintained are physical locations having specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits.

[0365] Data bits may also be maintained on computer-readable media, including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory ("RAM")) or CPU-readable non-volatile (e.g., Read-Only Memory ("ROM")) mass storage systems. The computer-readable media may include cooperative or interconnected computer-readable media distributed among multiple interconnected processing systems, which may reside exclusively on a processing system or be local or remote to the processing system. Typical embodiments are not limited to the memory described above, and it is understood that other platforms and memories may support the methods described.

[0366] Any element, action, or instruction used in the description of this application should not be construed as important or essential to the invention unless expressly stated otherwise. In addition, as used herein, the article "a" is intended to include one or more items. If only one item is intended, the term "one" or similar word may be used. Also, as used herein, the term "any of" followed by a list of multiple items and / or a list of categories of multiple items is intended to include "any of", "any combination of", "any number of", and / or "any number of combinations of", either individually or in combination with other items and / or categories of other 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] Furthermore, claims should not be read as being limited to the order in which they are described or the elements provided, unless otherwise specifically stated. In addition, the use of the term “means” in any claim is intended to appeal under Section 112, paragraph 6 of the U.S. Patent Act, and no claim that does not contain the word “means” is intended to appeal under that purpose.

[0368] Suitable processors include, for example, general-purpose processors, dedicated processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), field-programmable gate array (FPGA) circuits, any other type of integrated circuit (IC), and / or state machines.

[0369] A radio frequency transceiver can be implemented using a software-related processor for use in a radio transceiver 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 hardware and / or software-implemented modules such as software-defined radio (SDR), and may also be implemented in other components such as cameras, video camera modules, video phones, speakerphones, vibration devices, speakers, microphones, television transceivers, hands-free headsets, keyboards, Bluetooth® modules, frequency modulation (FM) radio units, near-field communication (NFC) modules, liquid crystal display (LCD) display units, organic light-emitting diode (OLED) display units, digital music players, media players, video game player modules, internet browsers, and / or wireless local area network (WLAN) or ultra-wideband (UWB) modules.

[0370] Although the present invention has been described in relation to a communication system, it is intended that the system may be implemented in software on a microprocessor / general-purpose computer (not shown). In certain embodiments, one or more functions of various components may be implemented in software that controls the general-purpose computer.

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

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

Claims

1. A method implemented in a wireless transceiver unit (WTRU), A step of receiving configuration information indicating a time window associated with positioning, wherein the configuration information indicates either the duration or periodicity of the time window; A step of receiving first scheduling information indicating that a first uplink transmission comprising a sounding reference signal transmission (SRS transmission) is to be transmitted, wherein the first uplink transmission does not include a positioning SRS (SRSp), The steps include receiving second scheduling information indicating that a second uplink transmission, including an SRSp transmission, The steps include: transmitting the second uplink transmission within the time window if the second uplink transmission is scheduled for transmission within the time window, and transmitting the first uplink transmission only when the first uplink transmission is scheduled for transmission outside the time window; A method for providing this.

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

3. The method according to any one of claims 1 and 2, wherein the duration is represented as one or more symbols, one or more slots, one or more frames, and one or more seconds.

4. The method according to any one of claims 1 to 3, wherein when the first uplink transmission is scheduled for a transmission within the time window, the first uplink transmission is postponed for a transmission outside the time window.

5. The method according to any one of claims 1 to 4, wherein the first uplink transmission is dropped when the first uplink transmission is scheduled for transmission within the time window.

6. The method according to any one of claims 1 to 5, wherein the time window is associated with a priority, and the SRS transmission has a lower priority than the priority associated with the time window.

7. The step of receiving third scheduling information indicating that a third uplink transmission is to be transmitted, which includes either a physical uplink control channel transmission or a physical uplink sharing channel transmission. The method according to any one of claims 1 to 6, comprising:

8. The method according to claim 7, wherein the second uplink transmission is scheduled for transmission within the time window, and the third uplink transmission is transmitted only when the third uplink transmission is scheduled for transmission outside the time window.

9. The method according to any one of claims 1 to 8, further comprising the step of receiving a fourth scheduling information indicating a downlink transmission scheduled within the aforementioned time window.

10. The method according to claim 9, further comprising the step of receiving the downlink transmission within the time window.

11. A wireless transceiver unit (WTRU) equipped with a circuit including one of a transmitter, receiver, processor, and memory, The system receives configuration information indicating a time window associated with positioning, and the configuration information indicates either the duration or periodicity of the time window. First scheduling information is received indicating that a first uplink transmission comprising a sounding reference signal transmission (SRS transmission) is to be transmitted, and the first uplink transmission does not include a positioning SRS (SRSp). Upon receiving second scheduling information indicating that a second uplink transmission, including an SRSp transmission, The WTRU transmits the second uplink transmission within the time window, provided that the second uplink transmission is scheduled for transmission within the time window, and transmits the first uplink transmission only when the first uplink transmission is scheduled for transmission outside the time window. A well-configured WTRU.

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

13. The WTRU according to any one of claims 11 and 12, wherein the duration is represented as one or more symbols, one or more slots, one or more frames, and one or more seconds.

14. The WTRU according to any one of claims 11 to 13, wherein when the first uplink transmission is scheduled for a transmission within the time window, the first uplink transmission is postponed for a transmission outside the time window.

15. The WTRU according to any one of claims 11 to 14, wherein the first uplink transmission is dropped when the first uplink transmission is scheduled for transmission within the time window.

16. The WTRU according to any one of claims 11 to 15, wherein the time window is associated with a priority, and the SRS transmission has a lower priority than the priority associated with the time window.

17. The WTRU according to any one of claims 11 to 16, wherein the WTRU is configured to receive third scheduling information indicating that it transmits a third uplink transmission, which includes either a physical uplink control channel transmission or a physical uplink sharing channel transmission.

18. The WTRU according to claim 17, provided that the second uplink transmission is scheduled for transmission within the time window, the third uplink transmission is transmitted only when the third uplink transmission is scheduled for transmission outside the time window.

19. The WTRU according to any one of claims 11 to 18, wherein the WTRU is configured to receive a fourth scheduling information indicating a downlink transmission scheduled within the time window.

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

Images