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] This application is a divisional of application with the application date of September 22, 2023, the application number of 202380069333.7, and the invention title of “Global Navigation Satellite System (GNSS) Reporting for Reduced Capability Devices”. This application claims the benefit of U.S. Provisional Application No. 63 / 410,321 filed September 27, 2022. The entire contents of which are hereby incorporated by reference in their entirety.

[0002] Cross Reference to Related Applications

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

[0004] Global Navigation Satellite Systems (GNSS) can include global, regional, and augmentation satellite systems, such as GPS, Galileo, and GLONASS systems. In certain scenarios, GNSS can be designed to interwork with a network. If GNSS is designed to interwork with a network, the network can assist a WTRU GNSS receiver to improve performance. SUMMARY

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

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

[0007] The WTRU can be 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.

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

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

[0010] The reporting trigger threshold can be exceeded when the current location of the WTRU exceeds the previously reported WTRU location by a configured threshold.

[0011] The WTRU can suspend user plane and control plane traffic (e.g., reception and transmission) to receive GNSS information.

[0012] The WTRU can be an Internet of Things (IOT) device.

[0013] The WTRU can be a Reduced Capability (RedCap) device.

[0014] The GNSS AI location report can be sent using a medium access control (MAC) information element (IE).

[0015] Reporting GNSS AI can be included in a measurement report.

[0016] Reporting GNSS AI can be accomplished using WTRU capability signaling.

[0017] The WTRU can 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 the WTRU to suspend reception and transmission.

[0018] The WTRU can be further configured to monitor a reporting trigger threshold to determine whether the reporting trigger threshold has been exceeded.

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

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

[0021] The WTRU can perform GNSS activity when the barring condition is determined to be inactive. Characteristics of the WTRU can include at least one of GNSS acquisition AI, change in location, or change in speed of the WTRU. The WTRU can determine coverage or termination of the barring condition in response to: one or more triggering events for GNSS reporting or occurrence of reporting during a barring period, where the barring period exceeds a threshold; receiving an explicit coverage request; or a GNSS validity timer expiring during the barring condition.

[0022] The WTRU can monitor one or more triggering conditions when the barring condition is determined to be active. The barring condition can be based on one or more of: GNSS validity duration, WTRU location, or WTRU speed.

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

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

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

[0026] A wireless transmit receive unit (WTRU) can be configured to perform global navigation satellite system assistance information (GNSSAI) reporting. The WTRU can receive a GNSS configuration. The GNSS configuration can include one or more triggering conditions associated with GNSSAI reporting. The GNSS configuration can further include a bias condition associated with each of the one or more triggering conditions. The WTRU can apply a bias to each of the one or more triggering conditions. The bias can be applied, for example, 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 can detect a triggering condition of the one or more triggering conditions. The WTRU can transmit a GNSS AI report based on the detection of the triggering condition. The GNSS AI report can be transmitted, for example, using a medium access control (MAC) information element. The GNSS AI report can be included, for example, in a measurement report. The GNSS AI report can be transmitted, for example, using WTRU capability signaling. BRIEF DESCRIPTION OF DRAWINGS

[0027] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments can be implemented;

[0028] FIG. 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system FIG. 1A illustrated in FIG. 1;

[0029] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system FIG. 1A illustrated in FIG. 1;

[0030] FIG. 1D is a system diagram illustrating another example RAN and another example CN that can be used within the communications system FIG. 1A illustrated in FIG. 1;

[0031] FIG. 2 illustrates an example associated with non-terrestrial networks (NTNs);

[0032] FIG. 3 illustrates an example associated with a protocol stack;

[0033] FIG. 4A and 4B illustrates an example associated with GNSS acquisition;

[0034] FIG. 5 illustrates an example associated with measurement gap configuration;

[0035] FIG. 6 An example associated with a reporting procedure is shown;

[0036] FIG. 7 An example associated with a GNSS report is shown; and

[0037] FIG. 8 Another example associated with a reporting procedure is shown. DETAILED DESCRIPTION

[0038] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments can be implemented. The communications system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 can employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZTUW DTS-s OFDM), unique-word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0039] As FIG. 1AAs shown, the communication system 100 can include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which can be referred to as a “station” and / or a “STA”) can be configured to transmit and / or receive wireless signals and can include a user equipment (WTRU), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, 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, a medical device and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or an automated processing chain environments), consumer electronics, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d can be interchangeably referred to as a WTRU.

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

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

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

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

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

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

[0046] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement multiple radio access technologies. For example, the base station 114a and WTRUs 102a, 102b, 102c can implement LTE wireless access and NR wireless access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c can be characterized by multiple types of radio access technologies and / or transmitted over multiple types of base stations (e.g., an eNB and a gNB).

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

[0048] As an example, FIG. 1AThe base station 114b in FIG. 1 A can be a wireless router, Home Node B, Home eNode B, or access point, for example, and can utilize any suitable RAT for facilitating wireless connectivity access to the Internet, such as IEEE 802.11. In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d can implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. As shown in FIG. 1 A, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114b can not be required to access the Internet 110 via the CN 106 / 115. FIG. 1A

[0049] The RAN 104 / 113 can be in communication with the CN 106 / 115, which can 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 can have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 can provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 can be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which can be utilizing a NR radio technology, the CN 106 / 115 can also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology. FIG. 1A

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

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

[0052] FIG. 1B This is a system diagram illustrating example WTRU 102. (See diagram for example.) FIG. 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that, while remaining consistent with the embodiments, WTRU 102 may include any sub-combination of the foregoing elements.

[0053] The processor 118 can 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 in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, which can be coupled to the transmit / receive element 122. While FIG. 1B The processor 118 and the transceiver 120 are depicted as separate components, but can be integrated together in an electronic package or chip.

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

[0055] Although the transmit / receive element 122 is depicted in the WTRU 102 FIG. 1B In one embodiment, the WTRU 102 can 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 can be configured to modulate information to be transmitted by the transmit / receive element 122 and to demodulate information received by the transmit / receive element 122. As noted above, the WTRU 102 can have multi-mode capabilities. Thus, the transceiver 120 can include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

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

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

