Unmanned aerial vehicle conditions updated based on WTRU LTM candidate set

Abstract

An example device may receive configuration information indicating a first layer one / two triggered mobility (LTM) procedure associated with a first cell, a first geographically related condition associated with the first LTM procedure, a second LTM procedure associated with a second cell, and a second geographically related condition associated with the second LTM procedure. The device may determine that a first geographically relevant condition is satisfied. Based on a first geographically relevant condition being satisfied, the device may perform the first LTM procedure by using or measuring a first cell. The device may determine that the second geographically relevant condition is satisfied. Based on a second geographically relevant condition being satisfied, the device may perform the second LTM procedure by using or measuring a second cell.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 445,430, filed February 14, 2023, the contents of which are incorporated herein by reference. Background Art

[0003] Mobile communications using wireless communications continue to develop. The fifth generation may be referred to as 5G. Previous (legacy) generations of mobile communications may be, for example, fourth generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0004] For example, a Layer 1 / Layer 2 (L1 / 2) Triggered Mobility (LTM) candidate set may be selected for an Unmanned Aerial Vehicle (UAV) process based on LTM factors such as altitude, speed, or waypoint conditions.

[0005] For example, a device (e.g., a wireless transmit / receive unit (WTRU), such as a UAV) may include a processor configured to receive configuration information indicating a first LTM process, a first geo-related condition associated with the first LTM process, a second LTM process, and a second geo-related condition associated with the second LTM process, wherein the first LTM process is associated with a first cell and the second LTM process is associated with a second cell. The device may determine that the first geo-related condition is satisfied. Based on satisfying the first geo-related condition, the device may execute the first LTM process. Executing the first LTM process may include using or measuring the first cell. The device may determine that the second geo-related condition is satisfied. Based on satisfying the second geo-related condition, the device may execute the second LTM process. Executing the second LTM process may include using or measuring the second cell.

[0006] The first geography-related condition may be a first altitude condition associated with the altitude at which the WTRU is located, a first speed condition associated with the speed at which the WTRU is moving, or a first waypoint condition associated with a first waypoint in the WTRU's flight path location. The second geography-related condition may be a second altitude condition associated with the altitude at which the WTRU is located, a second speed condition associated with the speed at which the WTRU is moving, or a second waypoint condition associated with a second waypoint in the WTRU's flight path location.

[0007] Determining that the first geography-related condition is satisfied may include determining that the WTRU's altitude is below an altitude threshold.Determining that the second geography-related condition is satisfied may include determining that the WTRU's altitude is above an altitude threshold.

[0008] Determining that the first geography-related condition is satisfied may include determining that a speed of the WTRU is below a speed threshold.Determining that the second geography-related condition is satisfied may include determining that a speed of the WTRU is above the speed threshold.

[0009] Determining that the first geography-related condition is satisfied may include determining that the WTRU has arrived at a first waypoint.Determining that the second geography-related condition is satisfied may include determining that the WTRU has arrived at a second waypoint.

[0010] The configuration information may indicate a first candidate cell set and a second candidate cell set. The device may select a first cell from the first candidate cell set and a second cell from the second candidate cell set.

[0011] Executing the second LTM procedure may involve ceasing execution of the first LTM procedure; and sending an indication to a network entity that the second cell is in use.

[0012] Performing the first LTM procedure may include sending a first indication of information associated with a first cell to a network entity (e.g., indicating that the first cell is in use). Performing the second LTM procedure may include sending a second indication to the network entity, the second indication indicating information associated with the second cell (e.g., indicating that the second cell is in use). At least one of the first indication and the second indication may be sent via a medium access control (MAC) control element (MACCE), a radio resource control (RRC) message, uplink control information (UCI), or a channel state information (CSI) report. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0014] Figure 1B is a system diagram according to an embodiment, which shows that Figure 1A An exemplary wireless transmit / receive unit (WTRU) for use in the illustrated communication system;

[0015] Figure 1C It is shown that according to the embodiment, Figure 1A A system diagram of an example radio access network (RAN) and an example core network (CN) used within the communication system shown in FIG;

[0016] Figure 1D It is shown that according to the embodiment, Figure 1A A system diagram of another example RAN and another example CN used within the communication system shown in FIG;

[0017] Figure 2Illustrate an example of a measurement model.

[0018] Figure 3 An example of an LTM is shown.

[0019] Figure 4 An example of an LTM process is shown.

[0020] Figure 5 An example of the signaling flow for flight path reporting in an LTE UAV is shown.

[0021] Figure 6 An example of the initial flight path reporting process is shown.

[0022] Figure 7 An exemplary use case utilizing known waypoints associated with a set of LTM candidate configurations (eg, or cells) is shown.

[0023] Figure 8 An example process is shown that utilizes waypoints or altitude or speed thresholds associated with a set of different LTM candidate configurations (eg, or cells).

[0024] Figure 9 Exemplary use cases utilizing waypoints, altitude, and / or speed thresholds associated with different types of mobility are shown.

[0025] Figure 10 Example processes are shown that utilize waypoint, altitude, and / or speed thresholds associated with different types of mobility.

[0026] Figure 11 An example process for fast candidate set update using network (NW) control is shown.

[0027] Figure 12 An example of signaling to perform this process using NW controlled fast candidate set update is shown. DETAILED DESCRIPTION

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

[0029] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d 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), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or MiFi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

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

[0031] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage to a specific 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 base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, one for each sector of the cell. In an embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

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

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

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

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

[0036] 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 implement both LTE and NR radio access, for example, using dual connectivity (DC) principles. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions to and from multiple types of base stations, such as eNBs and gNBs.

[0037] In other embodiments, the base station 114a and the WTRUs 102a, 102b, and 102c may implement wireless technologies 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, Internet Standard 2000 (IS-2000), Internet Standard 95 (IS-95), Internet Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0038] Figure 1A The base station 114B in the may be, for example, a wireless router, a home Node-B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may 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-A Pro, NR, etc.) to establish a picocell or a femtocell. Figure 1A As shown, base station 114b may have a direct connection to the Internet 110. Thus, base station 114b may not need to access the Internet 110 via CN 106 / 115.

[0039] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Data may have varying quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although in Figure 1AAlthough not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT 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 be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

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

[0043] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) 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. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0044] The transmit / receive element 122 may be configured to transmit signals to or receive signals 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, UV, or visible light signals. In another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It should be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

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

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

[0047] The processor 118 of the WTRU 102 may be coupled to and receive user input 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. Furthermore, the processor 118 may access information from and store data in any suitable type of 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, or the like. 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 a home computer (not shown).

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

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

[0050] The processor 118 may also be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (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, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0051] The WTRU 102 may include a full-duplex radio device for which the transmission and reception of some or all signals (e.g., signals associated with particular subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous.

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

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

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

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

[0056] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial contact of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also 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.

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

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

[0059] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication 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.

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

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

[0062] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic entering and / or leaving the BSS. Traffic originating from outside the BSS and destined for a STA may reach through the AP and be delivered to the STA. Traffic from a STA destined for a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Traffic between STAs within a BSS may be sent through the AP, for example, where a source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between a source STA and a destination STA (e.g., directly between the source and destination STAs) using 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 (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

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

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

[0065] Very high throughput (VHT) STAs can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining adjacent 20MHz channels. A 160MHz channel can be formed by combining 8 consecutive 20MHz channels or by combining two non-contiguous 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a fragment parser that can divide the data into two streams. Each stream can be subjected to inverse fast Fourier transform (IFFT) processing and time domain processing respectively. The stream can be mapped onto two 80MHz channels, and the data can be sent by the transmitting STA. At the receiver of the receiving STA, the operation of the above-mentioned 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

[0066] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah relative to the channel operating bandwidth and carrier 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 a representative embodiment, 802.11ah may support meter type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, for example, limited capabilities including support for certain and / or limited bandwidths (e.g., only support). MTC devices may include batteries with a battery life above a threshold (e.g., to maintain very long battery life).

[0067] 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 set and / or limited by the STA among all STAs operating in the BSS, which supports the minimum bandwidth operating mode. In the example of 802.11ah, for a STA that supports (e.g., only supports) 1 MHz mode (e.g., an MTC-type device), the primary channel can be 1 MHz wide, 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) settings can depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which only supports 1 MHz operating mode) transmitting to the AP, the entire available frequency band can be considered busy even if most of the frequency band remains idle and available.

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

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

