Global navigation satellite system (GNSS) reporting for reduced capability devices

Abstract

A wireless transmit-receive unit (WTRU) is configured to receive configuration information for reporting global navigation satellite system (GNSS) assistance information (AI). The configuration information includes a report trigger threshold that is at least one of a distance threshold or a time offset threshold. The WTRU determines that the report trigger threshold is exceeded and reports the GNSS AI. The GNSS AI includes at least one of a GNSS validity duration or a GNSS acquisition time. The GNSS validity duration includes an indication of a duration associated with validity of the GNSS acquisition, an indication of a duration associated with expiration of the GNSS acquisition, or a WTRU location associated with the GNSS acquisition. The GNSS acquisition time includes a time for acquiring GNSS positioning.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 410,321, filed September 27, 2022. The entire contents of which are incorporated herein by reference in their entirety. Background Art

[0003] The Global Navigation Satellite System (GNSS) may include global, regional, and augmented satellite systems, such as GPS, Galileo, and GLONASS systems. In certain scenarios, the GNSS may be designed to interwork with the network. If the GNSS is designed to interwork with the network, the network may assist the WTRU GNSS receiver to improve performance. Summary of the invention

[0004] A wireless transmit receive unit (WTRU) may be configured to receive configuration information for reporting global navigation satellite system (GNSS) assistance information (AI). The configuration information may include a reporting trigger threshold, the reporting trigger threshold being at least one of a distance threshold or a time offset threshold. The WTRU may determine that the reporting trigger threshold is exceeded. The WTRU may report the GNSS AI. The GNSS AI may include at least one of a GNSS validity duration or a GNSS acquisition time. The GNSS validity duration may include an indication of a duration associated with the validity of a GNSS acquisition, an indication of a duration associated with an expiration of a GNSS acquisition, or a WTRU position associated with a GNSS acquisition. The GNSS acquisition time may include a time for acquiring a GNSS position.

[0005] The GNSS AI may include at least one of a measurement gap configuration or a configuration index.

[0006] The WTRU may also be configured to modify the distance threshold or the time offset threshold based on at least one of the speed of the WTRU, the mobility state of the WTRU, or at least one characteristic of a satellite of the non-terrestrial network.

[0007] Reporting GNSS AI may be accomplished using different types of signaling based on reporting GNSS validity duration or GNSS acquisition time.

[0008] The reporting trigger threshold may be exceeded when the WTRU is scheduled to send or receive a transmission at a time that is less than a time offset threshold from the expiration of the GNSS validity duration.

[0009] The reporting trigger threshold may be exceeded when the WTRU's current location exceeds the previously reported WTRU location by a configured threshold.

[0010] The WTRU may suspend user plane and control plane traffic (eg, reception and transmission) to receive GNSS information.

[0011] The WTRU may be an Internet of Things (IoT) device.

[0012] The WTRU may be a reduced capability (RedCap) device.

[0013] GNSS AI position reports can be sent using the Medium Access Control (MAC) Information Element (IE).

[0014] Reporting GNSS AI can be included in the measurement report.

[0015] Reporting GNSS AI may be done using WTRU capability signaling.

[0016] The WTRU may be further configured to receive the measurement gap configuration based on exceeding the reporting trigger threshold, wherein the measurement gap configuration is associated with a length of time for which the WTRU reception and transmission are suspended.

[0017] The WTRU may also be configured to monitor a reporting trigger threshold to determine if the reporting trigger threshold has been exceeded.

[0018] When the GNSS AI includes a GNSS validity duration, the GNSS AI may be reported via a medium access control (MAC) information element (IE), and when the GNSS AI includes a GNSS acquisition time, the GNSS AI is reported via a radio resource control (RRC) based on an RRC state.

[0019] A wireless transmit receive unit (WTRU) may receive at least one inhibition condition configured to inhibit GNSS activity via configuration information. The GNSS activity may include at least one of GNSS acquisition, GNSS reporting, or GNSS assistance information (AI) reporting. The WTRU may identify a trigger related to the GNSS activity. The WTRU may determine whether the inhibition condition is activated. The inhibition condition may include a condition based on an inhibition timer, a condition based on a GNSS validity duration, or a condition based on a characteristic of the WTRU. When the inhibition condition is determined to be active, the WTRU may perform the GNSS activity in response to an override or termination of the inhibition condition and based on the inhibition condition being determined to be active.

[0020] The WTRU may perform GNSS activity when the prohibition condition is determined to be inactivity. The characteristic of the WTRU may include at least one of a GNSS acquisition AI, a change in position, or a change in speed of the WTRU.

[0021] The WTRU may determine coverage or termination of an inhibit condition in response to: one or more triggering events for GNSS reporting or reporting occurring during an inhibit period, where the inhibit period exceeds a threshold; receipt of an explicit coverage request; or expiration of a GNSS validity timer during an inhibit condition.

[0022] When an inhibit condition is determined to be active, the WTRU may monitor one or more trigger conditions. The inhibit condition may be based on one or more of the following: GNSS validity duration, WTRU position, or WTRU speed.

[0023] In the execution of GNSS activities, the WTRU may report via medium access control (MAC) information element (IE) when the GNSS AI includes the GNSS validity duration, and report via radio resource control (RRC) based on the RRC state when the GNSS AI includes the positioning fix duration.

[0024] When the GNSS reporting condition is met and the inhibit condition is active, the WTRU may perform one or more of the following: delay GNSS activity until the inhibit condition is not active or expires, indicate that the inhibit condition is active, or indicate when GNSS activity is enabled.

[0025] The WTRU may stop sending and receiving data signals, control signals and reference signals (e.g., SSB, PRS, CSI-RS) to receive GNSS information. The WTRU may be an Internet of Things (IoT) device. The WTRU may be a Reduced Capability (RedCap) device.

[0026] A wireless transmit receive unit (WTRU) may be configured to perform global navigation satellite system assistance information (GNSSAI) reporting. The WTRU may receive a GNSS configuration. The GNSS configuration may include one or more trigger conditions associated with the GNSS AI report. The GNSS configuration may further include a bias condition associated with each of the one or more trigger conditions. The WTRU may apply a bias to each of the one or more trigger conditions. For example, the bias may be applied based on one or more of the following: a speed associated with the WTRU, a mobility state estimate, and / or a characteristic associated with a satellite. The WTRU may detect a trigger condition in one or more trigger conditions. The WTRU may send a GNSS AI report based on the detection of the trigger condition. For example, a GNSS AI report may be sent using a medium access control (MAC) information element. For example, the GNSSAI report may be included in a measurement report. For example, the GNSS AI report may be sent using WTRU capability signaling. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0028] Figure 1B is a diagram showing that according to an embodiment, Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the communication system is shown;

[0029] Figure 1C is a diagram showing that according to an embodiment, Figure 1A A system diagram of an example radio access network (RAN) and an example core network (CN) used within the illustrated communication system;

[0030] Figure 1D is a diagram showing that according to an embodiment, Figure 1A System diagram of another example RAN and another example CN used within the communication system shown.

[0031] Figure 2 An example associated with a non-terrestrial network (NTN) is shown;

[0032] Figure 3 An example associated with a protocol stack is shown;

[0033] Figure 4A and 4B An example associated with GNSS acquisition is shown;

[0034] Figure 5 An example associated with a measurement gap configuration is shown;

[0035] Figure 6 An example associated with a reporting process is shown;

[0036] Figure 7 shows an example associated with a GNSS report; and

[0037] Figure 8 Another example associated with a reporting process is shown. DETAILED DESCRIPTION

[0038] Figure 1A1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero-tail unique-word DFT-spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC), etc.

[0039] 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, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. As an example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a "station" and / or "STA") may be configured to send and / or receive wireless signals and may include a user equipment (WTRU), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone. Medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), consumer electronic devices, devices operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a WTRU.

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

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

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

[0043] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 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).

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

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

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

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

[0048] As an example, Figure 1A The base station 114b in the example may be a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any appropriate RAT to facilitate wireless connectivity in a local area, such as a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In an embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell by utilizing a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). Figure 1A As shown, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.

[0049] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although in Figure 1A Although not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

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

[0053] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of 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), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal encoding and decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

[0056] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11).

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

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

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

[0060] The processor 118 may also be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game console module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The peripherals 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0061] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., signals associated with specific subframes for both 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 to reduce and / or substantially eliminate self-interference via hardware (e.g., choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., signals associated with specific subframes for both UL (e.g., for transmission) or ...

[0062] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0063] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

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

[0065] Figure 1C The illustrated CN 106 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.

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

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

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

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

[0070] Although the WTRU Figures 1A to 1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may use (eg, temporarily or permanently) a wired communication interface with a communication network.

[0071] In a representative embodiment, other network 112 may be a WLAN.

[0072] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that sends traffic into and / or out of the BSS. Traffic originating from outside the BSS to the STA may arrive through the AP and may be delivered to the STA. Traffic originating from the STA to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent (e.g., directly) between the source STA and the destination STA using direct link establishment (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0073] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may send beacons on a fixed channel (e.g., a primary channel). The primary channel may be a fixed width (e.g., a 20MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented, such as in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. At any given time in a given BSS, one STA (e.g., only one station) may transmit.

[0074] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, by combining a 20 MHz wide primary channel with an adjacent or non-adjacent 20 MHz wide channel to form the 40 MHz wide channel.

[0075] Very High Throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining 8 consecutive 20MHz channels or by combining two non-contiguous 80MHz channels (this can be referred to as an 80+80 configuration). For the 80+80 configuration, the data after channel coding can pass through a segment parser, which can divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed on each stream separately. The stream can be mapped onto two 80MHz channels, and the data can be sent by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

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

[0077] WLAN systems (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) that can support multiple channels and channel bandwidths include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA from all STAs operating in the BSS that support the minimum bandwidth operating mode. In the example of 802.11ah, for STAs (e.g., MTC type devices) that support (e.g., only support) 1MHz mode, the primary channel may 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 sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports the 1MHz operating mode) sends to the AP, the entire available band may be considered busy even if most of the band remains idle and may be available.

[0078] In the United States, the available frequency band that 802.11ah can use is from 902MHz to 928MHz. In South Korea, the available frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is from 916.5 MHz to 927.5 MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.

[0079] Figure 1D 1 is a system diagram showing the RAN 113 and the CN 115 according to an embodiment. As described above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

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

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

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

[0083] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to a user plane function (UPF) 184a, 184b, routing of control plane information to an access and mobility management function (AMF) 182a, 182b, and the like. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0084] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include a data network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

