Methods and apparatus for supporting the continuity of positioning services

Abstract

The present invention provides a method and apparatus for supporting the continuity of positioning services. [Solution] This disclosure relates to a method and apparatus for supporting positioning service continuity. One typical method includes a wireless transceiver unit (WTRU) receiving a configuration for supporting positioning service continuity during a handover. The method further includes the WTRU supporting positioning service continuity in accordance with the configuration, at least in part, by determining one or more transmissions to be performed. The method also includes assisting a radio access network using a data link handover by performing one or more transmissions in accordance with the configuration.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 257,213, filed on October 19, 2021; U.S. Provisional Patent Application No. 63 / 249,199, filed on September 28, 2021; and U.S. Provisional Patent Application No. 63 / 168,195, filed on March 30, 2021, the contents of which are incorporated herein by reference.

[0002] This disclosure relates to methods and apparatuses for performing wireless communication, and more particularly, to supporting positioning service continuity.

Background Art

[0003] In 3GPP Release 16, SRS resource sets and SRS resources configured for positioning are specified.

Summary of the Invention

[0004] In certain representative embodiments, a method, an apparatus, and a system may be implemented to support positioning service continuity for downlink (DL) - based positioning. <l

[0005] In certain representative embodiments, a method, an apparatus, and a system may be implemented to support positioning service continuity for uplink (UL) - based positioning.

[0006] In certain representative embodiments, a method, an apparatus, and a system may be implemented to support positioning service continuity based on switching between different positioning methods.

[0007] In certain representative embodiments, methods, apparatus, and systems can be implemented that allow a WTRU to switch from a first PRS configuration to a second PRS configuration after a handover (HO) based on configured PRS configurations associated with different base stations / gNBs / cells and thresholds. [Brief explanation of the drawing]

[0008] A more detailed understanding can be obtained from the following detailed description, provided as an example in conjunction with the drawings attached to this specification. The figures in such drawings, as well as the detailed description, are illustrative. Therefore, the figures and detailed description should not be considered limiting, and other equally effective examples are possible and likely. Furthermore, similar reference numerals ("ref") within the figures ("FIG") indicate similar elements. [Figure 1A] This is a system diagram showing an exemplary communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] This figure shows exemplary wireless transmit / receive units (WTRUs) used in the communication system shown in Figure 1A, according to one or more embodiments. [Figure 1C] This is a system diagram showing exemplary radio access networks (RAN) and core networks (CN) used in the communication system of Figure 1A, according to one or more embodiments. [Figure 1D] This is a system diagram showing further exemplary RAN and CN used within the communication system shown in Figure 1A, according to one or more embodiments. [Figure 2] This figure shows a WTRU that receives a downlink (DL) positioning reference signal (PRS) from a target gNB while connected to a source gNB, according to one or more embodiments. [Figure 3]This is a system diagram showing a WTRU that receives DL-PRS from a source gNB while connected to a target gNB, according to one or more embodiments. [Figure 4] This is a system diagram showing a WTRU that receives DL-PRS from a source gNB and a target gNB during a handover (HO) according to one or more embodiments. [Figure 5] This is a graph showing the timing of operations before, during, and after HO according to one or more embodiments. [Figure 6] This flowchart illustrates a typical method implemented by WTRU in one or more embodiments. [Figure 7] This flowchart illustrates another typical method implemented by WTRU, according to one or more embodiments. [Figure 8] This flowchart illustrates one or more representative methods implemented by WTRU. [Figure 9] This flowchart illustrates additional typical methods implemented by WTRU through one or more embodiments. [Figure 10] This flowchart illustrates yet another representative method implemented by WTRU, according to one or more embodiments. [Figure 11] This flowchart illustrates yet another representative method implemented by WTRU, according to one or more embodiments. [Figure 12] This flowchart illustrates additional representative methods implemented by WTRU through one or more embodiments. [Figure 13] This flowchart illustrates yet another representative method implemented by WTRU, according to one or more embodiments. [Figure 14] This flowchart illustrates yet another representative method implemented by WTRU, according to one or more embodiments. [Figure 15] This flowchart illustrates additional representative methods implemented by WTRU through one or more embodiments. [Modes for carrying out the invention]

[0009] preface 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, those embodiments and other examples explicitly, implicitly, and / or essentially (collectively "provided") herein, disclosed, or otherwise provided.

[0010] Exemplary network for implementing the embodiment 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 employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), quadrature FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word direct Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique-word OFDM (UW-OFDM), resource block filter OFDM, and filter bank multi-carrier (FBMC).

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

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

[0013] 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 a combination 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.

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

[0015] 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 a radio technology 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 (DL) Packet Access (HSDPA) and / or High-Speed Uplink (UL) Packet Access (HSUPA).

[0016] In one embodiment, the base stations 114a and the WTRUs 102a, 102b, 102c can implement a radio technology 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).

[0017] In one embodiment, base stations 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as NR radio access, which can establish an air interface 116 using New Radio (NR).

[0018] In one embodiment, base station 114a and WTRU 102a, 102b, 102c may implement multiple radio access technologies. For example, base station 114a and WTRU 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example, using the dual connectivity (DC) principle. Thus, the air interface utilized by WTRU 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to and from multiple types of base stations (e.g., eNB and gNB).

[0019] In other embodiments, base stations 114a and WTRUs 102a, 102b, and 102c are IEEE 802.11 (i.e., Wireless Fidelity, WiFi) and IEEE 802.16 (i.e., WiMAX (Worldwide Interoperability for Microwave Access)). It can implement wireless technologies such as CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), and GSM EDGE (GERAN).

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

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

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

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

[0024] Figure 1B is a system diagram showing an exemplary WTRU102. As shown in Figure 1B, the WTRU102 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 WTRU102 may include any partial combination of the aforementioned elements while maintaining consistency with one embodiment.

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

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

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

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

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

[0030] The processor 118 may receive power from the power supply 134 and be configured to distribute and / or control power to other components within 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.

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

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

[0033] WTRU102 may include a full-duplex radio in which the transmission and reception of some or all of a signal (for example, associated with specific subframes of both UL (for example, for transmission) and DL (for example, for reception) may be simultaneous and / or together. 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 some or all of a signal (for example, associated with specific subframes of either UL (for example, for transmission) or DL ​​(for example, for reception)).

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

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

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

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

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

[0039] SGW164 can be connected to each of eNode-B160a, 160b, and 160c in RAN104 via the S1 interface. Generally, SGW164 can route and forward user data packets to and from WTRU102a, 102b, and 102c. SGW 164 can perform other functions such as fixing the user plane during inter-eNode-B HO, triggering paging when DL data is available to WTRU102a, 102b, and 102c, and managing and remembering the context of WTRU102a, 102b, and 102c.

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

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

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

[0043] In a typical embodiment, the other network 112 may be a WLAN.

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

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

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

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

[0048] 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 bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV White Space (TVWS) spectrum, while 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz 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).

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

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

[0051] Figure 1D is a system diagram illustrating RAN113 and CN115 according to one 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.

[0052] RAN113 may include gNB180a, 180b, and 180c, but it will be understood that RAN113 may include any number of gNBs while maintaining consistency with one 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).

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

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

[0055] Each of the gNB180a, 180b, and 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, HO 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 toward User Plane Functions (UPF) 184a and 184b, routing of control plane information toward Access and Mobility Management Functions (AMF) 182a and 182b, etc. As shown in Figure 1D, the gNB180a, 180b, and 180c may communicate with each other via the Xn interface.

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

[0057] 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 that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or similar. AMF182A,182B are part of RAN113 and non-third-generation partnership projects (3) such as LTE, LTE-A, LTE-A Pro and / or WiFi. rd The Generation Partnership Project (GPP) may provide control plane functionality for switching between other RANs (not shown) that employ other wireless technologies such as GPP access technology.

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

[0059] 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 packet routing and forwarding, enforcement of user plane policies, support for multi-homed PDU sessions, processing of user plane QoS, buffering of DL packets, and providing mobility anchoring.

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

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

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

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

[0064] Support for the continuity of positioning services Positioning services in legacy systems Release 16 uses DL, UL, and DL, as well as the UL positioning method. In the DL positioning method, PRS is transmitted to the WTRU from multiple TX / RX points (TRP). The WTRU observes multiple reference signals and measures the time difference between a pair of PRSs. The WTRU then returns the measured reference signal time difference (RSTD) to the position management function (LMF). In addition, the WTRU can return the measured reference signal received power (RSRP) for each PRS. Based on the returned measurements, the LMF performs positioning of the WTRU. Alternatively, the WTRU can report the RSRP for DL ​​angle-based positioning methods.

[0065] LMF is a non-limiting example of a node or entity (e.g., a network node or entity) that may be used for or to support positioning. Other types of nodes or entities may be used instead of LMF and may still be consistent with this disclosure. In a UL positioning method, the WTRU transmits a sounding reference signal (SRS) for positioning, configured by Radio Resource Control (RRC), to the receiving point (RP). In a timing-based method, the RP measures the relative time of arrival (RTOA) of the received SRS and reports the measurement to the LMF. The WTRU may report an RSRP for the SRS. In an angle-based UL positioning method, the RP measures the angle of arrival and reports it to the LMF.

[0066] Finally, in UL and DL positioning methods, the WTRU measures the Rx-Tx time difference between the received PRS and the transmitted SRS. The Rx-Tx time difference is reported from the WTRU to the LMF. The WTRU can also report the measured RSRP for the PRS. Similarly, in the TRP, the Rx-Tx difference between the received SRS and the transmitted PRS is calculated.

[0067] This disclosure considers / implements various positioning methods. For example, “DL positioning method” may refer to any positioning method that uses a DL reference signal such as PRS. The WTRU receives multiple reference signals from the transmit point (TP) and measures the DL RSTD and / or RSRP. Examples of DL positioning methods include DL Angle of Departure (AoD) or DL ​​Time Difference of Arrival (TDOA) positioning. Additionally, “UL positioning method” may refer to any positioning method that uses UL reference signals such as SRS for positioning. A WTRU transmits SRS to multiple RPs, and the RPs measure UL RTOA and / or RSRP. Examples of UL positioning methods include UL-TDOA or UL-AoA positioning. “DL and UL positioning method” may refer to a positioning method that utilizes both UL reference signals and DL reference signals for positioning. In one embodiment, a WTRU transmits SRS to multiple TRPs, and a gNB measures the Rx-Tx time difference. The network can measure the RSRP for the received SRS. A WTRU measures the Rx-Tx time difference for PRS transmitted from multiple TRPs. A WTRU can measure the RSRP for the received PRS. The round-trip time is calculated using the Rx-TX difference measured at the WTRU and gNB, and possibly the RSRP. The Rx-Tx difference refers to the difference between the arrival time of the reference signal transmitted by the TRP and the transmission time of the reference signal transmitted from / by the WTRU. One example of a DL&UL positioning method is multi-round-trip time (RTT) positioning.

[0068] In this disclosure, “Network” may include one or more AMFs, one or more LMFs, and / or one or more Next Generation Radio Access Networks (NG-RANs). The Release 16 / 17 positioning procedure for DL-PRS measurements in the RRC CONNECTED state enables intra-gNB mobility (within the coverage area of ​​TRPs belonging to the same gNB) and inter-gNB mobility (for scenarios where the same PRS configuration is used by multiple gNBs). Reporting of measurements or location information to the LMF is supported via the serving gNB / cell. Positioning service continuity for UL-based positioning allows the WTRU to continue using the same Sounding Reference Signal (SRSp) configuration for positioning while / after HO is not supported in Release 16 / 17.

[0069] 3GPP Release 17 supports WTRU-based and LMF-based positioning for RAT-dependent positioning. The WTRU behavior and procedures for supporting low latency and high accuracy positioning service continuity for RAT-dependent positioning are unknown.

[0070] In DL-based positioning, where the WTRU determines positioning information based on DL-PRS measurements, when the WTRU receives a data link HO from the source gNB to the target gNB, if the PRS configurations used by the source gNB and the target gNB are different, the WTRU needs to request a new PRS configuration, or may request one. Sending a request to the LMF via the target gNB and receiving the new PRS configuration during the execution of the data link HO can result in increased latency and possible positioning gaps (e.g., positioning measurements may become unavailable). In addition, until the new PRS configuration becomes available to the WTRU, the inability of the WTRU to perform measurements on the PRS received from the target gNB, which can receive the strongest PRS compared to other gNBs, may also lead to a decrease in positioning accuracy at the WTRU. Furthermore, even if the target gNB uses the same PRS configuration as the source gNB, the measurement gap configured by the source gNB via RRC signaling may be released during the data link HO and reconfigured by the target gNB after the HO. This can result in possible positioning gaps and longer latency associated with the measurement gap configuration.

[0071] In UL-based positioning, the time / frequency resource configuration for UL-SRSp is configured in the WTRU by the serving gNB. When the WTRU receives a data link HO, the SRSp configuration provided by the source gNB may be released. Subsequently, there may be a long latency to receive a new SRSp configuration from the target gNB after the HO. In this case, a positioning gap and a decrease in positioning accuracy may occur because the TRP associated with the target gNB cannot perform measurements on the new SRSp transmitted by the WTRU.

[0072] For DL ​​and UL-based positioning (e.g., multi-RTT positioning methods), the set of TRPs that can transmit / receive PRS / SRSp may change based on WTRU mobility. This can also lead to inaccurate estimations of distance from WTRU to TRPs, the possibility of inaccurate positioning calculations, and reduced positioning accuracy.

[0073] In general, existing (Release 16 / 17) approaches to supporting RAT-dependent positioning can result in long latency and positioning gaps (periods during which positioning measurements are unavailable) due to delays in the LMF / RAN that trigger PRS / SRSp transmissions from target cells and / or WTRUs. In this regard, one issue that needs to be addressed is, or may be, how to ensure positioning service continuity so that the QoS associated with positioning (e.g., high accuracy, low latency, low signaling overhead) can be supported during WTRU mobility.

[0074] Typical positioning solutions / procedures With respect to reference signals in this disclosure, it should be noted that “SRS for positioning” in this specification refers to SRS signals / transmissions used for positioning. Resources for SRS for positioning (SRSp) may be defined by RRC (e.g., signaled). Release 16 specifies SRS resource sets and SRS resources configured for positioning. However, “SRS for positioning” or “SRS” in a particular embodiment may include various types of signals. For example, SRS may be an SRS configured under SRS-PosResourceSet-r16 and SRS-PosResource-r16. Alternatively or additionally, SRS may be an SRS configured under SRS-ResourceSet and SRS-Resource. Alternatively or additionally, SRS may be an SRS not configured under SRS-PosResourceSet-r16 and SRS-PosResource-r16. Alternatively or additionally, the SRS may be an SRS not configured under SRS-ResourceSet and SRS-Resource. Alternatively or additionally, the SRS may be an SRS not associated with SRS-PosResourceSet-r16, SRS-PosResource-r16, SRS-ResourceSet, or SRS-Resource. Alternatively or additionally, the SRS may be a UL reference signal associated for positioning. Alternatively or additionally, the SRS may be a demodulated reference signal (DM-RS) for UL. Alternatively or additionally, the SRS may be a phase tracking reference signal (PTRS) for phase for UL.

[0075] For brevity, an SRS for positioning is denoted as "SRSp". Furthermore, PRS or SRS as used herein are not limited to RS used for positioning. The disclosed methods can be applied to or used in conjunction with any DL or UL reference signal.

[0076] With respect to the positioning configuration in this disclosure, the positioning configuration may include a set of information relating to positioning measurements and / or SRSp transmissions. Various types of information may be included in the positioning configuration. For example, the positioning configuration may include information about the positioning method used (e.g., DL-TDOA, UL-TDOA, DL-AoD, UL-AoA, Multi-RTT). Additionally or alternatively, the positioning configuration may include information about PRS configurations, SRSp configurations, and / or UL resources (e.g., physical random access channels (PRACH), physical UL shared channels (PUSCH), and / or physical uplink control channels (PUCCH)) to report positioning measurements. Additionally or alternatively, the positioning configuration may include information about one or more thresholds for determining positioning measurement quality and / or positioning operation modes (e.g., initial positioning operation mode).

[0077] Regarding PRS resource configuration, this type of configuration can include various types of information. For example, the PRS configuration may include information about the PRS resource ID, PRS sequence ID, and / or other IDs used to generate the PRS sequence. Alternatively or additionally, the PRS configuration may include information about the PRS resource element offset, PRS resource slot offset, and / or PRS symbol offset. Alternatively or additionally, the PRS configuration may include information about PRS pseudo-collocation (QCL) information, PRS resource set ID, and / or information about a list of PRS resources in the resource set. Alternatively or additionally, the PRS configuration may include information regarding the number of PRS symbols, muting patterns for the PRS, muting parameters such as repetition coefficients, and / or muting options. Alternatively or additionally, the PRS configuration may include information regarding the PRS resource power, the periodicity of the PRS transmission, spatial orientation information of the PRS transmission (e.g., beam information, transmission angle), and / or spatial orientation information of the UL RS reception (e.g., beam ID used to receive the UL RS, angle of arrival (AoA)).

[0078] Regarding SRSp resource configurations, this type of configuration may include various types of information. For example, an SRSp resource configuration may include information about the resource ID, comb offset value, cyclic shift value, and / or the starting position in the frequency domain. Alternatively or additionally, an SRSp resource configuration may include information about the number of SRSp symbols, the frequency domain shift for the SRSp, the frequency hopping pattern, and / or the type of SRSp, e.g., aperiodic, semi-permanent, or periodic. Alternatively or additionally, an SRSp resource configuration may include information about the sequence ID used to generate the SRSp, or other IDs used to generate the SRSp sequence. Alternatively or additionally, an SRSp resource configuration may include spatial relationship information indicating which reference signal the SRSp is spatially related to. Alternatively or additionally, an SRSp resource configuration may include a resource set ID, a list of SRSp resources within the resource set, and / or transmit power-related information. Alternatively or additionally, the SRSp resource configuration may include path loss reference information, which may include a synchronization signal block (SSB), a channel status information (CSI) reference signal (CSI-RS), and / or an index for PRS. Alternatively or additionally, the SRSp resource configuration may include periodicity and / or spatial orientation information for SRSp transmissions (e.g., beam information, transmission angle). Alternatively or additionally, the SRSp resource configuration may include spatial orientation information for DL ​​RS reception (e.g., beam ID used to receive DL RS, angle of arrival). As part of the configuration, the WTRU may receive information relating to cell IDs, global cell IDs, and / or TRP IDs associated with PRS. For example, a TRP transmitting a PRS may be identified by a TRP ID, and the TRP ID may belong to a cell identified by a cell ID. The WTRU may be configured with timing information such as subframe number (SFN) offsets for PRS or SRSp transmissions. An offset may or may be introduced to prevent the WTRU from receiving overlapping PRSs in the time domain.

