Method and apparatus for high-efficiency positioning in wireless communication systems

Abstract

This invention provides a method and apparatus for high-efficiency positioning in a wireless communication system, specifically a method, apparatus, and system for determining and transmitting positioning information in a wireless communication network. For example, a method for wireless communication includes: receiving configuration information associated with a set of positioning configurations and small data transmission (SDT); determining, based on the configuration information, that at least one positioning configuration in the set of positioning configurations meets positioning requirements and is associated with a payload size less than a data volume threshold (DVT) associated with the SDT; selecting from the at least one positioning configuration a positioning configuration associated with a payload size closest to the DVT; performing a positioning measurement based on the selected positioning configuration; and transmitting a measurement report using uplink resources for the SDT based on the selected positioning configuration and the positioning measurement.

Description

[0001] This application is a divisional application of Chinese Patent Application No. 202180082064.9, filed on October 14, 2021, entitled “Method and Apparatus for High-Efficiency Positioning in a Wireless Communication System”, the contents of which are incorporated herein by reference.

[0002] Cross-references to related applications

[0003] This application claims priority and interest in U.S. Provisional Application No. 63 / 091,399, filed October 14, 2020, U.S. Provisional Application No. 63 / 134,331, filed January 6, 2021, U.S. Provisional Application No. 63 / 167,985, filed March 30, 2021, and U.S. Provisional Application No. 63 / 227,496, filed July 30, 2021, the entire contents of each of these applications are incorporated herein by reference as if their entire contents were fully set forth herein for all applicable purposes. Background Technology

[0004] The 3GPP (3rd Generation Partnership Project) standard (e.g., 3GPP Release 16) specifies downlink location methods, uplink location methods, and downlink and uplink location methods.

[0005] In the downlink positioning method, positioning reference signals (PRS) are sent from multiple transmit / receive points (TRPs) of the wireless communication network to the WTRU. The WTRU observes the multiple reference signals and measures the time difference of arrival between a pair of PRSs. The WTRU then returns the measured reference signal time difference (RSTD) to the location management function (LMF). Additionally, the WTRU can return the measured reference signal received power (RSRP) for each PRS. Based on the returned measurements, the LMF positions the WTRU. Alternatively, the WTRU can report the RSRP for an angle-based downlink (DL) positioning method.

[0006] In uplink positioning methods, the WTRU transmits a Sounding Reference Signal (SRS) configured for positioning by Radio Resource Control (RRC) signaling to the Receiver Point (RP) or TRP. For timing-based methods, the TRP measures the relative time of arrival (RTOA) with respect to the received SRS signal and reports the measured value to the LMF. The WTRU can report the RSRP with respect to the SRS. In angle-based uplink positioning methods, the RP or TRP measures the angle of arrival and reports it to the LMF.

[0007] In both the uplink and downlink localization methods, the WTRU measures the Rx-Tx time difference between the received PRS and the transmitted SRS. This Rx-Tx time difference is reported to the LMF. The WTRU can also report the RSRP measured for the PRS, and the TRP is used to calculate the Rx-Tx difference between the received SRS and the transmitted PRS.

[0008] "DL positioning method" can refer to any positioning method that requires a downlink reference signal (such as PRS). In such positioning techniques, the WTRU can receive multiple reference signals from the TP and measure the DL RSTD and / or RSRP. Examples of DL positioning methods include DL-AoD or DL-TDOA positioning.

[0009] "UL positioning method" can refer to any positioning technique that requires an uplink reference signal (such as an SRS for positioning). In such techniques, the WTRU can transmit the SRS to multiple RPs or TRPs, and these RPs or TRPs measure the UL RTOA and / or RSRP. Examples of UL positioning methods include UL-TDOA or UL-AoA positioning.

[0010] "DL and UL positioning methods" can refer to any positioning method that requires both uplink and downlink reference signals for positioning. In one example, the WTRU transmits the SRS to multiple TRPs, and the gNB measures the Rx-Tx time difference. The gNB can measure the RSRP for the received SRS. The WTRU measures the Rx-Tx time difference for the PRS transmitted from the multiple TRPs. The WTRU can measure the RSRP for the received PRS. The Rx-Tx difference, along with the RSRP that may be measured at the WTRU and the gNB, are used to calculate the round-trip time. Here, the Rx and Tx differences refer to the difference between the arrival time of the reference signal transmitted by the TRP and the transmission time of the reference signal transmitted from the WTRU. An example of DL and UL positioning methods is multiple round-trip time (RTT) positioning.

[0011] DL-based positioning (and possibly DL and UL positioning) is WTRU-based (i.e., WTRU performs the positioning) or WTRU-assisted (the network uses measurement reports sent from the WTRU to perform positioning operations).

[0012] In various implementations, the term "network" includes AMF, LMF, and / or NG-RAN. Summary of the Invention

[0013] The embodiments disclosed herein generally relate to wireless communication networks. For example, one or more embodiments disclosed herein relate to methods, apparatus, and systems for determining and transmitting location information (e.g., geographic location, location configuration, location measurements, and / or measurement reports for location) in a wireless communication network. Various embodiments and methods can be implemented in a wireless transmit / receive unit (WTRU) within a wireless communication network (e.g., a cellular network) in low-power states (such as low-power connection states, idle states, and / or inactive states).

[0014] In one implementation, a method for wireless communication implemented in a WTRU includes: receiving configuration information associated with a set of location configurations and small data transmission (SDT); determining, based on the configuration information, that at least one location configuration in the set of location configurations meets a location requirement and is associated with a payload size less than a data volume threshold (DVT) associated with the SDT; selecting from the at least one location configuration a location configuration associated with a payload size closest to the DVT; performing a location measurement based on the selected location configuration; and transmitting a measurement report using uplink resources for the SDT based on the selected location configuration and the location measurement.

[0015] In one implementation, a method for wireless communication implemented in a WTRU includes: receiving auxiliary data comprising one or more Positioning Reference Signal (PRS) configurations, each PRS configuration including a measurement configuration and / or a measurement reporting configuration. At least one of the PRS configurations may be indicated to meet a minimum accuracy requirement. The method may further include: transmitting an indication (e.g., to a gNB) of the payload size (of the measurement reports) associated with the one or more PRS configurations. The method may include: (e.g., from the gNB) receiving a Small Data Transmission (SDT) configuration, the SDT configuration including a Data Volume Threshold (DVT) for the SDT (e.g., indicating a maximum payload size for the SDT). If at least one of the received PRS configurations indicated to meet the minimum accuracy requirement has a payload size smaller than the associated payload size of the DVT for the SDT, the method may include: selecting from the at least one PRS configuration meeting the minimum accuracy requirement a PRS configuration with an associated payload size closest to the associated payload size of the DVT for the SDT; and performing a PRS measurement using the SDT (e.g., in an inactive state) based on the selected PRS configuration and sending a measurement report (to the LMF), the measurement report indicating the selected PRS configuration and the DVT for the SDT. If none of the PRS configurations indicated to meet the minimum accuracy requirement has an associated payload size smaller than the associated payload size of the DVT for the SDT, the method may include: sending a connection request (e.g., to the gNB to transition to a connected state to enable the transmission of measurement reports). Attached Figure Description

[0016] A more detailed understanding can be obtained from the following detailed description, which is given by way of example in conjunction with its accompanying drawings. As with the detailed description, the figures in such drawings are exemplary. Therefore, the drawings and specific embodiments should not be considered limiting, and other equally effective examples are possible and contemplated. Additionally, similar reference numerals ("ref.") in the drawings ("Figures") indicate similar elements, and wherein:

[0017] Figure 1A This is a system diagram illustrating an exemplary communication system that can be implemented in one or more of the disclosed embodiments;

[0018] Figure 1B This illustrates that, according to one implementation scheme, it is possible to Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) used within the communication system shown;

[0019] Figure 1C This illustrates that, according to one implementation scheme, it is possible to Figure 1AA system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used within the communication system shown;

[0020] Figure 1D This illustrates that, according to one implementation scheme, it is possible to Figure 1A A system diagram of another exemplary RAN and another exemplary CN used in the communication system shown;

[0021] Figure 2 This is a signaling flowchart of a 4-step RACH for a DL positioning method that transmits measurement reports during inactivity, according to one implementation scheme.

[0022] Figure 3 This is a signaling flowchart of a 2-step RACH for a DL positioning method that transmits measurement reports during inactivity, according to an implementation scheme.

[0023] Figure 4 This is a signaling flowchart of a 2-step RACH for a UL positioning method that transmits measurement reports during inactivity, according to one implementation scheme.

[0024] Figure 5 This is a signaling flowchart of a 2-step RACH for a UL positioning method that transmits measurement reports during inactivity, according to one implementation scheme.

[0025] Figure 6 This is a signaling flowchart for positioning during WTRU inactive mode mobility according to one implementation, which shows PRS configuration and RNA alignment;

[0026] Figure 7 This is a signaling flowchart for location during WTRU inactive mode mobility according to one implementation, which shows SRS configuration and RNA alignment;

[0027] Figure 8 This is a signaling flowchart for positioning during WTRU idle mode mobility according to one implementation scheme, which shows PRS configuration and tracking area alignment;

[0028] Figure 9 It is a signaling flowchart of positioning during WTRU idle / inactive mode using PRS configuration and DRX cyclic alignment according to an implementation scheme;

[0029] Figure 10 It is a signaling flowchart for SRS configuration and RNA alignment for positioning during WTRU inactive mode mobility according to an implementation scheme;

[0030] Figure 11It is a signaling flowchart for trigger-based updates for SRS configuration and RNA alignment during WTRU inactive mode mobility according to one implementation scheme;

[0031] Figure 12 This is a flowchart illustrating the process of generating a measurement report according to the implementation plan; and

[0032] Figure 13 This is a diagram illustrating location measurements and reporting in inactive and connected states based on positioning requirements (e.g., accuracy requirements) and data volume thresholds for SDT. Detailed Implementation

[0033] introduction

[0034] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it should be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of, or in combination with, the embodiments and other examples expressly, implicitly, and / or inherently described, disclosed, or otherwise provided (collectively, the “Provided”) herein. Although various embodiments are described and / or claimed herein, in which apparatuses, systems, devices, etc., and / or any elements thereof perform operations, processes, algorithms, functions, etc., and / or any part thereof, it should be understood that any embodiment described herein and / or protected by the claims presupposes that any apparatus, system, device, etc., and / or any element thereof is configured to perform any operation, process, algorithm, function, etc., and / or any part thereof.

[0035] Figure 1A This is a schematic diagram illustrating an exemplary communication system 100 that can be implemented in one or more of the disclosed embodiments. Communication system 100 can be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. Communication system 100 enables multiple wireless users to access such content through the sharing of system resources (including wireless bandwidth). For example, 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), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word DFT Extended OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

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

[0037] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, Internet 110, and / or other networks 112. As an example, base stations 114a and 114b may be base transceiver stations (BTS), Node Bs, evolved Node Bs, home Node Bs, home evolved Node Bs, gNBs, NR Node Bs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0038] 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 base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. 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 in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of radio services to a specific geographic area, which may be relatively fixed or changeable over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in an embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

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

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

[0041] In the implementation scheme, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which can use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0042] In the implementation scheme, base station 114a and WTRUs 102a, 102b, 102c can enable radio technology such as NR radio access, which can use New Radio (NR) to establish air interface 116.

[0043] In the implementation scheme, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for example, use a dual connectivity (DC) principle to implement both LTE and NR radio access together. Therefore, the air interface utilized by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0044] In other implementations, base station 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.11 (i.e., WiFi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rate Evolution (EDGE), and GSM EDGE (GERAN).

[0045] Figure 1ABase station 114b can be, for example, a wireless router, a home node B, a home evolution node B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in localized areas such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for use by drones), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0046] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although not explicitly stated... Figure 1A As shown, but it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113 which can utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0047] CN 106 / 115 may also act as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication 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 use the same RAT as RAN 104 / 113 or a different RAT.

[0048] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capabilities (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example, Figure 1A The WTRU 102c shown can be configured to communicate with a base station 114a that can employ cellular-based radio technology and with a base station 114b that can employ IEEE 802 radio technology.

[0049] Figure 1B This is a system diagram illustrating an exemplary WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving 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 peripheral devices 138, etc. It should be understood that, while remaining consistent with the implementation, WTRU 102 may include any sub-combination of the foregoing elements.

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

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

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

[0053] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As noted above, WTRU 102 may have multi-mode capability. For example, transceiver 120 may therefore include multiple transceivers to enable WTRU 102 to communicate via various RATs (such as NR and IEEE 802.11).

[0054] The processor 118 of WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, 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 any type of suitable memory. 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. Removable memory 132 may include a user identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 may access information from memory that is not physically located on WTRU 102 (such as on a server or home computer (not shown)) and store data in that memory.

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

[0056] 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 air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that, while remaining consistent with the implementation, the WTRU 102 may acquire location information using any suitable location determination method.

[0057] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral device 138 may include an accelerometer, electronic compass, satellite transceiver, digital camera (for photos and / or video), Universal Serial Bus (USB) port, vibration device, television transceiver, hands-free headset, etc. Modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0058] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 for reducing and / or substantially eliminating self-interference through signal processing via hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

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

[0060] RAN 104 may include evolved Node Bs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of evolved Node Bs while remaining consistent with the implementation scheme. Each evolved Node B 160a, 160b, and 160c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In the implementation scheme, evolved Node Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, evolved Node B 160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

[0061] Each of the evolved nodes B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the UL and / or DL, etc. Figure 1C As shown, evolution nodes B 160a, 160b, and 160c can communicate with each other via the X2 interface.

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

[0063] The MME 162 can connect to each of the evolved nodes B 162a, 162b, and 162c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0064] The SGW 164 can connect to each of the evolved Nodes B 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 typically routes and forwards user data packets to and from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions such as anchoring the user plane during inter-evolved Node B handovers, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0065] SGW 164 can be connected to PGW 166, which provides WTRU 102a, 102b, 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0066] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to a circuit-switched network (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and conventional landline communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) or be able to communicate with such an IP gateway, which serves as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0067] Despite WTRU in Figures 1A to 1D While described as a wireless terminal, it is conceivable that in some representative implementations, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0068] In a representative implementation, the other network 112 may be a WLAN.

[0069] A WLAN in Infrastructure Basic Services Set (BSS) mode may have an access point (AP) for the BSS and one or more sites (STAs) associated with the AP. The AP may have an access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic out of the BSS. Traffic originating outside the BSS and destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA and destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative implementations, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this document.

[0070] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a 20 MHz wide bandwidth) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative implementations, such as in an 802.11 system, Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA) can be implemented. For CSMA / CA, each STA (including the AP) can listen to the primary channel. If the primary channel is listened to / detected and / or determined to be busy by a particular STA, that STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0071] High-throughput (HT) STAs can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels to form a 40MHz wide channel.

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

[0073] 802.11af and 802.11ah support operating modes below 1 GHz. Compared to those used in 802.11n and 802.11ac, 802.11af and 802.11ah reduce channel operating bandwidth and carrier. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative implementations, 802.11ah may support instrument-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support (e.g., only support) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain a very long battery life).

[0074] WLAN systems supporting multiple channels, as well as channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as primary channels. A primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by STAs operating in the BSS (each supporting a minimum bandwidth operating mode). In the 802.11ah example, for STAs supporting (e.g., only supporting) a 1MHz mode (e.g., MTC type devices), the primary channel can be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (supporting only the 1MHz operating mode) is transmitting to the AP, the entire available band can be considered busy even if most of the band remains idle and potentially available.

[0075] In the United States, the available frequency band for 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 available bandwidth for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0076] Figure 1DThis is a system diagram illustrating RAN 113 and CN 115 according to the implementation scheme. As noted above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 may also communicate with CN 115.

[0077] RAN 113 may include gNBs 180a, 180b, and 180c, but it will be understood that RAN 113 may include any number of gNBs while remaining consistent with the implementation. Each gNB 180a, 180b, and 180c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In the implementation, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In the implementation scheme, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). Subgroups of these component carriers can be on unlicensed spectrum, while the remaining component carriers can be on licensed spectrum. In the implementation scheme, gNBs 180a, 180b, and 180c can implement coordinated multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0078] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with an scalable set of parameters. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary depending on different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying absolute time lengths).

[0079] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., evolved Node Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can use one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate or connect to gNBs 180a, 180b, and 180c, and also communicate or connect to other RANs (such as evolved Node Bs 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more evolved Node Bs 160a, 160b, and 160c. In a non-standalone configuration, evolved Node Bs 160a, 160b, and 160c can be used as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0080] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

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

[0082] AMF 182a and 182b can connect to one or more of the gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can be used as control nodes. For example, AMF 182a and 182b can be responsible for: authenticating users of WTRU 102a, 102b, and 102c; supporting network slicing (e.g., handling different PDU sessions with different requirements); selecting specific SMF183a and 183b; managing registered areas; terminating Non-Access Stratum (NAS) signaling; mobility management, etc. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the type of service used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services that rely on Ultra-Reliable Low Latency (URLLC) access, services that rely on Enhanced Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, etc. AMF 162 can provide control plane functions for switching between RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies (such as WiFi)).

[0083] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure traffic routing through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0084] UPF 184a and 184b can connect via the N3 interface to one or more of the gNBs 180a, 180b, and 180c in RAN 113. These gNBs can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0085] CN 115 can facilitate communication with other networks. For example, CN 115 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 115 and PSTN 108, or be able to communicate with such an IP gateway. Additionally, CN 115 can provide WTRUs 102a, 102b, and 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, WTRUs 102a, 102b, and 102c can be connected to DNs 185a and 185b via UPFs 184a and 184b through their N3 interfaces and their N6 interfaces with local data networks (DNs) 185a and 185b.

[0086] Given Figures 1A to 1D as well as Figures 1A to 1D The corresponding descriptions herein refer to one or more of the functions described below, which may be performed by one or more emulation devices (not shown): WTRU102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-185b, and / or any other devices described herein. An emulation device may be one or more devices configured to mimic 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.

[0087] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, the one or more simulation devices may perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. The one or more simulation devices may perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communication to perform tests.

[0088] The one or more simulation devices may perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation devices may be used in test scenarios within a test laboratory and / or non-deployed (e.g., testing) wired and / or wireless communication networks to perform testing of one or more components. The one or more simulation devices may be test equipment. Direct RF coupling and / or wireless communication via an RF circuit system (e.g., which may include one or more antennas) may be used by the simulation devices to transmit and / or receive data.

[0089] Positioning in 3GPP Release 16

[0090] 3GPP Release 16 for NR (New Radio) supports positioning for RRC_CONNECTED mode. During idle or inactive modes, the positioning process or WTRU behavior is unknown.

[0091] To reduce power consumption, the WTRU needs to be in an inactive or idle mode. Furthermore, the recent demand for centimeter-level accuracy in IIoT (Industrial Internet of Things) applications requires both high accuracy and low latency during positioning. This specification discloses methods and apparatuses that meet the requirements of high accuracy and low latency even when the WTRU is in an inactive / idle mode.

[0092] The current 3GPP specifications do not specify the configuration of reference signals for positioning during idle and inactive modes. Furthermore, the process by which the WTRU obtains reference signal configuration or measurement reports is unclear. IIoT devices (such as sensors or cameras) may unexpectedly move from their current location; for example, a sensor might be removed from its base and carried to a different area by floods or strong winds. Therefore, positioning during inactive / idle modes requires mobility support to reduce latency during positioning. Additionally, IIoT applications may need to support a large number of IIoT devices, thus requiring support for simultaneous positioning.

[0093] In this document, "SRS for location" refers to SRS signaling / transmission for location. Resources for SRS for location may be defined by RRC (e.g., signaling notification). Version 16 specifies the set of SRS resources configured for location and SRS resources. However, as used in this disclosure, "SRS for location" or "SRS" may include at least one of the following:

[0094] ● SRS configured under SRS-PosResourceSet-r16 and SRS-PosResource-r16 in [2]

[0095] ● SRS configured under SRS-ResourceSet and SRS-Resource in [2]

[0096] ● SRS not configured under SRS-PosResourceSet-r16 and SRS-PosResource-r16 in [2]

[0097] ● SRS not configured under SRS-ResourceSet and SRS-Resource in [2]

[0098] ● SRS not associated with SRS-PosResourceSet-r16, SRS-PosResource-r16, SRS-ResourceSet, or SRS-Resource in [2]

[0099] ● Associated uplink reference signal used for positioning

[0100] ● DM-RS for uplink

[0101] ●PTRS for uplink

[0102] For the sake of brevity, the SRS used for positioning in this document is referred to as "SRSp", and the PRS or SRS used herein are not limited to RS used for positioning. The methods and apparatus disclosed herein can be applied to or used with any DL or UL reference signal.

[0103] Configuration and WTRU behavior during the RACH process

[0104] Trigger for location

[0105] Location Configuration

[0106] The positioning configuration may include a set of information related to positioning measurements and / or SRSP transmission. The positioning configuration may include one or more of the following types of information:

[0107] ● One or more positioning methods are used (e.g., DL-TDOA (Time Difference of Arrival), UL-TDOA, DL-AoD (Angle of Departure), UL-AoA (Angle of Arrival), Multiple RTT).

[0108] ●PRS Configuration

[0109] ●SRSp Configuration

[0110] ● Uplink resources used for reporting location measurements (e.g., Physical Random Access Channel (PRACH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH))

[0111] ● One or more thresholds used to determine the quality of positioning measurements

[0112] ● Positioning operation mode (e.g., initial positioning operation mode)

[0113] PRS resource configuration may include any one or more of the following:

[0114] ●PRS Resource ID

[0115] ● PRS sequence ID or other ID used to generate the PRS sequence

[0116] ●PRS resource element offset

[0117] ●PRS resource slot offset

[0118] ●PRS symbol offset

[0119] ●PRS Quasi-Co-location Information (QCL)

[0120] ●PRS Resource Set ID

[0121] ● List of PRS resources in this resource set

[0122] ● Number of PRS symbols

[0123] ●Silence mode for PRS, silence parameters such as repetition factor, silence options

[0124] ●PRS resource power

[0125] ●Periodicity of PRS transmission

[0126] ● Spatial direction information transmitted by PRS (e.g., beam information, transmission angle)

[0127] ● Spatial direction information received by the UL Reference Signal (RS) (e.g., beam ID, angle of arrival used to receive the UL RS)

[0128] SRSp resource configuration may include at least one of the following:

[0129] ●Resource ID

[0130] ● Comb-shaped offset value, cyclic shift value

[0131] ● Starting position in the frequency domain

[0132] ● Number of SRSp symbols

[0133] ● Shifting in the frequency domain for SRSp

[0134] ●Frequency hopping mode

[0135] ● The type of SRSp (e.g., aperiodic, semi-persistent, or periodic).