[0086] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

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

[0088] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local data network (DN) 185a, 185b through the UPF 184a, 184b via an N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0089] In view of Figures 1A to 1D and about Figures 1A to 1D In accordance with the corresponding description of the present invention, one or more or all of the functions described herein for one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a-c, AMFs 182a-ab, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0090] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or an operator network environment. For example, 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 in order to test other devices within the communication network. 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. For testing purposes, the simulation device may be directly coupled to another device, and / or over-the-air wireless communications may be used to perform testing.

[0091] One or more emulated devices may perform one or more functions, including all functions, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulated devices may be used in a test lab and / or in a test scenario in a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more emulated devices may be test devices. The emulated devices may send and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0092] As described herein, global navigation satellite systems (GNSS) may include global, regional, and augmented satellite systems, such as GPS, Galileo, and GLONASS systems. In certain scenarios, the GNSS may be designed to interwork with a network (e.g., NG-RAN). If the GNSS is designed to interwork with a network, the network may assist the WTRU GNSS receiver to improve performance (e.g., limit the search window and increase sensitivity). Assistance data signaling from the network to the WTRU may include one or more of the following: data to assist measurements, data that may be used for positioning calculations, data that may be used to increase positioning accuracy, and / or data that may facilitate determination of integrity of the calculated position result.

[0093] One or more GNSS modes may be supported. For example, WTRU-assisted GNSS and / or WTRU-based GNSS may be supported. In WTRU-assisted GNSS, for example, the WTRU may perform GNSS measurements (e.g., pseudorange, pseudoDoppler, carrier phase range, etc.). The WTRU may send the GNSS measurements to the network (e.g., a network function such as LMF). Positioning calculations may be performed based on GNSS measurements and / or additional measurements from other (e.g., non-GNSS) sources. In WTRU-based GNSS, for example, the WTRU may perform GNSS measurements. The WTRU may calculate its own position based on GNSS measurements, additional measurements from other (e.g., non-GNSS) sources, and / or assistance data from the network (e.g., a network function such as LMF).

[0094] The information may be sent to the network (eg, a network function such as LMF) based on the relevant GNSS mode (eg, WTRU-assisted and / or WTRU-based). For example, Table 1 provides an example of information that may be transmitted from the WTRU to the network.

[0095] Table 1

[0096] information WT-RU Assist WTRU-based / Standalone Latitude / longitude / altitude, and indeterminate shapes no yes Speed ​​and uncertain shape no yes Reference time, possibly together with GNSS to NG-RAN time association and uncertainty yes yes Indication of positioning method used in fixation no yes Code phase measurement, also called pseudorange yes no Doppler measurement yes no Carrier phase measurement, also known as accumulated delta range (ADR) yes no The carrier-to-noise ratio of the received signal yes no Measurement quality parameters for each measurement yes no Additional, non-GNSS related measurement information yes no

[0097] Non-terrestrial networks (NTNs) can be used to facilitate the deployment of certain networks (e.g., wireless networks in areas where land-based antennas such as those are impractical due to geography and / or cost). Terrestrial networks can be coupled with NTNs, which can increase network coverage. NTN deployments can support talk, text, and / or enhanced services (e.g., web browsing).

[0098] The NTN may include an airborne and / or space-based bearer platform that transmits signals from land-based gNBs to WTRUs and vice versa via a gateway (GW). The NTN may support, for example, power class 3 WTRUs with omnidirectional antennas and linear polarization and / or very small aperture antenna (VSAT) terminals with directional antennas and circular polarization. Additionally or alternatively, the NTN may support LTE-based narrowband IoT (NB-IoT) and eMTC type devices.

[0099] Airborne and / or space-born platforms may be classified according to orbit. Low Earth Orbit (LEO) satellites may include satellites associated with an altitude range of 300-1500 km. Geostationary Earth Orbit (GEO) satellites may include satellites associated with an altitude range of 35-786 km. Medium Earth Orbit (MEO) satellites may include satellites associated with an altitude range of 7000-25000 km. High Altitude Platform Stations (HAPS) may include stations associated with an altitude of 8-50 km. Satellite platforms may be further classified by payload (e.g., "transparent" and / or "regenerative"). For example, a transparent satellite payload may implement frequency conversion and RF amplification in both the uplink and downlink (e.g., utilizing multiple transparent satellites that may be connected to a land-based gNB). For example, a regenerative satellite payload may implement a gNB and / or a gNB distributed unit (DU) on a satellite. The regenerative payload may also or alternatively perform digital processing on the signal, including, for example, demodulation, decoding, recoding, remodulation, and / or filtering.

[0100] Figure 2 An example 200 associated with an interface in an NTN is shown. One or more radio interfaces may be defined in the NTN, including, for example: feeder links 202, 204, service links 206, and / or inter-satellite links (ISLs) 208. Feeder links 202, 204 may, for example, include wireless links between a gateway (GW) 210 and one or more corresponding satellites 212, 214. Service link 206 may, for example, include a radio link between a satellite and a WTRU 216. ISL 208 may include a transmission link between satellites. For example, an ISL may (e.g., may only) be supported by a regenerative payload and / or may be a 3GPP radio and / or a proprietary optical interface. The example 200 associated with an interface in the NTN may also include a central unit (CU).

[0101] Depending on the satellite payload configuration, different interfaces (e.g., 3GPP interfaces) may be used for the radio links (e.g., for each radio link). In a transparent payload, for example, a Uu interface (e.g., an NR-Uu radio interface) may be used for both the serving link and the feeder link. Uu may refer to the Universal Mobile Telecommunications System (UMTS) air interface, which is a radio interface between the UMTS Terrestrial Radio Access Network (UTRAN) and the WTRU 216 that utilizes code division multiple access (CDMA). For a regenerative payload, for example, a Uu interface (e.g., an NR-Uu radio interface) may be used on the serving link, and a satellite radio interface (SRI) may be used for the feeder link.

[0102] Figure 3 An exemplary user plane (UP) 302 and control plane (CP) 304 protocol stack 300 for a transparent satellite configuration is shown.

[0103] NTN satellites can support one or more cells. A cell can include one or more satellite beams. A satellite beam can cover a coverage area on the earth (e.g., like a terrestrial cell), which can vary in diameter. For example, the range of a beam in a low earth orbit (LEO) deployment can be 100-1000km. A beam in a geostationary orbit (GEO) deployment can be within a range of 200-3500km. The footprint of a beam in a GEO deployment can be fixed, for example, relative to the earth. In a LEO deployment, for example, the area covered by a beam / cell can change over time, for example, due to satellite movement. Beam movement in a LEO deployment can be classified as "earth moving". For example, a LEO beam can move continuously on the earth. In addition, or alternatively, a LEO beam can be "earth fixed" (e.g., where the beam is steered to maintain coverage of a fixed position), for example, until another cell takes over the coverage area with discrete and coordinated changes.

[0104] Due to the altitude and beam diameter of the NTN platform, the round trip time (RTT) and maximum differential delay may be larger than that of terrestrial systems. In a certain transparent NTN deployment, the RTT may range from 25.77 ms (e.g., LEO@600km altitude) to 541.46 ms (e.g., GEO), and the maximum differential delay may range from 3.12 ms to 10.3 ms. The RTT of the regenerated payload may be approximately half of the RTT of the transparent payload (e.g., because the transparent configuration may include both the serving link and the feeder link). The RTT of the regenerated payload may take into account (e.g., may only take into account) the serving link. The WTRU may, for example, perform timing precompensation before initial access, which may minimize the impact on the existing NR system (e.g., to avoid preamble ambiguity and / or to properly time the receive window).

[0105] During the pre-compensation process, the WTRU may obtain its position via GNSS. For example, the WTRU may obtain its position based on feeder link (or common) delay and / or satellite positioning (e.g., which may be determined via satellite ephemeris data). For example, satellite ephemeris data may be broadcast (e.g., periodically) in system information. For example, the satellite ephemeris data may include satellite velocity, direction, and / or speed. The WTRU may estimate the distance to the satellite (e.g., and delay). As an example, the WTRU may add a feeder link delay component to obtain the WTRU-gNB RTT (e.g., the complete WTRU-gNB RTT). The WTRU-gNB RTT may be used to offset timers, receive windows, and / or timing relationships. The WTRU may determine (e.g., assume) that frequency compensation may be performed by the network.

[0106] In certain scenarios, the NTN may support WTRU mobility and measurement reporting. The difference in reference signal received power (RSRP) between the cell center and the cell edge may be smaller in the NTN than in terrestrial systems. In addition, or alternatively, the NTN may be associated with larger cell overlap areas. Measurement-based mobility may be less reliable in an NTN environment. Conditional handover and / or measurement report triggering may be performed in the NTN. For example, conditional handover and / or measurement report triggering may depend on location and time, where the details are to be confirmed. Enhanced mobility may be supported in LEO deployments, where (e.g., due to satellite movement) a stationary WTRU may be expected to perform mobility (e.g., approximately every 7 seconds, for example, depending on deployment characteristics).

[0107] Non-terrestrial networks may be associated with large mobile cells and reduced effectiveness of measurement-based procedures, for example, due to reduced signal strength variation between the cell center and the cell edge. In certain scenarios, the location of the WTRU may be incorporated into one or more procedures, such as time / frequency pre-compensation, conditional handover (CHO), measurement reporting, and / or AMF determination. RAT-dependent positioning methods may not be supported in non-terrestrial networks, which may require NTN devices to maintain GNSS information (e.g., accurate GNSS information). Devices with NTN capabilities may also have GNSS capabilities.

[0108] The acquisition of GNSS information can be a time and power intensive process, which can cause issues for Internet of Things (IoT) and Reduced Capability (RedCap) devices (e.g., where reduced power consumption can be achieved). A subset of IoT and / or RedCap devices (e.g., NB-IoT) may not be able to support GNSS acquisition and data transmission / reception.

[0109] Figure 4A and Figure 4BAn example associated with GNSS acquisition is shown. Figure 4A As shown, in some NTN deployments, IoT traffic may be (e.g., limited to) short and sporadic traffic 406a, b, c, which may not affect GNSS acquisition 407. The WTRU may suspend user plane and control plane reception and transmission to receive GNSS information during GNSS acquisition 407. Techniques may be implemented to reduce GNSS acquisition time (e.g., position fix duration) (e.g., because scheduled transmission / reception is less likely to overlap with GNSS acquisition).

