Wireless communication method for wireless communication with air user equipment
By introducing altitude measurement and flight path reporting mechanisms into the aircraft, wireless resource management is optimized, solving the communication quality and efficiency problems of the aircraft under altitude changes and improving the wireless communication performance of the airborne UE.
Patent Information
- Application Number
- CN202280093753.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-22
- Publication Date
- 2024-11-08
AI Technical Summary
Existing wireless communication technologies struggle to effectively utilize wireless resources in aircraft, especially when considering changes in aircraft altitude and aerial characteristics, leading to a decline in communication quality and efficiency.
By introducing altitude measurement configuration and flight path reporting mechanisms, radio resource management is enhanced, UEs are configured to perform altitude measurement and flight path reporting, radio link configuration and maintenance are optimized, and the wireless communication function of in-flight UEs is improved by combining the CU/DU separation architecture and the coordination mechanism in the MR-DC scenario.
It improves the communication quality and efficiency of aircraft at different altitudes and flight paths, enhances mobility performance and interference detection capabilities, optimizes cell selection and reselection processes, and improves the overall communication performance of the system.
Smart Images

Figure CN118923156A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communications, and in particular to wireless communications associated with aircraft services. Background Art
[0002] The world is increasingly connected due to advances in wireless communication technology. Next-generation wireless communication systems can support a wider range of functions and applications compared to existing wireless networks. For example, support for higher data rates, large numbers of connections, ultra-low latency, and high reliability may be required. Efficient use of wireless communication resources is essential to support a variety of communication functions. Wireless communication based on aircraft, such as unmanned aerial vehicles (UVAs), has become a growing field for convenience and practicality in different situations. Summary of the invention
[0003] Techniques for improving wireless communication functionality of over-the-air UEs are disclosed.
[0004] According to one embodiment, the present disclosure provides a wireless communication method, including:
[0005] User equipment (UE) subscription information is sent from a first communication node to a second communication node, wherein the UE subscription information is used to indicate whether the UE is allowed to use over-the-air UE functionality.
[0006] According to another embodiment, the present disclosure provides a wireless communication method, including:
[0007] User equipment (UE) subscription information is received by a second communication node from a first communication node, wherein the UE subscription information is used to indicate whether the UE is allowed to use an over-the-air UE function.
[0008] According to another embodiment, the present disclosure provides a wireless communication method, including:
[0009] A configuration message is received by a user equipment (UE) from a wireless communication node to configure at least one of the following configurations of the UE:
[0010] UE altitude measurement configuration; or
[0011] Request for UE flight path reporting configuration; and
[0012] Reporting to the wireless communication node is triggered based on the configuration message.
[0013] According to another embodiment, the present disclosure provides a wireless communication method, including:
[0014] The wireless communication node sends a configuration message to the UE to configure at least one of the following configurations of the UE:
[0015] UE altitude measurement configuration; or
[0016] Request for UE flight path reporting configuration; and
[0017] A report is received by a wireless communication node from a UE, the report being generated according to the configuration message.
[0018] According to another embodiment, the present disclosure provides a wireless communication method, including:
[0019] A user equipment (UE) receives at least one of the following information from a wireless communication node to perform cell selection or reselection:
[0020] An indicator indicating whether the cell is not suitable for over-the-air UE access;
[0021] An indicator indicating whether the cell is not suitable for access by aerial UEs, where the altitude of aerial UEs is within a certain range;
[0022] An indicator indicating whether a frequency or a cell is not suitable for cell reselection by an aerial UE, the altitude of the aerial UE being within a certain range; or
[0023] Priority information, setting the priority for selecting between multiple neighboring cells; and
[0024] Cell selection or reselection is performed according to at least one item of the information.
[0025] According to another embodiment, the present disclosure provides a wireless communication method, including:
[0026] At least one of the following information is sent by a wireless communication node to a user equipment (UE) for cell selection or reselection:
[0027] An indicator indicating whether the cell is not suitable for over-the-air UE access;
[0028] An indicator indicating whether the cell is not suitable for access by aerial UEs, where the altitude of aerial UEs is within a certain range;
[0029] An indicator indicating whether a frequency or a cell is not suitable for cell reselection by an aerial UE, the altitude of the aerial UE being within a certain range; or
[0030] Priority information, which sets the priority for selecting between multiple neighboring cells.
[0031] According to another embodiment, the present disclosure provides a wireless communication device, including:
[0032] at least one memory storing at least one program; and
[0033] One or more processors communicate with at least one memory and are configured to execute at least one program to enable the wireless communication device to perform any method and steps disclosed in the present disclosure.
[0034] According to another embodiment, the present disclosure provides a non-transitory computer-readable storage medium storing at least one program, which, when executed by one or more processors, causes a wireless communication device to perform any method and steps disclosed in the present disclosure.
[0035] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 An example wireless communication network is shown;
[0037] Figure 2 A flowchart of a wireless communication method in the wireless communication method of the present disclosure is shown;
[0038] Figure 3 Another flow chart of the wireless communication method in the wireless communication method of the present disclosure is shown;
[0039] Figure 4 Another flowchart of the wireless communication method in the wireless communication method of the present disclosure is shown; and
[0040] Figure 5 An example wireless communication device is shown that can implement any of the wireless communication methods in the present disclosure. DETAILED DESCRIPTION
[0041] Wireless communications of an aircraft or a wireless device in an aircraft with a wireless access network, such as in a cellular network, may involve several aerial characteristics that are not present for ground-based wireless devices. Therefore, configuration and maintenance of wireless links may be handled in a special manner based on parameters related to aerial characteristics. For example, the altitude of an aircraft or a wireless device in an aircraft may vary significantly during various phases of communications and may need to be accounted for in wireless link configuration to maintain or improve communication quality and efficiency. These parameters may be reported to the access network in various ways so that they may be taken into account in network configuration and maintenance.
[0042] In some embodiments, the altitude of an aircraft or a wireless device in an aircraft (collectively referred to as a "user equipment (UE)") may be monitored. For example, one or more altitude / altitude reporting events for the user equipment (UE) may be introduced, such as two events referred to as H1 and H2. With these two new events, the UE triggers an altitude report, for example, when the altitude of the UE is above (i.e., event H1) or below (i.e., event H2) a network configured threshold. Further, in an enhanced embodiment, the RRM (Radio Resource Management) measurement framework may be extended so that the UE may be configured to trigger a measurement report when an event condition of a configurable number of cells is met. For example, events applicable to this enhancement may include: event A3 (defined as an offset where a neighbor becomes better than a PCell / PSCell), A4 (defined as a neighbor becomes better than an absolute threshold), and A5 (defined as a PCell / PSCell becomes worse than an absolute threshold 1, and a neighbor / SCell becomes better than another absolute threshold 2). These enhancements help the eNB (enhanced Node B) determine that the UE is flying and / or allow detection that the UE may be causing or experiencing interference.
[0043] To improve mobility performance, RRC (Radio Resource Control) signaling techniques may be added to allow the UE to indicate a planned flight path to the base station. More specifically, the UE may indicate where the UE has a planned flight path, which the base station may consider for mobility purposes. For example, the base station may be able to use this information to know in advance which cell is suitable for the UE to hand over to, and whether it is beneficial to establish a new connection.
[0044] In some embodiments, the over-the-air service may be subscribable, and in order for the network to know whether the UE has a suitable subscription, signaling from the core network to the base station may be introduced, which carries information about whether the subscription supports over-the-air UE functionality.
[0045] CU / DU (centralized unit / distributed unit) separation architecture
[0046] Depending on the network functions associated with the various layers in the wireless network protocol stack, the base station can be implemented in a split architecture. As an example, Figure 1The diagram illustrates an overall architecture with a Central Unit / Distributed Unit (CU / DU) separation. A gNB (3GPP 5G Next Generation Base Station supporting 5G New Radio) can consist of a gNB Centralized Unit (gNB-CU) and one or more gNB Distributed Units (gNB-DU). The gNB-CU and gNB-DU are connected via the F1 interface. The gNB-CU is defined as a logical node that hosts the RRC, SDAP (Service Data Adaptation Protocol), and PDCP (Packet Data Convergence Protocol) protocols of a gNB or the RRC and PDCP protocols of an en-gNB (denoting a gNB capable of connecting to an EPC and ng-eNB), and it controls the operation of one or more gNB-DUs. The gNB-DU is defined as a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. As an example, one cell is supported by only one gNB-DU.
[0047] 1. Enhanced measurement reporting
[0048] According to one embodiment of the present disclosure, a wireless communication method is disclosed. Figure 2 The methods shown include:
[0049] A configuration message is received by a user equipment (UE) from a wireless communication node to configure at least one of the following configurations of the UE:
[0050] UE altitude measurement configuration; or
[0051] Request for UE flight path reporting configuration; and
[0052] Reporting to the wireless communication node is triggered based on the configuration message.
[0053] Accordingly, a wireless communication method that can be performed by a base station or a core network is disclosed. The method includes:
[0054] The wireless communication node sends a configuration message to the UE to configure at least one of the following configurations of the UE:
[0055] UE altitude measurement configuration; or
[0056] Request for UE flight path reporting configuration; and
[0057] A UE altitude measurement report is received by a wireless communication node from a UE, the report being generated according to a configuration message.
[0058] According to one embodiment, the UE height measurement configuration is associated with at least one of the following items: cell ID information, reference signal identification (RS ID), or transmission reception point (TRP) information.
[0059] According to one embodiment, the UE height measurement configuration includes at least one of the following parameters:
[0060] Reference altitude threshold;
[0061] offset of the reference altitude threshold;
[0062] The hysteresis parameters used within the entry and exit conditions of event-triggered reporting conditions;
[0063] A trigger time parameter indicating a timer that needs to meet specific criteria of an event to trigger a measurement report;
[0064] Indicator indicating whether the UE is allowed to initiate UE altitude measurement when the leaving condition is met;
[0065] The interval or period at which the UE periodically reports UE altitude measurements; or
[0066] Maximum number of UE altitude measurement reports available to the UE.
[0067] In order to implement over-the-air UE applications in 5G scenarios, the following improvements can be made to enhance functionality.
[0068] 1.1 Measurement reporting based on configured altitude thresholds
[0069] According to one embodiment, in response to the UE's altitude satisfying an altitude threshold configuration configured by the wireless communication node, the UE may send a UE altitude measurement report to the wireless communication node.
[0070] Two reporting events can be introduced:
[0071] Event H1: the UE altitude in the air is higher than the threshold H1; and / or
[0072] Event H2: The height of the UE in the air is lower than the threshold H2.
[0073] That is, when the UE detects that its altitude is higher (i.e., event H1) or lower (i.e., event H2) than one or more altitude thresholds, the UE may trigger a UE altitude report to the NW (network) to report the UE's altitude report. The thresholds for event H1 and event H2 may be the same or different. The altitude report may be used to help the NW identify the flight status of the airborne UE. The NW may then perform certain operations (multiple) on scheduling or radio resource management (RRM), such as adjusting the UE's serving beam, or configuring some airborne UE-specific measurements of the UE.
[0074] 1.1.1 Altitude measurement configuration
[0075] According to one embodiment, the UE height measurement configuration includes at least one of the following items:
[0076] When a condition based on the reference altitude threshold is met, the UE triggers the reference altitude threshold for altitude measurement; or
[0077] A reference height threshold list, each reference height threshold being associated with at least one of the following items: cell ID information, reference signal identification (RS ID) or transmission reception point (TRP) information.
[0078] According to one embodiment, the UE height measurement configuration includes at least one of the following parameters:
[0079] Reference altitude threshold;
[0080] offset of the reference altitude threshold;
[0081] The hysteresis parameters used within the entry and exit conditions of event-triggered reporting conditions;
[0082] A trigger time parameter indicating the specific criteria of an event that needs to be met to trigger a timer for a measurement report;
[0083] Indicator indicating whether the UE is allowed to initiate UE altitude measurement when the leaving condition is met;
[0084] The interval or period at which the UE periodically reports UE altitude measurements; or
[0085] Maximum number of UE altitude measurement reports available to the UE.
[0086] According to one embodiment, the UE height measurement configuration is indicated by at least one of the following items: RRM / L3 (layer three) measurement configuration, measurement object information, measurement report configuration, L1 (layer one) measurement configuration, or RS or beam measurement configuration.
[0087] The RRC reconfiguration message or the RRC recovery message may include measurement configuration. When the UE is connected to a base station (BS), the network may update the measurement configuration to the UE. The configured measurement may include, for example, a measurement object, a report configuration, and a measurement identifier (MeasID).
[0088] In one example, the altitude measurement configuration (i.e., altitude reporting related parameters) may be set according to one of the following ways:
[0089] Example 1
[0090] The parameters of the height measurement configuration can be set independently between different UEs. That is, the network can customize the height measurement configuration for different UEs. Therefore, the following two options can be used to implement this method.
[0091] Option 1-1: The altitude measurement configuration including altitude reporting related parameters may be included directly in a measurement configuration, such as MeasConfig.
[0092] Option 1-2: Alternatively, the altitude measurement configuration including altitude reporting related parameters may be configured in the report configuration (eg, included in the reportType parameter within the ReportConfigNR parameter) and associated with a measurement object (eg, MeasObjectNR) of the serving cell (eg, SpCell).
[0093] Example 2
[0094] The parameters of the height measurement configuration can be set independently between different cells of the UE. That is, the network can customize the height measurement configuration for different cells. Therefore, the following two options can be used to implement this method.
[0095] Option 2-1: A list of height report related parameters may be configured in the measurement configuration (eg, in the MeasConfig or ReportConfig parameter in the RRC message), each height report related parameter being associated with the cell ID information (eg, PCI+frequency).
[0096] In this example, the configuration is associated with the corresponding cell ID information, so the configuration is cell-specific. Different measurement configurations can be implemented in different cells.
[0097] Option 2-2: Alternatively, high-level reporting related parameters may be configured in the reporting configuration (eg, included in the reportType parameter within the ReportConfigNR parameter) and associated to the measurement object of each serving cell (eg, including SpCell and SCell).
[0098] Option 2-3: Alternatively, the altitude reporting related parameters may be configured in the measurement object configuration (eg, MeasObjectNR or MeasObjectEUTRA in the RRC message). In this embodiment, the cell-specific altitude reporting related parameters are defined by the MeasObjectNR or MeasObjectEUTRA parameters in the RRC message.
[0099] Example 3:
[0100] In this example, the (multiple) parameters of the height measurement configuration can be set independently between the reference signaling (RS) or the beams of the serving cell. That is, the network can customize the height measurement configuration for different reference signaling or beams. Therefore, the following two options can be used to implement this method.
[0101] Option 3-1: A list of highly reported related parameters may be configured in an RRC message (e.g., in a MeasConfig or ReportConfig parameter). Each measurement configuration may be associated with an RS ID (e.g., an SSB index or a CSI-RS index) of a serving cell, so that RS / RS beam-specific measurement configurations may be implemented by identifying the corresponding RS using the RS ID associated with the configuration.
[0102] Option 3-2: Alternatively, the altitude reporting related parameters (e.g., SSB-ConfigMobility, CSI-RS-ResourceConfigMobility, or CSI-MeasConfig) may be configured in the RS / beam measurement configuration.
[0103] Example 4:
[0104] In this example, the (multiple) parameters of the altitude measurement configuration can be set independently between the transmission and reception points (TRPs) of the serving cell. That is, the network can customize the altitude measurement configuration for different transmission and reception points. For example, a list of altitude report-related parameters can be configured in, for example, a MeasConfig or ReportConfig information element. Each measurement configuration can be associated with TRP-related information (e.g., TCI-StateId or coresetPoolIndex) of the serving cell.
[0105] The above example implementations may be combined or used together. For example, for some serving cells, the height measurement value may be configured on an RS by RS, beam by beam, or TRP by TRP basis, while for other serving cells, the height measurement value may be configured on a cell by cell basis.
[0106] In an implementation, if multiple height measurement configurations (e.g., multiple reference height thresholds) are set for the UE, the configurations may be associated with the same measurement ID (MeasId). That is, one MeasId is associated with all height measurement configurations. Alternatively, multiple height measurement configurations may be associated with different measurement IDs. That is, one height measurement configuration is associated with one MeasId.
[0107] In the present disclosure, the altitude report related parameters that may be included in the measurement configuration may include at least one of the following items:
[0108] a reference altitude threshold (e.g., heightThreshRef), which is a value indicating the altitude (in meters) relative to sea level and is used as a threshold for triggering altitude measurement or reporting events;
[0109] Reference height threshold offset (e.g. h1-ThresholdOffset or h2-ThresholdOffset);
[0110] Hysteresis to threshold, which is a parameter used within the entry and exit conditions of event-triggered reporting conditions;
[0111] TimeToTrigger, which is the time at which the specific criteria for the event need to be met in order to trigger the measurement report;
[0112] Indicator indicating whether the UE should initiate a measurement reporting procedure (e.g. metreportOnLeave) when the leave condition is met;
[0113] When the UE periodically reports or measures altitude, the interval between two altitude reports or measurements (e.g. reportsreportInterval);
[0114] The number of measurement reports that the UE can trigger (e.g. reportAmount); or
[0115] The type of height reported (e.g. eventTriggered).
[0116] For each event (ie, H1 or H2), the value of each (multiple) altitude report related parameter may be set to be the same or different. For example, for events H1 and H2, the value of the reference altitude threshold is set to be the same.
[0117] 1.1.2 Triggering of Altitude Measurement Report
[0118] The following exemplarily defines conditions that trigger the UE to measure its altitude and / or report its altitude to the BS.
[0119] According to one embodiment of the present disclosure, in response to the UE's altitude satisfying an altitude threshold configuration configured by a wireless communication node (such as a base station), the UE may send a UE altitude measurement report to the wireless communication node.
[0120] According to one embodiment of the present disclosure, when the height of the UE meets the height threshold configuration configured by the wireless communication node based on the report interval configuration and the report quantity configuration in the UE height measurement configuration, the UE may periodically send additional UE height measurement reports to the wireless communication node. Figure 3 as described.
[0121] According to one embodiment of the present disclosure, the UE height measurement report may include at least one of the following items:
[0122] The height of the UE;
[0123] an indication that the altitude of the UE satisfies an altitude threshold configuration; or
[0124] An indication of the identity of a cell, RS / beam or TRP that meets the associated height threshold configured by the height threshold configuration.
[0125] In a first alternative, when the UE detects that the UE's altitude is above or below the reference altitude threshold(s) configured by the NW (ie, the condition of the event is satisfied), the UE is triggered to send an altitude measurement report to the NW (network).
[0126] In one embodiment, if multiple reference height thresholds are configured, the UE may trigger multiple height measurement reports to the NW when multiple events satisfying different height thresholds are met. That is, when any one of the reference height thresholds is detected to be satisfied, the UE may trigger a height measurement report.
[0127] Alternatively and additionally, when the UE detects that the UE's altitude meets one or more NW-configured reference altitude thresholds (i.e., when the conditions of an event are met), the UE can trigger an altitude report to the NW, and then periodically trigger altitude reports based on the reporting interval (e.g., reportInterval) and reporting amount (e.g., reportAmount) configured by the NW. The reporting interval determines the period or interval between two report transmissions. The reporting amount determines the total amount of reports to be sent. Additionally, if the UE is configured by the NW, the UE can also trigger additional altitude reports when the leaving conditions of the event are met.
[0128] In the present disclosure, the altitude measurement report / information may include one or more of the following:
[0129] (1) UE height;
[0130] (2) A timestamp associated with the UE's altitude;
[0131] (3) an indication that a reference altitude threshold is met to trigger the reporting process, i.e., the UE's altitude is above or below the reference altitude threshold; and / or
[0132] (4) An indication of a list of cell / RS / beam / TRP information that satisfies the associated reference height threshold to trigger the reporting process. That is, when the UE's altitude is above or below the corresponding reference height threshold of a certain cell / RS / beam / TRP, the identity of the cell / RS / beam / TRP may be included in the report.
[0133] Additionally, the height report may be sent via an RRC message (eg, a MeasurementReport message), a MAC CE, or / and L1 (layer one) signaling (eg, a CSI report).
[0134] 1.2 Flight Path Report
[0135] In addition to the altitude measurement report, the UE may also indicate whether the flight path information is available during the RRC setup / recovery / reconfiguration / reestablishment process. For example, the UE may include an indication (e.g., flightPathInfoAvailable) in the RRC setup / recovery / reconfiguration / reestablishment complete message. Thus, when the NW receives and processes the message with the indication, the NW may understand whether the flight path information is available.
[0136] Additionally, the NW may request the UE to report flight path information. For example, the NW may include a request indicator (e.g., flightPathInfoReq) in an RRC message (e.g., UEInformationRequest message). The request indicator may also include the maximum number of flight waypoints that the UE may include in the flight path information report, and whether the timestamp of each waypoint may be reported in the flight path information report (if available).
[0137] According to one embodiment, the request for flight path report configuration includes at least one of the following:
[0138] The maximum number of waypoints that a UE may include in a flight path report; or
[0139] Indicator to indicate whether timestamps for waypoints are required.
[0140] If requested by the NW, in response, the UE may report flight path information (eg, flightPathInfoReport) via an RRC message (eg, a UEInformationResponse message).
[0141] In the present disclosure, the flight path report / information may include at least one of the following:
[0142] A list of location information of waypoints along the planned flight path of the UE. Additionally, the location information may further include the speed and / or altitude information of the UE; and / or
[0143] Timestamp for each waypoint.
[0144] In response to the addition or change of the primary SCG cell (PSCell), the UE may indicate whether flight path information is available for the secondary node (SN). For example, the UE may include an indication (e.g., flightPathInfoAvailable) within an RRC reconfiguration complete message to the SN to indicate whether the flight path information is available. Thus, the PSCell / SN to which the UE is connected may understand whether the UE may have flight path information available to the SN.
[0145] In some embodiments, the SN may directly request a flight path report from the UE. Thus, the SN may send request information to the UE via an RRC message via SRB3. For example, the SN may send a request indicator (e.g., flightPathInfoReq in a UEInformationRequest message) to the UE via SRB3 to request a flight path report from the UE. Additionally, the UE may report flight path information to the SN via SRB3 (e.g., flightPathInfoReport, RRC message in a UEInformationResponse message).
[0146] 1.3 Measurements for interference detection
[0147] For interference detection, the airborne UE may be configured with RRM events A3, A4 or A5, which trigger a measurement report when the individual (per cell) RSRP (reference signal received power) values of a configured number of cells meet the configured event. For example, the configuration may be set by numberOfTriggeringCells in ReportConfigNR within an RRC message.
[0148] Considering the beam characteristics in NR, the interference detection requirements may be different from LTE. For example, one or two beams with strong RSRP can be considered as interference from the corresponding cell. Therefore, some enhancements can be considered to detect neighbor interference more effectively.
[0149] The number of triggering cells (e.g., numberOfTriggeringCells) can be configured in any event A (e.g., A1 to A6) or event B (e.g., B1, B2). The detailed description of event A / B is as follows:
[0150] Event A1: Service becomes better than the absolute threshold;
[0151] Event A2: Service becomes worse than the absolute threshold;
[0152] Event A3: Neighbor becomes better offset than PCell / PSCell;
[0153] Event A4: The neighbor becomes better than the absolute threshold;
[0154] Event A5: PCell / PSCell becomes worse than an absolute threshold 1, and the neighbor / SCell becomes better than another absolute threshold 2;
[0155] Event A6: Neighbor becomes better than SCell by offset;
[0156] Event B1: The neighbor becomes better than an absolute threshold; and
[0157] Event B2: PCell becomes worse than an absolute threshold 1, and the neighbor becomes better than another absolute threshold 2.
[0158] 1.3.1 Measurement Object (MO) Configuration
[0159] According to one embodiment of the present disclosure, a base station or a core network may provide a configuration message including at least one of the following items: a measurement object (MO) configuration or a report configuration for interference detection.
[0160] According to one embodiment of the present disclosure, the MO configuration includes a reference MO ID associated with a reference MO configuration, wherein the MO configuration and the reference MO configuration are associated with the same synchronization signal block (SSB) or channel state information reference signal (CSI-RS) frequency.
[0161] According to one embodiment of the present disclosure, the MO configuration includes at least one of the following items:
[0162] Multiple parameters for interference detection and RRM measurements respectively; or
[0163] Indicator indicating whether the UE is instructed to perform interference detection or whether the configuration object is applicable to interference detection.
[0164] According to one embodiment of the present disclosure, the plurality of parameters include at least one of the following items:
[0165] a threshold for combining measurements from a layer one (L1) filter for one or more synchronization signal (SS) / physical broadcast channel (PBCH) blocks;
[0166] a threshold for combining measurements from the L1 filter for one or more channel state information reference signal (CSI-RS) resource blocks;
[0167] Maximum number of averages of beam measurements based on one or more SS / PBCH blocks;
[0168] The maximum number of averages of beam measurements based on one or more CSI-RS resources; or
[0169] List of cells used for interference detection.
[0170] According to one embodiment of the present disclosure, the report configuration includes at least one of the following items:
[0171] Multiple parameters for interference detection and RRM measurements respectively; or
[0172] Indicator indicating whether the UE is instructed to perform interference detection or whether the reporting configuration is applicable to interference detection.
[0173] According to one embodiment of the present disclosure, the UE may derive cell quality of one or more neighboring cells based on multiple parameters for interference detection, wherein the cell quality is used to determine whether a measurement report is triggered for interference detection.
[0174] For MO configuration, consider at least one of the following alternatives:
[0175] Example 1
[0176] The NW may configure one or more separate MOs for interference detection. Thus, the NW may configure multiple MOs for the same frequency (e.g., SSB frequency, CSI-RS frequency). For example, the NW may configure two MOs associated with the same SSB / CSI-RS frequency, one for normal RRM measurements and the other for interference detection. The MO for normal RRM measurements may be associated with a reporting configuration that does not include the number of triggering cells. The MO for interference detection may be associated with a reporting configuration that includes the number of triggering cells.
[0177] Similarly, the NW may also include a reference MO ID (identifier) (e.g., ReferenceMeasObjectId) in the MO configuration. The reference MO ID may be used to identify the reference MO configuration. The reference MO configuration may be a baseline or template for the incremental configuration. The UE may adapt the incremental configuration (e.g., some parameter values different from the reference MO configuration) based on the reference configuration to generate different sets of MO configurations for interference detection. The MO configuration (i.e., including the reference MO ID) and the reference MO configuration may be associated with the same synchronization signal block (SSB) or channel state information reference signal (CSI-RS) frequency.
[0178] Example 2
[0179] Alternatively, the NW may configure the same MO for interference detection and normal RRM measurements. That is, in addition to the parameters for normal RRM measurements, the NW may configure additional and / or separate parameter sets in the same MO configuration for interference detection. The NW may also include an indicator (e.g., forInterferenceDetection) in the MO to indicate whether the MO is also applicable to interference detection, or whether to instruct the UE to perform interference detection. The indicator may be configured to indicate that the UE uses at least one of multiple parameters / parameter sets for interference detection. For example, if the value of the indicator is set to true, the UE should use the value in the additional / separate parameter set for interference detection. The UE can derive the cell quality (e.g., RSRP, RSRQ, SINR) of one or more neighboring cells based on multiple parameters / parameter sets for interference detection. The quality of the neighboring cell can be used to determine whether a measurement report (e.g., for interference detection) should be triggered, that is, whether the conditions of the event are met.
[0180] Additional and / or separate parameter sets may include at least one of the following:
[0181] (1) The (absolute) threshold for merging the measurement results in each (multiple) SS (synchronization signal) / PBCH block from (multiple) L1 (layer one) filters (e.g., absThreshSS-BlocksConsolidation2). This field is used to derive the cell measurement results. If the threshold is met, the UE merges the measurement results into the corresponding (multiple) SS / PBCH blocks;
[0182] (2) The (absolute) threshold for merging the measurement results of each (multiple) CSI-RS resource from (multiple) L1 filters (e.g., absThreshCSI-RS-Consolidation2). This field is used for deriving cell measurement results. If the threshold is met, the UE merges the measurement results into the corresponding (multiple) CSI-RS resource;
[0183] (3) The maximum number of measurements per beam based on SS / PBCH blocks to be averaged (e.g., nrofSS-BlocksToAverage2);
[0184] (4) The maximum number of measurements per beam based on the CSI-RS resources to be averaged (nrofCSI-RS-ResourcesToAverage2);
[0185] (5) An offset value applicable to all measurement cells with (multiple) reference signals indicated in the MO (e.g., offsetMO2);
[0186] (6) Cell list for interference detection, such as cellsForInterferenceDetectionToRemoveList, cellsForInterferenceDetectionToAddModList, cellsToRemoveList2, cellsToAddModList2, blackCellsToRemoveList2, blackCellsToAddModList2, whiteCellsToRemoveList2, whiteCellsToAddModList2;
[0187] (7) An offset value for combining the measurement results of each (multiple) SS / PBCH block from (multiple) L1 filters, such as absThreshSS-BlocksConsolidationOffset. This field is an offset value based on the threshold for normal RRM (i.e., absThreshSS-BlocksConsolidation) and is used to derive the absolute threshold for interference detection. For example, the threshold for interference detection can be equal to the threshold for RRM plus an offset; or
[0188] (8) An offset value for combining the measurement results of each (multiple) CSI-RS resource from (multiple) L1 filters, such as absThreshCSI-RS-ConsolidationOffset. This field is an offset value based on the threshold for normal RRM (i.e., absThreshCSI-RS-Consolidation) and is used to derive the absolute threshold for interference detection. For example, the threshold for interference detection can be equal to the threshold for RRM plus an offset.
[0189] These fields are used for interference detection by over-the-air UEs. The field values may be different from those used for normal RRM measurements.
[0190] 1.3.2 Report Configuration for Inference Detection
[0191] The NW may also introduce additional and / or separate parameter sets within a report configuration for interference detection (e.g., ReportConfigNR), and may also include an indicator (e.g., forInterferenceDetection) to indicate whether the report configuration is also applicable to interference detection, or whether to instruct the UE to perform interference detection. The indicator is configured to indicate that the UE uses at least one of multiple parameters / parameter sets for interference detection. For example, if the value of the indicator is set to true, the UE should use the value in the additional / separate parameter set for interference detection. The UE should determine whether a measurement report should be triggered, i.e., whether the conditions of the event are met, based on multiple parameters / parameter sets for interference detection. The measurement report may include interference measurement results, such as cell quality of neighboring cells (e.g., RSRP, RSRQ, SINR).
[0192] Additional and / or separate parameter sets for interference detection may include at least one of the following:
[0193] (1) A threshold value (e.g., a4-ThresholdForInterferenceDetection) associated with the selected trigger quantity (e.g., RSRP, RSRQ, SINR) for each RS type (e.g., SS / PBCH block, CSI-RS), which will be used as the measurement report trigger condition for event number aN / bN;
[0194] (2) One or more offset values used in the measurement report triggering condition of event aN (e.g., a3-OffsetForInterferenceDetection);
[0195] (3) the hysteresis (e.g., hysteresis2) value for interference detection, which is a parameter used within the entry and exit conditions of the reporting conditions for event triggering;
[0196] (4) a TimeToTrigger value for interference detection (e.g., timeToTrigger2), which is the time at which the specific criteria for the event need to be met to trigger a measurement report; or
[0197] (5) An offset value based on a threshold value (e.g., a4-Threshold) or an offset value (a3-Offset) of a measurement report trigger condition for event number aN / bN to be used for RRM, which is used to derive a threshold value and / or offset for interference detection; for example, the threshold value / offset for interference detection may be equal to the threshold value / bias for RRM plus an offset.
[0198] These fields are used for interference detection by over-the-air UEs. The field values may be different from those used for normal RRM measurements.
[0199] 2. Enhanced failure reporting
[0200] According to one embodiment of the present disclosure, a wireless communication method further includes: when an MCG or SCG failure is detected, sending a failure report to a wireless communication node, the failure report including at least one of the following information: UE location, altitude, speed or flight path information.
[0201] Accordingly, the wireless communication method that can be performed by the base station also includes receiving a failure report from the UE when the UE detects that the MCG or SCG fails, and the failure report includes at least one of the following information: the UE's location, altitude, speed or flight path information.
[0202] According to one embodiment of the present disclosure, MCG or SCG failure includes at least one of the following items: radio link failure, handover failure, PSCell addition failure, or PSCell change failure.
[0203] When the UE detects an MCG / SCG failure, such as RLF (Radio Link Failure), reconfiguration with synchronization failure (such as handover failure, PSCell addition failure or PSCell change failure), if the UE's position, altitude, speed or / and flight path information is available, the UE may include such information in a failure report, such as RLF report, RA report, MCG failure information message, SCG failure information message. The failure report may also include a timestamp for each position, altitude, speed or / and flight path information of the UE.
[0204] The detailed altitude information and flight path information may be implemented according to the disclosure in Section 1.1 Measurement report based on configured altitude threshold and Section 1.2 Flight path report of this disclosure.
[0205] 3. Enhancement of cell selection / reselection
[0206] According to one embodiment of the present disclosure, a wireless communication method is provided. Figure 4 As shown, the method includes:
[0207] At least one of the following information is received by a user equipment (UE) from a wireless communication node (such as a network) for cell selection or reselection:
[0208] (1) An indicator indicating whether the cell is not suitable for over-the-air UE access;
[0209] (2) an indicator indicating whether the cell is not suitable for access by aerial UEs, where the altitude of aerial UEs is within a certain range;
[0210] (3) an indicator indicating whether the frequency or cell is not suitable for cell reselection by an aerial UE, and the altitude of the aerial UE is within a certain range; or
[0211] (4) priority information, setting the priority for selecting between multiple neighboring cells; and
[0212] (5) Perform cell selection or reselection according to at least one item of the information.
[0213] Accordingly, a method that can be performed by a core network or a base station is disclosed. The method includes:
[0214] At least one of the following information is sent by the wireless communication node to perform cell selection or reselection:
[0215] (1) An indicator indicating whether the cell is not suitable for airborne UEs;
[0216] (2) An indicator indicating whether the cell is not suitable for airborne UEs, with a certain altitude range;
[0217] (3) an indicator indicating whether a frequency or cell is not suitable for airborne UEs, with altitudes within a certain range; or
[0218] (4) Priority information, which sets the priority for selecting between multiple neighboring cells.
[0219] According to one embodiment, the priority information includes: a first priority set and a second priority set corresponding to airborne UEs at different altitudes, and condition information indicating conditions for applying the first priority set and the second priority set.
[0220] For cell selection and reselection, aerial UEs may require special handling due to their mobility and other characteristics different from regular UEs. Enhancing the selection of cells to which aerial UEs can connect can help improve the functionality of aerial UEs.
[0221] For example, some cells may not be suitable for the aerial UE to reside (e.g., when the UE's altitude is above a defined altitude threshold). The NW may broadcast or send aerial UE related information for cell selection and / or reselection in a system information (SI) message or dedicated RRC signaling (e.g., an RRC reconfiguration message or an RRC release message).
[0222] For example, the over-the-air UE-related information used for cell selection / reselection may include at least one of the following items:
[0223] (1) An indicator for indicating whether the cell is not allowed to connect to the airborne UE. For example, the NW may include the cellBarredforUAV parameter in an SI message (e.g., MIB, SIB1, etc.);
[0224] (2) An indicator for indicating whether a cell with a height / altitude higher than and / or lower than a height threshold configured by the NW is not allowed to be connected to the UE. For example, the NW may include the cell-related height threshold in an SI message (e.g., MIB, SIB1, etc.);
[0225] (3) a list of height threshold information for cell reselection, each height threshold information being associated with frequency or cell information (e.g., frequency+PCI), indicating that when the height / altitude of the UE is higher / lower than the corresponding NW configured height threshold, the frequency / cell is not allowed to be used;
[0226] (4) A separate cell reselection priority indication (e.g., cellReselectionPriority2) is used to indicate the cell reselection priority of the UE in the air;
[0227] (5) An indicator indicating the cell reselection priority when the UE's height / altitude is higher or lower than the height threshold configured by the NW. For example, the NW may include a cell-related height threshold and / or a cell reselection priority indication (e.g., cellReselectionPriority2) to indicate the cell reselection priority (for connecting to another primary cell or secondary cell) when the UE's height / altitude is higher or lower than the height threshold. This information may be included in an SI message (e.g., SIB 2 / 3 / 4 / 5, etc.) or a dedicated RRC message. For example, when the UE's height is higher than the height threshold configured by the NW, the UE should use the cell priority indicated in the cell reselection priority indication (e.g., cellReselectionPriority2) for cell reselection. Otherwise, the UE should use the traditional cell priority indication (e.g., cellReselectionPriority) for cell reselection;
[0228] (6) a list of cell reselection priority information, each of which is associated with a height threshold configured by the NW, indicating that the cell reselection priority can be used when the height / altitude of the UE is higher / lower than the corresponding height threshold; or
[0229] (7) Derive a separate / additional parameter set for cell quality used for cell selection / reselection of UEs over the air.
[0230] A separate / additional parameter set for deriving cell quality for cell selection / reselection of an over-the-air UE may include at least one of the following:
[0231] The number of SS blocks to be averaged for cell measurement derivation, e.g., nrofSS-BlocksToAverageforUAV; or
[0232] Threshold for merging L1 measurements for each RS (e.g., SSB) index, e.g., absThreshSS-BlocksConsolidationforUAV.
[0233] The above indication and information (1) to (7) may be included in an SI message (eg, SIB 2 / 3 / 4 / 5, etc.) or a dedicated RRC message (eg, an RRC reconfiguration message or an RRC release message).
[0234] 4. Enhanced mobility
[0235] During the handover process, the UE may switch its connection from the source MN to the target MN. In order to operate with the UE over the air, some information may be transferred from the source MN to the target MN.
[0236] For handover (e.g., also including conditional handover (CHO), dual-activation protocol stack (DAPS) handover), the source MN can transmit the altitude information, flight path information, and / or interference measurement results received from the UE to the target MN via an Xn / X2 message (e.g., a handover request message) during handover preparation.
[0237] For the addition or change of SN / PSCell cells (including conditional PSCell cell addition / change (CPAC)), the MN or source SN can transmit the received altitude information, flight path information and / or interference measurement results to the target SN via Xn / X2 messages (e.g., SN add request messages) during the SN addition procedure.
[0238] When the system Figure 1 When the illustrated architecture is implemented with separated CUs and DUs (e.g., intra-CU and inter-DU mobility), the CU or source DU may transmit received altitude information, flight path information, and / or interference measurement results to a target DU via an F1 message (e.g., a UE context setup request message).
[0239] Example implementations of altitude information, flight path information, and / or interference measurement results are described in Section 1.1 Measurement Reporting Based on Configured Altitude Threshold, Section 1.2 Flight Path Reporting, and Section 1.3 Measurements for Interference Detection of this disclosure.
[0240] Exemplarily, the above information may be transmitted in at least one of the following ways:
[0241] This information may be included as an Information Element (IE) in an Xn / X2 message or an F1 message; or
[0242] Alternatively, the information may be included in an RRC message (eg, HandoverPreparationInformation), and the RRC message is included as an IE in an Xn / X2 message or an F1 message.
[0243] For conditional mobility (e.g., CHO, CPAC), the NW may configure one or more candidate cell configurations and corresponding one or more execution conditions to the UE. The UE may start evaluating one or more execution conditions upon receiving the conditional reconfiguration, and perform mobility when at least one execution condition is met.
[0244] For an aerial UE, one or more execution conditions may be configured as follows:
[0245] Example 1: Event H1 / H2, under which the UE triggers the conditional mobility procedure when the UE altitude is above or below a threshold (such as H1 or H2, respectively).
[0246] Example 2: Combination of events H1 / H2 and events / CondEvent A3 / A5 / A4 / B1. The execution condition of conditional mobility can be a combination of event H1 and events A / B. Event H and events A / B can be combined ("and") or non-combined ("or"). For example, conditional mobility is triggered when both event H1 and event A3 are met. That is, the UE height is higher than the threshold, and the candidate cell quality (RSRP / RSRQ / SINR) becomes better than the SpCell offset. Different events can be combined in a non-combined format by "or". For example, conditional mobility is triggered when at least one of event H1 or event A3 is met.
[0247] In one embodiment, one or more execution conditions may include a list of measID(s) associated with event H and events A / B above.
[0248] 5. Interaction / coordination between MN (primary node) and SN (secondary node)
[0249] When a secondary network node is added to the communication system, or when there is any change related to the SN, the MN can share different kinds of information related to the over-the-air UE to improve the functionality of the communication system.
[0250] According to one embodiment, the present disclosure provides a wireless communication method, including:
[0251] User equipment (UE) subscription information is sent from a first communication node (such as a MN or CU or a target MN) to a second communication node (such as a SN or DU or a source MN), wherein the UE subscription information is used to indicate whether the UE is allowed to use an over-the-air UE function.
[0252] In an exemplary embodiment, the method further includes: in response to receiving the UE subscription information, receiving, by the first communication node, at least one of the following information from the second communication node:
[0253] (1) an indicator for requesting the first communication node to configure a UE height measurement value for the UE;
[0254] (2) UE height measurement configuration, generated by the second communication node;
[0255] (3) an indicator for requesting a UE altitude report from the first communication node;
[0256] (4) an indicator indicating whether the second communication node requires a UE height measurement report;
[0257] (5) an indicator for requesting the first communication node to configure a UE flight path report to the UE;
[0258] (6) A request for UE flight path report configuration, generated by the second communication node;
[0259] (7) an indicator for requesting a UE flight path report owned by the first communications node; or
[0260] (8) An indicator used to indicate whether the second communication node requires a UE flight path report.
[0261] Transmission of UE subscription information
[0262] In response to the addition of the SN, the MN may send the air UE subscription information to the SN via an Xn / X2 message. For example, the MN may include the UE subscription information in the indicator in the SN add request message. This information is used to inform the SN whether the UE is allowed to use the air / UAV UE function. If the UE is allowed, the SN may configure the UAV-specific functions (e.g., altitude reporting, flight path reporting, interference detection, etc.) to the UE, or request UAV-related information (e.g., altitude reporting, flight path reporting) from the MN or UE.
[0263] Altitude measurement configuration
[0264] According to one embodiment of the present disclosure, a wireless communication method further includes: sending a UE altitude measurement configuration from a first communication node to a UE to configure the UE to perform altitude measurement, which may be in response to a request from a second communication node.
[0265] According to one embodiment of the present disclosure, the UE height measurement configuration includes at least one of the following:
[0266] When a condition based on the reference altitude threshold is met, the UE triggers the reference altitude threshold for altitude measurement; or
[0267] A reference height threshold list, each reference height threshold being associated with at least one of the following items: cell ID information, reference signal identification (RS ID), or transmission reception point (TRP) information.
[0268] In the MR-DC (Multi-RAT Dual Connectivity) scenario, the configuration of the altitude measurement value may be decided or configured by the MN and / or the SN.
[0269] If both the MN and the SN can configure altitude measurements independently, the MN and the SN may need to coordinate altitude-related measurement IDs according to the following alternatives.
[0270] For example, the MN may indicate the maximum number of highly correlated measurement IDs that the SN may configure via an Xn / X2 message (eg, an SN Add Request message or an SN Modify Request message).
[0271] Alternatively, the MN and SN may renegotiate the maximum number of highly correlated measurement IDs that the SN may configure.
[0272] The MN may indicate the maximum number of highly correlated measurement IDs that the SN may configure via an Xn / X2 message (eg, an SN Add Request message or an SN Modify Request message).
[0273] If the SN requests more, the SN may send the requested maximum number of highly correlated measurement IDs to the MN via an Xn / X2 message (eg, a message requiring SN modification). The MN may accept or reject the SN's request.
[0274] If only the MN can configure the height measurement value (ie, if the height measurement configuration can only be sent via a MN RRC message), the SN may send a request message (eg, heightMeas-Request) to the MN via an Xn / X2 message (eg, a message that requires modification by the SN).
[0275] If the MN has the latest altitude report received from the UE or / and the altitude report meets the requirements of the SN, for example, the altitude of the UE in the air is higher or lower than the reference altitude threshold required / configured by the SN, the MN may transmit the altitude report to the SN in response to the request of the SN via an Xn / X2 message (e.g., an SN modification confirmation message). Otherwise, the MN configures the altitude measurement value to the UE as the request information of the SN.
[0276] The request information may include at least one of the following:
[0277] An indicator for requesting the MN to configure an altitude measurement value; or
[0278] The altitude measurement configuration generated by the SN, such as the altitude reference threshold. The detailed altitude measurement configuration may also include the configuration described in Section 1.1.1 Altitude Measurement Configuration of this disclosure.
[0279] The above information (e.g., the maximum number of altitude-related measurement IDs, request information from the SN, altitude report information) may be transmitted between the SN and the MN in at least one of the following ways:
[0280] This information may be included directly in the Xn / X2 message as an IE; or
[0281] Alternatively, the information may be included in an RRC message (eg, CG-ConfigInfo or CG-Config message). The RRC message is included as an IE in an Xn / X2 message.
[0282] Altitude measurement report transmission
[0283] Additionally, altitude measurement reports may be transmitted between the MN and the SN.
[0284] According to one embodiment of the present disclosure, a wireless communication method further includes transmitting at least one of the following information from a first communication node to a second communication node: location, altitude, speed, or flight path information of a UE.
[0285] According to one embodiment of the present disclosure, a wireless communication method further includes sending at least one of the following from a first communication node to a second communication node:
[0286] an indication that the altitude of the UE satisfies an altitude threshold configured by the second communications node; or
[0287] An indication of the identity of a cell, RS or TRP, a threshold of which configured by the second communication node is met.
[0288] For example, when the MN receives the altitude measurement report from the UE, the MN may send altitude measurement report related information to the SN via an Xn / X2 message (eg, an SN modification request message or other / new message).
[0289] Alternatively, in response to a request from the SN or an indication from the SN that the SN needs an altitude measurement report, the MN may send altitude measurement report related information to the SN.
[0290] Specifically, the SN may send an indicator to the MN via an Xn / X2 message (e.g., a message requiring SN modification or other / new message) to request an altitude report, or indicate via an Xn / X2 message (e.g., an SN add response message or an SN modify response message) whether the SN is interested in or requires an altitude measurement report of the UE.
[0291] The MN may send the altitude measurement report related information to the SN via an Xn / X2 message (eg, an SN modification confirm message, an SN modification request message, or other / new messages).
[0292] The altitude measurement report related information in the present disclosure may include at least one of the following items:
[0293] (1) Altitude measurement report, such as the UE’s altitude;
[0294] (2) an indication of whether a height measurement report is received from the UE, or whether the height of the UE meets a threshold configured by the SN; or
[0295] (3) A list of cell / RS / PRP ID information whose associated altitude report is received from the UE, or the UE's altitude meets the threshold associated with the cell / RS / PRP information configured by the SN.
[0296] Additionally, the altitude report related information may be transmitted via at least one of the following methods:
[0297] (1) The information can be included directly in the Xn / X2 message as an IE; or
[0298] (2) This information may be included in an RRC message (eg, CG-ConfigInfo, CG-Config message), and the RRC message may be included as an IE in an Xn / X2 message.
[0299] Request for flight path report configuration
[0300] According to one embodiment of the present disclosure, a wireless communication method further includes: sending a request for flight path report configuration from the first communication node to the UE.
[0301] According to one embodiment of the present disclosure, the request for flight path report configuration includes at least one of the following items:
[0302] The maximum number of waypoints that a UE may include in a flight path report; or
[0303] Indicator to indicate whether a timestamp is required for the waypoint.
[0304] For the MR-DC case, the request for flight path report may be determined or configured by the MN and / or the SN.
[0305] If only the MN can configure the request for flight path reporting, the SN can send a request message (eg, flightPath-Request) to the MN via an Xn / X2 message (eg, a message that requires SN modification) to request the MN to configure the flight path reporting.
[0306] If the MN has the latest flight path report received from the UE, the MN may transmit the flight path report to the SN via an Xn / X2 message (e.g., SN Modify Confirm message) in response to the SN's request for the flight path report. Otherwise, the MN may configure the flight path request to the UE as the SN's request information.
[0307] The request information received by the MN from the SN may include at least one of the following items:
[0308] (1) An indicator for requesting the MN to configure a flight path report;
[0309] (2) the maximum number of waypoints that a UE may include in a flight path information report; or
[0310] (3) If timestamp information is available at the UE, an indicator indicating whether the timestamp of each waypoint can be reported in the flight path report.
[0311] The above information (e.g., request information from SN, flight path report information) may be transmitted in at least one of the following ways:
[0312] (1) The information can be included directly in the Xn / X2 message as an IE; or
[0313] (2) This information may be included in an RRC message (eg, CG-ConfigInfo or CG-Config message), and the RRC message may be included in an Xn / X2 message as an IE.
[0314] Flight path report transmission
[0315] Additionally, the MN may transmit the flight path report in one of the following ways.
[0316] For example, when the MN receives a flight path report from the UE, the MN may send the flight path report information to the SN via an Xn / X2 message (eg, an SN modification request message or other / new message).
[0317] Alternatively, the MN may send flight path report information to the SN in response to a request from the SN or if the SN indicates that the SN requires a flight path report.
[0318] For example, the SN may send an indicator to the MN via an Xn / X2 message (e.g., a message requiring SN modification or other / new message) to request a flight path report, or indicate via an Xn / X2 message (e.g., an SN add response or an SN modify response) whether the SN is interested in or requires a flight path report from the UE.
[0319] In an embodiment, the MN may send the flight path information to the SN via an Xn / X2 message (eg, an SN modification confirm message, an SN modification request message, or other / new messages).
[0320] Exemplarily, the above flight path information may include at least one of the following items:
[0321] A list of position information of waypoints along the planned flight path of the UE; or
[0322] Timestamp for each waypoint.
[0323] Exemplarily, the above flight path report related information (such as an indicator from the SN, flight path information from the MN) may be transmitted via at least one of the following methods:
[0324] This information may be included directly in the Xn / X2 message as an IE; or
[0325] Alternatively, the information may be included in an RRC message (eg, CG-ConfigInfo, CG-Config message), and the RRC message may be included as an IE in an Xn / X2 message.
[0326] 6. Interaction / Coordination between CU and DU
[0327] When wireless communication has Figure 1 When the CU / DU separation structure is shown, the information transmission between the CU and DU can improve the functionality of the UE in the air.
[0328] Transmission of UE subscription information
[0329] When setting up the UE context between the CU and the DU, the CU may send the air UE subscription information to the DU via the F1 message. For example, the CU may include an indicator in the UE context setup request message to the DU. This information is used to inform the DU whether the UE is allowed to use the air UE function. If the UE is allowed to use the air UE function, the DU may configure the UE with UAV-specific functions (e.g., altitude reporting, flight path reporting, interference detection, etc.), or may request UAV-related information (e.g., altitude reporting, flight path reporting) from the CU or the UE.
[0330] Altitude measurement configuration
[0331] In case of CU / DU separation, the configuration of the altitude measurement value can be determined by the CU and / or the DU.
[0332] If the DU decides on the altitude measurement configuration or partial altitude measurement configuration (e.g., reference altitude threshold), the DU may send the altitude measurement configuration to the CU via the F1 message. For example, the DU may include the altitude measurement configuration in the IE DU to CU RRC information in a message requiring UE context modification or other message.
[0333] Exemplarily, the height measurement configuration may include at least one of the following items:
[0334] A reference altitude threshold, used as the threshold to trigger altitude measurement; or
[0335] A list of reference height thresholds, each reference height threshold is associated with cell ID information (e.g., CGI, PCI+frequency), RS information (e.g., SSB index, CSI-RS index), or TRP information (e.g., TCI-StateId, coresetPoolIndex).
[0336] Altitude measurement report transmission
[0337] Additionally, altitude measurement reports may be transmitted between the CU and the DU.
[0338] For example, when the DU receives an altitude measurement report from the UE, the CU may send altitude measurement report related information to the DU via an F1 message (eg, a UE context modification request message or other / new message).
[0339] Alternatively, in response to a request from the DU, or an indication from the DU that the DU needs an altitude measurement report, the CU may send altitude measurement report related information to the DU.
[0340] Specifically, the DU may send an indicator to the CN via an F1 message (e.g., a message requiring UE context modification or other / new message) to request an altitude report, or indicate via an F1 message (e.g., a UE context setup response message or other / new message) whether the DU is interested in or requires an altitude measurement report from the UE.
[0341] The CU may send the altitude measurement report related information to the DU via an F1 message (eg, a UE context modification confirm message, a UE context modification request message, or other / new messages).
[0342] The altitude measurement report related information in the present disclosure may include at least one of the following items:
[0343] (1) Altitude measurement report, such as the UE’s altitude;
[0344] (2) an indication of whether a height measurement report has been received from the UE; or
[0345] (3) A list of cell / RS / TRP ID information, whose associated height report is received from the UE.
[0346] Additionally, the altitude report related information may be transmitted via at least one of the following methods:
[0347] (1) The information may be included directly in the F1 message as an IE; or
[0348] (2) This information may be included in an RRC message (eg, CG-ConfigInfo, CG-Config message), and the RRC message may be included in the F1 message as an IE.
[0349] Flight path report transmission
[0350] Additionally, the CU may transmit the flight path report in one of the following ways.
[0351] For example, when the CU receives a flight path report from the UE, the CU may send the flight path report information to the DU via an F1 message (eg, a UE context modification request message or other / new message).
[0352] Alternatively, the CU may send flight path report information to the DU in response to a request from the DU or if the DU indicates that the DU requires a flight path report.
[0353] For example, the DU may send an indicator to the CN via an F1 message (e.g., a message requiring UE context modification or other / new message) to request a flight path report, or indicate via an F1 message (e.g., a message requiring UE context modification or other / new message) whether the DU is interested in, or requires, a flight path report from the UE.
[0354] In an embodiment, the CU may send the flight path information to the DU via an F1 message (eg, a UE context modification confirm message, a UE context modification request message, or other / new messages).
[0355] Exemplarily, the above flight path information may include at least one of the following items:
[0356] A list of position information of waypoints along the planned flight path of the UE; or
[0357] Timestamp for each waypoint.
[0358] Exemplarily, the above flight path report related information (such as an indicator from the DU, flight path information from the CU) can be transmitted via at least one of the following methods:
[0359] This information may be included directly in the F1 message as an IE; or
[0360] Alternatively, the information may be included in an RRC message (eg, CG-ConfigInfo, CG-Config message, or HandoverPreparationInformation), and the RRC message may be included in the F1 message as an IE.
[0361] 7. Platform
[0362] Figure 5 A wireless communication device according to an embodiment of the present disclosure is shown. The structure can be used as a UE, BS, MN, SN, CU or DU or other wireless communication system to perform the method of the present disclosure. The wireless communication device includes one or more processors and one or more memory sets. The memory stores one or more non-transient computer-readable medium programs. One or more processors can execute the non-transient computer-readable medium program to execute the method for wireless communication illustrated above. Exemplarily, the wireless communication device may include a transmitter and a receiver for sending or receiving signals. The wireless communication device may also include a user input / output interface for accepting user commands. The method of the present disclosure can be performed by a communication system having a group of devices, wherein the group of devices can be regarded as the whole of the wireless communication device.
[0363] Further, at least one program may be stored in the memory, and the program may be delivered by a computer program product. The computer program product includes a non-transitory computer-readable program medium code stored thereon. When executed by at least one processor, the code causes the at least one processor to implement the method for wireless communication program illustrated above.
[0364] Some embodiments described herein are described in the general context of methods or processes, which in some embodiments may be implemented by a computer program product implemented in a computer-readable medium, including computer executable instructions, such as program code, executed by a computer in a networked environment. Computer-readable media may include volatile and non-volatile storage devices, including but not limited to digital versatile disks (DVDs), compact disks (CDs), read-only memories (ROMs), random access memories (RAMs), and the like. Therefore, computer-readable media may include non-transient storage media. Typically, program modules may include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. Computer or processor executable instructions, associated data structures, and program modules represent examples of program codes for executing the steps of the methods disclosed herein. A specific sequence of such executable instructions or associated data structures represents an example of corresponding actions for implementing the functions described in such steps or processes.
[0365] Some disclosed embodiments may be implemented as devices or modules using hardware circuits, software or a combination thereof. For example, a hardware circuit implementation may include discrete analog and / or digital components, which are, for example, integrated as a part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as field programmable gate arrays (FPGAs) and / or application specific integrated circuits (ASICs) devices. Some embodiments may additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor with an architecture optimized for the operational needs of digital signal processing associated with the functionality disclosed in the present application. Similarly, various components or subcomponents within each module may be implemented with software, hardware or firmware. Any of the connection methods and media known in the art may be used to provide connectivity between modules and / or components within the modules, including but not limited to communication using appropriate protocols through the Internet, wired or wireless networks.
[0366] Although many details are included herein, these details should not be interpreted as limitations on the scope of the claimed invention or the content that may be claimed, but as descriptions of features specific to particular embodiments. Some features described in the context of a separate embodiment herein can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or according to any suitable sub-combination. Moreover, although features may be described as working with certain combinations or even initially claimed in this way above, one or more features from the claimed combination can be cut out from the combination in some cases, and the claimed combination can point to a sub-combination or a change in the sub-combination. Similarly, although operations are described in a particular order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or all illustrated operations are performed to achieve the desired result.
[0367] Only a few implementations and examples are described, and other implementations, enhancements, and variations may be made based on what is described and illustrated in this disclosure.
Claims
1. A wireless communication method, comprising: User equipment (UE) subscription information is sent from a first communication node to a second communication node, wherein the UE subscription information is used to indicate whether the UE is allowed to use over-the-air UE functionality.
2. The method according to claim 1, further comprising: In response to receiving the UE subscription information, the first communication node receives at least one of the following information from the second communication node: An indicator for requesting the first communication node to configure UE height measurement for the UE; a UE altitude measurement configuration generated by the second communication node; an indicator for requesting a UE altitude report from the first communication node; an indicator indicating whether the second communication node requires a UE altitude measurement report; an indicator for requesting the first communication node to configure a UE flight path report to the UE; a request for UE flight path reporting configuration generated by the second communication node; an indicator for requesting a UE flight path report owned by the first communications node; or An indicator for indicating whether the second communication node requires a UE flight path report.
3. The method according to claim 1, further comprising: At least one of the following items is sent from the first communication node to the UE: UE altitude measurement configuration, used to configure the UE to perform altitude measurement; or Request for UE flight path reporting configuration.
4. The method according to claim 3, wherein the UE height measurement configuration comprises at least one of the following items: a reference height threshold, for the UE to trigger the height measurement for the UE if a condition based on the reference height threshold is met; or A reference height threshold list, each reference height threshold being associated with at least one of the following items: cell ID information, reference signal identification (RSID) or transmission reception point (TRP) information.
5. The method of claim 3, wherein the request for the UE flight path reporting configuration comprises at least one of: The maximum number of waypoints that the UE may include in a flight path report; or Indicator to indicate whether a timestamp is required for the waypoint.
6. The method according to claim 1, further comprising: At least one of the following information is sent from the first communication node to the second communication node: location, altitude, speed, or flight path information of the UE.
7. The method according to claim 1, further comprising: Sending at least one of the following from the first communication node to the second communication node: an indication that the altitude of the UE satisfies an altitude threshold configured by the second communications node; or An indication of the identity of a cell, RS or TRP, a threshold of which configured by the second communication node is met.
8. The method according to any one of claims 1 to 7, wherein the first communication node is a master node (MN) and the second communication node is a secondary node (SN).
9. The method according to any one of claims 1 to 7, wherein the first communication node is a centralized unit (CU) and the second communication node is a distributed unit (DU).
10. The method according to any one of claims 1 to 7, wherein the first communication node is a source MN and the second communication node is a target MN, and wherein the information is sent via a handover request message.
11. A wireless communication method, comprising: User equipment (UE) subscription information is received by a second communication node from a first communication node, wherein the UE subscription information is used to indicate whether the UE is allowed to use over-the-air UE functionality.
12. The method according to claim 11, further comprising: In response to receiving the UE subscription information, the second communication node sends at least one of the following information to the first communication node: An indicator for requesting the first communication node to configure UE height measurement for the UE; UE altitude measurement configuration, where the UE altitude measurement configuration is generated by the second communication node; an indicator for requesting a UE altitude report from the first communication node; an indicator indicating whether the second communication node requires a UE altitude measurement report; an indicator for requesting the first communication node to configure a UE flight path report to the UE; a request for UE flight path reporting configuration generated by the second communication node; an indicator for requesting a UE flight path report owned by the first communications node; or An indicator for indicating whether the second communication node requires a UE flight path report.
13. The method according to claim 12, wherein the UE height measurement configuration comprises at least one of the following: a reference height threshold, for the UE to trigger the height measurement when a condition based on the reference height threshold is met; or A reference height threshold list, each reference height threshold being associated with at least one of the following items: cell ID information, reference signal identification (RS ID), or transmission reception point (TRP) information.
14. The method of claim 12, wherein the request for the UE flight path reporting configuration comprises at least one of: The maximum number of waypoints that the UE may include in a flight path report; or Indicator to indicate whether a timestamp is required for the waypoint.
15. The method according to claim 12, further comprising: At least one of the following information is received by the second communication node from the first communication node: location, altitude, speed, or flight path information of the UE.
16. The method according to claim 12, further comprising: Receiving, by the second communication node from the first communication node, at least one of the following: an indication that the altitude of the UE satisfies an altitude threshold configured by the second communications node; or An indication of an identification of a cell, an RS or a TRP, a threshold of the cell, the RS or the TRP configured by the second communication node is met.
17. The method according to any one of claims 11 to 16, wherein the first communication node is a master node (MN) and the second communication node is a secondary node (SN).
18. The method according to any one of claims 11 to 16, wherein the first communication node is a centralized unit (CU) and the second communication node is a distributed unit (DU).
19. The method according to any one of claims 11 to 16, wherein the first communication node is a source MN and the second communication node is a target MN, and wherein the information is sent via a handover request message.
20. A wireless communication method, comprising: A configuration message is received by a user equipment (UE) from a wireless communication node to configure at least one of the following configurations of the UE: UE altitude measurement configuration; or Request for UE flight path reporting configuration; and Based on the configuration message, a report to the wireless communication node is triggered.
21. The wireless communication method according to claim 20, wherein the UE height measurement configuration comprises at least one of the following parameters: Reference altitude threshold; offset of the reference altitude threshold; The hysteresis parameters used in the entry and exit conditions of the event trigger reporting conditions; a trigger time parameter indicating a timer during which a specific criterion for the event needs to be met to trigger a measurement report; an indicator indicating whether the UE is allowed to initiate UE altitude measurement when the leaving condition is met; The UE periodically reports the interval or period of UE height measurement; or The maximum number of UE altitude measurement reports available to the UE.
22. The wireless communication method according to claim 21, wherein the UE height measurement configuration is associated with at least one of the following items: cell ID information, reference signal identification (RSID), or transmission reception point (TRP) information.
23. The wireless communication method according to claim 20, wherein the UE height measurement configuration is indicated by at least one of the following items: measurement object information, measurement report configuration, or RS or beam measurement configuration.
24. The wireless communication method according to claim 20, further comprising: In response to the altitude of the UE satisfying an altitude threshold configuration configured by the wireless communication node, sending a UE altitude measurement report to the wireless communication node.
25. The wireless communication method according to claim 24, further comprising: Based on the reporting interval configuration and the reporting quantity configuration in the UE height measurement configuration, when the height of the UE meets the height threshold configuration configured by the wireless communication node, additional UE height measurement reports are periodically sent to the wireless communication node.
26. The wireless communication method according to claim 24, wherein the UE height measurement report comprises at least one of the following: The height of the UE; an indication that the altitude of the UE satisfies the altitude threshold configuration; or An indication of the identity of a cell, RS or TRP, the associated height threshold of the cell, RS or TRP configured by the height threshold configuration being met.
27. The wireless communication method according to claim 24, wherein the UE height measurement report is carried by at least one of the following items: a radio resource control (RRC) message, a medium access control control element (MAC CE), or layer one (L1) signaling.
28. The wireless communication method according to claim 20, wherein the configuration message further includes at least one of the following items: a measurement object (MO) configuration for interference detection, or a report configuration.
29. A wireless communication method according to claim 28, wherein the MO configuration includes a reference MO ID associated with a reference MO configuration, wherein the MO configuration and the reference MO configuration are associated with the same synchronization signal block (SSB) or channel state information reference signal (CSI-RS) frequency.
30. The wireless communication method according to claim 28, wherein the MO configuration comprises at least one of the following: a plurality of parameters used for said interference detection and radio resource management (RRM) measurement respectively; or An indicator indicating whether the UE is instructed to perform the interference detection, or whether the measurement object is applicable to interference detection.
31. The wireless communication method according to claim 30, wherein the plurality of parameters comprises at least one of the following: a threshold for combining one or more synchronization signal (SS) / physical broadcast channel (PBCH) block based measurements from a layer one (L1) filter; a threshold for combining measurements from one or more channel state information reference signal (CSI-RS) resource blocks based on the L1 filter; Maximum number of averages of beam measurements based on one or more SS / PBCH blocks; The maximum number of averages of beam measurement results based on one or more CSI-RS resources; or List of cells used for interference detection.
32. The wireless communication method of claim 28, wherein the reporting configuration comprises at least one of the following: a plurality of parameters respectively used for said interference detection and RRM measurement; or An indicator indicating whether the UE is instructed to perform the interference detection, or whether the reporting configuration is applicable to interference detection.
33. The wireless communication method according to claim 31, further comprising: The UE derives cell quality of one or more neighboring cells based on the multiple parameters used for the interference detection, wherein the cell quality is used to determine whether to trigger a measurement report for interference detection.
34. The wireless communication method according to claim 20, further comprising: When an MCG or SCG failure is detected, a failure report is sent to the wireless communication node, and the failure report includes at least one of the following information: the location, altitude, speed, or flight path information of the UE.
35. The wireless communication method according to claim 34, wherein the MCG or SCG failure comprises at least one of the following items: radio link failure, handover failure, PSCell addition failure or PSCell change failure.
36. A wireless communication method, comprising: The wireless communication node sends a configuration message to the UE to configure at least one of the following configurations of the UE: UE altitude measurement configuration; or Request for UE flight path reporting configuration; and A report is received by the wireless communication node from the UE, the report being generated according to the configuration message.
37. The wireless communication method according to claim 36, wherein the UE height measurement configuration comprises at least one of the following parameters: Reference altitude threshold; offset of the reference altitude threshold; The hysteresis parameters used in the entry and exit conditions of the reporting conditions triggered by the event; a trigger time parameter indicating a timer during which specific criteria for the event need to be met to trigger a measurement report; an indicator, indicating whether the UE is allowed to initiate UE altitude measurement when the leaving condition is met; The UE periodically reports the interval or period of UE height measurement; or The maximum number of UE altitude measurement reports available to the UE.
38. The wireless communication method of claim 37, wherein the UE height measurement configuration is associated with at least one of the following items: cell ID information, reference signal identification (RSID), or transmission reception point (TRP) information.
39. The wireless communication method according to claim 36, wherein the UE height measurement configuration is indicated by at least one of the following items: measurement object information, measurement report configuration, or RS or beam measurement configuration.
40. The wireless communication method of claim 36, wherein the UE altitude measurement report is sent in response to the altitude of the UE satisfying an altitude threshold configuration configured by the wireless communication node.
41. The wireless communication method according to claim 36, further comprising: Based on the reporting interval configuration and the reporting quantity configuration in the UE height measurement configuration, when the height of the UE meets the height threshold configuration configured by the wireless communication node, the wireless communication node periodically receives additional UE height measurement reports.
42. The wireless communication method of claim 36, wherein the UE altitude measurement report comprises at least one of the following: The height of the UE; an indication that the altitude of the UE satisfies an altitude threshold configuration; or An indication of an identification of a cell, RS or TRP, the associated height threshold of the cell, RS or TRP configured by the height threshold configuration is met.
43. The wireless communication method according to claim 36, wherein the UE height measurement report is carried by at least one of the following items: a radio resource control (RRC) message, a medium access control control element (MAC CE), or layer one (L1) signaling.
44. The wireless communication method according to claim 36, wherein the configuration message further includes at least one of the following items: measurement object (MO) configuration for interference detection, or report configuration.
45. A wireless communication method according to claim 44, wherein the MO configuration includes a reference MOID associated with a reference MO configuration, wherein the MO configuration and the reference MO configuration are associated with the same synchronization signal block (SSB) or channel state information reference signal (CSI-RS) frequency.
46. The wireless communication method of claim 44, wherein the MO configuration comprises at least one of the following: a plurality of parameters used for said interference detection and radio resource management (RRM) measurement respectively; or An indicator indicating whether the UE is instructed to perform the interference detection or whether the measurement object is applicable to interference detection.
47. The wireless communication method of claim 46, wherein the plurality of parameters comprises at least one of the following: a threshold for combining one or more synchronization signal (SS) / physical broadcast channel (PBCH) block based measurements from a layer one (L1) filter; a threshold for combining measurements from one or more channel state information reference signal (CSI-RS) resource blocks based on the L1 filter; Maximum number of averages of beam measurements based on one or more SS / PBCH blocks; The maximum number of averages of beam measurement results based on one or more CSI-RS resources; or List of cells used for interference detection.
48. The wireless communication method of claim 44, wherein the reporting configuration comprises at least one of the following: a plurality of parameters respectively used for said interference detection and RRM measurement; or An indicator indicating whether the UE is instructed to perform the interference detection or whether the reporting configuration is applicable to interference detection.
49. The wireless communication method according to claim 46, further comprising: An interference detection report is received from the UE, wherein the interference detection report includes cell quality of one or more neighboring cells, wherein the cell quality is derived based on the multiple parameters for the interference detection.
50. The wireless communication method according to claim 36, further comprising: In the case where the UE detects that the MCG or SCG fails, a failure report is received from the UE, the failure report including at least one of the following information: the location, altitude, speed, or flight path information of the UE.
51. The wireless communication method according to claim 50, wherein the MCG or SCG failure comprises at least one of the following items: radio link failure, handover failure, PSCell addition failure, or PSCell change failure.
52. A wireless communication method, comprising: Receiving, by a user equipment (UE), at least one of the following information for cell selection or reselection from a wireless communication node: An indicator indicating whether the cell is not suitable for over-the-air UE access; an indicator indicating whether the cell is not suitable for access by an aerial UE, wherein the altitude of the aerial UE is within a certain range; an indicator indicating whether a frequency or a cell is not suitable for cell reselection by an aerial UE, wherein the altitude of the aerial UE is within a certain range; or priority information, the priority information setting a priority for selecting between a plurality of neighboring cells; and Cell selection or reselection is performed according to the at least one item of the information.
53. The wireless communication method according to claim 52, wherein the priority information comprises: A first priority set and a second priority set corresponding to the airborne UEs at different altitudes, and condition information indicating the conditions for applying the first priority set and the second priority set.
54. A wireless communication method, comprising: At least one of the following information for cell selection or reselection is sent by a wireless communication node to a user equipment (UE): An indicator indicating whether the cell is not suitable for over-the-air UE access; an indicator indicating whether the cell is not suitable for access by an aerial UE, wherein the altitude of the aerial UE is within a certain range; an indicator indicating whether a frequency or a cell is not suitable for cell reselection by an aerial UE, wherein the altitude of the aerial UE is within a certain range; or Priority information, where the priority information sets a priority for selecting between multiple neighboring cells.
55. The wireless communication method according to claim 54, wherein the priority information comprises: A first priority set and a second priority set corresponding to the airborne UEs at different altitudes, and condition information indicating the conditions for applying the first priority set and the second priority set.
56. A wireless communication device, comprising: at least one memory storing at least one program; as well as One or more processors, in communication with the at least one memory and configured to execute the at least one program so that the wireless communication device performs the method according to any one of claims 1 to 55.
57. A non-transitory computer-readable storage medium storing at least one program, which, when executed by one or more processors, causes a wireless communication device to perform the method according to any one of claims 1 to 55.