[0136] ● The sequence ID used to generate SRSp or other IDs used to generate SRSp sequences.

[0137] ● Spatial relation information indicating which reference signal the SRSp is spatially related to.

[0138] ●Resource Set ID

[0139] ● List of SRSp resources in the resource set

[0140] ●Transmission power related information

[0141] ● Path loss reference information, which may include an index for the synchronization block (SSB), channel state information reference signal (CSI-RS), or PRS.

[0142] ●Periodicity of SRSp transmission

[0143] ●Spatial direction information transmitted by SRSp (e.g., beam information, transmission angle)

[0144] ● Spatial direction information received by DL RS (e.g., beam ID and angle of arrival used to receive DL RS)

[0145] As part of its configuration, the WTRU can receive information related to the cell ID, global cell ID, or TRPID associated with the PRS. For example, the TRP transmitting the PRS is identified by the TRP ID, which can belong to the cell identified by the cell ID. The WTRU can be configured with timing information, such as the system frame number (SFN) offset for PRS or SRSp transmission. The offset is introduced to prevent the WTRU from receiving overlapping PRS in the time domain.

[0146] In one approach, the WTRU can be configured with a measurement gap to receive PRS from the network.

[0147] Positioning operation mode and conditions for the occurrence of positioning mode

[0148] In one implementation, the WTRU can be configured, determined, or instructed to perform positioning measurements in an RRC idle mode and / or an RRC inactive mode. For example, one or more positioning operation modes can be used. In a first positioning operation mode, when the WTRU is in an RRC connected mode, the WTRU can perform positioning measurements and reporting; in a second positioning operation mode, the WTRU can perform positioning measurements and reporting in one or more RRC connected states (e.g., connected, inactive, and idle). One or more of the following may be applied:

[0149] ●WTRUs can indicate to the LMF their ability to support positioning operation modes. For example, a first WTRU can indicate its ability to support only the first positioning operation mode, while a second WTRU can indicate its ability to support both the first and second positioning operation modes.

[0150] ● The positioning operation mode can be configured or indicated (e.g., by LMF).

[0151] ● The positioning operation mode can be determined based on the WTRU's power status. For example, if the WTRU is in a low-power state (e.g., the remaining battery level is below a threshold), the WTRU can perform a first positioning operation mode (e.g., performing positioning measurements and reporting only in RRC connected state); otherwise, the WTRU can perform a second positioning operation mode (e.g., performing positioning measurements and reporting at least in RRC connected / inactive state or RRC connected / inactive / idle state).

[0152] ● The location operation mode can be determined based on the application type (or usage scenario), which can be at least one of enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), IIoT, public safety, V2X, and massive machine-type communication (mMTC).

[0153] ○ Application type can be used interchangeably with usage scenario, traffic type, device type, target QoS, QoS, requirements, and WTRU category.

[0154] The first positioning operation mode can be used for application types that may not require high reliability and / or low latency, while the second positioning operation mode can be used for application types that may require high reliability and / or low latency.

[0155] ● The positioning operation mode can be determined based on the availability of other positioning signals (e.g., Global Navigation Satellite System (GNSS) or WiFi signals). For example, a first positioning operation mode can be used when another positioning signal (e.g., GNSS) is available, while a second positioning operation mode can be used when the other positioning signal is unavailable.

[0156] In this scenario, assuming the WTRU is in an inactive or idle RRC state, adequate positioning accuracy can be achieved even without a RAN-based positioning method.

[0157] ● The positioning operation mode can be determined based on the accuracy of positioning measurements. Positioning measurement accuracy can be used interchangeably with positioning measurement reliability and positioning measurement quality.

[0158] In one example, if the positioning measurement accuracy (e.g., the RSRP level measured by PRS) is below a threshold, the WTRU can execute a first positioning operation mode; otherwise, the WTRU can execute a second positioning operation mode.

[0159] For example, if a line-of-sight (LoS) path exists for positioning measurements, the WTRU can execute the first positioning operation mode; otherwise, the WTRU can execute the second positioning operation mode.

[0160] ○ Positioning measurement accuracy metrics may include at least one of RSRP, L1-RSRP, the presence of the Loss path, beam quality, and the number of beams used for PRS transmission.

[0161] The WTRU can switch positioning operation modes when one or more predefined conditions are met. For example, when the positioning measurement accuracy is below a threshold, the WTRU can execute the first positioning operation mode. When the positioning measurement accuracy improves and exceeds the threshold, the WTRU can switch to the second positioning operation mode.

[0162] ●WTRU can (e.g., request LMF) to switch from the first positioning operation mode to the second positioning operation mode.

[0163] DRX is used to determine when to wake up in order to perform positioning measurements.

[0164] In one approach, the WTRU can be woken up for a positioning event in the DRX (referred to as a DRX positioning event) to perform measurements and / or report positioning-related data. The DRX positioning event may include: an on-duration period, a subgroup of DRX off-cycles, a subgroup of on-duration periods where the WTRU identification has been determined to be signaled during the on-duration period (e.g., in a P-RNTI or Power Saving RNTI (Radio Network Temporary Identifier)), and / or a subgroup of on-duration periods where the WTRU has already received a wake-up signal.

[0165] A WTRU can be configured with a specific RNTI or a group of RNTIs, which can be used to instruct the WTRU (or a group of WTRUs) to wake up in order to perform location measurements and / or reporting. The WTRU can determine the configuration of the PRS or SRSp (including the applicable resource set, resource, and sequence ID content) from the received RNTI, the PDSCH transmission addressing that RNTI, or the paging message itself. The WTRU can also receive uplink grants and configurations to provide associated location reports.

[0166] In the inactive state, the WTRU can monitor the PDCCH during the on-time of addressing the I-RNTI or C-RNTI to receive indications of positioning.

[0167] When a location indication is received during a paging event, the WTRU can determine the relevant configuration for the PRS or SRSSp, perform the relevant location measurements, and / or report the relevant location or location report (as part of the PUSCH transmission during the RACH process or as authorization regarding the configuration applicable to the current serving cell).

[0168] In idle / inactive mode, the WTRU initiates the localization process based on the reception / detection of localization-related triggers.

[0169] In various implementations, the WTRU can receive triggers for initiating a positioning process for different RAT-dependent positioning methods (e.g., DL-based, UL-based, or UL and DL-based positioning) while remaining in an idle / inactive mode. For example, the triggers received / detected by the WTRU may contain information about the WTRU ID, the identifier of the positioning method, and the identifier of the selected / activated PRS / SRSp configuration. Before transitioning or while operating in idle / inactive mode, the WTRU can receive configurations related to the positioning method (including PRS / SRSp (pre-)configuration).

[0170] The triggering conditions for initiating a location operation (e.g., DL PRS measurement or SRSp transmission) and / or receiving PRS / SRSp configuration for a WTRU in idle / inactive mode can be one or more of the following:

[0171] ● Higher-level / Application Triggering: For example, in the context of WTRU-based positioning, a higher level within the WTRU can trigger the reception of PRS configuration (e.g., auxiliary information in the SIB) or trigger the transmission of a request message for receiving PRS / SRSp configuration. In this case, for example, if the WTRU is pre-configured with a PRS / SRSp configuration and that pre-configured PRS / SRSp is valid when triggered by a higher-level function (e.g., the PRS / SRSp configuration can be considered valid if the timing and / or cell area list information associated with the PRS / SRSp configuration is within the valid time and / or valid cell area boundary), the WTRU can use the existing PRS / SRSp configuration for positioning. Otherwise, the WTRU can send an indication message requesting PRS / SRSp configuration to the LMF / RAN.

[0172] ● Network triggering: For example, in the case of WTRU-assisted positioning, triggers for receiving PRS configuration and / or for initiating DL PRS measurements can be received from the LMF or RAN in a core network (CN) paging message or System Information Block (SIB). Similarly, for example, triggers for receiving SRSp configuration and / or for initiating UL SRSp transmissions can be received from the RAN in a RAN paging message or SIB.

[0173] ●SIB: For example, in idle / inactive mode, WTRU can be triggered by SIB-based reception to receive PRS / SRSp configuration or to update existing PRS / SRSp.

[0174] ● Paging: For example, upon receiving a CN or RAN paging message, the WTRU can be triggered to initiate a PRS measurement or SRSp transmission.

[0175] In WTRU-based positioning, when in idle / inactive mode and receiving a trigger from a higher layer / application, the WTRU can apply the received / available PRS configuration to DL-based positioning, the SRSp configuration to UL-based positioning, or both PRS and SRSp to UL- and DL-based positioning. For DL ​​positioning, the WTRU can directly provide the upper layer with a measurement report determined by measuring the downlink PRS. For UL-based and UL- and DL-based positioning, the WTRU can receive the measurement report from the RAN when sending the SRSp. The received measurement report and any calculated positioning information are then sent to the upper layer.

[0176] In WTRU-assisted positioning, a trigger requesting WTRU location can be received from the LMF, and the WTRU can apply the received / available PRS configuration to DL-based positioning, the SRSp configuration to UL-based positioning, or both PRS and SRSp to UL- and DL-based positioning. For DL-based positioning, the WTRU can send a measurement report to the LMF determined by measuring the downlink PRS. For UL-based and UL- and DL-based positioning, the WTRU can transmit the SRSp to the RAN, which then forwards the measurement report to the LMF.

[0177] Using the above method, the WTRU can initiate the positioning process during idle or inactive modes, thereby allowing the WTRU to reduce power consumption.

[0178] Configure / Reconfigure

[0179] Configuration for receiving SRSp or PRS in idle or inactive mode

[0180] The WTRU can determine and receive the configuration associated with location measurements and reporting from a stored configuration that is part of the WTRU context, based on broadcast signaling, and / or by requesting such configuration during a RACH procedure. If the configuration of location measurement resources (e.g., PRS, SRSP, and / or associated parameters and sequence IDs) is known to the WTRU, the WTRU can report the associated location measurements, the WTRU location, and / or the location report portion of the RACH procedure, or authorization (CG) regarding the configuration applicable to the serving cell. If the WTRU does not have such a configuration, the WTRU can initiate a new RACH procedure to obtain the configuration associated with location measurements and reporting.

[0181] The WTRU can obtain resource configurations for the PRS and / or SRSp in Msg2, Msg4, or MsgB. The WTRU can perform location measurements and then report these location measurements (e.g., WTRU location or location-related measurements in WTRU-assisted mode) in a portion of Msg3 / A, authorized by the gNB and provided by a portion of MsgB or Msg4, authorized by the gNB after the RACH process is completed (e.g., Msg 5), and / or authorized by the uplink configuration.

[0182] The configuration for location measurement may also include a sequence ID for the PRS and / or SRSP, which can be unique for the WTRU or for any WTRU using the same PRACH resource. In the absence of such a sequence ID, the WTRU may use a previously used sequence ID (e.g., the sequence ID used in connected mode or the last used sequence ID), a default sequence ID, and / or a random sequence ID, which may be determined from the WTRU identity or resource identity (e.g., I-RNTI, C-RNTI, RA-RNTI, MsgB-RNTI, small data RNTI, paging RNTI, or CS-RNTI).

[0183] The WTRU can also combine the configuration received by broadcast signaling with the configuration obtained using a paging or RACH procedure to determine the complete configuration of the PRS or SRSSp (including applicable resources and sequence IDs). For example, broadcast signaling can indicate the allocation of location resources, while paging indications (e.g., in the Physical Downlink Shared Channel (PDSCH) or Physical Downlink Control Channel (PDCCH)) can include remaining WTRU-specific parameters for location (e.g., sequence ID, scrambling identity, security key). Broadcast signaling can also provide a minimum subgroup of the configuration required to obtain the remaining configuration (e.g., in the PDSCH following part of a paging or RACH procedure).

[0184] In one implementation, the WTRU can be configured with a scrambling ID, which the WTRU can use to descramble the PRS sequence. This scrambling ID can be used by the network to randomize the PRS sequence, such that if the number of WTRUs the network attempts to locate is large, the network can use the scrambling ID to randomize the PRS sequence, allowing only WTRUs configured with the scrambling ID to descramble the PRS. If a WTRU does not have a scrambling ID and attempts to descramble the PRS, the resulting PRS will be noise.

[0185] How to obtain time advance for SRSp

[0186] The WTRU can obtain the TA (Timing Lead) for SRSSp transmission from the RACH procedure. The WTRU can receive the TA in message 2 sent from the network during a 4-step RACH procedure. Alternatively, if a 2-step RACH is performed instead of a 4-step RACH, the WTRU can assume that it has a TA of zero. This assumption is reasonable because a RSRP high enough for the measured SSB to allow for a 2-step RACH indicates that the WTRU is close to the TRP and does not need to perform timing adjustments. Therefore, the WTRU can assume that the TA is almost zero. Furthermore, the WTRU can receive idle / inactive mode-specific TAs for SRSSp transmission in the PDCCH or PDSCH. The WTRU can receive TAs associated with SRSSp transmission in RRCRelease, RRC, or MAC-CE. The WTRU can determine which TA to apply before the SRSSp transmission for accurate timing alignment.

[0187] Configuration messages for location

[0188] The WTRU can receive configuration messages for positioning (e.g., SRS, PRS, and / or configuration of resources applicable to positioning reporting) as part of an RRC release message, as part of a WTRU context transport, or in an RRC or LTE Positioning Protocol (LPP) configuration message, for example, during transition to an inactive state or within the inactive state itself. Such configuration messages can be received in connected mode. Such configuration messages can be received in an inactive state in Msg4 or MsgB or in any PDSCH transport. Configuration messages (RRC or LPP messages) can contain at least one or more of the following: resource allocation for SRS, resource allocation for PRS, indication of which Small Data Transmission (SDT) resources are applicable for reporting positioning reports (e.g., CG and / or RACH resources), on-demand or temporary positioning resources or reference signals, and / or resource allocation for resources used for reporting positioning reports.

[0189] WTRU requests for configuration messages or resources

[0190] For example, when inactive, the WTRU may request a configuration message for positioning. The WTRU may include such a request as part of an RRC message (e.g., a standalone RRC recovery request, or part of a recovery reason indicated as an RRC recovery request). The WTRU may include such a request as part of MsgA, Msg3, a context transfer message, or a CG transfer. In one method, the WTRU may include such a request for positioning configuration and / or for resources used for positioning if at least one of the following is satisfied:

[0191] - If the WTRU does not have the resources for transmitting location resources. For example, if the WTRU does not have a PUSCH authorization or if the available CG becomes invalid (e.g., due to moving to a different cell, associated TA timer timeout, and / or release of CG configuration), the WTRU may include such a request.

[0192] - After moving to a different serving cell or a different RNA (e.g., a cell in a different RAN notification region (RNA) or tracking region).

[0193] - When a timer expires: For example, if a TA timer associated with a CG used for reporting location has expired or is about to expire, the WTRU can request resources for location. Alternatively, the WTRU can start a timer when it receives PUSCH resources (e.g., a CG) for transmitting location reports. The WTRU can transmit location reports while such timers are running and can stop reporting after the timer expires.

[0194] The WTRU may request resources for transmitting location reports, SRSp, and / or location-related reference signals. Specifically, since such needs may not be reflected in the Buffer Status Report (BSR), resources can be requested using explicit indications (e.g., RRC or LPP messages, such as configuration request messages). The WTRU may want to transmit such location measurement reports or may trigger transmission of such reports when it does not have UL resources on which it can transmit them, for example, after a previous transmission.

[0195] In one approach, WTRU can indicate such a need for uplink location resources as part of a BSR or as part of a small data BSR MAC CE. The WTRU can be configured with logical channels (LCH), logical channel groups (LCG), and / or data radio bearers (DRBs) associated with the transmission of location report bits, which can be treated as small data by the WTRU. The WTRU can report that it has new small data (e.g., a location report) ready to be transmitted to the network as part of a BSR or in a small data BSR MAC CE. The WTRU can trigger a new BSR (or small data BSR) when generating new small data or a location report for transmission. If the WTRU already has valid UL-SCH resources for containing a BSR MAC CE, the WTRU can multiplex the BSR MAC CE on it. For example, if the WTRU already has buffered data suspended from other non-SDT DRBs, the WTRU does not need to trigger a BSR to request UL resources for transmitting the location report. Instead, the WTRU can simply append a request for UL resources for transmitting the location report to the BSR that will be transmitted for the already suspended buffered data.

[0196] In addition, the WTRU may cancel a pending small data BSR when or after at least one of the following: (1) all small data is contained in the SDT resource, (2) when / after the SDT BSR MAC CE is contained in the PDU, if no other small data is buffered, (3) during the transmission of subsequent small data transmission (transmission of another small data transmission after the transmission of the initial small data PDU containing the BSR MAC CE, possibly on a different SDT resource), (4) the UE receives a HARQ-ACK value equal to the “ACK” for the transmitted PDU containing the multiplexed BSR MAC CE, and / or (5) after receiving an uplink grant for subsequent small data transmission. For example, the WTRU may cancel the SDT BSR when switching to connected mode (e.g., including the reception of an RRC recovery request or RRC connection recovery / (re)establishment message). If the WTRU still has pending SDT BSRs or location reports to be sent, the WTRU may trigger a scheduling request (SR) in connected mode. If the SDT BSR MAC CE is a padding BSR, the WTRU can cancel the SDT BSR MAC CE if there are no other accompanying data bits in the PDU and / or if there are data bits from a non-SDT DRB or LCH. When an SDT BSR is triggered and the WTRU does not have any valid UL-SCH resources for transmitting the SDT BSR, the WTRU can initiate a new RACH procedure. The WTRU can be configured with mapping constraints (e.g., LCP mapping constraints or UL-SCH resource types on which BSRs can be transmitted), so that if the WTRU satisfies the configured mapping constraints, the WTRU only multiplexes the SDT BSR on the resource.

[0197] The WTRU can indicate the intention to transmit the SRSp in a small data transmission before the SRSp. For example, the WTRU can indicate the intention to transmit the SRSp within a portion of the MsgA, msg1, msg3, or PUSCH transmission. The WTRU can then transmit the SRSp on the configured resources. The WTRU can transmit the SRSp as part of a CG resource configured for small data transmission. The WTRU can multiplex the SRS and other channels (such as PUCCH or PUSCH) within the CG resource configured for small data transmission.

[0198] Configuration

[0199] In idle / inactive mode, the WTRU may receive PRS / SRSp configuration (for WTRU-based positioning and WTRU-assisted positioning), requests for positioning information (for WTRU-assisted positioning), or measurement reports (for WTRU-based positioning) in one or more of the following:

[0200] Connection establishment process: For example, during or after the connection establishment or registration process, the network may provide the WTRU with at least one SRSp (pre-)configuration (e.g., via RRC signaling) and / or at least one PRS configuration (e.g., via RRC or LPP signaling) based on WTRU capability information. For example, the WTRU may receive PRS / SRSp configurations while in an RRC connected state.

[0201] SIB / On-Demand SIB: For example, the WTRU can directly receive PRS / SRSp configurations in the SIB. Alternatively, the WTRU can be triggered to use the PRS / SRSp configuration based on the cell ID received in the SIB and the mapping between the PRS / SRSp configuration configured in the WTRU and the cell ID. For example, for PRS, the WTRU can receive in the SIB an indication containing an identifier of the PRS configuration to be applied / activated for DL ​​measurements in idle / inactive mode. For example, the WTRU can receive in the SIB an indication containing an identifier of the following to be used for transmitting SRSp in UL in idle / inactive mode: an identifier of SRSp resources and other parameters (e.g., periodicity) or a resource type (e.g., RACH, Sound Reference Signal (SRS)). For example, for UL-based positioning, the WTRU can also apply pre-configured or indicated selection criteria (e.g., Listen Before Talk, Random Backoff) to mitigate interference when transmitting SRSp. For example, when a minimum SIB is received from the network (e.g., there is no location configuration information in the received SIB) and the accessibility of the location SIB using the on-demand SIB request is determined, the WTRU can be triggered to send an on-demand SIB message to the network to request PRS / SRSp configuration.

[0202] Paging (Core Network and / or RAN Paging): For example, in idle / inactive mode, the WTRU may receive a PRS / SRSp configuration while receiving a CN or RAN paging message during the on-duration of the DRX cycle. In this case, for example, the WTRU may set an inactive timer with a specific configuration time period corresponding to the reception of the PRS or SRSp configuration. For example, the duration of the inactive timer used to extend the on-duration may be set by the WTRU based on the identifier / index included in the paging message (e.g., different identifiers may be used for PRS or SRSp) or based on the type of paging message (e.g., CN paging or RAN paging). In one example, the WTRU may receive an activation message in a RAN paging message for transmitting an SRSp or a measurement report for WTRU-based positioning. As another example, the WTRU may receive a request for location / positioning information from the LMF in a CN paging message. In RAN paging messages and / or CN paging messages, the WTRU may determine the corresponding action (e.g., activation of SRSp transmission or measurement of DL PRS) based on the identifier / index associated with the action included in the RAN / CN paging message or based on the implicit signaling sent in the paging message (e.g., receiving a first paging message and then receiving a second paging message within a specific time period).

[0203] Initial Access Message: For example, the WTRU may receive one or more of the following in message 2 / 4 (during a 4-step RACH process) or in message B (during a 2-step RACH process):

[0204] ●PRS / SRSp Configuration: For example, the WTRU may receive one or more of the PRS / SRSp configuration parameters and / or PRS / SRSp identifiers (e.g., when receiving an instruction to select a pre-configured PRS / SRSp).

[0205] ●PRS: For example, a WTRU can receive a PRS from one or more TRPs associated with a gNB that receives a trigger message (e.g., Msg 1 / 3 or Msg A) from the WTRU.

[0206] ● Requests for location information (e.g., for WTRU-assisted positioning)

[0207] ● Measurement reports (e.g., for WTRU-based positioning)

[0208] When the WTRU determines that the PRS / SRSp configuration is unavailable (e.g., when triggered by a higher layer / network) or that the existing PRS / SRSp configuration is inapplicable / valid, the WTRU may send an instruction to the network requesting PRS / SRSp (re)configuration. In addition to the request for PRS / SRSp, the WTRU may also transmit SRSp and other messages, including measurement reports (e.g., for WTRU-assisted positioning), in one or more of the following:

[0209] ●Initial Access Message: For example, the WTRU may send a request for PRS / SRSp in message 1 / 3 (during the 4-step RACH process) or in message A (during the 2-step RACH process).

[0210] ●SRSp Resources: For example, WTRU can send measurement reports in resources associated with SRSp for UL+DL-based positioning.

[0211] ●TA / RNA (Tracking Region / RAN Notification Region) Update Message

[0212] ● On-demand SIB

[0213] The content of the request for PRS / SRSp configuration sent by the WTRU may include one or more of the following information:

[0214] ●WTRU ID: For example, a WTRU may include a WTRU ID assigned by a CN (e.g., Temporary Mobile Subscriber Identity (TMSI)) or RAN (I-RNTI). Alternatively, a WTRU may include a random ID selected from an ID pool configured / accessible to the WTRU. In this case, for example, the WTRU may select an ID from a different ID pool associated with different types of PRS / SRSp configurations.

[0215] ●PRS / SRSp ID

[0216] ●DRX Configuration ID

[0217] Figure 2Example of a 4-step RACH signaling flow for a DL positioning method that transmits measurement reports during inactive mode is shown. WTRU 201 receives PRS configuration 212 and location request 216 from gNB 203, which may be generated by LMF 205 (see, for example, 210 and 214). WTRU 201 measures (220) the PRS (218) transmitted by gNB 203 and returns a RACH preamble in Msg 1 (222). An uplink grant is sent to WTRU 201 in Msg 2 (224). A measurement report corresponding to the received PRS is sent in Msg 3 (226). In this example, the PRS is sent in Msg 4 (230). The measurement report (228) is sent from gNB to LMF. If the PRS is not configured by the network, the RACH preamble can be replaced with a request for PRS configuration, which may include the WTRU ID, as previously described.

[0218] Figure 3 Another example of the 2-step RACH signaling flow for the DL positioning method during inactivity mode is shown. WTRU 201 receives PRS configuration 312 and location request 316 from gNB 203, which can be generated by LMF (see 310 and 314). For example, WTRU 201 measures (320) the PRS 318 transmitted by gNB 203 and returns a RACH preamble in Msg A (322). Uplink grant 326 is sent to WTRU 201 in Msg B 326. A measurement report corresponding to the received PRS is sent back to gNB in ​​Msg A 328. This measurement report (330) is sent from gNB 203 to LMF 205.

[0219] Figure 4 Example of a 4-step RACH signaling flow for a UL positioning method that transmits measurement reports during inactive mode is shown. WTRU 201 receives a RAN paging 422 to activate the UL SRS, which can be initiated by LMF 205 (e.g., see 420). WTRU 201 returns a RACH preamble 424. Subsequently, gNB 203 returns a RAR in Msg 2 426. In Msg 3 428, WTRU transmits the SRS. gNB 203 can then measure SRSp (430) and transmit a measurement report 432 to LMF 205.

[0220] Figure 5 The image shows an example of the 2-step RACH signaling flow for the UL positioning method during inactivity mode, demonstrating measurement report transmission. No discussion is given regarding... Figure 4The signals discussed herein are similar to those in the previous section. WTRU 203 receives RAN paging 522 to activate ULSRS. WTRU transmits SRSp in Msg A524.

[0221] In idle / inactive mode, the WTRU sends a PRS / SRSp (reconfiguration) request to the network based on the validity label. Setting Instructions

[0222] In one implementation, the WTRU in inactive / idle mode can send an indication to the network requesting (re)configuration of the PRS / SRSp based on a configured validity label. For example, the WTRU may be initially configured with one or more PRS and / or SRSp configurations, which it can maintain while operating in idle / inactive mode. Different PRS / SRSp (pre-configured) configurations can be assigned identifiers. Furthermore, the WTRU can be configured with a location validity label associated with the PRS / SRSp configuration, which can also be maintained during the duration of the WTRU's idle / inactive mode. The location validity label may contain one or more of the following information / conditions:

[0223] ●Time validity: For example, a time period can be associated with individual PRS and / or SRSp (pre-configured) settings in the WTRU. Similarly, a common time period can be associated with two or more PRS / SRSp (pre-configured) settings from a set or all PRS / SRSp (pre-configured) settings configured in the WTRU. For instance, the WTRU can initialize a timer when transitioning to an idle / inactive mode and can use the PRS / SRSp configuration for positioning during the idle / inactive mode, provided the associated timer has not expired.

[0224] ● Area Validity: For example, an effective area consisting of at least one cell (e.g., determined by cell ID) can be configured in a WTRU and associated with individual PRS / SRSp (pre-configured) or a set of PRS / SRSp (pre-configured). For example, the WTRU can move within one or more cells in the effective area and can be allowed to use the PRS / SRSp (pre-configured) as long as the cell identification information (e.g., a list of cell IDs) matches the information in the effective area.

[0225] ● Allowed Exports: For example, when certain conditions are met (e.g., RSRP measurement is above a threshold, multipath with / without LoS is detected), WTRU may be allowed to export / determine the PRS / SRSp configuration based on a combination of two or more pre-configured conditions.

[0226] When triggered by a request for location information from the LMF (for WTRU-assisted positioning) or from a higher layer / application within the WTRU (for WTRU-based positioning), the WTRU can verify the conditions in the validity label to determine if the (pre-)configured PRS / SRSp is still valid. In this case, if the conditions in the validity label are met, the WTRU can use the (pre-)configured PRS / SRSp. If at least one of the conditions in the validity label is not met, the WTRU can send a request to reconfigure the PRS / SRS configuration. For example, in one or more of the methods indicated in the previous section, the WTRU can receive the (re)configured PRS / SRSp upon determining that the validity label has expired.

[0227] Using the above method, the WTRU can initiate the positioning process during idle or inactive modes, thereby allowing the WTRU to reduce power consumption while achieving high positioning accuracy.

[0228] Contextual Search

[0229] Context retrieval can be performed if the following conditions are met. For inactive states, the WTRU can persist or store the PRS and / or SRSp configuration as part of the WTRU context. Such configurations may include location resources for the PRS and / or SRSp, sequence IDs used to determine the PRS, etc. The WTRU may assume that this configuration applies to a subgroup of serving cells, such as serving cells whose context is still known at the gNB, cells within the same RNA, cells that do not require anchor relocation, etc.

[0230] When in RRC inactive / idle mode, WTRU uses the CG configuration stored in the WTRU context.

[0231] In one implementation, the WTRU in RRC inactive / idle mode uses the CG included in the WTRU context to send location information and / or measurement reports to the network, for example, using the configuration associated with the CG received when in RRC connected mode. The CG configuration (e.g., type 1 or type 2) received by the WTRU in RRC signaling may include one or more of the following: C-RNTI configuration, BWP configuration, periodicity, time offset, time allocation, and the number of HARQ processes. Additionally, the WTRU may receive one or more identifiers and validity conditions associated with the CG configuration for location using the CG when operating in RRC idle / idle mode. For example, the WTRU in RRC idle / idle mode may use the CG configuration if the associated validity conditions (e.g., validity period, TA timer, cell ID in RNA) are met. Furthermore, when one or more validity conditions are not met or expire, the WTRU in RRC idle / idle state may, for example, send a request for a new CG configuration in an RRCResumeRequest and receive the new CG configuration in, for example, an RRCRelease message. The WTRU can then send location information and / or measurement reports to the network using the received new CG configuration while remaining in the RRC idle / inactive state. Alternatively, upon receiving a new CG configuration, for example in an RRC Resume message, the WTRU can switch to RRC connected mode and then send location information and / or measurement reports to the network while in a connected state.

[0232] When operating in RRC connected mode, the WTRU can receive CG configuration in a dedicated RRC signaling message. For example, the WTRU can also receive CG configuration in an RRC Resume message under a suspendConfig configuration (e.g., in Msg B or Msg4). In this case, for example, when transitioning from RRC connected mode to RRC inactive mode or when the WTRU sends an RRC Resume Request while in an RRC inactive state, the CG configuration in the RRC Resume message can be received.

[0233] In one example, (e.g., in an RRCLease message) the CG configuration received by the WTRU may contain the same or different configuration as that received by the WTRU while in RRC connected state. In this case, the WTRU may receive the same or different identifier associated with the CG configuration used during RRC inactivity. As another example, the WTRU may receive a differential CG configuration in the RRCLease message, which may at least partially contain some configuration information common to the CG configuration received / used during RRC connected state. For example, the differential CG configuration may include increases / decreases in the amount of time / frequency resources and / or changes in periodicity relative to the previous CG configuration received during RRC connected mode. In such cases, for example, the WTRU may receive the same identifier associated with the previous CG configuration as well as incremental configuration information indicating the differential CG configuration in the RRCLease message.

[0234] The WTRU can store the received CG configuration in the WTRU context and apply the stored configuration to send one or more of the following when in RRC inactive / idle mode:

[0235] Location Service (LCS) clients request location information from the LMF (e.g., for Mobile Origin-Location Request (MO-LR) service).

[0236] -WTRU capability information (e.g., supported positioning methods)

[0237] - Requests for auxiliary information (e.g., PRS / SRSp configuration), including non-periodic or periodic requests for auxiliary data.

[0238] Location information, including the estimated / calculated WTRU location for WTRU-based positioning (e.g., for Mobile Station Termination-Location Request (MT-LR) services). Location information may be sent to the LMF either aperiodically or periodically.

[0239] - A measurement report consisting of measurements taken on the received PRS (e.g., for LMF-based positioning) can be sent aperiodically or periodically.

[0240] In addition, the WTRU can store the spatial / QCL relationships of the PRS with other RSs or channels received / determined when in RRC connected mode, such as TCI information, QCL-TypeA, QCL-TypeB, QCL-TypeC or QCL-TypeD, spatial relationships, so that it can be used based on similar RRC signaling and / or applied to validity conditions configured using CG when transitioning to RRC inactive / idle mode.

[0241] The WTRU uses the same positioning method / configuration during RRC inactive / idle mode as it does during RRC connected mode. Set the associated location method / configuration

[0242] In one implementation, when operating in RRC inactive / idle mode, the WTRU can use one or more positioning methods applied when in RRC connected mode for positioning. For example, a WTRU configured to support DL-based or UL-based positioning (i.e., triggered to perform as WTRU-based or LMF-based positioning) can use the same positioning method configured during the RRC connected state after transitioning to RRC inactive / idle mode. Alternatively, when transitioning to RRC inactive / idle mode, the WTRU can use a positioning method that may differ from the method used during the RRC connected state. In both examples, one or more configurations (e.g., PRS / SRSp configurations) associated with the positioning method applied by the WTRU in RRC inactive / idle mode may be the same as or different from the configuration applied when in RRC connected mode.

[0243] The WTRU can receive from the network, while in RRC connected mode (e.g., immediately after transitioning to RRC inactive / idle mode or before transitioning to RRC inactive / idle mode), an indication of whether it uses the same or different positioning methods and / or associated configurations when in inactive / idle mode. For example, the WTRU can receive an explicit indication, such as in an RCRelease message, regarding whether to retain or release one or more positioning methods and / or associated configurations it used while in RRC connected mode. In this case, the RCRelease message may contain an identifier of the positioning methods / configurations to be retained and / or released while operating in RRC inactive / idle mode. Alternatively, the WTRU can receive an implicit indication to retain a positioning method based on the absence of any indication that it should release a positioning method, or (b) when the same positioning method / configuration is to be continued by the network after the WTRU transitions to RRC inactive / idle mode (e.g., DL-PRS transmission). Alternatively, the WTRU can receive an implicit indication to change a positioning method based on reported changes (such as the removal or addition of a specific measurement). Examples of measurements include:

[0244] -Angle of arrival

[0245] -Time difference of arrival

[0246] -Reference signal time difference,

[0247] -Arrival time,

[0248] -PRS or RSRP, a reference signal used for positioning.

[0249] -WTRU Rx-Tx time difference,

[0250] - Measurement timestamp,

[0251] -The mass and / or quality of each measurement

[0252] - Number of paths.

[0253] Using the above method, the WTRU can initiate the positioning process during idle or inactive modes, thereby allowing the WTRU to reduce power consumption while achieving high positioning accuracy.

[0254] RACH process for positioning

[0255] For idle / inactive instances, variants of Msg A and B are included.

[0256] The WTRU can perform location measurements and report these measurements in a portion of Msg3 / A, in authorizations scheduled by the gNB and provided by a portion of MsgB or Msg4, in authorizations scheduled by the gNB after the RACH process is completed (e.g., Msg 5), and / or in authorizations configured for the uplink.

[0257] After reporting location-related measurements and / or reports during the RACH procedure, the WTRU can remain in an idle or inactive mode. For a RACH procedure initiated in idle or inactive mode for location purposes, the WTRU can include a specific RRC message in Msg3 or MsgA to indicate to the gNB the intention to perform the RACH procedure to report location data or obtain location-related configuration. The WTRU can select PRACH (Physical Random Access Channel) resources (preamble group and / or PRACH timing) to indicate to the network that the RACH (Random Access Channel) procedure is for location, for reporting location data, and / or for obtaining location-related configuration.

[0258] The WTRU can remove C-RNTIs (cell-RNTIs) or temporary C-RNTIs acquired in idle mode as part of the RACH process for location purposes, such as upon successfully reporting WTRU location or location-related reports and / or returning to DRX sleep. The WTRU can monitor the PDCCH (Physical Downlink Control Channel) addressed to such C-RNTIs, potentially for a period of time, such as until all location-related transmissions and / or transmissions of WTRU location or location reports are successfully performed.

[0259] PRACH allocation

[0260] The WTRU can provide an SRSp as part of a PRACH process, or instruct the gNB that it will transmit an SRSp as part of a RACH process. For example, this instruction can be performed by the WTRU by selecting a subgroup of PRACH resources (e.g., preambles and / or RACH timing, which can be pre-configured to instruct the gNB that the WTRU is using such RACH to position and / or transmit the SRSp portion of the RACH process). In one example, the WTRU can transmit the SRSp as part of a PUSCH transmission associated with a RACH process or a configured authorization (e.g., via punched PUSCH transmission, via appended PUSCH transmission, or at the end of a PUSCH transmission).

[0261] The correlation between RACH resources (i.e., RACH timing + preamble combination) and PRS or SRSp

[0262] The WTRU can use message 3 or message A to transmit measurement reports to the network. The WTRU can be configured with the following set of associations to determine the PRS resources received by the WTRU.

[0263] In one implementation, the WTRU can receive two sets of associations. In the first set of associations, each SSB can be associated with a RACH timing (RO). Alternatively, multiple SSBs can be associated with one RO, or multiple ROs can be associated with one SSB. In the second set of associations, information about the spatial relationship or QCL relationship between the SSB and other reference signals (such as PRS) or channels can be included. Examples of different types of QCLs can be found in 3GPP specification 38.214.

[0264] The WTRU can receive a second set of associations from the network via broadcast. The WTRU can determine a spatial filter for receiving PRS resources in message 4 or message B based on the first and second sets of associations. Alternatively, the WTRU can receive PRS configuration from the network during message 2 or message B. The WTRU can be configured, for example, to receive PRS in any one or more of the following locations:

[0265] - PRS resources in message 4

[0266] - PRS resources in message B

[0267] - PRS resources outside of message 4 or other messages

[0268] Using the above method, the WTRU can send measurement reports to the server during idle or inactive modes, thereby allowing the WTRU to reduce power consumption while achieving high positioning accuracy.

[0269] Convert to RRC_CONNECTED

[0270] The WTRU may include an indication of preference for transitioning to a connection mode. Such an indication may be transmitted via an indication portion that includes an RRC (re)establishment request, an RRC recovery request, an RRC message and / or payload indicating the preference for transitioning to a connection mode, a MAC subheader, or a MAC CE. This indication may be provided as part of MsgA, as part of Msg3, as part of Msg1 (e.g., via preamble selection), on the CG, or on the scheduling authority provided for subsequent transmissions.

[0271] In response to one or more conditions, the WTRU may include such indications of preference for switching to connected mode. In one approach, the WTRU may issue an indication if: the WTRU does not have a valid security key to transmit the payload; the payload of the location report is greater than a certain threshold; idle or inactive reporting resources do not meet the latency required to provide the location report; more accurate location measurements are needed; the payload size is greater than a threshold; and / or more granular location data / reports are needed. In one example, the WTRU may issue an indication to switch to connected mode if the RACH used to report the location report or the configured authorization (CG) periodically exceeds a threshold. The WTRU may also provide an indication to switch to connected mode if the number or size of measurement reports generated by the WTRU after receiving the PRS exceeds a threshold; if the number of measured cells exceeds a threshold; and / or if the report size exceeds the size of the PUSCH resources associated with the RACH procedure of the CG.

[0272] The WTRU may also provide such an indication after a configured or predetermined number of failed attempts to transmit location reports / data. The WTRU may also provide such an indication after a configured or predetermined timer expires. The WTRU may start such a timer on the first attempt to transmit a location report and may stop the timer upon successful transmission of the location report (e.g., upon receiving a HARQ-ACK or after receiving a DL RACH message in response to a transmission of Msg3 or MsgA).

[0273] Using the above method, the WTRU can send measurement reports to the service to achieve high positioning accuracy, while allowing the WTRU to reduce power consumption.

[0274] Security processing for location during idle mode

[0275] Secure retrieval for location during idle mode

[0276] Report data while idle when the security key has been removed.

[0277] The WTRU can use subgroups of positioning methods (e.g., uplink-based positioning, WTRU-assisted positioning, or WTRU-based positioning) in idle mode. In one approach, for example when a security key is unavailable, the WTRU can restrict the positioning method to uplink-based positioning (based on SRSp transmission) in idle mode. In another approach, the WTRU can be configured with a temporary security key as part of the RACH process (e.g., including MAC-I, possibly as part of an RRC message) to transmit WTRU location or positioning reports (as associated with WTRU-assisted DL-based positioning). Such temporary security keys can be assumed by the WTRU to be valid for a specific time period (pre-configured or indicated) or for a limited number of UL authorizations provided after Msg2, Msg4, or MsgB.

[0278] In one approach, if the security key is no longer valid, the WTRU can use an RRC message to initiate a new RACH procedure for location (e.g., RRC recovery or RRC re-establishment). The WTRU may assume that the security key is valid in the same set of serving cells known to the WTRU context (e.g., the same serving cell before transitioning from a connected state to an inactive state and / or any other cell in the same RNA). The WTRU can only use CG resources if the security key is maintained and known at the serving cell (e.g., inactive for the same serving cell or another cell in the same RNA).

[0279] In one implementation, the WTRU in idle mode determines a security key to be used for encrypting and sending location-related messages to the network. For WTRU-based positioning in idle mode, the WTRU can send a request for PRS configuration to the LMF and receive the PRS configuration in an encrypted NAS message. Similarly, for WTRU-assisted positioning in idle mode, the WTRU can receive the PRS configuration from the LMF and request location information, and send a measurement report to the LMF in an encrypted NAS message.

[0280] To determine the security key to be applied when sending / receiving location-related messages in idle mode, the WTRU can perform one or more of the following actions:

[0281] ● Reusing the security key provided by the CN: For example, the WTRU can use a security key along with a WTRU identifier provided by the CN (e.g., TMSI (Temporary Mobile Subscriber Identity), IMSI (International Mobile Subscriber Identity)), which can be received during initial access and applied in RRC connection mode. For example, the security key can be associated with a time / area restriction, which the WTRU can monitor before using the key during idle mode.

[0282] ● Exporting Security Keys: For example, the WTRU can use a configured key export algorithm and a WTRU identifier provided by the CN to export a security key to be used for transmitting / receiving NAS messages in idle mode. The WTRU can also be configured to include a location-related identifier (e.g., a PRS configuration ID) for exporting the security key.

[0283] ● Selecting a security key from a pre-configured one: For example, the WTRU can select a set of security keys from multiple pre-configured ones based on selection criteria (e.g., based on a timer and / or the cell ID in the tracking area), which can be configured by the network in the WTRU before transitioning to idle mode.

[0284] ● Retrieving Security Keys: For example, when moving within a tracking area, the WTRU can send an instruction to the network containing the WTRU identifier provided by the CN (e.g., in Msg A / Msg1) to retrieve a security key and / or initiate a security key export process. For instance, the WTRU can send this instruction to the network when it determines that a stored security key has expired or is inaccessible.

[0285] Using the above method, the WTRU can safely send measurement reports to the server during idle or inactive modes, thereby allowing the WTRU to reduce power consumption while achieving high positioning accuracy.

[0286] WTRU behavior during measurement reporting period

[0287] Resource allocation

[0288] Resource retrieval for reporting location data

[0289] Where available, if the WTRU context is known to the serving gNB and / or uplink timing is maintained (e.g., the TA (Timing Lead) value is zero or maintained by a timing alignment timer), the WTRU can use the PUSCH resources associated with the configured authorization in an inactive state. Even if the WTRU moves to a serving cell other than the one from which it received the CG configuration (in cases where that cell is part of the same RNA or tracking area), the WTRU can assume that the CG is available. Otherwise, the WTRU can initiate a RACH procedure and use the PRACH resources to report location data.

[0290] Determine the size, segmentation, and optimization of the report content.

[0291] During idle or inactive modes, the bandwidth available for uplink transmissions may be limited, and the authorized size may not be large enough to include the measurement reports generated by WTRU.

[0292] Positioning measurement payload indication

[0293] WTRU can determine the payload size of the measurement. The payload size in a positioning measurement report can be determined based on one or more of the following:

[0294] ○ Number of PRS configurations associated with the report

[0295] ○ The number of positioning measurements that meet applicable requirements (e.g., positioning measurement quality)

[0296] ○ Number of TRPs or cells associated with location measurements

[0297] ○ Number of positioning measurement methods used

[0298] ○ Number of beams used for positioning measurements

[0299] ○ The number of positioning measurement results with Loss of Path (LoS) in its measurements

[0300] ○ The number of LoS paths to be reported or other detected paths.

[0301] ○TRP ID, Cell ID, Global Cell ID, or a unique ID associated with the WTRU

[0302] ○ Timing-related information, such as RSTD associated with the received PRS pair or WTRU RX-TX time difference associated with the number of PRS received by the WTRU.

[0303] ○ Number of Rx-Tx time differences to be reported

[0304] ○ The number of RSRP values ​​associated with the path or PRS pair or WTRU RX-TX time difference

[0305] In one implementation, the WTRU may indicate its payload size for positioning measurement reporting to receive an uplink grant sufficient to carry the positioning measurement report. One or more of the following may apply:

[0306] ○ PRACH resource allocation can be used. For example, PRACH resources can be configured specifically for non-periodic positioning measurement reporting, and subgroups of PRACH resources can be associated with one or more payload sizes used for positioning measurement reporting.

[0307] Each subgroup of a PRACH resource can be associated with a payload size range.

[0308] In one implementation, WTRUs are only permitted to use PRACH resources associated with a payload size equal to or greater than their reported payload size.

[0309] When using contention-based RACH, the WTRU can determine one PRACH resource partition within a PRACH resource partition, where each PRACH resource partition can be associated with a payload size (or a range of payload sizes). For example, a first partition can support a first payload size range (e.g., <100 bytes), a second partition can support a second payload size range (e.g., 100 bytes–500 bytes), a third partition can support a third payload size range (e.g., 500 bytes–1000 bytes), and so on. When the payload size determined by the WTRU is within the first payload size range, the WTRU can begin using (or can be required to use) the PRACH resources in the first partition. If the WTRU fails to receive the RAR for a previously transmitted PRACH, the WTRU can use (or can be permitted to use) the next partition (or the partition that can support the determined payload size). In this document, this partition can be used interchangeably with the PRACH resource partition.