[0070] The RAN 113 may include gNBs 180a, 180b, and 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. Each of the gNBs 180a, 180b, and 180c includes one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, and 180c may implement MIMO technology. For example, the gNBs 180a and 180b may utilize beamforming to transmit and / or receive signals to and from the gNBs 180a, 180b, and 180c. Thus, the gNB 180a may, for example, use multiple antennas to transmit and / or receive wireless signals to and from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers (not shown) to the WTRU 102a. 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, and 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0071] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable digital architecture. 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 varying or scalable lengths (e.g., containing a varying number of OFDM symbols and / or a continuously varying absolute time length).

[0072] 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 also accessing other RANs (e.g., the eNode-Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNBs 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-Bs 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 eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may serve 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.

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

[0074] Figure 1DThe CN 115 shown in FIG may include at least one AMF 182 a, 182 b, at least one UPF 184 a, 184 b, at least one session management function (SMF) 183 a, 183 b, and possibly a data network (DN) 185 a, 185 b. While each of the aforementioned 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.

[0075] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act 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 specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, and the like. The AMF 182a, 182b may use network slicing to customize CN support for the WTRUs 102a, 102b, 102c based on the types of services being used by 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, and the like. 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 (e.g., LTE, LTE-A Pro, and / or non-3GPP access technologies such as WiFi).

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

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

[0078] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) or may communicate with an IP gateway that serves as an interface between the CN 115 and the PSTN 108. Furthermore, 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 connect to local data networks (DNs) 185a, 185b through 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.

[0079] Given that Figures 1A-1D and Figures 1A-1D

[0015] In accordance with the descriptions herein, one or more or all of the functionality described herein with respect to one or more of the following: the WTRUs 102a-102d, base stations 114a-114b, eNode-Bs 160a-160c, MME 162, SGW 164, PGW 166, gNBs 180a-180c, AMFs 182a-182b, UPFs 184a-184b, SMFs 183a-183b, DNs 185a-185b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more or all of the functionality described herein. For example, the emulation device may be used to test other devices and / or simulate network and / or WTRU functionality.

[0080] The simulation device can be designed to implement one or more tests of other devices in a laboratory environment and / or in a carrier network environment. For example, one or more simulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device can be directly connected to another device for testing purposes and / or can perform tests using over-the-air wireless communications.

[0081] One or more simulation devices can perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to enable testing of one or more components. The one or more simulation devices can be test devices. The simulation device can use direct RF connection and / or wireless communication via RF circuitry (e.g., which can include one or more antennas) to send and / or receive data.

[0082] In the connected state (e.g., RRC_CONNECTED), the WTRU may measure one or more beams (e.g., multiple beams) of a cell. The measurement results (e.g., power values) may be averaged to derive the cell quality. The WTRU may (e.g., be configured to) consider a subset of the detected beams. Filtering may be performed at multiple (e.g., two) different levels (e.g., at the physical layer to obtain beam quality and at the RRC level to obtain cell quality from multiple beams). The cell quality of the serving cell and the non-serving cell may be derived (e.g., in the same way) from the beam measurements. The measurement report may include measurement results for the X best beams (e.g., if the WTRU is configured to do so by the gNB).

[0083] Figure 2An example measurement model is described. Inter-cell L1 / L2 triggered mobility (LTM) may be implemented. Inter-cell beam management may be used to manage beams (e.g., managing beams in carrier aggregation (CA)). Cell changes / additions may or may not be supported. L1 / L2 based inter-cell mobility may be implemented to reduce mobility delays. Configuration and maintenance may be provided for multiple candidate cells to allow rapid application of the configuration of candidate cells (e.g., in RAN2, RAN3). Dynamic switching between candidate serving cells (e.g., including SpCells and SCells) may be provided for applicable scenarios based on L1 / L2 signaling (e.g., in RAN2, RAN1). L1 enhancements may be provided for inter-cell beam management (e.g., including L1 measurements and reporting) and beam indication (e.g., in RAN1, RAN2). Timing advance management may be provided (e.g., in RAN1, RAN2). Centralized unit-distributed unit (CU-DU) interface signaling may be provided to support L1 / L2 mobility (e.g., in RAN3). L1 / L2-based inter-cell mobility can be applicable to one or more of the following scenarios: independent (e.g., CA and NR-DC cases, where the serving cell changes within a cell group (CG)); intra-DU case and intra-CU inter-DU case (e.g., applicable to independent and CA); intra-frequency and inter-frequency cases; frequency range (FR) (e.g., FR1 and FR2); source cell and target cell (e.g., synchronized or asynchronous); and / or inter-CU case.

[0084] L1 / L2 based mobility and inter-cell beam management can handle intra-DU and intra-frequency scenarios. The serving cell can remain unchanged (e.g., if there is no possibility of changing the serving cell using L1 / L2 based mobility). In FR2 deployments, CA can be used to utilize the available bandwidth (e.g., aggregating multiple control channels (CCs) in (one) frequency band). The CCs can transmit in the same analog beam pair (e.g., gNB beam and WTRU beam). The WTRU can be configured with a transmission configuration index (TCI) state (e.g., 64 TCI states) for receiving the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). (Each) TCI state may include a reference signal (RS) or synchronization signal block (SSB) to which the WTRU refers to set its beam. The SSB may be associated with a non-serving physical cell identity (PCI). Medium Access Control (MAC) signaling (e.g., "TCI state indication for WTRU-specific PDCCH MAC CE") may activate the TCI state for a control resource set (CORESET) and / or PDCCH. A MAC CE indicating a TCI state associated with a non-serving PCI may support reception of PDCCH from a non-serving cell. MAC signaling (e.g., "TCI state activation / deactivation for WTRU-specific PDSCH") may activate a subset of TCI states (e.g., up to 8) for PDSCH reception. Downlink Control Information (DCI) may indicate which of the TCI states (e.g., 8). For example, in the absence of multiple transmit / receive points (multi-TRPs), a "unified TCI state" may be supported by different update mechanisms (e.g., based on DCI). Unified TCI state with multiple TRPs may be supported.

[0085] LTM may improve handover latency. The WTRU may (e.g., first) send measurement reports using RRC signaling for (e.g., conventional or conditional) L3 handover. The network may provide further measurement configuration and / or conditional handover configuration. After the WTRU reports using RRC signaling that the cell meets the configured radio quality criteria, the network may (e.g., for conventional handover) provide the configuration for the target cell. The network may (e.g., for conditional handover (CHO)) provide (e.g., pre-provision) the target cell configuration and / or measurement criteria that determines whether the WTRU should trigger the CHO configuration, e.g., to reduce the handover failure rate due to delays in sending measurement reports before receiving the RRC reconfiguration. These conventional and conditional L3 handovers may suffer from delays due to sending measurement reports and receiving the target configuration (e.g., particularly in the case of conventional (unconditional) handovers).

[0086] LTM can allow for rapid application of candidate cell configuration (e.g., including dynamic switching between SCells and PCell switching, e.g., switching roles between SCells and PCells) without performing RRC signaling. Inter-CU cases can involve relocation of the Packet Data Convergence Protocol (PDCP) anchor. RRC-based methods can support inter-CU handovers.

[0087] Before the WTRU moves to complete the handover to the target cell in the new site coverage area, the active (e.g., currently active) SCell may be released. After a successful handover, the active (e.g., currently active) SCell may be added back, which may result in a decrease in throughput during the handover. L1 / L2 may enable CA operation immediately upon serving cell change.

[0088] Figure 3 An example of LTM operation is shown. The candidate cell group can be configured by RRC. Dynamic switching between PCell and SCell can be achieved using L1 / 2 signaling.

[0089] Figure 4 An example of LTM is shown. Figure 4 As shown, at 1, the WTRU may send a MeasurementReport message to the gNB. The gNB may (e.g., decide) to use LTM and start LTM candidate preparation.

[0090] At 2, the gNB may transmit an RRCReConfiguration message to the WTRU. The RRCReConfiguration message may include the configuration of one or more LTM candidate target cells.

