ltm measurement parameter determination based on height condition, speed condition or position condition

Abstract

A Wireless Transmit / Receive Unit (WTRU) can be configured to receive configuration information from the network indicating a first Layer 1 / Layer 2 Triggered Mobility (LTM) measurement parameter set and a second LTM measurement parameter set to be applied when performing beam-related measurements. The WTRU can be configured to receive indications of conditions associated with the WTRU's altitude, speed, and / or location. The WTRU can be configured to use the first LTM measurement parameter set to measure the beam when the condition is not met, or to use the second LTM measurement parameter set when the condition is met. The WTRU can be configured to transmit beam measurements to the network based on these conditions.

Description

[0001] This application is a divisional application of patent application No. 202480025478.1, filed on February 13, 2024, entitled "Determination of LTM Measurement Parameters Based on Height, Speed ​​or Position Conditions". Cross-references to related applications

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

[0003] In RRC_CONNECTED mode, a Wireless Transmit / Receive Unit (WTRU) can measure and / or detect multiple beams in a cell (e.g., at least one cell), and the measurement results (e.g., power values) can be averaged to derive cell quality. In doing so, the WTRU can be configured to consider a subset of the measured / detected beams. In the example, filtering can be performed at two different levels: beam quality is obtained at the physical layer, and then cell quality is obtained from multiple beams at the RRC level. In the example, cell quality can be derived from beam measurements for both serving and non-serving cells in the same manner. In the example, if the WTRU is configured to do this via a gNB, the measurement report can include measurement results for X best beams. Summary of the Invention

[0004] A wireless transmit / receive unit (WTRU) can be configured to transmit messages associated with performing measurements on one or more candidate cells, and to determine configuration information associated with the one or more candidate cells. The configuration information includes one or more conditions associated with waypoints.

[0005] According to an exemplary aspect, the WTRU is configured to determine a first set of parameters and a second set of parameters for performing measurements on one or more candidate cells based on one or more conditions associated with waypoints; to perform one or more measurements on one or more candidate cells based on the first set of parameters; and to perform one or more measurements on one or more candidate cells based on the second set of parameters, provided that one or more conditions associated with waypoints are met. According to the exemplary aspect, the WTRU is also configured to send reports associated with the first set of parameters and the second set of measurements performed on the one or more candidate cells.

[0006] The WTRU can be configured to receive configuration information from the network. This configuration information may indicate a first Layer 1 / Layer 2 Triggered Mobility (LTM) measurement parameter set and a second LTM measurement parameter set to be applied when performing beam-associated measurements. The first LTM measurement parameter set and / or the second LTM measurement parameter set may include: Channel State Information (CSI) resources to be applied for one or more specific altitudes of the WTRU, sampling interval, sampling frequency, one or more offsets, number of beams, filter coefficients, trigger time, and / or the average duration of the measurement. The WTRU can be configured to receive indications of conditions associated with the WTRU's altitude, speed, and / or location. The WTRU can be configured to use the first LTM measurement parameter set to measure the beam when the conditions are not met or to use the second LTM measurement parameter set to measure the beam when the conditions are met. The WTRU can be configured to send beam measurements to the network based on the satisfaction of the conditions. These conditions may include the WTRU's periodicity, proximity to a specific waypoint, and / or altitude.

[0007] The WTRU can be configured to determine whether a condition is met based on the WTRU's altitude, speed, and / or position. The condition can be determined to be met when the WTRU exceeds a threshold altitude, exceeds a threshold speed, remains at a specific altitude for a specified time period, remains at a specific speed for a specified time period, arrives at a waypoint within a predetermined time, remains at a specific waypoint for a specified time period, changes speed by more than a predetermined value, changes altitude by more than a predetermined value, changes a timestamp associated with a specific waypoint by more than a predetermined value, and / or the WTRU's position is within a predetermined distance of the waypoint. The condition can also be determined to be met when the WTRU exceeds a predetermined speed range or a predetermined altitude range.

[0008] The WTRU can be configured to determine the reporting interval for transmitting measurements based on the stated conditions. The reporting interval can be associated with event-based reporting or periodic reporting. A first set of LTM measurement parameters may include a first carrier frequency for measuring Layer 1 / Layer 2 mobility, and a second set of LTM measurement parameters may include a second carrier frequency for measuring Layer 1 / Layer 2 mobility. This condition can be associated with the WTRU's height relative to a threshold. When the WTRU's height is below the threshold, the first carrier frequency can be used; when the WTRU's height is above the threshold, the second carrier frequency can be used. Attached Figure Description

[0009] Figure 1A This is a system diagram illustrating an exemplary communication system that can implement one or more of the disclosed embodiments.

[0010] Figure 1B This illustrates the possibility of implementation according to an embodiment. Figure 1A The system diagram shows an exemplary wireless transmit / receive unit (WTRU) used in the communication system.

[0011] Figure 1C This illustrates that, according to an embodiment, it is possible to Figure 1A The diagram shows a system diagram of an example radio access network (RAN) and an example core network (CN) used within a communication system.

[0012] Figure 1D This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shows another example RAN and another example CN used within the communication system shown.

[0013] Figure 2 This is a schematic diagram illustrating an exemplary high-level measurement model.

[0014] Figure 3 This is a schematic diagram illustrating an example of Layer 1 / Layer 2 triggered mobility (LTM) operation using carrier aggregation (CA).

[0015] Figure 4 This is a schematic diagram illustrating an exemplary LTM baseline process.

[0016] Figure 5 This is a schematic diagram illustrating an exemplary signaling flow used for flight path reporting.

[0017] Figure 6 This is a schematic diagram illustrating an example of performing a measurement based on satisfying conditions associated with a waypoint.

[0018] Figure 7 A schematic diagram illustrating an example of performing measurements based on conditions associated with WTRU speed. Detailed Implementation

[0019] Figure 1AThis diagram illustrates an exemplary communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables 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-Tail Unique Word DFT-Extended OFDM (ZT-UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

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

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

[0022] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of 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, i.e., one transceiver per sector of the cell. In embodiments, 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.

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

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

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

[0026] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as NR radio access, which can use a new radio (NR) to establish an air interface 116.

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

[0028] In other embodiments, base station 114a and wireless transmission / reception units 102a, 102b, and 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA 2000, CDMA 2000 1X, CDMA 2000 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 Rate GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0029] Figure 1A Base station 114B can be, for example, a wireless router, a home Node-B, a home eNode-B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business premises, home, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA 2000, GSM, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can have a direct connection to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN 106 / 115.

[0030] RAN 104 / 113 can communicate with CN 106 / 115, and can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 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. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113, which can utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

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

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

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

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

[0037] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, transceiver 120 can include multiple transceivers for enabling WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11).

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

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

[0040] 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) about the current location of the WTRU 102. In addition to, or alternatively to, the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or determine its location based on the timing of signals received from two or more neighboring base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0041] The processor 118 can also be connected to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0042] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., chokes) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In embodiments, WTRU 102 may include a half-duplex radio where the transmission and reception of some or all signals (e.g., signals associated with specific subframes for both uplink (e.g., for transmission) and downlink (e.g., for reception)) may occur.

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

[0044] RAN 104 may include eNode-Bs 160a, 160b, and 160c, but it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. Each eNode-B 160a, 160b, and 160c may each include one or more transceivers to communicate with radio transmit / receive units 102a, 102b, and 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

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

[0046] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is depicted as part of 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.

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

[0048] The SGW 164 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102B, and 102c, managing and storing the context of WTRUs 102a, 102B, and 102c, etc.

[0049] The SGW 164 can connect to the PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks such as the Internet 110 to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0050] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communication between WTRU 102a, 102b, 102c and traditional landline communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), or can communicate with an IP gateway that serves as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 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.

[0051] Although WTRU is Figure 1A-1D While described as a wireless terminal, it is anticipated that in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0052] In a representative embodiment, another network 112 may be a WLAN.

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

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

[0055] High-throughput (HT) STAs can 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.

[0056] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining adjacent 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels or by combining two non-consecutive 80 MHz channels; this is known as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segmented parser that divides the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. The streams can be mapped onto the two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0057] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV whitespace (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah can support metering-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities including support for certain and / or limited bandwidths (e.g., only support). MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0058] WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the 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 STAs operating in the BSS, supporting minimum bandwidth operating modes. In the 802.11ah example, for STAs supporting (e.g., only supporting) 1MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports 1 MHz operating mode) is transmitting to the AP, the entire available band can be considered busy even if most of the band remains idle and available.

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

[0060] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR wireless technology. RAN 113 can also communicate with CN 115.