[0059] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. As a supplement or replacement to the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that, while remaining consistent with the embodiments, the WTRU 102 may acquire location information using any suitable location determination method.

[0060] The processor 118 can also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, etc. The peripheral devices 138 can include one or more sensors, which can be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, a compass 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 can include a full duplex radio for which transmission and reception of some or all signals associated with a particular subframe, based on a determination made by the WTRU 102, can be concurrent and / or simultaneous. The full duplex radio can include an interference management unit 139 to reduce and or substantially eliminate self-interference and / or cross-interference due to concurrent transmission and reception. In an embodiment, the WTRU 102 can include a half duplex radio for which transmission and reception of some or all signals associated with a particular subframe is time divided.

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

[0063] The RAN 104 can include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 can include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c can 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 can implement MIMO technology. Thus, the eNode-B 160a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0064] Each of eNode-Bs 160a, 160b, 160c can be associated with a particular cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown, the eNode-Bs 160a, 160b, 160c can communicate with one another over an X2 interface. FIG. 1C

[0065] FIG. 1C The CN 106 can 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 are depicted as part of the CN 106, it will be appreciated that any of these elements can be owned and / or operated by an entity other than the CN operator.

[0066] The MME 162 can be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and can serve as a control node. For example, the MME 162 can 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 can 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 can be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 can generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 can perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0068] The SGW 164 can be connected to the PGW 166, which can 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 can facilitate communications with other networks. For example, the CN 106 can 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 landline communications devices. For example, the CN 106 can include, or can 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 can provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which can include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0070] Although WTRUs are often described herein as being wireless terminals, it is contemplated that in certain representative embodiments such terminals can use, e.g., temporarily or permanently, a wired interface to a communication network. FIGS. 1A-1D

[0071] In representative embodiments, the other network 112 can be a WLAN.

[0072] A WLAN in Infrastructure Basic Service Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can have an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that is carried by the DS can be transmitted from the AP, and traffic from STAs can be transmitted to the AP to be carried by the DS. Traffic between STAs can be transmitted using the AP as a broker (e.g., relay). Business

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

[0074] High Throughput (HT) STAs can use a 40 MHz wide channel for communication, e.g., by combining a 20 MHz wide primary channel with an adjacent or nonadjacent 20 MHz wide secondary channel.

[0075] Very High Throughput (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. A 40 MHz and / or 80 MHz channel can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, data, after channel coding, can be parsed into two streams by a segment parser. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed on each stream, respectively. The streams can be mapped on to the two 80 MHz channels, and the data can be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Medium Access Control (MAC).

[0076] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers in 802.11af and 802.11ah are reduced relative to those used in 802.11η and 802.1 lac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah can support meter type control / machine type communications, such as MTC devices in a macro coverage area. MTC devices can have certain capabilities, such as including limited capabilities that support (e.g., only support) certain and / or limited bandwidths. MTC devices can include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0077] WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11η, 802.1 lac, 802.11af, and 802.11ah) include a channel that can be designated as a primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by STAs from all STAs operating in the BSS that support the minimum bandwidth operating mode. In an example of 802.11ah, for STAs (e.g., MTC type devices) that support (e.g., only support) 1 MHz mode, the primary channel can be 1 MHz wide, even though other STAs in the AP and BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sense and / or network allocation vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, e.g., due to a STA (that only supports 1 MHz operating mode) transmitting to the AP, then the entire available frequency band can be considered busy, even though most of the frequency band remains idle and can be available.

[0078] In the United States, the available frequency band that 802.11ah can use is 902 MHz to 928 MHz. In 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. The total bandwidth available to 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0079] FIG. 1Dis a system illustration of a RAN 113 and a CN 115 in accordance with the embodiments. As described above, the RAN 113 can employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 can also be in communication with the CN 115.

[0080] The RAN 113 can include gNBs 180a, 180b, 180c, although it will be appreciated that the RAN 113 can include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c can 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 can implement MIMO technology. For example, gNBs 180a, 108b can utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, can 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 can implement carrier aggregation technology. For example, the gNB 180a can transmit multiple component carriers (not shown) to the WTRU 102a. A subset of these component carriers can be on unlicensed spectrum while the remaining component carriers can be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c can implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

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

[0082] The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, the WTRUs 102a, 102b, 102c can communicate with the gNBs 180a, 180b, 180c without also accessing other RANs, such as eNode-Bs 160a, 160b, 160c. In the standalone configuration, the WTRUs 102a, 102b, 102c can utilize one or more of the gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, the WTRUs 102a, 102b, 102c can utilize signal transmission and reception over an unlicensed frequency band. In the non-standalone configuration, the WTRUs 102a, 102b, 102c can communicate / connected with the gNBs 180a, 180b, 180c, while also communicating / connected with another RAN, such as eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c can implement DC principles to substantially simultaneously communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c. In the non-standalone configuration, the eNode-Bs 160a, 160b, 160c can serve as the WTRUs' 102a, 102b, 102c mobility anchor point, and the gNBs 180a, 180b, 180c can provide additional coverage and / or throughput to the WTRUs 102a, 102b, 102c.

[0083] Each of the gNBs 180a, 180b, 180c can be associated with a particular cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and / or the like. As shown, the gNBs 180a, 180b, 180c can communicate with one another over an Xn interface. FIG. 1D As shown, the gNBs 180a, 180b, 180c can be in communication with the AN 102a, 102b, 102c over one or more interfaces. Each of the gNBs 180a, 180b, 180c can also be in direct or indirect communication with other gNBs, such as the gNBs 180a, 180b, 180c. For example, the gNBs 180a, 180b, 180c can communicate with one another over an Xn interface.

[0084] FIG. 1DThe illustrated CN 115 can include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements can be owned and / or operated by an entity other than the CN operator.

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

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