[0110] like Figure 4B As shown, in certain NTN deployments, IoT traffic may not be (e.g., limited to) short and infrequent traffic 408a-f, which may increase throughput and / or the probability of collision between the GNSS acquisition window and UL transmission / DL reception. The WTRU may tune away to acquire GNSS packets that cannot be received. Tuning away may include retuning the WTRU's receiver chain (e.g., antenna) to receive GNSS packets that the WTRU was previously unable to receive when previously tuned. In some cases, the first receiver (e.g., LTE) and the second receiver (e.g., GNSS) may each be located on separate chips (e.g., one LTE chip and one GNSS chip). In some limited capability devices (e.g., IoT devices), the two chips may not be able to operate simultaneously. If the WTRU is operating an LTE receiver to receive data, then the WTRU may not be able to receive GNSS data, and vice versa. Switching between operating receivers may be referred to herein as "tuning away." Figure 4B In some embodiments, the WTRU may be able to tune away from the first receiver to the GNSS receiver to receive and / or send GNSS data (e.g., switch from an LTE receiver to a GNSS receiver to receive GNSS data). In other cases, the WTRU may be able to operate the first receiver and the second receiver simultaneously without tuning away.

[0111] GNSS acquisition 410 may occur in time slots (or sub-bands) 412a, 412b where no UL transmission / DL reception occurs due to the WTRU tuning away. GNSS acquisition 410 may also occur in time slots (or sub-bands) 414a, 414b where no UL transmission / reception is scheduled. The timing and / or frequency of UL transmission / DL reception and GNSS acquisition may be varied (e.g., by the WTRU, gNB, and / or configuration information) such that the probability of collision is reduced.

[0112] To support GNSS acquisition in a higher traffic environment (e.g., which may occur in a GNSS acquisition window) 410, assistance information (AI) may be used for GNSS acquisition 410 (referred to herein as GNSS acquisition assistance information). The GNSS acquisition assistance information may be used to facilitate configuration of measurement gaps for GNSS acquisition. For example, the GNSS acquisition assistance information may include the time it takes the WTRU to acquire GNSS. Additionally or alternatively, the GNSS acquisition assistance information may include a validity duration of the GNSS information (e.g., the time before the WTRU reacquires GNSS). Techniques for preventing excessive GNSS acquisition (e.g., to limit WTRU power consumption) may be implemented.

[0113] One or more techniques may be implemented to report WTRU assistance information and / or support measurement gap configuration for GNSS acquisition. One or more techniques may be implemented to reduce excessive GNSS acquisition and reporting (eg, for power-constrained devices).

[0114] As disclosed herein, the term "GNSS" may be used to refer to the location / position of a WTRU, which may be used, for example, in a non-terrestrial network for timing advance calculation. However, the techniques described herein may also or alternatively be used with any suitable information (e.g., instead of and / or in addition to GNSS information). The terms "GNSS assistance information," "GNSS acquisition assistance information," and "measurement gap configuration assistance information" may be used interchangeably herein and may be used to describe assistance information reported by a WTRU (e.g., to assist in GNSS acquisition). The terms "IoT," "NB-IoT," and "eMTC" devices may be used to describe lower capability devices (e.g., lower capability devices supported by LTE). However, the techniques described herein may equally apply to other devices, including NR Reduced Capability (RedCap) devices.

[0115] GNSS acquisition and reporting techniques may be performed with IoT and / or reduced capability devices operating in non-terrestrial networks in mind. For example, WTRU assistance information may be used to support GNSS acquisition. Additionally or alternatively, excessive GNSS reporting may be reduced.

[0116] As described herein, a GNSS acquisition assistance information reporting process may be performed. One or more of the following may apply. The WTRU may receive an indication and / or configuration (indication / configuration) associated with a GNSS acquisition assistance information report (e.g., a GNSS AI report). For example, the WTRU may receive configuration information for reporting the GNSS AI. The indication / configuration may be provided via system information (e.g., if the AI ​​is sent in a RACH message) and / or via signaling (e.g., RRC configuration and / or signaling). The indication and / or configuration may include one or more of the following: an enable / disable flag, a report trigger (e.g., a period, a threshold), a signaling method to be used, a prohibition timer, and / or a possible measurement gap configuration. For example, the configuration information may include a report trigger threshold, which is at least one of a distance threshold or a time offset threshold, for example, as described herein.

[0117] The WTRU may monitor a trigger condition associated with a GNSS assistance information report. For example, the trigger condition may include a NW request. For example, the trigger condition may include a threshold (e.g., last time of GNSS report > time threshold, WTRU position change > number, etc.). For example, the WTRU may periodically send GNSS assistance information reports. The trigger threshold may be biased, for example, based on: WTRU speed, mobility state estimate, device type, measurements, satellite characteristics, etc.

[0118] If the WTRU determines that a trigger condition has been met (e.g., the WTRU determines that a trigger threshold has been exceeded), the WTRU may report GNSS assistance information. For example, the WTRU may report GNSS assistance information via a MAC CE (e.g., a GNSS acquisition assistance information MAC CE) and / or via RRC signaling (e.g., included in a WTRU capability report, a WTRU information response, and / or a measurement report). In certain scenarios, the WTRU may select among one or more signaling methods based on, for example, the content of the report, the RRC state, whether AS security has been activated, and / or the triggering condition that caused the GNSS acquisition assistance information report. For example, the GNSS assistance information (GNSS AI) may include, for example, one or more of the following: GNSS validity duration, GNSS acquisition time, characteristics of the WTRU's movement (e.g., WTRU speed, direction), preferred measurement gap configuration, and / or configuration index, etc. The characteristics of the WTRU may include at least one of the GNSS acquisition AI, a change in position, or a change in speed of the WTRU.

[0119] As described herein, the GNSS validity duration may include an indication of a duration associated with the validity of a GNSS acquisition, an indication of a duration associated with the expiration of a GNSS acquisition, or a WTRU position associated with a GNSS acquisition. In addition, as also described herein, the GNSS acquisition time may include the time at which a GNSS position fix is ​​acquired.

[0120] As described herein, excessive GNSS acquisition and / or reporting may be prohibited. One or more of the following may apply. GNSS reporting (e.g., GNSS reporting of measurements and / or location information) and GNSS AI reporting (e.g., as described herein) may be subject to one or more techniques to reduce the reporting frequency. For example, the WTRU may receive (e.g., via configuration) a condition to prohibit (e.g., temporarily prohibit) GNSS acquisition and / or reporting (e.g., GNSS reporting and / or GNSS AI reporting). The prohibition condition may apply to: GNSS acquisition, GNSS reporting, and / or GNSS assistance information reporting. For example, the prohibition condition may include one or more of the following: a prohibition timer (e.g., started when GNSS is acquired and / or at the last transmission of GNSS); a condition based on the GNSS validity duration (e.g., do not report and / or reacquire before X seconds of GNSS validity remain); and / or a condition based on WTRU characteristics, such as the WTRU's position change and / or the WTRU's speed (e.g., do not report GNSS unless the position changes by X meters and / or unless the WTRU speed>Y m / s).

[0121] GNSS reporting may include the WTRU reporting (e.g., to the network gNB) its location information (e.g., GNSS information) obtained via GNSS. GNSS AI reporting may include the WTRU reporting additional information (e.g., to the network, gNB, satellite) to support the WTRU in acquiring its GNSS information. For example, the AI ​​may include how long it took the WTRU to acquire GNSS, how long the WTRU remains valid before it will reacquire GNSS, etc. The triggers for GNSS reporting and GNSS AI reporting may be different. For example, a trigger for GNSS reporting may be new location information available (e.g., GNSS position). Whereas a trigger for GNSS AI reporting may be an increase in the time it takes to acquire GNSS (e.g., the WTRU is blocked by buildings, trees, and / or tunnels).

[0122] The WTRU may receive at least one inhibition condition configured to inhibit GNSS activity via configuration information. The GNSS activity may include at least one of GNSS acquisition, GNSS reporting, or GNSS assistance information (AI) reporting. The WTRU may identify a trigger related to the GNSS activity. The WTRU may determine whether the inhibition condition is activated. The inhibition condition may include a condition based on an inhibition timer, a condition based on a GNSS validity duration, and / or a condition based on a characteristic of the WTRU. When the inhibition condition is determined to be active, the WTRU may perform the GNSS activity in response to the override or termination of the inhibition condition and based on the inhibition condition being determined to be active.

[0123] As described herein, if a GNSS reporting condition is met (e.g., updated GNSS information is available and / or in response to a network request) and an inhibition condition is active, one or more of the following may occur. The WTRU may report GNSS and / or GNSS AI when the number of triggering events for GNSS reporting and / or GNSS AI reporting exceeds a threshold. The WTRU may delay GNSS reporting and / or GNSS AI reporting until the inhibition condition (e.g., one or more or all inhibition conditions) is inactive and / or expires. The WTRU may indicate that one or more inhibition conditions are active (e.g., via one or more flags). The WTRU may provide (e.g., send) an indication that GNSS reporting and / or GNSS AI reporting is (or will be) enabled again. For example, separate indications may be provided for GNSS reporting and GNSS AI reporting.

[0124] The WTRU may override the inhibition of GNSS reporting and / or GNSS acquisition assistance information reporting. For example, if the number of triggering events for GNSS reporting and / or GNSS acquisition assistance information reporting that occurs during the inhibition time exceeds a threshold, the WTRU may override the inhibition of GNSS reporting and / or GNSS acquisition assistance information reporting. If the WTRU receives a NW request (e.g., an indication to override the inhibition condition), the WTRU may override the inhibition of GNSS reporting and / or GNSS acquisition assistance information reporting. If the GNSS validity timer expires during the inhibition condition, the WTRU may override the inhibition of GNSS reporting and / or GNSS acquisition assistance information reporting. If, for example, the GNSS reporting condition is met and the inhibition condition is not active, the WTRU may report GNSS information (e.g., measurements and / or position) and / or GNSS AI information.

[0125] The WTRU may perform GNSS activity when the prohibition condition is determined to be inactivity. The characteristic of the WTRU may include at least one of a GNSS acquisition AI, a change in position, or a change in speed of the WTRU.

[0126] The WTRU may determine coverage or termination of an inhibit condition in response to: one or more triggering events for GNSS reporting or reporting occurring during an inhibit period, where the inhibit period exceeds a threshold; receipt of an explicit coverage request; or expiration of a GNSS validity timer during an inhibit condition.

[0127] When an inhibit condition is determined to be active, the WTRU may monitor one or more trigger conditions. The inhibit condition may be based on one or more of the following: GNSS validity duration, WTRU position, or WTRU speed.