[0310] When using a 2-step RACH for positioning measurement reporting, RACH MsgA allocation can be based on payload size. For example, a dedicated RACH MsgA resource can be configured for non-periodic positioning measurement reporting, and subgroups of the RACH MsgA resource can be associated with payload size (or a range of payload sizes).

[0311] Compared to PUSCH resources with RACH MsgA resources associated with larger payload sizes, PUSCH resources with RACH MsgA resources associated with smaller payload sizes can use, correspond to, or determine PUSCH resources that can have a smaller number of RBs (resource blocks).

[0312] ○ Payload size can be explicitly indicated during the RACH process. For example, the WTRU can indicate its payload size for positioning measurement reporting in MsgA / Msg3 during the RACH process. The WTRU can receive PUSCH resource allocation after the RACH process is completed.

[0313] Subsequent transmission

[0314] In one implementation, when the location report or the location of the WTRU is not compatible with the PUSCH grant (as a result of the Logical Channel Priority (LCP) process), the WTRU may include indications for subsequent transmissions (e.g., MsgA, Msg3, or CG PUSCH resources). The WTRU may monitor the PDCCH addressed to the C-RNTI or I-RNTI to receive PUSCH resources, thereby performing subsequent transmissions.

[0315] The WTRU can select PRACH resources (preamble group and / or PRACH timing) based on the payload size required to transmit the location report. The WTRU can be configured by RRC or provided by broadcast signaling with a mapping between subgroups of PRACH resources and payload size (or size threshold).

[0316] If the WTRU is not compatible with the applicable reporting PUSCH resource (as a result of LCP), the WTRU can segment the location report / data. The WTRU may include a WTRU identity or a resource identity for each report segment along with the report (e.g., I-RNTI, temporary C-RNTI, C-RNTI, and / or MsgB / RA-RNTI), which can help the network schedule subsequent transmissions and / or identify and attach report segments together. In idle mode, the WTRU may select the same RACH resource (e.g., RACH timing (RO)) to transmit subsequent segments of the location report. This will allow the gNB to potentially group segments together by associating them with RA-RNTIs. In idle mode, if the WTRU remains in idle mode but has subsequent segments to transmit, the WTRU may include its identity (or a resource identity for the first segment portion of the payload) in each subsequent segment. The WTRU may include indications to segment the PUSCH payload or reserve more segments for transmission (e.g., in the MAC subheader). Such indications can be interpreted by the network as implicit requests for subsequent transmission instructions.

[0317] Segmentation / Assignment Method

[0318] In one approach, WTRU may determine the segmentation and / or allocation of reported content, as well as the reporting method, based on a configuration. This configuration may include at least one of the following:

[0319] ●WTRU is not configured with segmentation. In this case, WTRU determines at least one of the following reporting methods:

[0320] ○ The WTRU reports only a portion of the available relevant data (which may be adapted within available resources). In one implementation, the WTRU may not report receive power-related information or timing-related information for additional paths. The WTRU only reports the RSTD of the PRS received by each pair of WTRUs or the WTRU Rx-Tx time difference of the received PRS received by each WTRU. The WTRU may report the RSRP of the PRS received by the WTRU.

[0321] ○WTRU determines the content of its reports based on the payload size.

[0322] ●The WTRU is configured with multiple segments, and the WTRU determines how to segment the measurement report according to predefined segmentation rules. Segmentation schemes may include (1) a segmentation scheme in which measurement data is divided into subgroups and all measurement data is transmitted to the network, and (2) a segmentation scheme in which only some segments are transmitted. Segmentation rules may include at least one of the following rules:

[0323] ○Overhead only: WTRU can determine information related to the PRS transmission source or PRS generation, such as the cell ID from which the PRS was transmitted, the global cell ID, or the ID used to generate the PRS in a segment of the report.

[0324] ○ Timing and power information is used only for the main path: The WTRU can determine the amount of pre-configured information to include in a segment of the measurement report, such as the RSTD of the PRS received by each WTRU pair or the WTRU Rx-Tx time difference for each received PRS. The WTRU can be configured to include power-related information.

[0325] ○ Timing information for additional paths: The WTRU can determine timing-related information including additional detection paths, which are associated with each RSTD of the PRS received by each WTRU pair or the WTRU Rx-Tx time difference for each received PRS. The WTRU can be configured to include power-related information of the PRS received by the WTRU.

[0326] ○ Timing Information Only: The WTRU can determine timing-related information, such as the RSTD or WTRU Rx-TX time difference for the PRS received by the WTRU, and also includes timing-related information for additional detection paths associated with each RSTD or WTRU Rx-Tx timing difference.

[0327] ○ Power Information Only: The WTRU can determine power-related information, such as the RSRP for the PRS received by the WTRU, and also includes power-related information such as the RSRP associated with each RSTD or WTRU Rx-Tx timing difference, or the differential power compared to the reference PRS.

[0328] ○ Segmentation via TRP / Cell: The WTRU can determine timing or power-related information, such as the TRP or cell from which the PRS transmission originated. Therefore, the WTRU can segment the report based on the TRP ID, cell ID, or global cell ID.

[0329] ○ Segmentation via frequency layer: The WTRU can determine timing or power-related information, including PRS-related information, by locating the frequency layer. Therefore, the WTRU can segment the report based on the frequency layer parameters.

[0330] ○ Segmentation by PRS Resource ID: WTRU can segment reports based on PRS Resource IDs. For example, for DL ​​and UL positioning methods or positioning methods based on DL departure angles, WTRU measures timing or power-related information for each PRS. Therefore, WTRU can segment reports based on PRS Resource IDs.

[0331] Power-related information may include RSRP or differential power compared to a reference RSRP, which may be the RSRP of a reference PRS. In this disclosure, PRS, PRS beams, and PRS resources are used interchangeably. Similarly, in this disclosure, SRSp, SRSp beams, and SRSp resources are used interchangeably.

[0332] In another implementation, the WTRU may be configured with the number of segments to be reported. The WTRU may receive this configuration during the RACH process, either during Msg A, Msg 2, or Msg 4, or via paging or broadcast.

[0333] Reporting methods for segmented reports

[0334] The WTRU can assign the same identifier number to each segmented report and send them to the network accordingly. Alternatively, the WTRU can assign a different identifier number to each segmented report and send them to the network accordingly. The WTRU can send the segmented reports periodically or in a predetermined sequence. For example, segments containing overhead information (such as the cell ID or TRP ID indicating the origin of the PRS) do not need to be sent at every time. Therefore, the WTRU can be configured with measurement reporting periods during which the WTRU sends the segment containing overhead information only once. For example, if the WTRU segments the report into four segments with identifier numbers #0, #1, #2, and #3, where #0 contains overhead information and the other segments contain measurement reports, then the WTRU can send #0 once during the reporting period and send #1, #2, and #3 periodically. Each segment can contain a common report ID, allowing the network to combine the segmented reports. As previously mentioned, a WTRU may include a WTRU identity identifier or a resource identity identifier (e.g., I-RNTI, temporary C-RNTI, C-RNTI, and / or MsgB / RA-RNTI) for each report segment.

[0335] In one approach, the WTRU can periodically send reports. For example, if the WTRU segments reports into four segments with identifiers #0, #1, #2, and #3, where #0 contains overhead information and the other segments contain measurement reports, the WTRU can send the segmented reports in the following sequence: #0, #1, #2, #3, #1, #2, #3, #1, #2, #3, ... The WTRU can be configured with a segmented reporting cycle mode. Furthermore, segments can be reported repeatedly, and the WTRU can be configured to repeat each reporting segment a certain number of times. For example, if the WTRU is configured with a repetition count K = 2, the WTRU can send the segmented reports as follows: #0, #1, #1, #2, #2, #3, #3, #1, #1, ...

[0336] In one approach, the WTRU can update measurements included in a report. For example, the WTRU can indicate to the network that the content of the report has been updated by updating a tag associated with the measurement report or fragment, which indicates that the measurements included in the fragment have been updated. The WTRU can send the aforementioned tag in MsgA, Msg3, or CG PUSCH resources.

[0337] The process of segmenting LPP messages

[0338] When the payload size of the LPP messages (e.g., LPP ProvideLocationInformation) generated by the WTRU is relatively small, the WTRU can continue to perform measurements and send LPP messages while remaining inactive. However, it is possible that the data volume threshold configured when SDT is supported is limited, or the resource authorization allocated during inactive mode may not be large enough to carry the generated LPP messages (e.g., measurement reports).

[0339] To transmit larger payload sizes, the WTRU can use resources with appropriate identifiers configured for the SDT to segment and transmit measurement reports / location estimates sequentially, so that segments of received LPP messages / PDUs can be assembled at the RAN or LMF.

[0340] For example, the number of supported segments can be determined by the WTRU itself or with the assistance of LMF / gNB, based on one or more location QoS requirements (e.g., accuracy, latency) and a configured data volume threshold for SDT. During segmentation, the WTRU can use SDT to send different segments sequentially, allowing overall location information to be sent within accuracy / latency requirements while adhering to the data volume threshold for each segment.

[0341] To support the transmission of segmented LPP messages (e.g., those containing measurement reports), the WTRU can receive specific segmentation configuration information from the network (e.g., LMF and / or RAN), such as indications (e.g., identifiers, one or more markers indicating segmentation, end markers) and / or sequence numbers (e.g., in the header) for use when segmenting LPP messages / PDUs. This configuration information can be received by the WTRU in the LPP Provide Assistance Data or in the LPP Request Location Information. Then, when the generated LPP message does not fit within the data volume threshold, the WTRU can apply the segmentation configuration to segment the segmented LPP message / PDU at multiple SDT transmission times and transmit it to the network.

[0342] Condition-based reporting

[0343] Conditions that trigger WTRU to report, for example, when WTRU observes a measurement difference.

[0344] For example, the WTRU can monitor a trigger signal from the gNB, which can be part of the paging timing. This trigger signal can be, for example, the paging configuration itself, a paging message addressing the WTRU's RNTI, a PDCCH, a DL RS, or a DL transmission on a subgroup of DL resources.

[0345] WTRUs autonomously trigger location during idle / inactive periods.

[0346] Periodic reports

[0347] In one approach, the WTRU can be configured to periodically perform location reporting (e.g., location measurements for WTRU-assisted positioning techniques and / or location information for WTRU-based positioning techniques). For example, the WTRU may use one or more CGs to report location measurements and / or location information. Alternatively, the WTRU may use configured RACH resources (MsgA, Msg3, and / or Msg5) to perform location reporting.

[0348] Event-triggered reporting

[0349] In another approach, WTRU can perform location reporting based on one or any combination of the following location-related events.

[0350] ●WTRU detected a change in its position.

[0351] ●The WTRU detects a measurement change. Specifically, if the WTRU detects a change in positioning measurements, it can generate a measurement report. This change can be based on any of the following.

[0352] ○WTRU detected a change in RSTD for the same pair of TRPs between two PRS receive instances.

[0353] ○The RSRP of the PRS becomes greater than and / or less than a threshold and / or the RSRP difference between two PRS receiving instances from the same TRP is greater than a threshold.

[0354] ○The WTRU detects an increase or decrease in the number of paths (possibly paths with RSRPs greater than a threshold) and / or the WTRU detects a change in the time interval between two paths received from two different PRSs from the TRP.

[0355] ○WTRU detected a change in RTT (the time gap between SRSp transmission and PRS reception).

[0356] ○WTRU speed change.

[0357] The WTRU can receive event-triggered reporting configurations (e.g., RSRP thresholds) along with PRS / SRSp configurations (e.g., in paging messages, SIBs, and / or RRC messages when the WTRU is in RRC connected state).

[0358] WTRU Incremental Reporting

[0359] In one approach, the WTRU can perform incremental reporting for locating the report (e.g., reporting only the difference between a given parameter and a previously reported value for that same parameter). Specifically, the WTRU can include information about changes in the report. For example, the WTRU can be asked to report the RSTD for multiple TRP pairs. However, the WTRU can include the RSTD for changes to the TRP pairs in the report. This approach can be encouraged to reduce message size.

[0360] In the implementation, the WTRU can perform rule-based reporting in periodic reports and incremental reporting in event-triggered reports. The incremental report in an event-triggered report can be associated with the previous periodic report. Specifically, if the WTRU detects a change in positioning measurements compared to the previous periodic report, the WTRU can perform an event-triggered report and / or the WTRU can include only the incremental information compared to the previous periodic report.

[0361] In one implementation, the UE can determine which location measurement report to execute based on the configured authorized time-frequency resources and / or the size of each measurement report. For example, if the configured authorization is sufficient for such a report, the UE can determine to execute a normal measurement report. Alternatively, if the configured authorization is insufficient for a complete report, the UE can execute an incremental report. Alternatively, the UE can execute an incremental report while also indicating the necessity of an additional report (e.g., a complete report) in the first authorization. Such indication can be conveyed by a MAC CE (e.g., BSR) and / or a MAC header. In another implementation, the UE can segment the location measurement report into multiple sequential reports. The UE can also indicate the necessity of subsequent reports in the aforementioned reports (e.g., in the MAC CE and / or MAC header of the aforementioned reports).

[0362] Configurable authorization method

[0363] Authorization allocation for the configuration of measurement reports

[0364] When a positioning measurement or report is triggered in an idle or inactive state, the WTRU can report its positioning measurements, its location, and / or positioning reports (or related data) on pre-configured uplink resources (e.g., configured authorization). The WTRU can use such resources if timing lead is known or if the relevant timing alignment timer is still running.

[0365] In another approach, the WTRU can use uplink-based positioning regardless of whether uplink timing maintenance is applied. An example of timing maintenance is the use of timing lead. For example, the WTRU can use uplink-based positioning if: (1) a timing lead timer is running; (2) a timing lead timer associated with a PUSCH or PRACH resource is running if the RSRP associated with the associated PUSCH or PRACH resource is above a threshold; (3) the RSRP associated with small data transfer is above a threshold; and / or (4) a timing lead value has been acquired since transitioning to an idle or inactive state.

[0366] For location reports / data transmitted on CG resources, the WTRU can monitor the PDCCH used for HARQ-ACK determination after transmission; such PDCCH can be scrambled by I-RNTI, C-RNTI, small data-RNTI, or CS-RNTI. The WTRU can monitor explicit HARQ ACK / NACK signaling and / or assume HARQ-ACK is ACK or NACK upon the timeout of a configured or predetermined timer. The WTRU can start such a timer when transmitting the payload on the CG resource. If the timer times out (1) before the WTRU receives or determines a HARQ-ACK and / or (2) the WTRU receives a dynamic grant for retransmission, the WTRU can retransmit or autonomously retransmit the payload. Alternatively, the WTRU can refresh the HARQ buffer associated with the payload upon timeout. In one implementation, such a timer can be a conventionally configured grant timer.

[0367] In one approach, the WTRU can be configured with one or more TA timers. Each TA timer can be associated with one or more configured licenses. In one example, the WTRU can be configured with one TA timer associated with all configured licenses for the WTRU in idle / inactive mode. Alternatively, the WTRU can be configured with multiple configured licenses, each configured license being associated with one TA timer.

[0368] When the TA timer associated with the configured authorization times out, the WTRU can execute a RACH procedure to continue the positioning measurement reporting process. In one implementation, the WTRU can report positioning measurements in a RACH resource (e.g., MsgA for a 2-step RACH or Msg3 for a 4-step RACH). In another implementation, the WTRU can report the buffer status in a RACH resource when the TA timer times out. Specifically, the WTRU can determine to include a BSR in MsgA and / or Msg3 to indicate the availability of positioning measurement data. In another approach, the WTRU can execute a RACH procedure to indicate the invalidity of the configured authorization. Specifically, the WTRU can be configured with a dedicated RACH resource (e.g., a dedicated RACH preamble or a dedicated RO) to report the invalidity of the configured authorization (e.g., due to the TA timer timeout). The WTRU can then wait for a command from the network to continue positioning measurement reporting. The WTRU can then verify the configured authorization by restarting the TA timer upon receiving a timeout command from the network. Such commands can be received in MsgA, Msg3, PDCCH, and / or PDSCH.

[0369] The WTRU can monitor one or more CORSET / search spaces associated with one or more configured licenses in idle / inactive mode to receive commands from the network after one or more uplink transmissions. The WTRU can restart the TA timer associated with the configured license based on any one or more of the following commands from the network:

[0370] -WTRU successfully decoded the PDCCH from the network.

[0371] - The WTRU detects no PDCCH transmission in the configured CORSET / search space (the WTRU may assume that the network successfully received the PUSCH from the network with the correct TA value).

[0372] In one approach, the WTRU may be configured with a dedicated CG for location measurement reports. Specifically, the WTRU may be configured with a DRB / SRB (Signaling Radio Bearer), LCH, and / or LCG associated with the location measurement report. During the LCP procedure, the WTRU may be restricted to multiplexing higher-priority data with location measurement report data within the configured authorization. Alternatively, the WTRU may be restricted to multiplexing location measurement report data within the configured authorization. The WTRU may perform a RACH procedure to transmit additional data and / or the WTRU may use other configured authorizations to transmit additional data.

[0373] In one approach, the WTRU can be configured with an authorization associated with a DRX / DTX cycle configured for the WTRU in idle / inactive mode. In another approach, the WTRU can then be configured to monitor the CORESET / search space, which can occur before each group of one or more of the following resources:

[0374] -DL-PRS receiver

[0375] -UL-SRS transmission

[0376] -PUSCH transmission / PUCCH transmission.

[0377] The WTRU can determine whether to wake up to perform DL-PRS reception, UL-SRS transmission, and / or PUSCH / PUCCH transmission (e.g., to perform location measurement reporting) based on the availability and / or content of the PDCCH. For example, the WTRU can be configured by the network to wake up based on the PDCCH decoding status in a configured CORESET / search space associated with resources used for DL-PRS reception, UL-SRS transmission, and / or PUSCH / PUCCH transmission. In one configuration, the WTRU can be configured to wake up if no PDCCH is decoded in the configured CORESET / search space. Otherwise, if the WTRU decodes the PDCCH, the WTRU determines whether to wake up based on the content of the bit fields in the PDCCH. In another configuration, the WTRU can be configured not to wake up if it does not detect a PDCCH in the configured CORESET / search space.

[0378] In another approach, the WTRU can be configured to associate a configured authorization with a periodic / semi-persistent UL-SRS / DL-PRS measurement resource. The WTRU can then determine whether to perform a transmission within the configured authorization based on the reception / transmission activity of the associated resource. In one example, if no DL-PRS is detected in the resource, the WTRU can determine not to perform a location measurement report within the associated configured authorization. Similarly, if the WTRU does not transmit UL-PRS in the associated resource, the WTRU can choose not to perform a measurement report in the configured resource.

[0379] WTRU expects to receive PRS timing

[0380] In the implementation, the WTRU can be configured to expect to receive the PRS at a (pre-)configured time offset after receiving a timer for the CG. The timer may time out, and the WTRU may need to perform a RACH procedure to reset the timer. In this case, the WTRU can expect to receive the PRS at the (pre-)configured time offset once a new timer, a new value for that timer, or the timer has been reset for the CG.

[0381] Non-periodic measurement report

[0382] Non-periodic positioning measurement report

[0383] When the WTRU is in idle / inactive mode, it can be triggered to report positioning measurements or transmit SRSp. One or more of the following features can be applied:

[0384] ● One or more non-periodic PRS configurations can be configured, defined, or used, and subgroups of these non-periodic PRS configurations can be indicated for positioning measurement reports.

[0385] ○ The time / frequency location of this subgroup in the non-periodic PRS configuration used for measurement can be indicated in the trigger message (or indication).

[0386] ● If the WTRU is in idle / inactive mode, the trigger message (or indication) may include one or more uplink resources for reporting.

[0387] ○ Uplink resources can be one or more uplink resources in the physical cell associated with the report. For example, when paging is used to trigger an aperiodic location measurement report, the physical cell associated with the report can be a physical cell in the paging tracking area.

[0388] ■ Uplink resources can be provided for each physical cell in the paging tracking area, where each physical cell can be associated with a unique physical cell identity.

[0389] ○ Uplink resources can be one or more SRSp resources sent by WTRU.

[0390] ○ Uplink resources can be a set of PRACH resources for WTRU to use for content-free RACH procedures for positioning measurement reports.

[0391] ○ Uplink resources can be PUSCH resources that can be scheduled in the DCI that triggers aperiodic positioning measurement reports.

[0392] ● When a WTRU is triggered to report a location measurement, the WTRU can determine whether to report based on the quality of the location measurement. For example, if the location measurement quality is below a threshold, the WTRU can discard the location measurement report; otherwise, the WTRU can report the triggered or requested location measurement.

[0393] In the implementation, paging events can be used as triggers for location measurement reports, wherein a subgroup of paging opportunities (POs) can be used for non-periodic triggering of location measurement reports. For example, one or more of the following can be applied:

[0394] Receiving a paging indication in this subgroup of paging timing (Po) can be considered a non-periodic triggering event for a location measurement report.

[0395] ○ Specific RNTIs (e.g., P-RNTI or Pos-RNTI associated with non-periodic triggering in positioning measurement reports) can be used to indicate non-periodic triggering.

[0396] A DCI with Pos-RNTI can schedule PDSCH, which may include location measurement report information. This location measurement report information may include at least one of the following:

[0397] ■ WTRU identification for triggering location measurement reports

[0398] ■ One or more positioning and measurement resources

[0399] ■ One or more SRSp resources used for transmission

[0400] ■ Uplink resources used for reporting

[0401] A DCI with Pos-RNTI can include a direct indication of which WTRU is triggered for reporting. For example, it can include a bitmap, and bit positions in the bitmap can be associated with WTRU identification. When the bit position associated with the WTRU indicates true (e.g., 1), the WTRU can be triggered to report a positioning measurement; otherwise, the WTRU is not triggered for reporting.

[0402] In various implementations, the non-periodic triggering of positioning measurement reports can be used interchangeably with: 1) non-periodic triggering; 2) activation / deactivation of semi-persistent positioning measurement reports; and / or 3) configuration of periodic positioning measurement reports.

[0403] Condition-based measurement reporting methods

[0404] In one implementation, if the RSRP is higher than a configured threshold, the WTRU can transmit the location report on an available CG resource. This threshold can be the same one configured for small data transfers. If the RSRP is lower than the threshold, the WTRU can transmit the location report on a RACH resource or an SDT RACH resource, and if the report is not suitable for use within the PUSCH resource associated with the RA, the WTRU can request resources (i.e., the MSGA payload or Msg3) for subsequent transmissions.

