Altitude dependent measurement and reporting configuration

Abstract

Apparatus and methods for altitude dependent measurement and reporting configuration are described. An apparatus is configured to receive a measurement object configuration from a network node, where the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. The apparatus is further configured to measure an SSB value for each SSB in the set of SSBs based on the measurement object configuration and the altitude of the UE. The additional device is configured to configure a measurement object configuration for the UE, where the measurement object configuration indicates at least one altitude parameter associated with the set of SSBs. The additional device is further configured to provide a set of SSBs indicated in the measurement object configuration.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application No. 63 / 493,994, entitled "ALTITUDE-DEPENDENT MEASUREMENT AND REPORTING CONFIGURATIONS", filed April 3, 2023, and U.S. Non-Provisional Patent Application No. 18 / 603,050, entitled "ALTITUDE-DEPENDENT MEASUREMENT AND REPORTING CONFIGURATIONS", filed March 12, 2024, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] In general, this disclosure relates to communication systems, and more specifically, to wireless communication using signal measurements. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies, enabling communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative launched by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., regarding the Internet of Things (IoT)), and others. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following presents a simplified overview of one or more aspects to provide a basic understanding of these aspects. This invention is not a broad overview of all anticipated aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to introduce some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0007] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus (which may be a user equipment (UE)) is configured to receive a measurement object configuration from a network node, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. The apparatus is further configured to measure an SSB value for each SSB in the set of SSBs based on the measurement object configuration and the altitude of the UE.

[0008] In this aspect, the method includes receiving a measurement object configuration from a network node, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. The method also includes measuring an SSB value for each SSB in the set of SSBs based on the measurement object configuration and the altitude of the UE.

[0009] In another aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus is configured to configure a measurement object configuration for a UE, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. The apparatus is also configured to provide the set of SSBs indicated in the measurement object configuration.

[0010] In this aspect, the method includes configuring a measurement object configuration for a UE, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. The method also includes providing the set of SSBs indicated in the measurement object configuration.

[0011] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate certain illustrative features of the one or more aspects in detail. However, these features indicate only some of the various ways in which the principles of these aspects can be employed. Attached Figure Description

[0012] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.

[0013] Figure 2A This is a diagram illustrating an example of the first frame of various aspects according to this disclosure.

[0014] Figure 2B This is a diagram illustrating an example of a downlink (DL) channel within a subframe according to various aspects of this disclosure.

[0015] Figure 2C This is a diagram illustrating an example of the second frame according to various aspects of this disclosure.

[0016] Figure 2D This is a diagram illustrating an example of an uplink (UL) channel within a subframe according to various aspects of this disclosure.

[0017] Figure 3 This is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0018] Figure 4 This is a diagram illustrating an example communication system with UEs located at different altitudes or elevations.

[0019] Figure 5 This is a diagram illustrating an example of beam measurement for a Synchronization Signal Block (SSB) burst according to various aspects of this disclosure.

[0020] Figure 6 This is a diagram illustrating examples of measurement object information elements (IEs) according to various aspects of this disclosure.

[0021] Figure 7 This is a diagram illustrating an example of Machine Type Communication (MTC) IE according to various aspects of this disclosure;

[0022] Figure 8 This is a call flow diagram for wireless communication illustrating various aspects of this disclosure.

[0023] Figure 9 This is a diagram illustrating an example configuration for altitude-dependent measurements and reporting, according to various aspects of this disclosure.

[0024] Figure 10 This is a diagram illustrating an example configuration for altitude-dependent measurements and reporting, according to various aspects of this disclosure.

[0025] Figure 11 This is a diagram illustrating an example configuration for altitude-dependent measurements and reporting, according to various aspects of this disclosure.

[0026] Figure 12 This is a diagram illustrating an example configuration for altitude-dependent measurements and reporting, according to various aspects of this disclosure.

[0027] Figure 13 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0028] Figure 14 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0029] Figure 15 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0030] Figure 16 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0031] Figure 17 This is a diagram illustrating an example of a hardware implementation for an example device and / or network entity.

[0032] Figure 18 This is a diagram illustrating an example of a hardware implementation used for a sample network entity.

[0033] Figure 19 This is a diagram illustrating an example of a hardware implementation used for a sample network entity. Detailed Implementation

[0034] Wireless communication networks (such as 4G LTE networks, 5G NR networks, etc.) enable UEs to measure directional communication beams (e.g., for beam management and / or mobility operations). In a 5G NR network, as an example, a given physical cell can exchange wireless communications via multiple beams, and the UE can measure multiple SSBs from the cell. The configuration for such measurements can be referred to as a measurement object configured for the UE and can include a bitmap (“ssb-ToMeasure”) indicating the set of SSBs to be measured during the SMTC measurement duration. ssb-ToMeasure can include a single bitmap in a measurement object for SSB measurements used for mobility determination (e.g., it can be referred to as an SSB-ConfigMobility object) and can be applied to measurements in multiple measurement configurations (e.g., “smtc” and “smtc2”) for a given measurement object (e.g., it can be referred to as measObjectNR).

[0035] However, multiple measurement object configurations for a given SSB frequency (e.g., which may be referred to as "ssbFrequency") may not be enabled or permitted for a cell group. For example, some wireless networks may be implemented to ensure that in a measurement configuration (which may be referred to as "measConfig") associated with configured permission (CG): (1) for all SSB-based measurements, there exists at most one measurement object with the same ssbFrequency; and / or (2) "smtc1" included in any measurement object with the same ssbFrequency has the same value, as does "smtc2" included in any measurement object with the same ssbFrequency, as does "smtc3list" included in any measurement object with the same ssbFrequency, and "smtc4list" included in any measurement object with the same ssbFrequency has the same value. This paper enables SMTC to possess flexibility that allows a UE (e.g., an unmanned aerial vehicle (UAV)) to measure a first set of beams (or [cell, beam] ordered pairs) at an altitude range (e.g., below or at the level of clutter) and different sets of beams (including for different cells) at different altitude ranges (e.g., above a specific altitude where line-of-sight (LOS) is typically expected). The altitude range, or altitude threshold or parameter, for the SSB to be measured allows the network to configure the UE to perform more efficient measurements by considering the possibilities for different UE altitudes.

[0036] In summary, the various aspects relate to wireless communication systems and measurement operations for wireless devices. Specifically, some aspects involve altitude-dependent measurement and reporting configurations. In one example, the UE may receive a measurement object configuration from a network node, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. The UE may also measure SSB values ​​for each SSB in the SSB set based on the measurement object configuration and the UE's altitude. In another example, a network node (e.g., a base station, gNB, etc.) may configure a measurement object configuration for the UE, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. The network node may also provide the set of SSBs indicated in the measurement object configuration.

[0037] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by implementing a configuration for altitude-specific measurements of synchronization signals, the described techniques can be used to improve the flexibility and accuracy of location and mobility measurements at the UE based on UE altitude (e.g., for UAV). In some examples, by enabling a configuration for altitude-specific measurements of synchronization signals with altitude ranges / intervals, the described techniques can be used to improve the flexibility and accuracy of location and mobility measurements at the UE based on a specific synchronization signal (e.g., for UAV) based on UE altitude. In some examples, by enabling a configuration for altitude-specific measurements with an SSB-MTC list in the measurement object, the described techniques can be used to provide an SSB-MTC sub-configuration where each element in the SSB-MTC list flexibly allows altitude ranges to achieve flexibility and accuracy of location and mobility measurements at the UE based on a specific synchronization signal based on UE altitude.

[0038] The following detailed description, illustrated with reference to the accompanying drawings, describes various configurations, but does not represent the only configuration in which the concepts described herein can be implemented. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, these concepts can be implemented without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0039] Several aspects of a telecommunications system are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the detailed description below and are shown in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0040] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. When multiple processors are implemented, the multiple processors can perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referring to software, firmware, middleware, microcode, hardware description languages, or others, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads in execution, procedures, functions, or any combination thereof.

[0041] Therefore, in one or more example aspects, implementations, and / or use cases, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium accessible to a computer. For example, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described, or any other medium capable of storing computer-executable code in the form of computer-accessible instructions or data structures.

[0042] Although aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, artificial intelligence (AI) enabled devices, etc.). While some examples may or may not specifically point to a use case or application, the applicability of various types of the described examples may appear. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components of one or more technologies incorporated herein to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and enforcing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / converters, etc.). The techniques described herein can be implemented in various devices, chip-level components, systems, distributed arrangements, aggregated or deaggregated components, end-user equipment, etc., of different sizes, shapes, and configurations.

[0043] The deployment of communication systems (such as 5G NR systems) can be arranged in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in an aggregated or deaggregated architecture. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or deaggregated base stations.

[0044] Aggregated base stations can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. Deaggregated base stations can be configured to utilize a protocol stack physically or logically distributed across two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, the CU may be implemented within the RAN node, and one or more DUs may be located in the same location as the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit (i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0045] Base station operation or network design can take into account the aggregation characteristics of base station functions. For example, de-aggregating base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations sponsored by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). De-aggregation can include: allocating functions among two or more units at various physical locations, and virtually allocating functions for at least one unit, which allows for flexibility in network design. Individual units of a de-aggregating base station or de-aggregating RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0046] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The wireless communication system shown includes a deconverged base station architecture. The deconverged base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more deconverged base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midrange link, such as an F1 interface. DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0047] Each of the units (i.e., CU 110, DU 130, RU 140) and the near-RT RIC 125, non-RT RIC 115, and SMO framework 105 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the unit, or an associated processor or controller providing instructions to the unit's communication interface, may be configured to communicate with one or more other units via a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more other units. Additionally, a unit may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals, or both, over a wireless transmission medium to one or more other units.

[0048] In some implementations, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), and so on. Each control function may be implemented using an interface configured to transmit signaling to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, the CU 110 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 when necessary for network control and signaling.

[0049] DU 130 may correspond to a logic unit that includes one or more base station functions to control the operation of one or more RU 140s. In some aspects, DU 130 may, at least in part, manage one or more of the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) based on functional breakdowns such as those defined by 3GPP. In some aspects, DU 130 may also manage one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to transmit signals with other layers (and modules) managed by DU 130 or with control functions managed by CU 110.

[0050] Low-level functions can be implemented by one or more RU 140s. In some deployments, the RU 140 controlled by the DU 130 can correspond to a logical node that, at least in part, manages RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based on function splitting (such as low-level function splitting). In such an architecture, the RU 140 can be implemented to handle over-the-air (OTA) communication with one or more UE 104s. In some implementations, the real-time and non-real-time aspects of control and user plane communication with the RU 140 can be controlled by the corresponding DU 130. In some cases, this configuration allows the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as vRAN).

[0051] SMO framework 105 can be configured to support RAN deployment and configuration for both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RUs 140 via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0052] The non-RT RIC 115 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) workflows (including model training and updates), or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125 (e.g., via the A1 interface). The near-RT RIC 125 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on interfaces (e.g., via the E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the near-RT RIC 125.

[0053] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or via the creation of RAN management policies (such as A1 policies).

[0054] At least one of CU 110, DU 130, and RU 140 can be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component indicated by a dashed line represents whether or not it may be included in base station 102). Base station 102 provides an access point to core network 120 for UE 104. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network including both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB), which can provide service to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from BS 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be via one or more carriers. Base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.) bandwidth per carrier allocated in carrier aggregation for transmission in each direction. Carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell), and the secondary component carrier can be referred to as the secondary cell (SCell).

[0055] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more side-link channels, such as Physical Side-Link Broadcast Channel (PSBCH), Physical Side-Link Discovery Channel (PSDCH), Physical Side-Link Shared Channel (PSSCH), and Physical Side-Link Control Channel (PSCCH). D2D communication can be conducted through various wireless D2D communication systems, such as, for example, Bluetooth. TM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wi-Fi.) TM (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0056] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also known as a Wi-Fi station (STA)) via a communication link 154, for example in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE104 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0057] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes arise regarding FR2; although different from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0058] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have designated the operating bands for these mid-band frequencies as the frequency range name FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and therefore can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating bands have been designated as the frequency range names FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher bands falls within the EHF band.