[0128] In the execution of GNSS activities, the WTRU may report via medium access control (MAC) information element (IE) when the GNSS AI includes the GNSS validity duration, and report via radio resource control (RRC) based on the RRC state when the GNSS AI includes the positioning fix duration.

[0129] When the GNSS reporting condition is met and the inhibit condition is active, the WTRU may perform one or more of the following: delay GNSS activity until the inhibit condition is not active or expires, indicate that the inhibit condition is active, or indicate when GNSS activity is enabled.

[0130] The WTRU may stop sending and receiving data signals, control signals and reference signals (e.g., SSB, PRS, CSI-RS) to receive GNSS information. The WTRU may be an Internet of Things (IoT) device. The WTRU may be a Reduced Capability (RedCap) device.

[0131] A WTRU may be configured with measurement gaps (e.g., to enable the WTRU to acquire GNSS position / location information). Measurement gap configuration may be used for devices that are not capable of acquiring GNSS position information and sending / receiving data simultaneously (e.g., NB-IoT and / or Reduced Capability (RedCap) devices).

[0132] GNSS acquisition (e.g., duration and validity) may depend on WTRU capabilities / device type and / or WTRU specific characteristics (e.g., WTRU mobility and speed, which may be related to how often GNSS is updated). The WTRU may report assistance information to the network, for example, to facilitate measurement gap configuration for GNSS acquisition.

[0133] Figure 5 An example 500 associated with a measurement gap 506 configuration 502 for GNSS 508 acquisition (eg, based on WTRU reported assistance information 504) is shown.

[0134] The assistance information may include the GNSS 508 acquisition time and / or the validity of the current GNSS 508 position fix. One or more techniques associated with configuration, triggering, reporting, and signaling for GNSS 508 acquisition of assistance information may be implemented.

[0135] The WTRU assistance information may be used for GNSS 508 acquisition 504. One or more of the following may apply. The WTRU may report assistance information 504 to facilitate GNSS 508 acquisition. For example, the assistance information 504 may be used to facilitate measurement gap 506 configuration, for example, to avoid scheduling UL transmissions and / or DL ​​receptions during GNSS 508 acquisition, and / or to reduce excessive GNSS 508 acquisitions / reporting. In some cases, the measurement gap configuration may be associated with a length of time to suspend WTRU reception and transmission to reacquire GNSS. The WTRU may be an Internet of Things (IoT) device and / or a Reduced Capability (RedCap) device.

[0136] The WTRU may determine and / or report a validity duration of the acquired GNSS 508 information. The validity duration may, for example, include a time when the WTRU may no longer maintain time / frequency synchronization with the network. For example, in an NTN, if the GNSS 508 position used for timing advance reporting is no longer suitable for maintaining accurate time synchronization, the WTRU may no longer maintain time / frequency synchronization with the network. The validity duration may, for example, include a time when the WTRU should start GNSS 508 re-acquisition. For example, a GNSS 508 acquisition measurement gap 506 should start (or alternatively start) at the end of the validity duration. The validity duration may, for example, include a time when the GNSS 508 acquisition should be completed (for example, at least one GNSS 508 acquisition measurement gap 506 will be completed at the end of the validity duration). The validity duration may, for example, include a time when the GNSS 508 may not be used for WTRU procedures. For example, at the expiration of the GNSS 508 validity duration, the GNSS 508 position may not be used for timing advance calculations in non-terrestrial networks. The validity duration may, for example, include a time when the GNSS 508 information may not be reported. For example, after the GNSS 508 validity duration expires, the GNSS 508 position may no longer be reported to the network.

[0137] The WTRU may maintain the GNSS 508 validity duration, for example, via a timer. Upon successful acquisition of the GNSS 508, the WTRU may start the GNSS 508 validity timer. The duration of the timer may be preconfigured (e.g., via RRC signaling) and / or may be determined by the WTRU (e.g., based on characteristics of the WTRU, such as WTRU speed and capabilities). The WTRU may include the validity duration in the GNSS 508 assistance information report. Upon successful confirmation of the validity duration (e.g., via an ACK of a transmission carrying the validity duration), the WTRU may determine that the reported validity duration is the duration of the validity timer. Upon expiration of the timer, the WTRU may report and / or indicate to the network that the validity duration has expired.

[0138] In certain scenarios, the GNSS 508 validity duration may be represented and / or reported. For example, the GNSS 508 validity duration may be represented and / or reported via a duration (e.g., 10 seconds). For example, the GNSS 508 validity duration may be represented and / or reported via an absolute validity expiration time (e.g., until 12:10:35 UTC time). For example, the GNSS 508 validity duration may be represented and / or reported via a validity duration associated with a time of day (e.g., between absolute time 1 and time 2, the GNSS 508 may be considered valid for x seconds, between absolute time 3 and time 4, the GNSS 508 may be considered valid for y seconds, etc.). For example, the GNSS 508 validity duration may be represented and / or reported via a location-dependent validity duration (e.g., if the reported GNSS 508 position is between coordinate 1 and coordinate 2, then the reported GNSS 508 position is considered valid for x seconds; if the reported GNSS 508 position is between coordinate 3 and coordinate 4, then the reported GNSS 508 position is considered valid for y seconds, etc.).

[0139] The determination of the validity duration may be based on (eg, taking into account) WTRU characteristics including, for example, WTRU mobility, WTRU speed, and / or WTRU capabilities. The WTRU may be configured to report one or more WTRU characteristics (eg, such as those listed herein) for determining the validity duration.

[0140] The WTRU may determine and report the GNSS 508 acquisition time. The WTRU may be configured to determine the GNSS 508 acquisition time based on an earlier acquisition. For example, the WTRU may be configured to calculate the GNSS 508 acquisition time based on the mean / average / median of the last n GNSS 508 acquisitions, e.g., where n is a configurable value. For example, the WTRU may be configured to calculate the GNSS 508 acquisition time based on the mean / average / median of the GNSS 508 acquisitions completed within a certain configured time period. For example, the WTRU may be configured to calculate the GNSS 508 acquisition time based on filtered GNSS 508 acquisition times (e.g., where the most recent acquisition time has more weight than an earlier acquisition time).

[0141] The WTRU may be configured to determine GNSS 508 acquisition times that depend on a location range and / or duration. For example, GNSS 508 acquisition may be longer in certain locations (e.g., locations where there are shadowing elements (such as trees, tall buildings) and / or when the WTRU is indoors). As another example, the WTRU may be more likely to be indoors at certain times of the day, and the GNSS 508 acquisition times may be longer during those times. The WTRU may be configured to provide different sets of acquisition times that depend on location and / or time of day. For example, if the WTRU location is between coordinates 1 and 2, the WTRU may provide a first acquisition duration of X, and if the WTRU location is between coordinates 3 and 4, the WTRU may provide a second acquisition duration of Y, and so on. Additionally or alternatively, the WTRU may be configured to provide a first acquisition duration of A if the time of day is between absolute time 1 and time 2, and a second acquisition duration of B if the time of day is between absolute time 3 and 4, and so on.

[0142] The WTRU may be configured with a training period. For example, the training period may include a period during which the WTRU collects information about the acquisition time and validity duration of the GNSS 508 information. In some scenarios, the training period may be (e.g., may only be) applicable when the WTRU is in connected mode. In some scenarios, the training period may be (e.g., may only be) applicable when the WTRU is in idle / inactive mode. In some scenarios, the training period may be applicable regardless of the RRC state of the WTRU.

[0143] The WTRU may report additional assistance information to the network (e.g., in addition to the validity duration and / or acquisition time). For example, the WTRU may report the accuracy of the GNSS 508 information to the network (e.g., whether the GNSS 508 information is coarse and / or fine). For example, the WTRU may report the characteristics of the WTRU's movement to the network (e.g., WTRU speed, WTRU direction, etc.). For example, the WTRU may report other positioning information to the network (e.g., measurements and / or results associated with PRS, sPRS, AoA, AoD, multi-RTT, TDOA, etc.). For example, the WTRU may report characteristics associated with the serving satellite and / or neighboring satellites (e.g., satellite ephemeris and / or other aspects of satellite assistance information). For example, the WTRU may report the mobility state estimation status. For example, the WTRU may report whether the WTRU GNSS 508 information has been verified by the network. For example, the WTRU may report a preferred (or alternatively requested) measurement gap 506 configuration. If the WTRU reports a preferred measurement gap 506 configuration, the WTRU may be provided / indicated (or alternatively may have stored) one or more GNSS 508 measurement gap 506 configurations. Additionally or alternatively, the WTRU may indicate one or more preferred configurations, for example, via an index and / or indication of a measurement gap 506 ID. For example, the WTRU may report a preferred time and / or frequency resource for which the measurement gap 506 occurs.

[0144] The WTRU may receive an indication and / or configuration to report GNSS 508 acquisition assistance information and / or control aspects of GNSS 508 acquisition assistance information reporting. The WTRU may, for example, be configured: semi-statically (e.g., via RRC signaling); via an indication in system information and / or dynamically (e.g., via DCI and / or MAC CE; upon NW request). The configuration may apply (e.g., be active) for the duration of the connection (e.g., only when the WTRU is in RRC connected state, only when the WTRU is in RRC connected and / or RRC inactive state, applicable as long as the WTRU is attached to the network, e.g., even when in RRC idle state, etc.). The configuration may apply (e.g., be active) at a given time of the day (e.g., until 12:01:03 UTC time). The configuration may apply (e.g., be active) to a given location (e.g., between GNSS 508 coordinates 1 and 2). The configuration may apply (e.g., be active) to the next GNSS 508 acquisition report and / or X GNSS 508 report.

[0145] The WTRU may have one or more configurations. For example, the WTRU may receive configurations (e.g., different configurations) for: each serving cell; for a PCell and / or SPCell (e.g., compared to an SCell); and / or for each MAC entity (e.g., for each cell group, one for an MCG, one for an SCG, etc.).

[0146] Instructions and / or configurations to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting may include an enable / disable / pause GNSS 508 acquisition assistance information reporting flag.