[0087] The UPF 184a, 184b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which can 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 can 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, and the like.

[0088] The CN 115 can facilitate communications with other networks. For example, the CN 115 can include, or can 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. Further, the CN 115 can provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which can include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c can be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0089] In view of the FIGS. 1A-1D and corresponding description regarding FIGS. 1A-1D 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 device described herein can be performed by one or more emulation devices (not shown). An emulation device can be one or more devices configured to emulate one or more or all of the functions described herein. For example, emulation devices can be used to test other devices and / or to simulate network and / or WTRU functionality.

[0090] A simulation device can be designed to functionally test one or more other devices in laboratory, field, and / or operational environments. For example, one or more simulation devices can perform one or more or all functions as other devices while being fully or partially implemented and / or deployed in a wired and / or wireless communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed in a wired and / or wireless communication network. Simulation devices can be directly coupled to other devices, and / or can use over-the-air, wireless communication to perform testing.

[0091] One or more simulation devices can 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, simulation devices can be used in testing laboratories and / or test scenarios in non-deployed (e.g., testing) wired and / or wireless communication networks to implement testing of one or more components. The one or more simulation devices can be test equipment. Simulation devices can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas).

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

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

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

[0095] Table 1

[0096]

[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 are impractical, e.g., 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] NTNs can include airborne and / or space-borne platforms that transfer signals from a land-based gNB to a WTRU via a gateway (GW) and vice versa. NTNs can support, for example, power class 3 WTRUs with omnidirectional antennas and linear polarization and / or very small aperture terminal (VSAT) terminals with directional antennas and circular polarization. Additionally or alternatively, NTNs can support LTE-based narrowband IoT (NB-IoT) and eMTC type devices.

[0099] Air and / or space-born platforms can be categorized according to orbit. Low Earth Orbit (LEO) satellites can include satellites associated with an altitude range of 300-1500 km. Geostationary Earth Orbit (GEO) satellites can include satellites associated with a range of altitudes of 35-786 km. Medium Earth Orbit (MEO) satellites can include satellites associated with an altitude range of 7000-25000 km. High Altitude Platform Stations (HAPS) can include stations associated with an altitude of 8-50 km. Satellite platforms can be further categorized by payload (e.g., “transparent” and / or “regenerative”). For example, a transparent satellite payload can implement frequency conversion and RF amplification in both uplink and downlink (e.g., with multiple transparent satellites that can be connected to a land-based gNB). For example, a regenerative satellite payload can implement a gNB and / or gNB Distributed Unit (DU) on the satellite. A regenerative payload can also or instead perform digital processing on signals, including, for example, demodulation, decoding, re-encoding, re-modulation, and / or filtering.

[0100] FIG. 2 An example 200 associated with interfaces in an NTN is shown. One or more radio interfaces can be defined in an 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 respective satellites 212, 214. Service links 206 may, for example, include radio links between a satellite and a WTRU 216. ISLs 208 can include transmission links between satellites. For example, ISLs may, for example, be supported (e.g., can be supported only) by a regenerative payload and / or can be a 3GPP radio and / or a proprietary optical interface. Example 200 associated with interfaces in an NTN can also include a central unit (CU).

[0101] Depending on satellite payload configuration, different interfaces (e.g., 3GPP interfaces) can be used for radio links (e.g., each radio link). In a transparent payload, for example, a Uu interface (e.g., NR-Uu radio interface) can be used for both service links and feeder links. Uu can refer to a Universal Mobile Telecommunications System (UMTS) air interface, which is a radio interface between a UMTS Terrestrial Radio Access Network (UTRAN) and a WTRU 216 utilizing Code Division Multiple Access (CDMA). For a regenerative payload, for example, a Uu interface (e.g., NR-Uu radio interface) can be used on service links, and a satellite radio interface (SRI) can be used for feeder links.

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

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

[0104] Due to the height of the NTN platform and the beam diameter, the round trip time (RTT) and maximum differential delay can be larger than for terrestrial systems. In a certain transparent NTN deployment, the RTT can range from 25.77 ms (e.g., LEO @ 600 km altitude) to 541.46 ms (e.g., GEO), and the maximum differential delay can range from 3.12 ms to 10.3 ms. The RTT for a regenerative payload can be approximately half of the RTT for a transparent payload (e.g., because a transparent configuration can include both a service link and a feeder link). The RTT for a regenerative payload can consider (e.g., can only consider) the service link. A WTRU can perform timing pre-compensation, e.g., prior to initial access, which can minimize the impact on existing NR systems (e.g., to avoid preamble ambiguity and / or to properly time reception windows).

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

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

[0107] Non-terrestrial networks can be associated with large moving cells and reduced effectiveness of measurement-based procedures, e.g., due to reduced signal strength variation between cell center and cell edge. In certain scenarios, the location of the WTRU can 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 can not be supported in non-terrestrial networks, which can require NTN devices to maintain GNSS information (e.g., accurate GNSS information). NTN-capable devices can also have GNSS capability.

[0108] Acquisition of GNSS information can be a time and power-intensive procedure, which can cause issues for Internet of Things (IoT) and reduced capability (RedCap) devices (e.g., where reduced power consumption can be implemented). A subset of IoT and / or RedCap devices (e.g., NB-IoT) can not be capable of supporting GNSS acquisition and data transmission / reception.

[0109] FIG. 4A and FIG. 4BExamples associated with GNSS acquisition are shown. For example, as shown in FIG. 4A IoT traffic can be (e.g., limited to) short and sporadic traffic 406a, b, c, which can not impact GNSS acquisition 407 in certain NTN deployments. The WTRU can suspend user plane and control plane reception and transmission to receive GNSS information during GNSS acquisition 407. Techniques to reduce GNSS acquisition time (e.g., positioning fix duration) can be implemented (e.g., because scheduled transmission / reception is unlikely to overlap with GNSS acquisition).