[0059] In light of the foregoing, unless otherwise specified, the term "sub-6GHz" and the like (if used herein) may broadly refer to frequencies that are less than 6GHz, frequencies that are within FR1, or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise specified, if the term "millimeter wave" and the like are used herein, they may broadly refer to frequencies that may include intermediate frequency bands, frequencies that are within FR2, FR4, FR2-2 and / or FR5, or frequencies that are within the EHF band.

[0060] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions for base station 102 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0061] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, basic transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network device, or any other suitable term. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or as a deaggregated base station including one or more of CU, DU, and / or RU. A collection of base stations that may include deaggregated and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0062] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key protocol (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are shown as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, typically, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the following: GMLC 165, LMF 166, Location Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may utilize one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional rate calculation based on measurements. Signal measurement may be performed by UE 104 and / or the base station 102 serving UE 104. The measured signal may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signal, Wireless Local Area Network (WLAN) signal, Bluetooth signal, Land Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signal (e.g., Multi-Round-Trip Time (Multi-RTT), DL Departure Angle (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0063] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also be used for one or more accompanying devices, such as in an equipment constellation arrangement. One or more of these devices can access the network together and / or individually. In all respects, the UE (e.g., UE 104) in this document can be a UAV or can be associated with a UAV.

[0064] Refer again Figure 1In some aspects, UE 104 may have an altitude-based measurement component 198 (“Component 198”), which can be configured to receive a measurement object configuration from a network node, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. Component 198 may also be configured to measure each SSB associated with one or more cell identifiers based on the absence of a corresponding set of SSBs for the additional altitude parameter in the SMTC. Component 198 may be configured to obtain the altitude of the UE. To obtain the altitude of the UE, Component 198 may be configured to measure the altitude of the UE based on information received by the UE and / or receive an indication of the altitude of the UE from a network node or network entity. Component 198 may be configured to report each measured SSB in the set of SSBs for at least one physical cell at the UE's altitude based on a reporting configuration associated with the UE's altitude and at least one of the UE's altitude, location, rate, or speed. In some aspects, base station 102 may have an altitude-based measurement component 199 (“Component 199”) that can be configured to configure a measurement object configuration for a UE, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. Component 199 may also be configured to provide the set of SSBs indicated in the measurement object configuration. Component 199 may be configured to obtain the altitude of the UE. Component 199 may be configured to measure the altitude of the UE based on information received from the UE. Component 199 may be configured to transmit an indication of the altitude of the UE to the UE. Therefore, these aspects provide additional flexibility for beam measurement beyond that offered in current solutions. In various aspects of this paper, the SMTC is made flexible enough to allow the UE (e.g., UAV) to measure a first set of beams (or [cell, beam] ordered pairs) at an elevation range (e.g., below or level with clutter) and different sets of beams at different elevation ranges (e.g., above a specific elevation where line of sight (LOS) is typically expected) (including: different beams for different cells, and / or different elevation ranges / intervals).

[0065] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2DFigure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL), or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). In the process of... Figure 2A , Figure 2C In the provided example, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 is configured with slot format 1 (fully UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are fully DL and fully UL, respectively. Other slot formats 2-61 include a mixture of DL symbols, UL symbols, and flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the TDD 5G NR frame structure.

[0066] Figure 2A-2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 subframes (1 ms) of the same size. Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Depending on whether the cyclic prefix (CP) is ordinary or extended, each time slot may include 14 or 12 symbols. For ordinary CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe may be based on the CP and the numbering scheme. The digital scheme defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be proportional to 1 / SCS.

[0067]

[0068] Table 1: Digital Scheme, SCS, and CP

[0069] For a standard CP (14 symbols / slot), different digital schemes μ0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, digital scheme 2 allows 4 slots per subframe. Therefore, for both the standard CP and digital scheme μ, there are 14 symbols / slot and 2 slots per subframe. μ One time slot / subframe. The subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 4. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15kHz, and digital scheme μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 2A-2D Examples are provided for a standard frequency division multiplexing (CP) scheme with 14 symbols per slot and a digital scheme with 4 slots per subframe (μ=2). The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, one or more distinct bandwidth portions (BWPs) of frequency division multiplexing may exist (see [link to relevant documentation]). Figure 2B Each BWP can have a specific numerical scheme and CP (normal or extended).

[0070] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) (also called a physical RB (PRB)) that extends for 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0071] like Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS). RSs may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0072] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring opportunities on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe within the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe within the frame. The SSS is used by the UE to determine the Physical Layer Cell Identity Group Number and radio frame timing. Based on the Physical Layer Identity and Physical Layer Cell Identity Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0073] like Figure 2C As shown, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or second symbol of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0074] Figure 2DExamples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACK)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0075] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL (Data Link Module), Internet Protocol (IP) packets can be provided to the controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptive Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), and MAC... SDU performs demultiplexing of TB, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0076] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to generate a physical channel for carrying the time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes, as well as for spatial processing. Channel estimates can be derived based on reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to different antennas 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate a radio frequency (RF) carrier with the corresponding spatial stream for transmission.

[0077] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of separate OFDM symbol streams for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. Subsequently, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0078] The controller / processor 359 may be associated with at least one memory 360 (also referred to as "at least one memory 360") storing program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0079] Similar to the functions described in the DL transmission combined with base station 310, controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, error correction via ARQ, RLC SDU connection, segmentation and reassembly, RLC data PDU resegmentation, and RLC data PDU reordering; and MAC layer functions associated with mapping between logical channels and transport channels, MAC SDU multiplexing onto TB, demultiplexing MAC SDU from TB, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority.

[0080] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0081] The UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives the signal through its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0082] The controller / processor 375 may be associated with a memory 376 (also referred to as "at least one memory 376") that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0083] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform operations related to... Figure 1 The aspects related to component 198. At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform actions related to Figure 1 The aspects related to component 199.

[0084] In other examples, a UE may include or be associated with a UAV. A UAV may include unmanned aerial vehicles (UAVs) or other aircraft, and may include aircraft without an onboard human pilot. In some aspects, a UAV may be operated remotely or autonomously based on a set of instructions, and may include sensors, cameras, and other instruments, such as, but not limited to, the UE. UAVs are used in a variety of applications, such as surveillance, wildlife conservation, disaster mitigation, delivery services, and aerial photography. They offer advantages such as the ability to reach hard-to-access locations. UAVs can reach different altitudes (e.g., which may be interchangeably referred to as altitudes) that are inaccessible to terrestrial UEs. UAVs may fly at different altitudes, and a UAV including a UE may cause interference to or from other distant UEs due to line-of-sight channels. However, a UAV including a UE and on the ground may cause less interference to or from other distant UEs due to non-line-of-sight channels compared to a UAV flying in the air.

[0085] Figure 4 An example communication system 400 is shown, in which network nodes (such as base station 402) communicate with multiple UEs (e.g., UEs 416, 406, and 418) at various heights (e.g., altitudes) relative to the ground plane 404. Figure 4 It is shown that UE406 and UE418 can be UAVs or can be located at UAVs or other aircraft. In some aspects, base station 402 can be located at or near ground plane 404 and can also communicate with one or more UEs 416 that are also located at or near ground plane 404. UE406 can be in the air (e.g., traveling or flying), such that UE406 is at an altitude, elevation, or altitude 408 above ground plane 404. UE418 can be at altitude 409. Figure 4 It is shown that UE 406 can exchange communication 414 with base station 402, and UE 418 can exchange communication 424 with base station 402. UE 416 can exchange communication 420 with base station 402. The base station can use one or more directional beams 405 to transmit communication, for example, as in combination with... Figure 1As described in section 182. Base station 402 may transmit signals on beam 405 for the UE to perform synchronization or other measurements (such as for beam management or mobility). As an example, base station 402 may transmit SSBs on beam 405, and the UE (e.g., 406, 416, and 418) may measure one or more SSBs transmitted by base station 402.

[0086] Figure 5 Figure 500 illustrates examples of beam measurements for SSB bursts (e.g., SSB transport groups) in various aspects. The base station can provide the UE with an SSB measurement timing configuration (also referred to herein as SMTC) for the UE to use in performing beam measurements (e.g., for mobility purposes). Physical broadcast channel (PBCH) block configurations can be similarly implemented in these aspects.

[0087] In the example shown in Figure 500, cell A 502 and cell B 504 are illustrated as examples. Cell A 502 can be the serving cell of UE 516 to which SSBs can be provided / transmitted, and cell B 504 can be a neighboring cell of UE 516. As shown, cell A 502 has four SSBs in SS burst set 506 with SSB period 510, and cell B 504 can have eight SSBs in SS burst set 508, which are provided / transmitted to UE 516.

[0088] In various aspects, the SSB period 510 for the SS burst set 506 can be 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, etc. However, when the UE 516 is in connected mode, the UE 516 may not perform measurements with this period, and the appropriate measurement period can be configured according to channel conditions. This avoids unnecessary measurements and saves UE 516 power. The SMTC window 512 with the SMTC window period 514 can be used to notify the UE 516 of the SSB period and timing, and the UE 516 may be allowed to use the SSB period and timing for cell quality measurements, mobility events, etc. The UE 516 may also be prohibited from monitoring SSBs outside the SMTC window 512. Thus, the network (e.g., cell A 502) can appropriately set the SMTC window 512 and measurement interval length based on the SSB period 510 for the corresponding measurement object (e.g., measObject) of the SSB burst set 506.

[0089] Figure 6Figure 600 illustrates an example of a measurement object IE configured for a UE (e.g., such as UE 406, 416, or 418) in various aspects. In various aspects, Figure 600 may represent a measurement object IE. In the aspects shown, the UE can be configured to establish the first SMTC (also the SS / PBCH block measurement timing configuration) based on the periodicityAndOffset parameter (providing period and offset values ​​for the following conditions) received in the smtc1 configuration. The first subframe of each SMTC opportunity occurs at the system frame number (SFN) and subframe (e.g., a combination of protocol and / or hardware) of the SpCell that satisfies the following conditions:

[0090] SFN mod T = (FLOOR(offset / 10));

[0091] If the period is greater than sf5:

[0092] Then subframe = offset mod 10;

[0093] otherwise:

[0094] Then subframe = offset or (offset + 5);

[0095] Where T = CEIL (period / 10).

[0096] If SMTC2 exists, for the cell indicated in the PCI-List parameters of SMTC2 within the same measurement object, the UE can establish an additional SS / PBCH block measurement timing configuration (e.g., SMTC) based on the received period parameters in the SMTC2 configuration, using the offset (derived from the periodityAndOffset parameter) and duration parameters from the SMTC1 configuration. The first subframe of each SMTC opportunity can occur at the SFN and subframe of the SpCell that satisfy the above conditions.

[0097] If SMTC2-LP exists, for cells indicated in the PCI list (e.g., pci-List parameter) in SMTC2-LP at the same frequency (for intra-frequency cell reselection) or different frequencies (for inter-frequency cell reselection), the UE can establish an additional SS / PBCH block measurement timing configuration (e.g., SMTC) based on the received period parameters in the SMTC2-LP configuration, and use offset (e.g., derived from the periodityAndOffset parameter) and duration parameters from the SMTC configuration for that frequency. The first subframe of each SMTC opportunity can occur at the SFN and subframe of the SpCell or serving cell (e.g., for cell reselection) that satisfy the above conditions.

[0098] If smtc3list exists, for the cell indicated in the pci-List parameter of each SSB-MTC3 element in the list of the same measurement object, the IAB-MT antenna can set up an additional SSB measurement timing configuration based on the received periodicityAndOffset parameter in each SSB-MTC3 configuration (e.g., using the same conditions as smtc1 to identify the SFN and subframe for SMTC opportunities), and using the duration and ssb-ToMeasure parameter from each SSB-MTC3 configuration.

[0099] If an smtc4list exists, for each SSB-MTC4 element in the list of the same measurement objects, the UE can establish an additional SS / PBCH block measurement timing configuration (e.g., SMTC) based on the Offset parameter received in the smtc4 configuration, using the period (e.g., derived from the periodicityAndOffset parameter) and duration parameters from the smtc1 configuration. The first subframe of each SMTC opportunity can occur at the SFN and subframe of the SpCell that satisfy the above conditions.