[0147] The indications and / or configurations for reporting GNSS 508 acquisition assistance information and / or for controlling aspects of GNSS 508 acquisition assistance information reporting may include configurations associated with triggering GNSS 508 acquisition assistance information reporting. For example, the configurations associated with triggering GNSS 508 acquisition assistance information reporting may include location / distance based thresholds (e.g., WTRU moved x meters from last reported location, WTRU is within GNSS 508 coordinates x and y, etc.). For example, the configurations associated with triggering GNSS 508 acquisition assistance information reporting may include time based thresholds (e.g., WTRU reported X seconds ago, time of day is between absolute time 1 and time 2, etc.). For example, the configurations associated with triggering GNSS 508 acquisition assistance information reporting may include a periodicity between times when GNSS 508 is to be reported. For example, the configurations associated with triggering GNSS 508 acquisition assistance information reporting may include data dependent thresholds.

[0148] Instructions and / or configurations to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting may include an indication of the type of signaling to be used (eg, MAC CE, RRC).

[0149] The indication and / or configuration for reporting GNSS 508 acquisition assistance information and / or for controlling aspects of GNSS 508 acquisition assistance information reporting may include an indication of whether the reporting is applicable during random access. For example, the configuration may indicate that the GNSS 508 assistance information report may be included in a random access message. The configuration may also or alternatively indicate in which random access message the information is to be included.

[0150] The indication and / or configuration for reporting GNSS 508 acquisition assistance information and / or for controlling aspects of GNSS 508 acquisition assistance information reporting may include an indication of a bias to be applied to a trigger condition. For example, the configuration may include an indication of whether the WTRU applies a bias to one or more trigger conditions (e.g., see the section on “Scaling Reporting Based on WTRU Characteristics”).

[0151] Indications and / or configurations for reporting GNSS 508 acquisition assistance information and / or for controlling aspects of GNSS 508 acquisition assistance information reporting may include indications of whether to report complete assistance information, a subset of information, and / or incremental signaling. For example, the WTRU may be configured to report: certain GNSS 508 assistance information (e.g., validity time and GNSS 508 acquisition time); additional assistance information (e.g., GNSS 508 accuracy, characteristics of WTRU mobility, etc.); and / or values ​​that have changed (e.g., only validity time if GNSS 508 acquisition time has not changed; and / or a null report if no change has occurred, and / or no report at all).

[0152] The indication and / or configuration for reporting the GNSS 508 acquisition of assistance information and / or for controlling aspects of the GNSS 508 acquisition of assistance information reporting may include an indication of resources for reporting the assistance information. For example, the configuration may include an indication that the WTRU may report assistance information on configured grants (e.g., on all configured grants, or on one or more configured grants).

[0153] Instructions and / or configurations to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting may include a set of possible measurement gap 506 configurations for GNSS 508 acquisition.

[0154] The WTRU and / or the MAC entity may be configured with trigger conditions to report GNSS 508 acquisition assistance information. For example, the WTRU may report GNSS 508 assistance based on the receipt of a network request. For example, the WTRU may report GNSS 508 assistance based on an indication in system information. For example, the WTRU may report GNSS 508 assistance based on events based on thresholds (e.g., the WTRU has moved a certain distance since the WTRU last reported GNSS 508 acquisition assistance information, a certain amount of time has passed since the WTRU last reported GNSS 508 acquisition assistance information, etc.). For example, if the WTRU is at a certain location, the WTRU may report GNSS 508 assistance information (e.g., if the WTRU determines that it is located between GNSS 508 coordinates x and y for the first time, GNSS 508 acquisition assistance information is triggered, etc.). For example, the WTRU may report GNSS 508 assistance information during certain times of the day (e.g., GNSS 508 acquisition assistance information is triggered at absolute time t1, t2, etc.). For example, the WTRU may report GNSS 508 assistance information periodically. For example, if the validity time / duration of the last reported GNSS 508 has expired (e.g., and / or is about to expire), the WTRU may report the GNSS 508 assistance information. For example, if the WTRU has an UL grant and does not have enough UP / CP data to fill the grant, the WTRU may report the GNSS 508 assistance information (e.g., piggy-backed assistance information to use the remaining UL resources). For example, if the WTRU is scheduled during a time when the GNSS 508 is about to expire (e.g., the GNSS 508 validity is set to expire at a time before and / or during the time when the WTRU is scheduled for DL ​​reception and / or UL transmission), the WTRU may report the GNSS 508 assistance information. For example, the WTRU may report the GNSS 508 assistance information based on an RRC state transition (e.g., when establishing / resuming a connection). For example, the WTRU may report the GNSS 508 assistance information based on an RRM measurement report. For example, the WTRU may report the GNSS 508 assistance information based on an RLF report.

[0155] The WTRU may report and / or signal GNSS 508 assistance information (e.g., to support the WTRU in acquiring a GNSS 508 position) via one or more of: MAC CE; RRC signaling; RACH signaling (e.g., Msg3, MsgA, Msg5); UCI; PUSCH resources; and / or PUCCH resources.

[0156] The WTRU may report the assistance information using one or more (e.g., multiple) techniques. For example, the WTRU may select a given assistance information reporting technique based on the type of information to be sent. For example, if the information to be sent includes WTRU privacy (e.g., location information), the WTRU may send the assistance information via RRC signaling. Additionally or alternatively, if the information is sent during random access and / or if an RRC connection with AS security has not been established (e.g., if the WTRU is in RRC idle and / or RRC inactive state), the WTRU may send the message via PUSCH resources and / or via MAC CE.

[0157] For example, the WTRU may select a given assistance information reporting technology based on device type and / or device capabilities (e.g., eMTC and / or WTRU devices may use RRC signaling, NB-IoT devices may use MAC CE, etc.).

[0158] For example, the WTRU may select a given assistance information reporting technique based on the type of random access (eg, a WTRU performing a 2-step RACH may include messages within Msg 1A, a WTRU performing a 4-step RACH may include messages within Msg 3 and / or Msg 5, etc.).

[0159] For example, the WTRU may select a given assistance information reporting technique based on the gNB configuration (e.g., the WTRU may be configured to report information via MAC CE and / or RRC signaling).

[0160] The WTRU may select a given assistance information reporting technique based on the event and / or indication that triggered the reporting. For example, if the WTRU performs assistance information reporting based on the expiration of a validity timer (e.g., maintained in the MAC layer), the assistance information may be reported via the MAC CE. Additionally or alternatively, if the WTRU performs assistance information reporting based on an RRC state transition, the assistance information may be reported via RRC signaling.

[0161] For example, the WTRU may select a given assistance information reporting technique based on the RRC state the WTRU is in (eg, a WTRU in RRC_IDLE / INACTIVE may not use RRC signaling to send assistance information, a WTRU may use RRC signaling to report information in RRC_Connected state, etc.).

[0162] For example, the WTRU may select a given assistance information reporting technique based on whether AS security (e.g., and / or other forms of security) has been activated. For example, if (e.g., only if) AS security has been activated, then the WTRU may use RRC signaling. Otherwise, the WTRU may use MAC CE and / or other signaling.

[0163] The WTRU may send GNSS 508 acquisition assistance information via a MAC CE (e.g., a GNSS 508 Assistance Information MAC CE). For example, the GNSS 508 Assistance Information MAC CE may include one or more of the following information fields: an "activation / deactivation" request field (e.g., for configuration of measurement gaps 506, where the WTRU may indicate that it wants to activate a particular measurement gap 506); a cell ID field (e.g., where the measurement gap 506 is applicable); and / or WTRU assistance information for GNSS 508 acquisition (e.g., as described herein).

[0164] The WTRU may send one or more types of GNSS 508 Assistance Information MAC CEs. For example, the WTRU may send a "required" and / or "truncated" GNSS 508 Assistance Information MAC CE, which may include a subset of information (e.g., information used to configure the measurement gap 506, such as the GNSS 508 acquisition time and validity duration). For example, the WTRU may send a "full" GNSS 508 Assistance Information MAC CE, which may include additional assistance information (e.g., one or more of the additional information fields described herein).

[0165] The WTRU may determine whether to report a truncated GNSS 508 assistance information MAC CE and / or a full GNSS 508 assistance information MAC CE. For example, the WTRU may determine whether to report a full and / or truncated GNSS 508 assistance information MAC CE based on the amount of available resources that the WTRU may report (e.g., if the remaining available resources can support the full and / or truncated MAC CE and any additional header information). For example, the WTRU may determine whether to report a full and / or truncated GNSS 508 assistance information MAC CE based on a network configuration (e.g., the WTRU may be configured to report a truncated and / or full MAC CE). For example, the WTRU may determine whether to report a full and / or truncated GNSS 508 assistance information MAC CE based on a logical channel prioritization (LCP) procedure.

[0166] The WTRU may receive (e.g., via configuration, system information, based on specifications and / or dedicated signaling) a set of possible measurement gap 506 configurations associated with GNSS 508 acquisition. For example, each measurement gap 506 configuration may have an associated index and / or ID. The WTRU may send a MAC CE, which may indicate a preferred GNSS 508 measurement gap 506 configuration, as well as an indication to activate / deactivate the measurement gap 506.

[0167] The WTRU may report the GNSS 508 acquisition assistance information via RRC signaling. For example, the GNSS 508 acquisition assistance information may be included in a measurement report (eg, the WTRU may piggyback additional assistance information in a measurement report, which may be subject to explicit configuration).

[0168] The WTRU may include GNSS 508 acquisition assistance information with a WTRU capability report. For example, the WTRU may indicate that it is capable of reporting GNSS 508 assistance information, and / or may indicate that it can indicate one or more pieces of information (e.g., one or more of the WTRU assistance information described herein).

[0169] The WTRU may include the GNSS 508 with a WTRU INFORMATION REQUEST to acquire assistance information. For example, the WTRU may receive an indication of information to report via a WTRU INFORMATION REQUEST message. The indication may include specific types of information to include (e.g., one or more of the WTRU assistance information described herein). The WTRU may respond with a WTRU INFORMATION RESPONSE message and may include one or more of the requested information (if available).

[0170] The WTRU may report GNSS 508 assistance information during a random access procedure. The WTRU may suspend user plane and / or control plane reception and transmission to receive GNSS information. Reporting assistance information during random access may be controlled, for example, by an indication in system information and / or a message (e.g., RRC Release with Suspend message, which may be sent upon transition from RRC Connected to RRC Inactive state). The WTRU may be provided with an indication as to which random access message to include the GNSS 508 assistance information (e.g., Msg3, MsgA, and / or Msg5). The WTRU may be provided with an indication to enable / disable reporting during random access. The WTRU may be provided with an indication of information to include in the assistance information.

[0171] The WTRU may receive a measurement gap 506 configuration for GNSS 508 reporting. The measurement gap 506 configuration may, for example, include a default measurement gap 506 and / or a WTRU specific measurement gap 506 (e.g., in response to an assistance information report from the WTRU). The measurement gap 506 may indicate, for example: a set of time and / or frequency resources at which the WTRU may perform GNSS 508 acquisition; and / or an index corresponding to a pre-configured, pre-provisioned, and / or stored measurement gap 506 configuration.