[0110] As shown in FIG. 4B IoT traffic can not be (e.g., limited to) short and sporadic traffic 408a-f, which can increase the probability of collision between throughput and GNSS acquisition window and UL transmission / DL reception in certain NTN deployments. The WTRU can tune away to acquire GNSS packets that cannot be received. Tuning away can include retuning a receiver chain (e.g., antenna) of the WTRU to receive GNSS packets that the WTRU was unable to receive while previously tuned. In some cases, a first receiver (e.g., LTE) and a second receiver (e.g., GNSS) can 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 can not be capable of operating simultaneously. If the WTRU is operating the LTE receiver to receive data, the WTRU can not be able to receive GNSS data, and vice versa. The switching between operating the receivers can be referred to herein as “tuning away.” In FIG. 4B , the WTRU can tune away from the first receiver to the GNSS receiver to receive and / or transmit GNSS data (e.g., switch from the LTE receiver to the GNSS receiver to receive GNSS data). In other cases, the WTRU can be capable of operating the first receiver and the second receiver simultaneously without tuning away.

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

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

[0113] One or more techniques to report WTRU assistance information and / or support configuration of measurement gaps for GNSS acquisition can be implemented. One or more techniques to reduce excessive GNSS acquisition and reporting (e.g., for power-limited devices) can be implemented.

[0114] As disclosed herein, the term “GNSS” can be used to refer to positioning / location of a WTRU, which can be used for timing advance calculation, for example, in non-terrestrial networks. However, the techniques described herein can 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” can be used interchangeably herein and can be used to describe assistance information reported by a WTRU (e.g., to assist GNSS acquisition). The terms “IoT,” “NB-IoT,” and “eMTC” devices can be used to describe lower capability devices (e.g., lower capability devices supported by LTE). However, the techniques described herein can equally apply to other devices, including NR reduced capability (RedCap) devices.

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

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

[0117] A WTRU can monitor for a triggering condition associated with GNSS acquisition information reporting. For example, a triggering condition can include a NW request. For example, a triggering condition can include a threshold (e.g., last time of GNSS reporting > time threshold, WTRU location change > number, etc.). For example, a WTRU can periodically send GNSS acquisition information reporting. A triggering threshold can be biased, e.g., based on a WTRU’s speed, mobility state estimate, device type, measurements, satellite characteristics, etc.