[0079] Typical procedures / methods for supporting positioning service continuity for DL-based positioning In one family of solutions, the WTRU performs positioning service continuity based on PRS / Radio Resource Management (RRM) measurements. For example, the WTRU may initiate and perform positioning service continuity by sending a request for a new PRS configuration to the network (e.g., LMF and / or RAN) when triggered by one or more configured positioning service continuity conditions. Positioning service continuity can refer to the WTRU changing and / or updating one or more PRS configurations associated with different TRP / gNB / cells in the network. The PRS configuration used may be changed to perform measurements, for example, due to WTRU mobility and / or when the WTRU receives a data link HO. In another embodiment, positioning service continuity may not be directly due to WTRU mobility, in which case the PRS configuration used may be changed to perform measurements when the WTRU can detect one or more new TRP / gNB / cells (e.g., when the WTRU can receive an RS from a new TRP / gNB / cell due to interference removal). Hereafter, the terms “positioning service continuity” and “positioning mobility” may be used interchangeably to refer to any procedure that may change / update the PRS configuration used in the WTRU and / or network based on mobility and / or non-mobility events / triggers / conditions. Furthermore, hereafter, the term “new PRS configuration” may also refer to “update to PRS configuration” in which an existing PRS configuration in the WTRU may be updated or replaced with a new / different PRS configuration, or which may contain at least partial overlap with the existing PRS configuration.

[0080] LMF is a non-limiting example of a node or entity (e.g., a network node or entity) that may be used for or to support positioning. Other types of nodes or entities may be used instead of LMF and may still be consistent with this disclosure.

[0081] In one embodiment, positioning service continuity may be performed by the WTRU independently of the data link HO. Alternatively, positioning service continuity may be performed with or during the data link HO. The WTRU may transmit requests for support information and / or configuration updates, which may include PRS configurations associated with adjacent cells / target cells. In this case, the WTRU may transmit requests to the network via the serving gNB when, for example, the RRC CONNECTED or RRC INACTIVE state.

[0082] Upon receiving a new PRS configuration from the network, the WTRU may use the new configuration to perform positioning measurements based on one or more positioning initiation triggers. Positioning initiation triggers, which indicate when to use the new PRS configuration and / or when to stop using the existing PRS configuration, may be received by the WTRU from the network (e.g., LMF and / or RAN entities and / or base stations). For example, the WTRU may receive positioning initiation triggers along with the new PRS configuration from the network, and / or may be pre-configured in the WTRU via other procedures (e.g., other LTE Positioning Protocol (LPP) procedures or location request procedures).

[0083] In one embodiment, the WTRU may send a request for a new PRS configuration before or during a conventional data link / RRC connection HO, so that the target cell's PRS configuration can be received and / or used for PRS measurement before the HO. In this case, the PRS configuration can be received by the WTRU from the serving / source gNB. This also allows for the possible minimization of latency associated with sending the request and receiving the new PRS configuration, avoiding any positioning gaps that would allow the WTRU to perform positioning measurements continuously during mobility without interruption. In another embodiment, the WTRU may send a request during and / or while a data link HO is running, and the new PRS configuration can be received from the target gNB.

[0084] In one scenario, the WTRU may send a request for a new PRS configuration in the case of inter-gNB mobility, where the source / serving TRP / gNB and the target TRP / gNB may be configured with different PRS configurations. In this case, the WTRU may initially be configured with a first PRS configuration when connected to the source / serving gNB. The first PRS configuration may be received by the WTRU either, for example, via support information from the LMF or via a System Information Block (SIB) from the source gNB. The WTRU may optionally be configured with a first measurement gap configuration by the serving gNB to perform DL PRS measurements. The WTRU may also be configured with a second measurement gap configuration to perform RRM measurements, which may include, for example, performing measurements on the CSI-RS, SSB, and / or adjacent cell beams. In this case, the first and second measurement gap configurations may span, for example, non-overlapping time / frequency resources or one or more overlapping time / frequency resources.

[0085] In another scenario related to intra-gNB mobility, where the source TRP and target TRP may be under the control of the same gNB, the WTRU may send a request for a new PRS configuration associated with the target TRP. The WTRU may send this request directly to the serving gNB via the source TRP, or to the LMF if the target TRP is not configured with the PRS configuration currently configured in the WTRU.

[0086] In both intra / inter-gNB mobility scenarios, the WTRU may detect the unavailability of a suitable PRS configuration and / or the use of a different PRS configuration in the target TRP / gNB / cell based on existing PRS configurations available in the WTRU. In this case, from the cell ID of the target / adjacent cell determined by the WTRU and the mapping of different cell IDs associated with existing PRS configurations in the supporting information, the WTRU may identify whether the target / adjacent cell uses the same or different PRS configuration.

[0087] In certain embodiments, a WTRU may support positioning service continuity procedures using LPP. For example, a WTRU configured with one or more PRS configurations (e.g., indicating PRS information, patterns, and / or parameters) for positioning may perform positioning service continuity during mobility (e.g., HO procedures and / or re-establishment procedures) when it supports at least one LPP session / procedure. A WTRU may be triggered to support an LPP session / procedure, for example, for WTRU-assisted positioning or for WTRU-based positioning, for or in connection with a deferred mobile incoming location request (MT-LR).

