Conditional triggers for flight path update instructions

Abstract

Systems, methods, devices, and means related to conditional triggers for flight path update instructions are described herein. A wireless transmit / receive unit (WTRU) may receive configuration information. The configuration information may indicate a trigger condition (e.g., a threshold) associated with enabling transmission of a flight path update instruction. The WTRU may determine that the threshold associated with enabling transmission of the flight path update instruction is met. Based on the threshold being met, the flight path update instruction may be transmitted. The WTRU may receive a request to transmit updated flight path information and transmit the updated flight path information.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 445,617, filed February 14, 2023, the disclosure of which is incorporated herein by reference in its entirety. [Background technology]

[0002] Mobile communications using wireless communications continue to evolve. The fifth generation of mobile communications radio access technology (RAT) may be referred to as 5G new radio (NR). Previous (traditional) generations of mobile communications RAT may be, for example, fourth generation (4G) long term evolution (LTE). Summary of the Invention

[0003] SUMMARY Systems, methods, devices, and means relating to conditional triggering for flight path update instructions are described herein.

[0004] A wireless transmit / receive unit (WTRU) may receive configuration information. The configuration information may indicate a trigger condition (e.g., a threshold) associated with enabling transmission of a flight path update instruction. The WTRU may determine that the threshold associated with enabling transmission of a flight path update instruction is met.

[0005] For example, the threshold may be a configurable threshold. A distance threshold associated with enabling transmission of a flight path update instruction may be met based on the distance between the WTRU's position and a previously provided flight path location exceeding the distance threshold. In an example, the threshold may be a time-based threshold. A time-based threshold associated with enabling transmission of a flight path update may be met based on an arrival time at a waypoint location exceeding a previously reported arrival time by a time-based threshold. In an example, the threshold may be a waypoint threshold. A waypoint threshold associated with enabling transmission of flight path instructions may be met based on the number of disabled waypoints exceeding the waypoint threshold.

[0006] Based on the threshold being met, a flight path update indication may be transmitted. In an example, the flight path update indication may be transmitted via a UE assistance information (e.g., WTRU assistance information) message or via radio resource control (RRC) signaling. The WTRU may receive a request to transmit updated flight path information and transmit the updated flight path information. [Brief explanation of the drawings]

[0007] [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1B is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1C] 1A is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1D]1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 2] 1 illustrates an example signaling flow for flight path reporting. [Figure 3] 1 illustrates an exemplary unmanned aerial vehicle (UAV) procedure for updating an initial flight path report. [Figure 4] 1 illustrates an example of an initial flight path reporting procedure. [Figure 5] 10 illustrates an example of a conditional trigger for updated instructions. [Figure 6] 1 illustrates an example of a periodic or network-requested trigger for flight path status indication. [Figure 7] 1 illustrates an example of a partial and / or delta update instruction. [Figure 8] 1 illustrates an example of a pre-configured fallback. [Figure 9] 1 illustrates an exemplary request for an alternative flight path. DETAILED DESCRIPTION OF THE INVENTION

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

[0009] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RANs 104 / 113, CNs 106 / 115, public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of WTRUs 102a, 102b, 102c, 102d may 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 may be referred to as a "station" and / or "STA," may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (ioT) devices, watches or other wearable, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., for remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

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

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

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

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

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

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

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

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

[0018] 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point and may utilize any suitable RAT to facilitate wireless connectivity in a local area such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may 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 may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. 1A, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114b may not need to access the Internet 110 through the CN 106 / 115.

[0019] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, such as different throughput, latency, error tolerance, reliability, data throughput, and mobility requirements. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A , it will be understood that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs that use 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 may utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

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

[0023] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

[0026] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.

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

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

[0029] 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) regarding the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0030] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The peripheral device 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, a direction 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.

[0031] The WTRU 102 may include a full-duplex radio where transmission and reception of some or all of the signals associated with a particular subframe (e.g., for both the UL (e.g., for transmission) and downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference through either hardware (e.g., a choke) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either the uplink UL (e.g., for transmission) or downlink (e.g., for reception)).

[0032] 1C is a system diagram illustrating the RAN 104 and the CN 106, according to one embodiment. As mentioned above, the RAN 104 may use E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also communicate with the CN 106.

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

[0034] Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, etc. As shown in FIG. 1C, the eNodeBs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0035] 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the foregoing elements is depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

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

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

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

[0040] Although the WTRU is illustrated in FIGS. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments, such a terminal may use a wired communication interface (e.g., temporarily or permanently) with the communication network.

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

[0042] A WLAN in infrastructure Basic Service Set (BSS) mode may have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating outside the BSS and destined for a STA may arrive through the AP and be sent to the STA. Traffic originating at a STA and destined for a destination outside the BSS may be sent to the AP to be sent to the respective destination. Traffic between STAs within a BSS may be sent through the AP, for example, where the source STA may send traffic to the AP, and the AP may send traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between (e.g., directly between) a source STA and a destination STA using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (e.g., all of the STAs) may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad hoc" communication mode.

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

[0044] High Throughput (HT) STAs may use 40 MHz wide channels for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

[0045] A Very High Throughput (VHT) STA may support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. A 40 MHz and / or 80 MHz channel may be formed by combining adjacent 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-adjacent 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data may pass through a segment parser that may separate the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed, and the combined data may be sent to Medium Access Control (MAC).

[0046] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter-type control / machine-type communications, such as MTC devices within macro coverage areas. MTC devices may have limited capabilities, including support for (e.g., only) certain and / or limited bandwidths. MTC devices may include batteries with above-threshold battery life (e.g., to maintain very long battery life).

[0047] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 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 configured and / or limited by the STAs among all STAs operating in the BSS that support the minimum bandwidth operating mode. In an 802.11ah embodiment, the primary channel can be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) configuration can depend on the status of the primary channel. For example, if the primary channel is active due to a STA (that only supports 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered active, even though most of the frequency band may remain inactive and available.

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

[0049] 1D is a system diagram illustrating the RAN 113 and the CN 115, according to one embodiment. As noted above, the RAN 113 may use NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also communicate with the CN 115.

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

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

[0052] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., eNodeBs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to gNBs 180a, 180b, 180c while also communicating with and connecting to another RAN, such as eNodeBs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

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

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

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

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

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

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

[0059] 1A-1D and their corresponding descriptions, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[0060] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation devices may be directly coupled to another device for testing purposes and / or may perform the tests using terrestrial wireless communication.

[0061] One or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, e.g., one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0062] References herein to a timer may refer to determining a time or determining a period of time. References herein to a timer expiring may refer to determining that a time has occurred or that a period of time has expired. References herein to a timer may refer to time, a period of time, keeping track of time, keeping track of a period of time, etc.