[0091] At 3, the WTRU may store the configuration of the LTM candidate target cell. The WTRU may transmit an RRCReconComponationComplete message to the gNB.

[0092] At 4, the WTRU may perform DL synchronization and TA acquisition with the candidate target cell (e.g., before receiving the LTM cell handover command). DL synchronization for the candidate cell may be supported before the cell handover command (e.g., based on at least the SSB). TA acquisition of the candidate cell(s) may be supported before the LTM cell handover command (e.g., based on at least the RACH commanded by the PDCCH). The PDCCH command may be triggered by the source cell.

[0093] At 5, the WTRU may perform L1 measurements on the configured LTM candidate target cells. The WTRU may transmit lower layer measurement reports to the gNB. The lower layer measurement reports may be carried on L1 or MAC.

[0094] At step 6, the gNB may decide to perform an LTM cell handover to the target cell. The gNB may transmit a MAC CE triggering the LTM cell handover, for example, by including a candidate configuration index of the target cell. The WTRU may switch to the configuration of the LTM candidate target cell.

[0095] At 7, the WTRU may perform a random access procedure to the target cell (eg, if the TA is not available).

[0096] The WTRU may indicate successful completion of the LTM cell handover to the target cell at 8. An uplink signal or message after the WTRU has switched to the target cell may be used to indicate successful completion of the LTM cell handover.

[0097] Unmanned aerial vehicles (UAVs) can be supported (e.g., in LTE) (e.g., traveling at altitudes up to 300 m). Use cases may include drone operations, personal entertainment for the in-flight experience, and cargo delivery. Applications may support remote control and data transmission capabilities (e.g., including UL and DL interference and mobility).

[0098] Measurement reporting can be based on a configured altitude threshold. In LTE, an airborne WTRU can support altitude-triggered measurement reporting based on the WTRU's capabilities. For example, two altitude-based events can be defined: event H1, when the airborne WTRU's altitude becomes above an absolute threshold; and event H2, when the airborne WTRU's altitude becomes below an absolute threshold.

[0099] The altitude threshold may be configured in MeasConfig via the altitude thresholdRef. The altitude threshold may support values ​​ranging from -420 m to 8880 m (e.g., in increments of 300 m). The WTRU may be configured in ReportConfigEUTRA with offsets, such as h1-ThresholdOffset and h2-ThresholdOffset, and / or hysteresis parameters, such as h1-hysteresis and h2-hysteresis, which may be applied during event evaluation.

[0100] WTRU altitude, position, and / or velocity may be reported. The WTRU may be configured to include additional information (e.g., WTRU altitude, position, and / or horizontal / vertical velocity) in the measurement report. Location reporting in LTE may be supported via the LocationInfo information element (IE), which may be used to convey location information available at the WTRU (e.g., detailed location information) to correlate measurements with WTRU location information. The available information may include WTRU location information (e.g., via locationCoordinates) and / or WTRU orientation and horizontal velocity (e.g., via horizontalVelocity).

[0101] LTE UAV features may involve reporting vertical information (e.g., via verticalVelocityInfo). VerticalVelocityInfo may include a choice between the parameter verticalVelocity, which may include the WTRU's orientation, horizontal / vertical velocity, and / or vertical direction, and verticalVelocityAndUrtainty, which may include information within the uncertainty of verticalVelocity and / or horizontal and vertical velocity.

[0102] Feature(s) associated with flight path reporting are provided herein. In LTE, flight path reporting of an airborne WTRU may be supported based on WTRU capabilities. The flight path information may include multiple waypoints, which may be 3D locations. The WTRU may indicate whether flight path information is available, for example, via RRCConnectionReconfigurationComplete, RRCConnectionReeastatusMessComplete, RRCConnectionResumComplete, and / or RRCConnectionSetupComplee messages. The flight path information may allow the network to know (e.g., immediately after connection) whether flight path information is available, thereby enabling subsequent flight path reporting configuration and request.

[0103] The E-UTRAN may be used to request the WTRU to report flight path information (e.g., via the FlightPathInfoReq in the UEInformationRequest message). When requesting the reporting of the WTRU flight path information, the WTRU may include a FlightPathInfoReport in the UEInformationResponseMessage, for example, including available waypoints (e.g., up to a configured maximum). The flight path information is useful to the network, for example, for collision avoidance, resource provisioning, and / or WTRU configuration. LTE may support configuration of up to 20 waypoint locations within a flight path report. RAN2 may confirm that a maximum of 20 waypoint locations is sufficient for NR use cases.

[0104] Figure 5 An example of the signaling flow for flight path reporting in an LTE UAV is shown.

[0105] For example, by including a TimeStamp in the FlightPathInforReportCon, the WTRU may be configured to include timestamp information associated with (e.g., each) waypoint. The timestamp may improve the predictability of the WTRU's location at a given time, which may aid in the planning of WTRU configuration and future resource allocation. The timestamp information may not always be known. If the timestamp information is available at the WTRU, it may be included in the flight path report.

[0106] One or more triggering criteria may be met (e.g., simultaneously) for multiple cells. An airborne WTRU may be configured with a radio resource management (RRM) event (e.g., A3, A4, or A5) that may trigger a measurement report if the per-cell reference signal received power (RSRP) values ​​for a configured number of cells meet the configured event. The measurement report may be sent. If / when subsequent cell(s) meet the event, the list of triggered cells may be updated. While the list of triggered cells remains greater than the configured number of cells, no additional measurement reports may be sent.

[0107] The number of triggering cells for measurement reporting may be provided in ReportConfigEUTRA via numberOfTriggeringCells. The number of triggering cells may range from two (2) to a maximum of eight (8). The number of triggering cells may be useful, for example, for interference detection and / or to reduce signaling overhead (e.g., by reducing the number of measurement reports).

[0108] NR UAVs may support airborne WTRUs (e.g., which may be UAVs). LTE and NR support may be coordinated. NR and LTE may support altitude-based measurement reporting, flight path reporting, and simultaneous fulfillment of triggering criteria for multiple cells. Position and velocity reporting may be supported in both NR and LTE UAVs.

[0109] NR UAVs may support altitude-dependent parameter scaling, user-agreed location reporting, flight path updates after initial reporting, and / or beam consideration and departure condition reporting (e.g., in terms of the number of triggering cells). Flight path reports may include location coordinates, timestamps, and / or flight path information. Mobility control may include altitude-based parameter scaling, altitude-based events based on WTRU location information (e.g., H1 (above threshold), H2 (below threshold)). Interference control may include the number of triggering cells (e.g., A3, A4, A5), a list of triggering cells in MR, new events B1 / B2 (e.g., inter-RAT), and / or beam impact.

[0110] RRC may be enhanced for L1 / L2 triggered mobility (LTM) to support UAV use cases. The LTM procedure may support UAVs in a similar manner to other mobility procedures. The LTM procedure may take into account flight path reporting, altitude, and interference control, as there are a higher number of information elements and beams when the WTRU is at a higher altitude compared to other WTRUs on the ground. RRC management and measurement configuration of LTM candidate cells may take into account aspects specific to UAVs.

[0111] A waypoint in a UAV environment may be a set of 3D coordinates identifying a point in physical space. A waypoint may (for example, alternatively) be a set of 2D coordinates identifying a point on the ground, which may be used in conjunction with an altitude value to determine a 3D point in physical space. A waypoint may be associated with a timestamp to identify the time at which the WTRU is expected to be at the indicated location.

[0112] The flight path may include one or more waypoints (e.g., timestamps) indicating the location (e.g., and time) at which the WTRU expects to be at a certain location. (e.g., each) waypoint may be numbered or indexed so that each waypoint can be uniquely identified.

[0113] "Execute LTM" may mean to execute Figure 4 Any / all of the steps described in

[15] , such as early synchronization in the DL and / or UL to one or more candidate cells, performing L1 measurements and reporting on one or more candidate cells, switching between candidate cells (e.g., performing handover). For example, "performing LTM" may mean that the WTRU moves / hands off between multiple candidate cells during the procedure.