[0061] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each of gNBs 180a, 180b, and 180c includes one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to 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, gNBs 180a, 180b, and 180c may implement Cooperative Multipoint (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

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

[0063] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without needing to access other RANs (e.g., eNode-B160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, and also with another RAN such as eNode-B160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement the DC principle to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, and one or more eNode-B160a, 160b, and 160c. In a non-standalone configuration, eNode-B160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

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

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

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

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

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

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

[0070] Given Figure 1A-1D and Figure 1A-1D The functions described herein with respect to one or more of the following: WTRU 102a-d, Base Station 114a-B, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-B, SMF 183a-B, DN 185a-B, and / or any other devices described herein may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0071] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. 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 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. Simulation devices can be directly coupled to another device for testing purposes and / or can perform tests using over-the-air wireless communication.

[0072] One or more emulation devices may 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, emulation devices may be used in test scenarios within test laboratories and / or non-deployment (e.g., testing) wired and / or wireless communication networks to perform tests on one or more components. One or more emulation devices may be test equipment. Emulation devices may transmit and / or receive data using direct RF connections and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0073] In the example, within RRC_CONNECTED, the WTRU can measure and / or detect multiple beams in a cell (e.g., at least one cell), and the measurement results (e.g., power values) can be averaged to derive cell quality. In doing so, the WTRU can be configured to consider a subset of the measured / detected beams. In the example, filtering can be performed at two distinct levels: beam quality is obtained at the physical layer, and then cell quality is obtained from multiple beams at the RRC level. In the example, cell quality can be derived from beam measurements for both serving and non-serving cells in the same manner. In the example, if the WTRU is configured to do this via a gNB, the measurement report can include measurement results for X optimal beams.

[0074] Figure 2 This shows an example illustration of the corresponding high-level measurement model 200. In the example, K beams may correspond to measurements of SSB and / or CSI-RS resources configured for L3 mobility and detected by the WTRU at L1. Figure 2 In the diagram, A represents a measurement within the physical layer (e.g., a beam-specific sample). Layer 1 filtering illustrates the internal Layer 1 filtering of the input measured at point A; the precision of this filtering can depend on the implementation (e.g., related to the WTRU implementation). In this example, how measurements are performed in the physical layer via the implementation (e.g., input A and Layer 1 filtering) is not bound by standards. Figure 2In Figure A1, measurements (e.g., beam-specific measurements) that can be reported from Layer 1 to Layer 3 after filtering in Layer 1 are shown. Figure 2 In this example, beam combining / selection can occur when beam-specific measurements are combined to derive cell quality. The behavior of beam combining / selection can be standardized, and the module's configuration can be provided by RRC signaling. In the example, the reporting period at B can be equal to one measurement period at A1. At B, a measurement (e.g., cell quality) can be derived from a beam-specific measurement, and after beam combining / selection, this measurement can be reported to Layer 3.

[0075] In the example, layer 3 filtering for cell quality can be performed by filtering the measurements provided at point B. In the example, the behavior of the layer 3 filter can be normalized, and the configuration of the layer 3 filter can be provided via RRC signaling. In the example, the filtering reporting period at point C can be equal to one measurement period at point B. Figure 2 In the diagram, C represents the measurement after processing in the Layer 3 filter. The reporting rate can be the same as at point B, and this measurement can be used as input to one or more evaluation or reporting criteria. In the example, the evaluation of the reporting criteria can be performed by checking whether an actual measurement report is needed at point D. In the example, the evaluation of the reporting criteria can be based on more than one measurement stream at reference point C (e.g., for comparison between different measurements). In the example, the measurement stream can refer to measurements available at point C associated with different cells (e.g., they can be averaged in parallel). For example, Figure 2 This can be applied to each cell measurement or each measurement flow. The evaluation of the reporting criteria can be represented as inputs at points C and / or C1. In the example, the WTRU can evaluate the reporting criteria at least whenever a new measurement result is reported at point C and / or C1. The reporting criteria can be standardized and / or configured to be provided by RRC signaling (e.g., WTRU measurements).

[0076] exist Figure 2 In the example, at point D, measurement report information (e.g., a message) can be transmitted over the wireless interface. L3 beam filtering can occur as a filtering process that can be performed on a measurement (e.g., a beam-specific measurement) provided at point A1. In this example, the behavior of the beam filter can be normalized, and the configuration of the beam filter can be provided by RRC signaling. Figure 2 The filter reporting period at point E shown can be equal to one measurement period at point A1. In the example, E can represent the measurement after processing in the beam filter (e.g., a beam-specific measurement). In the example, the reporting rate can be the same as the reporting rate at point A1. This measurement result can be used as input to select X measurements to report. Figure 2In this example, beam selection for beam reporting involves selecting X measurements from those provided at point E. The behavior of beam selection can be standardized, and the configuration of this module can be provided via RRC signaling. Figure 2 In the example, F indicates when beam measurement information might be included in a measurement report on the radio interface (e.g., a measurement report transmitted on the radio interface). In this example, Layer 1 filtering may introduce a specific level of measurement averaging. In this example, how and when the WTRU performs the required measurements can be implementation-specific so that the output at B can meet one or more performance requirements. In this example, Layer 3 filtering for the cell quality and / or related parameters used may not introduce any delay in sample availability between B and C. In this example, the L3 beam filtering and / or related parameters used may not introduce any delay in sample availability between E and F.

[0077] In the example, a measurement report can be characterized by one or more of the following. For example, a measurement report can include a measurement identifier of an associated measurement configuration that triggered the report. For example, the cell and / or beam measurements to be included in the measurement report can be configured by the network. For example, the number of non-serving cells to be reported can be limited by the network through configuration. For example, cells belonging to an exclusion list configured by the network cannot be used in event assessments and reports. For example, when the network configures an allow list, one or more (e.g., only one) cells belonging to that allow list can be used in event assessments and reports. For example, beam measurements to be included in the measurement report can be configured by the network (e.g., only beam identifier, measurement result and beam identifier, or no beam report).

[0078] In the example, intra-frequency adjacent (cell) measurements and inter-frequency adjacent (cell) measurements can be defined as follows. For example, for SSB-based intra-frequency measurements, if the center frequency of the serving cell's SSB is the same as the center frequency of the adjacent cell's SSB, and the subcarrier spacing of the two SSBs is also the same, then the measurement can be defined as an SSB-based intra-frequency measurement. For example, for SSB-based inter-frequency measurements, if the center frequency of the serving cell's SSB is different from the center frequency of the adjacent cell's SSB, or the subcarrier spacing of the two SSBs is different, then the measurement can be defined as an SSB-based inter-frequency measurement. For SSB-based measurements, one measurement object can correspond to one SSB, and the WTRU can treat different SSBs as different cells.

[0079] For CSI-RS-based in-frequency measurements, a measurement can be defined as a CSI-RS-based in-frequency measurement if one or more of the following conditions are true: The subcarrier spacing of the CSI-RS resources configured for measurement on the neighboring cell can be the same as the SCS of the CSI-RS resources indicated for measurement on the serving cell. For a 60kHz subcarrier spacing, the CP type of the CSI-RS resources configured for measurement on the neighboring cell can be the same as the CP type of the CSI-RS resources indicated for measurement on the serving cell. The center frequency of the CSI-RS resources configured for measurement on the neighboring cell can be the same as the center frequency of the CSI-RS resources indicated for measurement on the serving cell.

[0080] For CSI-RS-based inter-frequency measurements, if the measurement is not a CSI-RS-based intra-frequency measurement, it can be defined as a CSI-RS-based inter-frequency measurement. In the example, extended CP for CSI-RS-based measurements may not be supported.

[0081] In the example, whether the measurement is non-gap-assisted or gap-assisted can depend on the capabilities of the WTRU, the WTRU's active BWP, and the current operating frequency. For example, for SSB-based inter-frequency measurements, if the WTRU reports measurement gap requirement information, a measurement gap configuration can be provided based on that information. The measurement gap configuration can be provided if the WTRU supports (e.g., only supports) per-UE measurement gaps; or if the WTRU supports per-FR measurement gaps, and either of the serving cells is within the same frequency range of the measurement object. For example, for SSB-based intra-frequency measurements, if the WTRU reports measurement gap requirement information, a measurement gap configuration can be provided based on that information. For example, a measurement gap configuration can be provided if, in addition to the initial BWP, either of the BWPs configured by the WTRU does not include the frequency domain resources of the SSB associated with the initial DL BWP. In the example, in a non-gap-assisted scenario, the WTRU may be able to perform such a measurement without a measurement gap. In a gap-assisted scenario, the WTRU may not be assumed to be able to perform such a measurement without a measurement gap.

[0082] In the example, inter-cell beam management can be used, which manages beams in CA scenarios but may not support cell changes / additions. In the example, the specified mechanisms and procedures for L1 / L2-based inter-cell mobility for mobility latency reduction can be specified based on the following: For example, to specify L1 / L2-based inter-cell mobility mechanisms and procedures for mobility latency reduction, the following can be performed: configuring and maintaining multiple candidate cells to allow for rapid application of candidate cell configurations; dynamic handover mechanisms between candidate serving cells (including SpCell and SCell) for potentially applicable scenarios based on L1 / L2 signaling; L1 enhancements for inter-cell beam management, including L1 measurement and reporting, and beam indication; advance timing management; and, if necessary, CU-DU interface signaling supporting L1 / L2 mobility. For example, early RAN2 involvement may be necessary, including further clarifying the possibility of interaction between the current bullet and previous bullets.