[0063] SUMMARY Systems, methods, devices, and means relating to conditional triggering for flight path update instructions are described herein.

[0064] A wireless transmit / receive unit (WTRU) may receive configuration information. The configuration information may indicate a trigger condition (e.g., a threshold) associated with enabling transmission of a flight path update instruction. The WTRU may determine that the threshold associated with enabling transmission of the flight path update instruction is met.

[0065] In an example, the threshold may be a distance threshold. A distance threshold associated with enabling transmission of a flight path update instruction may be met based on the distance between the WTRU's position and a previously provided flight path location exceeding the distance threshold. In an example, the threshold may be a time-based threshold. A time-based threshold associated with enabling transmission of a flight path update may be met based on an arrival time at a waypoint location exceeding a previously reported arrival time by a time-based threshold. In an example, the threshold may be a waypoint threshold. A waypoint threshold associated with enabling transmission of flight path instructions may be met based on the number of disabled waypoints exceeding the waypoint threshold.

[0066] Based on the threshold being met, a flight path update indication may be transmitted. In an example, the flight path update indication may be transmitted via a UE assistance information (e.g., WTRU assistance information) message or via radio resource control (RRC) signaling. The WTRU may receive a request to transmit updated flight path information and transmit the updated flight path information.

[0067] Examples of flight path update instructions and reporting configurations are provided herein. A WTRU may receive a UE Information Request message (e.g., a WTRU Information Request message) that includes a flight path reporting configuration requesting flight path information. The flight path reporting configuration (e.g., configuration information) may include at least one of the following: the number of waypoints, whether to include timestamp information, conditions and associated thresholds for triggering updated flight path instructions, a configuration for periodically reporting flight path information updates, or fallback candidate flight paths and / or waypoints if a deviation is necessary (e.g., additional fallback candidate flight paths and / or waypoints).

[0068] The periodicity configuration (e.g., periodicity configuration information) may include one or more of the following: periodicity, window and / or resources for reporting updated flight path, or scaling / bias for changing the periodicity based on the speed and / or location of the WTRU. The conditions for triggering updated flight path instructions may include one or more of the following: distance and / or delay from the original reported value exceeding a threshold, number of waypoints and / or timestamps exceeding a threshold that have been disabled, number of waypoints and / or timestamps exceeding a threshold (e.g., number of available new waypoints and / or timestamps exceeding a threshold), or receipt of a message to initiate collision avoidance (e.g., from the CN).

[0069] Examples of trigger conditions for a flight path update indication are provided herein. If one or more of the trigger conditions are met, the WTRU may transmit an indication that an updated flight path is available. With a configured periodicity, the WTRU may evaluate whether the flight path information has changed since the previous flight path report was sent (e.g., since the initial flight path report was sent). If the previous flight path has changed (e.g., the previous flight path information is invalid or a waypoint (e.g., a new waypoint) is available), the WTRU may transmit an indication (e.g., via example UE assistance information (e.g., WTRU assistance information)) that updated flight path information is available. The WTRU may receive a request to transmit updated flight path information. The WTRU may transmit the updated flight path information. If the previous flight path has not changed, the WTRU may transmit an acknowledgement that no changes have occurred since the previous flight path report. If the configured periodicity is a skip opportunity, the WTRU may retroactively indicate that an instruction was previously skipped (e.g., the past X instructions were skipped).

[0070] Examples of partial and / or delta flight data reporting are provided herein. The WTRU may transmit updated partial and / or delta flight path information that includes one or more of the following: a flag to report signaling (e.g., reporting waypoint and delta information from the initial flight path report), a flag to report that waypoint and / or timestamp information is available (e.g., reporting new waypoint and / or timestamp information that is available), a flag to report waypoints and / or timestamps, a flag to report information that has become invalid, or a flag to report information that has become invalid due to a threshold.

[0071] Examples of fallback flight path applications are provided herein. The WTRU may evaluate candidate fallback waypoints and / or flight paths to determine whether one or more candidate fallback waypoints and / or flight paths are suitable alternative routes. If suitable candidates are found, the WTRU may apply the fallback waypoints and / or flight paths and notify the network that the (e.g., pre-configured) fallback waypoints and / or flight paths are being applied. In an example, the WTRU may indicate (e.g., by sending an index) which waypoints and / or flight paths are being updated. The WTRU may detect that the initial flight path is invalid and notify the network. The WTRU may monitor network indications of updated fallback waypoints and / or flight paths to apply. If the WTRU receives one or more fallback waypoints and / or flight paths, the WTRU may update the currently maintained flight path (e.g., the initial flight path) and send an acknowledgment (ACK) to the network that the updated flight path is being applied.

[0072] Examples of flight path reporting are provided for unmanned aerial vehicles (UAVs) traveling at heights of up to 300 meters. These examples may target use cases including drone operations, personal entertainment for flight experiences, and / or cargo delivery. Examples of capabilities for remote control and data transmission related to flight path reporting may be provided.

[0073] An example of flight path reporting for an air WTRU based on WTRU capabilities is provided. The flight path information may include a number of waypoints, which may be 3D locations. The WTRU may indicate whether flight path information is available via the RRCConnectionReconfigurationComplete, RRCConnectionReestablishmentComplete, RRCConnectionResumeComplete, or RRCConnectionSetupComplete message. This may allow the network to know (e.g., immediately after) connection establishment, resumption, and / or modification whether flight path information is available, which may enable subsequent flight path report configurations and requests.

[0074] Figure 2 illustrates an example signaling flow for flight path reporting. The E-UTRAN may request the WTRU to report flight path information via a flightPathInfoReq in a UEInformationRequest message. When requesting to report WTRU flight path information, the WTRU may include a FlightPathInfoReport containing available waypoints (e.g., all available waypoints up to a configured maximum) in the UEInformationResponseMessage. Such information may be useful to the network (e.g., for collision avoidance, resource provisioning, and WTRU configuration). Support for configuring (e.g., currently supporting) up to 20 waypoint locations in the flight path report may be provided. The RAN2 may verify that up to 20 waypoint locations may be sufficient for NR use cases.