[0118] If a WTRU determines that a triggering condition has been met (e.g., a WTRU determines that a triggering threshold is exceeded), the WTRU can report GNSS acquisition information. For example, a WTRU can report GNSS acquisition information via a MAC CE (e.g., 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, a WTRU can select among one or more signaling methods based on, e.g., 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, GNSS acquisition information (GNSS AI) can include one or more of the following: GNSS validity duration, GNSS acquisition time, characteristics of WTRU movement (e.g., WTRU speed, direction), preferred measurement gap configuration and / or configuration index, etc. Characteristics of a WTRU can include at least one of GNSS acquisition AI, location change, or change in WTRU speed.

[0119] As described herein, GNSS validity duration can include an indication of a duration associated with validity of a GNSS acquisition, an indication of a duration associated with expiration of a GNSS acquisition, or a WTRU location associated with a GNSS acquisition. Also as described herein, GNSS acquisition time can include a time at which a GNSS positioning is acquired.

[0120] As described herein, excessive GNSS acquisition and / or reporting can be prohibited. One or more of the following can apply. GNSS reporting (e.g., GNSS reporting of measurements and / or location information) and GNSS AI reporting (e.g., as described herein) can be subject to one or more techniques to reduce reporting frequency. For example, a WTRU can 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 can apply to: GNSS acquisition, GNSS reporting, and / or GNSS assistance information reporting. For example, the prohibition condition can include one or more of: a prohibition timer (e.g., started at acquisition of GNSS and / or at last transmission of GNSS); a condition based on GNSS validity duration (e.g., do not report and / or re-acquire before X seconds of GNSS validity remain); and / or a condition based on WTRU characteristics, such as a change in location of the WTRU and / or a speed of the WTRU (e.g., do not report GNSS unless location changes by X meters and / or unless WTRU speed > Y m / s).

[0121] GNSS reporting can include a WTRU reporting (e.g., to a network gNB) its location information (e.g., GNSS information) obtained via GNSS. GNSS AI reporting can include a WTRU reporting additional information (e.g., to a network, gNB, satellite) to support the WTRU acquiring its GNSS information. For example, the AI can include how long it takes for the WTRU to acquire GNSS, how long the WTRU remains valid before it will re-acquire GNSS, etc. The triggers for GNSS reporting and GNSS AI reporting can be different. For example, the trigger for GNSS reporting can be new location information (e.g., GNSS location) available. While the trigger for GNSS AI reporting can be an increase in time taken to acquire GNSS (e.g., WTRU is blocked by a building, trees, and / or a tunnel).

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

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

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

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

[0126] The WTRU can determine the override or termination of the prohibition condition in response to one or more of the following: one or more triggering events for GNSS reporting or occurrence of reporting during a prohibition time period, where the prohibition time period exceeds a threshold; receiving an explicit override request; or a GNSS validity timer expiring during the prohibition condition.

[0127] The WTRU can monitor one or more triggering conditions when the prohibition condition is determined to be active. The prohibition condition can be based on one or more of the following: GNSS validity duration, WTRU location, or WTRU speed.

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

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

[0130] The WTRU can stop transmitting and receiving data signals, control signals, and reference signals (e.g., SSB, PRS, CSI-RS) to receive GNSS information. The WTRU can be an Internet of Things (IOT) device. The WTRU can be a reduced capability (RedCap) device.

[0131] The WTRU can be configured with measurement gaps (e.g., to support the WTRU acquiring GNSS position / location information). The measurement gap configuration can be for devices that cannot acquire GNSS location information and transmit / receive data simultaneously (e.g., NB-IoT and / or reduced capability (RedCap) devices).

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

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

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

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

[0136] The WTRU can determine and / or report a validity duration of acquired GNSS 508 information. The validity duration can include, for example, a time that the WTRU can 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 to maintain accurate time synchronization, the WTRU can no longer maintain time / frequency synchronization with the network. The validity duration can include, for example, a time that the WTRU should start GNSS 508 reacquisition. For example, a GNSS 508 acquisition measurement gap 506 should start (or alternatively start) at the end of the validity duration. The validity duration can include, for example, a time that GNSS 508 acquisition should be completed (e.g., at least one GNSS 508 acquisition measurement gap 506 will be completed at the end of the validity duration). The validity duration can include, for example, a time that GNSS 508 can not be used for WTRU procedures. For example, at the expiration of the GNSS 508 validity duration, GNSS 508 position can not be used for timing advance calculation in non-terrestrial networks. The validity duration can include, for example, a time that GNSS 508 information can not be reported. For example, at the expiration of the GNSS 508 validity duration, GNSS 508 position can no longer be reported to the network.

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

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

[0139] The determination of the validity duration can be based on (e.g., take into account) WTRU characteristics, including, for example, WTRU movement, WTRU speed, and / or WTRU capabilities. The WTRU can be configured to report one or more WTRU characteristics (e.g., such as those listed herein) for use in determining the validity duration.

[0140] The WTRU can determine and report GNSS 508 acquisition time. The WTRU can be configured to determine the GNSS 508 acquisition time based on an earlier acquisition. For example, the WTRU can be configured to calculate the acquisition time of GNSS 508 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 can be configured to calculate the acquisition time of GNSS 508 based on the mean / average / median of the GNSS 508 acquisitions completed within a certain configured time period. For example, the WTRU can be configured to calculate the acquisition time of GNSS 508 based on a filtered GNSS 508 acquisition time, e.g., where the most recent acquisition time has more weight than the earlier acquisition times.

[0141] The WTRU can be configured to determine GNSS 508 acquisition time that depends on location range and / or duration. For example, GNSS 508 acquisition can 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 can be more likely to be indoors at certain times of the day, and the GNSS 508 acquisition time can be longer during those times. The WTRU can be configured to provide different sets of acquisition times that depend on location and / or time of day. For example, the WTRU can provide a first acquisition duration of X if the WTRU location is between coordinates 1 and 2, and a second acquisition duration of Y if the WTRU location is between coordinates 3 and 4, etc. Additionally or alternatively, the WTRU can 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, etc.

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

[0143] The WTRU can report additional assistance information to the network (e.g., in addition to the validity duration and / or acquisition time). For example, the WTRU can report to the network the accuracy of the GNSS 508 information (e.g., whether the GNSS 508 information is coarse and / or fine). For example, the WTRU can report to the network the characteristics of the WTRU’s movement (e.g., WTRU speed, WTRU direction, etc.). For example, the WTRU can report to the network another positioning information (e.g., measurements and / or results associated with PRS, sPRS, AoA, AoD, multi-RTT, TDOA, etc.). For example, the WTRU can 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 can report mobility state estimation conditions. For example, the WTRU can report whether the WTRU GNSS 508 information has been verified by the network. For example, the WTRU can report a preferred (or alternatively requested) measurement gap 506 configuration. If the WTRU reports a preferred measurement gap 506 configuration, the WTRU can be provided / indicated (or alternatively can have stored) one or more GNSS 508 measurement gap 506 configurations. Additionally or alternatively, the WTRU can indicate one or more preferred configurations, e.g., via an indication of an index and / or measurement gap 506 ID. For example, the WTRU can report a preferred time and / or frequency resource for the occurrence of the measurement gap 506.

[0144] The WTRU can 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 can be configured, e.g., 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 can be applied (e.g., active) for the duration of a 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; as long as the WTRU is attached to the network, e.g., even when in RRC idle state, etc.). The configuration can be applied (e.g., active) for a given time of day (e.g., until 12:01:03 UTC time). The configuration can be applied (e.g., active) for a given location (e.g., between GNSS 508 coordinates 1 and 2). The configuration can be applied (e.g., active) for the next GNSS 508 acquisition report and / or X GNSS 508 report.

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

[0146] The indication and / or configuration to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting can include a GNSS 508 acquisition assistance information reporting flag to enable / disable / suspend.

[0147] The indication and / or configuration to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting can include a configuration associated with triggering GNSS 508 acquisition assistance information reporting. For example, the configuration associated with triggering GNSS 508 acquisition assistance information reporting can include a location / distance based threshold (e.g., WTRU moves x meters from last reported location, WTRU is within GNSS 508 coordinates x and y, etc.). For example, the configuration associated with triggering GNSS 508 acquisition assistance information reporting can include a time based threshold (e.g., WTRU reports before X seconds, time of day is between absolute time 1 and time 2, etc.). For example, the configuration associated with triggering GNSS 508 acquisition assistance information reporting can include a periodicity between times to report GNSS 508. For example, the configuration associated with triggering GNSS 508 acquisition assistance information reporting can include a data related threshold.

[0148] The indication and / or configuration to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting can include an indication of a signaling type (e.g., MAC CE, RRC) to use.

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

[0150] The indication and / or configuration to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting can include an indication of a bias applied to a triggering condition. For example, the configuration can include an indication of whether the WTRU is to apply a bias to one or more triggering conditions (e.g., see the section on “WTRU characteristics based scaling reporting”).

[0151] The indication and / or configuration to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting can include an indication of whether to report full assistance information, a subset of information, and / or incremental signaling. For example, the WTRU can 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 movement, etc.); and / or values that have changed (e.g., only the validity time if the GNSS 508 acquisition time has not changed; and / or an empty report if no changes have occurred, and / or no reporting at all).

[0152] The indication and / or configuration to report GNSS 508 acquisition assistance information and / or to control aspects of GNSS 508 acquisition assistance information reporting can include an indication of resources to report the assistance information. For example, the configuration can include an indication of whether the WTRU can report the assistance information on a configured grant (e.g., on all configured grants, or on one or more configured grant configurations).

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

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

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