[0100] Figure 7 Figure 700 illustrates an example of an MTC IE in various aspects. In various aspects, Figure 700 can represent an SSB-MTC IE. Figure 700 can be... Figure 6 Another aspect of Figure 600. In this respect, Figure 700 may represent an SSB-MTC IE. In the aspect shown, as an example, the UE can be configured to establish a list of Physical Cell Identifiers (PCIs), for example, it can follow a pci-LIST for a given SMTC, such as that described for Figure 600. Furthermore, an additional PCI list that also follows the SMTC can be provided. However, this additional PCI list may not be suitable for the measurement object and is part of the additional MIMO parameters in the SIB (e.g., for the mTRP use case).

[0101] A physical cell (e.g., serving cell, neighboring cells, etc.) can have multiple beams, and the UE can measure multiple SSBs for mobility, positioning, and / or beam management, for example, by combining... Figure 4The configuration for such measurements may include a bitmap (in some aspects, "ssb-ToMeasure") indicating the set of SSBs to be measured during the SMTC measurement duration. ssb-ToMeasure can be a single bitmap within an SSB-ConfigMobility object and can be applied to all measurements in a configuration for a given measurement object (e.g., "smtc" and "smtc2"). However, configurations for multiple measurement objects for a given SSB frequency ("ssbFrequency") may not be enabled or permitted for cell groups. For example, some wireless networks can be implemented to ensure that in a measurement configuration (“measConfig”) associated with a configured permission (CG): (1) for all SSB-based measurements, there exists at most one measurement object with the same SSB frequency (e.g., which may be referred to as “ssbFrequency”); and / or (2) “smtc1” included in any measurement object with the same SSB frequency has the same value, as does “smtc2” included in any measurement object with the same SSB frequency, as does “smtc3list” included in any measurement object with the same SSBFrequency, and as does “smtc4list” included in any measurement object with the same SSB frequency. However, for a given altitude range in which a UE exists, the additional flexibility for cell-specific beam measurements can improve beam measurements. In various aspects of this paper, the SMTC is made more flexible, allowing the UE (e.g., an unmanned aerial vehicle (UAV) or other type of UE) to measure a first beam set (or (cell, beam) ordered pair) based on the UE's altitude. For example, the UE can measure a first beam set at an altitude range (e.g., below or at the level of clutter) and different beam sets (including for different cells) at different altitude ranges (e.g., above an altitude where line-of-sight (LOS) is typically expected). As an example, Figure 4 UE 406 can measure a first beam set (e.g., a subset 403 of beam 405) based on an altitude threshold 410, and UE 418 can measure a second beam set (e.g., a subset 407 of beam 405) based on an altitude threshold 410.

[0102] The various aspects of the elevation-dependent measurement and reporting configurations described in this paper improve the flexibility and accuracy of positioning and mobility measurements at the UE via the configuration of elevation-specific measurements for synchronization signals. By implementing the configuration of elevation-specific measurements with elevation ranges / intervals for synchronization signals, these aspects enhance the flexibility and accuracy of positioning and mobility measurements at the UE based on the UE's elevation (e.g., for UAVs) for specific synchronization signals. Furthermore, by configuring elevation-dependent measurements with an SSB-MTC list in the measurement object, these aspects provide SSB-MTC sub-configurations, where each element in the SSB-MTC list flexibly allows for elevation ranges to achieve the flexibility and accuracy of positioning and mobility measurements at the UE based on the UE's elevation for specific synchronization signals. Therefore, the aspects described in this paper provide additional flexibility for beam measurements beyond that offered in current solutions. The various aspects of this document implement flexible measurement object configurations and / or SMTCs that allow a UE (e.g., a UAV) to measure a first set of beams (or [cell, beam] ordered pairs) at an elevation range (e.g., below or level with clutter) and different sets of beams at different elevation ranges (e.g., above a specific elevation where line-of-sight (LOS) is typically expected) (including: for different cells, and / or for different beams in different elevation ranges / intervals). In these aspects, the term elevation may be used interchangeably with height, altitude, etc., and may be used in the context of its relation to the ground, sea level, or some other reference.

[0103] Figure 8 This is a call flowchart 800 for wireless communication in various aspects. Call flowchart 800 illustrates a configuration for an altitude-dependent measurement and reporting configuration performed by a UE (e.g., UE 802) capable of communicating with a network node (base station 804, such as a gNB or other types of base stations, as an example, as shown). The aspects described for base station 804 can be performed by the base station in an aggregated form and / or by one or more components of base station 804 in a deaggregated form. Additionally or alternatively, the aspects can be performed autonomously by UE 802, except and / or in lieu of the operation of base station 804. In some aspects, base station 804 may correspond to... Figure 4 Base station 402 in the middle, or can perform with Figure 4 Similar to base station 402 in the text.

[0104] In the aspects shown, base station 804 may configure (at 806) a measurement object configuration and / or SMTC 808 for UE 802, wherein the measurement object configuration and / or SMTC 808 indicates altitude parameters (e.g., minimum altitude value, maximum altitude value, threshold altitude value, altitude range, and / or hysteresis value) for a set of SSBs. In each aspect, a given altitude parameter may be associated with at least one cell identifier corresponding to at least one physical cell. In each aspect, each of one or more (e.g., multiple) altitude ranges may be associated with a corresponding set of at least one cell identifier and a corresponding set of SSBs (e.g., a subset of SSBs to be measured from the set of SSBs associated with at least one physical cell falling within the SMTC window). The SMTC may include a combination of Figure 7 Any aspect described. In each aspect, the measurement object configuration and / or SMTC 808 may include adding altitude-specific flexibility to the measurement object by indicating the altitude-specific SSB to be measured. In each aspect, this newly added altitude-specific flexibility for the measurement object may be implemented for an existing measurement object. In each aspect, the new configuration for the measurement object configuration and / or SMTC 808 may include altitude ranges / intervals. In one example, the SSB-MTC configuration for the measurement object configuration and / or SMTC 808 may include different SSBs to be measured for different altitude ranges / intervals (e.g., ssb-ToMeasure). In another example, a new list of SSB-MTCs may be included in the measurement object, wherein each element in the new list of SSB-MTCs may represent an SSB-MTC sub-configuration with a corresponding altitude range / interval. In each aspect, the hysteresis value of the hysteresis range may be defined and associated with the altitude range / interval boundary. Base station 804 may be configured to provide / transmit the measurement object configuration and / or SMTC 808 for UE 802.

[0105] Base station 804 can also be configured to provide / transmit a set of SSBs for UE 802. In various aspects, base station 804 can be a serving / serving cell or a neighboring cell, and can be configured to transmit a number of SSBs 810 for UE 802, including the set of SSBs indicated in the measurement object configuration and / or SMTC 808. In various aspects, different base stations can be configured to transmit different numbers of SSBs 810 to UE 802. A cell can be a physical cell with a corresponding PCI. In various aspects, at least one physical cell in the environment of UE 802 can be a serving / serving cell, and the measurement object configuration and / or SMTC 808 can be a cell-specific SMTC for the serving / serving cell. In some aspects, at least one physical cell in the environment of UE 802 can include two or more physical cells (e.g., serving / serving cell and neighboring cells), and the measurement object configuration and / or SMTC 808 can be configured for UE 802 separately for each physical cell, as described herein.

[0106] The UE can be configured to obtain its altitude, for example, by being configured to measure the UE's altitude based on information received by the UE, or by being configured to receive an indication of the UE's altitude from a network node or network entity. UE 802 can be configured to obtain its altitude. In various aspects, to obtain its altitude, UE 802 can be configured to measure (at 812) its altitude based on information received by UE 802 and / or receive an indication of the UE's altitude from a network node or network entity (e.g., base station 804). Base station 804 can be configured to obtain the altitude of UE 802. In various aspects, to obtain its altitude, base station 804 can be configured to measure (similar to 812) the altitude of UE 802 based on information received from UE 802 or from another network node / entity. Base station 804 can be configured to provide an indication of the UE's altitude to UE 802. The altitude of UE 802 can be quantified relative to ground, sea level, debris, etc. UE 802 can be configured to measure (at 812) the SSB value for each SSB in an SSB set (e.g., from the number of SSBs 810 provided / transmitted from base station 804) based on the measurement object configuration and / or SMTC 808 and the altitude of UE 802. The SSB set can be for at least one physical cell in all aspects (e.g., the SSB set is associated with one or more physical cells, such as during an SMTC window).

[0107] UE 802 can be configured, for example, to report, each measured SSB 814 at an altitude of UE 802 relative to at least one physical cell (e.g., from the number of SSBs 810 provided / transmitted from base station 804) based on a reporting configuration associated with the altitude of UE 802 and at least one of the altitude, location, rate, or speed of UE 802. In various aspects, UE 802 can be configured to report each measured SSB 814 to base station 804.

[0108] As described above, the aspects of this paper provide additional flexibility for beam measurement beyond that offered in current solutions. These aspects enable the SMTC to have the flexibility to allow a UE (e.g., UAV) to measure a first set of beams (or [cell, beam] ordered pairs) at an altitude range (e.g., below or level with clutter) and different sets of beams at different altitude ranges (e.g., above an altitude where the LOS is typically expected) (including: for different cells, and / or for different beams in different altitude ranges / intervals). In this context, and referring to the above... Figure 8 The following describes Figure 9-11 .

[0109] Figure 9 Figure 900 illustrates an example configuration for altitude-dependent measurement and reporting in various aspects. Figure 900 shows a UE 902 (which may be a UAV or may be associated with a UAV) that can be configured to communicate with a network node / base station (e.g., gNB). For example, Figure 900 includes a first base station 904 (e.g., serving / serving base station) of a first physical cell (cell 1), a second base station 904' (e.g., neighboring base station) of a second physical cell (cell 2), and a third base station 904" (e.g., neighboring base station) of a third physical cell (cell 3). The base stations can perform any of the aspects described in conjunction with base stations 402 or 804. Figure 9 The aspects described can be performed by base station 402 or 804. The aspects shown in Figure 900 can be used for altitude-dependent measurement and reporting configuration of UE 902 (e.g., via SMTC), as described herein.

[0110] Figure 900 illustrates SMTC 914, which configures UE 902 for three different altitude ranges / intervals, for example: altitude range 906, altitude range 908, and altitude range 910. Although aspects are described for ranges or intervals, one or more altitude thresholds can also be used to apply these aspects. As shown for SMTC 914, altitude range 1 (e.g., altitude range 906) indicates that for cell 1, UE 902 should measure SSB 1, SSB 2, and SSB 3; for cell 2, UE 902 should measure SSB 3, SSB 4, and SSB 5; and for cell 3, UE 902 should measure SSB 2. As shown for SMTC 914, altitude range 2 (e.g., altitude range 908) indicates that for cell 1, UE 902 should measure SSB 1, SSB 2, and SSB 3; for cell 2, UE 902 should measure SSB 3 and SSB 4; and for cell 3, UE 902 should measure SSB 2 and SSB 6. As shown for SMTC 914, altitude range 3 (e.g., altitude range 910) indicates that for cell 1, UE 902 should measure SSB 1 and SSB 2; for cell 2, UE 902 should measure SSB 3; and for cell 3, UE 902 should measure SSB 2, SSB 5, and SSB 8.

[0111] The elevation ranges 906, 908, and / or 910 can be defined or delimited by minimum and / or maximum elevation values, as described herein (e.g., relative to those described below). Figure 10-12 In all aspects, if no minimum altitude value is specified, it may default to zero (or another pre-configured value); if no maximum altitude value is specified, it may default to infinity (or another pre-configured value). In the example shown in Figure 900, the minimum altitude value may be altitude value 1 (e.g., the ground) for altitude range 906 (e.g., below or at the level of debris such as buildings and / or other structures), and the maximum altitude value may be altitude value 2 for altitude range 906. In the example shown in Figure 900, the minimum altitude value may be altitude value 2 for altitude range 908 (e.g., above the altitude of most debris such as buildings and / or other structures in which LOS may exist), and the maximum altitude value may be altitude value 3 for altitude range 908. In the example shown in Figure 900, the minimum altitude value may be altitude value 3 for altitude range 910 (e.g., above the altitude of debris such as buildings and / or other structures in which LOS can generally be expected), and the maximum altitude value may be altitude value 4 for altitude range 910.