[0172] During the measurement gap 506, the WTRU may acquire GNSS 508. The WTRU may ignore scheduled UL transmissions and / or DL ​​receptions during the measurement gap 506. For example, the WTRU may determine whether to ignore UL transmissions and / or DL ​​receptions based on the type of scheduling associated with the UL transmissions and / or DL ​​receptions (e.g., whether the transmission / reception is dynamic and / or based on a grant of semi-persistent scheduling / configuration), the priority of the UL transmissions and / or DL ​​receptions (e.g., if the transmission is high priority), and / or the type of transmissions (e.g., if the transmission / reception is data and / or control signaling).

[0173] If the WTRU has a valid GNSS 508 position during the measurement gap 506, the WTRU may not perform GNSS 508 acquisition. If the WTRU has a valid GNSS 508 position during the measurement gap 506, the WTRU may use the measurement gap 506 for other purposes (e.g., performing radio link monitoring measurements, performing positioning measurements not related to GNSS 508, entering DRX).

[0174] In certain scenarios, the WTRU may receive a measurement gap 506 configuration for other purposes, such as positioning and / or radio link monitoring (e.g., to perform measurements for radio link monitoring). The WTRU may reuse the measurement gap 506 for GNSS 508 acquisition. For example, if the validity duration of the GNSS 508 has expired, the WTRU may determine whether to reuse the measurement gap 506 configured for other purposes. For example, if the GNSS 508 validity is about to expire (e.g., if the GNSS 508 validity duration remains X seconds), the WTRU may determine whether to reuse the measurement gap 506 configured for other purposes. For example, if the GNSS 508 validity will expire in a future scheduled period (e.g., for UL transmission and / or DL ​​reception), the WTRU may determine whether to reuse the measurement gap 506 configured for other purposes. For example, if the measurement gap 506 is configured sufficient for GNSS 508 acquisition (eg, if the measurement gap 506 contains sufficient time / frequency resources to perform GNSS 508 acquisition), the WTRU may determine whether to reuse the measurement gap 506 configured for other purposes.

[0175] As described herein, the frequency of GNSS 508 acquisition and reporting may be reduced. One or more of the following may apply. GNSS 508 acquisition may be time consuming and power intensive, e.g., depending on the capabilities of the WTRU and / or the required accuracy of the GNSS 508. Power and time consumption may be further increased in IoT NTN scenarios, e.g., where devices may suspend transmission / reception to acquire GNSS 508 and / or where WTRU power consumption should be minimized.

[0176] The WTRU may receive a configuration to inhibit the GNSS 508 from acquiring and / or reporting GNSS 508 information (e.g., a GNSS 508 inhibition configuration). The GNSS 508 inhibition configuration may be, for example, semi-statically configured (e.g., configured via RRC). The GNSS 508 inhibition configuration may be, for example, indicated in system information (e.g., within an NTN specific system information block such as SIB31 / 32). The GNSS 508 inhibition configuration may be, for example, dynamically indicated (e.g., within a DCI indication and / or within a NW request for GNSS 508 position information).

[0177] The GNSS 508 inhibition configuration may include one or more of: inhibition duration; conditions for updating a variable length timer; conditions for overriding inhibition; an indication of WTRU behavior during the inhibition period; and / or a configuration associated with the inhibition method (e.g., timer and duration, and / or thresholds and events for conditional inhibition).

[0178] The WTRU may be configured with a GNSS 508 barring configuration, for example, to prevent excessive GNSS 508 reporting. For example, the GNSS 508 barring configuration may be activated / deactivated and / or configured by the network.

[0179] The WTRU may be configured with an inhibit timer. For example, the inhibit timer may be applied to GNSS 508 acquisition and / or GNSS 508 reporting. In certain scenarios, the WTRU may be configured with multiple inhibit timers (e.g., a timer for GNSS 508 acquisition and a timer for GNSS 508 reporting). When the inhibit timer is running, the WTRU may be prevented from performing GNSS 508 acquisition and / or reporting. The WTRU may start and / or restart the inhibit timer. For example, the WTRU may start and / or restart the inhibit timer after acquiring GNSS 508 location information. For example, the WTRU may start and / or restart the inhibit timer after confirming a GNSS 508 information report after successful reception (e.g., upon receiving a HARQ-ACK for a transmission containing a GNSS 508 report). The WTRU may stop the inhibit timer. For example, the WTRU may stop the inhibit timer when the RRC connection state transitions (e.g., when transitioning to an idle and / or inactive state). For example, the WTRU may stop the inhibit timer when a radio link failure (RLF) occurs. For example, the WTRU may stop the inhibit timer when BFD occurs. For example, the WTRU may stop the inhibit timer when initiating the random access procedure.

[0180] The WTRU may scale triggering events and / or conditions for GNSS 508 reporting (e.g., to increase and / or decrease the frequency of reporting at GNSS 508 as needed). For example, the WTRU may scale the GNSS 508 reporting via the application of a bias and / or offset. For example, if one or more conditions are met (e.g., if the WTRU is considered to be in a low mobility state), the WTRU may apply a bias to extend the GNSS 508 reporting period (e.g., and / or extend the inhibit timer duration). For example, the WTRU may scale the GNSS 508 reporting based on the device type. For example, the WTRU may scale the GNSS 508 reporting based on the mobility state of the WTRU (e.g., whether the WTRU is stationary and / or moving, the WTRU speed and / or velocity if it is moving, etc.). For example, the WTRU may scale the GNSS 508 reporting based on whether measurement relaxation is active. For example, the WTRU may scale the GNSS 508 reporting based on the amount of buffered data (e.g., UP data, CP data, all data, data from a specific bearer, etc.). For example, if the WTRU is scheduled (e.g., for the duration of the packet transmission), the WTRU may scale the GNSS 508 reports. For example, the WTRU may scale the GNSS 508 reports based on the remaining validity time of the last reported GNSS 508 position. For example, the WTRU may scale the GNSS 508 reports based on the current WTRU position (e.g., more frequent reports when the WTRU is between positions 1 and 2, etc.). For example, the WTRU may scale the GNSS 508 reports based on the current time of day (e.g., more frequent reports between absolute times 1 and 2, etc.).

[0181] As described herein, a WTRU may be configured with a GNSS 508 acquisition and / or reporting inhibit timer. The WTRU may start and / or restart the timer, for example, each time it performs a GNSS 508 acquisition and / or reports to the network. While the inhibit timer is running, the WTRU may not perform further GNSS 508 acquisition and / or reporting (e.g., until the inhibit timer expires). A timer may be applied to GNSS 508 acquisition and / or reporting. One or more of the following may apply.

[0182] The WTRU may ignore the configured GNSS 508 reporting trigger condition associated with the inhibit timer, for example, until another event triggers GNSS 508 acquisition and reporting. The WTRU may send the latest GNSS report (e.g., the latest GNSS report), which may be the same as the previously reported GNSS 508 position. The WTRU may indicate that an updated GNSS is not available. For example, the WTRU may also or alternatively indicate when an updated GNSS may be reacquired. The WTRU may delay GNSS 508 reporting until after the inhibit timer expires. After the inhibit timer expires, the WTRU may reacquire GNSS 508 and report. In certain scenarios, the WTRU may be configured with an inhibit timer for reporting but not for acquisition. If the WTRU is configured with an inhibit timer for reporting but not for acquisition, the WTRU may perform GNSS 508 acquisition before the timer expires and / or may delay reporting until after the timer expires.

[0183] The inhibit timer value may be fixed. The inhibit timer may vary (e.g., depending on a number of conditions). For example, a WTRU moving at a higher speed may use a shorter inhibit timer (e.g., to allow for more frequent reporting). The WTRU may detect the speed based on GNSS 508 acquisition, changes in RSRP, and / or changes in cells. The WTRU may use different inhibit timer lengths, for example, based on the type of service and / or bearer. The WTRU may use different timer lengths, for example, based on radio conditions. For example, if the measured RSRP is below a threshold, the WTRU may use a shorter inhibit timer.

[0184] While the inhibit timer is running, the WTRU may be prohibited from sending any SR and / or BSR to request transmission of a GNSS 508 report. Additionally or alternatively, the WTRU may include a GNSS 508 report in an already scheduled transmission if, for example, the received uplink grant provides sufficient resources to include the report and any other pending higher priority data.

[0185] The WTRU may override the inhibition of GNSS 508 reporting, which may be subject to configuration constraints. One or more of the following may apply. The WTRU may override the inhibition of GNSS 508 reporting based on the type of triggering condition that causes GNSS 508 acquisition and reporting. For example, if GNSS 508 acquisition and / or reporting is periodic and / or WTRU event triggered, an explicit request from the network may be the inhibition of GNSS 508 reporting / acquisition. The WTRU may override the inhibition of GNSS 508 reporting based on a NW request (e.g., the NW may override the inhibition based on an explicit flag). The WTRU may implicitly override the inhibition of GNSS508 reporting, for example, if (e.g., any) RRC reconfiguration is received. The WTRU may restart the inhibition timer after changing its state (e.g., RRC state). For example, if the WTRU moves to RRC_INACTIVE and then returns to RRC_CONNECTED, the inhibition timer may be restarted. The WTRU may override the inhibition of GNSS508 reporting after RLF recovery and / or reestablishment. The WTRU may override the inhibition of GNSS 508 reporting after (e.g., any) cell change (e.g., cell reselection and / or handover). The WTRU may override the inhibition of GNSS 508 reporting if one or more (e.g., multiple) trigger conditions have been met (e.g., the number of satisfied trigger conditions for override may be configured).

[0186] The WTRU may receive at least one inhibition condition configured to inhibit GNSS activity via configuration information. The GNSS activity may include at least one of GNSS acquisition, GNSS reporting, or GNSS assistance information (AI) reporting. The WTRU may identify a trigger related to the GNSS activity. The WTRU may determine whether the inhibition condition is activated. The inhibition condition may include a condition based on an inhibition timer, a condition based on a GNSS validity duration, or a condition based on a characteristic of the WTRU. When the inhibition condition is determined to be active, the WTRU may perform the GNSS activity in response to the override or termination of the inhibition condition and based on the inhibition condition being determined to be active.