[0156] A WTRU can use one or more (e.g., multiple) techniques to report assistance information. For example, a WTRU can 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 can 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 can send the message via PUSCH resources and / or via a MAC CE.

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

[0158] For example, a WTRU can select a given assistance information reporting technique based on the type of random access (e.g., a WTRU performing a 2-step RACH can include a message within a MSG A, a WTRU performing a 4-step RACH can include a message within a MSG 3 and / or a MSG 5, etc.).

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

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

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

[0162] For example, the WTRU can 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, the WTRU can use RRC signaling if (e.g., only if) AS security has been activated. Otherwise, the WTRU can use MAC CE and / or other signaling.

[0163] The WTRU can send GNSS 508 acquisition assistance information via a MAC CE (e.g., GNSS 508 assistance information MAC CE). For example, the GNSS 508 assistance information MAC CE can include one or more of the following information fields: an “activate / deactivate” request field (e.g., for configuration of measurement gap 506, where the WTRU can 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 can send one or more types of GNSS 508 assistance information MAC CEs. For example, the WTRU can send a “necessary” and / or “truncated” GNSS 508 assistance information MAC CE, which can include a subset of information (e.g., information for configuring a measurement gap 506, such as GNSS 508 acquisition time and validity duration). For example, the WTRU can send a “full” GNSS 508 assistance information MAC CE, which can include additional assistance information (e.g., one or more of the additional information fields described herein).

[0165] The WTRU can determine whether to report a truncated GNSS 508 assistance information MAC CE and / or a full GNSS 508 assistance information MAC. For example, the WTRU can determine whether to report a full and / or truncated GNSS 508 assistance information MAC CE based on an amount of available resources that the WTRU can report (e.g., if the remaining available resources can support a full and / or truncated MAC CE and any additional header information). For example, the WTRU can determine whether to report a full and / or truncated GNSS 508 assistance information MAC CE based on network configuration (e.g., the WTRU can be configured to report a truncated and / or full MAC CE). For example, the WTRU can 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 can receive (e.g., via configuration, system information, based on specification, and / or dedicated signaling) a set of possible measurement gap 506 configurations associated with GNSS 508 acquisition. For example, each measurement gap 506 configuration can have an associated index and / or ID. The WTRU can send a MAC CE that can indicate a preferred GNSS 508 measurement gap 506 configuration, and an indication to activate / deactivate measurement gap 506.

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

[0168] The WTRU can include GNSS 508 acquisition assistance information with a WTRU capability report. For example, the WTRU can indicate that it is capable of reporting GNSS 508 assistance information, and / or can 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 can include GNSS 508 acquisition assistance information with a WTRU information request. For example, the WTRU can receive an indication to report information via a WTRU information request message. The indication can include a specific type of information to include (e.g., one or more of the WTRU assistance information described herein). The WTRU can respond with a WTRU information response message and can include one or more pieces of requested information (if available).

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

[0171] The WTRU can receive a measurement gap 506 configuration for GNSS 508 reporting. The measurement gap 506 configuration can include, for example, 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 can indicate, for example: a set of time and / or frequency resources in which the WTRU can perform GNSS 508 acquisition; and / or an index corresponding to a preconfigured, pre-provisioned, and / or stored measurement gap 506 configuration.

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

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

[0174] In certain scenarios, the WTRU can receive measurement gap 506 configurations for other purposes, such as positioning and / or radio link monitoring (e.g., to perform measurements for radio link monitoring). The WTRU can repurpose the measurement gap 506 for GNSS 508 acquisition. For example, if the validity duration of GNSS 508 has expired, the WTRU can determine whether to repurpose 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 has X seconds remaining), the WTRU can determine whether to repurpose the measurement gap 506 configured for other purposes. For example, if the GNSS 508 validity will expire during a future scheduled period (e.g., for UL transmission and / or DL reception), the WTRU can determine whether to repurpose the measurement gap 506 configured for other purposes. For example, if the measurement gap 506 configuration is sufficient for GNSS 508 acquisition (e.g., if the measurement gap 506 contains sufficient time / frequency resources to perform GNSS 508 acquisition), the WTRU can determine whether to repurpose the measurement gap 506 configured for other purposes.

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

[0176] The WTRU can receive a configuration to prohibit GNSS 508 acquisition and / or reporting of GNSS 508 information (e.g., GNSS 508 prohibit configuration). The GNSS 508 prohibit configuration can be, e.g., semi-statically configured (e.g., via RRC configuration). The GNSS 508 prohibit configuration can be, e.g., indicated in system information (e.g., within an NTN-specific system information block, such as SIB31 / 32). The GNSS 508 prohibit configuration can be, e.g., dynamically indicated (e.g., within a DCI indication, and / or indicated within a NW request for GNSS 508 location information).

[0177] The GNSS 508 prohibit configuration can include one or more of the following: a prohibit duration; a condition to update a variable length timer; a condition to override the prohibition; an indication of WTRU behavior during the prohibit period; and / or a configuration associated with the prohibition method (e.g., timer and duration, and / or thresholds and events for conditional prohibition).

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

[0179] A WTRU can be configured with a prohibit timer. For example, the prohibit timer can apply to GNSS 508 acquisition and / or GNSS 508 reporting. In certain scenarios, a WTRU can be configured with multiple prohibit timers (e.g., a timer for GNSS 508 acquisition and a timer for GNSS 508 reporting). While the prohibit timer is running, the WTRU can be prevented from performing GNSS 508 acquisition and / or reporting. A WTRU can start and / or restart the prohibit timer. For example, a WTRU can start and / or restart the prohibit timer after acquiring GNSS 508 location information. For example, a WTRU can start and / or restart the prohibit timer after acknowledging successful reception of a GNSS 508 information report (e.g., upon receiving a HARQ-ACK for a transmission containing the GNSS 508 report). A WTRU can stop the prohibit timer. For example, a WTRU can stop the prohibit timer upon RRC connection state transition (e.g., upon transitioning to idle and / or inactive state). For example, a WTRU can stop the prohibit timer upon radio link failure (RLF). For example, a WTRU can stop the prohibit timer upon BFD. For example, a WTRU can stop the prohibit timer upon initiating a random access procedure.

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

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

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

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

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