[0405] The WTRU can select a positioning method based on: (a) the selected resources for transmitting positioning reports, (b) channel measurements (e.g., RSRP or SINR) and / or (c) the selected SSB associated with the CG on which the positioning report is transmitted. In one example, the WTRU can select a specific positioning method and / or resource (e.g., PRS or SRSp) based on channel conditions. A positioning method may include at least: DL-based positioning, UL-based positioning, PRS-based positioning, SRSp-based positioning, time difference of arrival-based positioning, and / or multi-RTT-based positioning, etc. In one example, the WTRU can select a DL-based positioning method if the channel conditions (e.g., RSRP or SINR) are worse than or better than a configured threshold (e.g., under cell edge conditions). The WTRU can select a UL-based positioning method if the channel conditions are better than a configured threshold. The WTRU can select an RTT-based positioning method (e.g., multi-RTT) when the channel conditions are better than a configured threshold (e.g., RSRP > threshold, or RSRP differential is within the configured range). WTRU can measure RSRP not only from the serving cell to determine the selected positioning method.

[0406] The WTRU can select a location reporting method (e.g., a selected resource for reporting the location report) based on channel measurements (e.g., RSRP or SINR), uplink timing alignment, and / or based on the selected SSB associated with the CG on which the location report is transmitted. In one example, if the measured channel conditions (e.g., RSRP or SINR) are above a configured threshold or within a configured range, and / or if the WTRU is uplink timing aligned, the WTRU can transmit the location report on a CG that is valid for small data transmissions (e.g., valid in the sense that its TA timer is running and in the same serving cell where it is received). Otherwise, the WTRU can choose a PRACH resource to transmit the location report.

[0407] Measurement reporting via control plane (CP)

[0408] WTRU sends location information to the network via the control / use plane in the SDT.

[0409] In one implementation, when sending measurement reports and / or location information to the network in Small Data Transmission (SDT) while in RRC inactive / idle mode, the WTRU can be assigned a priority value associated with the SRB. To send measurement reports and / or location information to the RAN / LMF in SDT via the control plane (via AMF) in one or more NAS messages / PDUs, the WTRU can use the priority value assigned to SRB1, SRB2, or any SRB, for the following situations:

[0410] - Request UL authorization using the LCG / BSR process

[0411] - Use the LCP process to multiplex the NAS PDU in the received UL authorization.

[0412] To send a NAS PDU in an SRB (e.g., SRB2) using an SDT, the WTRU can send a request to the network to activate the security associated with the SRB. The request for security activation can be sent in a separate RRCResumeRequest message before sending the SDT containing the NAS PDU. Alternatively, the request for security activation can be sent along with the SDT when sending the NAS PDU.

[0413] To activate security for an SRB (e.g., SRB2), the WTRU can use security-related information (e.g., security key and next-hop chain counter) that may have been previously received in an RRC Retention message and stored as part of the WTRU context when transitioning to RRC Inactive / Idle mode. For example, when sending a NAS message in the SDT, the WTRU may include a recovery cause value to indicate control plane forwarding and / or security activation. Security activation also enables the RAN to activate security and integrity protection for the SRB to carry the NAS PDU from the WTRU to the LMF in the control plane via the AMF in the SDT. In the case of a separate RRC Retention Request, upon receiving an indication message acknowledging control plane forwarding and / or security activation for the SRB (e.g., in an RRC Retention message), the WTRU can use the SRB (e.g., SRB2) to carry the NAS PDU. The indication message received by the WTRU may also contain an indication to use the SDT for the SRB (e.g., SRB2) while remaining in RRC Inactive / Idle mode without transitioning to RRC Connected mode.

[0414] In one example, one or more SRBs carrying NAS PDUs can be assigned priority values, which by default are higher than the priority values ​​assigned to DRBs used to send data in the SDT. Furthermore, different SRBs can be associated with different priorities, and these SRBs can carry NAS messages whose priorities may depend on the location service. For example, when using the SDT, a WTRU supporting a location service with moderate latency requirements can be configured with one or more SRBs with relatively low priorities. In this case, the SRB carrying the NAS message can be assigned a lower priority compared to other high-priority DRBs using the SDT.

[0415] In another implementation, the WTRU can transmit location information and / or measurement reports to the RAN / LMF via the user plane (via the UPF) from one or more DRBs configured to be used with the SDT. In this case, for example, different DRBs can be assigned different priority values, and the WTRU can use the DRBs to transmit location information in the SDT based on the priority assigned to the location service.

[0416] WTRU uses SDT to send location information based on a configured data volume threshold.

[0417] In one implementation, the WTRU (operating in an inactive state) can transmit one or more types of location information (e.g., measurement reports and / or location information) using an SDT configured for one or more SRBs, based on a configured and / or data volume threshold associated with the SRB. In this case, different SRBs (e.g., SRB1, SRB2, SRB3) can be configured in the WTRU, possibly for carrying location information in NAS messages using the SDT. The different SRBs configured for the SDT in the WTRU can be configured with one or more data volume thresholds, which may be associated with different types of location information (e.g., location estimation, measurement reports associated with PRS, Rx-Tx time difference measurements for multi-RTT methods). The data volume threshold can be used to reactivate the SRB configured for the SDT (e.g., SRB2) when triggered by the arrival of a NAS message from a higher layer that may contain location information. In one example, the WTRU can reactivate SRB2 for transmitting RRC and / or NAS messages in the SDT when the size of the RRC / NAS message is less than or equal to the data volume threshold configured for SRB2. For example, the data volume threshold can be configured by LMF or gNB. For example, a similar method for sending location information using SDT when the WTRU is inactive can also be applied, for example, when the WTRU is in idle mode.

[0418] For example, based on the size of the location information determined by the WTRU, the WTRU can be configured with one or more SRBs, which can be used to carry the location information in the SDT. In this case, based on an indication sent by the WTRU to the network (e.g., gNB) indicating the size of the location information to be carried using the SDT, the WTRU can be configured with a data volume threshold corresponding to the SRB. For example, upon receiving a location request from the network (e.g., LMF), the WTRU can indicate to the serving gNB the size of the location information to be sent in the UL when operating in an inactive state. For example, the WTRU can send the indication of the size of the location information to the gNB in ​​an RRC message, MAC CE, or UCI. For example, the WTRU can send this indication to the gNB before, during, or after transitioning to an inactive state. With the corresponding data volume threshold configured, the WTRU can then use the SDT to send the location information in an RRC / NAS message in the associated SRB (e.g., SRB2).

[0419] For example, each SRB (e.g., SRB1, SRB2) configured for SDT in the WTRU can be associated with different data volume thresholds at different times, wherein at any given time, at least one data volume threshold can be activated for the SRB. Different data volume thresholds can be associated with markers or indications that can be used during the triggering of the SDT procedure. For example, when initially configuring an SRB for SDT, a default data volume threshold can be activated and applied. In one example, the WTRU can be configured with a default / first data volume threshold that is aligned with or higher than the size of a NAS message carrying location information (e.g., a measurement report). For example, the data volume threshold can be dynamically changed / updated based on the triggering of the SDT procedure. In this case, when a NAS message of a specific size arrives, the WTRU can initially determine whether the NAS message is smaller than the default / first data volume threshold in order to determine whether the NAS message can be sent with the SDT. When a NAS message is determined to be above a first data volume threshold (e.g., the aforementioned default value) and less than or equal to a second configured data volume threshold that is greater than the first data volume threshold, the WTRU can trigger the SDT procedure by sending a recovery request to the network containing an indication identifier / tag associated with the second data volume threshold (e.g., in MSGA, MSG3, or CG). The WTRU can send the NAS message upon receiving a recovery message indicating activation of the second data volume threshold (e.g., in RRC). In this case, for example, as long as the second data volume threshold remains active and / or is not deactivated by the network, the WTRU can continue to send one or more NAS messages (e.g., carrying location information). For example, the aforementioned data volume threshold can be configured by an LMF or gNB.

[0420] For example, based on data volume thresholds that can be configured and / or activated for associated SRBs (e.g., SRB1, SRB2), the WTRU can determine the attributes of the location information to be transmitted using the SDT, including the type and size of the location information. For instance, based on data volume thresholds configured in the WTRU and / or associated with the SRBs used to carry location information, the WTRU can determine whether the location information (i.e., carried in the NAS message) needs to be segmented into multiple fragments. In this case, for example, the WTRU can segment the location information into different fragments, which may be less than or equal to the configured data volume threshold. For another example, the WTRU can segment the location information into several fragments, where the number of fragments can be determined based on location-related delay requirements configured in the WTRU. For example, the WTRU can use the data volume threshold and / or the configured location delay requirements (which may be related to the requirement to transmit the location information within delay boundaries) to determine the number of fragments to be processed when segmenting the location information. The WTRU can then use the SDT to transmit the different fragments containing the location information.

[0421] For example, when using SDT, the WTRU can determine the type and number of positioning measurements to be performed and / or sent to the network as measurement reports based on a configured data volume threshold associated with the SRB (e.g., SRB1, SRB2). For instance, the WTRU can be configured with one or more PRS configurations for measuring DL-PRS and sending measurement reports to the network. Different types of measurement reports that can be sent by the WTRU can be associated with different positioning accuracies. In one example, the WTRU can determine whether to send a rich measurement report (e.g., a higher-granularity measurement that may contain information about multipath and / or interference / tags) or a normal / simplified measurement report (e.g., a measurement with minimal configuration granularity) based on the configured data volume threshold. In this case, for example, when the data volume threshold configured for SDT in SRB2 is higher than or equal to the size of the NAS message carrying a rich measurement report, the WTRU can send a rich measurement report containing arrival timing or angle of arrival measurements for additional paths at higher resolution.

[0422] WTRU uses the WTRU RRC status to indicate the RAN configuration to the LMF to support the positioning process.

[0423] In one implementation, the WTRU may send information to the LMF indicating its RAN configuration, including its RRC status and / or configuration to be applied in RRC mode, for receiving positioning assistance information and / or measurement reporting configuration associated with the RAN configuration. For example, when transitioning from a connected state to an inactive state, the WTRU may send an indication to the LMF that the WTRU can receive assistance information (e.g., PRS configuration) and / or measurement reporting configuration that can be applied when the WTRU is operating in an inactive state. The WTRU may send the aforementioned indication to the LMF via the LPP.

[0424] In one example, based on information about its RRC status sent to the network by the WTRU, the WTRU may receive one or more positioning configurations (e.g., assistance information, positioning report configurations) that include updates to QoS requirements associated with positioning, including positioning accuracy and / or latency. In this case, for example, the configurations received by the WTRU may allow the WTRU to flexibly weigh trade-offs in achieving high positioning accuracy, high device efficiency (i.e., low power consumption), and / or low-latency positioning.

[0425] In one example, based on indications sent by the WTRU to the network regarding its current and / or future RRC status, the WTRU may receive auxiliary information containing one or more PRS configurations to be used for measurement when operating in an inactive / idle state. For example, the WTRU may receive auxiliary information / PRS configurations to be used when operating in a specific RRC state. For instance, when operating in a connected state, the WTRU may use a first PRS configuration, and when operating in an inactive state, the WTRU may use a second PRS configuration. In this example, using the first PRS configuration may result in a longer measurement duration, potentially with higher accuracy at the WTRU. Alternatively, using the second PRS configuration may result in lower power operation and a shorter measurement duration at the WTRU, potentially with reduced accuracy.

[0426] For example, where the WTRU can be configured with an SDT for transmitting data (e.g., location information) when inactive, the WTRU can receive a measurement report configuration from the network (e.g., LMF) indicating one or more parameters to be used when transmitting measurement reports while inactive. For example, parameters associated with the measurement report configuration received by the WTRU may include the type of measurement to be reported (e.g., rich / simplified reporting), the amount of measurement to be reported (e.g., the size of each measurement report), and / or the periodicity of the reporting. Whether a report is simplified or rich can be determined by the number of additional paths the WTRU reports for its measurements. For example, in a simplified report, the WTRU may report PRS measurements associated with the main path. In a rich report, the WTRU may report PRS measurements associated with the main path and N additional paths, where N can be configured by the LMF. For example, in one or more SRBs / DRBs, parameters for the measurement report configuration can be received from the LMF based on information sent by the WTRU regarding a data volume threshold for the SDT configuration. For example, based on knowledge of the (lower) data volume threshold configured for SDT at LMF, WTRU can be configured to send simplified measurement reports (possibly with reduced granularity) in an inactive state.

[0427] For example, the WTRU can send configuration information for inactive mode operation to the LMF, including information about the SRB / DRB (e.g., SRB2) configured for the SDT and / or the associated data volume thresholds configured for the SDT. The WTRU can send the aforementioned information to the LMF via the LPP. Configuration information for inactive mode operation can be sent from the WTRU to the LMF upon receiving one or more of the following signaling / messages:

[0428] - Higher-level location requests (e.g., MO-LR, MT-LR)

[0429] -(LPP) Capability Transfer Request

[0430] -(LPP) Auxiliary data transmission

[0431] -(LPP) Location Request Transmission Request

[0432] -(LPP) Location Information Transmission

[0433] For example, when the first inactive mode configuration is received from the gNB, and / or when an update to the inactive mode configuration is triggered and received by the WTRU, the configuration information for inactive operation can also be sent by the WTRU to the LMF. In one example, if the WTRU may have already transitioned to an inactive state, the WTRU can send an indication of the first / updated inactive mode operation configuration to the LMF in a NAS message. For example, when triggered, for instance, by an update to the inactive mode configuration (e.g., a change in the data volume threshold), the WTRU can send an indication in a NAS message in MSG A, MSG 3, or the CG in a recovery message.

[0434] LMF is a non-limiting example of a node or entity (e.g., a network node or entity) that can be used to or support location. Any other node or entity may be used in place of LMF and consistent with this disclosure.

[0435] Beam management for CG

[0436] Beam management during CG configuration.

[0437] In various implementation schemes, "PRS" and "PRS resource" can be used interchangeably. Additionally, "PRS", "DL PRS", and "downlink PRS" can be used interchangeably.

[0438] Conditions for using CG-based measurement reports for localization

[0439] Conditions for continuing to use the configured authorization for measurement reporting

[0440] The WTRU can be pre-configured with PRS via LPP during RRC connection state. In the implementation, for the WTRU to use the configured authorization (CG) to perform measurement reporting for positioning, at least one of the following conditions must be met.

[0441] ●WTRU is configured with a valid timer for the configured license.

[0442] ●The WTRU receives at least one SSB that meets the (pre-configured) criteria, for example, the RSRP of the received SSB is higher than the (pre-configured) threshold.

[0443] ●WTRU has PRS configuration in LPP ancillary data.

[0444] ● If the WTRU receives at least one SSB that meets the (pre-configured) criteria, the WTRU also receives at least one PRS resource that meets the (pre-configured) criteria (e.g., the RSRP of the received PRS is higher than the (pre-configured) threshold).

[0445] ●WTRU performs WTRU-assisted localization or WTRU-based localization.

[0446] The above conditions can be combined to allow WTRU to be configured with authorization based on multiple conditions.

[0447] After the WTRU receives the configuration for the CG, it can receive the PRS configuration. In this case, the WTRU can send a request for the PRS configuration by sending LPP request auxiliary data to the LMF in the CG, thus enabling the WTRU to receive the PRS configuration. The WTRU can send the request to the network in RRRCResumeRequest, message 3, or message A.

[0448] Definition of 2 sets of associations (SSB<->CG, SSB<->PRS / SRSp)

[0449] Definition of 2 sets of association rules

[0450] The WTRU can use the configured authorized resources to transmit measurement reports to the network. If the WTRU is not configured with any authorized resources, it can perform the following procedure to obtain the configuration for the configured authorization.

[0451] In one implementation, the WTRU can receive two sets of associations.

[0452] ● In the first set of associations, each SSB (SS block) can be associated with a configured licensed (CG) resource. Alternatively, multiple SSBs can be associated with a single configured licensed resource, or multiple configured licensed resources can be associated with a single SSB.

[0453] ● In the second set of associations, information may be included regarding the spatial or QCL relationships between the SSB and other reference signals (such as PRS) or channels. Examples of different types of QCLs can be found in 3GPP Technical Specification 38.214.

[0454] How to store associations at WTRU

[0455] The WTRU can receive these group associations via a higher layer during RRC connected state or after transitioning to RRC idle or inactive mode. The WTRU can receive these group associations via RRC Release messages, RRC, or LPP messages.

[0456] SSB Reception: The process used for measurement reporting

[0457] For example, WTRU can perform the following procedure to return a measurement report to the network.

[0458] 1. The WTRU selects an SSB from among multiple SSBs transmitted from the gNB based on a (pre-)configured criterion. This criterion can be whether the RSRP of the SSB received by the WTRU is higher than a pre-configured threshold;

[0459] 2. The WTRU receives the PRS associated with the selected SSB, where the association is indicated in the second set of associations;

[0460] 3. The WTRU uses the received PRS to perform measurements;

[0461] 4. The WTRU transmits measurement reports to the network from the configured resources associated with the selected SSB.

[0462] Multiple SSBs correspond to one CG, or multiple CGs correspond to one SSB.

[0463] For example, multiple SSBs can be associated with a single configured authorization, allowing the WTRU to flexibly determine SSB beams during mobility. An SSB can be mapped to multiple CG resources, enabling the WTRU to determine which CG resources to use to send measurement reports at multiple measurement reporting times, where there is a one-to-one correspondence between measurement reporting times and CG resources. Furthermore, when an SSB is mapped to multiple CG resources (i.e., a set of CG resources), the CG resources between groups do not overlap, thus avoiding conflicts.

[0464] For example, in the second set of associations, the WTRU receives associations between the SSB and other RSs or channels, and these associations can be spatially related. For instance, the WTRU can receive configurations indicating spatial quasi-co-location relationships associated with QCL-TypeD between the SSB and PRS resources. It is possible for PRSs to exist that can be transmitted from the same location in the same direction as the SSB. In other words, the WTRU can assume that the same Tx (transmission) spatial filter is used to transmit the SSB and PRS.

[0465] In the first set of associations, for example, the SSB's identifier and the resource identifier of the configured authorized resource can be associated.

[0466] Since the WTRU can receive SSBs from both the serving cell and neighboring cells, the WTRU can use a first set of associations that associate the configured authorized resources with the SSBs from the serving cell.

[0467] Since the gNB does not know which SSB the WTRU might choose, the WTRU can receive multiple variants of the first set of associations, with different SSBs within each variant.

[0468] SSB Receive + PRS Beam Scan: Used for measurement reporting processes

[0469] In the implementation scheme, in the second set of associations, there may be multiple PRS resources associated with the selected SSB. (Reference) Figure 12 The flowchart shows that WTRU can perform the following procedure to return a measurement report to the network.

[0470] 1. After receiving an SSB (1201), the WTRU selects an SSB (1203) from among the multiple SSBs transmitted from the gNB according to a standard. This standard can be whether the RSRP of the SSB received by the WTRU is higher than a pre-configured threshold.

[0471] 2. WTRU determines the PRS to be received (1205) based on its association with SSB.

[0472] 3. The WTRU receives the PRS associated with the SSB, where the association is indicated in the second set of associations (1207). The WTRU can receive the PRS resource in a different symbol or time slot that has a unique association with the PRS resource. The WTRU can receive information about the association between the PRS resource and the symbol / time slot in RRC Release, RRC, LPP messages, or higher-level signaling.

[0473] 4. The WTRU selects a PRS that meets the (pre-)configured standard. The WTRU can receive the standard in RRC Release, RRC, LPP messages or higher-level signaling (1209).

[0474] 5. The WTRU uses the PRS received by the WTRU to perform measurements (1211).

[0475] 6. The WTRU transmits measurement reports to the network at the configured resource associated with the selected SSB (1213).

[0476] The WTRU transmits measurement reports to the network at the configured resource associated with the selected SSB.

[0477] Definition of two sets of association rules for SRSp

[0478] For example, in the first association, each SSB can be associated with a configured authorized resource. The second association information contains information about the spatial relationship or QCL between the SSB and the SRS used for positioning. In this disclosure, "SRSp" and "SRSp resource" are used interchangeably.

[0479] WTRU can implement the following process to transmit SRSp.

[0480] 1. The WTRU selects an SSB from multiple SSBs transmitted from the gNB according to the standard;

[0481] 2. The WTRU finds the SRSp spatially associated with the SSB selected by the WTRU and transmits the SRSp in the configured licensed resources associated with the selected SSB.

[0482] In another implementation, the first set of associations relates to the PRS and the configured authorized resources. The second association relates to the SSB and multiple PRSs regarding spatial or QCL information. In this case, once the WTRU selects an SSB, the WTRU selects one of the PRSs associated with that SSB. The WTRU expects to send measurement reports in the configured authorized resources associated with the selected PRS.

[0483] Assumptions regarding the beam correspondence of SRSp

[0484] The WTRU can determine to transmit the SRSp using the spatial filter it has already used to receive the SSB selected by the WTRU. In this case, the WTRU does not need to receive a second set of associations containing the spatial or QCL relationship between the SRSp and the SSB. The WTRU can determine the configuration of the TX spatial filter, which can be explicit or implicit. The WTRU can receive explicit indications in higher-layer signals such as RRCrease, LPP messages, or RRC. If the WTRU does not receive a second set of associations, it can receive implicit indications to determine to transmit the SRSp using the spatial filter it has used to receive the SSB.

[0485] Given only the association between SSB and CG: WTRU reports back to the selected SSB.

[0486] In another implementation, the WTRU may be configured with only the first set of associations. In this case, the WTRU may transmit information about the SSB selected by the WTRU at the configured authorized resource associated with the SSB selected by the WTRU. The WTRU may send information about the selected SSB, such as the resource ID, in an RRCresumRequest, message 3, or message A during the RACH procedure. After this transmission, the WTRU may receive a second set of associations from the network. The second set of associations contains spatial information or QCL relationships between the selected SSB and the PRS.

[0487] Given only the association between SSB and CG: WTRU requests PRS auxiliary data

[0488] In another implementation, the WTRU can receive configuration for the CG based on the first set of associations. If the WTRU is not configured with a PRS, the WTRU can send LPP auxiliary data in the CG to request PRS configuration from the LMF.

[0489] WTRU can have PRS configurations that have been passed down from RRC_CONNECTED: WTRU can be traced back to obtain Get the CG configuration.

[0490] The WTRU can receive the PRS configuration during the RRC connected state. This configuration is retained even after transitioning to RRC idle or inactive mode. Therefore, after transitioning to RRC idle or inactive mode, the WTRU can receive the same PRS as it received during the RRC connected state. The WTRU can determine the CG resource using the configured first and second set of associations. For example, the WTRU can determine the CG resource using the following steps.