[0187] Once the coverage condition is met, the WTRU may report (e.g., immediately report), for example, available (e.g., most recently available) GNSS 508 information and / or once updated GNSS 508 information has been acquired (e.g., if the GNSS 508 information is the same as previously reported GNSS 508 information). Additionally or alternatively, the WTRU may acquire (e.g., immediately acquire) GNSS 508 information when the coverage condition is met.

[0188] As described herein, the WTRU may be configured to perform a GNSS 508 acquisition assistance information reporting procedure. One or more of the following may apply.

[0189] The WTRU may receive a configuration for GNSS 508 acquisition assistance information reporting (e.g., GNSS 508 AI reporting). The GNSS 508 acquisition AI reporting configuration may be provided / received via RRC signaling (e.g., via the GNSS 508 acquisition AI IE). The GNSS 508 acquisition AI reporting configuration may be applicable to each MAC entity and / or each serving cell. The GNSS 508 acquisition AI IE may include one or more of the following information fields (e.g., RRC parameters): an enable / disable indication; a condition to trigger a GNSS 508 acquisition AI report (e.g., a reporting threshold); a signaling method to report the GNSS 508 acquisition AI (e.g., via RRC and / or MAC CE); information to be included in the GNSS 508 acquisition AI report (e.g., GNSS 508 validity duration and / or GNSS 508 acquisition time); and / or an inhibit condition to reduce over-reporting (e.g., an inhibit timer duration and / or a scaling offset for reporting triggering).

[0190] Upon receiving the GNSS 508 acquisition AI configuration, the WTRU may monitor one or more of the following: an indication of reporting the GNSS 508 acquisition AI; a reporting trigger condition (e.g., a threshold based on WTRU movement, the remaining time in the GNSS 508 validity duration, a change in the GNSS 508 position compared to the last successfully reported GNSS 508 position information, etc.); and / or the status of the GNSS 508 validity timer.

[0191] The WTRU may trigger the GNSS 508 acquisition AI report. For example, if the WTRU detects that one or more GNSS 508 reporting trigger conditions have been met, the WTRU may trigger the GNSS 508 acquisition AI report. For example, if the WTRU receives an indication to report the GNSS 508 acquisition AI, the WTRU may trigger the GNSS 508 acquisition AI report. For example, the WTRU may trigger the GNSS 508 acquisition AI report upon expiration of a GNSS 508 validity timer. The WTRU may report the GNSS 508 assistance information via, for example, a MAC CE and / or via RRC signaling (e.g., via measurement reports, WTRU information responses, and / or WTRU capability signaling).

[0192] The WTRU may start and / or restart the GNSS 508 validity duration timer upon transmitting the GNSS 508. Additionally or alternatively, the WTRU may start and / or restart the GNSS 508 validity duration timer upon successful acquisition of the GNSS 508 information and / or upon receipt of HARQ feedback (e.g., ACK) for a transmission carrying the GNSS 508 acquisition AI and / or the GNSS 508 information.

[0193] Figure 6 An example 600 associated with a GNSS acquisition AI reporting process is shown. A WTRU may receive a configuration 602 for GNSS AI reporting. The WTRU may be an Internet of Things (IoT) device and / or a Reduced Capability (RedCap) device. Configuration information for GNSS AI reporting may include one or more enable / disable flags, reporting thresholds, and / or bias conditions. The WTRU may receive configuration information for reporting Global Navigation Satellite System (GNSS) Assistance Information (AI). The configuration information may include a reporting trigger threshold, which may be at least one of a distance threshold or a time offset threshold.

[0194] The WTRU may apply a scaling bias 604 (e.g., based on WTRU speed, WTRU velocity, WTRU acceleration, mobility state estimate, and / or satellite characteristics) and / or consider additional inhibition mechanisms (e.g., if a GNSS acquisition assistance information inhibit timer is running). For example, the WTRU may monitor a trigger condition 606. The WTRU may apply a scaling bias and / or consider additional inhibition techniques when evaluating a report trigger condition and / or in response to a report trigger condition being met or not met. The WTRU may modify the distance threshold or the time offset threshold based on one or more of the WTRU speed, the WTRU's mobility state, or at least one characteristic of a satellite of a non-terrestrial network. The WTRU may continue to monitor the trigger condition 606 when the trigger is not met.

[0195] At 608, when a trigger is met, the WTRU may determine whether an inhibit mechanism is active (e.g., based on an inhibit timer) that inhibits the WTRU from acquiring and / or reporting GNSS. The trigger being met may include the WTRU determining that a report trigger threshold is exceeded. The report trigger threshold may be exceeded when the WTRU is scheduled to send or receive a transmission at a time that is less than a time offset threshold from the expiration of the GNSS validity duration. The report trigger threshold may be exceeded when the WTRU's current position exceeds a previously reported WTRU position by a configured threshold. One or more of the following may apply.

[0196] The WTRU may receive (e.g., via configuration) a prohibition condition (e.g., to prevent GNSS reporting and / or acquisition). The GNSS report prohibition configuration may be received, for example, via RRC signaling (e.g., via a GNSS prohibition IE) and may be applied for each MAC entity and / or each serving cell. For example, the GNSS prohibition IE may include one or more of: an indication of enabling / disabling prohibition; a prohibition timer duration; and / or a scaling factor that may be applied to the GNSS report triggering condition (e.g., based on the WTRU speed and / or mobility state estimate). The WTRU may receive, via configuration information, at least one prohibition condition configured to prohibit GNSS activity. The GNSS activity may include at least one of GNSS acquisition, GNSS reporting, or GNSS assistance information (AI) reporting. The WTRU may identify a trigger related to the GNSS activity. The WTRU may determine whether the prohibition condition is activated. The prohibition condition may include a condition based on a prohibition timer, a condition based on a GNSS validity duration, or a condition based on a characteristic of the WTRU. When the prohibition condition is determined to be active, the WTRU may perform the GNSS activity in response to an override or termination of the prohibition condition and based on the prohibition condition being determined to be active.

[0197] At 610, the WTRU may report the GNSS AI if allowed. The WTRU may report the GNSS AI using MAC CE, RRC, measurement report, and / or capability signaling. The GNSS AI may include one or more of a GNSS validity duration, a GNSS acquisition time, a measurement gap configuration, and / or a configuration index. The GNSS validity duration may include an indication of a duration associated with the validity of the GNSS acquisition, an indication of a duration associated with the expiration of the GNSS acquisition, and / or a WTRU location associated with the GNSS acquisition. The GNSS acquisition time may include the time to acquire the GNSS location. In some cases, the WTRU may receive a measurement gap configuration based on a report trigger threshold being exceeded. In some cases, the measurement gap configuration may be associated with a length of time to suspend the WTRU's reception and transmission.

[0198] The WTRU may perform GNSS activities when an inhibit condition is determined to be inactive. The characteristics of the WTRU may include at least one of a GNSS acquisition AI, a change in position, or a change in speed of the WTRU. The WTRU may determine the override or termination of an inhibit condition in response to: one or more triggering events for GNSS reporting or reporting occurring during an inhibit period, where the inhibit period exceeds a threshold; receiving an explicit override request; or expiration of a GNSS validity timer during an inhibit condition. When an inhibit condition is determined to be active, the WTRU may monitor one or more triggering conditions. The inhibit condition may be based on one or more of: GNSS validity duration, WTRU position, or WTRU speed.

[0199] In the execution of GNSS activity, the WTRU may report via a medium access control (MAC) information element (IE) when the GNSS AI includes a GNSS validity duration, and report via a radio resource control (RRC) based on the RRC state when the GNSS AI includes a positioning fix duration. When the GNSS reporting condition is met and the inhibit condition is active, the WTRU may perform one or more of the following: delay the GNSS activity until the inhibit condition is not active or expires, indicate that the inhibit condition is active, or indicate when the GNSS activity is enabled. The WTRU may stop sending and receiving data signals to receive GNSS information. The WTRU may be an Internet of Things (IOT) device. The WTRU may be a reduced capability (RedCap) device.

[0200] The WTRU may report GNSS AI using different types of signaling based on reporting GNSS validity duration or GNSS acquisition time. For example, the WTRU may report GNSS validity duration using signal type A (e.g., MAC CE) and GNSS acquisition time using signal type B (e.g., RRC). The WTRU may send / issue GNSS AI position reports to the gNB using medium access control (MAC) information elements (IEs). In some cases, the GNSS AI may be included in the measurement report. In some cases, the WTRU may report GNSS AI using WTRU capability signaling.

[0201] The WTRU may start and / or restart the GNSS report inhibit timer when sending the GNSS report. During the inhibit timer, the WTRU may be restricted and / or prevented from reporting GNSS position information. Additionally or alternatively, the WTRU may start and / or restart the GNSS inhibit timer upon successful acquisition of GNSS information and / or upon receipt of HARQ feedback (e.g., ACK) for a transmission carrying GNSS information and / or GNSS report.

[0202] In certain scenarios, GNSS reporting may be triggered when one or more inhibition conditions are active / valid. If GNSS reporting has been triggered and one or more inhibition conditions are active / valid, the WTRU may delay reporting until the inhibition conditions (e.g., one or more and / or all inhibition conditions) are not active and / or expire. If GNSS reporting has been triggered and one or more inhibition conditions are active / valid, the WTRU may indicate that the one or more inhibition conditions are active (e.g., via a flag). If GNSS reporting has been triggered and one or more inhibition conditions are active / valid, the WTRU may provide (e.g., send) an indication of when GNSS reporting and / or GNSS AI reporting will be (or will be again) enabled.

[0203] The WTRU may override the inhibit conditions for GNSS reporting and / or GNSS acquisition AI reporting, which may be further affected by additional conditions. For example, the additional conditions may include: the number of triggering events during the inhibit time exceeds a threshold; network (NW) request; and / or when the GNSS validity period expires.

[0204] Figure 7 An example 702 associated with inhibition of GNSS (eg, and / or GNSS acquisition assistance information) reporting is shown.

[0205] The prohibition condition may also or alternatively be applied to GNSS acquisition AI reports. Separate configurations and / or indications may be provided for GNSS reports and GNSS AI reports. Separate prohibition timers may be maintained for GNSS reports and GNSS assistance information reports.