[0114] The candidate cell set may be a group of more than one RRC configurations corresponding to handover configurations for one or more candidate SpCells (e.g., and SCells). The candidate cell set may be modeled or received as one or more complete RRC reconfiguration messages, one or more cell group configurations, or one or more cell configurations. (Each) candidate cell configuration may include a candidate configuration identifier. (Each) candidate cell group may include a candidate cell group identifier. Switching between different sets of candidate cells may include updating the serving cell index or candidate configuration index used in L1 and MAC signaling to reference a specific index, for example, if grouping is performed at the RRC. For example, the MAC CE that triggers the reconfiguration may include a candidate configuration index that informs the WTRU on which cell to perform the reconfiguration.

[0115] One or more candidate cell groups may be configured as a single list or group of candidate cell configurations at RRC. Grouping may occur, for example, during early synchronization or LTM execution phase rather than during configuration phase. The set of candidate cells may be considered to be a (e.g., single) group in terms of an RRC configuration list or group. The cells selected for performing early synchronization, L1 measurements, and / or LTM execution may depend on further grouping into multiple subsets of the total candidate cell list. The grouping itself may not be modeled using a candidate configuration identifier at RRC. Grouping may be performed as part of the early synchronization or LTM execution process.

[0116] The LTM candidate configuration may be applied to any type of pre-configured cell information. For example, a WTRU may be configured with one or more conditional reconfigurations, such as CHO, Conditional PSCell Addition (CPA), or Conditional PSCell Change (CPC), which may be valid before and / or after a cell change, or may be valid in certain cells.

[0117] The examples indicate that UAVs support improved performance for L3 mobility, and measurements may be applied in a similar manner to LTM. The LTM process may be applicable to UAV devices. The use of altitude, speed, and location information may enhance the mobility process. Devices at high altitudes may experience different challenges than devices at lower altitudes / ground level altitudes, such as detecting a higher number of beams or cells and causing higher interference in the uplink due to DL measurements. For example, cells that are in relatively close proximity to a beam directed at ground level may be measured with relatively low quality. The WTRU may transmit at a higher power in the UL, for example based on determining that the perceived low quality is due to high path loss. For at least some devices, the precise location is predictable (e.g., if the WTRU reports flight path information, the location at a particular time may be known with a high degree of confidence).

[0118] L1 measurements may include measurements of RSRP, Reference Signal Strength Indicator (RSSI), etc., performed by the WTRU for a cell, beam, set of cells, or set of beams. L1 measurements may be similar to L3 measurements reported in RRM (e.g., differences in filtering, reference signals measured, reporting mechanism, etc.).