[0083] For example, FR2-specific enhancements may not be excluded, if any. For example, L1 / L2-based inter-cell mobility procedures may be applicable to the following scenarios: stand-alone, CA, and NR-DC scenarios, where the serving cell changes within a CG DU and between DUs within a CU (e.g., applicable to stand-alone and CA: no new RAN interface is expected); both intra-frequency and inter-frequency; both FR1 and FR2; the source and target cells may be synchronous or asynchronous; and excluding inter-CU scenarios.

[0084] L1 / L2-based mobility was initially introduced in Release 17 (R17), where inter-cell beam management addresses intra-DU and intra-frequency scenarios. In this context, the serving cell can remain unchanged (e.g., it's impossible to change the serving cell using L1 / 2-based mobility). In FR2 deployments, CA (Cyclic Array Controller) can typically be used to utilize available bandwidth, such as aggregating multiple CCs within a single frequency band. These CCs can typically transmit with the same analog beam pair (e.g., gNB beam and WTRU beam). The WTRU can be configured with TCI states (e.g., a considerable number, such as 64) for PDCCH and PDSCH reception. Each TCI state can include an RS (Representative RS) or SSB (Signal Sub-Brain), which the WTRU can reference to set its beam. In the example, the SSB can be associated with a non-serving PCI. MAC signaling can activate the TCI states for Coreset / PDCCH. A MAC CE indicating the TCI state associated with a non-serving PCI can support PDCCH reception from the non-serving cell. MAC signaling can activate a subset (e.g., up to) of the eight TCI states used for PDSCH reception. DCI can indicate which of the eight TCI states is being used. A unified TCI state with different update mechanisms (e.g., DCI-based) can be supported, but without multiple TRPs. A unified TCI state with multiple TRPs can also be supported.

[0085] LTM can improve handover latency. For example, for conventional L3 handover or conditional handover, the WTRU can first send a measurement report using RRC signaling. In response, the network can provide further measurement configurations and potential conditional handover configurations. For regular handover, after the WTRU reports that the cell meets the configured radio quality criteria using RRC signaling, the network can provide the configuration for the target cell. For conditional handover, to reduce the handover failure rate due to delays caused by sending measurement reports and then receiving RRC reconfiguration, the network can pre-provide the target cell configuration and measurement criteria that determine when the WTRU should trigger CHO configuration. In the example, both L3 methods may experience delays due to, for example, sending measurement reports and receiving target configurations, especially in the case of regular (unconditional) handover.

[0086] In the example, the purpose of LTM could be to allow for the rapid application of configurations for candidate cells, which could include dynamic handovers between SCells and PCells (e.g., switching roles between SCells and PCells) without performing RRC signaling. Inter-CU cases may not be included, as this could require relocating the PDCP anchor and may have already been excluded from the work items. Therefore, an RRC-based approach may be needed to at least support inter-CU handover.

[0087] Using the traditional L3 handover mechanism, currently active SCells can be released before the WTRU completes handover to the target cell in the coverage area of ​​the new site, and can be added back (e.g., only) after a successful handover, which may result in reduced throughput during the handover. L1 / 2 enables CA operation immediately after a change of serving cell.

[0088] Figure 3 An exemplary LTM operation 300 is shown, whereby candidate cell groups can be configured by RRC, and dynamic handover between PCell and SCell can be achieved using L1 / 2 signaling.

[0089] Figure 4 An exemplary baseline LTM process 400 is illustrated. Figure 4As shown, the LTM procedure 400 can be as follows: At 410, WTRU 402 can initiate RRC connection mode. At 412, WTRU 402 can send a MeasurementReport message to gNB 404. gNB 404 can decide to use LTM and initiate LTM candidate preparation at 414. At 416, gNB 404 can transmit an RRCReconconfiguration message to WTRU 402. The RRCReconconfiguration message may include the configuration of one or more LTM candidate target cells. At 418, WTRU 402 can store the configuration of the LTM candidate target cells and transmit an RRCReconfigurationComplete message to gNB 404. At 420, WTRU 402 can, for example, perform DL synchronization and / or TA acquisition with the candidate target cells before receiving an LTM cell handover command. In the example, DL synchronization of candidate cells before the cell handover command can be supported at least based on SSB. In the example, TA acquisition of candidate cells prior to an LTM cell handover command can be supported at least based on the RACH of the PDCCH instruction, where the PDCCH instruction can be triggered by the source cell (e.g., triggered only by the source cell). At 422, WTRU 402 can perform one or more L1 measurements on the configured LTM candidate target cell and can transmit one or more low-layer measurement reports to gNB 404. At 424, gNB 404 can make an LTM decision, for example, based on the low-layer measurement reports. At 426, gNB 404 can decide to perform an LTM cell handover to the target cell and transmit the MAC CE that triggers the LTM cell handover by including the candidate configuration index of the target cell. WTRU 402 can switch to the configuration of the LTM candidate target cell. At 430, for example, if the TA is unavailable, WTRU 402 can perform a random access procedure for the target cell. At 432, WTRU 402 can indicate the successful completion of the LTM cell handover to the target cell.

[0090] Unmanned aerial vehicles (UAVs) operating at altitudes up to 300m (e.g., airborne WTRUs) can be associated with one or more use cases, including drone operation, personal entertainment for flight experiences, and cargo delivery. As a foundation for these applications, remote control and data transmission capabilities can be key aspects of enhancements, particularly UL and DL interference and mobility. Airborne WTRUs can support altitude-triggered measurement reporting based on WTRU capabilities. In the example, two altitude-based events can be defined. For example, in altitude-based event 1, the airborne WTRU altitude may become above an absolute threshold. In altitude-based event 2, the airborne WTRU altitude may become below an absolute threshold. In the example, the altitude threshold can be configured in MeasConfig via heightThreshRef and supports values ​​ranging from -420m to 8880m in 300m increments. In the example, the WTRU can be configured in ReportConfigEUTRA with offsets h1-ThresholdOffset and h2-ThresholdOffset, respectively, applied during event evaluation, and hysteresis parameters h1-Hysteresis and h2-Hysteresis.

[0091] In the example, the WTRU can be configured to include additional information (such as WTRU altitude, location, and horizontal / vertical velocity) in the measurement report. For instance, location reporting can be supported via a LocationInfo IE, which can be used to transmit detailed location information available at the WTRU to correlate measurements with WTRU location information. In the example, available information may include WTRU location information (e.g., via LocationCoordinates) and WTRU azimuth and horizontal velocity (e.g., via HorizontalVelocity). In the example, vertical information is reported via verticalVelocityInfo. verticalVelocityInfo can include a choice between the parameters verticalVelocity (which may include, for example, WTRU orientation, horizontal / vertical velocity, and vertical direction) and verticalVelocityAndUncertainty (which may include, for example, information within verticalVelocity and uncertainties in horizontal and vertical velocities).

[0092] Figure 5An example illustration of a signaling flow 500 for flight path reporting is shown. In the example, flight path reporting for an airborne WTRU can be supported based on WTRU capabilities. Flight path information may include multiple waypoints, which can be 3D locations / coordinates. At 510, WTRU 5002 may indicate whether the flight path information is available via the RRCConnectionReconfigurationComplete, RRCConnectionReestablishmentComplete, RRCConnectionResumeComplete, or RRCConnectionSetupComplete messages. The flight path information allows the network to determine its availability after a connection is established (e.g., immediately following the connection), which enables subsequent flight path reporting configuration and requests.

[0093] In step 512, gNB 504 can send a WTRU Information Request message to WTRU 502. The E-UTRAN (e.g., gNB 504) can request WTRU 502 to report flight path information via the flightPathInfoReq in the WTRUInformationRequest message. In step 514, WTRU 502 can send a WTRU Information Response message to gNB 504. WTRU 502 can include a flightPathInfoReport in the WTRUInformationResponseMessage based on the request to report WTRU flight path information. This flightPathInfoReport includes one or more (e.g., all) available waypoints up to a configured maximum. This information is useful for the network, for example, for collision avoidance, resource provisioning, and / or WTRU configuration. In the example, up to 20 waypoint locations can be configured in the flight path report. WTRU 502 can be configured to include timestamp information associated with each waypoint via includeTimeStamp in FlightPathInformationReportConfig. Timestamps can improve the predictability of WTRU location at a given time, further aiding in WTRU configuration planning and future resource allocation. In the example, timestamp information may not always be known, and if such information is available at WTRU 502, it may be included (e.g., only) in the flight path report.

[0094] In the example, the over-the-air WTRU can be configured with RRM events (e.g., A3, A4, or A5) that trigger a measurement report when the per-cell RSRP value for a configured number of cells meets the configured event. Once the measurement report is sent, the list of triggered cells can be updated when subsequent cells complete the event. In the example, no additional measurement report needs to be sent if the list of triggered cells remains greater than the configured number of cells. In the example, the number of triggered cells required for the measurement report can be provided via `numberOfTriggeringCells` in `ReportConfigEUTRA` and can vary from 2 to a maximum of 8.

[0095] In the example, additional considerations for UAV may include altitude-related parameter scaling, user consent for location reporting, flight path updates after initial reporting, and / or beamforming considerations and reporting of departure conditions in the number of triggering cells. In the example, UAV enhancements may include NR updates for flight path reporting (e.g., location coordinates and timestamps) and / or flight path information. UAV enhancements may include mobility control, such as altitude-based parameter scaling, altitude-based events based on WTRU location information, and / or H1 above (e.g., greater than) a threshold, and H2 below a threshold. UAV enhancements may include interference control (e.g., the number of triggered cells (A3, A4, A5), the list of triggered cells in the MR), which may include potential new events B1 / B2 (inter-RAT) and / or beamstriking.

[0096] In this example, mobility control and interference control are part of the UAV's operation. RAN-level issues regarding UAV and UAV support could include interference and excessive measurement reporting. Due to the UAV's altitude, many cells may appear to have roughly the same strength, potentially leading to continuous fulfillment of measurement events and frequent measurement reports. If L1 / L2-triggered mobility is used for the UAV, this problem could be amplified, considering that the WTRU might expect to report L1 / L2 measurements of the cell / beam to enable the network to trigger LTM. In this example, this could result in LTM being triggered by the network, potentially causing ping-pong handovers and latency due to interruptions (e.g., the need for MAC or other protocol layer resets when the cell changes). Consequently, a dedicated final measurement procedure for LTM might need to be enhanced to avoid interference and excessive signaling and power consumption for the UAV WTRU performing continuous measurement reporting.

[0097] In the example, the WTRU can determine which parameters to use when performing beam measurements based on whether conditions associated with the WTRU have been met (e.g., satisfied). One or more WTRU autonomous LTM measurement parameters can be updated based on conditions (e.g., altitude or waypoint conditions). The WTRU can determine one or more LTM measurement parameters based on altitude, speed, and / or location. For example, altitude can be the altitude associated with the WTRU (e.g., absolute altitude or relative altitude). Speed ​​can be the speed associated with the WTRU (e.g., absolute speed or relative speed). Location can be the location associated with the WTRU (e.g., absolute location or relative location). The WTRU can receive configuration information, for example, from the network. This configuration information can indicate multiple sets of LTM measurement parameters to be applied when performing beam-associated measurements (e.g., a first set of LTM measurement parameters and a second set of LTM measurement parameters). LTM measurement parameters may include: one or more CSI resources to be applied for one or more specific altitudes of the WTRU, sampling interval, sampling frequency, one or more offsets, number of beams, one or more filter coefficients, trigger time, and / or the average duration of the measurement. For example, configuration information may indicate a first set of LTM measurement parameters and a second set of LTM measurement parameters (e.g., CSI resources, number of beams, filter coefficients, etc.) to be applied when measuring beams and / or cells (e.g., RSRP). For example, the WTRU may receive indications of conditions (e.g., configuration for conditions) associated with one or more of the WTRU's altitude, speed, and / or location (e.g., with respect to waypoints). Additionally or alternatively, this indication may be associated with multiple conditions related to the WTRU's altitude, speed, and / or location. For example, the conditions may be associated with the WTRU's altitude (e.g., relative altitude), speed (e.g., relative speed), and / or location (e.g., relative position). The WTRU may be configured to report LTM measurements based on whether conditions are met (e.g., satisfied). For example, when an associated reception condition is not met, the WTRU may perform measurements associated with the beam (e.g., the cell) using the first set of LTM measurement parameters. The WTRU may determine whether the condition has been met. For example, the condition can be determined to be met when the WTRU exceeds a threshold altitude, when the WTRU exceeds a threshold speed, when the WTRU is at a specific altitude for a certain period of time, when the WTRU is at a specific speed for a certain period of time, when the WTRU arrives at a waypoint within a predetermined time, when the WTRU is at a specific waypoint for a certain period of time, when the WTRU changes speed greater than a predetermined value, when the WTRU changes altitude greater than a predetermined value, when the timestamp associated with a specific waypoint changes greater than a predetermined value, and / or when the WTRU's position is within a predetermined distance from the waypoint.Additionally or alternatively, the condition may be determined to be met when the WTRU exceeds a predetermined speed range and / or when the WTRU exceeds a predetermined height range.

[0098] When the associated reception conditions are met, the WTRU can perform measurements associated with the beam (e.g., the cell's) using a second set of LTM measurement parameters. The WTRU can report the measurements (e.g., beam measurements) to the network, for example, based on reporting conditions, as described herein.

[0099] In the example, the L1 measurement reporting function / behavior may depend on the number of candidate beams / cells and / or one or more conditions associated with the candidate beams / cells (e.g., reporting conditions). The WTRU may transmit beam measurements to the network based on one or more conditions that are met. For example, the WTRU may determine its LTM reporting behavior (e.g., one or more reporting conditions) based on the number of specific cells / beams that meet the measurement conditions and / or the specific cell / beam. For example, the WTRU may determine the reporting interval for transmitting measurements (e.g., beam measurements) based on the reporting conditions. This reporting interval may be associated with event-based reporting or periodic reporting. The reporting conditions may include the WTRU's periodicity, proximity to a specific waypoint, and / or altitude.

[0100] The WTRU can receive configuration (e.g., configuration information) associated with a first reporting behavior and a second reporting behavior (e.g., reporting period, number of cells / beams included in the report). The WTRU can receive a threshold number of cells / beams in its candidate set whose measurements exceed a measurement threshold. For example, the configuration information may include the threshold number of cells / beams. When the number of cells / beams with measurements exceeding the measurement threshold exceeds the threshold number, the WTRU can determine to report the measurement. For example, when the number of cells / beams does not exceed the threshold number of cells / beams, the WTRU can perform measurement reporting according to the first configured reporting behavior. For example, when the number of cells / beams (e.g., associated with a candidate set and having measurement quality exceeding the measurement threshold) exceeds the threshold number of cells / beams, the WTRU can perform measurement reporting according to the second configured reporting behavior.

[0101] In the example, L1 measurement reporting functionality / behavior may depend on altitude conditions, speed conditions, and / or waypoint conditions. For example, the WTRU may determine its LTM reporting behavior (e.g., one or more reporting conditions) based on the WTRU's altitude (e.g., relative altitude), speed (e.g., relative speed), and / or location (e.g., relative location). The WTRU may receive configurations (e.g., configuration information indicating the first and second reporting behaviors) for a first reporting behavior and a second reporting behavior (e.g., reporting period, number of cells / beams included in the report). For example, reporting conditions may include the WTRU's periodicity, proximity to a specific waypoint, and / or altitude. The first reporting behavior may be associated with the WTRU not meeting the altitude and / or waypoint conditions. The WTRU may receive configurations of conditions associated with the WTRU's altitude (e.g., relative altitude), speed (e.g., relative speed), and / or (e.g., associated with a waypoint) location (e.g., relative location). When the conditions associated with the WTRU's altitude, speed, and / or location are not met, the WTRU may perform measurement reporting (e.g., sending beam measurements to the network) according to the first configured reporting behavior. When conditions associated with the WTRU's altitude, speed, and / or location are met, the WTRU can perform measurement reporting (e.g., sending beam measurements to the network) according to the reporting behavior of the second configuration.

[0102] The following are examples of the terms and definitions used in this document. In the context of a UAV, a "waypoint" can refer to a set of 3D coordinates that identify a point in physical space. A "flight path" can include one or more waypoints and may optionally include a timestamp indicating the location and the time the WTRU expects to be at that location. For example, each waypoint can be numbered or indexed to uniquely identify it. "Performing LTM" or "performing an LTM procedure" can refer to the execution of... Figure 4 The steps described herein. For example, “performing LTM” or “performing an LTM procedure” may refer to early synchronization of one or more candidate cells in the DL and / or UL, performing L1 measurements and reporting on one or more candidate cells, and / or handover between candidate cells (e.g., performing a handover). In the example, “performing LTM” may mean that the WTRU moves / handover between multiple candidate cells during the procedure.

[0103] One or more “candidate cell sets” can refer to a group of more than one RRC configuration, which may correspond to a handover configuration for one or more candidate SpCells and / or SCells. In the example, a candidate cell set can be modeled or received as one or more complete RRC reconfiguration messages, one or more cell group configurations, and / or one or more cell configurations. For example, each of the candidate cell configurations may include a candidate configuration identifier, and each of the candidate cell groups may include a candidate cell group identifier. If grouping is performed at the RRC, handover between different candidate cell sets may include updating the serving cell index or candidate configuration index, which can be used in L1 and MAC signaling to reference a specific index. In the example, the MAC CE that triggers the reconfiguration may include a candidate configuration index that informs the WTRU which cell the reconfiguration will be performed on. In the example, one or more candidate cell groups can be configured as a single list or group of candidate cell configurations at the RRC. Grouping may occur during the early synchronization or LTM execution phase (e.g., rather than the configuration phase). For example, the candidate cell set can be considered a single group in terms of the RRC configuration list or groups, and the cells selected for performing early synchronization, L1 measurement, and / or LTM execution can depend on multiple subsets of the overall candidate cell list, further grouped. For example, the group itself may not be modeled using candidate configuration identifiers at the RRC. For example, the group may be executed as part of an early synchronization or LTM execution process. In this application, LTM candidate configurations can be applied to any type of pre-configured cell information. For example, the WTRU can be configured with one or more conditional reconfigurations, such as Conditional Handover (CHO), Conditional PSCell Increase (CPA), and / or Conditional PSCell Change (CPC), which can be effective before and / or after cell changes, or in certain cells.

[0104] In this example, the L1 measurement described herein may include measurements of RSRP, RSSI, etc., which can be performed by the WTRU of a cell, beam, cell set, and / or beam set. In this example, such an L1 measurement can be similar to an L3 measurement reported in an RRM, differing in filtering, the reference signal for the measurement, the reporting mechanism, etc.

[0105] This paper describes a solution that can trigger reports and / or define WTRU behavior based on specific waypoints (e.g., coordinates in a UAV path). For example, such waypoints can be used interchangeably with locations. For instance, this solution can use any mechanism to define the geographic location of the WTRU in space.

[0106] Here, measurement may refer to L1 measurement for LTM. Some of the solutions in this article can also be applied to RRM / L3 measurement as well as other measurements (e.g., speed, position, height, flow rate, etc.).

[0107] In the examples presented in this paper, the WTRU can be configured with altitude-based conditions for determining parameters, behaviors, etc. In these examples, altitude-based conditions can be configured by the network (e.g., in RRC) or can be predefined. For example, altitude-based conditions can be configured by the network and then enabled / disabled via NW signaling (e.g., MAC CE, DCI, SIB, RRC, etc.). For example, altitude-based conditions can be enabled / disabled by another condition presented in this paper (e.g., speed-based conditions, waypoint-based conditions, etc.).

[0108] Height-based conditions can take the form of WTRUs reaching at least or at most a specific height. For example, a height-based condition could be that the WTRU height is above a configured threshold, the WTRU height is below a configured threshold, and / or the WTRU height is between two configured thresholds. Height-based conditions can also take the form of changes in WTRU height. For example, a height-based condition could be that the WTRU height may change by an amount greater than a threshold within a configured time period / duration; the WTRU height may increase by an amount greater than a threshold within a configured time period / duration; the WTRU height may decrease by an amount greater than a threshold within a configured time period / duration; a change in WTRU height may have increased by an amount greater than a threshold within a configured time period / duration; and / or a change in WTRU height may have decreased by an amount greater than a threshold within a configured time period / duration.

[0109] Height-based conditions can take the form of the duration the WTRU remains at a specific height. For example, height-based conditions could be: the WTRU's height remains the same value for at least a configured time period; the WTRU's height remains within a configured range for at least a configured time period; the WTRU's height changes less than a configured amount within a configured time period; and / or the WTRU has maintained the maximum amount of time at a specific height within a configured time period.

[0110] In the examples presented in this paper, the WTRU can be configured with waypoint-based conditions for determining parameters, behaviors, etc. These waypoint-based conditions can be configured by the network (e.g., in RRC) or can be predefined. These waypoint-based conditions can be configured by the network and then enabled / disabled via NW signaling (e.g., MAC CE, DCI, SIB, RRC, etc.). These waypoint-based conditions can be enabled / disabled by another condition presented in this paper (e.g., speed-based conditions, altitude-based conditions, etc.).

[0111] Waypoint-based conditions can take the form of the WTRU arriving at (e.g., given coordinates) and / or being near a waypoint, which may have been reported earlier in the WTRU's flight path. This condition can be configured for one or more specific waypoints, or it can be generalized for any number of waypoints. For example, the condition could be that the WTRU might be located at a specific waypoint, or that the WTRU is within a specifically configured distance from the waypoint.

[0112] Waypoint-based conditions can be in the form of arrival time at the waypoint or duration of stay at the waypoint. For example, waypoint-based conditions could be: the WTRU will be within a configured distance from the waypoint for less than a configured threshold time; the WTRU will remain within a configured distance from the specific waypoint for at least a configured time period; the WTRU will not exceed a configured threshold time within a configured distance from the specific waypoint; and / or the WTRU will remain within a configured distance from the specific waypoint for less than a configured time period.

[0113] Waypoint-based conditions can be in the form of reported waypoint changes. For example, waypoint-based conditions could be: a waypoint change by at least a configured distance, a time stamp associated with a waypoint change by at least a configured time, and / or WTRU skipping a waypoint (e.g., arriving at a second waypoint that was expected to be reached after the first waypoint before arriving at the first waypoint, etc.).

[0114] In the examples presented in this paper, the WTRU can be configured with speed-based conditions for determining parameters, behaviors, etc. For example, speed-based conditions can be configured by the network (e.g., in RRC) or can be predefined. These speed-based conditions can be configured by the network and then enabled / disabled via NW signaling (e.g., MAC CE, DCI, SIB, RRC, etc.). These speed-based conditions can also be enabled / disabled by other conditions presented in this paper (e.g., altitude-based conditions, waypoint-based conditions, etc.).

[0115] Speed-based conditions can be in the form of the WTRU reaching at least or at most a specific speed. For example, speed-based conditions could be: the WTRU's speed is higher than a configured threshold, the WTRU's speed is lower than a configured threshold, and / or the WTRU's speed is between two configured thresholds.

[0116] Speed-based conditions can be the form of WTRU speed changes (e.g., acceleration / deceleration). For example, speed-based conditions could be: the WTRU speed may change by an amount greater than a threshold over a time period; the WTRU speed may increase by an amount greater than a threshold over a time period; and / or the WTRU speed may decrease by an amount greater than a threshold over a time period.

[0117] Speed-based conditions can take the form of the duration for which the WTRU maintains a specific speed. For example, speed-based conditions could be: the WTRU's speed remains the same for at least a configured time period; the WTRU's speed remains within a configured range for at least a configured time period; and / or the WTRU's speed changes by a greater than / less than a configured amount within a configured time period.

[0118] Here, LTM measurement parameters can include any parameters or values ​​used to generate L1 / L2 measurements. For example, LTM measurement parameters can be: candidate target cells to be measured. For example, the WTRU can be configured to have one or more lists of cells, frequencies, or RATs to be measured. These cells may or may not be among the LTM candidate cells.

[0119] In the example, LTM measurement parameters may include a trigger time (TTT) associated with an event. For example, the WTRU may be configured with one or more values ​​for the trigger time associated with an event and reporting or other actions, such as initiating synchronization, changing the number of candidate measurements, etc. In the example, LTM measurement parameters may include the number of beams averaged / used to generate cell measurements. For example, the WTRU may be configured to have one or more values ​​for the number of beams (e.g., maximum number of beams) to average to generate cell measurements, or the number of beams considered when selecting beam measurements. In the example, LTM measurement parameters may include hysteresis for triggering or canceling conditions. For example, the WTRU may be configured to have one or more hysteresis values ​​used to determine when a measurement should trigger a condition. In the example, LTM measurement parameters may include the number of samples to be averaged to generate measurements. For example, the WTRU may be configured to have one or more samples to be used when generating measurements (e.g., over time, across different resources, etc.) (e.g., the number of samples to be averaged). In the example, LTM measurement parameters may include one or more coefficients used in averaging / filtering. For example, a WTRU can be configured with one or more sets of filter coefficients. Specifically, the WTRU can use either a first configured set of filter coefficients or a second set of filter coefficients.

[0120] In the example, LTM measurement parameters may include the time difference between averaged samples. For example, the WTRU may be configured to have different values ​​for the time difference between samples used to perform the measurement. For example, the WTRU may be configured to use certain specific samples when determining the average. In the example, LTM measurement parameters may include measurement offsets. For example, the WTRU may be configured with different measurement offsets to apply (e.g., to the serving cell, neighboring cells, a specific frequency, a specific RAT, etc.). For example, the WTRU may be configured with different cells whose measurement offsets (e.g., configured by the cell) should be applied at a given time. Specifically, the WTRU may select one cell or another cell and apply the measurement offset configured by / for the cell. In the example, LTM measurement parameters may include one or more thresholds for triggering measurement reporting / indication. For example, the WTRU may be configured with different absolute / relative thresholds for signal levels to trigger measurement reporting (e.g., absolute threshold for the serving cell, absolute threshold for neighboring cells, relative threshold between the serving cell and neighboring cells, etc.). In the example, LTM measurement parameters may include CSI measurement configurations. In the example, LTM measurement parameters may include a set of aperiodic CSI trigger states. In the example, LTM measurement parameters may include at least one CSI reporting configuration or at least one of its parameters, such as: period and offset, resources for channel measurements (e.g., SSB or CSI-RS resource set), CSI-IM (CSI-Interference Measurement) resources for interference measurements, NZP (Non-Zero Power) CSI-RS resources for interference measurements, and / or the number of reports. In the example, LTM measurement parameters may include a set of TCI states associated with the CSI-RS resources used for channel or interference measurements.

[0121] Here, LTM reporting functionality / behavior may include any different behaviors related to how L1 measurements are reported to the network for LTM purposes. For example, the WTRU may determine any of the following based on conditions: In the case of reporting intervals, the WTRU may be configured with different reporting intervals associated with L1 measurements (e.g., time between consecutive reports), and / or the WTRU may be configured with different measurement reporting prohibition timers (e.g., the minimum amount of time the WTRU must wait after sending a measurement report before sending the next, etc.). In the case of message format used for reporting, the WTRU may use different numbers of bits to represent quantities (e.g., altitude, RSRP measurement, etc.). For example, the WTRU may use different formats of MAC CE to report measurements. In the case of how to determine which measurements to include, specifically, determining the number of cells / beams to report, the WTRU may be configured to have a maximum / minimum number of beams / cells to report. In the case of how to determine which measurements to include, specifically, determining the frequency of cells / beams to report, the WTRU may be configured to report cells / beams associated with that frequency (e.g., only within that frequency). Additionally or alternatively, the WTRU can be configured to report cells / beams associated with frequency inter-frequency (e.g., frequency inter-frequency only). Alternatively, the WTRU can be configured to report cells / beams associated with frequencies determined based on conditions for one or more configurations. The WTRU can be configured to report cells / beams associated with a specific RAT (e.g., EUTRA cells, NR cells, etc.). In the example, regarding how to determine which measurements to include, an acceptability criterion for reporting cell / beam measurements is determined. For example, the WTRU can be configured with thresholds such as RSRP / RSRQ / RSSI, above which cells / beams can be reported. In the example, regarding how to determine which measurements to include, specifically, it is determined how to select which cells / beams to report when the required / maximum number meets the criteria. For example, under one condition, the WTRU can report N optimal beams, while under another condition, the WTRU can report N beams that are likely closest to the average.

[0122] In the example, WTRU autonomous LTM measurement parameter updates can be based on altitude, speed, or waypoint conditions. For instance, WTRU can determine one or more parameters for performing measurements based on conditions associated with waypoints.

[0123] In the example, the WTRU can determine the parameters used to perform LTM measurements based on conditions associated with waypoints. Specifically, the WTRU can determine the values ​​or configurations of any measurement parameters defined herein based on conditions associated with waypoints.

[0124] In the example, the WTRU can be configured with a set of filter coefficients to be applied for one or more specific waypoints, offsets to measurements applied to the serving cell or neighboring cells, offsets to measurements applied to a specific frequency, measurement sampling interval / frequency, and / or the average duration of the measurements. If the WTRU is close to a waypoint (e.g., the current distance from the waypoint is less than a configured threshold), the WTRU can apply the configured measurement parameters associated with that waypoint.

[0125] For example, a WTRU can be configured with a first set of filter coefficients for a first waypoint (e.g., near a first waypoint), a second set of filter coefficients for a second waypoint (e.g., near a second waypoint), and so on. Such coefficients can be configured to the WTRU in dedicated RRC signaling, where the WTRU can be configured with a set of filter coefficients for each waypoint reported by the WTRU in its flight path. The WTRU can also be configured to have a distance to a specific waypoint, at which each set of filter coefficients is used. If the WTRU is within the configured distance to a specific waypoint, the WTRU can use the set of filter coefficients associated with that waypoint; otherwise, the WTRU can use another set of filter coefficients (e.g., a default set, or a set separately configured for use outside of waypoints). The WTRU can also be configured to have a specific distance threshold for each waypoint individually.

[0126] In the example, in addition to the specific waypoints used to trigger behavior for the first and second time periods, the WTRU can be configured with a first set of filter coefficients for generating cell / beam measurements during the first time period and a second set of filter coefficients for the second time period. Specifically, the WTRU can perform measurements using the first set of filter coefficients until it reaches a waypoint (or is within a threshold distance of the waypoint). When the WTRU reaches the waypoint, and for the time period after reaching the waypoint, the WTRU can use the second set of filter coefficients to generate cell / beam measurements.

[0127] In the example, the WTRU can receive filter coefficients to be applied to different regions. This information can be provided, for example, in the SIB. This information can be provided as a range of latitude, longitude, and altitude, to which a specific set of filter coefficients can be applied. When the WTRU is in that region, it can apply the filter coefficients associated with that region. Alternatively, when the WTRU reaches a waypoint located in a region, it can change the filter coefficients for that region.

[0128] Figure 6An example location-based mobility scenario 600 for a WTRU 602 (e.g., an airborne WTRU) is illustrated. The WTRU 602 can move from a first location associated with a first waypoint 610 to a second location associated with a second waypoint 620. In the area surrounding the first waypoint 610 (e.g., waypoint 1), a network can be deployed using a first candidate cell set 612 for L1 / L2 mobility. Each cell in the first candidate cell set 612 can have a large cell coverage area. In the area surrounding the second waypoint 620 (e.g., waypoint 2), a second candidate cell set 622 can be deployed using a network. Each cell in the second candidate cell set 622 can have a small coverage area. In one example, to avoid excessive measurement reporting and potential ping-pong handovers of L1 / L2 mobility, WTRU 602 may be configured with a longer averaging time in the area around second waypoint 620 compared to when it is in the area around first waypoint 610. This is because instantaneous measurements (e.g., with little averaging) could lead to multiple unnecessary handovers in the second candidate cell set 622 compared to the first candidate cell set 612. WTRU 602 may be configured to be triggered based on waypoints (e.g., when WTRU 602 is closer to second waypoint 620 than first waypoint 610) to determine when to change the averaging applied to the measurements, for example, to differentiate the applied averaging.

[0129] Figure 7 An exemplary altitude-based mobility scenario 700 for WTRU 702 is illustrated. For example, WTRU 702 can perform measurements based on its altitude. WTRU 702 can move from a first altitude 710 (e.g., altitude 1) to a second altitude 720 (e.g., altitude 2). When WTRU 702 is at the first altitude 710, a first candidate cell set 712 can serve WTRU 702. When WTRU 702 is at the second altitude 720, a second candidate cell set 722 can serve WTRU 702. Each cell in the first candidate cell set 712 can have a small cell coverage area. Each cell in the second candidate cell set 722 can have a large cell coverage area. When the altitude of WTRU 702 exceeds a threshold altitude 715, WTRU 702 can transition (e.g., handover) from the first candidate cell set 712 to the second candidate cell set 722.

[0130] The WTRU 702 can determine one or more parameters for performing measurements based on conditions associated with its altitude. The WTRU 702 can determine measurement parameters associated with LTM measurements based on altitude-related conditions. For example, the WTRU 702 can determine the value or configuration of any measurement parameter defined herein based on conditions associated with its altitude. In the example, the WTRU can be configured with a set of filter coefficients to be applied for one or more specific altitudes, an offset for measurements applied to the serving cell or neighboring cells, an offset for measurements applied to a specific frequency, a measurement sampling interval / frequency, and / or the average duration of the measurement. If the WTRU has a specific altitude or is within a specific altitude range, the WTRU can apply the configured measurement parameters associated with that altitude or altitude range.

[0131] For example, a WTRU can be configured to use a first carrier frequency (F1) to measure L1 / L2 mobility when the WTRU altitude is below a threshold, and to use a second carrier frequency (F2) to measure it when the WTRU altitude is above the threshold. The WTRU can decide to perform (e.g., only) measurements associated with candidate cells at frequencies that can be configured to be measured at the WTRU's current altitude.

[0132] The combination of measurement parameters can be determined based on altitude-related conditions (or other conditions described herein). For example, the motivation and solution for such a situation are illustrated below. For instance, at a first altitude (below a threshold), the WTRU can perform L1 / L2 mobility on a set of candidate cells associated with frequency F1 because these cells have smaller coverage areas. When the WTRU's altitude is above the threshold, the candidate cells on F1 may have too small a coverage area to properly configure L1 / L2 mobility, and the WTRU can be configured to perform measurements on F2 instead. The WTRU can use different sets of measurement parameters (e.g., filter coefficients) to characterize different coverage areas of the cells at each frequency.

[0133] In the example, the WTRU can determine one or more parameters for performing the measurement based on conditions associated with the WTRU's speed. In the solution, the WTRU can determine the measurement parameters associated with the LTM measurement based on conditions associated with its speed. For example, the WTRU can determine the value or configuration of any measurement parameter defined herein based on speed-related conditions. For example, the WTRU can determine its vertical speed and can determine its measurement configuration based on that determined vertical speed. For example, the WTRU can be configured to use a first set of measurement parameters (e.g., filter coefficients, sampling interval / frequency, offset to be applied, etc.) if the vertical speed is below a threshold, and a second set of measurement parameters if the vertical speed is above a threshold. For example, the WTRU can be configured to use a set of measurement parameters if the WTRU's height is increasing, and a second set of measurement parameters if the WTRU's height is decreasing. For example, the WTRU can be configured to use a first set of measurement parameters for speeds below a threshold and a second set of measurement parameters for speeds above a threshold.

[0134] It should be noted that the measurement parameters discussed here, such as filter coefficients, sampling interval / frequency, and applied offset, along with different solutions, are merely examples and not an exhaustive list of measurement-related parameters. In general, configurations associated with different waypoints, altitudes, speeds, etc., can include any parameters that affect how the WTRU performs measurements and exactly what the WTRU measures. For example, one or more information elements associated with the measurement execution configuration (e.g., MeasObjectNR for L3 measurements, L1 measurement parameters, etc.) may depend on the waypoint, altitude, and / or speed. In some examples, in addition to having different values ​​for different parameters, some parameters may not even apply to a particular waypoint, altitude, or speed value. In some examples, the WTRU may be configured to not perform certain measurements at all (e.g., measurements of a specific frequency, RAT, cell, cell of an SSB with a specific periodicity, etc.) when the WTRU is at a particular waypoint, altitude, or traveling at a specific speed value.

[0135] In the examples, the L1 measurement reporting function / behavior can depend on the number / conditions of candidate beams / cells. The WTRU can determine a threshold for the measurement results used for measurement reporting. In some examples, the WTRU can be configured with a maximum number of cells for which the WTRU reports measurement results (e.g., RSRP using MAC CE) or L1 measurements (e.g., CSI-RSRP or SSB-RSRP) and / or a maximum number of SSB indices or CSI-RS resources. These maximum values ​​can be predefined, or the WTRU can receive them via signaling such as RRC or MAC CE. This maximum value can be referred to as the maximum report size. The WTRU can receive separate maximum report size values ​​for RRC measurement reports, MAC CE reports, or CSI measurements.

[0136] In the example, the WTRU can determine thresholds (e.g., RSRP, CSI-RSRP, SSB-RSRP) for measurement results. The WTRU can report (e.g., only report) measurement results for cells (or SSB indexes, or CSI-RS resources) whose measurement results are above the threshold.

[0137] The WTRU can determine a threshold based on one or more of the following. For example, the WTRU can receive a measurement result threshold via signaling such as RRC or MAC CE. For example, the WTRU can determine a threshold such that the number of cells (or SSB indexes, or CSI-RS resources) with measurement results above the threshold is less than the maximum reporting size. The WTRU can choose the lowest possible threshold to satisfy this condition. The WTRU can choose a threshold from a set of thresholds predefined by MAC CE or RRC or signaled. For example, if the number of detected and measured cells is less than the maximum reporting size, the WTRU can set the threshold to the lowest possible value, or it can be undetermined whether to set any threshold. In the example, the WTRU can indicate the number of cells (or SSB indexes, or CSI-RS resources) it can detect, and for that cell, the measurement result can be below the threshold.

[0138] In the example, the WTRU can select one or more resource sets for measurement based on the number of detected cells exceeding a threshold. For example, the WTRU can receive configuration for at least one resource set for measurement reporting purposes using RRC, MACCE, or CSI. Resources can include at least one of cells (e.g., cells identified by PCI), SSB indexes, and combinations of PCI and CSI-RS resource sets. The WTRU can receive this configuration from RRC or MAC CE signaling. Resource sets can have different sizes. A first resource set can be a strict subset of a second resource set. For example, the first resource set can include resources under the control of a single distributed unit (DU), while the second resource set can include resources under the control of multiple DUs.

[0139] In the example, the WTRU can select a resource set based on the number of cells (or SSB index, or CSI-RS resource) that can be detected within each set, or the number of cells whose measurements exceed a measurement result threshold. This number can be referred to as the number of important measurements. The WTRU can determine the measurement result threshold using one or more solutions described herein. For example, the WTRU can be configured to have two resource sets. If the number of important measurements is below the maximum reporting size, the WTRU can select a first resource set. Alternatively, the WTRU can select a second resource set.

[0140] In another example, the WTRU can be configured with N resource sets. The WTRU can select a set such that, when using that set, the number of important measurements does not exceed the maximum report size. If this condition is met for more than one set, the WTRU can select the set with the largest number of resources. Alternatively, the WTRU can select the set that maximizes the number of important measurements.

[0141] In the example, the WTRU may first select a first set of resources based on one or more solutions described herein. For instance, if the number of significant measurements obtained is less than the maximum report size, the WTRU may measure a subset of resources from a second set of resources and include the measurements in the report. The WTRU may then select the subset of resources with the highest number of measurements from the second set, ensuring that the total number of measurements included in the report does not exceed the maximum report size.

[0142] If the number of critical measurements exceeds the maximum value, the WTRU may fall back to L3 mobility (or disable LTM). In the example, the WTRU may receive a first configuration and a second configuration for measurement reporting at L1, MAC CE, and / or RRC. The first configuration enables at least one of L1 and MAC CE reporting (e.g., in addition to RRC reporting), while the second configuration enables RRC measurement reporting (e.g., RRC measurement reporting only). The WTRU may apply the first configuration if the number of critical measurements is not greater than the maximum report size. Otherwise, the WTRU may apply the second configuration. In the example, the WTRU may apply the first configuration if the number of critical measurements is not less than the minimum report size. Otherwise, the WTRU may apply the second configuration. The minimum report size may be predefined or signaled by the MAC CE or RRC.

[0143] In this example, L1 measurement reporting functionality / behavior can depend on altitude or waypoint conditions. For instance, the WTRU can determine one or more parameters for reporting measurements based on conditions associated with a waypoint. In this example, the WTRU can determine measurement reporting parameters associated with an LTM measurement based on conditions associated with a waypoint. For instance, the WTRU can determine the values ​​or configurations for any measurement reporting parameters defined herein based on conditions associated with a waypoint.

[0144] In the example, the WTRU can be configured with a set of thresholds (e.g., absolute thresholds for comparing the serving cell measurement or neighboring cell measurement, relative thresholds for comparing the serving cell with neighboring cells, etc.) to trigger measurement reports associated with different waypoints. For example, if the WTRU is close to a waypoint (e.g., the current distance to the waypoint is less than a configured threshold), the WTRU can apply the associated threshold for that waypoint when determining whether to trigger a measurement report.

[0145] In the example, the WTRU can be configured with a set of TTT values ​​for triggering measurement reports associated with different waypoints (e.g., to determine whether the serving cell signal level or neighboring cell signal level meets a measurement reporting threshold for a given time to prevent frequent measurement reports). For example, if the WTRU is near a waypoint (e.g., the current distance to the waypoint is below a configured threshold), the WTRU can apply the associated TTT value for that waypoint when determining whether to trigger a measurement report. In one example, the WTRU can be configured with a set of measurement reporting periods (e.g., if periodic measurement reporting is configured), which is used to trigger measurement reports associated with different waypoints. For example, when the WTRU is at a first waypoint (e.g., the current distance to the waypoint is below a configured threshold), the WTRU can perform periodic measurement reports with the period associated with that waypoint, and when the WTRU is at a second waypoint, it can perform periodic measurement reports with a second period associated with the second waypoint, and so on. In the example, the WTRU can be configured to not perform periodic measurement reporting at a specific waypoint or set of waypoints (e.g., between some coordinate ranges), but the WTRU can be configured to perform periodic measurement reporting at other waypoints.

[0146] In the example, the WTRU can be configured with measurement reporting enabled / activated at specific waypoints (e.g., only enabled / activated). For example, the WTRU can (e.g., always) perform measurements, but no measurement report can be triggered unless the WTRU is at / near a configured waypoint, and / or reporting at waypoints where reporting is enabled can be controlled differently depending on any example described herein. The association between measurement reporting parameters and waypoints can be such that the WTRU is configured to use one set of parameters from a set / range of waypoints, another set of parameters from another set / range of waypoints, etc. For example, the WTRU can be configured to have a first waypoint / position range (e.g., between coordinates 1 and 2) and a second waypoint / position range (e.g., between coordinates 3 and 4). For the first waypoint range, the WTRU can be configured to use a first TTT, while for the second waypoint range, the WTRU can use a second TTT.

[0147] In the example, the WTRU can determine one or more parameters for reporting measurements based on conditions associated with its height. For instance, the WTRU can determine the measurement reporting parameters associated with an LTM measurement based on conditions associated with its height. For example, the WTRU can determine the value or configuration of any measurement reporting parameter defined herein based on conditions associated with its height.

[0148] In the example, the WTRU can be configured with a set of thresholds (e.g., absolute thresholds for comparing the serving cell measurement or neighboring cell measurement, relative thresholds for comparing the serving cell with neighboring cells, etc.) for triggering measurement reports associated with different WTRU altitudes. For example, if the WTRU is at a specific altitude, the WTRU can apply the associated threshold for that altitude when determining whether to trigger a measurement report. In the example, the WTRU can also be configured with a set of TTT values ​​(e.g., for determining whether the serving cell signal level or neighboring cell signal level meets a measurement report threshold for a given time to prevent frequent measurement reports) for triggering measurement reports associated with different altitudes. For example, if the WTRU is at a specific altitude, the WTRU can apply the associated TTT value for that altitude when determining whether to trigger a measurement report.

[0149] In the example, the WTRU can be configured to trigger a set of periodic measurement reporting cycles associated with different heights (e.g., if periodic measurement reporting is configured). For example, when the WTRU is at a first height, it can perform periodic measurement reporting with a cycle associated with that height, and when the WTRU is at a second height, it can perform periodic measurement reporting with a second cycle associated with that second height, and so on. In the example, the WTRU can be configured to perform periodic measurement reporting when (e.g., only when) the WTRU is within a specific height range (e.g., below a specific height, above a specific height, between two height levels, etc.). In the example, the WTRU can be configured with measurement reporting configurations that are enabled / activated only at specific heights. For example, the WTRU can (e.g., always) perform measurements, but will not trigger measurement reporting unless the WTRU is at a height configured for measurement reporting, and reporting at heights where reporting is enabled can be controlled differently depending on any of the examples given above. In the example, the association between measurement reporting parameters and WTRU height can be such that the WTRU is configured to use one set of parameters from a height set / range, another set of parameters from another height set / range, etc. For example, a WTRU can be configured to have a first altitude range (e.g., between H1 and H2) and a second altitude range (e.g., between H3 and H4). For the first altitude range, the WTRU can be configured to use a first TTT, while for the second altitude range, the WTRU can use a second TTT.

[0150] In the example, the WTRU can determine one or more parameters for reporting measurements based on conditions associated with its speed. Specifically, the WTRU can determine measurement reporting parameters associated with the LTM measurement based on conditions associated with its speed. For example, the WTRU can determine the value or configuration of any measurement reporting parameter defined herein based on conditions associated with its speed. For example, the WTRU can determine its vertical speed and can determine its measurement reporting configuration based on that determined vertical speed. For example, the WTRU can be configured to use a first set of measurement reporting parameters (e.g., threshold, TTT, reporting periodicity, etc.) if the vertical speed is below a threshold, and a second set of measurement reporting parameters if the vertical speed is above a threshold. For example, the WTRU can be configured to use a set of measurement reporting parameters if the WTRU's height is increasing, and a second set of measurement reporting parameters if the WTRU's height is decreasing. For example, the WTRU can be configured to use a first set of measurement reporting parameters for speeds below a threshold and a second set of measurement reporting parameters for speeds above a threshold.

[0151] In some examples, in addition to having different values ​​for different parameters, some of the measurement reporting parameters may not be applicable to a specific waypoint, altitude, or movement at a specific speed(s). In some examples, the WTRU may be configured to not perform measurement reporting at all when the WTRU is traveling at a specific waypoint, altitude, or speed (e.g., measurements of a specific frequency, RAT, cell, cell with a specific periodicity SSB, etc.). In some examples, the WTRU may be configured to have different configurations to include the number of cells and / or the number of beams per cell based on the waypoint, altitude, or speed value. In some examples, the WTRU may be configured to switch between event-based and period-based measurement reporting based on the waypoint, altitude, or speed value. In some examples, the WTRU may be configured to switch between L2-based measurement reporting (e.g., via MAC CE) and L3-based measurement reporting (e.g., RRC measurement reporting) based on the waypoint, altitude, or speed value.

[0152] In the examples, the measurement reporting parameters such as TTT, threshold, and periodicity discussed in this article along with different solutions are not exhaustive of measurement reporting-related parameters. Generally, configurations related to different waypoints, altitudes, speeds, etc., can include any parameters that affect how the WTRU reports measurements. For example, one or more information elements associated with the measurement reporting configuration (e.g., ReportConfigNR for L3 measurement reporting, L1 measurement reporting parameters such as those for CSI-RS reporting, etc.) can depend on waypoints, altitudes, or speeds.

Claims

1. A wireless transmit / receive unit (WTRU), the WTRU comprising: The processor is configured to: Receive configuration information from the network, wherein the configuration information indicates a first measurement parameter and a second measurement parameter, wherein the first measurement parameter is associated with a height-based condition; The height-based conditions associated with the first measurement parameter are determined based on the height of the WTRU. The measurement of the first beam set associated with the first measurement parameter is determined based on the satisfaction of the altitude-based condition, and the measurement of the second beam set associated with the second measurement parameter is not performed. as well as The measurement of the first beam set associated with the first measurement parameter is sent to the network.

2. The WTRU of claim 1, wherein the second measurement parameter is associated with a second height-based condition, the second height-based condition being different from the height-based condition associated with the first measurement parameter.

3. The WTRU of claim 1, wherein the height-based condition includes the height of the WTRU being between a first height threshold and a second height threshold.

4. The WTRU of claim 1, wherein the processor is configured to: The measurement of the first beam set associated with the first measurement parameter is determined based on the hysteresis height value associated with the first measurement parameter, while the measurement of the second beam set associated with the second measurement parameter is not performed.

5. The WTRU of claim 1, wherein the height-based condition includes the height of the WTRU being between a first height threshold and a second height threshold, and wherein the height-based condition includes a hysteresis height value.

6. The WTRU of claim 1, wherein the processor is further configured to determine the first beam set associated with the first measurement parameter to be measured based on the set of synchronization signal block (SSB) resources associated with the first measurement parameter.

7. The WTRU of claim 1, wherein the second measurement parameter is a default measurement configuration.

8. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: Receive configuration information from the network, wherein the configuration information indicates a first measurement parameter and a second measurement parameter, wherein the first measurement parameter is associated with a height-based condition; The height-based conditions associated with the first measurement parameter are determined based on the height of the WTRU. The measurement of the first beam set associated with the first measurement parameter is determined based on the satisfaction of the altitude-based condition, and the measurement of the second beam set associated with the second measurement parameter is not performed. as well as The measurement of the first beam set associated with the first measurement parameter is sent to the network.

9. The method of claim 8, wherein the second measurement parameter is associated with a second height-based condition, the second height-based condition being different from the height-based condition associated with the first measurement parameter.

10. The method of claim 8, wherein the height-based condition includes the height of the WTRU being between a first height threshold and a second height threshold.

11. The method of claim 8, comprising: The measurement of the first beam set associated with the first measurement parameter is determined based on the hysteresis height value associated with the first measurement parameter, while the measurement of the second beam set associated with the second measurement parameter is not performed.

12. The method of claim 8, wherein the height-based condition includes the height of the WTRU being between a first height threshold and a second height threshold, and wherein the height-based condition includes a hysteresis height value.

13. The method of claim 8, further comprising: The first beam set associated with the first measurement parameter is determined based on the set of synchronization signal block (SSB) resources associated with the first measurement parameter.

14. The method of claim 8, wherein the second measurement parameter is a default measurement configuration.

15. A wireless transmit / receive unit (WTRU), the WTRU comprising: The processor is configured to: Receive an RRC message from the network that includes configuration information, wherein the configuration information includes multiple measurement configurations, and one of the multiple measurement configurations is associated with a height-based condition; The measurement configuration among the plurality of measurement configurations is determined based on the height of the WTRU and the height-based conditions associated with the measurement configuration; Based on the height of the WTRU and the height-based conditions associated with the measurement configuration, it is determined that a first measurement parameter cannot be applied to the WTRU and a second measurement parameter associated with the measurement configuration can be applied to the WTRU; Measure one or more beams according to the second measurement parameter; as well as The measurements of the one or more beams are sent to the network.

16. The WTRU of claim 15, wherein the height-based condition includes the height of the WTRU being between a first height threshold and a second height threshold.

17. The WTRU of claim 15, wherein the processor is configured to: The measurement configuration among the plurality of measurement configurations is determined based on (i) the height-based conditions associated with the measurement configuration and (ii) the hysteresis height value associated with the measurement configuration.

18. The WTRU of claim 15, wherein the height-based condition includes the height of the WTRU being between a first height threshold and a second height threshold, and is based on a hysteresis height value associated with the measurement configuration.

19. The WTRU of claim 15, wherein the processor is further configured to determine the one or more beams to be measured based on a set of synchronization signal block (SSB) resources.

20. The WTRU of claim 15, wherein a subset of at least the plurality of measurement configurations is associated with a corresponding height-based condition.

Images