[0491] 1. The WTRU determines the SSB spatially associated with the PRS configured during the RRC connection state.

[0492] 2. WTRU identifies the CG resources associated with the SSB selected in the first step.

[0493] WTRU can identify CG resources and send measurement reports associated with the PRS configured in WTRU.

[0494] How to obtain association

[0495] The WTRU can receive the first and second sets of associations mentioned above in higher-level information (such as RRRCRelease, LPP message-related signaling, or WTRU context).

[0496] Special cases related

[0497] This association can be limited to use during idle / inactive mode positioning. For example, the association can be limited to SSB, PRS, or SRSp resources used during RRC connected state.

[0498] Other situations

[0499] SSB source

[0500] In this disclosure, the SSB used in the association can originate from the serving cell or a neighboring cell. In either case, the cell ID indicating from which the SSB was transmitted is also included in the association information, which the WTRU uses to determine the transmission source of the SSB and the CG resource, PRS, or SSP associated with the SSB.

[0501] If the SSB is already set in the auxiliary data, then the WTRU does not need to measure these SSBs.The WTRU can receive auxiliary data from the LMF, which includes the configuration of the PRS and / or SSB transmitted in the serving cell or neighboring cells during idle / inactive mode or RRC connected state. The WTRU can receive auxiliary data via broadcast. In another implementation, the WTRU can receive RRC configuration regarding the SSB transmitted from the TRP. In this case, if the WTRU receives the first set of associations, the WTRU can determine the CG configuration without measuring the SBS. The WTRU can send a request for auxiliary data to the network in an RRC Resume Request, message 3, or message A.

[0502] MO-LR

[0503] When in RRC inactive / idle mode, the WTRU sends an LCS request for the MO-LR location service.

[0504] In one implementation involving MO-LR, the request for location information originates from an LCS client located in the WTRU, which sends the location information request to the network (i.e., the RAN and / or LMF) while remaining in RRC idle / inactive mode. Specifically, the request for location information (i.e., the LCS request) may be sent to the network in a control plane NAS message (e.g., sent from the AMF to the LMF) or a user plane message (e.g., sent from the UPF to the LMF). In addition to the LCS request, the WTRU in RRC inactive / idle mode may also send one or more of the following to the network:

[0505] - WTRU capability information used for positioning

[0506] For example, the WTRU can transmit the ability to support one or more positioning methods and / or configurations, including RAT-dependent methods (e.g., DL based on PRS measurements (DL-TDoA or DL-AoD) or UL based on SRSp transmissions (UL-TDoA or UL-AoA)) and RAT-independent methods (e.g., GNSS).

[0507] - Request for auxiliary information

[0508] For example, a WTRU can request one or more PRS and / or SRSp configurations to support one or more positioning methods. A WTRU can also indicate which PRS / SRSp configurations are supported or currently available at the WTRU.

[0509] In one example, the WTRU can piggyback WTRU capability information for location and / or requests for ancillary data onto the LCS request. In this case, the WTRU can send one or more of the aforementioned information / requests in a single transport (e.g., a single NAS message) or in multiple transports (e.g., multiple NAS messages) at encapsulation time. When sent in a single transport, the WTRU can send the NAS message in MsgA (i.e., when using a 2-step RACH), Msg3 (i.e., when using a 4-step RACH), or using a CG pre-configured in the WTRU, possibly in an RRC Resume Request or SDT. Similarly, when sent in multiple transports, the WTRU can send NAS messages in multiple SDTs (e.g., multiple MsgA, Msg3, or CGs) while remaining in RRC inactive / idle mode.

[0510] For example, a WTRU operating in RRC idle / inactive mode might skip the transmission of requests for WTRU capability information and / or ancillary information when sending an LCS request to the network. The decision to send such information / requests can be made by the WTRU based on one or more validity conditions associated with the WTRU capability and / or ancillary information. For example, validity conditions can be monitored by the WTRU upon receiving a trigger from the LCS client. For example, the WTRU might have previously transmitted WTRU capability information and / or received ancillary information during RRC connected mode. For example, when transitioning to RRC inactive / idle mode, the WTRU may also have validity conditions configured or set in the RRC Release message (e.g., timers, cell ID in RNA / TA, PLMN restrictions). In this case, when an LCS request is triggered by the LCS client and / or sent to the network, the WTRU can determine whether to include or exclude requests for WTRU capability information and / or ancillary information based on whether the validity conditions are valid (e.g., the timer has not expired or the cell ID is valid).

[0511] For example, when operating in RRC inactive / idle mode, the decision on whether to send WTRU capability information and / or (request) auxiliary information can be based on receiving a request message from the network before or after sending an LCS request to the network. In this case, the WTRU in RRC inactive / idle mode can send WTRU capability information or auxiliary data information (e.g., supported PRS configuration) in a NAS message when receiving a request from the network, which can be sent, for example, in a paging or RRC Release or RRC Resume message. For example, a request for WTRU capability and / or information about auxiliary data can be triggered by the network (e.g., LMF) when receiving an LCS request from the WTRU and / or when it is determined that the context related to WTRU capability / auxiliary data is unavailable or invalid (e.g., at AMF or LMF).

[0512] When in RRC inactive / idle mode, the WTRU receives responses associated with the MO-LR location service. information

[0513] When sending an LCS request for MO-LR service and / or information about WTRU capabilities / auxiliary data, the WTRU may receive one or more response messages containing one or more of the following:

[0514] - The confirmation of LCS requests supports responses that provide WTRU location information.

[0515] - Request for WTRU capability information

[0516] - Auxiliary data, including one or more PRS / SRSp configurations, to enable WTRU to determine location when operating in RRC inactive / idle mode.

[0517] - Configuration for sending measurement reports, including information about the resources to be used (e.g., CG), the periodicity of the reports, etc.

[0518] In one example, when sending an RRC ResumeRequest message, the WTRU can receive a response message in one or more RRC Resume messages (e.g., in Msg B in a 2-step RACH or in Msg4 in a 4-step RACH). For example, for a WTRU operating in RRC inactive mode, it can receive a response message in an RRC Resume message under the suspendConfig configuration. As another example, the WTRU can receive a response message in one or more RRC Resume messages (e.g., Msg B or Msg 4). For example, the WTRU can also receive a response message containing one or more of the above information in a (RAN / CN) paging message.

[0519] Reporting by bypassing the control plane

[0520] WTRU-based positioning does not require a measurement report.

[0521] In one implementation, for WTRU-based positioning, the WTRU can transition to an RRC connected state to report its location. For example, after transitioning to an RRC connected state, the WTRU can report a (pre-)configured number of locations. In this case, the WTRU can be configured not to report measured or estimated locations when it is in an idle or inactive mode.

[0522] The reported (pre-configured) number of locations can be the estimated locations of the WTRUs at various times, assuming the WTRUs are idle or inactive. The WTRU's location can be obtained after the WTRU estimates its own location following measurements of the PRS transmitted from the TRP. The WTRU can estimate its location after collecting measurements such as AoD, AoA, RSTD, and / or ToA for each or more PRSs transmitted from the TRP. Multiple locations can be associated with different timestamps indicating that each location was estimated at a different time.

[0523] The WTRU can report statistical characteristics of multiple locations, which may include at least the average of the multiple locations (e.g., the geometric center of the multiple locations) and / or the standard deviation of the multiple locations. These characteristics can be reported after the WTRU transitions to RRC connected state. Specifically, reporting the cumulative number of locations reduces the number of times the WTRU must send reports, thereby reducing the power consumption for transmitting reports.

[0524] The WTRU can receive an indication from the network to return to the RRC connection status to report the estimated location. The WTRU can receive this indication in RRC or LPP messaging.

[0525] WTRU can configure the number of locations to be reported via higher-level messages (such as RRC, RRC Release messages, or LPP).

[0526] In another implementation, WTRU can use message 3, message A, or CG to report multiple (pre-)configured locations during inactive mode.

[0527] Location switching during mobility

[0528] Limited to idle / inactive mode

[0529] In idle / inactive mode, the WTRU assist network will match the tracking region and / or RNA configuration with the PRS / SRSp configuration. alignment

[0530] In various implementations, when operating in idle / inactive mode, the WTRU sends an instruction to the network to align configuration parameters (e.g., cell ID) associated with the PRS / SRSp configuration with configuration parameters of the tracking area and / or RAN notification area (RNA) configured in the WTRU. In idle mode, the WTRU may be assigned a list of tracking areas consisting of a list of cell IDs, where the WTRU can be mobile without sending tracking area update messages to the network. In inactive mode, the WTRU may be assigned a list of RNAs consisting of cell IDs, where the WTRU can be mobile without sending RNA update (RNAU) messages to the RAN. The WTRU may be configured with a PRS configuration along with the associated cell ID in auxiliary information, which can be maintained and used by the WTRU during idle / inactive mode for DL-based positioning and / or UL+DL-based positioning. Similarly, the WTRU may be configured with SRS resources along with the associated cell ID for UL-based positioning and / or UL+DL-based positioning in idle / inactive mode.

[0531] In this scenario, the WTRU might use PRS / SRSp configuration parameters (e.g., the cell ID associated with the PRS configuration and / or SRP resources) during mobility that are not aligned with the cell / gNB associated with the TA / RNA used during idle / inactive modes. Therefore, the WTRU might experience a mismatch during the on-duration of the DRX cycle used to receive PRS in the DL and / or transmit SRPs in the UL during idle / inactive modes, leading to potential inefficient resource usage, power waste, and inaccurate location measurements. By aligning the PRS / SRSp configuration parameters with the TA / RNA parameters, the WTRU can receive PRS or transmit SRPs in similar time slots when receiving paging messages or transmitting initial access messages during mobility in idle / inactive modes. Furthermore, the WTRU can also be configured to send / receive measurement reports, which may potentially be associated with TA / RNA update messages sent to the network or paging messages received from the network.

[0532] In one implementation, the WTRU can assist the network in associating the TA / RNA configuration with parameters associated with the PRS / SRSp configuration, enabling the WTRU to support different positioning methods during mobility while remaining in an idle / inactive mode. In this case, upon receiving the PRS / SRSp configuration and associated cell-related parameters (e.g., in SIB, CN / RAN paging messages), the WTRU can compare the cell ID associated with the PRS / SRSp configuration with the cell ID in the TA / RNA to determine the TA / RNA configuration used for positioning. For example, the TA / RNA configuration used for positioning may be the same as or different from the TA / RNA configuration used for CN / RAN paging. Based on the identification of the common and different cell IDs in the two configurations, the WTRU can then perform one or more of the following:

[0533] ● When the WTRU identifies at least one cell ID that may differ between the TA / RNA list and the PRS / SRSp configuration parameters (e.g., the cell list), the WTRU can send an instruction to the network.

[0534] ●The WTRU can select a TA / RNA configuration for positioning from one or more pre-configured settings, which may consist of a different list of cell IDs (which may be matched with cell-related parameters associated with the PRS / SRSp configuration). The WTRU can then send an indication to the network including the selected TA / RNA configuration for positioning.

[0535] ●WTRU can determine / export this parameter (e.g., cell ID) to update the list of TA / RNAs used for localization, and send the updated parameter to the network.

[0536] ●WTRU can send auxiliary information to the network to associate the PRS configuration with a list of TA / RNAs used for localization.

[0537] When the WTRU sends instructions on parameters in the alignment TA / RNA and parameters in the PRS / SRSp configuration, the WTRU may include one or more of the following information in the instructions:

[0538] ●WTRU ID: For example, a WTRU may include a CN-assigned ID (e.g., S-TMSI, IMSI) and / or a RAN-assigned ID (e.g., I-RNTI). Alternatively, when sending an instruction to the network, the WTRU may select a random ID from a pool of IDs configured within the WTRU.

[0539] ● Parameters related to PRS / SRSp configuration: For example, WTRU can indicate the identifier of the PRS / SRSp configuration that can be currently aligned with TA / RNA or is to be reconfigured to be aligned with it.

[0540] ● Parameters related to TA / RNA: For example, when sending an instruction to LMF / RAN, WTRU may indicate one or more parameters including the number of cells and / or cell IDs that may differ from those in TA / RNA and are associated with PRS / SRSp. In one example, WTRU may include in the instruction an identifier of a RACH resource and / or a RACH resource that can be updated when aligned with the TA / RNA list. As another example, WTRU may send a group ID representing one or more cells that differ from those in TA / RNA and are associated with PRS / SRSp.

[0541] ●TA / RNA ID: For example, when the WTRU selects a TA / RNA configuration from a set of pre-configurations, the WTRU can indicate the identifier of the selected TA / RNA pre-configuration to the network.

[0542] ● Auxiliary information: For example, the WTRU can indicate information about WTRU mobility (e.g., WTRU speed, direction) and / or WTRU environment (e.g., congestion on LOS paths, multipaths).

[0543] When the WTRU determines / derives a list of cells for TA / RNA for location based on the alignment of cell-related parameters associated with the PRS / SRSp configuration, the WTRU may determine one or more of the following:

[0544] ● The number / list of cell IDs can be one threshold higher than the existing list and less than the cell ID list in the tracking region and / or RNA.

[0545] ● Number / list of cell IDs that can be matched with a list of cell IDs in the tracking region and / or RNA

[0546] ● The number / list of cell IDs can be higher than a specific threshold than the list of cell IDs in the tracking region and / or RNA.

[0547] ●The number / list of cell IDs can be determined based on a combination of cell IDs in the RNA and the tracking area.

[0548] The criteria used to determine the number of cells updated associated with the PRS / SRSp configuration, including a threshold number of cells, can be (pre-)configured in the WTRU. For example, during mobility while remaining in an idle / inactive mode, whether a wider area is available for performing positioning, or whether more positioning measurement reports must be sent, can be determined based on a trade-off between these two factors. For instance, if the WTRU is intended to send a frequent number of measurement reports in TA / RNA update messages while moving within a smaller area, the WTRU can be configured to determine a number of cells fewer than the cell count in the TA / RNA. Similarly, if the WTRU is intended to send fewer measurement reports in TA / RNA update messages while moving within a wider area, the WTRU can be configured to determine a number of cells higher than the cell count in the TA / RNA.

[0549] Based on one or more of the following triggering conditions, the WTRU may send an instruction to the network in the TA / RNA update message or in the initial access message (e.g., Msg 1 / 3 or Msg A) for aligning the TA / RNA and PRS / SRS configuration:

[0550] ● Different cell IDs were detected during mobility.

[0551] ● A PRS different from the configured PRS was detected.

[0552] ● Receiving paging messages

[0553] ● Timers (e.g., used to indicate periodic message transmissions)

[0554] ● Measurements performed at WTRU

[0555] ● Triggered by higher layers / applications

[0556] When aligning parameters, parameters corresponding to the PRS / SRSp configuration (e.g., cell ID, SRSSp resources) can be associated with the WTRU context and maintained together with the TA / RNA in the network (e.g., at the Access and Mobility Management Function (AMF) in the CN for tracking areas or at the anchor gNB in ​​the RAN for RNA) and / or the WTRU. The WTRU can also be assigned an identifier / index indicating the alignment between parameters in the TA / RNA and PRS / SRSp configurations. In this case, the assigned alignment identifier can be maintained together with the WTRU context along with other parameters associated with supporting location during WTRU mobility (e.g., authorization for sending measurement reports). When the WTRU detects a misalignment between parameters (e.g., a difference in cell ID), the WTRU can send an indication to the network including the assigned identifier for the network to retrieve the WTRU context from the CN function / anchor gNB and potentially update the PRS / SRSp and / or TA / RNA configurations.

[0557] Figure 6 Example of a signaling flow for location during WTRU inactive mode mobility is shown, illustrating PRS configuration and RNA alignment. Before transitioning to RRC inactive mode, WTRU 201 is initially configured with RNA by the RAN (620). When triggered by LMF 205 (622, 624), WTRU 201 sets up the PRS configuration in an SIB, CN paging, or RAN paging message (626). When triggered by a location mobility event 628 (e.g., identification of a new cell ID outside the RNA or identification of a cell ID associated with a PRS configuration outside the RNA or interference from a neighboring cell), WTRU sends an RNAU to the RAN to update the RNA and / or PRS configuration (630). The RAN updates (632) WTRU's RNA to align with the PRS configuration based on information about the cell associated with the PRS in the RNAU. WTRU receives the updated RNA and, possibly, the updated PRS configuration in a RAN paging message (634). The WTRU receives a location request from the LMF in a CN paging or RAN paging message (636, 638). The gNB sends a PRS to the WTRU (640), and the WTRU measures the DL PRS (e.g., during the DRX on duration) (642) and sends a measurement report to the gNB / LMF in an initial access (e.g., SDT), RNAU, or TAU (Tracking Area Update) message (644). The gNB may transmit the report to the LMF (646).

[0558] Figure 7Another example of the signaling flow for location during WTRU inactive mode mobility is shown, illustrating SRS configuration and RNA alignment. Before transitioning to RRC inactive mode, the WTRU is initially configured with RNA by the RAN (720). When triggered by the LMF (722), the WTRU sets the SRSp configuration in a RAN paging message (724). When triggered by a location mobility event (726), the WTRU sends an RNAU to the RAN to update the RNA and / or SRSp configuration (728). The RAN updates the WTRU's RNA to align with the SRSp configuration. The WTRU receives the updated RNA and, possibly, the updated SRSp configuration in a RAN paging message (730). Finally, the SRSp transmitted by the WTRU (734) is measured at the RAN (736), and a measurement report is sent to the LMF (738).

[0559] Figure 8 Example of a signaling flow for location during WTRU idle mode mobility is shown, illustrating PRS configuration and tracking area alignment. Before transitioning to RRC inactive mode, WTRU 201 is initially configured with RNA by the RAN (820). When triggered by LMF 205 (822), WTRU sets the PRS configuration in a CN paging or RAN paging message (824). When triggered by a location mobility event (826) (e.g., identification of a new cell ID outside the tracking area or identification of a cell ID associated with the PRS configuration outside the tracking area or interference from a neighboring cell), WTRU sends a TAU (828) to the AMF (207) to update the tracking area or PRS configuration. The AMF updates WTRU's tracking area to align with the PRS configuration based on information about the cell associated with the PRS sent in the TAU (834). WTRU receives the updated tracking area and, possibly, the updated PRS configuration in a paging message (836). The WTRU receives a location request from the LMF in a CN paging or RAN paging message (840). The WTRU receives and measures the DL PRS (842 and 844, respectively) (e.g., during the DRX on duration) and sends a measurement report to the gNB / LMF in an initial access (e.g., SDT), RNAU, or TAU message (846). The gNB sends the measurement report to the LMF (848).

[0560] WTRU pairs in idle / inactive mode are aligned with paging timings in the DRX cycle. DL PRS execution measurement. quantity

[0561] In one implementation, the WTRU in idle / inactive mode performs location measurements on the DL PRS, which can be received along with the paging message during a time period aligned with the paging timing. In this case, the WTRU can be (pre-)configured with one or more PRS configurations including different parameters (e.g., periodicity, resources), which can be associated with and aligned with different DRX cycles configured in the WTRU (e.g., consisting of different on-time and sleep-time durations). Alternatively, the WTRU can receive a PRS / SRSp configuration that can be aligned with a DRX cycle configured in the WTRU.

[0562] For example, alignment between PRS reception and paging message reception can be supported by the WTRU for both CN paging and RAN paging. In this case, the mapping between different PRS configurations (identified by PRS configuration IDs) and DRX configurations (identified by DRX cyclic IDs) can be provided to the WTRU by CN functions (e.g., AMF, LMF) when CN paging is supported, or by the RAN when RAN paging is supported. For example, when the WTRU is in RRC connected mode or after transitioning to RRC idle / inactive mode (e.g., via SIB or paging messages), the mapping between the PRS configuration (i.e., auxiliary information) and DRX configuration can be configured in the WTRU.

[0563] Furthermore, WTRUs can be assigned WTRU identifiers (e.g., location P-RNTI, location I-RNTI) by the CN or RAN. WTRUs can use these identifiers to identify the presence of a PRS when a paging message is received during a paging opportunity, or when a DL PRS is received. The identifier assigned to a WTRU can be dedicated to each WTRU or to each group, where a group of WTRUs can use a common identifier when a PRS is received during a paging opportunity. In the case of group paging / location, a group of WTRUs can use a group identifier (e.g., location group RNTI) to detect the presence of a PRS during a paging opportunity in a DRX cycle; this group identifier can be common to all WTRUs in the group.

[0564] In idle / inactive mode, the WTRU can be triggered to measure the PRS based on the detection of the identifier and / or PRS ID assigned to the WTRU during the paging period of the default DRX cycle. To continue receiving DL PRS, the WTRU can switch to a different DRX cycle, which can be determined, for example, based on the PRS configuration ID and the mapping configured between the PRS configuration ID and the DRX cycle ID. The WTRU can continue measuring the received DL PRS without switching to RRC connection mode based on auxiliary information about the PRS configuration available at the WTRU (e.g., measurement duration), and send a measurement report (e.g., small data transmission, early data transmission) to the network when the measurement duration is complete.

[0565] Figure 9 Example of a signaling flow for location using PRS configuration and DRX cyclic alignment during WTRU idle / inactive mode is shown. Before transitioning to RRC inactive mode, WTRU 201 is initially configured with DRX by the RAN (920). When triggered by LMF (922, 924), gNB provides the WTRU with the PRS configuration in an SIB, CN paging, or RAN paging message (926). When triggered by a configuration alignment event (928) (e.g., DRX configuration not aligned with PRS configuration), WTRU sends an indication to gNB (RAN) to update the DRX configuration in an initial access (e.g., Msg A) / RNAU message (930). RAN updates the WTRU's DRX configuration to align with the PRS configuration (932). WTRU receives the updated DRX configuration in a RAN paging message (934). When the gNB receives a location request from the LMF or DL ​​data from the AMF (936), the gNB pagees the WTRU in a CN paging or RAN paging message (938). The WTRU may also receive a PRS during the same time period in which the paging message is received. The WTRU measures the DL PRS (940) (e.g., during the DRX on duration) and sends a measurement report to the gNB / LMF in an initial access (e.g., SDT) or RNAU message (942). The gNB sends the measurement report to the LMF (944).

[0566] In idle / inactive mode, WTRU sends SRSp based on the trigger condition for sending TA / RNA update messages.

[0567] In one implementation, the WTRU in idle / inactive mode transmits SRSp for UL positioning based on a trigger condition that sends a TA / RNA update message. In this case, the WTRU may be configured with one or more associated SRSp configurations (e.g., consisting of different SRSp IDs, resources, power, and periodicity), which may also be configured with an associated tracking area by the CN or with an RNA by the RAN. For example, an SRSp configuration (e.g., SRSp ID X) may be associated with a tracking area consisting of at least one cell in cell list A (e.g., cell IDs 1, 2, ..., N), and / or may be associated with an RNA consisting of at least one cell in cell list B (e.g., cell IDs 1, 2, ..., M). The list of cells configured in the WTRU for tracking areas and / or RNA for SRSp transmission may be the same or different lists of cells associated with tracking areas and / or RNA configured for idle / inactive mode mobility.