[0088] Typical steps for implementing positioning service continuity using LPP may include the following: (1) The WTRU transmits positioning capability information to the network (e.g., in particular network entities, base stations, LMFs, and / or gNBs) (for example, the WTRU may include capability information related to WTRU mobility, including, for example, information about any of the following: (i) WTRU speed / velocity, (ii) expected WTRU speed / velocity, (iii) WTRU direction of travel, (iv) expected direction of travel, and / or (v) the area in which the WTRU is expected to travel or roam (e.g., geographical area and / or area / cell ID)). When the WTRU transmits information to the network (e.g., in particular network entities, base stations, LMFs, and / or gNBs), for example, in an LPP message or Access Layer (AS) layer message (e.g., RRC signaling), it may include information regarding supporting positioning service continuity (e.g., requirements for supporting positioning measurement / reporting without interruption). Positioning capability information may be provided by the WTRU in an LPP capability provision message, for example. The WTRU may transmit positioning capability information, for example, after or upon receiving an LPP request capability message from the network (e.g., in the MT-LR scenario), or when it receives a location service request from an LCS client / application (e.g., in the MO-LR scenario). (2) The WTRU receives support information that indicates, encompasses, and / or includes one or more PRS configurations / parameters (for example, the WTRU may receive additional information associated with a PRS configuration, including either (i) validity conditions for using one or more PRS configurations (e.g., area / cell IDs on which the PRS configuration should be used), or (ii) mobility conditions that may or may need to be met for using a particular PRS configuration (e.g., speed and / or direction). The support information may be received in one or more messages (e.g., LPP support data transfer messages). The WTRU may receive support data / information indicating and / or including a positioning mobility configuration that encompasses and / or includes one or more rules / conditions. One or more rules and / or conditions may include (a) timing information, (b) cell ID information, and / or (3) for example, a PRS configuration associated with a source cell / gNB / base station. The WTRU may indicate / include one or more of the following: a PRS or an RSRP threshold for measurements made on a non-positioning RS / channel, which indicates when to release / stop and when to begin using a new PRS configuration associated with a target cell / gNB / base station during mobility. The WTRU may receive information indicating / includes a reporting configuration. The reporting configuration may indicate information including when the WTRU will transmit a positioning report, which will include a measurement report and / or a location estimate. For example, the reporting configuration may include / include any of the following: information about the cell ID to be reported, periodicity for transmitting positioning reports, and / or mobility information to be reported (e.g., among other things, WTRU speed, expected speed, direction, expected direction, environmental conditions, expected environmental conditions, indoor / outdoor conditions, expected indoor / outdoor conditions). (3) The WTRU receives a request for location information from the network (e.g., a network entity, base station, gNB, and / or LMF) (e.g., the request may indicate to initiate a positioning measurement (e.g., in a message, e.g., an LPP request location information message)). Upon or after receiving the request, the WTRU may use at least one PRS configuration that satisfies the associated validity conditions to perform the measurement on the PRS. When the WTRU is connected to a source base station / gNB, the WTRU may use, for example, the PRS configuration associated with the source base station / gNB. When or during a HO to a target base station / gNB (e.g., for a data link HO) which may be associated with a different PRS configuration, the WTRU may use, for example, the PRS configuration associated with the target gNB. When the WTRU determines that the PRS configuration associated with the target gNB is unavailable (for example, due to the PRS configuration not being (i) pre-configured in the WTRU, (ii) not provided to the WTRU in LPP support data, and / or (iii) not accessible via posIB), the WTRU may send an indication to the network (e.g., in particular base stations, network entities, LMFs and / or gNBs) to request a new PRS configuration (e.g., in an LPP request support data message), for example, to indicate the identifier / ID of the target base station / gNB. When the WTRU determines that the PRS configuration associated with the target base station / gNB is available (e.g., pre-configured, provided via support data, and / or accessible via posIB), the WTRU may send information or an indication to the network (e.g., in particular base stations, network entities, LMFs and / or gNBs) to indicate a change in the PRS configuration from the one associated with the source base station / gNB to the one associated with the target base station / gNB.WTRUs may transmit information or indications in LPP messages (e.g., in particular LPP location information messages and / or LPP support information provision / request messages) and / or Access Layer (AS) layer messages (e.g., via RRC signaling, Media Access Control (MAC) control elements (CE) and / or uplink control information (UCI)). (4) The WTRU performs PRS measurements using an appropriate PRS configuration before, during, and / or after HO (for example, when supporting WTRU-assisted positioning, the WTRU may send measurement reports to the network (e.g., in particular base stations, network entities, LMFs, and / or serving gNBs)). The WTRU may send measurements to the LMF via LPP location information messages, which may include or indicate information about WTRU mobility (e.g., in particular, the time instance when receiving the HO command, the time instance when sending the HO complete message, and / or the time instance when changing to a different PRS configuration during mobility). When supporting WTRU-based positioning, the WTRU may determine its location estimate based on PRS measurements. When supporting MT-LR and / or delayed MT-LR, the WTRU may, for example, send location estimates to the LMF via location information messages, which may include information about WTRU mobility. When supporting Mobile Outgoing Location Request (MO-LR), the WTRU may send location estimates to, for example, Application / Location Services (LCS) - Client / Application.

[0089] The content of a request submitted by a WTRU for a new PRS configuration may include various types of information. For example, the request may include information about the target TRP / gNB, such as the cell ID. Alternatively or additionally, the request may include information about measurements of the target / adjacent TRP / gNB, such as the RSRP measured by RRM measurements (e.g., SSB, CSI-RS) and PRS measurements. Alternatively or additionally, the request may include information about the PRS configuration, such as flags and / or identifiers indicating an existing / new PRS configuration. Alternatively or additionally, the request may include information about mobility, such as a mobility report including a mobility route (e.g., a list of one or more cell IDs traversed by the WTRU and / or WTRU coordinates over a period of time) and / or WTRU mobility attributes (e.g., WTRU speed, direction, distance traveled by direct / straight-line route).

[0090] A WTRU may transmit requests for new PRS configurations and / or updates / modifications to existing PRS configurations in a variety of ways. For example, a WTRU may transmit a request in a NAS message using at least one of the LPP procedures for transmitting support information and / or requests for configuration updates to an LMF. Alternatively, a WTRU may include a request in positioning information transmitted to the network, including positioning measurement reports and / or location information. Another alternative is for a WTRU to transmit a request in a positioning mobility report, which may include mobility information. Alternatively or additionally, a WTRU may transmit a request using RRC signaling, such as by sending a request for a new PRS configuration to a TRP / gNB in ​​the RAN, which may be associated with a serving / source or target cell. Alternatively or additionally, a WTRU may transmit a request using Layer 2 / Layer 1 (L2 / L1) signaling, such as by sending a request in a MAC control element (CE) or uplink control information (UCI) to a serving gNB.

[0091] In one solution, the WTRU may be configured by the network using a positioning service continuity configuration, which may include one or more positioning service continuity conditions and / or configurations to support at least one positioning service continuity mode. In this case, both the positioning service continuity conditions and positioning service continuity modes may be configured in the WTRU by either the LMF or the RAN (e.g., serving gNB via RRC). Alternatively, for example, the positioning service continuity conditions may be configured by the LMF and the positioning service continuity modes may be configured by the RAN.

[0092] Using a positioning service continuity configuration to enable service continuity and / or mobility support can be supported for both WTRU-based positioning and WTRU-assisted positioning. In the case of WTRU-based positioning, the WTRU may receive appropriate support information / configuration updates and PRS configurations in a timely manner (e.g., before / during data link HO) based on WTRU mobility, so that the WTRU can perform PRS measurements and determine its location information. Similarly, in the case of WTRU-assisted positioning, the WTRU may perform PRS measurements using the PRS configuration received during mobility and transmit measurement reports via a serving gNB. In both WTRU-based and WTRU-assisted positioning, the new PRS configuration may consist of one or more TRPs / gNBs, for example, one or more TRPs / gNBs that may be using a PRS similar to the PRS of the target TRP / gNB from which the WTRU receives the data link HO. In addition, positioning mobility may also be supported for example, mobile outgoing location request (MO-LR) and mobile incoming location request (MT-LR) procedures associated with WTRU-based and WTRU-assisted positioning.

[0093] Positioning service continuity conditions configured in and / or monitored by the WTRU may include requirements that the WTRU send a request for a new PRS configuration to the network (e.g., LMF and / or RAN entities and / or base stations) or update / modify an existing PRS configuration when triggered by one or more conditions. For example, conditions that can trigger the sending of a request may include the unavailability of a suitable PRS configuration. For example, the WTRU may send a request if it determines that one or more target / neighboring cells (e.g., cell IDs) that can be detected by the WTRU from the SIB / SSB received from a target / neighboring cell are not currently in the available support information / configurations and / or existing PRS configurations in the WTRU. Similarly, the WTRU may send a request for a new PRS configuration if it is able to receive, or can receive, at least a portion of, a PRS from a target cell and does not have an associated PRS configuration.

[0094] Another condition that can trigger the transmission of a request may include one or more RRM measurement thresholds. For example, a WTRU may request a new PRS configuration when an RRM measurement associated with a target / adjacent cell (e.g., RSRP, CSI-RS for an SSB) exceeds a configured threshold and / or remains above the threshold for a specific configured period. The threshold for sending a request for a new PRS configuration based on an RRM measurement may be lower / higher than, for example, the threshold configured for conventional data link HO. In another embodiment, the thresholds for positioning service continuity and data link HO may be the same. In this case, the WTRU may include a positioning service continuity flag / indication in the RRM measurement report sent to the serving gNB for data link HO, for example. The serving gNB may, for example, when performing an HO procedure, forward the request for a new PRS configuration to the LMF (e.g., via a new radio positioning protocol A (NRPPa)) or to the target gNB (e.g., via Xn).

[0095] Another condition that can trigger the sending of a request may include timers associated with one or more existing PRS configurations. For example, a WTRU may send a request when an active timer associated with one or more of the existing PRS configurations expires.

[0096] Another condition that can trigger the sending of a request may include indications from the network / upper layer. For example, a WTRU may send a request for a new PRS configuration when it receives an indication from a serving gNB indicating the release of an existing PRS configuration and / or measurement gap configuration for PRS measurement. Similarly, a WTRU may send a request when triggered by an Application / Location Services (LCS) client within the WTRU (e.g., MO-LR).

[0097] Other conditions that can trigger the transmission of a request may include changes in the WTRU radio environment or WTRU attributes. For example, a WTRU may transmit a request for a new PRS configuration when it detects certain attributes in the WTRU radio environment, including interference and / or multipath (e.g., measurements above / below a threshold).

[0098] Another condition that can trigger the sending of a request may include a change in WTRU attributes. For example, a WTRU may send a request for a new PRS configuration when it detects a change in WTRU attributes. An example of a WTRU attribute is an increase / decrease in WTRU velocity in a particular direction (e.g., a direction away from the coverage area of ​​one or more TRP / gNBs in which the existing PRS configuration is used). Another example of a WTRU attribute is a change in WTRU orientation (e.g., in the opposite direction to the direction in which the beam associated with the existing PRS configuration is received). Another example of a WTRU attribute is the change in distance traveled by a WTRU by a specific distance threshold (e.g., along a straight / direct path). A WTRU may send a request in response to one or more of these or other conditions being met.

[0099] Other conditions that can trigger the transmission of a request may include data link HO triggers. For example, a WTRU may transmit a request for a new PRS when triggered by one or more conditions / signaling associated with a data link HO procedure. Exemplary data link HO triggers include the transmission of an RRM measurement report from a serving gNB and / or the reception of a radio resource control (RRC) reconfiguration message (including an HO command), and the transmission of a connection establishment message to a target gNB (e.g., Random Access Control Channel (RACH), RRC signaling).

[0100] In one embodiment, the WTRU may be configured to transmit positioning information (e.g., measurement reports for WTRU-assisted positioning and / or location information for the WTRU base) to the LMF when triggered by one or more positioning service continuity conditions described above. The WTRU may transmit the positioning information via the serving gNB before / during data link HO. In this case, the LMF may decide to provide a new PRS configuration based on the positioning information transmitted by the WTRU, and if it configures the new PRS configuration in one or more target TRP / gNBs, it may transmit support information / configuration updates including the new / updated PRS configuration to the WTRU. In one embodiment, the positioning information transmitted by the WTRU based on the above trigger conditions may include a positioning service continuity report.

[0101] In another embodiment, one or more PRS configurations may be pre-configured in the WTRU, along with a mapping to PRS configurations potentially associated with positioning service continuity conditions. Different PRS preconfigurations may also be associated with one or more groups of TRP / gNBs (e.g., TRP / gNB IDs). In this case, the WTRU may select a new PRS configuration from the list of preconfigurations and / or release an existing PRS configuration when it detects one or more positioning service continuity conditions. The selected new PRS configuration may then be used, for example, to request an associated measurement gap configuration and / or to perform a PRS measurement.

[0102] In addition, the positioning service continuity configuration received by the WTRU may also include various positioning service continuity modes. For example, a positioning service continuity mode included in the configuration may indicate the use of a new PRS configuration of the target gNB prior to data link HO while within the coverage area of ​​the source gNB. Alternatively or additionally, a positioning service continuity mode included in the configuration may indicate the use of an existing PRS configuration of the source gNB after data link HO while within the coverage area of ​​the target gNB. Alternatively or additionally, a positioning service continuity mode included in the configuration may indicate the use of PRS configurations of both the source gNB and the target gNB during data link HO.

[0103] The WTRU may use one or more positioning service continuity modes, which are determined autonomously by the WTRU based on indications received from the network (e.g., the same or different indications including a new PRS configuration) or triggers similar to the positioning service continuity conditions described above.

[0104] The WTRU may receive one or more RAN configurations (e.g., RAN configuration information) associated with positioning to be applied during mobility. For example, the WTRU may receive a RAN configuration (e.g., RAN configuration information) from a serving gNB (e.g., source base station / gNB) or a target base station / gNB, which may be applied by the WTRU before, during, and / or after HO while continuing to support the positioning procedure. The RAN configurations described herein may include any of the following attributes / parameters / information and may be applicable to the various embodiments disclosed herein. (1) One or more measurement gap (MG) configurations (for example, WTRU may be configured using a first MG configuration when using a first PRS configuration associated with a source base station / gNB / cell (e.g., before and / or during HO), and / or using a second MG configuration when using a second PRS configuration associated with a target base station / gNB / cell (e.g., during and / or after HO)). (2) For the purpose of transmitting measurements, reports, and / or location estimations in accordance with one or more configured authorization (CG) configurations (e.g., associated PRS measurement and / or reporting configurations), a WTRU may be configured using a first CG configuration when associated with a source gNB / cell (e.g., before and / or during HO), and may be configured using a second CG configuration when associated with a target gNB / cell (e.g., during and / or after HO). In another embodiment, a WTRU configured by a source gNB / cell using a CG configuration may continue to use the same or updated CG configuration during or receiving an HO when it receives an indication from the source gNB / cell or target gNB / cell that the WTRU may be authorized to use the CG configuration. (3) Timing Advance (TA) Configuration (For example, to support UL-based positioning, the WTRU may be configured using a first TA configuration including a TA timer (TAT) (e.g., timer parameters / information) when using a first SRSp configuration associated with a source gNB / cell (e.g., before and / or during HO), and may be configured using a second TA configuration when using a second SRSp configuration associated with a target gNB / cell (e.g., during and / or after HO). The WTRU may use the first SRSp configuration on the condition, or to the extent that, the TAT associated with the first TA configuration is valid (e.g., the conditions for the TA configuration are valid and / or the time interval associated with that TAT has not expired), and the WTRU may use the second TA configuration when the TAT associated with the second TA configuration is valid (e.g., the conditions for the TA configuration are valid and / or the time interval associated with that TAT has not expired). A second SRSp configuration may be used, provided that the specified time interval has not expired. The first and second TA configurations may be received by the WTRU, for example, from a source gNB / cell and / or a target gNB / cell. In some embodiments, a TA configuration (e.g., using a TAT) may be associated with a CG configuration and / or a PRS configuration. The WTRU may use one or more TA configurations provided by the source / target gNB / cell when determining which of the one or more CG configurations should be used during mobility and / or when performing positioning measurements / reports. For example, the WTRU may use a first CG configuration, provided that the TAT associated with the first TA configuration is valid, or as long as it is valid, and may use a second CG configuration, provided that the TAT associated with the second TA configuration is valid, or as long as it is valid.

[0105] In some situations, the WTRU may send a request to the serving gNB for a new PRS configuration to support positioning mobility. For example, if LMF functionality can be supported in the RAN, the WTRU may send a request to the serving gNB to support positioning service continuity (e.g., a request for a new PRS configuration) based on the detection of one or more configured positioning service continuity conditions.

[0106] The WTRU may transmit a request for positioning service continuity in RRC signaling, UL MAC CE, and / or UCI either before or during data link HO. The serving gNB may then transmit a request for a new PRS configuration associated with one or more target cells / gNBs to the LMF and / or directly to the target cells / gNBs. The LMF or target cells / gNBs may forward the associated PRS configurations to the serving gNBs to support positioning mobility / service continuity. The WTRU may receive an indication from the serving gNBs to use / activate the new PRS configurations and / or (new) PRS (pre-)configurations via RRC signaling, DL MAC CE, and / or Downlink Control Information (DCI). The new PRS configurations may be received by the WTRU before or during data link HO in an RRCReconfiguration message (e.g., with an HO command) or in a different message. Next, the WTRU may perform DL-PRS measurements using the newly received / activated PRS configuration and send the measurement report to the current serving gNB.

[0107] In some situations, a WTRU may receive a new / updated PRS configuration when it transmits a positioning service continuity report. For example, a WTRU may receive a new / updated PRS configuration from the network (e.g., LMF and / or RAN entities and / or base stations) based on a positioning service continuity report transmitted by the WTRU. For example, a WTRU may indicate in its positioning service continuity report the ID of a target / neighboring cell and / or information related to RRM measurements associated with a target / neighboring cell, regardless of whether the target cell / gNB uses the same or a different PRS configuration available in the WTRU. A WTRU may transmit in its positioning service continuity report information related to WTRU mobility attributes such as speed, direction, and / or orientation. In another embodiment, a WTRU may transmit mobility status indications to the network in an LPP measurement report or in a separate positioning mobility report. A WTRU may transmit a positioning service continuity report when triggered by one or more of the trigger conditions described above.

[0108] Positioning service continuity reports may be transmitted via the serving gNB periodically or based on one or more of the conditions described above (e.g., when the RSRP of an adjacent cell exceeds a threshold, or when triggered by a data link HO). For example, a WTRU may increase the transmission periodicity for positioning service continuity reports when its WTRU speed increases in order to provide the network with a more accurate assessment of its WTRU location. A WTRU may change from a first reporting periodicity to a second reporting periodicity, for example, when it receives a data link HO, and the second periodicity may be higher than the first periodicity. In another embodiment, the WTRU may consist of a group of one or more TRP / gNBs associated with PRS configurations available in the WTRU. The WTRU may also be configured with markers associated with one or more TRP / gNBs, indicating that the WTRU will send a positioning continuity report to the network when the WTRU detects the ID of a TRP / gNB that has a marker.

[0109] In response to sending a positioning service continuity report, the WTRU may receive a new / updated PRS configuration, along with information on when to begin using the new PRS configuration and when to stop / release the use of the existing PRS configuration. The new / updated PRS configuration may be received before and / or independently of the data HO procedure. Reception may be based on the determination of the WTRU's location within the positioning area (e.g., the area associated with a group of TRP / gNBs to which the existing PRS configuration is applied and which can be used by the WTRU for positioning measurements). Reception may also be based on coordination between the TRP / gNB and the LMF. The WTRU may periodically receive a new / updated PRS configuration, for example, when the WTRU receives an HO to a different cell.

[0110] Resources for transmitting positioning information to the network, including at least positioning service continuity reports and / or measurement reports, may be received by the WTRU from the serving gNB. These resources may be received as dynamic or configured authorizations based on requests for resources transmitted by the WTRU (e.g., scheduling requests (SRs) / buffer status reports (BSRs) or RRC support information). In one embodiment, the WTRU may send a request for a configured authorization to a serving cell to transmit positioning information. The WTRU may also indicate the use of a configured authorization during / after a HO to transmit positioning information, including measurements taken during the HO. In this case, the serving gNB may transfer the context associated with the configured authorization to the target gNB and indicate to the WTRU the specific conditions for using the configured authorization. For example, the WTRU may use the same configured authorization at the time of HO to the target gNB, at least for the initial transmission and / or possibly within a specific validity period.

[0111] In an alternative solution, when the WTRU receives a data link HO to the target cell, the target cell may be in an existing PRS configuration available in the WTRU, and the LMF may receive an indication of the WTRU's mobility status from the RAN. Based on the mobility status, the LMF may send an update to the WTRU that includes an updated PRS configuration. In this case, the updated PRS configuration may include information about one or more new TRP / gNBs that the WTRU can use for PRS measurements.

[0112] The updated PRS configuration received by the WTRU may also include information relating to TRP / gNBs of higher importance / priority to the WTRU, for example, to perform PRS measurements and improve positioning accuracy. In one embodiment, when the WTRU receives an HO from a source cell to a target cell, the importance of the source cell in the updated PRS configuration switches from a higher value to a lower value because the previous source cell becomes an adjacent cell after the HO.

[0113] The updated PRS configuration may be received by the WTRU either periodically or based on its mobility status. For example, the updated PRS configuration may be received more frequently and with greater periodicity when the WTRU is moving at a faster speed or when the rate of HOs to one or more target cells is high.

[0114] In some situations, a WTRU uses the target gNB's PRS configuration before HO in the source gNB's coverage area. For example, a WTRU configured with a new PRS configuration associated with a target TRP / gNB may use the new PRS configuration when it is still connected to the source TRP / gNB via a data / RRC link. In this case, the target TRP / gNB's new PRS configuration may be used by the WTRU to perform positioning measurements when it is within the source TRP / gNB's coverage area before data link HO. When using a new PRS configuration, the WTRU may, in some cases, extend, release, and / or suspend its existing PRS configuration, for example, when the WTRU is under the coverage of the source TRP / gNB.

[0115] A WTRU may initiate the use of a new PRS configuration based on various PRS usage triggers configured within the WTRU. An exemplary trigger for initiating the use of a new PRS configuration may include the reception of the new PRS configuration. In this embodiment, the WTRU may use the new PRS configuration immediately or within a specific configured period. In this case, the WTRU may, for example, start a timer upon reception and use the new PRS configuration when the timer expires.

[0116] Another exemplary trigger for initiating the use of a new PRS configuration may include RRM / PRS measurements of the target cell. For example, WTRU may use a new PRS configuration when the RSRP of the SSB and / or neighboring cell RS exceeds a threshold and / or remains above the threshold for the configured period. Similarly, WTRU may initiate the use of a new PRS configuration when the RSRP measurement of the PRS received from the target cell exceeds a threshold.

[0117] Another exemplary trigger for initiating the use of the new PRS configuration could involve target cell ID detection. For example, a WTRU might use the new configuration when it detects the target cell ID in the SIB / SSB received from the target cell.

[0118] Another exemplary trigger for initiating the use of a new PRS configuration may include receiving an indication from the network. For example, a WTRU may initiate the use of a new PRS configuration when it receives an indication from the LMF (e.g., in an LPP location request) or from the RAN (e.g., in a MAC CE or DCI).

[0119] Another exemplary trigger for initiating the use of a new PRS configuration could include priority. For example, a new PRS configuration may be used when the priority associated with the new PRS configuration is higher than or equal to that of an existing PRS configuration or other data transmission / reception.

[0120] Another exemplary trigger for initiating the use of a new PRS configuration may include data / signaling transmissions. For example, a WTRU may initiate the use of a new PRS configuration upon completion of data / signaling transmissions / receptions on a dedicated resource bearer / signaling resource bearer (DRB / SRB). Alternatively or additionally, a WTRU may initiate the use of a new PRS configuration when it determines that there are no buffered or pending data / signaling transmissions / receptions within a subsequent configured period / slot.

[0121] Another exemplary trigger for initiating the use of a new PRS configuration may include a data link HO trigger. For example, a WTRU may use a new PRS configuration either before or after sending an RRM measurement report containing adjacent cell measurements, potentially triggering a data link HO. Alternatively, a WTRU may initiate the use of a new PRS configuration upon receiving an HO command, which may contain an explicit or implicit indication to initiate the use of the new PRS configuration.

[0122] Another exemplary trigger for initiating the use of a new PRS configuration may include alignment with the measurement gap configuration. For example, a WTRU may use a new PRS configuration if it sends a request (e.g., in the RRC) for the measurement gap or reception of the measurement gap configuration associated with the new PRS configuration of a target TRP / gNB / cell. In this case, the request and / or response for the measurement gap configuration may be performed by the WTRU via the serving TRP / gNB.

[0123] When using a new PRS configuration, the WTRU may extend, deactivate, and / or release the existing PRS configuration, or continue to use the new PRS configuration and the existing PRS configuration with at least one overlap of time / frequency resources used for the PRS. Possible combinations of using the new and existing PRS configurations may be received by the WTRU in support information / configuration updates from the network, or may be determined by the WTRU. For example, the WTRU may decide to use a new PRS configuration together with an existing PRS configuration with at least one overlap of time / frequency resources between the configurations in order to improve positioning accuracy. In this case, the WTRU may use one or more combinations of PRS configurations when it determines that the positioning accuracy achieved by measurements using the existing PRS configuration is below an accuracy threshold, for example, due to interference or fluctuations in the WTRU radio environment.

[0124] Figure 2 is a system diagram showing a WTRU that receives a downlink (DL) positioning reference signal (PRS) from a target TRP / gNB while connected to a source TRP / gNB, according to one embodiment.

[0125] Referring to Figure 2, the first coverage area 208 associated with source TRP / gNB202 may overlap with the second coverage area 206 associated with target TRP / gNB204. WTRU200 may use the PRS configuration of source TRP / gNB204 after HO in the coverage area 206 of target TRP / gNB202. For example, WTRU200 configured with the new PRS configuration associated with target TRP / gNB202 may continue to use the existing PRS configuration associated with source TRP / gNB202 after performing a data link HO to target TRP / gNB204 and / or after establishing a data / RRC connection with target TRP / gNB204. In this case, the PRS configuration of source TRP / gNB202 may be used by WTRU200 to perform positioning measurements while within the coverage area 206 of target TRP / gNB204 after the data link HO.

[0126] WTRU200 may release / update existing PRS configurations associated with source TRP / gNB202 based on various trigger conditions configured in WTRU200. One exemplary trigger condition for releasing / updating existing PRS configurations may include the reception of a new PRS configuration. For example, WTRU200 may release / update existing PRS configurations when it receives a new PRS configuration for target TRP / gNB204 from target TRP / gNB204.

[0127] Another exemplary trigger condition for releasing / updating an existing PRS configuration may include a source cell RRM / PRS measurement. For example, WTRU200 may release / update an existing PRS configuration when the RSRP of the SSB and / or source cell RS falls below a threshold and / or remains below the threshold for the configured duration. Similarly, WTRU200 may release / update an existing PRS configuration when the RSRP measurement of the PRS received from the source cell falls below a threshold.

[0128] Another exemplary trigger condition for releasing / updating an existing PRS configuration may include receiving an indication from the network. For example, WTRU200 may release / update an existing PRS configuration and begin using a new PRS configuration upon receiving an indication from the LMF (e.g., in an LPP location request) or from the RAN (e.g., in a MAC CE or DCI).

[0129] Another exemplary trigger condition for releasing / updating an existing PRS configuration may include timer expiration. For example, WTRU200 may release / update an existing PRS configuration within a specific period while a data link HO to a target cell is running. In this case, WTRU200 may start a timer when it receives an HO command / RRCReconfiguration message from source TRP / gNB202 or when it sends a RACH / Radio Resource Control (RRC) message to target TRP / gNB204 for connection establishment. Subsequently, the WTRU200 may release / update the existing PRS configuration when the configured timer expires.

[0130] Another exemplary trigger condition for releasing / updating an existing PRS configuration may include priority. For example, an existing PRS configuration may be released / updated when the priority associated with the new PRS configuration is higher than or equal to that of the existing PRS configuration or other data send / receiver.

[0131] Another exemplary trigger condition for releasing / updating an existing PRS configuration may include data / signaling transmissions. For example, the WTRU200 may release / update an existing PRS configuration upon completion of data / signaling transmission / reception via the DRB / SRB, and / or when it determines that there are no buffered or pending data / signaling transmissions / receptions for the subsequent configured duration when connected to the target TRP / gNB204.

[0132] Another exemplary trigger condition for releasing / updating an existing PRS configuration may include a data link HO trigger. For example, WTRU200 may release / update an existing PRS configuration before or after sending an RRM measurement report that includes an adjacent cell measurement to trigger a data link HO. Alternatively, WTRU200 may release / update an existing PRS configuration upon receiving an HO command, which may optionally include an explicit or implicit indication for releasing an existing PRS configuration.

[0133] Another exemplary trigger condition for releasing / updating an existing PRS configuration may include alignment with the measurement gap configuration. For example, WTRU200 may release / update an existing PRS configuration when it sends a request (e.g., in RRC) for the measurement gap or reception of the measurement gap configuration associated with the new PRS configuration of the target TRP / gNB / cell. In this case, the request and / or response regarding the measurement gap configuration may be performed by WTRU200 via, for example, the target TRP / gNB204.

[0134] Another exemplary trigger condition for releasing / updating an existing PRS configuration may include return / failure conditions. For example, after receiving a new PRS configuration, the WTRU200 may revert to using the existing PRS configuration without releasing it if the new PRS configuration fails to meet certain positioning accuracy conditions (e.g., RSRP for PRS measured below a threshold) or due to other failure conditions related to the new PRS configuration. The WTRU200 may also revert to the existing PRS configuration if, for example, it fails to receive the measurement gap configuration associated with the PRS configuration of the target TRP / gNB204.

[0135] When an existing PRS configuration is released / updated, WTRU200 may begin using the new PRS configuration to perform positioning measurements in the coverage area 206 of the target TRP / gNB204. WTRU200 may use the new PRS configuration, for example, when it transmits and / or receives the new PRS configuration of the target TRP / gNB204 and the associated / matched measurement gap configuration.

[0136] In an example where the same PRS configuration is used by both source TRP / gNB202 and target TRP / gNB204, WTRU200 can continue using the existing PRS configuration after HO without releasing or updating the configuration. In this case, WTRU200 may receive an indication from source TRP / gNB202 (e.g., within an HO command) to pause performing measurements using the existing measurement gap configuration during HO and / or resume performing measurements using the same measurement gap configuration after HO. In this case, during HO execution, WTRU200 can either explicitly indicate to target TRP / gNB204 the use of the existing measurement gap configuration (e.g., in a RACH message, RRC signaling, MAC CE, and / or UCI) or implicitly indicate by resuming measurements using the existing measurement gap configuration.

[0137] Figure 3 is a system diagram showing a WTRU receiving DL-PRS from a source gNB while connected to a target gNB.

[0138] Referring to Figure 3, the first coverage area 308 associated with source TRP / gNB302 may overlap with the second coverage area 306 associated with target TRP / gNB204. During data link HO, WTRU300 may use the PRS configuration of source TRP / gNB302 and the PRS configuration of target TRP / gNB304. For example, a WTRU300 configured with an existing PRS configuration associated with source TRP / gNB302, along with a new PRS configuration associated with target TRP / gNB304, may use both PRS configurations during data link HO. The use of both PRS configurations may be intended to improve, for example, the accuracy and reliability of positioning measurements.

[0139] In this case, WTRU300 may use both PRS configurations to perform positioning measurements based on PRS received from both source TRP / gNB302 and target TRP / gNB304. To use both PRS configurations, WTRU300 may start using the new PRS configuration while continuing to use the existing PRS configuration before HO. In this case, WTRU300 may send a request to the serving gNB to extend / modify the existing measurement gap configuration so that the updated measurement gap configuration spans both the existing and new PRS configurations, for example.

[0140] WTRU300 may temporarily suspend measurements using the extended measurement gap configuration for a specific period during a data link HO, for example, to support one or more signaling / functions associated with the HO. Upon completion of the HO, WTRU300 may resume measurements using the extended measurement gap configuration until conditions for releasing / updating the PRS configuration of the source TRP / gNB302 are met (e.g., the RSRP of the PRS falls below a threshold). In this case, after releasing / updating the PRS configuration of the source TRP / gNB302, WTRU300 may revert to using the new PRS configuration of the target TRP / gNB304, possibly along with the associated reduced / updated measurement gap configuration. WTRU300 may transition from using the extended measurement gap configuration to the reduced / updated measurement gap configuration based on sending an explicit request to the target gNB to change the measurement gap configuration, or implicitly by using a measurement gap configuration aligned with the new PRS configuration.

[0141] Figure 4 is a system diagram showing a WTRU that receives DL-PRS from a source gNB and a target gNB during HO, according to one embodiment.

[0142] Referring to Figure 4, the first coverage area 408 associated with source TRP / gNB402 may overlap with the second coverage area 406 associated with target TRP / gNB404. WTRU400 may determine the use of a PRS configuration based on the measurement gap configuration. For example, in an implementation where a measurement gap configuration is applied to perform a PRS measurement, WTRU400 may send a request to the serving gNB requesting configuration / configuration information for the measurement gap associated with a new PRS configuration of one or more target gNBs / cells. In this case, the request for the measurement gap configuration may be transmitted in RRC signaling, MAC CE, and / or UCI upon receipt of the new PRS configuration. The determination of the size / length of the measurement gap configuration (e.g., in the time domain and / or frequency domain) may be based, for example, on new and / or existing PRS configurations. WTRU400 may perform a positioning measurement using either an existing or new PRS configuration, for example, when WTRU400 is configured with a suitable and effective measurement gap configuration.

[0143] In one embodiment, the WTRU400, which may be configured with a measurement gap configuration for performing measurements using an existing PRS configuration, may suspend performing measurements using the measurement gap configuration according to a new PRS configuration. In this case, the WTRU may perform various operations. For example, WTRU400 may perform an action that involves suspending / releasing a measurement gap configuration associated with an existing PRS configuration. In this case, WTRU400 may be configured by the network using rules to determine how / when to suspend / release the existing measurement gap configuration. Hereinafter, suspending / releasing a measurement gap configuration may mean that WTRU400 suspends / stops using the measurement gap configuration to perform PRS measurements. In one embodiment, suspending / releasing a measurement gap configuration may correspond to updating the measurement gap configuration. WTRU400 may suspend / release a measurement gap configuration when, for example, one or more conditions associated with using the PRS configuration are met. WTRU400 may, for example, send a request for a new measurement gap configuration to the network when suspending / releasing an existing measurement gap configuration. When WTRU400 suspends an existing measurement gap configuration without releasing it, WTRU400 may, for example, return to using the measurement gap configuration to perform PRS measurements when it sends a request for a new measurement gap.

[0144] Another operation that the WTRU400 may perform involves dynamically updating the measurement gap. For example, the WTRU400 may dynamically update the measurement gap configuration when it receives a new PRS configuration and / or determines an updated measurement gap configuration. In this case, the updated measurement gap configuration may be a new measurement gap configuration that does not include any overlapping time / frequency resources that overlap with the measurement gap time / frequency resources of the previous configuration. For example, the WTRU400 may determine a new measurement gap configuration based on a newly received PRS configuration. Alternatively, the updated measurement gap configuration may include one or more overlapping time / frequency resources or may extend the existing measurement gap configuration. The WTRU400 may send an indication to the network showing the updated measurement gap configuration (e.g., a delta change from the existing measurement gap configuration).

[0145] In one embodiment, a request to suspend / release / update an existing measurement gap configuration may be explicitly sent in the same request to configure a new measurement gap configuration. In this case, the response received by WTRU400 may include commands to suspend / release / update the configurations of the existing and new measurement gaps. In another embodiment, a request to suspend / release an existing measurement gap is implicitly indicated through the request for a new measurement gap configuration. Alternatively, requests and responses to suspend / release / update the existing and new measurement gap configurations may be made via separate signaling.

[0146] In another embodiment, WTRU400 may begin using a new measurement gap configuration upon receiving a response from the network (e.g., source TRP / gNB402 or target TRP / gNB404) containing information about the measurement gap configuration (e.g., the ID of the time / frequency resource or measurement gap associated with the measurement). WTRU400 may cease using an existing measurement gap configuration after sending a request or upon receiving a new measurement gap configuration from the network. Alternatively, WTRU400 may cease using an existing measurement gap configuration upon the expiration of a configured timer, which may be set after sending a request or after receiving a network response containing a new measurement gap configuration.

[0147] In another embodiment, WTRU400 configured with a measurement gap configuration associated with the PRS configuration of target TRP / gNB402 may perform a measurement of the PRS received from target TRP / gNB404 when WTRU400 is under coverage of source TRP / gNB404. In another embodiment, WTRU400 may use a measurement gap configuration associated with the existing PRS configuration of source TRP / gNB404 to measure the PRS received from source TRP / gNB402 after HO when WTRU400 is under coverage of target TRP / gNB402.

[0148] In another embodiment, the WTRU400 may suspend / release a measurement gap configuration, including a measurement gap associated with an existing and / or new PRS configuration, to ensure that signaling / functions associated with the data link HO can be supported during the HO. In this case, the data link HO signaling / functions may include sending RRM measurement reports, receiving RRC reconfiguration messages / HO commands, receiving synchronization signals from the target cell (e.g., primary synchronization signal (PSS), secondary synchronization signal (SSS)), and / or sending connection establishment messages (e.g., RACH / RRC signaling). In one embodiment, when configured with a measurement gap associated with a new PRS configuration, the WTRU400 may suspend the measurement gap configuration and perform measurements on the PRS received from the target cell to support the HO signaling / functions during the HO. In another embodiment, the WTRU400 may suspend / release a measurement gap configuration associated with an existing PRS configuration and perform measurements on the PRS received from the source cell to support the signaling / functions during the HO. Upon completion of HO signaling, the WTRU400 may then resume the suspended measurement gap configuration to perform PRS measurements. The WTRU400 may continue to use the measurement gap configuration after HO until one or more release conditions associated with releasing the measurement gap configuration (e.g., a trigger, timer expiration, and / or network indication for using a new PRS configuration) are met.

[0149] In another embodiment, the WTRU400 may be configured with one or more priority rules for using a measurement gap configuration when the measurement gap configuration overlaps with a signaling / function associated with the HO. For example, the priority rule may indicate that when the WTRU400 is sending an RRM measurement report to the serving gNB in ​​the RRC signaling, the measurement gap configuration associated with the positioning measurement may be suspended / released due to the RRC signaling being assigned a higher priority than the positioning measurement. When a higher priority is assigned to the positioning measurement, the WTRU400 may resume the positioning measurement using the measurement gap configured, for example, when the RRC signaling is sent or after receiving an RRCReconfiguration message containing an HO command from the serving gNB. In this case, different HO-related signalings / functions may be associated with different priority values, and the WTRU400 may support one or more of the signalings / functions, for example, that include priority-based positioning measurements and reports.

[0150] In another embodiment, a priority rule configured in WTRU400 may indicate that WTRU400 should not interrupt / release the measurement gap configuration associated with positioning measurements when WTRU400 is triggered by one or more data link signaling / functions associated with HO. In this case, when the signaling / functions associated with data link HO are performed on an active bandwidth portion (BWP) which may overlap / not overlap with the bandwidth / resources associated with PRS measurements, WTRU400 may, for example, continue to transmit / receive HO-related signaling during HO while continuing to perform PRS measurements using the configured measurement gap configuration. Upon completion of the HO procedure (e.g., when WTRU400 establishes connectivity with the target TRP / gNB404), WTRU400 may, for example, return to performing PRS measurements using the configured measurement gap configuration (e.g., simply perform them). In this embodiment, skipping a rule to perform either PRS measurements or transmit / receive data / signaling via the active BWP may, for example, ensure that positioning accuracy is maintained and avoid any positioning gaps.

[0151] To reduce the latency associated with signaling / procedures for configuring measurement gap configurations, the WTRU400 may be pre-configured with one or more measurement gap configurations by the source gNB. Measurement gap pre-configurations may be associated with existing and / or new PRS configurations. The WTRU400 may trigger the activation of pre-configured measurement gaps during HO by sending an indication (e.g., an identifier) ​​regarding the measurement gap to the target TRP / gNB404 in RACH messages and / or RRC signaling. In this case, for different measurement gap pre-configurations, the WTRU400 may be configured by the serving gNB using one or more RACH resources / preambles. During / at HO to the target TRP / gNB404, the WTRU400 may determine which measurement gap configuration to use at the target TRP / gNB404. For example, when WTRU400 may use a new PRS configuration associated with target TRP / gNB404 after HO, WTRU400 may send a RACH message to target TRP / gNB404 using a RACH resource / preamble corresponding to the new measurement gap configuration. In this case, the sending of the corresponding RACH message by WTRU400 indicates the commencement of use of the new PRS configuration and the associated measurement gap configuration at target TRP / gNB404 to the network. In another embodiment where WTRU400 uses an existing PRS configuration associated with source TRP / gNB402, WTRU400 may send a RACH message to target TRP / gNB404 using a RACH resource / preamble corresponding to the existing / previous measurement gap configuration. The sending of the corresponding RACH message by WTRU400 indicates the use of the existing PRS configuration and the associated measurement gap configuration after HO to target TRP / gNB404.

[0152] In another embodiment, if WTRU400 uses a new PRS configuration associated with target TRP / gNB404 before HO, the context associated with the measurement gap configuration aligned with the new PRS configuration can be transferred from target TRP / gNB404 to source TRP / gNB402 (e.g., via the Xn interface). In this case, WTRU400 may receive an indication from source TRP / gNB402 indicating the identifier of the configured measurement gap configuration, and as a result, WTRU400 may use the new PRS configuration along with the measurement gap configuration before HO.

[0153] In another embodiment, where WTRU400 can continue to use the existing PRS configuration associated with source TRP / gNB404 after HO to target TRP / gNB402, the context associated with the measurement gap configuration, which is consistent with the existing / previous PRS configuration, may be transferred from source TRP / gNB402 to target TRP / gNB404 (e.g., via the Xn interface) prior to HO. In this case, WTRU400 may send an indication to target TRP / gNB404 at HO (e.g., in RRC signaling, RACH, MAC CE, and / or UCI) which may contain an identifier for the configured measurement gap configuration, and as a result, WTRU400 may use the existing PRS configuration with the measurement gap after HO.

[0154] In various implementations, including those described above with reference to Figures 2-4, the WTRU may transmit information about positioning measurements to a serving gNB / cell in the RAN to support data link HO. For example, the WTRU may support the RAN to perform conventional data link HO based on positioning measurements. In this case, the WTRU, which can receive PRS from one or more target / neighboring cells, may transmit positioning information, including a measurement report of the PRS measurement, to the serving gNB. Additional information that the WTRU may include in the measurement report to support the RAN may include, for example, changes in distance between the WTRU and the target / neighboring TRP / gNB, possibly over a specific period of time, determined based on the PRS measurement. The serving gNB may use the PRS measurement report and / or the changes in distance information reported by the WTRU to determine at least one of the target TRP / gNBs on which the WTRU can potentially perform data link HO.

[0155] Positioning information transmitted by the WTRU can also be used by the RAN to support conditional HO procedures. In this case, for example, one or more candidate target gNBs for HO can be selected based on the positioning information transmitted by the WTRU. The serving gNB may then also provide the WTRU with specific conditions for evaluation (e.g., one or more thresholds associated with the RSRP and / or RRM measurements of the PRS) before determining the target gNB for performing the data link HO. Alternatively, the WTRU may send an early request for a data link HO to the target cell to the serving cell based on the PRS measurement and / or distance measurement. The request transmitted by the WTRU may, for example, trigger an HO preparation procedure between the serving gNB and the indicated target gNB.

[0156] A WTRU may use validity conditions to determine which PRS configurations to apply during mobility. In some embodiments, a WTRU may use validity conditions associated with one or more PRS configurations to determine when to start and / or stop using the PRS configurations associated with the source base station / gNB / cell and the target base station / gNB / cell during mobility. Validity conditions may be received by the WTRU from the network (e.g., network entities, base stations, LMFs, and / or gNBs) in, for example, (i) one or more LPP messages (e.g., LPP support data provision messages, (ii) LPP request location information messages), (iii) positioning service request messages (e.g., for MT-LR, delayed MT-LR, and / or MO-LR), and / or (iv) AS layer messages (e.g., via RRC signaling, MAC CE, and / or DCI). In some embodiments, one or more validity conditions received by the WTRU may be associated with one or more conditions configured when the WTRU supports delayed MT-LR services / procedures. The validity conditions associated with the PRS configuration may include or indicate any of the following: (1) One or more area validity conditions (e.g., area validity information), e.g., cell ID, RAN notification area (RNA), and / or CN area for which a PRS configuration may be valid for use. In a particular embodiment, the WTRU may consist of a first set of PRS configurations to be used by the WTRU when it is in a first valid area (e.g., under coverage of a first set of cells / gNBs / base stations), and a second set of PRS configurations to be used by the WTRU when it is in a second valid area (e.g., under coverage of a second set of cells / gNBs / base stations). (2) One or more time-validation conditions (e.g., time-validation information) (e.g., a period from start time to expiration time) that may make the PRS configuration valid for use. When a WTRU receives an indication to start using the PRS configuration (e.g., via an LPP position request and / or HO command), it may start the timer (apply the expiration period) and use the configuration for PRS measurement, for example, on the condition that the timer / expiration period is valid and / or has not expired within the configured period. (3) One or more mobility states of the WTRU (e.g., mobility information (e.g., the WTRU may use one or more PRS configurations when (i) the WTRU speed is below / above a configured speed threshold, and / or (ii) the amount and / or rate of the WTRU's movement / orientation increases / decreases by a certain threshold)). (4) One or more radio environment conditions of the WTRU (for example, radio environment information (for example, the WTRU may change from a first set of one or more PRS configurations to a second set if, in particular, (i) the RSRP of measurements made for PRS or non-positioning RS / channels (e.g., CSI-RS, SSB) associated with a first set is above / below the RSRP threshold, (ii) several multipaths are detected to be above / below the threshold, and / or (iii) non-line of sight (NLOS) conditions are detected). (5) RRC state conditions of the WTRU (e.g., whether the WTRU is in the CONNECTED state, the INACTIVE state, or the IDLE state (e.g., the WTRU may change the use of one or more PRS configurations from a first set to a second set when operating in different RRC states before, during, and / or after HO)). In one embodiment, the WTRU may use a first set of PRS configurations when operating in the RRC CONNECTED state, a second set of PRS configurations when operating in the RRC INACTIVE state, and / or a third set of PRS configurations when operating in the RRC_Idle state. The first, second, and third sets associated with different RRC states may, for example, include or contain subsets of PRS configurations that may be common across all sets. Alternatively, PRS configurations may be mutually exclusive across different sets associated with different RRC states.

[0157] When the WTRU determines that one or more of the PRS configurations are no longer valid (for example, one or more validity conditions indicate the expiration of one or more PRS configurations) or are not satisfied, the WTRU may do one of the following: (1) Sending indications to the network (for example, a WTRU may send information or indications to the network that indicate a PRS configuration identifier / ID and / or the expiration status of the configuration; a WTRU may indicate that it is updating the PRS configuration and / or updating one or more valid conditions associated with the indicated PRS configuration. Information or indications sent to the network may be, for example, in or as LPP messages, on-demand PRS messages (e.g., to network entities, base stations, LMFs, and / or gNBs), and / or AS layer messages (e.g., via RRC, MAC CE, and / or UCI)). (2) Change to an alternative valid PRS / SRSp configuration (for example, if the WTRU determines that the first PRS configuration is no longer valid, it may use a second PRS configuration that may be determined to satisfy its validity conditions. If there may be multiple PRS configurations that are found to be valid, the WTRU may, for example, select the PRS configuration that is assigned / associated with the highest priority as the second PRS configuration, and / or (3) Updating and / or forwarding the validity conditions of a PRS / SRSp configuration (for example, if the WTRU determines that a PRS configuration is no longer valid (for example, according to one or more validity conditions), the WTRU may update / forward one or more of its validity conditions based, for example, on the validity conditions of another PRS configuration that has been determined to be valid). The WTRU may, for example, modify the first validity condition (associated with the first PRS configuration) to be the same as or identical to the validity conditions of the second validity condition (associated with the second PRS configuration) if the first validity condition has expired and it is found that a second validity condition was active during the expiration of the first validity condition. The WTRU may, for example, transmit information or indications to the network (e.g., network entities, base stations, gNBs, or LMFs) indicating the status of validity condition updates / forwarding from one PRS configuration to another.

[0158] Upon receiving or at the time of receiving the PRS configuration and one or more associated valid conditions, the WTRU may perform a PRS measurement using the configuration determined to be valid when it receives and / or detects a trigger. A trigger may include, for example, the reception of any of the following: (i) an LPP message (e.g., an LPP request for location information), (ii) a positioning service request (e.g., MO-LR, MT-LR, and / or stationary MT-LT), and / or an AS layer message (e.g., via RRC signaling, MAC CE, and / or DCI).

[0159] In certain representative embodiments, the WTRU may decide whether to initiate use of a new PRS configuration before or after data link HO. A representative procedure may be implemented for the WTRU to decide whether to initiate use of a new PRS configuration associated with a target gNB / cell before or after data link HO. For example, a representative procedure may avoid any positioning gaps and may be based on one or more PRS configurations and / or one or more positioning mobility configurations. These configurations may include, indicate, or encompass information (e.g., rules / conditions) indicating when existing PRS configurations should be released / deactivated and when new PRS configurations should be initiated during mobility. For example, the WTRU may receive from the LMF one or more PRS configurations (e.g., a first PRS configuration associated with a serving cell and a second PRS configuration associated with a target cell) and a positioning mobility configuration. The WTRU may receive (e.g., from the serving gNB) a first RAN configuration (e.g., information including or indicating (i) a measurement gap (MG) configuration (e.g., for performing PRS measurements) and (ii) a CG configuration (e.g., for transmitting positioning reports) based on information about the first PRS configuration provided by the WTRU to the serving base station / gNB. The WTRU may perform PRS measurements using the first PRS configuration and the received RAN configuration when it is under the coverage (e.g., within the coverage area) of the serving cell / gNB / base station. If the positioning mobility configuration indicates that the use of a second PRS configuration will commence before the data link HO and one or more associated conditions are met (e.g., the serving cell's RSRP falls below the RSRP threshold, and / or the RSRP of an adjacent cell (e.g., an adjacent cell or a cell near the WTRU) is above the same or a different RSRP threshold), the WTRU may (1) determine a second RAN configuration (e.g., an MG configuration or a CG configuration) associated with the second PRS configuration, or (2) transmit information or an indication to the serving base station / gNB indicating the determined second RAN configuration associated with the second PRS configuration.Provided that information or indications for using / activating a second RAN configuration (e.g., MG configuration or CG configuration) are received, for example, from a serving base station / gNB / cell, the WTRU may (i) stop and / or release the use of the first PRS configuration and / or the first RAN configuration, and / or (ii) start performing PRS measurements using the second PRS configuration and / or the second RAN configuration when within the coverage area of ​​the serving cell (e.g., under coverage).

[0160] If the positioning mobility configuration indicates that it will continue to use the first PRS configuration after data link HO to the target base station / gNB / cell and the associated conditions are met (e.g., the RSRP of the adjacent cell exceeds the RSRP threshold), the WTRU (1) determines a second RAN configuration (e.g., MG configuration or CG configuration) associated with the second PRS configuration, (2) transmits information or indications to the serving base station or gNB indicating the continued use of the determined second RAN configuration and the first RAN configuration (e.g., MG configuration or CG configuration) associated with the second PRS configuration after data link HO, and (3) during HO and / Alternatively, if the WTRU later performs a PRS measurement using the first PRS configuration and / or the first RAN configuration, and (4) information or indication to use / activate a second RAN configuration (e.g., MG configuration or CG configuration) is received from the target base station / gNB / cell, the WTRU may (i) stop and / or release the use of the first PRS configuration and / or the first RAN configuration, and / or (ii) begin performing a PRS measurement using the second PRS configuration and / or the second RAN configuration when the WTRU is within the coverage area of ​​the target base station / gNB / cell (e.g., under the coverage of the target cell).

[0161] The WTRU may transmit measurement reports to the network (e.g., base stations, gNBs, LMFs, and / or network entities). The measurement reports may include information indicating one or more PRS measurements and / or timing / duration information for initiating and / or discontinuing the use of a first PRS configuration and / or a second PRS configuration.

[0162] In certain representative embodiments, the WTRU may dynamically switch between different positioning methods during HO.

[0163] Typical procedures for a WTRU to switch from a first positioning method (e.g., multi-RTT) to a second positioning method (e.g., DL-TDoA) during a HO (Hold-Off) may be implemented, for example, to ensure positioning service continuity. For example, a WTRU may receive configuration information associated with the first positioning method (e.g., multi-RTT method) and the second positioning method (e.g., DL-TDoA method), as well as trigger information indicating one or more trigger conditions / rules for starting / stopping the use of the second positioning method (e.g., during or after a HO).

[0164] The WTRU may perform a PRS measurement or SRSp transmission using the indicated configuration associated with the first positioning method. When trigger conditions for initiating the use of the second positioning method are met (e.g., the RSRP of the target / adjacent cell exceeds the RSRP threshold and / or an HO command is received from the serving base station / gNB), the WTRU may, among other things, (1) suspend the use of the first positioning method, (2) initiate the use of the second positioning method (e.g., by performing a PRS measurement using the PRS configuration associated with the second positioning method), (3) transmit information or an indication to the network (e.g., LMF and / or serving base station / gNB) that the trigger conditions / rules have been met, and / or (4) transmit a measurement report including measurement information (e.g., which may be provided by the time the first positioning method was suspended).

[0165] When trigger conditions / rules for discontinuing the use of the second positioning method are met (e.g., the RSRP of the source cell / gNB / base station falls below the RSRP threshold, or an HO completion message is sent to the target cell / gNB / base station), the WTRU may, among other things, (1) discontinue the use of the second positioning method, (2) resume the use of the first positioning method, and / or (3) transmit information or indications to the network (e.g., network entities, gNBs, base stations and / or LMFs) indicating that the trigger conditions / rules have been met, and / or (3) transmit a measurement report including measurement / measurement information (e.g., which may be provided until the first positioning method is resumed).

[0166] The WTRU may transmit a measurement report to the network (e.g., LMF or another network entity) containing information indicating the PRS measurement and / or timing for suspending / resuming the use of the first and / or second positioning method.

[0167] In a particular representative embodiment, the WTRU may select the PRS configuration to use during mobility based on one or more valid conditions / rules.

[0168] Typical procedures can be implemented for a WTRU to select a PRS configuration to use during mobility (for example, based on the detection of one or more configured area validity conditions (for example, based on one or more cell IDs)). For example, a WTRU may receive one or more area validity conditions that show a mapping between one or more PRS configurations and / or PRS configurations associated with one or more cell IDs in a valid area. If one or more cell IDs indicated in the area validity conditions are detected (for example, the RSRP of a detected cell exceeds the RSRP threshold during mobility), the WTRU may, among other things, (1) select a PRS configuration that matches at least one of the detected cell IDs; (2) send information or indications to the LMF (e.g., a network entity) indicating the detected cell IDs and / or the selected PRS configuration; (3) perform PRS measurements using the selected PRS configuration; and / or (4) send a measurement report to the network (e.g., an LMF or another network entity) containing information indicating PRS measurements and / or timing for using a different PRS configuration during mobility (e.g., a mobility event such as HO and / or re-establishment procedures).

[0169] In a particular representative embodiment, the WTRU may transmit one or more positioning reports to the LMF or other network entities during mobility, for example, based on a reporting configuration.

[0170] Typical procedures may be implemented for a WTRU to send one or more positioning reports to an LMF (e.g., based on the detection of reporting configurations and / or one or more mobility triggers). For example, a WTRU may receive information indicating one or more PRS configurations and / or one or more reporting configurations (e.g., information including / including / including cell IDs to be reported and / or reporting periodicity). Reporting configurations may be associated with one or more mobility triggers. A WTRU may perform a PRS measurement using the received information indicating the PRS configurations. If a mobility trigger is detected (e.g., an adjacent cell ID is detected and / or the WTRU speed increases above a speed threshold), the WTRU may (1) select a reporting configuration that matches the mobility trigger, (2) send a positioning report to an LMF or network entity (e.g., based on the selected reporting configuration, using the reporting periodicity associated with the indicated reporting configuration), and / or (3) send a measurement report to the network (e.g., an LMF or network entity) including the timing of using different reporting configurations during PRS measurements and / or mobility (e.g., a mobility event).

[0171] In certain representative embodiments, the WTRU may use a first PRS configuration associated with the source base station / gNB / cell before and / or during the HO (e.g., data link HO) and a second PRS configuration associated with the target gNB / cell after the HO (e.g., data link HO). For example, a typical procedure may avoid any positioning gaps and be based on one or more PRS configurations and / or one or more RSRP thresholds related to the PRS measurement. For example, the WTRU may receive configuration information from the network (e.g., base stations, gNBs, LMFs, and / or network entities) indicating one or more PRS configurations. Configuration information may indicate, for example, any of the following: (1) a first PRS configuration associated with a source base station / gNB / cell; (2) a second PRS configuration associated with a target base station / gNB / cell; (3) one or more RSRP thresholds, the first RSRP value and the second RSRP threshold, which may be associated with measurements on PRS resources in the first PRS configuration and / or the second PRS configuration; and / or (4) one or more RRM RSRP thresholds, associated with measurements on RRM resources (e.g., CSI-RS and / or SSB) of the source base station / gNB / cell and / or target / neighbor base station / gNB / cell. The WTRU may receive further information from the serving base station / gNB / cell (e.g., source base station / gNB / cell) indicating (1) the configuration and / or (2) activation indications / information to trigger the use of, for example, a first measurement gap (MG) configuration (e.g., to perform measurements on PRS resources in the first PRS configuration). The WTRU may perform measurements (1) on the PRS resources in the first PRS configuration, and / or (2) using the first MG configuration.

[0172] Provided that the RSRP of the measurement of the PRS resources in the first PRS configuration is below the first RSRP threshold, and / or the RSRP of the measurement of the RRM resources associated with the target base station / gNB / cell is above the first RRM RSRP threshold, the WTRU may transmit indications / information to the serving base station / gNB / cell (e.g., source base station / gNB / cell) indicating continued use of the first MG configuration during and / or after a HO (e.g., data link HO), and may transmit information associated with the second MG configuration (e.g., to perform measurements on the PRS resources in the second PRS configuration after releasing / deactivating the first MG configuration). The WTRU may receive information from the serving base station / gNB / cell indicating use of the first MG configuration during and / or after a HO (e.g., data link HO) (e.g., via (1) an acknowledgment message in response to or following information transmitted by the WTRU, and / or (2) an indication message indicating that the first MG configuration will not be released after receiving an HO command). The WTRU may perform measurements on the PRS resource in a first PRS configuration and / or using a first MG configuration during and / or after the HO (e.g., data link HO).

[0173] If the RSRP of the resource measurement in the first PRS configuration falls below the second RSRP threshold, and / or the RSRP of the RRM resource measurement associated with the target base station / gNB / cell exceeds the second RRM RSRP threshold, the WTRU may transmit information to the serving base station / gNB / cell (which may be, for example, the target base station / gNB / cell) indicating a request to switch to the second MG configuration. The WTRU may receive information from the serving base station / gNB (which may be, for example, the target base station / gNB / cell) indicating a configuration and / or activation indication to trigger the use of the second MG configuration. The WTRU may perform measurements on the PRS resource in a second PRS configuration and / or using a second MG configuration. The WTRU may send one or more measurement reports to the network (e.g., base stations, gNBs, LMFs, and / or network entities). For example, the measurement report may include timing information (e.g., a timestamp) indicating when the WTRU switched from using the first PRS configuration to the second PRS configuration.

[0174] In certain representative embodiments, methods, procedures, apparatus, and systems may be implemented to switch a WTRU from a first PRS configuration to a second PRS configuration after an HO (e.g., based on a plurality of configured PRS configurations associated with different base stations / gNBs / cells and / or thresholds (e.g., RSRP thresholds)). For example, a WTRU may switch from a first PRS configuration to a second PRS configuration (e.g., after an HO and / or another mobility event) based on configured PRS configurations associated with different base stations, gNBs, and / or cells. The switch may further be based on RSRP thresholds.

[0175] In various embodiments, the WTRU may use the PRS configuration associated with the previous serving base station / gNB / cell (e.g., source base station / gNB / cell) during and / or after the data link HO to avoid a positioning gap (e.g., any positioning gap) based, for example, one or more configured PRS configurations and thresholds associated with PRS measurements (e.g., RSRP thresholds).

[0176] In certain embodiments, the WTRU may receive one or more of the following from the network (e.g., LMF, gNB, and / or base station): (1) Multiple PRS configurations (e.g., a first PRS configuration and a second PRS configuration) (for example, the first PRS configuration may be associated with a first base station, gNB and / or cell which may be a serving base station, gNB and / or cell (e.g., a source cell), and the second PRS configuration may be associated with a second base station, gNB and / or cell which may be an adjacent / non-serving base station, gNB and / or cell (e.g., a target cell)), and / or (2) A PRS configuration switching threshold associated with the measurement of a signal received from a base station / gNB / cell / TRP (e.g., the threshold may correspond to, among other things, an RSRP value, an RSSI value, and / or an RSRQ value), the signal received from the base station / gNB / cell / TRP may correspond to, for example, PRS and / or non-PRS signals (e.g., among other things, an RRM signal, a CSI-RS signal, an SSB signal, and / or an SRS signal). The PRS configuration switching threshold may be used by the WTRU to switch from a first PRS configuration to a second PRS configuration, among other things, when the RSRP value of the signal received from the base station / gNB / cell / TRP is, for example, above / below the RSRP threshold.

[0177] The WTRU may transmit an indication to a network / cell (e.g., a network entity, e.g., an LMF, base station, gNB, cell, and / or AMF) requesting that it configure a measurement gap for performing measurements on the PRS resources associated with the first PRS configuration. The WTRU may receive an indication from, for example, the first base station / gNB / cell that includes and / or contains information indicating the first measurement gap configuration.

[0178] The WTRU may perform one or more measurements of a first set on the PRS using a first PRS configuration and a first measurement gap configuration. During mobility, the WTRU may decide whether to (1) perform cell selection from the first base station / gNB / cell to the second base station / gNB / cell or to perform cell reselection, and / or (2) switch from the first PRS configuration to the second PRS configuration, based on the detection of one or more of the following events: (1) The RRM measurement of an adjacent cell (e.g., the CSI-RS and / or SSB of the adjacent cell) is above / below one or more RRM thresholds established by the network (e.g., in particular, network entities, LMF, AMF, gNB, and / or base stations). The RRM measurement / RRM threshold may be based in part on RSRP, RSSI, and / or RSRQ. (2) For example, when monitoring a System Information Block (SIB) and / or performing an adjacent cell measurement, the detection of information related to one or more System Information Blocks (SIBs) and / or adjacent / target cells associated with an SIB (e.g., cell ID, posSIB), (3) For example, when using one or more PRS configurations, if the PRS measurement is above / below one or more thresholds (e.g., using RSRP, RSSI, and / or RSRQ in particular) (e.g., WTRU may determine the HO from the first cell to the second cell and / or switch from the first PRS configuration to the second PRS configuration when the RSRP of the PRS received from the source cell (e.g., the first cell) is below the first RSRP threshold and / or above the second RSRP threshold, and the PRS received from the source cell may be associated with the first PRS configuration). In another embodiment, WTRU may determine the HO from the first cell to the second cell and / or switch from the first PRS configuration to the second PRS configuration when the RSRP of the PRS received from the adjacent / target cell (e.g., the second cell) is above the first RSRP threshold and / or below the second RSRP threshold, and the PRS received from the adjacent / target cell may be associated with the second PRS configuration.

[0179] The WTRU may, in particular, (1) transmit an indication to the first base station / gNB / cell that indicates an HO, (2) perform cell selection or reselection from the first base station / gNB / cell to the second base station / gNB / cell, and / or (3) switch from using the first PRS configuration to using the second PRS configuration based on the detection of one or more event / trigger conditions (e.g., the event / trigger conditions described above). The WTRU may indicate to the network (e.g., network entities, LMFs, and / or serving the first base station / gNB / cell) a request to maintain the first PRS configuration and / or maintain the first measurement gap configuration associated with the first base station / gNB / cell after an HO (e.g., it may indicate further).

[0180] Indications for maintaining a first PRS configuration and / or a first measurement gap configuration may be transmitted by a WTRU for, for example, one or more of the following: (1) Indications from the network (e.g., LMF or other network entity), for example, a WTRU may transmit an indication requesting continued use of the first PRS configuration after receiving an indication from the LMF (e.g., after receiving support data and / or configuration) indicating that it will continue using the first PRS configuration after HO (e.g., when under coverage of a neighbor / target base station / gNB / cell). A WTRU may receive an indication indicating that it will continue using the first PRS configuration until, for example, the RSRP of the PRS is above / below the RSRP threshold, and / or (2) PRS measurements (e.g., a WTRU may transmit an indication when PRS measurements taken by the WTRU using the first PRS configuration and / or a second PRS configuration are above, for example, the first RSRP threshold and / or below the second RSRP threshold).

[0181] The WTRU may receive an HO request / command from the first base station / gNB / cell for an HO to the second base station / gNB / cell. The WTRU may receive an indication from the first base station / gNB / cell, along with the HO request / command and / or in a separate indication (e.g., in particular an RRC message and / or MAC CE), that the first measurement gap configuration will be maintained after the HO is performed. Upon or after receiving the HO request / command, the WTRU performs the HO, and the second base station / gNB / cell (e.g., the target cell) becomes the serving cell, and the first cell may become, for example, a non-serving cell after the HO.

[0182] The WTRU may perform a second set of measurements on the PRS using the first PRS configuration and the first measurement gap configuration. The WTRU may then perform one or more of the following based on the second set of measurements: (1) Provided that the second set of PRS measurements is equal to or greater than the PRS configuration switching threshold, the WTRU may perform a third set of measurements on the PRS using the first PRS configuration and the first measurement gap configuration; (2) Provided that the second set of PRS measurements is less than or equal to the PRS configuration switching threshold, the WTRU may send an indication to the serving base station / gNB / cell to request that the measurement gap associated with the second PRS configuration be configured and / or activated. The WTRU may receive information / indications from the serving base station / gNB / cell that include, or contain, configuration information and / or activation indications for using the second measurement gap configuration. The WTRU may perform a fourth set of measurements on the PRS using the second PRS configuration and the second measurement gap configuration.

[0183] After performing measurements on the PRS during HO, the WTRU may transmit a measurement report to the network (e.g., LMF and / or serving base station / gNB) indicating at least a third set of PRS measurements and / or a fourth set of PRS measurements performed by the WTRU. The WTRU may transmit information / indications indicating which PRS configuration is used during HO (e.g., IDs of the first and / or second PRS configurations), and / or, for example, timing information (e.g., a timestamp) indicating when the WTRU switched from using the first PRS configuration to the second PRS configuration, if switching between different PRS configurations.

[0184] Typical procedures / methods for supporting positioning service continuity for UL-based positioning In one family of solutions, a WTRU performs positioning service continuity based on the transmission of UL-SRSp. For example, a WTRU may perform UL-based positioning by transmitting UL-SRSp during mobility and when receiving a data link HO from a source / serving TRP / gNB / cell to one or more target TRP / gNB / cells. The resources used to transmit the SRSp are allocated to the WTRU by the network (e.g., the serving gNB). Typically, one or more neighboring cells / TRP / gNBs are configured by the network (e.g., LMF and / or RAN entities and / or base stations) to receive the SRSp transmitted by the WTRU and perform the measurement. When the WTRU receives a data link HO from the source gNB to the target gNB, the WTRU may be indicated by the serving gNB to release the resources used for transmitting the SRSp. The WTRU can then be reconfigured by the target gNB after the HO using the same or different SRSp resources. Additionally, the network may reconfigure one or more existing TRP / gNBs or add new TRP / gNBs to receive SRSp transmitted by WTRUs based on WTRU mobility and / or HO, thereby enabling the location of WTRUs to be determined with high accuracy.

[0185] In another family of solutions, the WTRU may send positioning-related reports to the network to update the TRP / gNBs that can receive the UL-SRSp transmitted by the WTRU. For example, the WTRU may be configured to determine and send a positioning-related report to the network about whether one or more target / neighboring cells can receive the SRSp transmitted by the WTRU during WTRU mobility. In this case, the WTRU may be configured using a mapping between the SRSp and a group containing one or more target TRPs / cells (e.g., cell IDs) configured to receive the SRSp transmitted by the WTRU. The WTRU may also be configured to perform RRM measurements to facilitate data link HO, so that the WTRU can determine / detect target / neighboring cells and identify the corresponding cell IDs based on the RRM measurements. The WTRU may then determine whether the target cell is within the existing mapping between the SRSp configured in the WTRU and the list of cells that can measure the SRSp, and report this to the serving cell. For example, a WTRU may report to the serving cell (e.g., in RRC signaling, UL MAC CE, and / or UCI) indicating one or more detected target cell IDs that are not present in the mapping showing the association between the SRSp and the target cell list configured in the WTRU. Based on the report transmitted by the WTRU, the network may, in some cases, configure new target cells for receiving and measuring the SRSp. The WTRU may receive an updated mapping, in some cases including the new target cells in the cell list. The WTRU may also receive a new / updated SRSp configuration, for example, for support during mobility.

[0186] To minimize the latency associated with configuring a new target cell to receive an SRSp transmitted by a WTRU, the WTRU can be configured using one or more positioning service continuity conditions, which the WTRU can monitor and report to the network when triggered by those conditions. For example, the WTRU can be configured using UL-based positioning measurement thresholds such that RSRP measurements made for SSB, CSI-RS, and / or PRS transmitted by a target cell may exceed and / or remain above a threshold over a period of time. The measurement threshold configured for UL-based positioning may be less than or equal to the threshold configured for RRM measurements related to data link HO. Alternatively or additionally, the WTRU can be configured using service continuity conditions relating to the detection of a new target cell ID, in which case the WTRU may detect the new target cell ID (e.g., in an SIB / SSB) during mobility or when the blockage between the WTRU and the target cell is resolved. Alternatively or additionally, the WTRU may be configured using service continuity conditions relating to WTRU mobility attributes, such as changes in WTRU speed, direction, orientation, etc., based on predetermined or dynamically determined thresholds.

[0187] When reporting to the network, the WTRU can include information related to positioning service continuity conditions (e.g., target cell ID, measurement). Sending reports in advance when positioning service continuity conditions are triggered may allow the network to perform target TRP / gNB / cell reconfiguration with low latency and / or before the WTRU receives HO.

[0188] In an alternative solution, a WTRU configured using a mapping between an SRSp and an associated TRP / gNB / cell that can receive SRSps transmitted by a WTRU may send a request to the serving gNB to modify an existing SRSp configuration. In this case, the WTRU may send a request to the serving gNB to modify / update the SRSp, for example, when it detects one or more configured positioning service continuity conditions as described above. The WTRU may then receive the updated / new SRSp configuration from the serving gNB. The new / updated SRSp configuration may, in some cases, be received by the WTRU, for example, when it receives signaling associated with a data link HO (e.g., RRCReconfiguration messages and / or HO commands).

[0189] In another family of solutions, a WTRU may be configured with SRSp usage rules for using SRSp configurations. For example, a WTRU may be (pre-)configured with one or more resources / resource sets associated with an SRSp configuration, along with SRSp usage rules indicating when and how to start / stop using the SRSp configuration. In such a case, the WTRU may receive the SRSp configuration and / or SRSp usage conditions from the RAN. Alternatively or additionally, the WTRU may receive the SRSp configuration from the RAN and at least some of the SRSp usage rules from the LMF. The SRSp usage rules received by the WTRU may be associated with at least one SRSp configuration. The SRSp usage rules may indicate the start / stop of transmission of the associated SRSp configuration (e.g., the ID of the SRSp configuration) when triggered by various conditions.

[0190] Exemplary conditions for starting / stopping the transmission of associated SRSp configurations include the detection of target / adjacent cell IDs. For example, a configured rule might indicate that a first SRSp configuration should be used when a target cell ID is detected (e.g., in a SIB / SSB) within a group of TRP / gNBs associated with the first SRSp configuration. A similar rule could be applied, for example, to the use of a second SRSp configuration.

[0191] Another exemplary condition for initiating / stopping the transmission of associated SRSp configurations involves RRM / PRS measurements of one or more target TRP / gNBs. For example, a configured rule might indicate that a first SRSp configuration should be used when the measured RSRP value (e.g., via the received SSB and / or PRS) is above / below a first threshold, and a second SRSp configuration should be used when the measured RSRP value is above / below a second threshold.

[0192] Another exemplary condition for initiating / stopping the transmission of associated SRSp configurations is the inclusion of an effective area. For example, one or more pre-configured SRSp configurations in a WTRU may be associated with an effective area consisting of a group of one or more TRPs / gNBs. In this case, the WTRU may use the first SRSp configuration as long as the WTRU is mobile or receives HOs from a source to target cells within the effective area (e.g., one or more target TRPs / gNBs / cell IDs discovered by the WTRU or receiving data link HOs are within the effective area group). Based on configured rules, the WTRU may stop using the first SRSp configuration and start using the second SRSp configuration when it discovers a different TRP / gNB during mobility.

[0193] Another exemplary condition for starting / stopping the transmission of an associated SRSp configuration includes its validity period. For example, one or more SRSp configurations may be associated with a validity period. WTRUs may be started / stopped using the SRSp configuration based on the setting / expiration of timers over the configured validity period.

[0194] Another exemplary condition for starting / stopping the transmission of an associated SRSp configuration includes one or more WTRU mobility attributes. For example, a configured rule might indicate that a first SRSp configuration should be used when the WTRU speed is within a first range (e.g., upper and lower threshold speed values). The rule might also indicate that a second SRSp configuration should be used when the WTRU speed is within a second range.

[0195] If one or more of the trigger conditions are not met (for example, the WTRU detects a new target cell ID outside of the TRP / gNB group and one of the associated SRSp configured in the WTRU), the WTRU may send an indication to the network, for example, to request a new SRSp configuration and / or a new SRSp usage rule.

[0196] In another family of solutions, the WTRU may receive an SRSp configuration associated with the target gNB via a serving gNB before / during HO. For example, the WTRU may be configured by the source gNB with an SRSp configuration that can be determined based on coordination with the target gNB during WTRU mobility. In one embodiment, the WTRU may be configured with an SRSp for UL-based positioning by the source / serving gNB. When the WTRU receives a potential data link HO to the target gNB, the source gNB can ensure support for positioning service continuity, and the WTRU may continue to transmit SRSps before and / or during HO without interruption.

[0197] A WTRU can indicate to the network its support for positioning service continuity, and in some cases, based on that indication, the serving gNB may determine the appropriate resources and SRSp configuration to be allocated to the WTRU. The WTRU may transmit an indication to support positioning service continuity in a separate message (e.g., in RRC signaling, UL MAC CE, and / or UCI), or together with RRM measurements to facilitate data link HO.

[0198] A serving gNB may coordinate with a target gNB (e.g., via HO ​​signaling over Xn) to identify the target gNB based on WTRU indications / reports and determine the SRSp configuration to be provided to the WTRU. In this case, the WTRU, which may be configured with a first SRSp configuration, may receive a second SRSp configuration to be used during and after the data link HO. The second SRSp configuration may be associated with resources allocated by the target gNB, which may be shown to the serving gNB during the HO procedure, for example. The WTRU may receive the second SRSp configuration before or with an RRCReconfiguration message containing an HO command. The WTRU may also receive one or more conditions associated with when to start / stop using the second SRSp configuration. For example, the WTRU may start using the second SRSp configuration when it receives an HO command from the serving cell and / or releases the first SRSp configuration. The WTRU may cease using the second SRSp configuration upon receiving an RRC reconfiguration indication from the target gNB, which may be received, for example, after HO and / or after connectivity with the target gNB is established.

[0199] In another embodiment, the WTRU may use a first SRSp configuration before HO to the target gNB (e.g., before and / or after receiving the HO command) and begin using a second SRSp configuration immediately after HO (e.g., after sending RACH and / or RRC signaling to establish connectivity with the target gNB). Receiving an SRSp configuration before receiving a data link HO may enable the WTRU to support positioning service continuity for UL-based positioning with low latency, for example.

[0200] In another family of solutions, a WTRU may assist RAN in performing data link HO based on SRSp transmissions. For example, a WTRU may assist in performing data link HO from a source cell to a target cell based on the selection of an appropriate SRSp configuration and the transmission of the selected SRSp. A WTRU may be (pre)configured with one or more SRSp configurations to support UL-based positioning. A WTRU may also be configured with one or more rules indicating when to start / stop using the SRSp (pre)configurations. In this case, the rules may indicate using a first SRSp configuration until the target gNB / cell ID is detected (e.g., via RRM measurement or adjacent cell SIB), and then using a second SRSp configuration. Reception of an SRSp (e.g., using the second SRSp configuration) in the serving gNB and / or target gNB may trigger the data link HO procedure.

[0201] In another example, a WTRU may select an SRSp configuration from a set of (pre)configurations based on an indication from the network that supports a conditional HO (CHO). In this case, the WTRU may select an SRSp configuration that may have different Tx power levels (e.g., higher than existing SRSps targeting conventional HOs) so that the SRSp can be received with a better RSRP by multiple TRP / gNBs. The RAN may then identify potential target gNBs for the CHO by determining, for example, a subset of target gNBs that can receive SRSps transmitted by the WTRU above a certain RSRP threshold. The WTRU may then receive conditions associated with the CHO procedure from the serving gNB, which can be used by the WTRU, for example, to evaluate and / or determine target gNBs for the HO.

[0202] In certain representative embodiments, the WTRU may determine the SRSp configuration to be used during mobility (for example, based on the detection of configured mobility triggers).

[0203] A typical procedure may be implemented for the WTRU to determine the SRSp configuration to use for UL positioning during mobility (for example, based on the detection of configured mobility triggers). For example, a WTRU may transmit information or indications (e.g., indicating the WTRU's capabilities / capabilities for supporting positioning service continuity during mobility) to a serving base station / gNB.

[0204] The WTRU may receive any of the following: (1) one or more SRSp configurations, (2) one or more activation conditions associated with the SRSp configurations (e.g., RAN notification area and / or TA timer / timing information), and / or (3) one or more SRSp usage rules indicating when to start and / or stop using the SRSp configurations (e.g., one or more RSRP measurements from adjacent cells exceeding an RSRP threshold and / or reception of an HO command).

[0205] When a mobility trigger is detected, the WTRU may (1) select an SRPp configuration that satisfies one or more activation conditions, and / or (2) transmit information or an indication of the selected SRPp configuration to the serving base station / gNB. The WTRU may, for example, perform an SRSp transmission using the selected SRSp configuration after or upon receiving information or an indication from the gNB, base station, and / or network entity that the SRSp configuration has been activated, based on the SRSp usage rules.

[0206] Typical procedures / methods for supporting positioning service continuity based on switching between different positioning methods In certain representative embodiments, the WTRU may support positioning service continuity procedures using LPP. For example, the WTRU may receive one or more RAN configurations associated with positioning to be applied during mobility. The WTRU may use one or more validity conditions to determine the PRS configuration to apply during mobility.

[0207] In certain representative embodiments, the WTRU may decide whether to initiate use of the new PRS configuration before or after data link HO.

[0208] In certain representative embodiments, the WTRU may dynamically switch between different positioning methods during HO.

[0209] In certain representative embodiments, the WTRU may select the PRS configuration to use during mobility based on the validity conditions.

[0210] In a particular representative embodiment, the WTRU may, based on its reporting configuration, transmit one or more positioning reports to the LMF or other network entities during mobility.

[0211] In certain representative embodiments, the WTRU may determine the SRSp configuration to use during mobility based on the detection of configured mobility triggers.

[0212] Figure 5 is a graph showing the timing of operations before, during, and after HO according to one embodiment.

[0213] Referring to Figure 5, the WTRU can switch to different positioning methods during HO to ensure positioning service continuity. For example, the WTRU can switch from a first positioning method at 500A to a second positioning method at 502 over the period 504 of the data link HO, and possibly switch back to the first positioning method at 500B after the HO. In such a case, the WTRU may be configured to perform DL and UL-based positioning methods (e.g., multi-RTT) by the serving gNB. In this multi-RTT positioning method, the WTRU may perform measurements on DL-PRS received from a group of TRP / gNBs over a first period and transmit UL-SRSp to the group of TRP / gNBs over a second period. The WTRU's positioning information may be determined, for example, based on the RTT it takes for the PRS and SRSp to travel between the network node and the WTRU.

[0214] To support positioning service continuity, if positioning-related measurements can be supported when receiving a data link HO, the WTRU may be configured using at least a second positioning method in addition to the first positioning method. If the WTRU is configured with multi-RTT as the first positioning method, the WTRU may also be configured by the network with DL-based (DL-PRS) or UL-based (UL-SRSp) as the second positioning method, for example, performed in 504. The WTRU may also be configured using one or more positioning service continuity conditions, as described above, to determine when to switch from the first method to the second method. In one embodiment, the WTRU may be configured to perform multi-RTT positioning by measuring DL-PRS and transmitting UL-SRSp before detecting a positioning service continuity condition (e.g., reception of an RRCReconfiguration message / HO command), and may switch to performing DL-PRS measurement (e.g., measurement only) during the HO period. Once the WTRU establishes connectivity with the target gNB (for example, by performing RRC signaling send / receive), it can switch back to performing multi-RTT operations.

[0215] Temporarily switching from a first positioning method in 500A to a second positioning method in 504 during HO may enable, for example, the achievement of graceful degradation in positioning accuracy and reliability performance. When switching from one positioning method to another, the WTRU may transmit an indication to the network (LMF and / or RAN) in RRC signaling, MAC CE, and / or UCI. The WTRU may transmit an indication of switching to another positioning method, for example, along with signaling associated with the data link HO (e.g., RRC signaling including measurement reports, RACH messages). The WTRU can be configured to use one or more different second positioning methods during HO and to switch between them, and the different positioning methods used by the WTRU may be correlated / aligned with signaling associated with the data link HO, for example.

[0216] In one embodiment, the WTRU is configured to use the DL-TDoA positioning method before the HO, and during the HO, the WTRU may switch to using the multi-RTT method. Upon completion of the HO, the WTRU may switch back to using DL-TDoA. Achieving certain accuracy in positioning using DL-ToA may require timing synchronization between the WTRU and the TRP / gNB. Because there may be certain periods during the HO when the WTRU may lose synchronization with the serving gNB and / or may not be synchronized with the target gNB, the WTRU may use a positioning method that may have less stringent synchronization requirements with the network, such as the multi-RTT or DL-AoD method during the HO. In this case, a second positioning method with relaxed synchronization may be used during the associated periods when the WTRU may not be synchronized with the network and / or based on synchronization-related triggers. The WTRU may then switch to using the DL-TDoA method once it has established synchronization with the target gNB, for example.

[0217] In another embodiment, the switching point may be determined by the WTRU with or without network assistance based on monitoring of WTRU mobility attributes and / or the WTRU radio environment. For example, if the WTRU detects an increase in delay or a decrease in positioning accuracy while measuring DL-PRS (e.g., the RSRP of the PRS falls below a threshold), possibly due to an increase in WTRU speed, the WTRU may switch to performing UL-SRSp transmission for a certain period while performing HO. The WTRU may then switch back to measuring DL-PRS, possibly after HO, after sending a switching indication to the network.

[0218] When using a multi-RTT method that includes both DL-based and UL-based methods, the WTRU may be configured (in advance) with DL-PRS and UL-SRSp configurations, and both configurations may be activated before the HO. When the WTRU receives the HO, one of the methods / configurations may be deactivated for the duration of the HO and then activated upon completion of the HO. Signaling associated with activating / deactivating one or more positioning methods may be received by the WTRU from the network in RRC signaling, MAC CE, and / or DCI. If the WTRU decides to activate / deactivate a positioning method based on the detection of one or more positioning service continuity conditions, the WTRU may transmit activation / deactivation indications to the network, for example, in RRC signaling, MAC CE, and / or UCI.

[0219] Typical Procedures / Methods Implemented in WTRU to Support Positioning Service Continuity Figure 6 is a flowchart showing typical methods implemented by WTRU.

[0220] Referring to Figure 6, typical methods 600 implemented in WTRUs 102, 200, 300, 400, and 500 can support positioning service continuity. In block 610, WTRU 102 may receive configuration information indicating a configuration for supporting positioning service continuity during HO. For example, as further detailed herein, WTRUs 102, 200, 300, 400, and 500 may receive configurations for performing support for positioning service continuity for DL ​​positioning and / or UL positioning. Alternatively or additionally, WTRUs 102, 200, 300, 400, and 500 may receive information / configurations for switching positioning methods before and / or during data link HO. The operation may proceed from block 610 to block 620.

[0221] In block 620, WTRU102, 200, 300, 400, and 500 may, at least partially, support positioning service continuity according to their configuration by determining one or more transmissions to be performed. For example, WTRU102, 200, 300, 400, and 500 may use a new PRS configuration associated with a target gNB / base station when under the coverage of a source gNB / base station and / or connected to a source gNB / base station, as previously described with reference to Figure 2. Alternatively or additionally, WTRU102, 200, 300, 400, and 500 may use an existing PRS configuration associated with a source gNB / base station when under the coverage of a target gNB / base station and / or connected to a target gNB / base station, as previously described with reference to Figure 3. Alternatively or additionally, WTRU102, 200, 300, 400, and 500 may use the existing PRS configuration associated with the source gNB / base station and the new PRS configuration associated with the target gNB / base station during data link HO, as previously described with reference to Figure 4. Alternatively or additionally, WTRU102, 200, 300, 400, and 500 may use the first positioning method before data link HO and switch to the second positioning method during data link HO, as previously described with reference to Figure 5. The operation may proceed from block 620 to block 630.

[0222] In block 630, WTRU102, 200, 300, 400, and 500 can operate a radio access network with data link HO by performing one or more transmissions according to their configuration. For example, when supporting positioning service continuity for DL ​​positioning, WTRU102, 200, 300, 400, and 500 may transmit information about positioning measurements to the radio access network to support data link HO. Alternatively or additionally, when supporting positioning service continuity for DL ​​positioning, WTRU102, 200, 300, 400, and 500 may perform UL-SRSp transmissions.

[0223] In some implementations, WTRU102, 200, 300, 400, and 500 support positioning service continuity for DL ​​positioning, and the configuration is at least one PRS configuration. In these implementations, method 600 may include various operations or steps specific to these implementations. For example, the method may include performing positioning service continuity based on PRS / RRM measurements and / or sending a request for a new PRS configuration message to the serving gNB / base station. Alternatively or additionally, the method may include sending a positioning service continuity report and / or receiving at least one of the new or updated PRS configurations in response to the positioning service continuity report. Alternatively or additionally, the method may include using the target gNB's PRS configuration before the data link HO in the source gNB / base station's coverage area, using the source gNB / base station's PRS configuration after the data link HO in the target gNB / base station's coverage area, and / or using the source gNB / base station's PRS configuration and the target gNB / base station's PRS configuration during the data link HO. Alternatively or additionally, the method may include determining, based on the measurement gap configuration, the use of two or more PRS configurations, including at least the source gNB / base station's PRS configuration and the target gNB / base station's PRS configuration, and / or transmitting information regarding positioning measurements to the radio access network to support the data link HO.

[0224] In some implementations, WTRU102, 200, 300, 400, and 500 support positioning service continuity for UL positioning, and the configuration includes one or more SRSp configurations and SRSp usage rules for using one or more SRSp configurations. In these implementations, method 600 may include various operations or steps specific to these implementations. For example, the method may include performing positioning service continuity based on the transmission of UL-SRSp and / or transmitting positioning-related reports to the radio access network to update TRP / gNBs that can receive UL-SRSp transmitted by WTRU102, 200, 300, 400, and 500. Alternatively or additionally, the method may include receiving an SRSp configuration associated with a target gNB / base station via a serving gNB / base station at least one of the following: before or during data link HO. Alternatively or additionally, the method may include assisting the radio access network in performing data link HO based on the transmission of UL-SRSp.

[0225] In some embodiments, WTRU102, 200, 300, 400, and 500 may use a first positioning method before data link handover and switch to a second positioning method during data link handover.

[0226] Figure 7 is a block diagram showing another typical method implemented by WTRU.

[0227] Referring to Figure 7, a typical method 700 may include, in block 710, receiving information indicating (1) a first positioning reference signal (PRS) configuration associated with a first cell, (2) a second PRS configuration associated with a second cell, and (3) a measurement gap (MG) configuration. In block 720, WTRU102, 200, 300, 400, and 500 may perform a first PRS measurement for a first transmission from the first cell using the first PRS configuration and MG configuration. In block 730, WTRU102, 200, 300, 400, and 500 may send a request to a first network entity (NE) associated with the first cell, including information indicating that the MG configuration should be maintained after a mobility event (ME) associated with the second cell has occurred. In block 740, WTRU102, 200, 300, 400, and 500 may transmit and receive information indicating (1) to perform an ME associated with the second cell, and (2) to maintain the MG configuration after the ME has been performed. In block 750, WTRU102, 200, 300, 400, and 500 may, after the ME has been performed, perform a second PRS measurement for a first transmission or further transmission from the first cell using the first PRS configuration and MG configuration. In block 760, WTRU102, 200, 300, 400, and 500 may transmit information indicating a second PRS measurement to the second NE associated with the first cell.

[0228] For example, WTRU102, 200, 300, 400, and 500 may receive (e.g., from a base station, LMF, and / or NE) (1) a first PRS configuration, (2) a second PRS configuration (e.g., the first PRS configuration may be associated with a first cell (e.g., a source cell) and the second PRS configuration may be associated with a second cell (e.g., a target cell)), (3) a PRS switching threshold, and (4) one or more reference signal received power (RSRP) thresholds (e.g., first and second RSRP thresholds). WTRU102, 200, 300, 400, and 500 may perform a first PRS measurement (e.g., of the PRS from the first cell) using the first PRS configuration (received from the first cell) and the first MG configuration.

[0229] WTRU102, 200, 300, 400, and 500 may send a request to the first cell to maintain the first MG configuration after HO when one or more first PRS measurements meet the RSRP threshold criteria (for example, when the PRS measurements are higher than the first threshold and / or lower than the second threshold).

[0230] WTRU102, 200, 300, 400, and 500 may receive HO indications from the first cell indicating HO to the second cell, and indications maintaining the first MG configuration during and / or after HO.

[0231] WTRU102, 200, 300, 400, and 500 may perform a second PRS measurement after HO to the second cell. The second PRS measurement may be performed using the first PRS configuration and the first MG configuration of the first cell.

[0232] WTRU102, 200, 300, 400, and 500 may determine whether the second PRS measurement meets the PRS switching threshold (e.g., is below the threshold). If the PRS switching threshold is not met, WTRU102, 200, 300, 400, and 500 may send a report (e.g., to the LMF). The report may include the second PRS measurement and / or indication of the first PRS configuration identifier (ID) used during HO. If the PRS switching threshold is met, WTRUs 102, 200, 300, 400, and 500 may (1) send a request to the second cell of the second MG gap configuration associated with the second PRS configuration, (2) receive information indicating the second MG configuration, (3) perform a third PRS measurement using the second PRS configuration and the second MG configuration, or (4) send a report (e.g., to the LMF) including an indication of the second PRS measurement, the third PRS measurement, and / or the second PRS configuration ID, and a time (e.g., a timestamp) indicating the time when the WTRU switched from the first PRS configuration to the second PRS configuration.

[0233] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may decide to send a request to a first cell indicating that the MG configuration will be maintained after the ME is performed.

[0234] In certain embodiments, the first NE associated with the first cell and the second NE associated with the first cell may be a single base station, or the first NE may be a first base station and the second NE may be a location management function (LMF) entity.

[0235] In certain representative embodiments, WTRUs 102, 200, 300, 400, and 500 may, provided that the second PRS measurement does not meet the PRS ME threshold, (1) send a request for further MG configuration to the first NE associated with the second cell, (2) receive information indicating further MG configuration, (3) perform a third PRS measurement for a transmission from the second cell using the second PRS configuration and further MG configuration, and / or (4) send further information to the second NE associated with the second cell indicating any of (1) the third PRS measurement, (2) the second PRS configuration, and / or (3) the time when the WTRU began using the second PRS configuration.

[0236] In some embodiments, the first NE associated with the first cell and the second NE associated with the first cell may be a single base station, or the first NE associated with the first cell may be the first base station and the second NE associated with the first cell may be an LMF entity. The first NE associated with the second cell and the second NE associated with the second cell may be another single base station, or the first NE associated with the second cell may be the second base station and the second NE associated with the second cell may be an LMF entity.

[0237] In certain representative embodiments, the ME may be either (1) handover or (2) reselection, and WTRU102, 200, 300, 400, and 500 may perform a handover or reselection of WTRU102, 200, 300, 400, and 500 to a second cell.

[0238] In some embodiments, further information may be included in the positioning service continuity report. WTRU102, 200, 300, 400, and 500 may receive a new or updated PRS configuration in response to or after the positioning service continuity report. The new or updated PRS configuration may be associated with a target NE or a first NE associated with a second cell.

[0239] In certain representative embodiments, performing a second PRS measurement for a first or further transmission from the first cell using the first PRS configuration and MG configuration after ME has been performed may include WTRU102, 200, 300, 400, and 500 performing a first PRS measurement for a first transmission from the first cell using the first PRS configuration associated with the first cell after a data link handover in the coverage area of ​​the second cell.

[0240] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may perform further PRS measurements on transmissions from a second cell using a second PRS configuration associated with the second cell within the coverage area of ​​the first cell, before the ME is performed.

[0241] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may perform further PRS during ME (Mechanism of Transmission) (1) for transmissions from the first cell using the first PRS configuration of the first cell, and (2) for transmissions from the second cell using the second PRS configuration of the second cell.

[0242] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 can be switched from a first positioning method to a second positioning method during ME.

[0243] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may transmit information indicating that one or more of the PRS configurations are being used, activated, or deactivated.

[0244] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may trigger the execution of a second PRS measurement in response to or after the ME. For example, (1) the first PRS measurement may use the first PRS configuration and MG configuration before the ME is performed, and / or (2) the second PRS measurement may use the first PRS configuration and MG configuration during at least the first part of the ME. WTRU102, 200, 300, 400, and 500 may perform further PRS measurements using the second PRS configuration and second MG configuration (1) during at least the second part of the ME, and / or (2) after the ME has been performed.

[0245] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may initiate the use of a second positioning operation on the condition that (1) they receive information associated with one or more trigger conditions for initiating and / or stopping the use of a first positioning operation, (ii) a second positioning operation, and / or (iii) a second positioning operation, and / or (2) one or more trigger conditions are met for initiating the use of a second positioning operation. For example, (1) a first PRS measurement may use a first PRS configuration associated with a first positioning operation, and / or (2) a second PRS measurement may use a second PRS configuration associated with a second positioning operation.

[0246] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may trigger the execution of a second PRS measurement in response to or after an ME using a second PRS configuration associated with a second positioning operation. For example, (1) a first PRS measurement may use the first PRS configuration (i) before the ME is performed and / or (ii) during at least a first portion of the ME, and / or (2) a second PRS measurement may use the second PRS configuration (i) during at least a second portion of the ME and / or (ii) after the ME is performed.

[0247] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may receive reporting configuration information indicating multiple reporting configurations. For example, each of the indicated reporting configurations may be associated with a type of trigger condition associated with the ME. WTRU102, 200, 300, 400, and 500 transmit positioning reports to the LMF entity according to the type of trigger condition associated with the ME. For example, the types of trigger conditions associated with ME may include any of the following: (1) speed-related trigger conditions associated with WTRU102, 200, 300, 400, and 500; (2) velocity-related trigger conditions associated with WTRU; (3) direction-related trigger conditions for movement associated with WTRU102, 200, 300, 400, and 500; (4) orientation-related trigger conditions associated with WTRU102, 200, 300, 400, and 500; (5) environment-related trigger conditions associated with WTRU102, 200, 300, 400, and 500; (6) indoor / outdoor state-related trigger conditions associated with WTRU102, 200, 300, 400, and 500; and / or (7) adjacent cell detection / discovery-related trigger conditions.

[0248] In certain representative embodiments, the first reporting configuration among the multiple reporting configurations shown may include first periodicity information, and the second reporting configuration among the multiple reporting configurations shown may include second, different periodicity information.

[0249] Figure 8 is a flowchart illustrating further typical methods implemented by WTRU.

[0250] Referring to Figure 8, a typical method 800 may include, in block 810, WTRU 102, 200, 300, 400, and 500 receiving information indicating (1) a first positioning reference signal (PRS) configuration associated with a first cell, (2) a second PRS configuration associated with a second cell, and (3) a first measurement gap (MG) configuration associated with a first cell. In block 820, WTRU 102, 200, 300, 400, and 500 may, prior to a handover (HO), perform a first PRS measurement for a first transmission from a first cell using the first PRS configuration and the indicated first MG configuration. In block 830, WTRU 102, 200, 300, 400, and 500 may, provided that an HO has been performed, decide whether to use the indicated first MG configuration or a further MG configuration associated with a second cell. In block 840, WTRU102, 200, 300, 400, and 500 may send a request for further MG configuration to the first network entity (NE) associated with the second cell, provided that further MG configuration is used. In block 850, WTRU102, 200, 300, 400, and 500 may receive information indicating further MG configuration. In block 860, WTRU102, 200, 300, 400, and 500 may, after HO, perform a second PRS measurement for transmissions from the second cell using the second PRS configuration and further MG configuration. In block 870, WTRUs 102, 200, 300, 400, and 500 may transmit to the second NE associated with the second cell any of the following: (1) a second PRS measurement, (2) a second PRS configuration, and / or (3) the time (e.g., a timestamp) when the WTRU began using the second PRS configuration.

[0251] In certain representative embodiments, the decision of whether to use the indicated first MG configuration associated with the first cell or a further MG configuration associated with the second cell may include a decision on whether the first PRS measurement satisfies the PRS ME threshold.

[0252] In certain representative embodiments, information transmitted to a second NE associated with a second cell may be included in a positioning service continuity report. In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may receive a new or updated PRS configuration in response to or after a positioning service continuity report. For example, a new or updated PRS configuration may be associated with a target NE or a first NE associated with a second cell.

[0253] In a particular representative embodiment, the first NE associated with the first cell and the second NE associated with the first cell may be a single base station, or (2) the first NE associated with the first cell may be a first base station and the second NE associated with the first cell may be an LMF entity.

[0254] In some embodiments, (1) the first NE associated with the second cell and the second NE associated with the second cell may be another single base station, or (2) the first NE associated with the second cell may be the second base station and the second NE associated with the second cell may be an LMF entity.

[0255] Figure 9 is a flowchart illustrating additional typical methods implemented by WTRU.

[0256] Referring to Figure 9, a typical method 900 may include, in block 910, WTRUs 102, 200, 300, 400, and 500 receiving information indicating (1) a positioning reference signal (PRS) configuration associated with a first cell, and (2) a measurement gap (MG) configuration. In block 920, WTRUs 102, 200, 300, 400, and 500 may receive information indicating that a mobility event (ME) associated with a second cell should be performed. In block 930, WTRUs 102, 200, 300, 400, and 500 may use the PRS configuration and MG configuration to perform a first PRS measurement for one or more transmissions from the first cell. For example, the PRS measurement may be performed before and after the indicated ME is performed.

[0257] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may either (1) send a request to the first cell, including priority information indicating that the MG configuration will be maintained after the ME associated with the second cell is performed, and / or (2) receive confirmation information indicating confirmation that (i) the ME associated with the second cell should be performed, and (ii) the MG configuration will be maintained after the ME is performed.

[0258] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may (1) perform a second PRS measurement for a first or further transmission from a first cell after an ME has been performed, using a first PRS configuration and an MG configuration, and / or (2) transmit information indicating the second PRS measurement to a network entity (NE) of a second cell.

[0259] Figure 10 is a flowchart illustrating yet another typical method implemented by WTRU.

[0260] Referring to Figure 10, a typical method 1000 may include, in block 1010, WTRUs 102, 200, 300, 400, and 500 receiving configuration information, which includes receiving configuration information indicating (1) one or more sounding reference signal (SRSp) configurations for positioning, and (2) one or more valid conditions. In block 1020, WTRUs 102, 200, 300, 400, and 500 may select a indicated SRSp configuration, provided that one or more indicated valid conditions associated with the indicated SRSp configuration are satisfied. In block 1030, WTRUs 102, 200, 300, 400, and 500 may transmit an uplink transmission containing one or more SRSps to a network entity (NE) according to the selected SRSp configuration.

[0261] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may receive positioning information associated with WTRU102, 200, 300, 400, and 500 from the NE. For example, the positioning information may be derived according to the SRSp measurement of the uplink transmission.

[0262] In a particular representative embodiment, each SRSp configuration may be associated with a set of specified validity conditions, which include (1) one or more area-related conditions, (2) one or more time-related conditions, and / or (3) one or more mobility-related attribute conditions. For example, one or more area-related conditions may include (1) detected cell identifiers associated with the coverage area of ​​cells for serving WTRU102, 200, 300, 400, and 500, corresponding to the cell identifiers associated with each SRSp configuration, and (2) detected radio access network (RAN) notification areas of WTRU102, 200, 300, 400, and 500, corresponding to the RAN notification areas associated with each SRSp configuration. (3) The detected geographical areas of WTRU102, 200, 300, 400, and 500 may correspond to the geographical areas associated with their respective SRSp configurations, or (4) The determined area identifiers of WTRU102, 200, 300, 400, and 500 may correspond to the area identifiers associated with their respective SRSp configurations. The detected cell identifiers may correspond to the cell identifiers associated with their respective SRSp configurations.

[0263] As a second example, one or more time-related conditions may include any of the following: (1) time during a period after the trigger condition is met, (2) time from when the trigger condition is met until after the period has ended (e.g., a timestamp), and / or (3) time within a time window after the trigger condition is met.

[0264] As a third example, one or more mobility-related attribute conditions are: (1) the detected speed or velocity of WTRU102, 200, 300, 400, and 500 satisfies the speed or velocity condition associated with their respective SRSp configuration; (2) the determined speed change or velocity change of WTRU102, 200, 300, 400, and 500 satisfies the speed change or velocity change condition associated with their respective SRSp configuration; (3) the expected speed or velocity of WTRU102, 200, 300, 400, and 500 satisfies the speed change or velocity change condition associated with their respective SRSp configuration (4) The expected speed change or velocity change of WTRU102, 200, 300, 400, and 500 satisfies the speed change or velocity change condition associated with each SRSp configuration. (5) The detected direction of movement of WTRU102, 200, 300, 400, and 500 satisfies the direction of movement condition associated with each SRSp configuration. (6) The expected direction of movement of WTRU102, 200, 300, 400, and 500 satisfies the direction of movement condition associated with each SRSp configuration. (7) The detected orientations of WTRU102, 200, 300, 400, and 500 satisfy the orientation conditions associated with their respective SRSp configurations. (8) The expected orientations of WTRU102, 200, 300, 400, and 500 satisfy the orientation conditions associated with their respective SRSp configurations. (9) The determined environmental conditions experienced by WTRU102, 200, 300, 400, and 500 satisfy the environmental conditions associated with their respective SRSp configurations. (10) WTRU102, 200, 30 (11) The determined indoor / outdoor status of WTRU102, 200, 300, 400, and 500 satisfies the indoor / outdoor condition associated with each SRSp configuration, and / or (12) The expected indoor / outdoor condition of WTRU102, 200, 300, 400, and 500 satisfies the indoor / outdoor condition condition associated with each SRSp configuration.

[0265] Figure 11 is a flowchart illustrating yet another typical method implemented by WTRU.

[0266] Referring to Figure 11, a typical method 1100 may include, in block 1110, WTRUs 102, 200, 300, 400, and 500 receiving configuration information associated with (1) a first positioning operation, (2) a second positioning operation, and (3) one or more trigger conditions for initiating and / or stopping the use of the second positioning operation. In block 1120, WTRUs 102, 200, 300, 400, and 500 may use the first configuration associated with the first positioning operation to perform either a first PRS measurement and / or a first SRSp transmission with a network entity (NE) associated with a first cell. In block 1130, WTRU102, 200, 300, 400, and 500 may (1) initiate the use of a second positioning operation, and (2) perform either a second PRS measurement and / or a second SRSp transmission using a second configuration associated with the second positioning operation, provided that one or more trigger conditions for initiating the use of a second positioning operation are met.

[0267] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may, after initiating a second positioning operation, trigger the execution of a second PRS measurement using a second configuration associated with the second positioning operation during a mobility event (ME), synchronize WTRU102, 200, 300, 400, and 500 with the second cell, and perform further PRS measurements using further configurations after synchronizing WTRU102, 200, 300, 400, and 500 with the second cell. In certain embodiments, the execution of a first PRS measurement may use a first configuration before the ME is performed.

[0268] In certain representative embodiments, after starting a second positioning operation, the WTRUs 102, 200, 300, 400, and 500 trigger the execution of a second SRSp transmission using a second configuration associated with the second positioning operation during a mobility event (ME), synchronize the WTRUs 102, 200, 300, 400, and 500 with a first NE associated with the second cell, and may execute a further SRSp transmission using a further configuration after synchronizing the WTRU with the second cell. In certain embodiments, the execution of the first SRSp transmission may use a first configuration before the ME is executed. For example, the second positioning operation may correspond to relaxed or more stringent synchronization timing requirements compared to the first positioning operation.

[0269] In certain representative embodiments, the first positioning operation may include any one of (1) a downlink arrival time difference operation, (2) an uplink SRSp operation, (3) a multi-round trip time (multi-RTT) operation, and / or (4) a downlink PRS operation. The second positioning operation may include any different one of (1) a downlink arrival time difference operation, (2) an uplink SRSp operation, (3) a multi-RTT operation, and / or (4) a downlink PRS operation.

[0270] In certain representative embodiments, the WTRUs 102, 200, 300, 400, and 500 may transmit to a network entity (NE) information indicating any one of (1) a second measurement value, (2) timing information, (3) a timestamp indicating when the WTRU switched from using a first PRS configuration to a second PRS configuration, (4) a time difference between the received PRS and the transmitted SRSp, and / or (5) a measured RSRP for the PRS.

[0271] FIG. 12 is a flowchart showing a further additional representative method implemented by a WTRU to support positioning service continuity, for example.

[0272] Referring to Figure 12, a typical method 1200 may include, in block 1210, WTRUs 102, 200, 300, 400, and 500 receiving configuration information indicating at least (1) a plurality of PRS configurations including a first PRS configuration associated with a first cell or first base station, a second PRS configuration associated with a second cell, and (2) a first RAN configuration. In block 1220, WTRUs 102, 200, 300, 400, and 500 may perform PRS measurements using the indicated first PRS configuration and the indicated first RAN configuration, provided that WTRUs 102, 200, 300, 400, and 500 are within the coverage area of ​​the first cell or first base station. In block 1230, WTRU102, 200, 300, 400, and 500 may decide to initiate the use of a second PRS configuration based on PRS measurements. In block 1240, WTRU102, 200, 300, 400, and 500 may determine a second RAN configuration associated with the second PRS configuration from the received configuration information. In block 1250, WTRU102, 200, 300, 400, and 500 may initiate the execution of PRS measurements using the second PRS configuration and the second RAN configuration.

[0273] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may either (1) transmit information indicating a determined second RAN configuration to a serving base station as a first base station, and / or (2) receive information from the serving base station confirming the use or activation of the second RAN configuration.

[0274] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may trigger the execution of a PRS measurement in accordance with a mobility event (ME). For example, the execution of a PRS measurement may be (1) before the ME and / or (2) during at least the first part of the ME, using a first PRS configuration and a first RAN configuration. In certain embodiments, WTRU102, 200, 300, 400, and 500 may perform a PRS measurement using a second PRS configuration and a second RAN configuration, (1) during at least the second part of the ME and / or (2) after the ME.

[0275] Figure 13 is a flowchart illustrating yet another typical method implemented by WTRU to support positioning service continuity, for example.

[0276] Referring to Figure 13, a typical method 1300 may include, in block 1310, WTRUs 102, 200, 300, 400, and 500 receiving configuration information associated with (1) a first positioning operation, (2) a second positioning operation, and (3) one or more trigger conditions for initiating and / or stopping the use of the second positioning operation. In block 1320, WTRUs 102, 200, 300, 400, and 500 may perform either a PRS measurement and / or an SRSp transmission using a first PRS configuration associated with the first positioning operation. In block 1330, WTRU102, 200, 300, 400, and 500 may (1) initiate the use of a second positioning operation, and / or (2) perform either a PRS measurement and / or an SRSp transmission using a second PRS configuration associated with the second positioning operation, provided that trigger conditions for initiating the use of a second positioning operation are met.

[0277] In certain representative embodiments, WTRU102, 200, 300, 400, and 500 may trigger the execution of a PRS measurement and / or SRSp transmission using a second PRS configuration associated with a second positioning operation, in accordance with a mobility event (ME). For example, the execution of a PRS measurement may use the first PRS configuration (1) before the ME and / or (2) during at least the first part of the ME. In another embodiment, the execution of a PRS measurement may use the second PRS configuration (1) during at least the second part of the ME and / or (2) after the ME.

[0278] Figure 14 is a flowchart illustrating yet another typical method implemented by a WTRU to support positioning service continuity, for example.

[0279] Referring to Figure 14, a typical method 1400 may include, in block 1410, WTRUs 102, 200, 300, 400, and 500 receiving configuration information indicating (1) one or more PRS configurations and (2) one or more area enable conditions. In block 1420, WTRUs 102, 200, 300, 400, and 500 may select a PRS configuration from the indicated PRS configurations that matches at least one of the detected cells, provided that one or more cells having cell IDs indicated by area enable conditions are detected. In block 1430, WTRUs 102, 200, 300, 400, and 500 may transmit information to a network entity indicating the cell ID of at least one detected cell and the selected PRS configuration. In block 1440, WTRUs 102, 200, 300, 400, and 500 may perform a PRS measurement using the selected PRS configuration.

[0280] Figure 15 is a flowchart illustrating additional typical methods implemented by WTRU.

[0281] Referring to Figure 15, a typical method 1500 may include, in block 1510, WTRUs 102, 200, 300, 400, and 500 receiving configuration information indicating at least (1) first and second PRS configurations, 2) a first set of thresholds associated with the first PRS configuration, and 3) a second set of thresholds associated with the second PRS configuration. In block 1520, WTRUs 102, 200, 300, 400, and 500 may perform a handover from the first base station to the second base station. For example, the indicated first PRS configuration associated with the first base station, and the indicated first set of thresholds associated with the indicated first PRS configuration, may be active during the handover. In block 1530, WTRUs 102, 200, 300, 400, and 500 may, after handover, switch from the active first PRS configuration associated with the first base station and the first set of thresholds associated with the indicated first PRS configuration to the indicated second PRS configuration associated with the second base station as the new active PRS configuration, and to the indicated second set of thresholds associated with the indicated second PRS configuration as the new active second set of thresholds.

[0282] 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 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 WTRU, UE, terminal, base station, RNC, or any host computer.

[0283] 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."

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

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

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

[0287] 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 that may affect the processes and / or systems and / or other technologies described herein, 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.

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

[0289] The present disclosure is not limited in terms of the perspective of the specific embodiments described in this application, and these embodiments are intended as examples of various aspects. As will be apparent to those skilled in the art, many modifications and variations can be made without departing from the spirit and scope of the present invention.

[0290] In addition to those listed herein, functionally equivalent methods and apparatuses within the scope of the present 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. The present disclosure is limited only by the terms of the appended claims, and is limited together with the full scope of equivalents to which such claims are entitled. It should be understood that the present disclosure is not limited to a particular method or system.

[0291] Also, it should be understood that the terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the present invention. As used herein, when referred to herein, "STA" and its abbreviation "STA", "user equipment" and its abbreviation "UE" mean (i) a wireless transmission and / or reception unit (WTRU) such as the described infrastructure, (ii) any of some embodiments of the WTRU such as the described infrastructure, (iii) in particular, a wireless and / or wired (e.g., tetherable) device configured to have some or all of the structure and functions of the WTRU such as the described infrastructure, (iii) a wireless and / or wired device configured to have less structure and function than all of the WTRU such as the described infrastructure, or (iv) others. Details of exemplary WTRUs that can represent any of the WTRUs listed herein are provided below with respect to FIGS. 1A to 1D, FIG. 2, and FIG. 3.

[0292] In certain 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.).

[0293] 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 considered “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 considered “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.

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

[0295] 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 words and / or phrase presenting two or more alternative terms in the specification, claims, or drawings should be understood as construing 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 possibilities 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", 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" or "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.

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

[0297] 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 fully explainable and enabling 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.

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

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

[0300] Any element, action, or indication 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 multiple of", and / or "any multiple combination of", items and / or categories of items, 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. Furthermore, as used herein, the term “number” is intended to include any number, including zero.

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

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

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

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

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

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), the method receiving information indicating (1) a first positioning reference signal (PRS) configuration associated with a first cell, (2) a second PRS configuration associated with a second cell, and (3) a measurement gap (MG) configuration, Using the first PRS configuration and the MG configuration, a first PRS measurement is performed for a first transmission from the first cell, Sending a request to the first network entity (NE) associated with the first cell, including information indicating that the MG configuration will be maintained after the mobility event (ME) associated with the second cell has been executed, (1) to execute the ME associated with the second cell, and (2) to maintain the MG configuration after the ME has been executed, A method comprising: performing a second PRS measurement for the first transmission or further transmission from the first cell using the first PRS configuration and the MG configuration after the ME has been executed; and transmitting information indicating the second PRS measurement to a second NE associated with the first cell.

2. The method according to claim 1, further comprising deciding to send the request to the first cell indicating that the MG configuration will be maintained after the ME has been executed.

3. The method according to claim 1 or 2, wherein the first NE associated with the first cell and the second NE associated with the first cell are a single base station, or the first NE is a first base station and the second NE is a location management function (LMF) entity.

4. Under the condition that the second PRS measurement does not meet the PRS ME threshold, Sending a request for further MG configuration to the first NE associated with the second cell, Receiving information indicating the further MG configuration, Using the second PRS configuration and the further MG configuration, a third PRS measurement is performed on the transmission from the second cell, The method according to any one of claims 1 to 3, comprising transmitting to a second NE associated with the second cell any of the following: (1) the third PRS measurement, (2) the second PRS configuration, and / or (3) the time at which the WTRU began using the second PRS configuration.

5. The first NE associated with the first cell and the second NE associated with the first cell are a single base station, or the first NE associated with the first cell is a first base station and the second NE associated with the first cell is a Location Management Function (LMF) entity. The first NE associated with the second cell and the second NE associated with the second cell are another single base station, or the first NE associated with the second cell is a second base station and the second NE associated with the second cell is the Location Management Function (LMF) entity. The method according to claim 4.

6. The aforementioned ME is either (1) handover or (2) reselection. The method involves performing the handover or re-selection of the WTRU to the second cell. The method according to any one of claims 1 to 5, including the method described in any one of claims 1 to 5.

7. The aforementioned further information is included in the positioning service continuity report. The method includes receiving a new PRS configuration or an updated PRS configuration in response to the positioning service continuity report, wherein the new PRS configuration or the updated PRS configuration is associated with a target NE associated with the second cell or the first NE. The method according to claim 4, including the method described in claim 4.

8. The method according to any one of claims 1 to 7, wherein, after the ME is performed, the second PRS measurement is performed using the first PRS configuration and the MG configuration for the first transmission from the first cell or for any further transmission, and the first PRS measurement is performed using the first PRS configuration associated with the first cell after a data link handover in the coverage area of ​​the second cell for the first transmission from the first cell.

9. The method according to any one of claims 1 to 8, further comprising performing a further PRS measurement for a transmission from the second cell using the second PRS configuration associated with the second cell in the coverage area of ​​the first cell before the ME is performed.

10. The method according to any one of claims 1 to 9, further comprising performing a PRS measurement during the ME (1) with respect to the transmission from the first cell using the first PRS configuration of the first cell, and (2) with respect to the transmission from the second cell using the second PRS configuration of the second cell.

11. The method according to any one of claims 1 to 10, further comprising switching from a first positioning method to a second positioning method during the ME.

12. The method according to any one of claims 1 to 11, further comprising receiving information by the WTRU indicating that one or more of the PRS configurations are to be used, activated, or deactivated.

13. The further includes triggering the execution of the second PRS measurement in response to the ME, (1) The first PRS measurement uses the first PRS configuration and the MG configuration before the ME is performed, (2) The second PRS measurement uses the first PRS configuration and the MG configuration during at least the first portion of the ME, The method involves (1) performing further PRS measurements using the second PRS configuration and the second MG configuration during at least the second portion of the ME, and (2) after the ME has been performed. A method according to any one of claims 1 to 12, including the method described in any one of claims 1 to 12.

14. (1) Information associated with a first positioning operation, (2) a second positioning operation, and (3) one or more trigger conditions for starting and / or stopping the use of the second positioning operation, is received by the WTRU. The process includes initiating the use of the second positioning operation, provided that one or more of the trigger conditions are met in order to initiate the use of the second positioning operation, Performing the first PRS measurement is done using the first PRS configuration associated with the first positioning operation, Performing the second PRS measurement uses the second PRS configuration associated with the second positioning operation. The method according to any one of claims 1 to 13.

15. In response to the ME, the further includes triggering the execution of the second PRS measurement using the second PRS configuration associated with the second positioning operation, Performing the first PRS measurement means (1) before the ME is performed and (2) during at least the first portion of the ME, using the first PRS configuration. Performing the second PRS measurement using the second PRS configuration (1) during at least the second portion of the ME, and (2) after the ME has been performed. The method according to claim 14.

16. The WTRU receives report configuration information indicating multiple report configurations, wherein each of the indicated report configurations is associated with the type of trigger condition associated with the ME. To send a positioning report to the Location Management Function (LMF) entity according to the type of trigger condition associated with the ME, The method according to any one of claims 1 to 15, further comprising:

17. The method according to claim 16, wherein the type of trigger condition associated with the ME includes any of the following: (1) a speed-related trigger condition associated with the WTRU, (2) a velocity-related trigger condition associated with the WTRU, (3) a direction-related trigger condition for movement associated with the WTRU, (4) an orientation-related trigger condition associated with the WTRU, (5) an environment-related trigger condition associated with the WTRU, (6) an indoor / outdoor state-related trigger condition associated with the WTRU, and / or (7) an adjacent cell detection / discovery-related trigger condition.

18. The method according to claim 16, wherein the first reporting configuration among the plurality of reporting configurations described above includes first periodicity information, and the second reporting configuration among the plurality of reporting configurations described above includes second different periodicity information.

19. A wireless transmit / receive unit (WTRU) comprising a processor, a transceiver, and a memory, configured to perform the method described in any one of claims 1 to 18.

Images