[0112] In each aspect, the boundaries of altitude ranges 906, 908, and / or 910 can be associated with a hysteresis value defining a hysteresis interval 912. That is, when the UE 902 crosses or operates at altitude 916 near the boundary of an altitude range / interval, it can switch to a configuration for the adjacent altitude range / interval once it is outside the hysteresis interval 912. This reduces or eliminates "ping-pong" or oscillations between different configurations and saves power / provides consistent measurements for the UE 902. In each aspect, the hysteresis value can be a quantity in length units (e.g., 1m, 2m, etc.), a percentage of an altitude range / interval (e.g., 0.1%, 1%, 5%, etc.), etc.

[0113] The various aspects presented in this paper envision any number of altitude ranges, SSBs to be measured, physical cells, hysteresis intervals / values, etc., and the aspects shown are provided as examples.

[0114] Figure 10 Figure 1000 illustrates example configurations for altitude-dependent measurements and reporting in various aspects. For example, a configuration may be provided to UE 802 at 808. As described herein, the SMTC can include altitude-specific flexibility in adding to the measurement object (e.g., which may be a measObjectNR or other measurement object) by indicating the altitude-specific SSBs to be measured. Figure 1000 shows a portion of the SMTC (e.g., the measurement object IE) where the altitude-specific SSBs to be measured are included for the UE.

[0115] For example, the aspects provided by the SMTC may include an indication 1002 for an altitude-specific SSB to be measured. The indication 1002 for the altitude-specific SSB to be measured may reference a number of altitude ranges 1004, for which the SMTC may configure the UE for one or more specific SSBs to be measured by the UE. An IE 1006 associated with an altitude range may be provided to each SSB 1008 to be measured. The altitude range may be based on at least one of a minimum altitude value or a maximum altitude value. In the aspects, if no minimum altitude value is specified, it may default to zero (or another pre-configured value); if no maximum altitude value is specified, it may default to infinity (or another pre-configured value). In the aspects, the IE 1006 for a given SSB 1008 to be measured may include a hysteresis value that defines a hysteresis range and is associated with the altitude range / interval boundary. In some aspects, the measurement objects for SMTC may include multiple IE 1006 for the corresponding multiple SSB 1008 to be measured.

[0116] Therefore, the various aspects of the altitude-dependent measurement and reporting configurations described herein, via the configuration of altitude-specific measurements for synchronization signals, improve the flexibility and accuracy of location and mobility measurements at the UE. By implementing the configuration of altitude-specific measurements with altitude ranges / intervals for synchronization signals, these aspects enhance the flexibility and accuracy of location and mobility measurements at the UE based on the UE's altitude (e.g., for UAVs) for specific synchronization signals.

[0117] Figure 11 Figure 1100 illustrates example configurations for altitude-dependent measurements and reporting in various aspects. For example, a configuration may be provided to UE 802 at 808. In various aspects, new configurations for SMTC may include altitude ranges / intervals. In one example, the SSB-MTC configuration for SMTC may include different SSBs (e.g., ssb-ToMeasure) to be measured for different altitude ranges / intervals. Figure 1100 shows a portion of SMTC (e.g., SSB-MTC object 1110) where, for the UE, an altitude-specific SSB 1102 is included to be measured.

[0118] For example, aspects of Figure 1100 provide that the SMTC can include an indication (e.g., SSB-ToMeasureAltudeBasedList-r18) of an altitude-specific SSB 1102 to be measured in the SSB-MTC object 1110. The altitude-specific SSB 1102 to be measured can include a list of altitude-dependent SSBs for measurement (e.g., in some examples, it may be referred to as "ssb-ToMeasure"). When the UE is within an altitude range indicated by a height range parameter (e.g., in some examples, it may be referred to as "heightRange" or "altitudeRange"), the UE can ignore ssb-ToMeasure (e.g., without a suffix), and if a corresponding ssb-ToMeasure-r18 exists, the corresponding ssb-ToMeasure-r18 can be applied; otherwise, if no ssb-ToMeasure-r18 exists, the UE can perform measurements on all SS blocks. When the UE is outside all altitude ranges (e.g., height ranges) indicated by altitudeRange (if any), ssb-ToMeasure (e.g., without a suffix) may be applied. For each altitude range, a minimum altitude parameter (e.g., which may be referred to as "heightMin" or "altitudeMin" in some examples) may indicate the minimum height in meters, a maximum altitude parameter (e.g., which may be referred to as "heightMax" or "altitudeMax" in some examples) may indicate the maximum height relative to sea level in meters, and a parameter, which may be referred to as "heightHyst" or "altitudeHyst" if included, may indicate the hysteresis used to determine the altitude range (e.g., in distances such as meters). For example, when altitudeHyst is configured for an altitude range, the UE may consider itself to be in the range if altitudeMin ≤ UE altitude ≤ altitudeMax, and after entering the range, the UE may consider itself to be within the range if (altitudeMin – altitudeHyst) ≤ UE altitude ≤ (altitudeMax + altitudeHyst). For each altitudeRange, if altitudeMin does not exist, the value minAltitude-r18 can be used, and if altitudeMax does not exist, the value maxAltitude-r18 can be used.

[0119] An altitude-specific SSB 1102 to be measured can be associated with a list of one or more PCIs 1104 for a corresponding physical cell. For the corresponding physical cell, the SMTC can configure the UE for one or more specific SSBs to be measured by the UE. An IE 1106 (e.g., SSB-ToMeasureAltudeBaed-r18) associated with an altitude range can be provided to each SSB 1108 to be measured. The altitude range can be based on at least one of a minimum altitude value or a maximum altitude value. In all aspects, if no minimum altitude value is specified, it can default to zero (or another pre-configured value); if no maximum altitude value is specified, it can default to infinity (or another pre-configured value). In all aspects, a hysteresis value that can define a hysteresis range and is associated with the altitude range / interval boundary can be included in the IE 1106 for a given SSB 1108 to be measured. In some aspects, the SSB-MTC object 1110 for SMTC may include multiple IE 1106 for the corresponding multiple SSB 1108 to be measured.

[0120] Therefore, this paper improves the flexibility and accuracy of positioning and mobility measurements at the UE by configuring altitude-dependent measurement and reporting configurations for altitude-specific measurements based on synchronization signals. Altitude ranges are achieved by providing SSB-MTC sub-configurations for each element in the SSB-MTC list, enabling flexibility and accuracy for positioning and mobility measurements at the UE based on specific synchronization signals and UE altitude.

[0121] Figure 12 Figure 1200 illustrates example configurations for altitude-dependent measurements and reporting in various aspects. In each aspect, the new configuration for SMTC may include an altitude range / interval. For example, a configuration may be provided to UE 802 at 808. In one example, SMTC list 1206 may be included in a measurement object (e.g., measObjectNR or other measurement object), where SMTC list 1206 references a new SSB-MTC list 1202. Each element in the new SSB-MTC list 1202 may represent an SSB-MTC sub-configuration with a corresponding altitude range / interval for the SSB 1208 to be measured.

[0122] For example, aspects of Figure 1200 provide that the SMTC can include indications of altitude-specific SSBs to be measured in a new SSB-MTC list 1202, which in turn references SSB-MTC objects 1210. Each SSB-MTC object 1210 can be associated with a list of one or more PCIs 1204 for a corresponding physical cell, for which the SMTC can configure the UE for one or more specific SSBs to be measured by the UE. A corresponding SSB-MTC object in the SSB-MTC objects 1210 associated with an altitude range can be provided to each SSB 1208 to be measured. The altitude range can be based on at least one of a minimum altitude value or a maximum altitude value. In this aspect, if no minimum altitude value is specified, it can default to zero (or another pre-configured value); if no maximum altitude value is specified, it can default to infinity (or another pre-configured value). In various aspects, an SSB-MTC object 1210 for a given SSB 1208 to be measured may include hysteresis values ​​that can define hysteresis ranges and are associated with altitude range / interval boundaries. In some aspects, for an SMTC, multiple SSB-MTC objects 1210 may be included for multiple corresponding SSBs 1208 to be measured, while in other aspects, an SSB-MTC object 1210 for an SMTC may include multiple SSBs 1208 to be measured.

[0123] Therefore, this paper improves the flexibility and accuracy of positioning and mobility measurements at the UE by configuring altitude-dependent measurement and reporting configurations for altitude-specific measurements based on synchronization signals. Altitude ranges are achieved by providing SSB-MTC sub-configurations for each element in the SSB-MTC list, enabling flexibility and accuracy for positioning and mobility measurements at the UE based on specific synchronization signals and UE altitude.

[0124] Figure 13 This is a flowchart 1300 of a method for wireless communication in various aspects. The method can be performed by a UE (e.g., UE 104, 406, 416, 418, 516, 802, 902; device 1704). In some aspects, the method may include combining... Figure 8 The communication process described in the text and / or in the aspects of the communication process described and / or in the text Figure 4Or the aspects described in 9-12. This method provides an altitude-dependent measurement and reporting configuration that enables improved flexibility and accuracy for location and mobility measurements at the UE via configuration of altitude-specific measurements for the synchronization signal. By implementing configuration of altitude-specific measurements with altitude ranges / intervals for the synchronization signal, these aspects improve the flexibility and accuracy for location and mobility measurements at the UE based on the UE's altitude (e.g., for a UAV) for a specific synchronization signal.

[0125] At 1302, the UE receives an SMTC from the network node, wherein the SMTC indicates an altitude range associated with an SSB set and at least one cell identifier corresponding to at least one physical cell. As an example, this transmission can be at least partially... Figure 17 The components 198, transceiver 1722, and / or antenna 1780 are used to perform this function. Figure 8-12 An example of UE 802 receiving such SMTC from a network node (e.g., base station 804) is shown.