[0568] In one implementation, the WTRU can be triggered to transmit SRSp based on one or more of the following conditions:

[0569] ● Detected a first cell ID outside the list of cells that can be associated with existing / current tracking areas and / or RNA configured in the WTRU.

[0570] ● Detected the first cell ID within a list of cells that can be associated with different tracking regions and / or RNAs configured in the WTRU.

[0571] The WTRU can determine the parameters of the SRSp used for UL transmission based on the mapping between the SRSp configuration and the associated cell list in the TA / RNA configured in the WTRU. The WTRU can continue transmitting the SRSp according to the SRSp configuration until a termination condition is met (e.g., detecting a different cell ID inside / outside the TA / RNA cell list, timer timeout, or receiving a DL paging message).

[0572] Figure 10Example of a signaling flow for SRS configuration and RNA alignment during location inactivity mode mobility of a WTRU is shown. Before transitioning to RRC inactivity mode, the WTRU 201 is initially configured with RNA by the RAN (1020). When triggered by the LMF (1022), the WTRU sets the SRS configuration in a RAN paging message (1024). When triggered by a location mobility event (1026) (e.g., the WTRU detects a new cell ID outside the RNA), the WTRU transmits an SRSp along with an RNAU message (1028). Finally, the gNB 203 measures the SRSp (1030), and the gNB sends a measurement report to the LMF 205 (1032).

[0573] WTRU receive trigger in idle / inactive mode to update SRSp configuration based on configured TA / RNA.

[0574] In one implementation, when in idle / inactive mode, the WTRU can receive a trigger to update its SRSp configuration based on an SRSp transmitted by the WTRU to at least one cell outside the configured tracking area and / or RNA. Specifically, in idle / inactive mode, a WTRU configured to perform UL-based or UL+DL-based positioning can use configured resources to transmit the SRSp and WTRU identifier (e.g., a CN-assigned ID such as TMSI, or a RAN-assigned ID such as I-RNTI). When the WTRU approaches a cell boundary or moves to a cell where the SRSp transmitted by the WTRU is invalid or the resources are not aligned with the TA / RNA, the WTRU can receive a paging message from the network to perform one of the following:

[0575] ● Update resource / SRSp configuration: For example, WTRU can receive paging messages containing one or more of the following:

[0576] ○ Disable triggers that use existing SRP configurations, where the triggers may include time / area restrictions (e.g., timer duration, cell ID, and / or AoD) for disabling the use of resources associated with the SRP configuration.

[0577] ○ Changes to SRSp configuration, wherein the request to change the SRSp configuration may be included in the same first paging message or in a different second RAN paging message sent after the first paging message.

[0578] ○ Select a different SRSp, wherein the instruction to (re)select an SRSp may include an identifier of the SRSp configuration selected by the network from a set of SRSps pre-configured in the WTRU.

[0579] ●Update TA / RNA: For example, the WTRU can receive a request to send a TA / RNA update message or receive an updated TA / RNA containing the updated cell ID in a paging message, whereby the WTRU can continue to use the existing SRSp configuration during mobility.

[0580] Figure 11 This is an example of a trigger-based signaling flow for SRS configuration and RNA alignment during location in WTRU inactive mode mobility, according to another implementation. Before transitioning to RRC inactive mode, WTRU 203 is initially configured with RNA by the RAN (1120). When triggered by LMF (1122), WTRU sets SRSp configuration in the RAN paging message (1124). When triggered by an activated SRSp indication identifier in the RAN paging message (1126), WTRU transmits SRSp (1128). If triggered by location mobility (e.g., the SRSp detected in the RAN at gNB / TRP differs from the RNA configured in WTRU) (1130), WTRU may set RNA update and / or SRSp configuration update in the RAN paging message (1132), and WTRU updates its RNA / SRSp accordingly (1134). Finally, the WTRU transmits the SRSp (1136), which is measured at gNB 203 (1138), and the measurement report is sent to LMF 205 (1140).

[0581] The WTRU receives an instruction to use the CG configuration in RRC inactive / idle mode during mobility.

[0582] In one implementation, the WTRU can receive a configuration for the CG, which can be used when moving to a new cell / gNB, allowing the WTRU to continue performing positioning while remaining in RRC inactive / idle mode. For example, the WTRU can receive the CG configuration from the source cell / gNB (e.g., in an RRC Release message) for use in sending positioning information and / or measurement reports (e.g., periodically). Along with the CG configuration, the WTRU can also be configured by the source cell / gNB with one or more validity conditions, such as a TA timer, a validity period, and / or a validity area (e.g., a cell ID possibly associated with RNA), which can be verified by the WTRU when using the CG in RRC inactive / idle mode.

[0583] In this scenario, for example, when the WTRU moves to a new cell where the new cell ID is within the validity area, the WTRU can continue using the CG configuration to send location information using SDT while remaining in RRC inactive / idle mode. When one or more validity conditions expire, and the WTRU moves to a new / target cell / gNB outside the validity area, the WTRU can send an RCResumeRequest message (e.g., in Msg A or Msg3) with a reason value indicating the expiration and release of the previous CG configuration and / or a request for a new CG configuration. For example, the WTRU can include an identifier associated with the previous CG configuration along with its own identifier (e.g., an Inactive Radio Network Temporary Identifier (I-RNTI)) in the RCResumeRequest. When the WTRU context is retrieved from the source cell / gNB, the target cell / gNB can determine, based on the identifier sent by the WTRU, whether the WTRU will be assigned / activated with a new CG configuration or can continue using the previous CG configuration. In response to the RCResumeRequest, the WTRU can receive one or more of the following from the target cell / gNB:

[0584] - Instructs the WTRU to use the new CG configuration's RRCResume message (e.g., in Msg B or Msg 4).

[0585] - An RRCRelease message instructing the WTRU to release the previous CG configuration and use the new CG configuration (e.g., in Msg B or Msg 4).

[0586] - Instructs the WTRU to continue using the previously configured RRCRelease message.

[0587] The RRCResume message and / or RRCRelease message may include parameters associated with the new CG configuration (e.g., periodicity, time / frequency resources) or may include an activation indication (e.g., the configuration ID) for activating a pre-configured CG configuration.

[0588] WTRU receives auxiliary data in RRC inactive / idle mode during mobility.

[0589] In one implementation, when moving to a new cell / gNB while continuing to operate in RRC inactive / idle mode, the WTRU acquires auxiliary data, which may contain one or more positioning configurations (e.g., PRS / SRSp configurations). When within the coverage of the source cell / gNB, the WTRU may initially receive auxiliary data via broadcast or dedicated RRC signaling upon triggering an LPP procedure for positioning. In this case, for example, when in RRC connected mode or when transitioning to RRC inactive / idle mode, the WTRU may receive auxiliary data in dedicated signaling (e.g., in an RRC Release message).

[0590] In one example, when moving to a new cell / gNB and requesting new auxiliary data, the WTRU can receive validity conditions associated with the auxiliary data (e.g., timers, cell IDs in the validity region), which can be used to verify the applicability of the auxiliary data. Alternatively, the WTRU can receive configuration / rules to determine whether the request for new auxiliary data is sent in dedicated NAS / RRC signaling or obtained via broadcast RRC signaling (i.e., SIB) (potentially including on-demand SIB). For example, the configuration / rule could indicate a first set including one or more cell / gNB IDs (where the WTRU may be allowed to send requests for new auxiliary data) and a second set including one or more cell / gNB IDs (where the WTRU may receive new auxiliary data in broadcast signaling), the second set potentially overlapping at least partially with the first set.

[0591] When conditions / rules associated with the transmission request are met (e.g., a new cell / gNB ID is outside the validity zone), a WTRU in RRC inactive / idle mode may send a request in an RCResumeRequest for new auxiliary data for one or more new PRS and / or SRSp configurations. The WTRU may include an identifier associated with the WTRU (e.g., I-RNTI) and previous auxiliary data (e.g., PRS / SRSp configuration ID) in the RCResumeRequest. The new cell / gNB may obtain the WTRU context from the source cell / gNB based on the WTRU ID and may implicitly determine the request for new auxiliary data from the WTRU when verifying the release / invalidation of previous auxiliary data from the auxiliary data ID. Alternatively, the WTRU may include a reason value in the RCResumeRequest indicating the expiration and / or release of previous auxiliary data / configuration for requesting new auxiliary data. In response to this request, the WTRU may receive new auxiliary data, an activation indication for pre-configured auxiliary data (i.e., a pre-configured PRS / SRSp configuration), or an indication to continue using previous auxiliary data. For example, the WTRU can receive this response indication in an RRC Resume message or an RRC Release message (i.e., in Msg B or Msg 4). Alternatively, an RRC Resume message or an RRC Release message can instruct the WTRU to obtain new auxiliary data via broadcast RRC signaling.

[0592] Minimum accuracy requirements and delays for MT-LR positioning

[0593] Example of minimum accuracy requirement

[0594] The WTRU can receive minimum accuracy or latency requirements associated with the PRS configuration received by the WTRU from the network (e.g., LMF, gNB). For example, the accuracy and / or latency requirements may be related to location QoS indicated by a higher layer / application (e.g., LCS client) associated with the WTRU. The minimum / maximum accuracy and / or latency requirements can be at least one of the following metrics:

[0595] ● A threshold for the standard deviation / variance of location estimates performed by the WTRU or measurements performed by the WTRU (e.g., RSRP, TDOA, time of arrival, angle of arrival): For example, the WTRU may receive a PRS configuration associated with the threshold, indicating that the PRS configuration can generate a standard deviation / variance below the threshold.

[0596] ● Threshold for the minimum / maximum range of location estimation or measurement (e.g., RSRP, TDOA, time of arrival, angle of arrival): For example, the WTRU can receive a PRS configuration associated with the threshold, indicating that the PRS configuration can generate a minimum / maximum value higher / lower than the threshold.

[0597] ● Latency Threshold: The WTRU can receive from the network an indication that the PRS configuration and measurement report configuration meet the indicated accuracy requirements. For example, the WTRU can receive multiple PRS configurations from the LMF, where the number of PRS resources is 3, 6, and 9. The WTRU can receive latency requirements (100ms, 200ms, 400ms) associated with the corresponding number of resources, indicating that measurements on 3, 6, and 9 PRS resources will produce latency of less than 100ms, less than 200ms, and less than 400ms, respectively.

[0598] ● Accuracy Thresholds: The WTRU can receive multiple PRS configurations from the network, indicating various accuracy levels (e.g., meter-level, centimeter-level) associated with each PRS configuration. For example, the WTRU can receive two PRS configurations from the network, one consisting of 6 PRS resources and the other consisting of 20 PRS resources. The WTRU can also receive configurations that associate the configuration with 6 PRS resources with meter-level and the configuration with 20 PRS resources with centimeter-level accuracy, respectively, indicating that the WTRU can achieve centimeter-level accuracy positioning using 20 PRS resources. The granularity of accuracy is not limited to the granularity of one accuracy level described in this example. The WTRU can also receive the association of accuracy requirements with different PRS configuration parameters, such as the number of repetitions, the number of TRPs from which the PRS is transmitted, the number of symbols, the number of repetitions, the comb value / factor, the bandwidth, the silence mode, the number of PRS resources, the PRS resource set, the frequency layer, etc.

[0599] Exemplary implementation using minimum accuracy / delay requirements

[0600] In implementations, the WTRU may be configured with one or more PRS configurations and / or be notified which of the indicated PRS configurations meets the minimum positioning QoS requirements (e.g., accuracy, latency) associated with the positioning service. In one example, the WTRU may receive a PRS configuration and / or associated identifier in a first indication (e.g., in LPP auxiliary data or SIB), followed by a second indication containing information about which PRS configurations (e.g., IDs / tags) meet the minimum accuracy (and / or latency) requirements. Alternatively, the WTRU may receive a PRS configuration and an indication in the same message (e.g., auxiliary data) that indicates which PRS configurations (e.g., IDs / tags) meet the minimum accuracy (and / or latency) requirements. Furthermore, based on comparisons of measurements taken and / or positioning information calculations relative to positioning information determined using one or more other reference positioning methods (e.g., GNSS positioning), the WTRU may determine which of the (pre-)configured PRS configurations provided to the WTRU meet the minimum accuracy requirements.

[0601] In one implementation, when the WTRU is operating in either an RRC connected or RRC inactive state, the WTRU may select a PRS configuration for measurement from one or more pre-configured PRS configurations received from the network (e.g., LMF and / or gNB). This selection may be based at least on whether the chosen PRS configuration meets the minimum accuracy requirements associated with the WTRU's positioning service. For example, when the WTRU is operating in an inactive state and is configured with SDT for transmitting data in the UL, other criteria used by the WTRU to select the PRS configuration may include a data volume threshold configured by the network (e.g., gNB). In this case, the WTRU may be (pre-)configured with one or more PRS configurations, where different PRS configurations may include measurement configurations (e.g., PRS resources for performing measurements) and / or reporting configurations (e.g., information about which measurements to report). For example, the reporting configuration may indicate whether to report: the absolute value of measurements performed on each of N resources, the average value of measurements when averaging over N resources, and selected measurements selected based on measurements higher / lower than a configured threshold, etc. When sending measurement reports to the network in the uplink, different reporting configurations can result in different payload sizes. The (desired) payload size of the measurement report associated with the reporting configuration can be determined by the network instructing the WTRU (e.g., in auxiliary data) or by the WTRU based on an estimate of the number of bits obtained in the measurement report before or after the measurement is performed.

[0602] Upon receiving a PRS configuration (i.e., a measurement configuration and / or a reporting configuration) and an SDT configuration (e.g., a data volume threshold) for use during inactive operation, the WTRU can select a PRS configuration such that the selected configuration meets minimum accuracy requirements and / or the resulting payload size of the measurement report is less than or equal to the data volume threshold associated with the resource (e.g., RACH / CG) configured for the SDT. If at least one of the PRS configurations received from the network meets minimum accuracy (and / or latency) requirements and results in a measurement report with a payload size less than or equal to the SDT data volume threshold, the WTRU can select a PRS configuration from the (pre-)configured settings to perform the measurement. In this case, for example, the WTRU can select a PRS configuration such that the resulting difference between the payload size of the measurement report and the configured data volume threshold is minimized.

[0603] For example, when selecting such a PRS configuration, the WTRU can perform measurements on the PRS and can send measurement reports to the network using resources configured for the SDT (e.g., RACH and / or CG) when inactive. In one example, the WTRU may include information related to the selected PRS configuration and / or the data volume threshold configured for use with the SDT, along with the measurement reports sent to the network (e.g., LMF). Alternatively, if no PRS configuration in the (pre-configured) PRS configurations meets the minimum accuracy (and / or latency) requirements and / or results in a measurement report whose payload size is less than or equal to the SDT data volume threshold, the WTRU may send an indication to the gNB requesting a transition to the RRC connected state (e.g., in an RRCResumeRequest message). This will enable the WTRU to perform measurements using an appropriate PRS configuration (e.g., a PRS configuration that meets the minimum accuracy / latency requirements) and to send measurement reports to the network when operating in the connected state.

[0604] Figure 13 The foregoing exemplary implementation is illustrated, including a process by which the WTRU performs positioning measurements and reporting in an inactive and / or connected state based on accuracy requirements and SDT data volume thresholds. More specifically, at step 1, the WTRU (e.g., from the LMF) receives one or more PRS configurations, which include measurement configurations and measurement reporting configurations. The WTRU may also receive indications of which configurations among the various configurations meet which minimum accuracy requirements. Optionally, at step 2, the WTRU may send a measurement report to the serving gNB, which may include a payload of a determined size for the PRS configuration. At step 3, the serving gNB may send an SDT configuration including a data volume threshold to the WTRU.

[0605] Next, at step 4, the WTRU can eventually enter an inactive state (e.g., due to data inactivity). While in an inactive state, the WTRU determines at step 5 whether any PRS configuration meets the minimum accuracy requirement and has a payload size smaller than the established data volume threshold. If either of these conditions is not met, the WTRU will seek to return to the connected state so that it can perform measurements and / or report its measurements to the network (step 6b). On the other hand, if both conditions are met, the WTRU then remains in an inactive state to perform measurements and / or report these measurements to the network (step 6a). Specifically, in an implementation, the WTRU selects a PRS configuration from those meeting the minimum accuracy requirement that has a payload size closest to, but less than, the SDT data volume threshold, performs measurements according to the selected configuration, and sends a measurement report to the LMF using the SDT. This report may include measurement information as well as indications of the selected PRS configuration and the SDT data volume threshold.

[0606] In this implementation, the WTRU can be configured (e.g., from the LMF) to receive auxiliary data including one or more PRS configurations (each PRS configuration including a measurement configuration and a measurement reporting configuration), wherein at least some of the PRS configurations are indicated to meet minimum accuracy requirements. The WTRU can send (to the gNB) an indication (to the gNB) of the payload size (of the measurement reports) associated with the one or more PRS configurations (the payload size is determined by the WTRU or indicated by the LMF). The WTRU can receive (from the gNB) a Small Data Transfer (SDT) configuration, which includes a Data Volume Threshold (DVT) for the SDT (indicating the maximum payload size for the SDT). In one example, when at least one of the received PRS configurations indicated to meet the minimum accuracy requirement has a payload size smaller than the associated payload size of the DVT for the SDT: the WTRU can select the PRS configuration with the closest associated payload size to the DVT for the SDT from the at least one PRS configuration meeting the minimum accuracy requirement, perform a PRS measurement, and (in an inactive state) use the SDT to send a measurement report based on the selected PRS configuration (e.g., to the LMF), where the measurement report indicates the selected PRS configuration and the DVT for the SDT. As another example, when none of the PRS configurations indicated to meet the minimum accuracy requirement have an associated payload size smaller than the DVT for the SDT, the WTRU can send a connection request (to the gNB) (e.g., to transition to a connected state to be able to send measurement reports).

[0607] Delayed MT-LR localization in inactive state

[0608] In one implementation, while operating in an inactive state, the WTRU can perform location-related actions, including selecting a PRS configuration, performing measurements on the DL-PRS, and transmitting measurement reports / location estimates, when triggered by one or more events configured by the delayed MT-LR location process. Delayed MT-LR location refers to the process in which a higher layer / application (e.g., an LCS client) within the network can establish and configure a location service session (e.g., an LPP session) involving the LMF, AMF, and WTRU. In this case, upon receiving a delayed MT-LR request from a higher layer / application, the WTRU can be configured with a PRS configuration and one or more triggering events for the WTRU to use the PRS configuration to monitor and perform measurements. For example, when the WTRU detects a triggering event, it performs measurements and sends a measurement report (e.g., for WTRU-assisted mode) or a location estimate (e.g., for WTRU-based mode) to the LMF. The LMF then sends the WTRU's location information to the higher layer / application. The delayed MT-LR procedure is typically configured for use when the WTRU can operate in RRC connected state, where the positioning procedures (e.g., LPP procedure) associated with the WTRU receiving auxiliary data (e.g., composed of PRS configuration), performing measurements, and sending measurement reports can be performed without regard to any low-power operation or any limitations in the size of the payload that can be supported for measurement report transmission.

[0609] To support delayed MT-LR in inactive / idle mode, the WTRU should be able to perform one or more location-related actions before, during, or after a configured event trigger. When performing location-related actions (including measuring and transmitting measurement reports / location estimates when a trigger event is detected), the WTRU may, for example, use one or more pre-configured PRS configurations. The pre-configured PRS configurations received by the WTRU may include one or more aperiodic, periodic, and / or semi-persistent PRS configurations, where using different configurations for measurement may result in, for example, different location QoS (e.g., accuracy, latency). In this case, the PRS configuration may be received by the WTRU while it is in a connected state, while the detection of the trigger event and the execution of the location-related actions may be completed when transitioning to an inactive state. For example, a trigger event configured in the WTRU for delayed MT-LR may include one or more of the following:

[0610] - Time / Sequence Events: WTRU can perform measurements when a sequence event starts / exits (e.g., the start / timeout of a timer with a configured duration). For fixed-configuration time periods, WTRU can perform measurements periodically, for example, based on the periodicity of the time period.

[0611] - Area / Mobility Events: When one or more configured cell IDs are detected during mobility, the WTRU can perform measurements. In this case, for example, when entering a coverage area that includes at least one new cell, the WTRU can perform measurements and send a measurement report.

[0612] - End of Data / Control Channel Reception: When the reception of a PDCCH or PDSCH is completed during an inactive state, the WTRU may perform measurements. The WTRU may receive from the network an indication of the PDCCH or PDSCH (e.g., DCI) that the WTRU can receive. After receiving the indicated PDCCH or PDSCH, the WTRU should perform measurements on the PRS.

[0613] In one implementation involving inactive / idle mode operation, the WTRU can associate the detection of one or more triggering events with the selection of a (pre-)configured PRS configuration, such that measurements performed in inactive / idle mode and the determined WTRU location information result in satisfaction of location QoS requirements (e.g., accuracy, latency) associated with the delayed MT-LR. In one example, the WTRU may potentially be configured with one or more triggering events when a set of PRS configurations (e.g., in LPP auxiliary data) is received. When transitioning to an inactive state, the WTRU may be configured by the gNB with one or more data volume thresholds associated with the payload size of data to be transmitted in the uplink using resources (e.g., RACH / CG) associated with the SDT configuration. When operating in an inactive state, the WTRU can select a PRS configuration upon detection of a triggering event, wherein the selection of the PRS configuration may be based on various factors, including a data volume threshold for the measurement report payload size, location QoS requirements (e.g., minimum accuracy / latency), and / or the type of the detected triggering event (e.g., timing, mobility). For example, the WTRU can select a PRS configuration such that the resulting payload size of the measurement report is less than a data volume threshold, meets the minimum accuracy requirements of the delayed MT-LR, and / or corresponds to the type of triggering event. When performing measurements using the selected PRS configuration, the WTRU can use resources configured for the SDT to send measurement reports, which may include, for example, information about the selected PRS configuration, the size of the data volume threshold, and / or the type of triggering event detected.

[0614] WTRU reports subgroups of measurements during inactive mode positioning.

[0615] Smaller number of reports to be submitted

[0616] To reduce the amount of measurement reports during the inactive mode, the WTRU can be configured by the network (e.g., LMF or gNB) to report a subgroup of the measurements that the WTRU makes during RRC_CONNECTED. For example, if the WTRU is configured to report measurements for up to M PRS resources during RRC_CONNECTED, the WTRU can be configured by the network to report up to N PRS resources, where N < M. As another example, the WTRU can be configured to report at least one of the following measurements / parameters with a reduced measurement resolution / granularity or number of measurements during inactive mode positioning:

[0617] ● The number of paths in a multipath channel

[0618] ● The number of PRS resources

[0619] ● The resolution / granularity of RSRP

[0620] ● The resolution / granularity of time of arrival, TDOA, RSTD

[0621] ● The resolution / granularity of Rx-Tx time difference

[0622] ● The resolution / granularity of angle of arrival, angle of departure

[0623] Reduced reporting frequency

[0624] As another example, the WTRU can be configured to report measurement reports at different periods. Compared to the number of occasions when the WTRU is in the connected mode, the WTRU can be configured with a smaller number of measurement report occasions (e.g., longer intervals between reports). For example, the WTRU can be configured with a decimation / silence mode (e.g., represented in a bitmap mode) that indicates which measurement occasions the WTRU should skip or report during the inactive mode. For example, during the connected mode, the WTRU can be configured to report once every 1 ms. However, compared to the reporting occasions during the connected mode, when the WTRU is in the inactive mode, the WTRU can be configured to report once every 10th occasion. Therefore, when the WTRU transitions to the inactive mode, the WTRU can report once every 10 ms. When the WTRU is in the connected mode, the configuration of the reporting occasions for the inactive mode can be sent to the WTRU. Once the WTRU transitions from the inactive mode to the connected mode, the WTRU can revert to the reporting configuration it had during the connected mode (i.e., once every 1 ms).

[0625] For example, the WTRU can be configured (e.g., in connected mode) to send a certain number of measurement reports to the network. For instance, when the WTRU is in inactive mode, it can be configured to send N measurement reports. After sending these N measurement reports, the WTRU can send an indication to the network requesting further location information. Alternatively, after sending N measurement reports to the network, the WTRU can terminate location services. Furthermore, when the WTRU is in inactive mode, it can be configured to continue sending measurement reports at a configured periodic rate until it switches to connected mode.

[0626] Determine and transmit location information

[0627] In one implementation, a method for reporting location information to a network in a WTRU includes: receiving an indication from the network to initiate a location report while in a low-power connection state; performing location measurements while maintaining the low-power connection state in response to the indication; and transmitting the location report to the network. In one example, the indication is received during a RACH process. The low-power connection state can be one of an RRC idle mode and an RRC inactive mode. In one example, in response to the indication from the network, the method may include: 1) transmitting a request to switch to an RRC_CONNECTED mode; and 2) transmitting a signal to the network indicating the WTRU's ability to perform a location report while in the low-power connection state.

[0628] In one example, the instruction from the network includes a location reporting configuration for that WTRU.

[0629] In one example, the method may include: transmitting a request to the network for configuration for location measurements and / or reporting while in the low-power connection state.

[0630] In one example, the WTRU can divide the location report into multiple independent messages.

[0631] In one example, the method may include: configuring a data volume threshold for at least one signaling radio bearer (SRB); and transmitting the measurement report in small data transmission (SDT) on the at least one SRB with the configured data volume threshold when the amount of the measurement report is less than the data volume threshold configured for the SRB. In some cases, the method may include: receiving the data volume threshold configuration from an LMF of the network.

[0632] In one example, the method may include transmitting to the network information indicating the size of the measurement data to be transmitted. This information indicating the size of the measurement data to be transmitted may be transmitted in any of a Radio Resource Control (RRC) message, a Medium Access Control (MAC) control element (CE), or an Uplink Control Information (UCI).

[0633] In one example, the method may include: dynamically reconfiguring the data volume threshold for the at least one SRB. Dynamically reconfiguring the data volume threshold for the at least one SRB may include: determining that the size of the measurement data to be transmitted exceeds a default data volume threshold for the applicable SRB but is less than a second data volume threshold for the applicable SRB that is greater than the default threshold; and in response to the determination, transmitting a recovery request to the network containing an indication associated with the second data volume threshold.

[0634] In one example, the method may include: determining that the size of the measurement data to be transmitted exceeds a data volume threshold, and in response to the determination, segmenting the measurement data into fragments smaller than the data volume threshold and transmitting the data in the fragments.

[0635] In one example, the method may include determining the amount of measurement data to be transmitted to the network based on the data volume threshold.

[0636] In one example, the method may include: receiving from the network an indication of at least one Positioning Reference Signal (PRS) configuration, the at least one PRS configuration including a configuration for performing measurements and a configuration for reporting measurements to the network; receiving from the network an indication of a positioning determination quality level satisfied for each PRS configuration; and selecting a PRS configuration to be used in a low-power connectivity state based on satisfying a minimum positioning accuracy threshold and a maximum measurement payload size threshold. The indication of the positioning determination quality level satisfied for each PRS configuration may include at least one of the positioning determination accuracy and the positioning determination delay. The PRS configuration may be determined / selected based on a criterion that minimizes the difference between the payload size reported in the measurement and the maximum payload size requirement.

[0637] In some examples, if the WTRU does not have a PRS configuration that satisfies the minimum positioning accuracy threshold and the maximum measurement payload size threshold, the WTRU may transmit a request to the network to switch to connected mode.

[0638] In some examples, the indication for determining the quality level of the location includes at least one of the following: a threshold for the standard deviation / variance of the location estimate; a threshold for the range of the location estimate; a threshold for delay; and / or a threshold for accuracy.

[0639] In one implementation, a method for reporting location information to a network in a WTRU includes: receiving auxiliary data comprising one or more Positioning Reference Signal (PRS) configurations (each PRS configuration may include a measurement configuration and a measurement reporting configuration), wherein at least one of the PRS configurations is indicated to meet a minimum accuracy requirement; (e.g., to a gNB) sending an indication of the payload size (for measurement reporting) associated with the one or more PRS configurations; (e.g., from the gNB) receiving a Small Data Transmission (SDT) configuration including a Data Volume Threshold (DVT) for the SDT (e.g., indicating a maximum payload size for the SDT); and if at least one of the one or more received PRS configurations indicated to meet the minimum accuracy requirement is received... A PRS configuration has a payload size smaller than the associated payload size of the DVT for the SDT: From the at least one PRS configuration that meets the minimum accuracy requirement, select a PRS configuration with an associated payload size closest to the DVT for the SDT; and perform a PRS measurement and send a measurement report to the LMF using the SDT based on the selected PRS configuration (e.g., in an inactive state), wherein the measurement report indicates the selected PRS configuration and the DVT for the SDT; and if none of the PRS configurations indicated to meet the minimum accuracy requirement has a payload size smaller than the associated payload size of the DVT for the SDT, then (e.g., to the gNB) a connection request is sent (e.g., to transition to a connected state so that the measurement report can be sent).

[0640] References

[0641] The following references have been mentioned above and are incorporated herein by reference in their entirety: [1] 3GPP, “User Equipment (UE) positioning in NG-RAN,” TS 38.305, ver.16.1.0, July 2020; and [2] 3GPP, “Radio Resource Control (RRC) protocol specification,” TS 38.331, ver.16.1.0, July 2020.

[0642] in conclusion

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

[0644] Furthermore, the above embodiments specify processing platforms, computing systems, controllers, and other devices including processors. These devices may include at least one central processing unit (“CPU”) and memory. According to the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions can be executed by various CPUs and memories. Such actions and operations or instructions can be considered as being “executed,” “computer-executed,” or “CPU-executed.”

[0645] Those skilled in the art will recognize that the actions and symbols representing operations or instructions include the CPU's manipulation of electrical signals. The electrical system represents data bits that can result in the final transformation or reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise altering the CPU's operation and performing other signal processing. The memory location holding the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing 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 also support the provided methods.

[0646] Data bits may also be stored on a computer-readable medium, including disks, optical disks, and any other CPU-readable volatile (e.g., random access memory (“RAM”)) or non-volatile (e.g., read-only memory (“ROM”)) mass storage system. The computer-readable medium may include cooperative or interconnected computer-readable media that are uniquely present on the processing system or distributed across multiple interconnected processing systems, which may be local or remote relative to the processing system. It should be understood that representative embodiments are not limited to the memory described above, and other platforms and memories may also support the method described.

[0647] 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 a processor of a mobile unit, network element, and / or any other computing device.

[0648] There is little difference between the hardware and software implementations of various aspects of the system. The use of hardware or software typically (but not always, as the choice between hardware and software can become important in certain contexts) represents a design choice that weighs cost against efficiency. Various media (e.g., hardware, software, and / or firmware) may exist to implement the processes and / or systems and / or other technologies described herein, and the preferred media may vary depending on the context of deployment. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose a media that is primarily hardware and / or firmware. If flexibility is most important, the implementer may choose a primarily software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0649] The above detailed description has illustrated various embodiments of the apparatus and / or process using block diagrams, flowcharts, and / or examples. Where such block diagrams, flowcharts, and / or examples contain one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware, or virtually any combination thereof. Suitable processors include (by way of example) general-purpose processors, special-purpose 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 machine.

[0650] Although features and elements have been provided above in specific combinations, those skilled in the art will understand that each feature or element may be used alone or in any combination with other features and elements. This disclosure is not limited to the specific embodiments described in this patent application, which are intended as examples of various aspects. Many modifications and variations are possible without departing from the spirit and scope of the invention, as will be apparent to those skilled in the art. Unless expressly stated otherwise, no element, action, or description used in this specification should be construed as essential or necessary to the invention. Based on the foregoing description, functionally equivalent methods and apparatus within the scope of this disclosure, other than those listed herein, will be apparent to those skilled in the art. Such modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only to the terms of the appended claims and the full scope of equivalents of such claimed claims. It should be understood that this disclosure is not limited to any particular method or system.

[0651] It should also be understood that the terminology used herein is for the purpose of describing specific embodiments only and is not intended to be limiting. As used herein, when referred to herein, the term “station” and its abbreviation “STA”, “user equipment” and its abbreviation “UE” may mean: (i) a wireless transmitting and / or receiving unit (WTRU), as described below; (ii) any of several embodiments of a WTRU, as described below; (iii) equipment having wireless and / or wired (e.g., tetherable) capabilities configured with some or all of the structure and functions of a WTRU, as described below; (iii) equipment having wireless and / or wired capabilities configured with fewer than all the structure and functions of a WTRU, as described below; or (iv) etc. This document is relative to Figures 1A to 1D Details of an exemplary WTRU that may represent any WTRU described herein are provided.

[0652] In some representative embodiments, portions of the subject matter described herein may be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integration formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein are, wholly or partially, equivalently implemented in an integrated circuit as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware, or virtually any combination thereof, and that designing circuitry and / or writing software and / or firmware code according to this disclosure will be entirely within the skill of those skilled in the art. Furthermore, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as program products in various forms, and the exemplary embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used to actually implement that distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media (such as floppy disks, hard disks, CDs, DVDs, digital magnetic tapes, computer memory, etc.); and transmission media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).

[0653] The topics described herein sometimes illustrate different components contained within or connected to different other components. It should be understood that such depicted architectures are merely examples, and many other architectures can in fact achieve the same functionality. Conceptually, any arrangement of components achieving the same function is effectively “associated” to enable the desired functionality. Therefore, any two components combined herein to achieve a particular function can be considered “associated” with each other to enable the desired functionality, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to each other to achieve the desired functionality, and any two components that can be suchly associated can also be considered “operably coupled” to each other to achieve the desired functionality. Specific examples of operably coupled components include, but are not limited to, components that can physically cooperate and / or physically interact and / or components that can wirelessly interact and / or logically interact and / or logically interact.

[0654] Regarding virtually any plural and / or singular terms used herein, those skilled in the art can appropriately convert them from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed herein.

[0655] Those skilled in the art will understand that, in general, the terminology used herein, particularly in the appended claims (e.g., the body of the appended claims), is typically intended as “open-ended” terms (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” etc.). Those skilled in the art will also understand that if it is intended to specify a particular number of introduced claim objects, such intention will be explicitly stated in the claims, and if no such claim objects are present, such intention will not exist. For example, the term “single” or similar language may be used where only one item is anticipated. To aid understanding, the appended claims and / or the description herein may contain the use of the introductory phrases “at least one” and “one or more” to introduce claim objects. However, the use of such phrases should not be construed as implying that any particular claim containing such introduced claim objects is limited to an embodiment containing only one such claim object by using the indefinite articles “a” or “an.” This is true even when the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce the subject matter of a claim. Furthermore, even when a specific number of the introduced subject matter of a claim is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the stated number (e.g., a bare statement of "two subject matters" without other modifiers means at least two subject matters, or two or more subject matters). Additionally, in instances where conventions such as "at least one of A, B, and C" are used, generally speaking, such constructions mean that those skilled in the art will understand that convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, systems having A alone, having B alone, having C alone, having both A and B, having both A and C, having both B and C, and / or having both A, B, and C, etc.). In instances where conventions such as "at least one of A, B, or C" are used, generally speaking, such a construction implies that a person skilled in the art will understand that the convention (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having both A and B, having both A and C, having both B and C, and / or having both A, B, and C, etc.). A person skilled in the art should also understand that, in fact, any separate words and / or phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one term, any one of the terms, or both terms.For example, the phrase “A or B” will be understood to include the possibility of “A” or “B” or “A and B”. Additionally, as used herein, the term “any one of…” followed by a list of multiple items and / or multiple item categories is intended to include items alone or in combination with other items and / or other item categories, “any one of,” “any combination,” “any multiple,” and / or “any combination of multiples of.” Furthermore, as used herein, the term “group” or “cluster” is intended to include any number of items, including zero. Additionally, as used herein, the term “quantity” is intended to include any quantity, including zero.

[0656] Furthermore, where features or aspects of this disclosure are described in accordance with the Markush Group, those skilled in the art will recognize that this disclosure is also described in accordance with any individual member of the Markush Group or a subgroup of its members.

[0657] As those skilled in the art will understand, for any and all purposes (such as for providing a written description), all scopes disclosed herein also encompass any and all possible subscopes and combinations thereof. Any listed scope can be readily identified as sufficiently descriptive and such that the same scope can be divided into at least two equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily divided into a lower third, a middle third, and an upper third, etc. As those skilled in the art will also understand, all language such as “at most,” “at least,” “greater than,” “less than,” etc., includes the referenced number and refers to a scope that can subsequently be divided into subscopes as described above. Finally, as those skilled in the art will understand, a scope includes each individual number. Thus, for example, a group having 1 to 3 units means a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units means a group having 1, 2, 3, 4, or 5 units, etc.

[0658] Furthermore, unless otherwise stated, the claims should not be construed as being limited to the order or elements provided. Additionally, the use of the term "means for..." in any claim is intended to invoke 35 U.S.SC §112. 6. The claim format is either device plus function, and any claim without the term "device for..." is not intended to be so.

[0659] While the invention has been shown and described herein with reference to specific embodiments, it is not intended to be limited to the details shown. Rather, various modifications may be made to the details within the scope and domain of the equivalents of the claims without departing from the invention.

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

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

[0662] Furthermore, the above embodiments specify processing platforms, computing systems, controllers, and other devices including processors. These devices may include at least one central processing unit (“CPU”) and memory. According to the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions can be executed by various CPUs and memories. Such actions and operations or instructions can be considered as being “executed,” “computer-executed,” or “CPU-executed.”

[0663] Those skilled in the art will recognize that actions and symbols representing operations or instructions include the CPU's manipulation of electrical signals. Electrical systems represent data bits that can lead to the final transformation or reduction of electrical signals and the retention of data bits at memory locations in a memory system, thereby reconfiguring or otherwise altering the CPU's operations and performing other signal processing. The memory location holding the data bits is a physical location having specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits.

[0664] Data bits may also be stored on a computer-readable medium, including disks, optical disks, and any other CPU-readable volatile (e.g., random access memory (“RAM”)) or non-volatile (e.g., read-only memory (“ROM”)) mass storage system. The computer-readable medium may include cooperative or interconnected computer-readable media that are uniquely present on the processing system or distributed across multiple interconnected processing systems, which may be local or remote relative to the processing system. It should be understood that representative embodiments are not limited to the memory described above, and other platforms and memories may also support the method described.

[0665] Unless explicitly described herein, no element, action, or description used in this application specification should be construed as essential or necessary to the invention. Additionally, as used herein, the article “a” is intended to include one or more items. Where only one item is anticipated, the term “a” or similar language is used. Furthermore, as used herein, the term “any one of…” followed by a list of multiple items and / or multiple item categories is intended to include items alone or in combination with other items and / or other item categories, “any one of,” “any combination,” “any multiple,” and / or “any combination of multiples of.” Moreover, as used herein, the term “group” is intended to include any number of items, including zero. Additionally, as used herein, the term “quantity” is intended to include any quantity, including zero.

[0666] Furthermore, unless otherwise stated, the claims should not be construed as being limited to the order or elements described. Additionally, the use of the term "apparatus" in any claim is intended to invoke 35 U.S.SC §112. 6. And any claim that does not use the term "device" is not intended to be so.

[0667] Suitable processors include (by way of example) general-purpose processors, special-purpose 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 arrays (FPGAs), any other type of integrated circuit (IC) and / or state machines.

[0668] The software-associated processor can be used to implement the radio frequency transceiver in a Transmitter-Receiver Unit (WTRU), User Equipment (UE), terminal, base station, Mobility Management Entity (MME), or Evolved Packet Core (EPC), or any host. The WTRU can be used in conjunction with modules and can be implemented in hardware and / or software including: Software-defined Radio (SDR) and other components such as cameras, video camera modules, videophones, speakerphones, vibration devices, speakers, microphones, television transceivers, hands-free headsets, keypads, etc. Modules, FM radio units, Near Field Communication (NFC) modules, Liquid Crystal Display (LCD) units, Organic Light Emitting Diode (OLED) units, Digital Music Players, Media Players, Video Game Players, Internet Browsers, and / or any Wireless Local Area Network (WLAN) or Ultra-Wideband (UWB) modules.

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

[0670] Furthermore, while the invention has been shown and described herein with reference to specific embodiments, it is not intended to be limited to the details shown. Rather, various modifications may be made to the details within the scope and domain of equivalents of the claims without departing from the invention.

Claims

1. A wireless transmit / receive unit (WTRU), the WTRU comprising: The processor is configured as follows: A configuration for receiving a detection reference signal (SRS) for positioning, wherein the configuration includes information indicating one or more SRS resources, valid area information associated with the configuration, and valid time information associated with the configuration, wherein the valid area information associated with the configuration includes one or more cells indicated by a cell ID; Switch to inactive mode; Initialize the validity timer according to the validity time information indicated by the configuration; During operation in the inactive mode, a first SRS transmission is sent using one or more of the configured SRS resources; It has been determined that the WTRU has been moved to a different cell; Under the condition that the different cells are one of the cells included in the validity area information associated with the configuration, and under the condition that the validity timer is running, the second SRS transmission is sent using the one or more configured SRS resources; If the different cells are not among the one or more cells included in the validity area information associated with the configuration, a connection recovery process is initiated, wherein the processor is configured to send a recovery request message during the connection recovery process, and wherein the recovery request message includes a reason value indicating an SRS configuration request.

2. The WTRU of claim 1, wherein the configuration is received in a Radio Resource Control (RRC) release message.

3. The WTRU of claim 1, wherein the processor is configured to initialize the validity timer according to the validity time information indicated by the configuration during transition to the inactive mode.

4. The WTRU of claim 1, wherein the processor is configured to suppress the transmission of SRS according to the configuration if the validity timer has expired.

5. The WTRU of claim 1, wherein the information indicating the one or more SRS resources includes information indicating the following: frequency location information, frequency hopping information, spatial relationship information, transmission power information, or symbol information.

6. The WTRU of claim 1, wherein the configuration includes information indicating an SRS resource set, the SRS resource set including the one or more SRS resources.

7. The WTRU of claim 1, wherein the processor is configured to: Generate a Small Data Buffer Status Report (BSR) Media Access Control (MAC) Control Element (CE), wherein the Small Data BSR MAC CE indicates a request for uplink location resources, wherein the WTRU is configured with a logical channel associated with the transmission of location report bits, the location report bits being associated with small data transmission, and the Small Data BSR MAC CE being triggered based on the generation of the location report bits; In the case that the WTRU has uplink shared data resources available for transmission, the small data BSR MAC CE indicating the request for the uplink location resources is multiplexed in the uplink shared data resources; The small data BSR MAC CE indicating the request for uplink location resources is sent using the uplink shared data resources; and Once a subsequent small data transfer is sent using a different Small Data Transfer (SDT) resource, the small data BSR MACCE is cancelled.

8. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: A configuration for receiving a detection reference signal (SRS) for positioning, wherein the configuration includes information indicating one or more SRS resources, valid area information associated with the configuration, and valid time information associated with the configuration, wherein the valid area information associated with the configuration includes one or more cells indicated by a cell ID; Switch to inactive mode; Initialize the validity timer according to the validity time information indicated by the configuration; During operation in the inactive mode, SRS transmissions are sent using one or more of the configured SRS resources; It has been determined that the WTRU has been moved to a different cell; Under the condition that the different cells are one of the one or more cells included in the validity area information associated with the configuration, and under the condition that the validity timer is running, the one or more configured SRS resources are used to send a second SRS transmission; If the different cells are not among the one or more cells included in the validity area information associated with the configuration, a connection recovery process is initiated, wherein the connection recovery process includes sending a recovery request message during the connection recovery process, and wherein the recovery request message includes a reason value indicating an SRS configuration request.

9. The method according to claim 8, wherein, The configuration is received in a Radio Resource Control (RRC) release message.

10. The method according to claim 8, wherein, The validity timer is initialized during the transition to the inactive mode.

11. The method of claim 8, further comprising: If the validity timer has expired, the transmission of SRS is suppressed according to the configuration.

12. The method according to claim 8, wherein, Information indicating the one or more SRS resources includes information indicating the following: frequency location information, frequency hopping information, spatial relationship information, transmission power information, or symbol information.

13. The method according to claim 8, wherein, The configuration includes information indicating an SRS resource set, which includes the one or more SRS resources.

14. The method of claim 8, further comprising: Generate a Small Data Buffer Status Report (BSR) Media Access Control (MAC) Control Element (CE), wherein the Small Data BSR MAC CE indicates a request for uplink location resources, wherein the WTRU is configured with a logical channel associated with the transmission of location report bits, the location report bits being associated with small data transmission, and the Small Data BSR MAC CE being triggered based on the generation of the location report bits; In the case that the WTRU has uplink shared data resources available for transmission, the small data BSR MAC CE indicating the request for the uplink location resources is multiplexed in the uplink shared data resources; The small data BSR MAC CE is sent using the uplink shared data resource to indicate the request for the uplink location resource; as well as Once a subsequent small data transfer is sent using a different Small Data Transfer (SDT) resource, the small data BSR MACCE is cancelled.

Images