[0119] One or more events may trigger reporting or define WTRU behavior, for example, based on a specific waypoint (e.g., coordinates in the UAV's path). The term waypoint may be used interchangeably with location. Examples may use any mechanism to define the WTRU's geographic location in space.

[0120] The measurement may refer to an L1 measurement of an LTM. In some examples, the measurement may (eg, also) refer to an RRM / L3 measurement and / or other measurements (eg, measurements of speed, position, altitude, flow, etc.).

[0121] LTM candidate cell management for UAVs may provide benefits. LTM may reduce handover delays and radio link failure rates. The performance of LTM (e.g., when used by UAV devices) may be improved (e.g., under certain conditions). The use of rapid mobility with new conditions such as altitude, speed, and / or predictable location may improve signaling efficiency (e.g., by reducing the total amount of information to be configured or reconfigured by RRC). For example, by adjusting the LTM process to take into account UAV-specific information, unnecessary L1 measurement reports may be reduced, handover failure rates may be improved, and data interruptions may be reduced.

[0122] Figure 6 An example of an initial flight path reporting procedure is shown. The WTRU may indicate whether flight path information is available, for example, via one or more messages such as an RRCConnectionReconfigurationComplete message, an RRCConnectionReeastatusMessComplete message, an RRCConnectionResumComplete message, and / or an RRCConnectionSetupComplete message.

[0123] The E-UTRAN may request the WTRU to report flight path information via a FlightPathInfoReq in a UEInformationRequest message. Timestamp information may be requested (e.g., and included) via includeTimeStamp. LTE may support configuration of up to 20 waypoint locations within a flight path report. The WTRU may include a FlightPathInfoReport in a UEInformationResponseMessage, e.g., including (e.g., all) available waypoints (e.g., up to a configured maximum) and timestamp information (e.g., if configured and available at the WTRU).

[0124] The UAV may provide flight path report content (e.g., waypoints and optional timestamps) and / or an initial reporting procedure. The UAV may update a previously reported flight path, for example, via an indication in a UEAssistanceInformation message. Upon indication, the network (NW) may retrieve the updated flight path using a WTRU (e.g., UE) information request / response procedure.

[0125]

[0014] Feature(s) associated with flight path reporting are provided herein. Flight path reporting may be associated with LTM configuration. In some examples, a WTRU may report flight path information to a gNB. The gNB may configure the WTRU with parameters or conditions associated with one or more waypoints. The WTRU may report flight path information (e.g., GPS coordinates and time of one or more waypoints in the future) to the gNB. The gNB may configure a set of LTM candidates or parameters corresponding to one or more waypoints.

[0126] The WTRU may receive one or more of the following types of configurations, which may be associated with one or more waypoints (eg, by associating the configurations with waypoint indices): one or more candidate cell configurations, mobility-related parameters, and / or synchronization type.

[0127] A candidate cell configuration or a set of candidate cell configurations may be referenced by an index (eg, a candidate configuration index).

[0128] The mobility-related parameters may include, for example, one or more of the following: radio quality threshold; trigger time; measurement identifier (e.g., to identify the measurement event type and / or a set of measurement parameters); CSI-RS reporting configuration; CSI-RS resource configuration; one or more TCI states; measurement filter parameters; measurement evaluation type (e.g., L3 or L1 measurement); and / or report type (e.g., RRC, MAC CE, or CSI-RS).

[0129] The synchronization type may include, for example, one or more of: whether to perform early synchronization in DL or UL (e.g., before handover is triggered); what type of random access procedure is performed (e.g., no RACH, 2-step RA, 4-step RA); and / or a timing advance (TA) value.

[0130] In some examples (e.g., if / when the WTRU arrives at a certain waypoint), parameters or configurations that were previously configured and associated with that waypoint may be applied, and currently used parameters or configurations that are not associated with the new waypoint may be deactivated or released.

[0131] Altitude-based conditions may be implemented. (E.g., each) altitude threshold may be associated with a configuration or parameter in a similar manner as described for waypoints (e.g., the configurations and parameters described herein for potential association with waypoints may additionally or alternatively be associated with an altitude threshold).

[0132] In some examples (e.g., if / when the WTRU is above or below a certain altitude threshold), previously configured parameters or configurations associated with the threshold may be applied, and currently used parameters or configurations not associated with the threshold may be deactivated or released. In some examples, if / when above a threshold, one or more (e.g., specific) parameters and / or configurations may be applied, and if / when below a threshold, other parameters and / or configurations may be applied. Multiple thresholds may be configured and associated with different parameters and thresholds.

[0133] The WTRU may be configured with altitude-based conditions for determining parameters, behavior, etc. The altitude-based conditions may be configured by the network (e.g., in RRC) or may be predefined. The altitude-based conditions may be configured by the network. For example, the altitude-based conditions may be enabled / disabled via NW signaling (e.g., MAC CE, DCI, System Information Block (SIB), RRC, etc.). The altitude-based conditions may be enabled / disabled by another condition (e.g., speed-based conditions, waypoint-based conditions, etc.).

[0134] The altitude-based condition may be in the form of the WTRU reaching at least or at most a certain altitude. For example, the altitude-based condition may indicate one or more of the following: the WTRU's altitude is above a configured threshold; the WTRU's altitude is below a configured threshold; and / or the WTRU's altitude is between thresholds (e.g., two configured thresholds).

[0135] The altitude-based condition may be in the form of a change in the WTRU's altitude. For example, the altitude-based condition may indicate one or more of the following: the WTRU's altitude has changed by an amount greater than a threshold (e.g., within a configured time period / duration); the WTRU's altitude has increased by an amount greater than a threshold (e.g., within a configured time period / duration); the WTRU's altitude has decreased by an amount greater than a threshold (e.g., within a configured time period / duration); the WTRU's altitude change has increased by an amount greater than a threshold (e.g., within a configured time period / duration); and / or the WTRU's altitude change has decreased by an amount greater than a threshold (e.g., within a configured time period / duration).

[0136] The altitude-based condition may be in the form of the time the WTRU spends at a particular altitude. For example, the altitude-based condition may indicate one or more of the following: the WTRU's altitude remains at the same value for at least a configured period of time; the WTRU's altitude remains within a configured range for at least a configured period of time; the WTRU's altitude changes by less than a configured amount over a configured period of time; and / or the WTRU has spent a maximum amount of time at a particular altitude over a configured period of time.

[0137] Location-based conditions may be implemented. The WTRU may be configured with waypoint-based conditions for determining parameters, behavior, etc. Waypoint-based conditions may be configured by the network (e.g., in RRC) or may be predefined. Waypoint-based conditions may be configured by the network. The waypoint-based conditions may then be enabled / disabled, for example, via NW signaling (e.g., MAC CE, DCI, SIB, RRC, etc.). Waypoint-based conditions may be enabled / disabled by another condition (e.g., speed-based conditions, altitude-based conditions, etc.).

[0138] A waypoint-based condition may be in the form of the WTRU arriving at a waypoint (e.g., given coordinates) and / or approaching a waypoint reported earlier in the WTRU's flight path. A waypoint-based condition may be configured for one or more (e.g., specific or selected) waypoints, or may be generic for any number of waypoints. For example, a waypoint-based condition may indicate one or more of the following: the WTRU is located at a specific waypoint; and / or the WTRU is within a (e.g., specific) configured distance from a waypoint.

[0139] The waypoint-based condition may be in the form of a time to arrive at the waypoint or a time spent at the waypoint. For example, the waypoint-based condition may indicate one or more of the following: the WTRU will be within a configured distance from the waypoint for less than a configured threshold time; the WTRU will spend at least a configured period of time within the configured distance from a particular waypoint; the WTRU will not be within the configured distance from the waypoint for more than a configured threshold time; and / or the WTRU will spend less than a configured period of time within the configured distance from a particular waypoint.

[0140] The waypoint-based condition may be in the form of a change in the reported waypoint. For example, the waypoint-based condition may indicate one or more of the following: the waypoint changes by at least a configured distance; the timestamp associated with the waypoint changes by at least a configured time; and / or the WTRU skips a waypoint (e.g., arrives at a second waypoint that was intended to be reached after the first waypoint before arriving at the first waypoint, etc.).

[0141] Speed-based conditions may be implemented. The WTRU may be configured with speed-based conditions for determining parameters, behavior, etc. The speed-based conditions may be configured by the network (e.g., in RRC) or may be predefined. The speed-based conditions may be configured by the network. The speed-based conditions may be enabled / disabled via NW signaling (e.g., MAC CE, DCI, SIB, RRC, etc.). The speed-based conditions may be enabled / disabled by another condition (e.g., an altitude-based condition, a waypoint-based condition, etc.).

[0142] The speed-based condition may be in the form of the WTRU reaching at least or at most a certain speed. For example, the speed-based condition may indicate one or more of the following: the WTRU's speed is above a configured threshold; the WTRU's speed is below a configured threshold; and / or the WTRU's speed is between two configured thresholds.

[0143] The speed-based condition may be in the form of a change in the WTRU's speed (e.g., acceleration / deceleration). For example, the speed-based condition may indicate one or more of the following: the WTRU's speed has changed by an amount greater than a threshold (e.g., within a time period); the WTRU's speed has increased by an amount greater than a threshold (e.g., within a time period); or the WTRU's speed has decreased by an amount greater than a threshold (e.g., within a time period).

[0144] The speed-based condition may be in the form of the time the WTRU spends at a particular speed. For example, the speed-based condition may indicate one or more of the following: the WTRU's speed remains at the same value for at least a configured period of time; the WTRU's speed remains within a configured range for at least a configured period of time; and / or the WTRU's speed changes by more than / less than a configured amount within a configured period of time.

[0145] The WTRU LTM candidate set update may be based on altitude, speed, and / or waypoint conditions. For example, a device may include a processor configured to receive first configuration information. The first configuration information may indicate a first candidate cell and a second candidate cell. For example, the first candidate cell may be an LTM candidate cell. The second candidate cell may be an LTM candidate cell. The first candidate cell may be part of a first LTM candidate cell set. The second candidate cell may be part of a second LTM candidate cell set. The first configuration information may indicate the first LTM candidate cell set and the second LTM candidate cell set. The WTRU may select a first cell from the first candidate cell set and a second cell from the second candidate cell set.

[0146] The processor may be configured to receive second configuration information. The second configuration information may indicate a first geo-related condition and a second geo-related condition (e.g., a potential UAV condition). For example, the geo-related condition may include metrics related to aspects such as UAV altitude, UAV speed, waypoints, etc., as described herein. For example, the geo-related condition may represent a condition that may potentially be met during UAV operation. For example, the geo-related condition may include any UAV parameter that may be reported to the E-UTRAN. For example, the geo-related condition may represent a threshold metric associated with UAV operation.

[0147] The processor may receive information indicating a significant UAV condition. For example, the processor may receive information related to aspects of UAV operation, such as current and / or most recently current UAV altitude, UAV speed, waypoints, etc. The significant UAV condition may be determined by the UAV. For example, the significant UAV condition may be determined by determining and / or measuring the state of the UAV operation.

[0148] The configuration information may indicate a first layer one / two triggered mobility (LTM) process and a second LTM process. The processor may be configured to determine which of the first candidate cell and the second candidate cell to perform the LTM process on based on a comparison of an obvious UAV condition and a potential UAV condition. For example, the LTM process may be performed on the first candidate cell based on the obvious UAV condition not satisfying the potential UAV condition. For example, the LTM process may be performed on the second candidate cell based on the obvious UAV condition satisfying the potential UAV condition.

[0149] In one example, a WTRU may receive a configuration (e.g., or a CHO / CPAC configuration) of a first set of LTM candidate cells and a second set of LTM candidate cells. The WTRU may receive a configuration that associates (e.g., each) set with one or more geography-related conditions (e.g., altitude, speed, and / or waypoint conditions). For example, the geography-related condition may be an altitude condition associated with the altitude at which the WTRU is located, a speed condition associated with the speed at which the WTRU is moving, or a waypoint condition associated with a waypoint on the WTRU's flight path. The first geography-related condition may be associated with a first LTM process, and the second geography-related condition may be associated with a second LTM process.

[0150] The WTRU may perform an LTM procedure using a first set of candidate cells (e.g., measurements, reports, early synchronization, MAC CE content involving cells in the first set). For example, the WTRU may perform a first LTM procedure by using or measuring a first cell (e.g., in the first set).

[0151] The WTRU may determine that a first geo-related condition (e.g., one or more altitude, speed, and / or waypoint conditions) is satisfied (e.g., altitude is above a threshold or a waypoint is reached). The WTRU may transmit an indication (e.g., based on satisfying the one or more geo-related conditions). The WTRU may perform an LTM procedure using a second set of candidate cells. For example, the WTRU may perform a first LTM procedure by using or measuring a first cell (e.g., in the first set).

[0152] Figure 7 An exemplary use case utilizing known waypoints associated with a set of LTM candidate configurations (e.g., or cells) is shown. If the WTRU determines that the WTRU has arrived at a first waypoint, the WTRU may determine that a first geo-related condition is satisfied. If the WTRU determines that the WTRU has arrived at a second waypoint, the WTRU may determine that a second geo-related condition is satisfied. Figure 7 As shown, a set of candidate LTM configurations or cells may be associated with previously reported waypoints. Waypoint 1 may be associated with Candidate Set 1, and waypoint 2 may be associated with Candidate Set 2. Figure 7 As described herein, a position / waypoint-based condition may be, for example, a range of positions (eg, within a specific radius of a position, between two position coordinates, etc.), rather than an exact position.

[0153] Conditions based on location / waypoints that are specified as a location range may be appropriate, for example, if the WTRU moves from one geographic area to another, the WTRU may monitor a different set of cells after a certain time. The WTRU may move from the location indicated by waypoint 1 to the location indicated by waypoint 2. The WTRU may perform a second LTM procedure (e.g., associated with waypoint 2). For example, the WTRU may stop performing the first LTM procedure (e.g., stop monitoring the cell associated with waypoint 1) and monitor the cell associated with waypoint 2. The WTRU may send an indication (e.g., to the network) that the second cell (e.g., the cell associated with waypoint 2) is in use.

[0154] In some examples (e.g., use cases), each of the known waypoints may be at a different altitude. For example, a WTRU at a waypoint closer to the ground may be configured to monitor cells that are in close proximity to each other, or cells with less coverage, while a WTRU with a waypoint higher in the air may be configured to monitor cells that are geographically farther away, or cells with wider coverage. A WTRU with a waypoint at a higher altitude (e.g., absolute altitude or altitude relative to ground level) may (e.g., alternatively) be configured to measure a larger or smaller set of cells than a WTRU with a waypoint closer to the ground. For example, a WTRU may be able to detect and use a greater number of different cells at high altitudes. The best cell (e.g., at any point in time) may be one of a larger set than when the WTRU is closer to the ground. In another example, the number of monitored cells may be smaller at a waypoint at a higher altitude, for example, if each of the cells has greater coverage than each of the larger set of monitored cells when the WTRU is at a waypoint closer to the ground. For example, a cell with greater coverage may use a carrier or frequency band in FR1, while a cell with less coverage may use a carrier or frequency band in FR2. Similarly, a candidate cell set may alternatively or additionally be associated with one or more altitude thresholds. As described in the context of using waypoints at different altitudes, the WTRU may monitor a different set of cells when it is above an altitude threshold than when it is below the threshold. If the WTRU is above a speed-based threshold, the WTRU may monitor a first set of cells, and if the WTRU is below the threshold, the WTRU may monitor a second set of cells.

[0155] Figure 8 An example process utilizing waypoints or altitude or speed thresholds associated with a set of different LTM candidate configurations (e.g., or cells) is shown. Figure 8As shown, at 1, the WTRU may receive a configuration of a first set of LTM candidate cells and a second set of LTM candidate cells. The (e.g., each) set of cells may be associated or linked to (e.g., a specific) condition based on waypoint, altitude, and / or speed conditions. The configuration may be received using RRC signaling.

[0156] At 2, the WTRU may perform LTM procedures (eg, early synchronization, L1 measurements, LTM execution) using the first set of LTM candidate cells.

[0157] At 3, the WTRU may evaluate the configured altitude, speed, and / or waypoint-based conditions when performing LTM on the first set of candidate cells. If the WTRU's altitude is below an altitude threshold, the WTRU may determine that the first geography-related condition is met. If the WTRU's speed is below a speed threshold, the WTRU may determine that the first geography-related condition is met. For example, the WTRU may perform the LTM process using the first set of candidate cells as long as the second geography-related condition is not met. For example, the WTRU may use the first set of candidate cells if the WTRU has not reached the second waypoint, or as long as the altitude or speed is below a configured threshold.

[0158] At 4, a second geography-related condition may be met. For example, if the WTRU's altitude is above an altitude threshold, the WTRU may determine that the second geography-related condition is met. If the WTRU's speed is above a speed threshold, the WTRU may determine that the second geography-related condition is met. The WTRU may reach waypoint 2, or the WTRU's altitude or speed may be above a configured threshold. The WTRU may begin LTM execution using the second set of LTM candidate cells.

[0159] In some examples, the WTRU may send an indication (e.g., a usage flag) to the network (e.g., based on / upon selecting the second LTM candidate cell set) that the second LTM candidate cell set is in use. The indication may be sent in a MAC CE, in an RRC message, or in an L1 UCI (e.g., a scheduling request resource configured for this purpose). In some examples, the indication may be delayed (e.g., not sent immediately). The indication may be included in another uplink message (e.g., a MAC CE or a CSI report, e.g., including L1 measurement results for the candidate cells). The indication may be implicit. For example, measurements of cells in Candidate Set 1 may be included, which may imply that Candidate Set 1 is in use.

[0160] L3 and LTM mobility handovers may be based on altitude, speed, and / or waypoint conditions. For example, a WTRU may receive a configuration of a first mobility assessment associated with a first measurement type (e.g., a first type of mobility assessment (LTM) using L1 measurements) and a second mobility assessment associated with a second measurement type (e.g., a second type of mobility assessment (L3 handover) using RRC measurements). (E.g., each type of mobility assessment may be associated with one or more altitude, speed, and / or waypoint conditions.

[0161] The WTRU may perform a mobility assessment (e.g., a first mobility assessment) based on (e.g., using) a first measurement type / type of mobility assessment (e.g., L1 measurement, reported using a MAC CE). The WTRU may send (e.g., to the network) a result of the first mobility assessment (e.g., sending the L1 measurement using a MAC CE).

[0162] The WTRU may determine that a geography-related condition is satisfied. For example, the WTRU may determine (e.g., based on a mobility assessment) that an altitude condition (e.g., associated with the altitude at which the WTRU is located), a speed condition (e.g., associated with the speed at which the WTRU is moving), and / or a waypoint condition (e.g., associated with a waypoint on the WTRU's flight path location) is satisfied (e.g., the altitude or speed may be above a threshold or the waypoint may be reached). The WTRU may transmit an indication (e.g., based on satisfying the geography-related condition) and / or perform a mobility assessment (e.g., a second mobility assessment) based on (e.g., using) a second measurement type / type of mobility assessment (e.g., L3 filtering, reporting using RRC measurement reporting). The WTRU may send (e.g., to the network) the results of the second mobility assessment (e.g., sending L3 measurements in RRC signaling).

[0163] Figure 9 Example use cases utilizing waypoints, altitude, and / or speed thresholds associated with different types of mobility are shown. Figure 9 As shown in the example in

[15] , the WTRU may be configured with different types / methods of mobility depending on the current altitude. An altitude / altitude threshold may be configured. If the WTRU is below the altitude / altitude threshold, the WTRU may perform LTM. If the WTRU is above the altitude / altitude threshold, the WTRU may determine that the geo-related conditions are met (e.g., and therefore use L3 mobility).

[0164] It may be appropriate to use different types / methods of mobility, for example, to control whether the WTRU performs enhanced (e.g., lower latency) LTM procedures when performing mobility between cells belonging to the same CU (e.g., for LTM, intra-DU and inter-DU may be supported) and when performing mobility between cells belonging to different CUs (e.g., for LTM, inter-CU mobility may not be supported). Groups of cells that are in close proximity to each other may (e.g., may) belong to the same CU. A WTRU close to the ground may measure and perform handovers between cells of the same CU. A WTRU at higher altitudes may be able to measure cells from multiple different CUs. (e.g., each) CU may provide cells with different coverage (e.g., using different frequency layers or bands). For example, a single CU may provide one or more wider coverage cells (e.g., in FR1) and multiple narrower coverage cells (e.g., in FR2). A WTRU at high altitude may be configured to perform L3 mobility using one or more wider coverage cells covering a larger geographic area, while a WTRU at lower altitude may be configured to perform LTM using a set of narrower coverage cells covering a smaller geographic area (e.g., but which may provide higher throughput and lower latency).

[0165] In some examples, the WTRU may be at a higher altitude where more beams and cells may be "visible" (e.g., detectable). The WTRU may be configured to use L3 measurements and L3 mobility at higher altitudes, for example, to ensure more stable transitions between different cells and reduce the number of possible handovers by utilizing longer evaluation times and reduced ping-pong switching rates (e.g., compared to LTM). The WTRU may (e.g., alternatively) be configured to utilize a higher number of detected beams. The WTRU may enable LTM at higher altitudes, for example, to give the network more scheduling flexibility if / when more potential cells and beams are available. For example, if / when the WTRU is closer to the ground, the WTRU may (e.g., be configured to) use L3 mobility. For example, if the WTRU moves at a relatively high speed when close to the ground, such that the WTRU moves between different CUs (e.g., relatively regularly) and uses L3 mobility (e.g., frequently), while at higher altitudes the WTRU may detect more beams and cells in a single CU over a longer period of time, then multiple configurations based on the altitude or height of the ground may be advantageous.

[0166] In some examples, each of the multiple known waypoints may be at a different altitude. For example, a WTRU at a waypoint closer to the ground may be configured to use LTM procedures to monitor cells that are in close proximity to each other (e.g., or to monitor cells with less coverage), while a WTRU with a waypoint higher in the air may be configured to use L3 measurements to monitor cells that are geographically farther away or have wider coverage.

[0167] In some examples, the number of monitored cells may be smaller at waypoints at higher altitudes, for example, if each cell has greater coverage than each of the larger set of cells being monitored when the WTRU is at a waypoint closer to the ground. For example, cells with greater coverage may use a carrier or frequency band in FR1, while cells with less coverage may use a carrier or frequency band in FR2. Similarly, the set of candidate cells may alternatively or additionally be associated with one or more altitude thresholds. As described herein (e.g., in the context of using waypoints at different altitudes), the WTRU may monitor a different set of cells when above an altitude threshold than when below the threshold. The WTRU may monitor a different set of cells when above a speed-based threshold than when below the threshold.

[0168] Figure 10 An example process utilizing waypoints, altitude, and / or speed thresholds associated with different types of mobility is shown. For example, a device may include a processor configured to receive first configuration information and second configuration information. The first configuration information may indicate a first mobility method (e.g., an L1-based mobility method) and a second mobility method (e.g., an L3-based mobility method). The second configuration information may indicate a potential UAV condition (e.g., a potential UAV condition disclosed herein). The processor may be configured to determine which of the first mobility method and the second mobility method to perform based on a comparison of an apparent UAV condition and the potential UAV condition.

[0169] For example, Figure 10 As shown, at 1, the WTRU may receive a configuration for a first type of mobility and a second type of mobility. The WTRU may receive a configuration that associates each type of mobility with one or more waypoints, altitude, and / or speed conditions. The configuration may be received using RRC signaling. The first type of mobility may be, for example, LTM. The first type of mobility (e.g., LTM) may use L1 measurements and reporting and MAC CE cell change triggers. The second type of mobility may be L3 mobility. The second type of mobility (e.g., L3) may use L3 measurements, RRC measurement reports, and RRC reconfiguration.

[0170] At 2, the WTRU may perform mobility using a first mobility method.

[0171] At 3, the WTRU may evaluate the configured conditions based on altitude, speed, and / or waypoints when performing the first type of mobility. For example, the WTRU may use the first type of mobility to perform mobility as long as the geo-related conditions are not met. For example, the WTRU may use LTM if the WTRU does not reach the second waypoint, or as long as the altitude or speed is below a configured threshold.

[0172] At 4, for example, if / when geo-related conditions are met (e.g., the WTRU reaches waypoint 2, or the WTRU's altitude or speed is above a configured altitude or speed threshold), the WTRU may start using a second type of mobility (e.g., L3 mobility).

[0173] In some examples, the WTRU may send an indication (e.g., a usage flag) to the network (e.g., upon selecting the second mobility method) indicating that the second mobility method is in use or that a condition is met. For example, the indication may be sent in a MAC CE, an RRC message, or in an L1 UCI. In some examples, the indication may be delayed (e.g., not sent immediately). The indication may be included in another uplink message (e.g., a MAC CE or CSI report including L1 measurement results for the candidate cell). The indication may be implicit. For example, the WTRU may send an RRC measurement report including L3 measurements, which may (e.g., implicitly / implicitly) indicate that an L3-based mobility procedure has been selected. The WTRU may send an L1 measurement report (e.g., a CSI report or a MAC CE) which may (e.g., implicitly / implicitly) indicate that an L1 / 2-based mobility procedure has been selected.

[0174] In some examples, multiple (e.g., two) types of mobility can be configured and run in parallel. Each type of mobility can be associated with a condition (e.g., the same condition or a separate condition) that enables or disables that type of mobility. In some examples, conditional reconfiguration (e.g., CHO evaluation and trigger) can be enabled / disabled based on the condition.

[0175] The update may be a fast candidate set update controlled by the NW.

[0176] For example, the WTRU may receive configuration information indicating a first LTM process associated with a first cell (e.g., of a first LTM candidate cell set) and a second LTM process associated with a second cell (e.g., of a second LTM candidate cell set). The WTRU may select the first cell from the first candidate cell set and the second cell from the second candidate cell set. The WTRU may receive (e.g., in the configuration information) geo-related conditions (e.g., measurement event conditions) related to altitude and / or speed thresholds and / or waypoint arrival.

[0177] The WTRU may perform a first LTM procedure based on (e.g., using or measuring) a first cell (e.g., in a first set of candidate cells). The WTRU may determine that a measurement event condition has been met. The WTRU may transmit an L1 / 2 indication of the event (e.g., via a MAC CE / in a MAC CE). The WTRU may receive an L1 / 2 indication of an index to a second set of cells (e.g., in a MAC CE). The WTRU may (e.g., additionally) receive an indication of a new SpCell / SCell (e.g., to trigger LTM execution). The WTRU may update the candidate cell set and / or perform LTM (e.g., if instructed). The WTRU may perform LTM using the second set of candidate cells.

[0178] The WTRU may autonomously update, for example, based on certain criteria (such as if the LTM set is in use). In some examples, the WTRU may report that a condition has been met, and (eg, in response) the network may control the change of the LTM set.

[0179] Figure 11 An example process for fast candidate set update with NW control is shown. At 1, the WTRU may receive a configuration of a first LTM process associated with a first cell (e.g., of a first LTM candidate cell set) and a second LTM process associated with a second cell (e.g., of a second LTM candidate cell set). The (e.g., each) set of cells may be a grouping of separate candidate cell configurations. Some candidate cell configurations may be part of more than one set. The (e.g., each) set of cells may be provided with an index or identifier. The (e.g., each) set of cells may be provided with a different index or identifier. The configuration may be received using RRC signaling.

[0180] At 2, the WTRU may receive a measurement reporting event configuration. For example, if the altitude or speed is determined to be above or below a threshold, the WTRU may receive a geo-related condition (e.g., a configuration that triggers a measurement event). For example, if / when it is determined that a waypoint has been reached, or that the WTRU is within a threshold distance or time from a waypoint, the WTRU may receive a geo-related condition (e.g., a configuration that triggers a measurement event).

[0181] At 3, the WTRU may perform LTM procedures (eg, early synchronization, L1 measurements, LTM execution) using the first set of LTM candidate cells.

[0182] At 4, the WTRU may determine whether a geography-related condition has been met. For example, the geography-related condition may be an altitude condition associated with the altitude at which the WTRU is located, a speed condition associated with the speed at which the WTRU is moving, or a waypoint condition associated with a waypoint on the WTRU's flight path. The WTRU may evaluate the configured altitude, speed, and / or waypoint-based conditions when performing LTM on the first set of candidate cells. For example, the WTRU may use the first set of candidate cells to perform the LTM process as long as the geography-related condition is not met. For example, the WTRU may use the first set of candidate cells if the WTRU has not reached the second waypoint, or as long as the altitude or speed is below a configured threshold.

[0183] At 5, the WTRU may determine that a geo-related condition has been met / satisfied (e.g., if / when the WTRU reaches waypoint 2, or the altitude / altitude or speed exceeds a configured altitude / altitude or speed threshold). The WTRU may (e.g., in response to determining that the geo-related condition is met) send an indication (e.g., to the network) that the geo-related condition (e.g., a measurement event) is met. The indication may be sent using a MAC CE or an RRC measurement report. The indication may include a standard configured index or identifier (e.g., an event ID). The indication may include measurement information, such as an indication of the radio quality (e.g., RSRP, RSRQ) of one or more beams or cells.

[0184] At 6, the WTRU may receive (e.g., from the network) an indication associated with a second LTM procedure (e.g., a MAC CE, which may include an index or identifier for the second set of cells). The MAC CE may indicate an index or identifier for the new SpCell / SCell to trigger LTM execution and / or SCell activation / deactivation.

[0185] At 7, in response to receiving an indication associated with a second LTM procedure, the WTRU may perform a second LTM procedure (e.g., by using or measuring a second cell). For example, the WTRU may update the candidate cells being considered for LTE to a second set of candidate cells. The update may involve updating the respective candidate cell indices. The WTRU may perform LTM (e.g., if indicated) to perform RRC reconfiguration to the new SpCell. The WTRU may activate or deactivate one or more SCells (e.g., if indicated). The indication to perform LTM may be received in the same message (e.g., MAC CE) as the indication to update the set of cells in use. In some examples, the WTRU may perform a cell change and update the set of candidate cells at the same time.

[0186] At 8, the WTRU may begin LTM execution using the second set of LTM candidate cells. The WTRU may determine that a second geography-related condition has been met (e.g., the WTRU has reached a third waypoint, or the altitude / altitude or speed is below an altitude / altitude or speed threshold). The WTRU may send an indication (e.g., to a network entity) that the second geography-related condition has been met. The WTRU may receive (e.g., from a network entity) an indication associated with the first LTM procedure. In response to receiving the indication associated with the first LTM procedure, the WTRU may use or measure a third cell based on the first LTM procedure.

[0187] Figure 12 An example of signaling to perform this process with NW controlled fast candidate set update is shown. At 1, an RRC reconfiguration message may be received. The reconfiguration message may be provided in any type of downlink signaling from the gNB to the WTRU. The measurement conditions may be provided in an RRC measurement control message, or may be provided along with the configuration at 1 (e.g., in an RRC reconfiguration), or may be provided in any other downlink signaling message from the gNB to the WTRU. The event at 5 may be reported using a MAC CE in the uplink. The uplink indication may include measurement results for cells or beams measured as part of performing LTM. The indication at 6 may be provided in a MAC CE. The indication at 6 may include an indication to perform LTM on a new SpCell and / or to activate or deactivate one or more SCells.

[0188] The event at 5 may (e.g., alternatively) be reported via a transmission on a PUCCH resource, such as a scheduling request resource configured for this purpose, e.g., as part of the second LTM configuration. For example, the WTRU may initiate a procedure (e.g., a CSI hinting procedure) that may be identical to the scheduling request procedure, but the condition for canceling the scheduling request may be receiving signaling that performs at least one of: activating or triggering L1 (e.g., CSI) reporting for a reporting configuration or triggering state associated with the second LTM configuration, or for a second candidate cell set, SSB index, or CSI-RS resource; and / or activating resources for channel and / or interference measurement associated with the second LTM configuration for at least one of the reporting configuration or triggering state.

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

[0190] Although the embodiments described herein may consider 3GPP specific protocols, it should be understood that the embodiments described herein are not limited to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR), or 5G specific protocols, it should be understood that the solutions described herein are not limited to this scenario and may also be applied to other wireless systems.

[0191] The above process may be implemented in a computer program, software, and / or firmware that is incorporated into 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 disc (CD)-ROM disks and / or digital versatile disks (DVDs). A processor associated with the software may be used to implement a radio frequency transceiver used in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), the WTRU comprising: A processor configured to: receiving configuration information indicating a first layer one / two triggered mobility (LTM) procedure, a first geography-related condition associated with the first LTM procedure, a second LTM procedure, and a second geography-related condition associated with the second LTM procedure, wherein the first LTM procedure is associated with a first cell and the second LTM procedure is associated with a second cell; determining that the first geography-related condition is satisfied, wherein the first geography-related condition comprises a first altitude condition associated with the altitude at which the WTRU is located, a first speed condition associated with the speed at which the WTRU is moving, or a first waypoint condition associated with a first waypoint in a flight path location of the WTRU; Based on satisfying the first geographically related condition, performing the first LTM process, wherein the processor being configured to perform the first LTM process comprises: the processor being configured to use or measure the first cell; determining that the second geographically relevant condition is satisfied; and Based on satisfying the second geographically related condition, performing the second LTM process, wherein the processor being configured to perform the second LTM process includes the processor being configured to use or measure the second cell.

2. The WTRU of claim 1 , wherein the second geography-related condition comprises: A second altitude condition associated with the altitude at which the WTRU is located, a second speed condition associated with the speed at which the WTRU is moving, or a second waypoint condition associated with a second waypoint in the flight path location of the WTRU.

3. The WTRU of claim 1 , wherein the processor is configured to determine that the first geo-related condition is satisfied comprises: The processor is configured to determine that the altitude of the WTRU is below an altitude threshold, and the processor is configured to determine that the second geo-related condition is satisfied includes the processor being configured to determine that the altitude of the WTRU is above the altitude threshold.

4. The WTRU of claim 1 , wherein the processor is configured to determine that the first geo-related condition is satisfied comprises: The processor is configured to determine that a speed of the WTRU is below a speed threshold, and the processor is configured to determine that the second geo-related condition is satisfied includes the processor being configured to determine that the speed of the WTRU is above the speed threshold.

5. The WTRU of claim 1 , wherein the processor is configured to determine that the first geo-related condition is satisfied comprises: The processor is configured to determine that the WTRU has arrived at a first waypoint, and the processor is configured to determine that the second geo-related condition is satisfied includes the processor being configured to determine that the WTRU has arrived at a second waypoint.

6. The WTRU of claim 1 , wherein the configuration information further indicates a first set of candidate cells and a second set of candidate cells, and the processor is further configured to: selecting the first cell from the first set of candidate cells; and The second cell is selected from the second candidate cell set.

7. The WTRU of claim 1 , wherein the processor being configured to perform the second LTM process comprises the processor being configured to: stopping execution of the first LTM process; and An indication that the second cell is in use is sent to a network entity.

8. The WTRU of claim 1 , wherein the processor being configured to perform the first LTM process comprises: The processor is configured to send a first indication indicating information associated with the first cell to a network entity, and the processor is configured to perform the second LTM process including: the processor is configured to send a second indication indicating information associated with the second cell to the network entity, wherein at least one of the first indication and the second indication is sent via a medium access control (MAC) control element (MAC CE), a radio resource control (RRC) message, uplink control information (UCI), or a channel state information (CSI) report.

9. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: receiving configuration information indicating a first layer one / two triggered mobility (LTM) procedure, a first geography-related condition associated with the first LTM procedure, a second LTM procedure, and a second geography-related condition associated with the second LTM procedure, wherein the first LTM procedure is associated with a first cell and the second LTM procedure is associated with a second cell; determining that the first geography-related condition is satisfied, wherein the first geography-related condition comprises a first altitude condition associated with the altitude at which the WTRU is located, a first speed condition associated with the speed at which the WTRU is moving, or a first waypoint condition associated with a first waypoint in a flight path location of the WTRU; Based on satisfying the first geographically related condition, executing the first LTM process, wherein executing the first LTM process includes: using or measuring the first cell; determining that the second geographically relevant condition is satisfied; and Based on satisfying the second geographical-related condition, the second LTM process is performed, wherein performing the second LTM process includes: using or measuring the second cell.

10. The method according to claim 9, wherein the second geographically related condition comprises: A second altitude condition associated with the altitude at which the WTRU is located, a second speed condition associated with the speed at which the WTRU is moving, or a second waypoint condition associated with a second waypoint in the flight path location of the WTRU.

11. The method according to claim 9, wherein determining whether the first geographically related condition is satisfied comprises: Determining that the altitude of the WTRU is below an altitude threshold, and determining that the second geo-related condition is satisfied includes determining that the altitude of the WTRU is above the altitude threshold.

12. The method of claim 9, wherein determining that the first geographically related condition is satisfied comprises: A speed of the WTRU is determined to be below a speed threshold, and determining that the second geo-related condition is satisfied includes determining that the speed of the WTRU is above the speed threshold.

13. The method of claim 9, wherein determining that the first geographically related condition is satisfied comprises: Determining that the WTRU has arrived at a first waypoint and determining that the second geo-related condition is satisfied includes determining that the WTRU has arrived at a second waypoint.

14. The method according to claim 9, wherein the configuration information further indicates a first candidate cell set and a second candidate cell set, and the method further comprises: Selecting the first cell from the first set of candidate cells; as well as The second cell is selected from the second candidate cell set.

15. The method of claim 9, wherein performing the second LTM process comprises: Stop executing the first LTM process; as well as An indication that the second cell is in use is sent to a network entity.

16. The method according to claim 9, wherein Performing the first LTM process includes: sending a first indication indicating information associated with the first cell to a network entity, and performing the second LTM includes: sending a second indication indicating information associated with the second cell to the network entity, wherein at least one of the first indication and the second indication is sent via a media access control (MAC) control element (MAC CE), a radio resource control (RRC) message, uplink control information (UCI), or a channel state information (CSI) report.

Images