[0185] The WTRU can override the prohibition of GNSS 508 reporting, which can be subject to configured constraints. One or more of the following can apply. The WTRU can override the prohibition of GNSS 508 reporting based on the type of triggering condition that caused the GNSS 508 acquisition and reporting. For example, if the GNSS 508 acquisition and / or reporting is periodic and / or WTRU event triggered, an explicit request from the network can override the prohibition of GNSS 508 reporting / acquisition. The WTRU can override the prohibition of GNSS 508 reporting based on a NW request (e.g., the NW can override the prohibition based on an explicit flag). The WTRU can implicitly override the prohibition of GNSS 508 reporting, e.g., if an (e.g., any) RRC reconfiguration is received. The WTRU can restart the prohibition 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 prohibition timer can be restarted. The WTRU can override the prohibition of GNSS 508 reporting after RLF recovery and / or reestablishment. The WTRU can override the prohibition of GNSS 508 reporting after (e.g., any) cell change (e.g., cell reselection and / or handover). The WTRU can override the prohibition of GNSS 508 reporting if one or more (e.g., multiple) triggering conditions have been met (e.g., the number of met triggering conditions can be configured for override).

[0186] The WTRU can receive, via configuration information, at least one prohibition condition configured to prohibit GNSS activity. The GNSS activity can include at least one of GNSS acquisition, GNSS reporting, or GNSS assistance information (AI) reporting. The WTRU can identify a trigger related to the GNSS activity. The WTRU can determine whether the prohibition condition is activated. The prohibition condition can 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 can 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.

[0187] Upon satisfying the override condition, the WTRU can report (e.g., immediately report) the available (e.g., most recent available) GNSS 508 information and / or upon having acquired updated GNSS 508 information (e.g., if the GNSS 508 information is the same as previously reported GNSS 508 information). Additionally or alternatively, upon satisfying the override condition, the WTRU can acquire (e.g., immediately acquire) GNSS 508 information.

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

[0189] A WTRU can receive a configuration for GNSS 508 acquisition assistance information reporting (e.g., GNSS 508 AI reporting). The GNSS 508 acquisition AI reporting configuration can be provided / received via RRC signaling (e.g., via a GNSS 508 acquisition AI IE). The GNSS 508 acquisition AI reporting configuration can apply per MAC entity and / or per serving cell. The GNSS 508 acquisition AI IE can include one or more of the following information fields (e.g., RRC parameters): an enable / disable indication; a condition (e.g., reporting threshold) that triggers the GNSS 508 acquisition AI reporting; a signaling method (e.g., via RRC and / or MAC CE) to report the GNSS 508 acquisition AI; information (e.g., GNSS 508 validity duration and / or GNSS 508 acquisition time) to include in the GNSS 508 acquisition AI report; and / or a prohibit condition (e.g., prohibit timer duration and / or scaling bias for reporting trigger) to reduce excessive reporting.

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

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

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

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

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

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

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

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

[0198] The WTRU can perform GNSS activity when the barring condition is determined to be inactive. Characteristics of the WTRU can include at least one of GNSS acquisition AI, change in location, or change in speed of the WTRU. The WTRU can determine coverage or termination of the barring condition in response to one or more of the following: one or more triggering events for GNSS reporting or occurrence of reporting during a barring period, where the barring period exceeds a threshold; receiving an explicit coverage request; or a GNSS validity timer expiring during the barring condition. When the barring condition is determined to be active, the WTRU can monitor one or more triggering conditions. The barring condition can be based on one or more of the following: GNSS validity duration, WTRU location, or WTRU speed.

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

[0200] The WTRU can report GNSS AI using different types of signaling based on reporting GNSS validity duration or GNSS acquisition time. For example, the WTRU can 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). The WTRU can use a medium access control (MAC) information element (IE) to send / issue a GNSS AI location report to a gNB. In some cases, the GNSS AI can be included in a measurement report. In some cases, the WTRU can use WTRU capability signaling to report GNSS AI.

[0201] In sending a GNSS report, the WTRU can start and / or restart a GNSS reporting barring timer. During the barring timer, the WTRU can be limited and / or prevented from reporting GNSS location information. Additionally or alternatively, the WTRU can start and / or restart the GNSS barring timer upon successful acquisition of GNSS information and / or upon receiving HARQ feedback (e.g., ACK) for a transmission carrying GNSS information and / or a GNSS report.

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

[0203] The WTRU can override the barring conditions for GNSS reporting and / or GNSS acquisition AI reporting, which can be further subject to additional conditions. For example, the additional conditions can include: a number of triggering events during a barring time exceeds a threshold; a network (NW) request; and / or at GNSS validity expiration.

[0204] FIG. 7 An example 702 is shown associated with barring for GNSS (e.g., and / or GNSS acquisition assistance information) reporting.

[0205] The barring conditions can also or alternatively apply to GNSS acquisition AI reporting. Separate configurations and / or indications can be provided for GNSS reporting and GNSS AI reporting. Separate barring timers can be maintained for GNSS reporting and GNSS assistance information reporting.

[0206] A gNB can send GNSS reporting configuration information, including barring conditions 704, to a WTRU. The WTRU can be an Internet of Things (IOT) device. The WTRU can be a Reduced Capability (RedCap) device. The barring conditions can include a barring timer based condition, a GNSS validity duration based condition, or a WTRU characteristic based condition. The WTRU can receive configuration information for reporting Global Navigation Satellite System (GNSS) assistance information (AI). The configuration information can include a reporting trigger threshold, which is at least one of a distance threshold or a time offset threshold. At 706, the WTRU can determine that a reporting trigger is satisfied (e.g., the reporting trigger threshold is exceeded). The reporting trigger threshold can 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 a GNSS validity duration expiration. The reporting trigger threshold can be exceeded when a current location of the WTRU exceeds a previously reported WTRU location by a configured threshold.

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