[0206] The gNB may send GNSS reporting configuration information to the WTRU, including a prohibition condition 704. The WTRU may be an Internet of Things (IoT) device. The WTRU may be a reduced capability (RedCap) device. The prohibition condition may include a condition based on a prohibition timer, a condition based on a GNSS validity duration, or a condition based on a characteristic of the WTRU. The WTRU may receive configuration information for reporting global navigation satellite system (GNSS) assistance information (AI). The configuration information may include a report trigger threshold, which is at least one of a distance threshold or a time offset threshold. At 706, the WTRU may determine that a report trigger is met (e.g., exceeds the report trigger threshold). The report trigger threshold may be exceeded when the WTRU is scheduled to send or receive a transmission at a time less than the time offset threshold from the expiration of the GNSS validity duration. The report trigger threshold may be exceeded when the current position of the WTRU exceeds the previously reported WTRU position by a configured threshold.

[0207] After the GNSS reporting trigger is met 706, the WTRU may start GNSS acquisition 708. The WTRU may suspend user plane and control plane reception and transmission to receive GNSS information. The WTRU may stop sending and receiving data signals to receive GNSS information. The WTRU may then report 710 GNSS AI to the gNB. During the GNSS inhibit time 716, the network (e.g., gNB) may send a request for GNSS AI 712 (e.g., gNB sends and WTRU receives). At 714, the WTRU may send one or more messages to the gNB indicating that GNSS AI acquisition and / or reporting is inhibited and when GNSS AI acquisition and / or reporting will become available. At 718, the WTRU may perform GNSS acquisition.

[0208] At 720, the WTRU may report (e.g., issue, send, etc.) the GNSS AI to the gNB. The WTRU may report the GNSS AI using MACCE, RRC, measurement report, and / or capability signaling. The GNSS AI may include one or more of a GNSS validity duration, a GNSS acquisition time, a measurement gap configuration, and / or a configuration index. The GNSS validity duration may include an indication of a duration associated with the validity of the GNSS acquisition, an indication of a duration associated with the expiration of the GNSS acquisition, and / or a WTRU location associated with the GNSS acquisition. The GNSS acquisition time may include the time at which the GNSS location was acquired. The WTRU may determine the coverage or termination of the inhibition condition in response to: one or more triggering events for GNSS reporting or reporting occurring during an inhibition period, wherein the inhibition period exceeds a threshold; receiving an explicit coverage request; or expiration of the GNSS validity timer during an inhibition condition.

[0209] In the performance of GNSS activity, the WTRU may report via a Medium Access Control (MAC) Information Element (IE) when the GNSS AI includes a GNSS validity duration, and report via a Radio Resource Control (RRC) based on the RRC state when the GNSS AI includes a position fix duration. When the GNSS reporting condition is met and the inhibit condition is active, the WTRU may perform one or more of the following: delay the GNSS activity until the inhibit condition is not active or expires, indicate that the inhibit condition is active, or indicate when the GNSS activity is enabled.

[0210] The WTRU may use different types of signaling to report GNSS AI based on reporting GNSS validity duration or GNSS acquisition time. For example, the WTRU may use signal type A (e.g., MAC CE) to report GNSS validity duration and signal type B to report GNSS acquisition time (e.g., RRC based on RRC state), or vice versa, or a combination of two or more signal types.

[0211] The WTRU may receive at least one inhibition condition configured to inhibit GNSS activity via configuration information. The GNSS activity may include at least one of GNSS acquisition, GNSS reporting, or GNSS assistance information (AI) reporting. The WTRU may identify a trigger related to the GNSS activity. The WTRU may determine whether the inhibition condition is activated. The inhibition condition may include a condition based on an inhibition timer, a condition based on a GNSS validity duration, or a condition based on a characteristic of the WTRU. When the inhibition condition is determined to be active, the WTRU may perform the GNSS activity in response to the override or termination of the inhibition condition and based on the inhibition condition being determined to be active.

[0212] Figure 8 Another example associated with a reporting process is shown. At 602, the WTRU may receive a configuration for GNSS AI reporting. Figure 6 In addition to the configuration information, Figure 8 The configuration information in may also include reporting thresholds related to distance and time (e.g., distance X, time offset T) and / or inhibition mechanisms. At 604, the WTRU may apply one or more biases to the triggering of the WTRU. At 606, the WTRU may monitor the triggering conditions. The WTRU may monitor the reporting trigger threshold to determine whether the reporting trigger threshold has been exceeded. The triggering conditions may include whether the WTRU has moved a configured distance X from the last reported location and / or whether the WTRU is scheduled (sending or receiving) within a time offset T from the expiration of the GNSS validity duration. At 608, it may be determined whether one or more inhibition mechanisms are active. The inhibition mechanisms may include one or more inhibition timers and / or coverage conditions (e.g., explicit network request, expiration of validity duration).

[0213] At 810, the WTRU may determine what the content of the GNSS AI is if GNSS reporting and / or acquisition is allowed and / or if the prohibition condition is overridden. At 812, if the GNSS AI includes a validity duration, the WTRU may send a GNSS AI report via the MAC CE. At 814, if the GNSS AI includes a position fix duration, the WTRU may send a GNSS AI report via the RRC. The RRC signaling may include one or more measurement reports, capability signaling, setup / restore messages.

Claims

1. A wireless transmit / receive unit WTRU, comprising: A processor, the processor being configured to: Receiving configuration information for reporting global navigation satellite system GNSS assistance information AI, wherein the configuration information includes a report trigger threshold, and the report trigger threshold is at least one of a distance threshold or a time offset threshold; determining that the report trigger threshold is exceeded; as well as Reporting GNSS AI, wherein the GNSS AI includes at least one of a GNSS validity duration or a GNSS acquisition time, wherein the GNSS validity duration includes an indication of a duration associated with the validity of the GNSS acquisition, an indication of a duration associated with the expiration of the GNSS acquisition, or a WTRU position associated with the GNSS acquisition, and wherein the GNSS acquisition time includes a time used to acquire a GNSS position.

2. The WTRU of claim 1 , wherein the GNSS AI comprises at least one of a measurement gap configuration or a configuration index.

3. The WTRU of claim 1 , wherein the processor is further configured to modify the distance threshold or the time offset threshold based on at least one of a speed of the WTRU, a mobility state of the WTRU, or at least one characteristic of a satellite of a non-terrestrial network.

4. The WTRU of claim 1 , wherein: When reporting the GNSS AI, the processor is further configured to use different types of signaling based on reporting the GNSS validity duration or the GNSS acquisition time.

5. The WTRU of claim 1 , wherein the reporting trigger threshold is exceeded when the WTRU is scheduled to send or receive a transmission at a time that is less than the time offset threshold from expiration of the GNSS validity duration.

6. The WTRU of claim 1, wherein the reporting trigger threshold is exceeded when a current location of the WTRU exceeds a previously reported WTRU location by a configured threshold.

7. The WTRU of claim 1 , wherein the processor is further configured to suspend user plane and control plane reception and transmission to receive GNSS information.

8. The WTRU of claim 1, wherein the WTRU is an Internet of Things (IoT) device.

9. The WTRU of claim 1, wherein the WTRU is a reduced capability (RedCap) device.

10. The WTRU of claim 1, wherein the processor is further configured to send a GNSS AI location report using a medium access control (MAC) information element (IE).

11. The WTRU of claim 1 , wherein the reporting of the GNSS AI is included in a measurement report.

12. The WTRU of claim 1 , wherein the reporting of the GNSS AI is accomplished using WTRU capability signaling.

13. The WTRU of claim 1 , wherein the processor is further configured to receive the measurement gap configuration based on exceeding the reporting trigger threshold, wherein the measurement gap configuration is associated with a length of time for suspending WTRU reception and transmission.

14. The WTRU of claim 1, wherein the processor is further configured to monitor the reporting trigger threshold to determine whether the reporting trigger threshold has been exceeded.

15. The WTRU of claim 1 , wherein the processor is further configured to report the GNSS AI via a medium access control (MAC) information element (IE) when the GNSS AI includes the GNSS validity duration, or to report the GNSS AI via a radio resource control (RRC) state based on an RRC state when the GNSS AI includes the GNSS acquisition time.

16. A method implemented by a wireless transmit receive unit WTRU, the method comprising: Receiving configuration information for reporting global navigation satellite system GNSS assistance information AI, wherein the configuration information includes a report trigger threshold, and the report trigger threshold is at least one of a distance threshold or a time offset threshold; determining that the report trigger threshold is exceeded; and Reporting GNSS AI, wherein the GNSS AI includes at least one of a GNSS validity duration or a GNSS acquisition time, wherein the GNSS validity duration includes an indication of a duration associated with the validity of the GNSS acquisition, an indication of a duration associated with the expiration of the GNSS acquisition, or a WTRU position associated with the GNSS acquisition, and wherein the GNSS acquisition time includes a time used to acquire a GNSS position.

17. The method according to claim 16, wherein: The GNSS AI includes at least one of a measurement gap configuration or a configuration index.

18. The method according to claim 16, further comprising: The distance threshold or the time offset threshold is modified based on at least one of a speed of the WTRU, a mobility state of the WTRU, or at least one characteristic of a satellite of a non-terrestrial network.

19. The method according to claim 16, wherein: Reporting the GNSS AI is accomplished using different types of signaling based on reporting the GNSS validity duration or the GNSS acquisition time.

20. The method of claim 16, wherein the reporting trigger threshold is exceeded when the WTRU is scheduled to send or receive a transmission at a time that is less than the time offset threshold from expiration of the GNSS validity duration.

21. The method of claim 16, wherein the reporting trigger threshold is exceeded when a current location of the WTRU exceeds a previously reported WTRU location by a configured threshold.

22. The method of claim 16 wherein the WTRU suspends user plane and control plane reception and transmission to receive GNSS information.

23. The method of claim 16, wherein the WTRU is an Internet of Things (IoT) device.

24. The method of claim 16, wherein the WTRU is a reduced capability (RedCap) device.

25. The method of claim 16, wherein: GNSS AI position reports are sent using the Medium Access Control (MAC) Information Element (IE).

26. The method of claim 16, wherein: Reporting The GNSS AI is included in the measurement report.

27. The method of claim 16, wherein reporting the GNSS AI is accomplished using WTRU capability signaling.

28. The method of claim 16, further comprising receiving the measurement gap configuration based on the reporting trigger threshold being exceeded, wherein the measurement gap configuration is associated with a length of time for which WTRU reception and transmission are suspended.

29. The method of claim 16, further comprising: The reporting trigger threshold is monitored to determine whether the reporting trigger threshold has been exceeded.

30. The method of claim 16, wherein: When the GNSS AI includes the GNSS validity duration, the GNSS AI is reported via a medium access control (MAC) information element (IE), and wherein, when the GNSS AI includes the GNSS acquisition time, the GNSS AI is reported via a radio resource control (RRC) based on an RRC state.

Images