[0075] The WTRU may be configured (e.g., additionally configured) to include timestamp information associated with waypoints (e.g., each waypoint) via includeTimeStamp in FlightPathInforReportConfig. The timestamp may improve the predictability of the WTRU location at a given time, further aiding in WTRU configuration and planning future resource allocation. However, timestamp information may not always be known and may be included (e.g., only included) in flight path reports if such information is available at the WTRU.

[0076] Examples of flight path reporting may be provided, including flight path availability indication via a radio resource control (RRC) completion message, flight path request and reporting via a UE information request and / or response (e.g., WTRU information request and / or response) procedure, and similar flight path reporting content.

[0077] 3 illustrates an example procedure for updating the initial flight path report. This specification provides examples of triggers for updating the flight path report of a UAV. During flight path reporting, if the flight path is not updated efficiently after the initial flight path report, this can cause problems, for example, if the WTRU deviates from the planned flight path due to collision avoidance (e.g., possibly invalidating one or more reported waypoints or timestamps).

[0078] To maximize the reuse of existing reporting procedures, most signaling can be reused for update reporting, apart from indicating flight path availability, which may be indicated in the UEAssistanceInformation message. The network may (e.g., may then) use UE information request and / or response (e.g., WTRU information request and / or response) procedures to retrieve the updated flight path. Excessive and unlimited flight path updates may result in additional interference, signaling overhead, and may impact the battery power consumption of the WTRU. Examples are provided herein for maintaining flight path information at a desired level of accuracy for the current needs of the WTRU / network, while minimizing signaling overhead and interference.

[0079] Exemplary flight path update scenarios may include a WTRU that may perform autonomous flight path updates and notify the network if a previously reported flight path is invalid or out of date. These examples may include the trigger and content of a flight path update instruction and / or the transmission and content of an updated flight path report.

[0080] An exemplary flight path update scenario may include a WTRU that may be limited to a set of candidate waypoints and / or routes. If the flight path is invalid, the WTRU may apply a fallback flight path. Examples may include pre-configuration of fallback candidates and WTRU autonomous application of a flight path update with subsequent notification. The network may provide a fallback route if the WTRU indicates that the route is no longer valid.

[0081] Although examples herein may refer to flight path reporting for a UAV, the described examples may apply (e.g., may be similarly applied) to other devices or situations in which trajectory or path information is exchanged, e.g., for autonomous vehicles, vehicle-mounted mobile repeaters / base stations, etc. In such situations, flight path may be exchanged for an equivalent interpretation (e.g., trajectory, itinerary, etc.).

[0082] Examples herein may consider at least one of the following: the WTRU may trigger (e.g., only trigger) a flight path update if the flight path change significantly impacts accuracy (e.g., there may be some margin of error built into the triggering conditions); the WTRU may update (e.g., only update) changed flight path information to minimize additional signaling overhead (e.g., unchanged information does not need to be retransmitted); the WTRU may have a better idea of ​​the flight path status than the network (e.g., therefore, the WTRU may ignore an update request if the information has not changed); or different conditions may apply if the WTRU is providing additional waypoints versus reporting an error in a previous flight path report.

[0083] Examples described herein may enable precise flight paths to be maintained (e.g., to ensure proper collision avoidance and resource allocation planning) while minimizing additional signaling overhead and interference.

[0084] 4 illustrates an example of an initial flight path reporting procedure. The WTRU may indicate whether flight path information is available via the RRCConnectionReconfigurationComplete, RRCConnectionReestablishmentComplete, RRCConnectionResumeComplete, or RRCConnectionSetupComplete message. The E-UTRAN may request the WTRU to report flight path information by including a flightPathInfoReq information element (IE) in a UEInformationRequest message. In this IE, the network may include the number of waypoints to be reported by the WTRU (e.g., up to a maximum of 20) and may request (e.g., also request) timestamp information. The WTRU may respond to the UEInformationRequest by including a flightPathInfoReport IE in a UEInformationResponseMessage, which may include waypoints up to a configured maximum (e.g., all available waypoints) and timestamp information requested by the network and available to the WTRU.

[0085] The exemplary UAV may employ similar flight path reporting content (e.g., waypoints and optional timestamps) and initial reporting procedures. The exemplary UAV may update (e.g., incrementally update) a previously reported flight path via an instruction in a UE assistance information message (e.g., a WTRU assistance information message). The network may retrieve the updated flight path using a legacy UE information request and / or response (e.g., legacy WTRU information request and / or response) procedure (e.g., where shown) (e.g., or in other examples herein may use a legacy UE information request and / or response (e.g., legacy WTRU information request and / or response) procedure). The UE assistance information message may be referred to herein as a WTRU assistance information message. The UE information request may be referred to herein as a WTRU information request. The UE information response may be referred to herein as a WTRU information response.

[0086] The WTRU may receive a value of at least one parameter of a configuration for triggering a flight path update (e.g., an instruction and / or a report) (e.g., configuration information) from RRC, MAC, or downlink control information (DCI) signaling (e.g., a trigger condition associated with enabling transmission of a flight path update instruction). In an example, the WTRU may receive the configuration information in an initial flight path reporting configuration (e.g., in a UE Information Request message (e.g., a WTRU Information Request message)) or in an HO command (e.g., in an RRC reconfiguration with synchronization message).

[0087] The WTRU may receive multiple configurations for triggering flight path updates. The configurations (e.g., each configuration) may be identified by an index and may receive an indication of the applicable configuration from signaling. The configurations may be specific to one or more of the following: a cell (e.g., a serving cell) or group of cells, a TRP or group of TRPs, or a location (e.g., a waypoint) or range of locations.

[0088] The WTRU may determine at least one value from one or more of the following: system information, a dedicated RRC message (e.g., RRC reconfiguration, RRC connection release), a field in a random access response (RAR) message, or characteristics of an RAR grant. In an example, the WTRU may determine the value of the configuration index from some most significant or least significant bits of a modulation and coding scheme (MCS) field or from a time domain resource allocation (TDRA) field. The mapping between bits and corresponding values ​​may be predefined or signaled by RRC.

[0089] At least one parameter or configuration index may be determined from a combination of the above examples. The configuration and / or indication by the network may be received with the first message and may be enabled / disabled (e.g., then enabled / disabled) in the second message by network signaling (e.g., MAC CE, DCI, SIB, RRC, random access channel (RACH) message, etc.).

[0090] The WTRU may send a flight path update indication (e.g., an indication that the current flight path has changed from the most recent flight path report) and / or an updated flight path report (e.g., a full flight path report or a delta / partial flight path report including waypoints and timestamps) via one or more of the following: UE assistance information (e.g., WTRU assistance information), UE information response message (e.g., WTRU information response message), RRC signaling, MAC CE, RACH msg (e.g., MSG3, MSG5, MSGA), configured grant opportunity, L1 report, or scheduling request.