[0208] At 720, the WTRU can report (e.g., send, transmit, etc.) GNSS AI to the gNB. The WTRU can report GNSS AI using a MAC CE, RRC, measurement report, and / or capability signaling. The GNSS AI can 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 can include an indication of a duration associated with validity of GNSS acquisition, an indication of a duration associated with expiration of GNSS acquisition, and / or a WTRU location associated with GNSS acquisition. The GNSS acquisition time can include a time to acquire a GNSS position. The WTRU can determine coverage or termination of a prohibit condition in response to one or more of: one or more triggering events for GNSS reporting or a report occurring during a prohibit period that exceeds a threshold; receiving an explicit coverage request; or a GNSS validity timer expiring during the prohibit condition.

[0209] In the performance of GNSS activity, the WTRU can report via a medium access control (MAC) information element (IE) when the GNSS AI includes a GNSS validity duration and via a radio resource control (RRC) based on RRC state when the GNSS AI includes a positioning fix duration. When a GNSS reporting condition is satisfied and a prohibit condition is active, the WTRU can perform one or more of: delaying GNSS activity until the prohibit condition is not active or expires, indicating that the prohibit condition is active, or indicating when GNSS activity is enabled.

[0210] A WTRU can report GNSS Al based on reporting GNSS validity duration or GNSS acquisition time using different types of signaling. For example, a WTRU can 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] A WTRU can receive, via configuration information, at least one prohibition condition configured to prohibit GNSS activity. GNSS activity can include at least one of GNSS acquisition, GNSS reporting, or GNSS assistance information (Al) reporting. The WTRU can identify a trigger related to GNSS activity. The WTRU can determine whether a prohibition condition is active. The prohibition condition can include a prohibition timer based condition, a GNSS validity duration based condition, or a WTRU characteristic based condition. When a prohibition condition is determined to be active, the WTRU can perform GNSS activity in response to an override or termination of the prohibition condition and based on the prohibition condition being determined to be active.

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

[0213] At 810, the WTRU can determine what the content of the GNSS AI is if GNSS reporting and / or acquisition is allowed and / or if the barring conditions are covered. At 812, the WTRU can send the GNSS AI report via MAC CE if the GNSS AI includes a validity duration. At 814, the WTRU can send the GNSS AI report via RRC if the GNSS AI includes a positioning fix duration. The RRC signaling can include one or more measurement reports, capability signaling, setup / resume message.

Claims

1. A wireless transmit receive unit (WTRU), comprising: a processor configured to: receive configuration information for reporting global navigation satellite system (GNSS) assistance information; transmit, via radio resource control (RRC) signaling, a first report including GNSS assistance information after a change in RRC state of the WTRU, wherein the GNSS assistance information includes a GNSS acquisition time and a GNSS validity duration; receive a measurement gap configuration associated with the GNSS report, wherein the measurement gap configuration includes an indication of time resources for performing a GNSS acquisition; acquire a GNSS during the time resources indicated by the measurement gap configuration; and transmit, via a medium access control (MAC) control element (CE), a second report, wherein the second report indicates a remaining portion of the GNSS validity duration.

2. The WTRU of claim 1, wherein the processor is configured to transmit the first report upon RRC connection setup complete or upon resuming an RRC connection.

3. The WTRU of claim 1, wherein the processor is configured to transmit the second report during a random access procedure.

4. The WTRU of claim 1, wherein the GNSS validity duration includes an indication of a duration associated with a validity of a GNSS acquisition, and the remaining portion of the GNSS validity duration includes an indication of a duration associated with an expiration of the GNSS acquisition.

5. The WTRU of claim 1, wherein the GNSS validity duration indicates an explicit duration associated with a validity of a GNSS acquisition.

6. The WTRU of claim 5, wherein the remaining portion of the GNSS validity duration indicates an explicit duration associated with an expiration of the GNSS acquisition.

7. The WTRU of claim 1, wherein the GNSS acquisition time includes a time for acquiring a GNSS position.

8. The WTRU of claim 1, wherein the processor is configured to perform a location based measurement to acquire the GNSS during the time resources indicated by the measurement gap configuration.

9. The WTRU of claim 1, wherein the processor is configured to determine a GNSS position associated with the WTRU to acquire the GNSS.

10. The WTRU of claim 1, wherein GNSS acquisition is based on capability information associated with the WTRU or a speed of the WTRU.

11. The WTRU of claim 1, wherein the WTRU is an internet of things (IOT) device.

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

13. 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; sending a first report including GNSS assistance information via radio resource control (RRC) signaling after a change in a RRC state of the WTRU, wherein the GNSS assistance information includes a GNSS acquisition time and a GNSS validity duration; receiving a measurement gap configuration associated with a GNSS report, wherein the measurement gap configuration includes an indication of time resources for performing a GNSS acquisition; acquiring a GNSS during the time resources indicated by the measurement gap configuration; and sending a second report via medium access control (MAC) control element (CE), wherein the second report indicates a remaining portion of the GNSS validity duration.

14. The method of claim 13, further comprising: sending the first report upon completion of RRC connection establishment or upon resumption of RRC connection.

15. The method of claim 13, further comprising: sending the second report during a random access procedure.

16. The method of claim 13, wherein the GNSS validity duration includes an indication of a duration associated with a validity of a GNSS acquisition, and the remaining portion of the GNSS validity duration includes an indication of a duration associated with an expiration of the GNSS acquisition.

17. The method of claim 13, wherein, the GNSS validity duration indicates an explicit duration associated with a validity of a GNSS acquisition.

18. The method of claim 17, wherein, the remaining portion of the GNSS validity duration indicates an explicit duration associated with an expiration of the GNSS acquisition.

19. The method of claim 13, wherein, the GNSS acquisition time includes a time for acquiring a GNSS position.

20. The method of claim 13, further comprising: performing a location-based measurement to acquire the GNSS during the time resources indicated by the measurement gap configuration.

Images