[0126] Base station 804 can be configured (at 806) for SMTC 808 of UE 802 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 1200 in the middle), of which SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the reference indicates the presence of at least one cell identifier and an SSB set (e.g., Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 The altitude range (or altitude parameter) associated with 1208 in the data (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210 in the example), the at least one cell identifier corresponds to at least one physical cell (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 (1208 in the middle). In various aspects, SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the text can be indicated by the altitude-specific SSB to be measured (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208, this includes adding altitude-specific flexibility to the measurement object (e.g., measObjectNR). In each aspect, this newly added altitude-specific flexibility can be implemented for existing measObjectNR measurement objects. In each aspect, new configurations for the SMTC808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the range can include an altitude range / interval (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 1210 in the example. In one example, for SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 SSB-MTC configuration of 1200 (e.g., Figure 11 1110 in the middle; Figure 12 1210 in the text can include different altitude ranges / intervals (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 In example 1210), different SSBs to be measured (e.g., ssb-ToMeasure). In another example, a new list of SSB-MTCs (e.g., Figure 12 1202 in the list can be included in the measurement object (e.g., measObjectNR), where the new SSB-MTC list (e.g., Figure 12 Each element in (1202) can represent a range / interval with a corresponding altitude (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 The SSB-MTC sub-configuration (1210 in the example). Hysteresis ranges can be defined in various aspects (e.g., Figure 9 912 in the middle; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 The hysteresis value of 1210 in the middle can be compared with the altitude range / interval boundary (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (associated with 1210 in the original text). Base station 804 can be configured to provide / transmit SMTC 808 (e.g., for UE 802) for UE 802. Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 (1200 in the middle).

[0127] At 1304, the UE measures the SSB value for each SSB in the SSB set based on the measurement object configuration and the UE's altitude. As an example, the measurement can be at least partially determined by... Figure 17 The components 198, transceiver 1722, and / or antenna 1780 are used to perform this function. Figure 8-12 An example of such SSB values ​​measured by UE 802 for SSBs from network nodes (e.g., base station 804) is shown. Figure 8 An example is shown where the UE measures a subset of the SSB based on the UE's altitude.

[0128] Base station 804 can also be configured to provide / transmit a set of SSBs for UE 802 (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208 of the above). In various aspects, base station 804 can be a serving / serving cell or a neighboring cell, and can be configured to transmit information for UE 802, including information in SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The SSB set indicated in 1200 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208) a number of SSB 810 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). In various aspects, different base stations can be configured to send different numbers of SSB 810 to UE802 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). A cell can be a physical cell with a corresponding PCI (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 (1208 in the example). In all aspects, at least one physical cell in the UE 802 environment (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the text can be a serving / serving cell, and SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 The 1000 in the UE 802 context can be a cell-specific SMTC for the serving / serving cell. In some aspects, at least one physical cell in the UE 802 environment (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the context can include two or more physical cells (e.g., serving / serving cell and neighboring cells) (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the middle), and SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the middle can be used to target physical cells (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 Configure UE 802 (1208) as described in this document.

[0129] UE 802 can be configured to obtain its altitude. In various aspects, to obtain the altitude, UE 802 can be configured to measure (at 812) its altitude based on information received by UE 802 and / or receive an indication of UE 802's altitude from a network node or network entity (e.g., base station 804). The altitude of UE 802 can be quantified relative to ground, sea level, debris, etc. UE 802 can be configured based on SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The elevation of UE 802 (at 812) is used to measure the elevation of at least one physical cell (e.g., 1200) and UE 802 (at 812). Figure 9 The numbers 904 (Community 1), 904' (Community 2), and 904" (Community 3) are included. Figure 11 1104 in the middle; Figure 12 Each SSB in the SSB set (e.g., from the number of SSBs 810 provided / transmitted from base station 804) of 1208) (e.g., in Figure 9 914 in the middle; Figure 11 1104 in the middle; Figure 12 The SSB value in 1208 (of which).

[0130] UE 802 can be configured to report based on a reporting configuration associated with the altitude of UE 802 and at least one of the following: altitude, location, rate, or speed of UE 802. For example, for base station 804, reporting is made at the altitude of UE 802 relative to at least one physical cell (e.g., ...). Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 Each measured SSB 814 (e.g., in the SSB set of 1208) (e.g., from the number of SSBs 810 provided / transmitted from base station 804) is a separate SSB. Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). In various aspects, UE 802 can be configured to report each measured SSB 814 to base station 804 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (Among 1208).

[0131] Figure 14This is a flowchart 1400 of a method for wireless communication in various aspects. The method can be performed by a UE (e.g., UE 104, 406, 416, 418, 516, 802, 902; device 1704). In some aspects, the method may include combining... Figure 8 The communication process described in the text and / or in the aspects of the communication process described and / or in the text Figure 4 Or the aspects described in 9-12. This method provides an altitude-dependent measurement and reporting configuration that enables improved flexibility and accuracy for location and mobility measurements at the UE via configuration of altitude-specific measurements for the synchronization signal. By implementing configuration of altitude-specific measurements with altitude ranges / intervals for the synchronization signal, these aspects improve the flexibility and accuracy for location and mobility measurements at the UE based on the UE's altitude (e.g., for a UAV) for a specific synchronization signal.

[0132] At 1402, the UE receives an SMTC from the network node, wherein the SMTC indicates an altitude range associated with an SSB set and at least one cell identifier corresponding to at least one physical cell. As an example, this transmission can be at least partially... Figure 17 The components 198, transceiver 1722, and / or antenna 1780 are used to perform this function. Figure 8-12 An example of UE 802 receiving such SMTC from a network node (e.g., base station 804) is shown.

[0133] Base station 804 can be configured (at 806) for SMTC 808 of UE 802 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 1200 in the middle), of which SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the text indicates the presence of at least one cell identifier and SSB set (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 The altitude range (or altitude parameter) associated with 1208 in the data (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210 in the example), the at least one cell identifier corresponds to at least one physical cell (e.g., Figure 9Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 (1208 in the middle). In various aspects, SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the text can be indicated by the altitude-specific SSB to be measured (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208, this includes adding altitude-specific flexibility to the measurement object (e.g., measObjectNR). In various aspects, this newly added altitude-specific flexibility can be implemented for existing measObjectNR measurement objects. In various aspects, new configurations for the SMTC808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the range can include an altitude range / interval (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 1210 in the example. In one example, for SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 SSB-MTC configuration of 1200 (e.g., Figure 11 1110 in the middle; Figure 12 1210 in the text can include different altitude ranges / intervals (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 In example 1210), different SSBs to be measured (e.g., ssb-ToMeasure). In another example, a new list of SSB-MTCs (e.g., Figure 12 1202 in the list can be included in the measurement object (e.g., measObjectNR), where the new SSB-MTC list (e.g., Figure 12Each element in (1202) can represent an SSB-MTC sub-configuration with a corresponding altitude range / interval (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210 in the text). In each aspect, the lag range can be defined (e.g., Figure 9 912 in the middle; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 The hysteresis value of 1210 in the middle can be compared with the altitude range / interval boundary (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (associated with 1210 in the original text). Base station 804 can be configured to provide / transmit SMTC 808 (e.g., for UE 802) for UE 802. Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 (1200 in the middle).

[0134] At 1404, the UE obtains its altitude. As an example, the measurement can be at least partially derived from... Figure 17 The components 198, transceiver 1722, and / or antenna 1780 are used to perform this function. Figure 8-12 An example of how UE 802 obtains such an altitude indication is shown. Figure 8 An example is shown where the UE measures a subset of the SSB based on the UE's altitude.

[0135] The UE can be configured to obtain its altitude, for example, by being configured to measure the UE's altitude based on information received by the UE, or by being configured to receive an indication of the UE's altitude from a network node or network entity. UE 802 can be configured to obtain its altitude. In various aspects, to obtain its altitude, UE 802 can be configured to measure (at 812) its altitude based on information received by UE 802 and / or receive an indication of the UE's altitude from a network node or network entity (e.g., base station 804). Base station 804 can be configured to obtain the altitude of UE 802. In various aspects, to obtain its altitude, base station 804 can be configured to measure (similar to 812) the altitude of UE 802 based on information received from UE 802 or from another network node / entity. Base station 804 can be configured to provide an indication of the UE's altitude to UE 802. The altitude of UE 802 can be quantified relative to ground, sea level, debris, etc.

[0136] At 1406, the UE measures the SSB value for each SSB in the SSB set based on the measurement object configuration and the UE's altitude. As an example, the measurement can be at least partially determined by... Figure 17 The components 198, transceiver 1722, and / or antenna 1780 are used to perform this function. Figure 8-12 An example of such SSB values ​​measured by UE 802 for SSBs from network nodes (e.g., base station 804) is shown. Figure 8 An example is shown where the UE measures a subset of the SSB based on the UE's altitude.

[0137] UE 802 can be configured to be based on SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The elevation of UE 802 (at 812) is used to measure the elevation of at least one physical cell (e.g., 1200) and UE 802 (at 812). Figure 9 The numbers 904 (Community 1), 904' (Community 2), and 904" (Community 3) are included. Figure 9 1104 in the middle; Figure 12 Each SSB in the SSB set (e.g., from the number of SSBs 810 provided / transmitted from base station 804) of 1208) (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 The SSB value (in 1208). For example, base station 804 can also be configured to provide / transmit the SSB set for UE 802 (e.g., in 1208). Figure 9 914 in Figure 10 1008 in Figure 11 1108 in Figure 12 In 1208 of the above). In various aspects, base station 804 can be a serving / serving cell or a neighboring cell, and can be configured to transmit information for UE 802, including information in SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The SSB set indicated in 1200 (e.g., in Figure 9 914 in Figure 10 1008 in Figure 11 1108 in Figure 12 In 1208) a number of SSB 810 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). In various aspects, different base stations can be configured to send different numbers of SSB 810 to UE 802 (e.g., Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (1208 in the example). A cell can be a physical cell with a corresponding PCI (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 (1208 in the example). In all aspects, at least one physical cell in the UE 802 environment (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the text can be a serving / serving cell, and SMTC808 (e.g., Figure 9 914 in the middle; Figure 10 The 1000 in the UE 802 context can be a cell-specific SMTC for the serving / serving cell. In some aspects, at least one physical cell in the UE 802 environment (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the context can include two or more physical cells (e.g., serving / serving cell and neighboring cells) (e.g., Figure 9Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the middle), and SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the middle can be used to target physical cells (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 Configure UE 802 (1208) as described in this document.

[0138] UE 802 can be configured to report based on a reporting configuration associated with the altitude of UE 802 and at least one of the following: altitude, location, rate, or speed of UE 802. For example, for base station 804, reporting is made at the altitude of UE 802 relative to at least one physical cell (e.g., ...). Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 Each measured SSB 814 (e.g., in the SSB set of 1208) (e.g., from the number of SSBs 810 provided / transmitted from base station 804) is a separate SSB. Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). In various aspects, UE 802 can be configured to report each measured SSB 814 to base station 804 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (Among 1208).

[0139] Figure 15 This is a flowchart 1500 of a method for wireless communication in various aspects. The method can be performed by base stations (e.g., base stations 102, 402, 804, first base station 904, second base station 904', third base station 904"; NR cell A 502, NR cell B 504; network entities 1702, 1802, 1960). In some aspects, the method may include combining... Figure 8 The communication process described in the text and / or in the aspects of the communication process described and / or in the text Figure 4Or the aspects described in 9-12. This method provides an altitude-dependent measurement and reporting configuration that enables improved flexibility and accuracy for location and mobility measurements at the UE via configuration of altitude-specific measurements for the synchronization signal. By implementing configuration of altitude-specific measurements with altitude ranges / intervals for the synchronization signal, these aspects improve the flexibility and accuracy for location and mobility measurements at the UE based on the UE's altitude (e.g., for a UAV) for a specific synchronization signal.

[0140] At 1502, the network node configures the SMTC for the UE, where the SMTC indicates the altitude range associated with at least one cell identifier and SSB set corresponding to at least one physical cell. As an example, the configuration can be at least partially determined by... Figure 18 The components 199, transceiver 1846, and / or antenna 1880 are used to perform this function. Figure 8-12 An example of such SMTC configured by base station 804 for UE (e.g., UE 802) is shown.

[0141] Base station 804 can be configured (at 806) for SMTC 808 of UE 802 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 1200 in the middle), of which SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the text indicates the presence of at least one cell identifier and SSB set (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 The altitude range (or altitude parameter) associated with 1208 in the data (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210 in the example), the at least one cell identifier corresponds to at least one physical cell (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 (1208 in the middle). In various aspects, SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the text can be indicated by the altitude-specific SSB to be measured (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208, this includes adding altitude-specific flexibility to the measurement object (e.g., measObjectNR). In various aspects, this newly added altitude-specific flexibility can be implemented for existing measObjectNR measurement objects. In various aspects, new configurations for the SMTC808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the range can include an altitude range / interval (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 1210 in the example. In one example, for SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 SSB-MTC configuration of 1200 (e.g., Figure 11 1110 in the middle; Figure 12 1210 in the text can include different altitude ranges / intervals (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210) Different SSBs to be measured (e.g., ssb-ToMeasure) (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208 of them). In another example, the new SSB-MTC list (e.g., Figure 12 1202 in the list can be included in the measurement object (e.g., measObjectNR), where the new SSB-MTC list (e.g., Figure 12 Each element in (1202) can represent an SSB-MTC sub-configuration with a corresponding altitude range / interval (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210 in the text). In each aspect, the lag range can be defined (e.g., Figure 9 912 in the middle; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 The hysteresis value of 1210 in the middle can be compared with the altitude range / interval boundary (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (associated with 1210 in the original text). Base station 804 can be configured to provide / transmit SMTC 808 (e.g., for UE 802) for UE 802. Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 (1200 in the middle).

[0142] At 1504, the network node provides the set of SSBs indicated in the SMTC. As an example, this provision / transmission can be at least partially provided by... Figure 18 The components 199, transceiver 1846, and / or antenna 1880 are used to perform this function. Figure 8-12 An example of such SMTC configured by base station 804 for UE (e.g., UE 802) is shown. Figure 8 An example of a base station transmitting SSBs in multiple beam directions is shown. Figure 5 An example of an SSB burst is shown.

[0143] Base station 804 can also be configured to provide / transmit a set of SSBs for UE 802 (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208 of the above). In various aspects, base station 804 can be a serving / serving cell or a neighboring cell, and can be configured to transmit information for UE 802, including information in SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The SSB set indicated in 1200 (e.g., in Figure 9 914 in Figure 10 1008 in Figure 11 1108 in Figure 12In 1208) a number of SSB 810 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). In various aspects, different base stations can be configured to send different numbers of SSB 810 to UE802 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (Among 1208). A cell can be a physical cell with a corresponding PCI (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 (1208 in the example). In all aspects, at least one physical cell in the environment of UE 802 (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the text can be a serving / serving cell, and SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 The 1000 in the UE 802 context can be a cell-specific SMTC for the serving / serving cell. In some aspects, at least one physical cell in the UE 802 environment can include two or more physical cells (e.g., serving / serving cell and neighboring cells). Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the middle), and SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the middle can be used to target physical cells (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 Configure UE 802 (1208) as described in this document.

[0144] UE 802 can be configured to report based on a reporting configuration associated with the altitude of UE 802 and at least one of the following: altitude, location, rate, or speed of UE 802. For example, for base station 804, reporting is made at the altitude of UE 802 relative to at least one physical cell (e.g., ...). Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 Each measured SSB 814 (e.g., in the SSB set of 1208) (e.g., from the number of SSBs 810 provided / transmitted from base station 804) is a separate SSB. Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). In various aspects, UE 802 can be configured to report each measured SSB 814 to base station 804 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (Among 1208).

[0145] Figure 16 This is a flowchart 1600 of a method for wireless communication in various aspects. The method can be performed by base stations (e.g., base stations 102, 402, 804, first base station 904, second base station 904', third base station 904"; NR cell A 502, NR cell B 504; network entities 1702, 1802, 1960). In some aspects, the method may include combining... Figure 8 The communication process described in the text and / or in the aspects of the communication process described and / or in the text Figure 4 Or the aspects described in 9-12. This method provides an altitude-dependent measurement and reporting configuration that enables improved flexibility and accuracy for location and mobility measurements at the UE via configuration of altitude-specific measurements for the synchronization signal. By implementing configuration of altitude-specific measurements with altitude ranges / intervals for the synchronization signal, these aspects improve the flexibility and accuracy for location and mobility measurements at the UE based on the UE's altitude (e.g., for a UAV) for a specific synchronization signal.

[0146] At 1602, the network node configures the SMTC for the UE, where the SMTC indicates the altitude range associated with at least one cell identifier and a set of SSBs corresponding to at least one physical cell. As an example, the configuration can be at least partially determined by... Figure 18 The components 199, transceiver 1846, and / or antenna 1880 are used to perform this function. Figure 8-12An example of such SMTC configured by base station 804 for UE (e.g., UE 802) is shown.

[0147] Base station 804 can be configured for UE 802 (at 806) SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 1200 in the middle), of which SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the text indicates the presence of at least one cell identifier and SSB set (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 The altitude range (or altitude parameter) associated with 1208 in the data (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210 in the example), the at least one cell identifier corresponds to at least one physical cell (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 (1208 in the middle). In various aspects, SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the text can be indicated by the altitude-specific SSB to be measured (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208, this includes adding altitude-specific flexibility to the measurement object (e.g., measObjectNR). In various aspects, this newly added altitude-specific flexibility can be implemented for existing measObjectNR measurement objects. In various aspects, new configurations for the SMTC808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12The 1200 in the range can include an altitude range / interval (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 1210 in the example. In one example, for SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 SSB-MTC configuration of 1200 (e.g., Figure 11 1110 in the middle; Figure 12 1210 in the text can include different altitude ranges / intervals (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210) Different SSBs to be measured (e.g., ssb-ToMeasure) (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208 of them). In another example, the new SSB-MTC list (e.g., Figure 12 1202 in the list can be included in the measurement object (e.g., measObjectNR), where the new SSB-MTC list (e.g., Figure 12 Each element in (1202) can represent an SSB-MTC sub-configuration with a corresponding altitude range / interval (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (1210 in the text). In each aspect, the lag range can be defined (e.g., Figure 9 912 in the middle; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 The hysteresis value of 1210 in the middle can be compared with the altitude range / interval boundary (e.g., Figure 9 906, 908, and 910; targeting Figure 10 1006 in the middle; targeting Figure 11 1106 in the middle; targeting Figure 12 (associated with 1210 in the original text). Base station 804 can be configured to provide / transmit SMTC 808 (e.g., for UE 802) for UE 802. Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 (1200 in the middle).

[0148] At position 1604, the UE obtains its altitude and provides the UE with an indication of its altitude. As an example, this altitude can be obtained at least partially by... Figure 18 The components 199, transceiver 1846, and / or antenna 1880 are used to perform this function. Figure 8-12 An example of such an altitude obtained by base station 804 for a UE (e.g., UE 802) is shown.

[0149] A base station / network node can be configured to obtain the altitude of the UE, for example, by being configured to measure the altitude of the UE based on information received from the UE, or by being configured to receive an indication of the UE's altitude from another network node or network entity. Base station 804 can be configured to obtain the altitude of UE 802. In various aspects, to obtain the altitude, base station 804 can be configured to measure (similar to 812) the altitude of UE 802 based on information received from UE 802 or from another network node / entity. Base station 804 can be configured to provide an indication of the altitude of UE 802 to UE 802. The altitude of UE 802 can be quantified relative to ground, sea level, debris, etc.

[0150] At 1606, the network node provides the set of SSBs indicated in the SMTC. As an example, this provision / transmission can be at least partially provided by... Figure 18 The components 199, transceiver 1846, and / or antenna 1880 are used to perform this function. Figure 8-12 An example of such SMTC configured by base station 804 for UE (e.g., UE 802) is shown. Figure 8 An example of a base station transmitting SSBs in multiple beam directions is shown. Figure 5 An example of an SSB burst is shown.

[0151] Base station 804 can also be configured to provide / transmit a set of SSBs for UE 802 (e.g., in...). Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 In 1208 of the above). In various aspects, base station 804 can be a serving / serving cell or a neighboring cell, and can be configured to transmit information for UE 802, including information in SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12The SSB set indicated in 1200 (e.g., in Figure 9 914 in Figure 10 1008 in Figure 11 1108 in Figure 12 In 1208) a number of SSB 810 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). In various aspects, different base stations can be configured to send different numbers of SSB 810 to UE802 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). A cell can be a physical cell with a corresponding PCI (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 (1208 in the example). In all aspects, at least one physical cell in the UE 802 environment (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the text can be a serving / serving cell, and SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 The 1000 in the UE 802 context can be a cell-specific SMTC for the serving / serving cell. In some aspects, at least one physical cell in the UE 802 environment can include two or more physical cells (e.g., serving / serving cell and neighboring cells). Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 1208 in the middle), and SMTC 808 (e.g., Figure 9 914 in the middle; Figure 10 1000 in; Figure 11 1100 in the middle; Figure 12 The 1200 in the middle can be used to target physical cells (e.g., Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 Configure UE 802 (1208) as described in this document.

[0152] UE 802 can be configured to report based on a reporting configuration associated with the altitude of UE 802 and at least one of the following: altitude, location, rate, or speed of UE 802. For example, for base station 804, reporting is made at the altitude of UE 802 relative to at least one physical cell (e.g., ...). Figure 9 Among them, 904 (Community 1), 904' (Community 2), and 904" (Community 3); Figure 11 1104 in the middle; Figure 12 Each measured SSB 814 (e.g., in the SSB set of 1208) (e.g., from the number of SSBs 810 provided / transmitted from base station 804) is a separate SSB. Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (In 1208). In various aspects, UE 802 can be configured to report each measured SSB 814 to base station 804 (e.g., in Figure 9 914 in the middle; Figure 10 1008 in the middle; Figure 11 1108 in the middle; Figure 12 (Among 1208).

[0153] Figure 17Figure 1700 illustrates an example of a hardware implementation for device 1704. Device 1704 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, device 1704 may include at least one cellular baseband processor 1724 (also referred to as a modem) coupled to one or more transceivers 1722 (e.g., cellular RF transceivers). Cellular baseband processor 1724 may include at least one on-chip memory 1724'. In some aspects, device 1704 may also include one or more Subscriber Identity Module (SIM) cards 1720 and at least one application processor 1706 coupled to a Secure Digital Card (SD) card 1708 and a screen 1710. Application processor 1706 may include on-chip memory 1706'. In some aspects, device 1704 may also include a Bluetooth module 1712, a WLAN module 1714, an SPS module 1716 (e.g., a GNSS module), one or more sensor modules 1718 (e.g., a barometer / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies used for positioning), an additional memory module 1726, a power supply 1730, and / or a camera 1732. Bluetooth module 1712, WLAN module 1714, and SPS module 1716 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 1712, WLAN module 1714, and SPS module 1716 may include their own dedicated antennas and / or communicate using antenna 1780. Cellular baseband processor 1724 communicates with UE 104 and / or RU associated with network entity 1702 via transceiver 1722 through one or more antennas 1780. Cellular baseband processor 1724 and application processor 1706 may each include computer-readable media / memory 1724', 1706' respectively. Additional memory module 1726 may also be considered computer-readable media / memory. Each computer-readable media / memory 1724', 1706', 1726 may be non-transitory. Cellular baseband processor 1724 and application processor 1706 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1724 / application processor 1706, the software causes cellular baseband processor 1724 / application processor 1706 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by cellular baseband processor 1724 / application processor 1706 during software execution.Cellular baseband processor 1724 / application processor 1706 may be a component of UE 350 and may include at least one of TX processor 368, RX processor 356, and controller / processor 359 and / or at least one memory 360. In one configuration, device 1704 may be at least one processor chip (modem and / or application) and includes only cellular baseband processor 1724 and / or application processor 1706, while in another configuration, device 1704 may be the entire UE (see, for example). Figure 3 The UE 350 includes an additional module of the device 1704.

[0154] As described above, component 198 can be configured to receive a measurement object configuration from a network node, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. Component 198 can also be configured to measure each SSB associated with one or more cell identifiers based on the absence of a corresponding set of SSBs for the additional altitude parameter in the SMTC. Component 198 can be configured to obtain the altitude of the UE. To obtain the altitude of the UE, component 198 can be configured to measure the altitude of the UE based on information received by the UE and / or receive an indication of the UE's altitude from a network node or network entity. Component 198 can also be configured to perform a combination... Figure 13-16 Any aspect described in the flowchart of any item in the document, and / or by the UE for Figure 4 , 5Or any aspect of any of 8-12 executed. Component 198 may be within cellular baseband processor 1724, application processor 1706, or both cellular baseband processor 1724 and application processor 1706. Component 198 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the process / algorithm individually or in combination. As shown, device 1704 may include various components configured for various functions. In one configuration, device 1704 (especially cellular baseband processor 1724 and / or application processor 1706) may include units for receiving measurement object configuration from a network node, wherein the measurement object configuration indicates at least one altitude parameter associated with an SSB set. In this configuration, device 1704 (especially cellular baseband processor 1724 and / or application processor 1706) may include units for measuring an SSB value for each SSB in the SSB set based on the measurement object configuration and the UE's altitude. In one configuration, device 1704 (especially cellular baseband processor 1724 and / or application processor 1706) may include units for measuring a second SSB value for each SSB associated with one or more cell identifiers based on the absence of a corresponding SSB set for an additional altitude range in the SMTC. In one configuration, device 1704 (especially cellular baseband processor 1724 and / or application processor 1706) may include units for obtaining the UE's altitude. To obtain the UE's altitude, device 1704 (especially cellular baseband processor 1724 and / or application processor 1706) may include units for measuring the UE's altitude based on information received by the UE and / or receiving an indication of the UE's altitude from a network node or network entity. The device may also include units for performing a combination Figure 13-16 Any aspect described in the flowchart of any item in the document, and / or by the UE for Figure 4 , 5 A unit that performs any aspect of any of the aspects described in 8-12. The unit may be component 198 of device 1704 configured to perform the functions described by the unit. As described above, device 1704 may include TX processor 368, RX processor 356, and controller / processor 359. Therefore, in one configuration, the unit may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described by the unit.

[0155] Figure 18Figure 1800 illustrates an example of a hardware implementation for network entity 1802. Network entity 1802 may be a BS, a component of a BS, or may implement BS functionality. Network entity 1802 may include at least one of CU 1810, DU 1830, or RU 1840. For example, depending on the layer functionality processed by component 199, network entity 1802 may include CU 1810; both CU 1810 and DU 1830; each of CU 1810, DU 1830, and RU 1840; DU 1830; both DU 1830 and RU 1840; or RU 1840. CU 1810 may include at least one CU processor 1812. CU processor 1812 may include on-chip memory 1812'. In some aspects, CU 1810 may also include an additional memory module 1814 and a communication interface 1818. CU 1810 communicates with DU 1830 via a mid-range link, such as an F1 interface. DU 1830 may include at least one DU processor 1832. DU processor 1832 may include on-chip memory 1832'. In some aspects, DU 1830 may also include an additional memory module 1834 and a communication interface 1838. DU 1830 communicates with RU 1840 via a front-end link. RU 1840 may include at least one RU processor 1842. RU processor 1842 may include on-chip memory 1842'. In some aspects, RU 1840 may also include an additional memory module 1844, one or more transceivers 1846, an antenna 1880, and a communication interface 1848. RU 1840 communicates with UE 104. On-chip memories 1812', 1832', 1842' and additional memory modules 1814, 1834, 1844 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1812, 1832, 1842 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor during software execution.

[0156] As described above, component 199 can be configured to configure a measurement object configuration for the UE, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. Component 199 can also be configured to provide the set of SSBs indicated in the measurement object configuration. Component 199 can be configured to obtain the UE's altitude and provide an indication of the UE's altitude to the UE. Component 199 can be configured to measure the UE's altitude based on information received from the UE. Component 199 can be configured to send an indication of the UE's altitude to the UE. Component 199 can also be configured to perform a combination. Figure 13-16 Any aspect described in the flowchart in any of the items, and / or by the network node / base station Figure 4 , 5 Or any aspect of any of 8-12 executed. Component 199 may be within one or more processors of one or more of CU 1810, DU 1830, and RU 1840. Component 199 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the process / algorithm individually or in combination. Network entity 1802 may include various components configured for various functions. In one configuration, network entity 1802 may include units for configuring a measurement object configuration for the UE, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. In this configuration, network entity 1802 may include units for providing the set of SSBs indicated in the measurement object configuration. In one configuration, network entity 1802 may include units for obtaining the altitude of the UE and providing the UE with an indication of the UE's altitude. In one configuration, network entity 1802 may include a unit for measuring the altitude of the UE based on information received from the UE. In one configuration, network entity 1802 may include a unit for transmitting an indication of the UE's altitude to the UE. In one configuration, network entity 1802 may include a unit for receiving SSB values ​​for each measured SSB in a set of SSBs for at least one physical cell at the UE's altitude, based on a reporting configuration associated with the UE's altitude and at least one of the UE's altitude, location, rate, or speed. The network entity may also include a unit for performing a combination. Figure 13-16 Any aspect described in the flowchart in any of the items, and / or by the network node / base station Figure 4 , 5A unit performing any aspect of any of the aspects described in 8-12. The unit may be a component 199 of network entity 1802 configured to perform the functions described by the unit. As described above, network entity 1802 may include at least one of TX processor 316, RX processor 370, and / or controller / processor 375. Thus, in one configuration, the unit may be a TX processor 316, RX processor 370, and / or controller / processor 375 configured to perform the functions described by the unit.

[0157] Figure 19 Figure 1900 illustrates an example of a hardware implementation for network entity 1960. In one example, network entity 1960 may be within core network 120. Network entity 1960 may include at least one network processor 1912. Network processor 1912 may include on-chip memory 1912'. In some aspects, network entity 1960 may also include an additional memory module 1914. Network entity 1960 communicates directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) with CU 1902 and / or UE 104 via network interface 1980. On-chip memory 1912' and additional memory module 1914 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Network processor 1912 is responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor during software execution.

[0158] As described above, component 199 can be configured to configure a measurement object configuration for the UE, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. Component 199 can also be configured to provide the set of SSBs indicated in the measurement object configuration. Component 199 can be configured to obtain the UE's altitude and provide an indication of the UE's altitude to the UE. Component 199 can be configured to measure the UE's altitude based on information received from the UE. Component 199 can be configured to send an indication of the UE's altitude to the UE. Component 199 can also be configured to perform a combination. Figure 13-16 Any aspect described in the flowchart of any item in the above, and / or by network nodes / base stations. Figure 4 , 5Or any aspect of any of 8-12 executed. Component 199 may be within network processor 1912. Component 199 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the process / algorithm individually or in combination. Network entity 1960 may include various components configured for various functions. In one configuration, network entity 1802 may include units for configuring a measurement object configuration for the UE, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs. In this configuration, network entity 1802 may include units for providing the set of SSBs indicated in the measurement object configuration. In one configuration, network entity 1802 may include units for obtaining the altitude of the UE and providing an indication of the altitude of the UE to the UE. In one configuration, network entity 1802 may include units for measuring the altitude of the UE based on information received from the UE. In one configuration, network entity 1802 may include a unit for transmitting an indication of the UE's altitude to the UE. In another configuration, network entity 1802 may include a unit for receiving SSB values ​​for each measured SSB in a set of SSBs for at least one physical cell at the UE's altitude, based on a reporting configuration associated with the UE's altitude and at least one of the UE's altitude, location, rate, or speed. The network entity may also include a unit for performing a combination. Figure 13-16 Any aspect described in the flowchart in any of the items, and / or by the network node / base station Figure 4 , 5 A unit that performs any aspect of any of the aspects described in 8-12. The unit may be a component 199 of network entity 1960, which is configured to perform the functions described by the unit.

[0159] Wireless communication networks can enable UE-to-beam measurements, for example, for mobility operations. In a 5G NR network, as an example, a given physical cell can have multiple beams, and therefore the UE can measure multiple SSBs. The configuration for such measurements can include a bitmap (“ssb-ToMeasure”) indicating the set of SSBs to be measured during the SMTC measurement duration. ssb-ToMeasure can be a single bitmap within an SSB-ConfigMobility object and can be applied to all measurements in a configuration for a given measObject NR measurement object (e.g., “smtc” and “smtc2”). However, multiple measObject configurations for a given SSB frequency (“ssbFrequency”) may not be enabled or allowed for cell groups. For example, some wireless networks can be implemented to ensure that in the measurement configuration (“measConfig”) associated with the configured permission (CG): (1) for all SSB-based measurements, there exists at most one measurement object with the same ssbFrequency; and / or (2) “smtc1” included in any measurement object with the same ssbFrequency has the same value, as does “smtc2” included in any measurement object with the same ssbFrequency, as does “smtc3list” included in any measurement object with the same ssbFrequency, and as does “smtc4list” included in any measurement object with the same ssbFrequency. However, for a given altitude range in which the UE exists, additional flexibility for cell-specific beam measurements beyond the flexibility provided in the current solution can improve beam measurements. The various aspects of this paper enable SMTC to have the flexibility to allow a UE (e.g., an unmanned aerial vehicle (UAV)) to measure a first set of beams (or (cell, beam) ordered pairs) at an altitude range (e.g., below or at the level of clutter) and different sets of beams (including for different cells) at different altitude ranges (e.g., above a specific altitude where line of sight (LOS) is typically expected).

[0160] The various aspects of the altitude-dependent measurement and reporting configurations described herein improve the flexibility and accuracy of location and mobility measurements at the UE via configurations for altitude-specific measurements of synchronization signals. By implementing configurations for altitude-specific measurements with altitude ranges / intervals for synchronization signals, these aspects enhance the flexibility and accuracy of location and mobility measurements at the UE based on the UE's altitude (e.g., for UAVs) for specific synchronization signals. Furthermore, by configuring altitude-dependent measurements with an SSB-MTC list in the measurement object, these aspects provide SSB-MTC sub-configurations, where each element in the SSB-MTC list flexibly allows for altitude ranges, achieving greater flexibility and accuracy for location and mobility measurements at the UE based on the UE's altitude for specific synchronization signals.

[0161] It is understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the example method. Based on design preferences, it is understood that the specific order or hierarchy of the boxes in the process / flowchart can be rearranged. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of each box in sample order, but are not limited to the specific order or hierarchy given.

[0162] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will readily be apparent to those skilled in the art, and the general principles defined herein may also be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but are to be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the time” do not imply an immediate temporal relationship or reaction. In other words, these phrases (e.g., "when...") do not imply an immediate action in response to the occurrence of an action or during the occurrence of such an action, but only that the action will occur if the condition is met, without requiring a specific or immediate time constraint for the occurrence of the action. The word "exemplary" as used herein means "as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred over or superior to other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, The combination of “B, C, or any combination thereof” can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. A set shall be interpreted as a set of elements in which one or more elements are numbered. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor may be configured to execute a specific subset of the set of functions, wherein the subset is the entire set, a proper subset of the set, or an empty subset of the set. A processor may be referred to as a processor circuit. A memory / memory module (also referred to as “at least one memory / memory module”) may be referred to as a memory circuit. If the first device receives data from or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a set of devices.Devices configured to "output" data such as transmissions, signals, or messages can, for example, use a transceiver to transmit data, or can send data to a device that transmits data. Devices configured to "receive" data such as transmissions, signals, or messages can, for example, use a transceiver to receive data, or can obtain data from a device that receives data. Information stored in memory includes instructions and / or data. Devices configured to "output" or "provide" data such as transmissions, signals, or messages can, for example, use a transceiver to transmit data, or can send data to a device that transmits data. Devices configured to "receive" data such as transmissions, signals, or messages can, for example, use a transceiver to receive data, or can obtain data from a device that receives data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of elements described throughout the various aspects of this disclosure that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended for public distribution, whether or not such disclosure is expressly recited in the claims. Terms such as “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “unit.” Thus, no claim can assert that an element should be interpreted as a functional unit unless the element is explicitly described using the phrase “unit for…”.

[0163] As used herein, the phrase “based on” should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless specifically and differently stated, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”.

[0164] The following aspects are illustrative only and may be combined with, but not limited to, other aspects or teachings described herein.

[0165] Aspect 1 is a method for wireless communication at a user equipment (UE), comprising: receiving a measurement object configuration from a network node, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs; and measuring an SSB value for each SSB in the set of SSBs based on the measurement object configuration and the altitude of the UE.

[0166] Aspect 2 is the method according to aspect 1, wherein the measurement object configuration includes a synchronization signal block (SSB) measurement time configuration (SMTC).

[0167] Aspect 3 is the method according to any one of aspects 1 and 2, wherein the at least one altitude parameter includes at least one of a minimum altitude value or a maximum altitude value.

[0168] Aspect 4 is the method according to aspect 3, wherein the UE uses a default minimum altitude value of zero when the first minimum altitude value for the altitude range does not exist; or wherein the UE uses a default maximum altitude value of infinity when the second maximum altitude value for the altitude range does not exist.

[0169] Aspect 5 is the method according to any one of aspects 1 to 4, wherein the at least one altitude parameter is associated with a hysteresis value.

[0170] Aspect 6 is the method according to any one of Aspects 1 to 5, wherein the measurement object configuration includes a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC) or SMTC Measurement Duration associated with the at least one altitude parameter, wherein the measurement object configuration includes multiple altitude ranges.

[0171] Aspect 7 is the method according to aspect 6, wherein the at least one altitude parameter is associated with a hysteresis value; or wherein each of the plurality of altitude ranges is associated with a corresponding set of at least one cell identifier and a corresponding set of SSBs.

[0172] Aspect 8 is the method according to any one of aspects 1 to 7, wherein the UE is associated with an unmanned aerial vehicle (UAV).

[0173] Aspect 9 is a method according to any one of Aspects 1 to 8, wherein the measurement object configuration includes a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC), wherein the SMTC includes an additional altitude parameter, wherein measuring the SSB value for each SSB in the SSB set includes: measuring each SSB associated with one or more cell identifiers based on the fact that there is no corresponding SSB set for the additional altitude parameter in the SMTC.

[0174] Aspect 10 is the method according to any one of aspects 1 to 9, wherein the at least one altitude parameter includes an altitude range, and wherein the altitude range is associated with an altitude list in the measurement objects in the measurement object configuration.

[0175] Aspect 11 is the method according to any one of aspects 1 to 10, wherein the measurement object configuration includes a synchronization signal block (SSB) measurement time configuration (SMTC), wherein the at least one altitude parameter includes an altitude range, wherein the altitude range is associated with an altitude list in the SMTC.

[0176] Aspect 12 is the method according to aspect 11, wherein the SMTC includes a list of cells indicating a set of cell identifiers.

[0177] Aspect 13 is a method according to any one of Aspects 1 to 12, wherein the at least one altitude parameter includes an altitude range, wherein the altitude range is associated with an SMTC list in a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC) included in the measurement object configuration, and wherein each of the one or more altitude ranges corresponds to an SMTC sub-configuration, the SMTC sub-configuration including at least one of the following: a cell list indicating a corresponding set of cell identifiers; a burst period of a corresponding set of SSBs; or the set of SSBs, wherein the set of SSBs is associated with a physical cell during the SMTC window.

[0178] Aspect 14 is a method according to any one of aspects 1 to 12, further comprising: obtaining the altitude of the UE based on at least one of the following: measuring the altitude of the UE based on information received by the UE; or receiving an indication of the altitude of the UE from the network node or network entity.

[0179] Aspect 15 is a method for wireless communication at a network node, comprising: configuring a measurement object configuration for a user equipment (UE), wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs; and providing the set of SSBs indicated in the measurement object configuration.

[0180] Aspect 16 is the method according to aspect 15, wherein the measurement object configuration includes a synchronization signal block (SSB) measurement time configuration (SMTC).

[0181] Aspect 17 is the method according to any one of aspects 15 and 16, wherein the at least one altitude parameter includes an altitude range, the altitude range including at least one of a minimum altitude value or a maximum altitude value.

[0182] Aspect 18 is a method according to any one of aspects 15 and 16, wherein the UE utilizes a default minimum altitude value of zero in the case that a first minimum altitude value for the altitude range does not exist; or wherein the UE utilizes a default maximum altitude value of infinity in the case that a second maximum altitude value for the altitude range does not exist.

[0183] Aspect 19 is the method according to any one of aspects 15 to 16, wherein the at least one altitude parameter is associated with a hysteresis value.

[0184] Aspect 20 is the method according to any one of aspects 15 to 19, wherein the measurement object configuration includes a synchronization signal block (SSB) measurement time configuration (SMTC) or SMTC measurement duration associated with the at least one altitude parameter, wherein the measurement object configuration includes multiple altitude ranges.

[0185] Aspect 21 is the method according to any one of aspects 15 to 20, wherein the at least one altitude parameter is associated with a hysteresis value; or wherein each of the plurality of altitude ranges is associated with a corresponding set of at least one cell identifier and a corresponding set of SSBs.

[0186] Aspect 22 is the method according to any one of aspects 15 to 21, wherein the UE is associated with an unmanned aerial vehicle (UAV).

[0187] Aspect 23 is the method according to any one of aspects 15 to 22, wherein the measurement object configuration includes a synchronization signal block (SSB) measurement time configuration (SMTC), wherein the SMTC includes an additional altitude parameter, wherein the additional altitude parameter does not have a corresponding SSB set in the SMTC.

[0188] Aspect 24 is the method according to any one of aspects 15 to 23, wherein the at least one altitude parameter includes an altitude range, and wherein the altitude range is associated with an altitude list in the measurement objects in the measurement object configuration.

[0189] Aspect 25 is a method according to any one of aspects 15 to 24, wherein the measurement object configuration includes a synchronization signal block (SSB) measurement time configuration (SMTC), wherein the at least one altitude parameter includes an altitude range, wherein the altitude range is associated with an altitude list in the SMTC.

[0190] Aspect 26 is the method according to aspect 25, wherein the SMTC includes a list of cells indicating a set of cell identifiers.

[0191] Aspect 27 is a method according to any one of Aspects 15 to 26, wherein the at least one altitude parameter includes an altitude range, wherein the altitude range is associated with an SMTC list in a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC) included in the measurement object configuration, and wherein each of the one or more altitude ranges corresponds to an SMTC sub-configuration, the SMTC sub-configuration including at least one of: a cell list indicating a corresponding set of cell identifiers; a burst period of a corresponding set of SSBs; or the set of SSBs, wherein the set of SSBs is associated with a physical cell during the SMTC window.

[0192] Aspect 28 is a method according to any one of aspects 15 to 27, further comprising: obtaining the altitude of the UE; wherein obtaining the altitude of the UE includes at least one of: measuring the altitude of the UE based on information received from the UE; or sending an indication of the altitude of the UE.

[0193] Aspect 29 is a method for wireless communication at a network node, comprising: receiving a measurement object configuration from the network node, wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs, wherein the at least one altitude parameter includes a hysteresis value; and measuring an SSB value for each SSB in the set of SSBs based on the measurement object configuration and the altitude of the UE.

[0194] Aspect 30 is a method for wireless communication at a network node, comprising: configuring a measurement object configuration for a user equipment (UE), wherein the measurement object configuration indicates at least one altitude parameter associated with a set of SSBs, wherein the at least one altitude parameter includes a hysteresis value; and providing the set of SSBs indicated in the measurement object configuration.

[0195] Aspect 31 is a device for wireless communication, including units for implementing any one of aspects 1 to 14.

[0196] Aspect 32 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any of aspects 1 to 14.

[0197] Aspect 33 is an apparatus for wireless communication at a network node. The apparatus includes: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured to implement any of aspects 1 to 14.

[0198] Aspect 34 is the apparatus according to aspect 33, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0199] Aspect 35 is a device for wireless communication, including units for implementing any aspect of aspects 15 to 28.

[0200] Aspect 36 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any of aspects 15 to 28.

[0201] Aspect 37 is an apparatus for wireless communication at a network node. The apparatus includes: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured to implement any of aspects 15 to 28.

[0202] Aspect 38 is the apparatus according to aspect 33, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured, at least in part, based on stored information stored in the at least one memory, to: Receive measurement object configuration from network node, wherein the measurement object configuration indicates at least one altitude parameter associated with the SSB set; as well as The SSB value for each SSB in the SSB set is measured based on the measurement object configuration and the altitude of the UE.

2. The apparatus according to claim 1, wherein, The measurement object configuration includes the Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC).

3. The apparatus according to claim 1, wherein, The at least one altitude parameter includes an altitude range, which includes at least one of a minimum altitude value or a maximum altitude value.

4. The apparatus according to claim 3, wherein, The UE utilizes a default minimum altitude value of zero if the first minimum altitude value for the altitude range does not exist. or Wherein, the UE utilizes an infinite default maximum altitude value in the case that the second maximum altitude value for the altitude range does not exist.

5. The apparatus according to claim 1, wherein, The at least one altitude parameter is associated with a hysteresis value.

6. The apparatus according to claim 1, wherein, The measurement object configuration includes a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC) or SMTC Measurement Duration associated with the at least one altitude parameter, wherein the measurement object configuration includes multiple altitude ranges.

7. The apparatus according to claim 6, wherein, The at least one altitude parameter is associated with a hysteresis value; or Each of the plurality of altitude ranges is associated with a corresponding set of at least one cell identifier and a corresponding set of SSBs.

8. The apparatus according to claim 1, wherein, The UE is associated with an unmanned aerial vehicle (UAV).

9. The apparatus according to claim 1, wherein, The measurement object configuration includes a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC), wherein the SMTC includes an additional altitude parameter, and wherein, in order to measure the SSB value for each SSB in the SSB set, the at least one processor is configured to: Each SSB associated with one or more cell identifiers is measured based on the fact that there is no corresponding set of SSBs for the additional altitude parameter in the SMTC.

10. The apparatus according to claim 1, wherein, The at least one altitude parameter includes an altitude range, and wherein the altitude range is associated with an altitude list in the measurement objects in the measurement object configuration.

11. The apparatus according to claim 1, wherein, The measurement object configuration includes a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC), wherein the at least one altitude parameter includes an altitude range, wherein the altitude range is associated with an altitude list in the SMTC.

12. The apparatus according to claim 11, wherein, The SMTC includes a list of cells that indicate a set of cell identifiers.

13. The apparatus according to claim 1, wherein, The at least one altitude parameter includes an altitude range, wherein the altitude range is associated with a list of SMTCs in a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC) included in the measurement object configuration, and wherein each of the one or more altitude ranges corresponds to an SMTC sub-configuration, the SMTC sub-configuration including at least one of the following: A list of cells used to indicate the corresponding set of cell identifiers; The burst cycle of the corresponding SSB set; or The SSB set, wherein the SSB set is associated with a physical cell during the SMTC window.

14. The apparatus according to claim 1, wherein, The at least one processor is further configured to: Obtain the altitude of the UE; In order to obtain the altitude of the UE, the at least one processor is configured to perform at least one of the following: The altitude of the UE is measured based on information received by the UE; or Receive an indication of the altitude of the UE from the network node or network entity.

15. An apparatus for wireless communication at a network node, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured, at least in part, based on stored information stored in the at least one memory, to: For user equipment (UE), a measurement object configuration is configured, the measurement object configuration indicating at least one altitude parameter associated with a set of SSBs; The set of SSBs indicated in the measurement object configuration is provided.

16. The apparatus according to claim 15, wherein, The measurement object configuration includes a Synchronization Signal Block (SSB) Measurement Time Configuration (SMTC); or Wherein, the at least one altitude parameter includes an altitude range, and the altitude range includes at least one of a minimum altitude value or a maximum altitude value; Wherein, at least one altitude parameter is associated with a hysteresis value; or The UE is associated with an unmanned aerial vehicle (UAV).

17. The apparatus according to claim 16, wherein, The UE utilizes a default minimum altitude value of zero if the first minimum altitude value for the altitude range does not exist. or Wherein, the UE utilizes an infinite default maximum altitude value in the case that the second maximum altitude value for the altitude range does not exist.

18. The apparatus according to claim 15, (i) wherein, The measurement object configuration includes a first synchronization signal block (SSB) measurement time configuration (SMTC) or SMTC measurement duration associated with the at least one altitude parameter, wherein the measurement object configuration includes multiple altitude ranges; (ii) wherein the measurement object configuration includes a second SMTC, wherein the second SMTC includes an additional altitude parameter, wherein the additional altitude parameter does not have a corresponding first SSB set in the second SMTC; (iii) wherein the at least one altitude parameter includes a first altitude range, and wherein the first altitude range is associated with a first altitude list in the measurement objects in the measurement object configuration; (iv) wherein the measurement object configuration includes a third SMTC, wherein the at least one altitude parameter includes a second altitude range, wherein the second altitude range is associated with a second altitude list in the third SMTC; (v) wherein the at least one altitude parameter includes a third altitude range, wherein the third altitude range is associated with a list of SMTCs in a fourth SMTC included in the measurement object configuration, and wherein each of the one or more altitude ranges corresponds to an SMTC sub-configuration, the SMTC sub-configuration including at least one of the following: Indicates the first list of cells in the corresponding set of cell identifiers. The corresponding burst cycle of the second SSB set, or The SSB set, wherein the SSB set is associated with a physical cell during the SMTC window; or (vi) wherein the at least one processor is further configured to: Obtain the altitude of the UE; and Provide the UE with an indication of the UE's altitude.

19. The apparatus according to claim 18, wherein, The at least one altitude parameter is associated with a hysteresis value; Each of the plurality of altitude ranges is associated with a corresponding set of at least one cell identifier and a corresponding third SSB set; or The third SMTC includes a second cell list indicating a set of cell identifiers.

20. A method for wireless communication at a user equipment (UE), comprising: Receive measurement object configuration from network node, wherein the measurement object configuration indicates at least one altitude parameter associated with the SSB set; and The SSB value for each SSB in the SSB set is measured based on the measurement object configuration and the altitude of the UE.

Images