[0091] Examples of the content of a flight path update instruction are provided herein. The flight path update instruction may include a flag that the current flight path information has changed from the previously reported flight path. In an example, the WTRU may send additional and / or more detailed information regarding the status of the current flight path. The WTRU may send one or more pieces of information within the flight path update instruction: invalid time information, invalid waypoint information, the number of invalid timestamps and / or waypoints, the level of change (e.g., small change, large change, percentage change, value of change) (where the WTRU may determine the level of change based on network configuration), the number of available timestamps and / or waypoints (e.g., available new timestamps and / or waypoints), the number of waypoints to be added (e.g., new waypoints to be added), or the number of waypoints to be deleted.

[0092] Examples of detecting that a previously reported flight path is no longer valid (e.g., enabling transmission of a flight path update instruction) are provided herein. In examples, a WTRU may autonomously (e.g., based on WTRU implementation) determine whether flight path information is considered changed and / or invalid (e.g., enabling transmission of a flight path update instruction) if at least one or a combination of the following conditions occurs: the WTRU's actual position deviates from its planned position (e.g., a previously provided flight path location) at a given time by more than a threshold (e.g., a first distance threshold), the WTRU's actual position deviates from the flight path's closest position by more than a threshold (e.g., a second distance threshold), the distance between the WTRU's actual position and the (valid) fallback flight path's closest position is less than the distance between the WTRU's actual position and the current flight path's closest position minus a threshold (e.g., a third threshold), the WTRU receives an indication from the network (e.g., by RRC) that the current flight path should be considered invalid, the WTRU receives an indication from the UAV control entity, or receiving an indication from another UAV that the current flight path should be considered invalid; if the expected / anticipated arrival time (e.g., a previously reported arrival time) for a particular waypoint or set of waypoints differs from the current flight path information (e.g., the arrival time at the current waypoint location) by a particular duration (e.g., a time-based threshold); if the expected / anticipated waypoint at a particular time differs by a particular distance from the waypoint shown in the current flight path information; if the WTRU does not expect to be within a particular configured radius / distance from the waypoint; if the WTRU does not expect to be at a waypoint within a particular configured time from the time it is expected to be at that waypoint; if the number or percentage of waypoints (e.g., invalidated waypoints) (e.g., in the current flight path information available in the network) that the WTRU does not expect to pass through rises above / falls below a threshold (e.g., a waypoint threshold);The WTRU may receive the first, second, and third distance thresholds by signaling, such as an RRC message, if the WTRU has not reached a waypoint that it was expected to reach when the periodic reporting was triggered, if the WTRU has not traversed a certain number or percentage of waypoints that it was expected to traverse when the periodic reporting was triggered, or if the WTRU's mobility state has changed by a certain level since the previous period when the periodic reporting was triggered and / or sent (e.g., the WTRU velocity has changed by a certain amount, percentage level, etc.). The WTRU may receive the first, second, and third distance thresholds by signaling, such as an RRC message.

[0093] Examples of conditional triggers for flight path updates are provided herein. In an example, a WTRU may be configured to send an indication to the network that its flight path information will be updated based on one or more conditions (e.g., based on one or more trigger conditions and / or thresholds being met). The WTRU may send the updated flight path if requested (e.g., subsequently) by the network. In an example, the WTRU may perform one or more of the following:

[0094] The WTRU may send a first message (e.g., an RRC Connection Complete message) indicating that flight path information is available. The WTRU may receive a second message (e.g., a UE Information Request message (e.g., a WTRU Information Request message)) including a flight path reporting configuration requesting the flight path information. The flight path reporting configuration (e.g., configuration information) may include at least one of the following: the number of waypoints, whether to include timestamp information, or conditions (e.g., and associated thresholds) for triggering updated flight path instructions (e.g., trigger conditions for indicating that updated flight path instructions are available). The WTRU may send the initial flight path report in a third message (e.g., a UE Information Response message (e.g., a WTRU Information Response message).

[0095] The WTRU may monitor conditions (e.g., and associated thresholds) for triggering updated flight path instructions (e.g., trigger conditions and thresholds are available for indicating updated flight path instructions). Conditions for triggering updated flight path instructions may include one or more of the following: distance and / or delay from original reported values ​​exceeding a threshold (e.g., a distance threshold), the number of disabled waypoints and / or timestamps exceeding a threshold (e.g., a waypoint threshold), the number of available waypoints and / or timestamps exceeding a threshold (e.g., the number of available new waypoints and / or timestamps exceeding a threshold), or receipt of a message to initiate collision avoidance (e.g., from the CN).

[0096] If one or more trigger conditions associated with enabling transmission of a flight path update indication are met, the WTRU may transmit an indication that an updated flight path is available. The WTRU may receive a request to transmit updated flight path information. The WTRU may transmit the updated flight path information.

[0097] 5 illustrates an example of a conditional trigger for updated instructions. The trigger condition associated with enabling the transmission of flight path updates may include one or more of the following: a threshold value associated with enabling the transmission of flight path update instructions, a specific value associated with enabling the transmission of flight path update instructions, or a range of values ​​associated with enabling the transmission of flight path update instructions. For a threshold value, the condition may be met if the measured value is above, below, or equal to the threshold value. For a specific value, the condition may be met if the measured value is equal to one or more indicated values. For a range of values, the condition may be met if the measured value is within the range (e.g., in another example, the condition may be met if the measured value is outside the indicated range).

[0098] In an example, a condition for triggering a flight path update report or indication according to any of the examples herein may include a (e.g., additional) time to trigger (TTT) configuration, where the condition may be met for TTT before the WTRU considers the condition met and the update report or indication is triggered. In an example, a conditional flight path update report or change indication configuration may be released and / or deleted after the WTRU triggers a report or update indication based on the configuration. In an example, the WTRU may use the conditional flight path update report or change indication (e.g., until the network instructs the WTRU to release it). In an example, a flight path update report may be sent at a lower priority than other RRC messages (e.g., measurement reports) by sending the report over SRB2.

[0099] Examples of trigger conditions for conditional flight paths being updated or reported are provided herein. The conditions for triggering a flight path update instruction or report may be time-related. For example, a WTRU may be configured to trigger a flight path update instruction or report if the expected / anticipated time (e.g., a previously reported arrival time) for a particular waypoint or set of waypoints differs from the current flight path information (e.g., the arrival time at the waypoint location) by a certain duration (e.g., a time-based threshold). This may be a delay duration (e.g., the WTRU expects to arrive at the waypoint later than the reported time in the flight path that the WTRU previously reported to the network), a pre-arrival duration (e.g., the WTRU expects to arrive at the waypoint earlier than the reported time in the flight path that the WTRU previously reported to the network), or an uncertainty window (e.g., the WTRU expects to arrive at the waypoint earlier or later than the reported time in the flight path that the WTRU previously reported to the network).

[0100] The conditions for triggering a flight path update instruction or report may be distance-related. For example, the WTRU may be configured to trigger a flight path update instruction or report if the predicted / expected waypoint at a particular time differs from the waypoint indicated in the current flight path information by a particular distance (e.g., the distance between the WTRU's position and the previously provided flight path location exceeds a distance threshold). This may be a delay (e.g., the WTRU may expect to be a particular distance behind a waypoint at the time the WTRU indicated it was at that waypoint in flight path information previously reported to the network), a pre-arrival (e.g., the WTRU may expect to be a particular distance further ahead of a waypoint at the time the WTRU indicated it was at that waypoint in flight path information previously reported to the network), or an uncertainty window (e.g., the WTRU may expect to be a particular distance ahead or behind a waypoint at the time the WTRU indicated it was at that waypoint in flight path information previously reported to the network).

[0101] The delay / pre-arrival / uncertainty window time or distance duration / value may refer to all waypoints, a subset of waypoints, or just one specific waypoint.

[0102] The trigger condition for a flight path update instruction or report may be that the number or percentage of waypoints (e.g., disabled waypoints) that the WTRU does not expect to pass (e.g., in current flight path information available in the network) exceed a threshold (e.g., a waypoint threshold). The distance threshold may be configured to determine whether the WTRU can consider a waypoint invalid (e.g., a waypoint may be configured to be invalid if the WTRU does not expect to be within a certain configured radius / distance from the waypoint). The time threshold may be configured to determine whether the WTRU can consider a waypoint invalid (e.g., a waypoint may be configured to be invalid if the WTRU does not expect to be at the waypoint within a certain configured time from the time it is expected to be at that location in (e.g., according to) flight path information available in the network).

[0103] In an example, a WTRU may be configured to send a flight path update instruction or report when it reaches or is near a particular waypoint (e.g., within a particular configured radius of a waypoint). In an example, a WTRU may be configured to send a flight path update instruction or report when it passes a particular number or percentage of waypoints previously indicated in the flight path information. For example, a WTRU may be configured to update a flight path when it has partially traversed a previously indicated flight path. In an example, a WTRU may be configured to send a flight path update instruction or report when it detects that its mobility has changed by a particular threshold. For example, a WTRU may trigger a report or update instruction when its speed / acceleration has changed by more than a particular percentage or absolute value compared to the time the previous flight path information was sent to the network. In an example, an update or update instruction may be triggered when the WTRU changes its mobility state from low mobility to high mobility, where the low and high mobility states may be based on a network-configured speed value range. The change in speed / acceleration / mobility may be axis dependent (e.g., a change in speed in the x, y, or z axis). In an example, the WTRU may be configured to send a flight path update instruction or report if the WTRU detects that its altitude has changed by a certain threshold since the last time flight path information was sent to the network.

[0104] The RAN may obtain information about the WTRU flight path from another entity other than the WTRU (e.g., a CN, an application server, etc.). The network may send the flight path information to the WTRU, and the WTRU may notify the WTRU to send a flight path update instruction or report (e.g., if the WTRU deviates from its current flight path information, according to any of the examples herein). Some of the waypoints in the flight path information may have higher importance than other waypoints. The WTRU may be configured to consider (e.g., only consider) those waypoints when checking for flight path update instruction triggers, or to prioritize conditions associated with those waypoints.

[0105] An example of sending an updated flight path report instead of an update instruction is provided herein, in which the WTRU may send an updated flight path (hereinafter also referred to as a flight path report) (e.g., instead of sending an indication to the network that its flight path information has been updated).

[0106] The WTRU may be configured with at least one set of conditions associated with sending an indication to the network that its flight path has changed, and at least another set of conditions for sending a (e.g., updated) flight path report directly (e.g., without sending an indication to the network and waiting for the network to request it). Different configurations of triggering conditions for a flight path update instruction or report may be uniquely identified (e.g., by an integer value), and the WTRU may include an identification of the configuration and / or condition that triggered the flight path instruction or report in the update instruction or report that the WTRU sends to the network. The WTRU may be configured to send an updated flight path report if the WTRU has sufficient available uplink (UL) grant to send the report. The WTRU may (e.g., simply) send an indication that a flight path update is available (e.g., otherwise).

[0107] Examples of explicit requests for flight path status are provided herein. In an example, the WTRU may periodically report flight path status (e.g., based on configuration and / or in response to an explicit request from the network). The WTRU may send an updated flight path report (e.g., if later requested by the network). In an example, the WTRU may perform one or more of the following:

[0108] The WTRU may send a first message (e.g., an RRC Connection Complete message) indicating that flight path information is available. The WTRU may receive a second message (e.g., a UE Information Request message (e.g., a WTRU Information Request message)) including a flight path reporting configuration requesting flight path information. The flight path reporting configuration (e.g., configuration information) may include at least one of the following: the number of waypoints, whether to include timestamp information, or a configuration for periodically reporting flight path information updates. The configuration for periodicity may include one or more of the following: periodicity, a window and / or resources for reporting updated flight path, or scaling / biasing for changing the periodicity based on the speed / location of the WTRU. The WTRU may send an initial flight path report (e.g., in the third message or a UE Information Response message (e.g., a WTRU Information Response message)).

[0109] With the configured periodicity, the WTRU may evaluate whether the flight path information has changed since the previous flight path report (e.g., the initial flight path report). If the flight path information has changed (e.g., the previous flight path information is invalid or a waypoint (e.g., a new waypoint) is available), the WTRU may send an indication that updated flight path information is available (e.g., via example UE assistance information (e.g., WTRU assistance information)). The WTRU may receive a request to send the updated flight path information. The WTRU may send the updated flight path information. If the flight path information has not changed, the WTRU may send an ACK that there have been no changes since the previous flight path report. If the configured periodicity is a skip opportunity, the WTRU may retroactively indicate that instructions have been skipped in the past (e.g., the past X instructions have been skipped). In an example, the WTRU may apply the above behavior when the network autonomously requests a flight path information update (e.g., without prior transmission of a WTRU update indication).

[0110] FIG. 6 illustrates an example of a periodic or network-requested trigger for flight path status indication. The WTRU may be configured to periodically report the status of the flight path. With the configured periodicity, the WTRU may compare the current flight path to a previously reported flight path. The periodicity configuration may include one or more of the following aspects: periodicity, a window and / or resources for reporting the updated flight path, or scaling / biasing for changing the periodicity based on the WTRU's speed and / or location. For the window and / or resources for reporting the updated flight path, the WTRU may be configured with a configured grant (e.g., periodically coinciding with the periodicity of flight path-related reports). The WTRU may use the resources to send flight path update reports or indications. With regard to scaling / biasing for changing the periodicity based on the WTRU's speed and / or location, the WTRU may scale the reporting periodicity if the WTRU is deemed to be in a high mobility or high velocity state.

[0111] In an example, the WTRU may receive a request from the network to report the status of its flight path information, e.g., via RRC signaling (e.g., a UE Information Request message (e.g., a WTRU Information Request message), etc.). The network may indicate (e.g., in addition to the request) one or more of the following: resources (e.g., an UL grant) to respond to the network request, whether to send an ACK / NACK if nothing has changed or skip the response entirely, or conditions for responding that the flight path has changed (e.g., the WTRU may report that the flight path has changed if it has changed by X% from the previously reported flight path).

[0112] When a periodic trigger is reached (e.g., or when a network request is received), the WTRU may compare the current status of the flight path with the last reported flight path. In an example, the WTRU may not send a flight path status if the flight path information has not changed. In an example, the flight path status may be a simple indication (e.g., yes or no, ACK or NACK) that may indicate whether the flight path information has changed. In an example, the WTRU may send an indication if the flight path has not changed. In an example, the WTRU may send an updated flight path if the flight path has changed. If the WTRU is configured with configured grant opportunities for reporting status updates, the WTRU may decide to send a status indication or a full report based on the size of the configured grant available at that time.

[0113] If the WTRU deprioritizes sending a flight path status or flight path update report (e.g., due to other high priority data or the current flight path not being changed), the WTRU may send the flight path status or flight path update report whenever UL resources become available later, or may skip completely until the next reporting period. If the WTRU skips an opportunity, the WTRU may retroactively indicate that one or more instructions were skipped the next time the WTRU sends an ACK / update indication.

[0114] The WTRU may be configured to deprioritize sending flight path status or flight path reports (e.g., even if a configured grant is available) if there is high priority data to be sent (e.g., via a measurement report). For example, this may be achieved by associating the flight path report with SRB2.

[0115] Examples of partial and / or delta updated flight path reports are provided herein. The WTRU may report partial and / or delta information to convey an updated flight path report (e.g., if requested by the network). The WTRU may do one or more of the following:

[0116] The WTRU may send a first message (e.g., an RRC Connection Complete message) indicating that flight path information is available. The WTRU may receive a second message (e.g., a UE Information Request message (e.g., a WTRU Information Request message)) including a flight path reporting configuration requesting flight path information. The WTRU may send an initial flight path report in a third message (e.g., a UE Information Response message (e.g., a WTRU Information Response message)). The WTRU may detect that a previously reported flight path (e.g., the initial flight path) requires an update (e.g., based on information associated with changing from the previous flight path to the updated flight path).

[0117] The WTRU may transmit an indication that an updated flight path is available. The indication may include information (e.g., additional details) about differences associated with changing from a previous flight path report to the updated flight path report. The information may include a flag indicating that an updated flight is available, a flag indicating that time information is invalid, a flag indicating that waypoint information is invalid, the number of invalid times and / or waypoints, or the number of available timestamps and / or waypoints (e.g., the number of new timestamps and / or waypoints available).

[0118] The WTRU may receive a request for partial and / or delta flight path information. The WTRU may transmit the updated partial and / or flight path information. The updated partial and / or flight path information may include one or more of the following: a flag to report delta signaling (e.g., reporting waypoint and delta information from the initial flight path report), a flag to report available waypoint / timestamp information (e.g., available new waypoint / timestamp information), a flag to report waypoints or timestamps, a flag to report information that has become invalid, or a flag to report information that has become invalid due to a threshold. The WTRU may receive an ACK that the partial and / or delta flight path information has been received.

[0119] 7 illustrates an example of a partial and / or delta update instruction. If the WTRU detects that the flight path is invalid (e.g., based on satisfaction of one or more conditions listed in the examples herein), the WTRU may send an indication that the flight path information has changed. The network may request the WTRU to send the entire route information or delta information including the changes (e.g., only the changes). The network may request delta route information for one or more waypoints. For example, the network may include in the request one or more waypoint indices (e.g., a list of indices, a range of indices, etc.), one or more timestamps or timestamp ranges (e.g., which may be interpreted by the WTRU to mean that the network requests an update of waypoints previously indicated to be reached in the indicated timestamp range or waypoints currently expected by the WTRU to be reached in the indicated timestamp range), waypoints that are expected to change in distance by a certain distance from waypoints indicated in the current route information, waypoints that are expected to arrive by a time that differs by more than a certain threshold from the timestamps indicated by the current flight information, or waypoints that are considered invalid (e.g., that the WTRU may not expect to pass any further).

[0120] If the WTRU determines that the flight path information has changed, it may send the delta information directly to the network (e.g., instead of sending an instruction and then waiting for the network to request the delta information). The WTRU's flight path report / information may include a waypoint index / identification, as well as corresponding waypoint coordinates and optional timestamp information (e.g., when the WTRU can be expected to be at that waypoint). The WTRU may send an instruction to the network that includes (e.g., includes only) the waypoint index / identification, updated waypoint coordinates, and / or updated timestamp. An example is shown in Table 1 below.

[0121] [Table 1]

[0122] If the WTRU determines that information about a particular waypoint has changed, the WTRU may send delta information (e.g., in a structure similar to the AddMod List used by the RRC message). For example, the structure in Table 2 below may be used to indicate to the network the change in coordinates for waypoint 2, the change in timestamp for waypoint 3, and the change in coordinates and timestamp for waypoint n.

[0123] [Table 2]

[0124] In examples, the waypoint coordinates or timestamp values ​​indicated in a delta flight path update may be absolute values. In examples, the waypoint coordinates or timestamp values ​​indicated in a delta flight path update may be relative to the previous value of the indicated waypoint (e.g., the network may add / subtract the indicated value from the previous value of the associated waypoint to obtain the waypoint coordinates or timestamp).

[0125] The delta information sent for a given waypoint may be applicable to the waypoint (e.g., all subsequent waypoints thereafter), and the WTRU may include such an indication in the waypoint indication. For example, the WTRU may explicitly indicate that the delta information is propagating (e.g., as shown in Table 3 below).

[0126] [Table 3]

[0127] When a delta update is received, the network may assume that the coordinates of waypoints with an index of 10 or greater (e.g., all waypoints) are updated by (w2_new-w2_old), and that the timestamps of waypoints with an index of 13 or greater (e.g., all waypoints) are updated by (t3_new-t3_old). The propagation instructions may be at the message level (e.g., as shown in the examples herein) or at the waypoint level. An example at the waypoint level is shown in Table 4 below.

[0128] [Table 4]

[0129] In the example, the absence of a propagation indication may be interpreted as a NO indication (e.g., that the delta update may only be applicable to the relevant waypoint). In the example, the absence of a propagation indication may be interpreted as a YES indication (e.g., that the delta update may be applicable to all subsequent waypoints).

[0130] A delta update may include information about waypoints to be removed from the flight path. For example, WayPointToReleaseList=index:10, 13, 15 may indicate to the network that waypoints 10, 13, and 15 are not valid (e.g., no longer valid) and may be removed.

[0131] The release of a waypoint may be propagative (e.g., similar to the modification of a waypoint) or non-propagative. For example, the deletion of waypoint 13 may be interpreted by the network as meaning that waypoints with index 13 or greater (e.g., all waypoints) should be deleted from the flight path information. In an example, when a waypoint is deleted, the indexes of other waypoints may not be affected. In an example, when a waypoint is deleted, the indexes of waypoints with indexes above this waypoint may be decreased by 1 to accommodate the change. For example, if a WTRU has three waypoints in a flight path and the WTRU sends an instruction that waypoint #2 should be released, the old waypoint #3 may take on an index value of 2.

[0132] To prevent cascading errors (e.g., additional errors) (e.g., due to erroneously received delta signaling) and to ensure proper alignment between the WTRU and the network regarding the current status of the flight path, the WTRU may receive an ACK from the network that the partial and / or delta flight path information has been successfully received. If the WTRU does not receive such an ACK (e.g., within a period of time after the delta flight path report), the WTRU may send (e.g., another) flight path report containing the full values.

[0133] Examples of pre-configured fallback waypoints and / or flight paths are provided herein. The WTRU may fall back to an alternative pre-configured flight path and / or waypoint. The WTRU may do one or more of the following:

[0134] The WTRU may send a first message (e.g., an RRC Connection Complete message) indicating that flight path information is available. The WTRU may receive a second message (e.g., a UE Information Request message (e.g., a WTRU Information Request message)) including flight path information and a flight path reporting configuration requesting candidate fallback waypoints or an updated flight path (e.g., additional candidate fallback waypoints or an updated flight path). The WTRU may send an initial flight path report in a third message. The WTRU may detect whether a previously reported flight path (e.g., the initial flight path) is invalid.

[0135] The WTRU may evaluate the candidate fallback waypoints and / or updated flight paths to determine whether one or more are suitable replacement routes. In an example, if suitable candidates are found, the WTRU may apply one or more fallback waypoints and / or updated flight paths. The WTRU may notify the network that the (e.g., pre-configured) fallback waypoints and / or updated flight paths have been applied.

[0136] In an example, the WTRU may indicate (e.g., by sending an index) which waypoints and / or updated flight paths have been updated. In an example, if a suitable candidate is found, the WTRU may send a request to confirm whether the WTRU can apply the (e.g., pre-configured) fallback waypoints and / or updated flight paths. The WTRU may receive a response regarding approval of the candidate fallback waypoints or updated flight paths. If the candidate is approved, the WTRU may acknowledge the approval and apply one or more of the fallback waypoints or updated flight paths. If the candidate is rejected, the WTRU may perform an autonomous update procedure. If no suitable candidate is found, the WTRU may perform an autonomous flight path update and notify the network.

[0137] 8 illustrates an example of a preconfigured fallback. A WTRU / UAV may be configured with at least one candidate flight path or waypoint. Without loss of generality, one of the at least one candidate flight path may be a flight path that the WTRU / UAV is currently following. Such a flight path may be referred to as a current or initial flight path. The remaining flight path of the at least one candidate flight path may be referred to as a fallback flight path.

[0138] The WTRU may send the initial flight path and at least one fallback flight path in at least one of the following: in an RRC Connection Complete message or in a UE Information Response message (e.g., a WTRU Information Response message) (e.g., as part of a UE Information Request (e.g., WTRU Information Request) procedure). The flight paths (e.g., each flight path) may be identified by flight path identification information. The WTRU may determine a priority level for the flight path (e.g., each flight path) based on at least one of the following: a flight path that minimizes the distance between the WTRU's actual location and the nearest point on the flight path, a flight path that minimizes the travel time or distance to the destination, or an explicit priority indication from the network.

[0139] In an example, the WTRU may receive an explicit priority indication for a flight path (e.g., each flight path) from the network (e.g., after transmission of the initial flight path and the fallback flight path). In an example, the WTRU may receive an explicit priority indication in response to a request to modify the current flight path to the fallback flight path.

[0140] The WTRU may notify the network that the current flight path will be changed to a fallback flight path. The WTRU may evaluate the validity of the fallback flight paths (e.g., according to the conditions described in the examples herein). If at least one fallback flight path is valid, the WTRU may select one of the fallback flight paths and update the current flight path to this fallback flight path. If the fallback flight path is not valid, the WTRU may autonomously determine an alternative (e.g., not previously shown) or default flight path.

[0141] The WTRU may send an instruction to the network to change the flight path to one of the fallback or default flight paths (e.g., using the flight path identification information), or may provide a previous flight path that was not indicated (e.g., if the fallback flight path is not valid). Such an instruction may be included in an RRC message (e.g., a measurement report, or a type of message specific to this purpose (e.g., a new type of message)). The WTRU may apply (e.g., then apply) the flight path change.

[0142] The WTRU may send a request to the network to change the flight path to one of the fallback flight paths. The WTRU may include an identification of the proposed fallback flight path in the request. The WTRU may (e.g., then receive) a response from the network. If the response indicates confirmation of the fallback flight path, the WTRU may change the current flight path to the fallback flight path. If the response indicates rejection of the proposed fallback flight path, the WTRU may apply a default flight path or an alternative (e.g., not previously signaled) flight path. The response may (e.g., also indicate) a set of possible fallback flight paths with a priority indication. The WTRU (e.g., in such a case) may select one of the fallback flight paths that is valid (e.g., the highest priority) and change the current flight path to this fallback flight path. The WTRU may (e.g., then transmit) a notification to the network including the selected fallback flight path.

[0143] Examples of network-directed fallback waypoints and / or flight paths are provided herein. The WTRU may request an updated flight path, waypoint, and / or set of waypoints from the network. The WTRU may do one or more of the following:

[0144] The WTRU may send a first message (e.g., an RRC connection complete message) indicating that flight path information is available. The WTRU may receive a second message (e.g., a UE information request message (e.g., a WTRU information request message)) including a flight path reporting configuration requesting flight path information. The WTRU may send an initial flight path report (e.g., in a third message). The WTRU may detect that the initial flight path is invalid and notify the network. The WTRU may indicate a set of waypoints that are no longer valid and may be alternatives (e.g., may require). The WTRU may monitor network indication of updated fallback waypoints and / or flight paths to apply. In an example, the WTRU may monitor a fixed duration for network duration.

[0145] If the WTRU receives the fallback waypoint and / or flight path, the WTRU may update the currently maintained flight path (e.g., the initial flight path). The WTRU may send an ACK to the network that the updated flight path has been applied. If the WTRU does not receive the fallback waypoint or flight path (e.g., in time), the WTRU may perform an autonomous flight path correction and send a flight path update instruction to the network.

[0146] 9 illustrates an example request for an alternative flight path. The WTRU may have the network determine a fallback route or waypoint location. This may be useful, for example, to allow the network to direct the WTRU to an area that is less congested by other WTRUs or to aid in network-side load balancing (e.g., by physically directing the WTRU to a different location).

[0147] If the WTRU detects that the current flight path is no longer valid (e.g., based on satisfaction of one or more conditions listed in the examples herein), the WTRU may notify the network. This notification may include (e.g., may additionally include) a request for updated waypoint and / or flight path information from the network. The WTRU may remain stationary in the air (e.g., while waiting for a network response).

[0148] The WTRU may monitor the network response for a given period of time (which may begin, for example, when an instruction / request is received). If the WTRU receives an instruction within the period containing alternative fallback flight path information and / or waypoints, the WTRU may adjust its flight path accordingly. If a flight path adjustment is performed, the WTRU may send an ACK to the network to notify that the flight path has been successfully updated. If a flight path update is performed, the WTRU may send an updated flight path report. The WTRU may receive the updated flight path and / or waypoints via one or more of the following: RRC signaling, MAC CE, or DCI.

[0149] If the WTRU does not receive the alternative flight path and / or waypoints, if it receives a negative acknowledgment (NACK) or rejection of the request, or if it does not receive the alternative flight path and / or waypoints within an indicated period of time, the WTRU may perform an autonomous flight path correction. If (e.g., when) an autonomous flight path correction is applied, the WTRU may notify the network (e.g., via a flight path update notification) or may send an updated flight path report directly.

[0150] Examples of inhibit conditions for triggering flight path instructions are provided herein. A inhibit timer may be configured to control the WTRU from sending two consecutive flight path update reports or instructions within a given time period (e.g., the WTRU may refrain from sending a second flight path update report or instruction after sending a first flight path update or report for the configured inhibit timer duration). This timer may be started when a flight path report is transmitted and / or when a flight path update is indicated. The inhibit timer may be overridden, for example, based on a network request or subject to some condition (e.g., more than X waypoints have become invalid).

[0151] Although the features and elements described above are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or may be used in various combinations with or without the other features and elements.

[0152] While the implementations described herein may consider 3GPP-specific protocols, it will be understood that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, while the solutions described herein consider LTE, LTE-A, new radio (NR), or 5G-specific protocols, it will be understood that the solutions described herein are not limited to this scenario and may be applicable to other wireless systems.

[0153] The processes described above may be implemented in a computer program, software, and / or firmware embodied in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact discs (CD-ROM) disks and / or digital versatile discs (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, a terminal, a base station, a radio network controller (RNC), and / or any host computer.

Claims

1. 1. A wireless transmit / receive unit (WTRU), comprising: a processor, the processor comprising: receiving configuration information via a radio resource control (RRC) reconfiguration message, the configuration information indicating a threshold associated with enabling transmission of a flight path update indication; determining that the threshold associated with enabling transmission of the flight path update instructions is met; A wireless transmit / receive unit (WTRU) configured to transmit the flight path update indication via a user equipment (UE) assistance information message or RRC signaling based on the threshold being met.

2. 2. The WTRU of claim 1, wherein the threshold is a distance threshold, and the distance threshold associated with enabling the transmission of the flight path update instruction is met based on the distance between the WTRU's position and a previously provided flight path location exceeding the distance threshold.

3. 2. The WTRU of claim 1, wherein the threshold is a time-based threshold, and the time-based threshold associated with enabling transmission of the flight path update instruction is met based on an arrival time at a waypoint location exceeding a previously reported arrival time by the time-based threshold.

4. 2. The WTRU of claim 1, wherein the threshold is a waypoint threshold, and the waypoint threshold associated with enabling transmission of the flight path update instruction is met based on a number of disabled waypoints exceeding the waypoint threshold.

5. The processor: receiving a request to transmit updated flight path information; The WTRU of claim 1 , further configured to transmit the updated flight path information.

6. 1. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: receiving configuration information via a radio resource control (RRC) reconfiguration message, the configuration information indicating a threshold associated with enabling transmission of a flight path update indication; determining that the threshold associated with enabling transmission of the flight path update instructions is met; and and transmitting the flight path update indication via a user equipment (UE) assistance information message or RRC signaling based on the threshold being met.

7. 7. The method of claim 6, wherein the threshold is a distance threshold, and the distance threshold associated with enabling transmission of the flight path update instruction is met based on a distance between the WTRU's position and a previously provided flight path location exceeding the distance threshold.

8. 7. The method of claim 6, wherein the threshold is a time-based threshold, and the time-based threshold associated with enabling transmission of the flight path update instruction is met based on an arrival time at a waypoint location exceeding a previously reported arrival time by the time-based threshold.

9. 7. The method of claim 6, wherein the threshold is a waypoint threshold, and the waypoint threshold associated with enabling transmission of the flight path update instruction is met based on a number of disabled waypoints exceeding the waypoint threshold.

10. receiving a request to transmit updated flight path information; The method of claim 6 , further comprising: transmitting the updated flight path information.

Images