Risk assessment system and method for low-altitude flight based on risk assessment model

Abstract

The invention provides a risk assessment system and method for low-altitude flight based on a risk assessment model, and relates to the technical field of traffic management. The system comprises a model management module which is used for establishing a new risk assessment model according to a model name and an application service range, and managing the newly established risk assessment model and a historically established risk assessment model; the model configuration module is used for displaying a plurality of preset risk categories and risk factors thereof to the user based on the model name and the application service range, configuring a newly built risk assessment model according to the selection and / or input of the user, and sending the configured risk assessment model to the model management module; and the risk assessment module is used for acquiring a target risk assessment model selected by a user from the model management module according to the business type of the to-be-assessed flight application, and performing risk assessment on the to-be-assessed flight application based on the target risk assessment model, thereby realizing low-altitude flight risk assessment with good adaptability and good flexibility.

Description

Technical Field

[0001] This application relates to the field of traffic management technology, specifically to a risk assessment system and method for low-altitude flight based on a risk assessment model. Background Technology

[0002] Currently, with the rapid development of the drone industry, drone flight activities are becoming increasingly frequent, making effective supervision of their operational safety an urgent need. At present, risk assessments for drone flights largely rely on relevant regulatory frameworks and internationally accepted methods such as SORA.

[0003] However, traditional risk assessment models are typically static, with fixed weights and parameters. Based on this, approvers can only conduct assessments according to the existing model's risk assessment standards. The assessment process relies heavily on the personal experience of the reviewers, potentially leading to assessment results that are out of touch with the actual risk situation—either too lenient, creating safety hazards, or too strict, restricting industrial development. Summary of the Invention

[0004] Based on this, this application provides a risk assessment system and method for low-altitude flight based on a risk assessment model, which achieves low-altitude flight risk assessment with good adaptability and flexibility.

[0005] According to one aspect of this application, a risk assessment system for low-altitude flight based on a risk assessment model is proposed, comprising: a model management module, used to create new risk assessment models according to model names and application business scopes, and manage newly created risk assessment models and historically constructed risk assessment models; a model configuration module, used to display multiple pre-set risk categories and their risk factors to users based on model names and application business scopes, configure the newly created risk assessment model according to user selections and / or inputs, and send the configured risk assessment model to the model management module; and a risk assessment module, used to obtain the target risk assessment model selected by the user from the model management module according to the business type of the flight application to be assessed, and perform risk assessment on the flight application to be assessed based on the target risk assessment model.

[0006] According to some embodiments, the model management module supports model creation, model query, model publishing, model decommissioning, model deletion, and / or model copying operations.

[0007] According to some embodiments, the model management module includes: a model repository for storing newly created risk assessment models and historically built risk assessment models.

[0008] According to some embodiments, the model configuration module includes: a basic information configuration unit, used to configure the basic information of the newly created risk assessment model according to the model name and application business scope; and a risk factor configuration unit, used to display multiple risk categories and their risk factors to the user, and to obtain the risk categories and risk factors selected and / or input by the user, as well as their corresponding weights, as the target risk categories and their category weights and target risk factors and their factor weights of the newly created risk assessment model.

[0009] According to some embodiments, the risk factor configuration unit includes: a weight configuration subunit, used to provide a configuration interface to obtain a first weight value configured by the user for a target risk category, and a second weight value configured for a target risk factor; and / or a parameter setting subunit, used to provide a setting interface to obtain risk calculation parameter values ​​set by the user for one or more target risk factors.

[0010] According to some embodiments, the weight configuration subunit is also used to: verify the category weights and factor weights according to preset verification logic.

[0011] According to some embodiments, the preset verification logic includes: the sum of the category weights of multiple risk categories is 100%; and / or the sum of the factor weights of the risk factors of the risk categories is 100%.

[0012] According to some embodiments, the risk factor configuration unit further includes: a risk weight calculator, used to display target risk categories and / or target risk factors, construct a target risk category matrix and / or target risk factor matrix based on a first weight value and / or a second weight value, and calculate category weights and / or factor weights based on the target risk category matrix and / or target risk factor matrix.

[0013] According to some embodiments, the risk weight calculator is also used to: perform consistency checks on category weights and factor weights.

[0014] According to some embodiments, multiple risk categories include at least one of the following: airspace risk, ground risk, weather risk, planning risk, operator risk, and social risk.

[0015] According to some embodiments, the risk assessment module is used to: filter risk assessment models from the model management module that match the business type and are currently active as a candidate risk assessment model group; obtain the target risk assessment model selected by the user from the candidate risk assessment model group; and perform risk assessment on the flight application to be assessed based on the target risk assessment model, and output the risk assessment result.

[0016] According to one aspect of this application, a risk assessment method for low-altitude flight based on a risk assessment model includes: creating a new risk assessment model based on a model name and application business scope; displaying multiple pre-set risk categories and their risk factors to the user based on the model name and application business scope, configuring the new risk assessment model according to the user's selection and / or input; obtaining the target risk assessment model selected by the user from the configured risk assessment model and historically constructed risk assessment models according to the business type of the flight application to be assessed, and performing a risk assessment on the flight application to be assessed based on the target risk assessment model.

[0017] According to one aspect of this application, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs; and, when the one or more programs are executed by the one or more processors, causing the one or more processors to implement the method as described above.

[0018] According to one aspect of this application, a computer-readable medium is provided that stores a computer program or instructions thereon, which, when executed by a processor, implement the method as described above.

[0019] Through the embodiments provided in this application, by setting up a model management module, users can freely create new risk assessment models based on model names and application business scopes; by setting up a model configuration module, users can intuitively select multiple risk categories and their risk factors. Simultaneously, users can configure risk categories and risk factors according to their needs. The configured risk assessment model is sent to the model management module for management, which stores newly created risk assessment models as well as historically constructed risk assessment models. By setting up a risk assessment module, users can select a target risk assessment model from the models stored in the model management module based on the business type of the flight application to be assessed, and perform risk assessment based on the target risk assessment model. Based on this, users can flexibly customize, deploy, and invoke risk assessment models according to actual needs, achieving adaptable and flexible low-altitude flight risk assessment. Attached Figure Description

[0020] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this application.

[0021] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings, without exceeding the scope of protection claimed by this application.

[0022] Figure 1A block diagram of a risk assessment system for low-altitude flight based on a risk assessment model provided in this application embodiment;

[0023] Figure 2 A block diagram of the model configuration module of the low-altitude flight risk assessment system based on a risk assessment model provided in this application embodiment; Figure 3 An operation flowchart of an embodiment of a risk assessment system for low-altitude flight based on a risk assessment model provided in this application; Figure 4 A block diagram of the risk factor configuration unit of the low-altitude flight risk assessment system based on a risk assessment model provided in this application embodiment; Figure 5 A flowchart of a risk assessment method for low-altitude flight based on a risk assessment model provided in this application embodiment; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0026] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0027] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0028] It should be understood that although the terms first, second, third, etc., may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Therefore, the first component discussed below may be referred to as the second component without departing from the teachings of this application. As used herein, the term "and / or" includes all combinations of any one and more of the associated listed items.

[0029] In existing technologies, traditional risk assessment models are typically static, with fixed weights and parameters, making them inflexible and unable to adapt to dynamic changes in management priorities and risk appetites across different regions and business scenarios (such as urban logistics, agricultural plant protection, and emergency rescue). Approving authorities cannot quickly adjust assessment standards or customize risk assessment standards to meet their own management needs based on specific flight activity applications or jurisdictional characteristics (such as population density and airspace complexity). This can lead to assessment results that are out of sync with actual risk conditions, either being too lenient and causing safety hazards, or too strict and restricting industrial development. Furthermore, the construction of risk assessment models is often a one-off process, and approving authorities lack an intuitive and systematic tool for continuous optimization and customization of risk assessment models, making the assessment process heavily reliant on the personal experience of reviewers.

[0030] Based on this, this application provides a risk assessment system and method for low-altitude flight based on a risk assessment model.

[0031] For specific implementation details, please refer to the following examples.

[0032] Figure 1 A block diagram of a low-altitude flight risk assessment system based on a risk assessment model, provided as an embodiment of this application. Figure 1 As shown, the system includes a model management module 110, a model configuration module 120, and a risk assessment module 130.

[0033] The model management module 110 is used to create new risk assessment models based on model names and application business scope, and to manage newly created risk assessment models and historically constructed risk assessment models.

[0034] The model management module 110 is used for centralized data management of all risk assessment models, including newly created risk assessment models and historically constructed risk assessment models. Each risk assessment model corresponds to an appropriate application business scope and a model name for differentiation.

[0035] In some embodiments, model names are globally unique within the system to better distinguish and query models.

[0036] According to the example implementation, the application business scope includes the approval of "flight activity application" or "takeoff application".

[0037] Furthermore, to distinguish whether a model managed by the model management module 110 can be called, the status of the model can also be set. According to the example embodiment, the status of the model that can currently be called for risk assessment is set to "in effect".

[0038] When it is necessary to create a new risk assessment model, a new risk assessment model is created based on the model management module 110, according to the model name and the scope of application business.

[0039] During the creation process, the model name and application business scope can be entered by the user or selected by the user based on the options provided on the interactive page; this application does not impose any restrictions on this.

[0040] According to the example implementation, a default risk assessment model is preset for each application service scope.

[0041] The model configuration module 120 is used to display multiple pre-set risk categories and their risk factors to the user based on the model name and application business scope, configure the newly created risk assessment model according to the user's selection and / or input, and send the configured risk assessment model to the model management module.

[0042] According to some embodiments, multiple risk categories include: At least one of the following: airspace risk, ground risk, weather risk, planning risk, operator risk, and social risk.

[0043] Based on the example implementation, the correspondence between risk categories and their risk factors is given in Table 1.

[0044] Table 1. Correspondence between risk categories and their risk factors

[0045] The model configuration module 120 is connected to the model management module 110 and is used to guide users in configuring the risk assessment model. Specifically, the configuration of the risk assessment model includes: receiving the model name and application business scope for basic model settings; displaying multiple pre-set risk categories for users to select and / or input; and displaying the risk factors under the selected risk category for users to select and / or input, thereby determining the model's hierarchy.

[0046] Furthermore, in some embodiments, the model configuration also includes: setting the weights of risk categories and risk factors, and setting risk calculation parameter values ​​for the risk factors. The weights and parameters can be input by the user or selected by the user based on options provided on the interactive page; this application does not impose any restrictions on this.

[0047] The configured model reflects user-defined risk assessment rules. These user-defined rules are packaged into an executable risk assessment algorithm model and sent to the model management module for data management, serving subsequent automated approval decisions.

[0048] This application aims to abstract low-altitude flight risk assessment into a multi-level decision-making problem, solidify users' experience and knowledge into a reusable assessment model, reduce subjective judgment differences, and make the assessment process more standardized and transparent. The newly established risk assessment model serves subsequent automated approval decisions.

[0049] The risk assessment module 130 is used to obtain the target risk assessment model selected by the user from the model management module according to the business type of the flight application to be assessed, and to conduct a risk assessment on the flight application to be assessed based on the target risk assessment model.

[0050] The risk assessment module 130 is connected to the model management module 110. During the approval process of a flight application to be assessed, users can match the corresponding application business scope model in the model management module 110 according to the business type and select one. The selected model is recorded as the target risk assessment model. The target risk assessment model is used to perform a quantitative risk assessment of the flight application to be assessed and output the results.

[0051] This application automatically calls the model for calculation during the approval process, which greatly improves the approval efficiency.

[0052] This application, through a model management module 110, allows users to freely create risk assessment models based on model name and application scope. Through a model configuration module 120, users can intuitively select multiple risk categories and their risk factors. Users can also configure risk categories and risk factors according to their needs. The configured risk assessment model is sent to the model management module 110 for management. The model management module 110 stores newly created and historically constructed risk assessment models. Through a risk assessment module 130, users can select a target risk assessment model from the models stored in the model management module 110 based on the business type of the flight application to be assessed, and perform risk assessment based on the target risk assessment model. Based on this, users can flexibly customize, deploy, and invoke risk assessment models according to actual needs, achieving highly adaptable and flexible low-altitude flight risk assessment.

[0053] According to some embodiments, the model management module 110 supports model creation, model query, model publishing, model decommissioning, model deletion, and / or model copying operations.

[0054] Depending on the requirements, the model management module 110 can provide one or more operations such as creating, querying, publishing, taking offline, deleting, and copying models.

[0055] This application's embodiments support continuous model iteration and multiple version management. Users can create and publish new models or decommission old models at any time based on changes in operational data and management policies, ensuring that risk assessment standards keep pace with the times.

[0056] According to some embodiments, the model management module 110 includes: A model repository for storing newly created risk assessment models and historically built risk assessment models.

[0057] To facilitate the data management of risk assessment models by the model management module 110, a model repository is set up to store newly created risk assessment models and historically constructed risk assessment models.

[0058] Once a new risk assessment model is configured, it can be updated directly in the model repository.

[0059] During the approval process, models can be extracted and called through the model repository.

[0060] According to some embodiments, refer to Figure 2 The model configuration module 120 includes a basic information configuration unit 210 and a risk factor configuration unit 220.

[0061] The basic information configuration unit 210 is used to configure the basic information of the newly created risk assessment model according to the model name and application business scope.

[0062] The basic information configuration unit 210 receives the model name and application service scope. Based on the received model name and application service scope, it configures the basic information of the newly created risk assessment model.

[0063] The risk factor configuration unit 220 is used to display multiple risk categories and their risk factors to the user, and to obtain the risk categories and risk factors selected and / or input by the user, as well as their corresponding weights, as the target risk categories and their category weights and target risk factors and their factor weights for the newly established risk assessment model.

[0064] The risk factor configuration unit 220 displays multiple pre-set risk categories to the user, and records the risk categories selected and / or entered by the user as target risk categories; it also displays the risk factors under the selected risk categories to the user, and records the risk factors selected and / or entered by the user as target risk factors. Simultaneously, it obtains the corresponding weights of the risk categories selected and / or entered by the user, and records them as category weights; it also obtains the corresponding weights of the risk factors selected and / or entered by the user, and records them as factor weights.

[0065] According to some embodiments, the risk factor configuration unit 220 includes a weight configuration subunit 310 and / or a parameter setting subunit 320.

[0066] The weight configuration subunit 310 is used to provide a configuration interface to obtain the first weight value configured by the user for the target risk category and the second weight value configured for the target risk factor.

[0067] The weight configuration subunit 310 provides a configuration interface (e.g., an input interface) for users to configure the first weight value of the category weight and the second weight value of the factor weight.

[0068] To facilitate user input, the first and second weight values ​​do not need to be entered / selected as percentages or decimals. Users can enter them according to their needs and then convert them to percentages or decimals accordingly to obtain the corresponding category weights and factor weights.

[0069] The parameter setting subunit 320 is used to provide a setting interface to obtain risk calculation parameter values ​​set by the user for one or more target risk factors.

[0070] The parameter setting subunit 320 provides a setting interface (such as a pop-up window) for users to set numerical parameters for specific risk factors, which are recorded as the risk calculation parameter values ​​for the corresponding risk factors.

[0071] According to the example embodiment, users can set parameters for corresponding factors in the parameter settings pop-up window of the settings interface. The input boxes in the parameter settings pop-up window are entered by default with system settings parameters, and the original settings are retained if the user does not change them.

[0072] According to the example embodiment, the risk factors for which risk calculation parameters can be configured include: airspace restrictions (configuring the minimum distance (in meters) that each type of aircraft should maintain from the controlled airspace boundary line), ground obstacles (configuring the minimum distance (in meters) that each type of aircraft should maintain from ground obstacles), densely populated areas (configuring the minimum distance (in meters) that each type of aircraft should maintain from densely populated areas), infrastructure (configuring the minimum distance (in meters) that each type of aircraft should maintain from infrastructure), and electromagnetic environment (configuring the minimum distance (in meters) that each type of aircraft should maintain from the electromagnetic environment). Secondary damage (configure the minimum distance (in meters) that each type of aircraft should maintain from each secondary damage-prone area), wind speed and force (select the maximum wind resistance capability of each type of aircraft), visibility (select the minimum visibility level required for each type of aircraft to fly), precipitation (select the maximum rainfall conditions for each type of aircraft to fly), historical weather warnings (select the weather conditions for each type of aircraft to receive warnings); flight noise (configure the minimum distance that each type of aircraft should maintain from noise-sensitive areas such as schools, hospitals, and residential areas, day and night).

[0073] In one specific embodiment, the configuration of risk calculation parameter values ​​is shown in Table 2.

[0074] Table 2 Configuration Results of Risk Calculation Parameter Values

[0075] According to the example embodiment, when the risk factor configuration unit 220 includes a weight configuration subunit 310 and a parameter setting subunit 320, the risk factor selection subunit is configured to provide a graphical interface for users to select risk categories and risk factors.

[0076] This application provides an interactive configuration platform that allows users (approvers) to intuitively construct the "skeleton" (hierarchical structure) of the assessment model and endow it with a "soul" (weights and parameters), thus achieving personalized, precise, and automated generation of risk assessment models. Through configurable risk factors, weight allocation, and parameter settings, the risk assessment model can accurately align with the management priorities of different scenarios, achieving a leap from a "one-size-fits-all" approach to "personalized customization."

[0077] According to some embodiments, the weight configuration subunit 310 is also used for: The category weights and factor weights are validated according to the preset validation logic.

[0078] The weight configuration subunit 310 also has built-in verification logic to ensure that the total weight meets the requirements.

[0079] According to some embodiments, the preset verification logic includes: the sum of the category weights of multiple risk categories is 100%; and / or the sum of the factor weights of the risk factors of the risk categories is 100%.

[0080] To facilitate subsequent conversions, category weight configuration rules and factor weight configuration rules are set so that the data in the user's input / selection boxes will conform to the configuration rules by default. The configuration rules can be adjusted according to the user's needs.

[0081] Set up preset verification logic based on the category weight configuration rules and factor weight configuration rules to verify the category weights and factor weights.

[0082] According to the example implementation, the category weight configuration rules include: the input weight must be a pure number (supporting integer and floating-point types); the weight of each selected category must be non-empty and greater than 0; the sum of the weights of each category = 100%.

[0083] According to the example implementation, the factor weight configuration rules include: the input weight must be a pure number (supporting integer and floating-point types); the weight of each selected category must be non-empty and greater than 0; the sum of the weights of all factors = 100%.

[0084] Furthermore, in some embodiments, such as Figure 3 As shown, if the first weight values ​​of multiple risk categories are configured and the preset verification logic is not met (the preset verification logic in this embodiment is that the sum of the category weights of multiple risk categories is 100%), the verification will fail. Click "Publish", and the alarm "The sum of category weights is 100%" will appear at the top of the page and disappear after a preset time (e.g., 3 seconds). The verification will then locate the corresponding category weight, and the input box will be highlighted in red for the user to modify the weight.

[0085] Similarly, in some embodiments, such as Figure 3 As shown, if the second weight value of the risk factor in the risk category is configured and the preset verification logic is not met (the preset verification logic in this embodiment is that the sum of the factor weights of the risk factors in the risk category is 100%), the verification will fail. Click "Publish", and the alarm "The sum of the weights of all factors in the same category is 100%" will be displayed at the top of the page and disappear after a preset time (e.g., 3 seconds). The verification will then locate the corresponding factor weight, and the input box will be highlighted in red for the user to modify the weight.

[0086] Furthermore, risk calculation parameter configuration rules can be set, and preset verification logic can be set according to the category weight configuration rules, factor weight configuration rules, and risk calculation parameter configuration rules to verify the category weight, factor weight, and risk calculation parameters.

[0087] The settings for risk calculation parameter configuration rules can refer to the category weight configuration rules and factor weight configuration rules, which will not be elaborated upon in this application.

[0088] According to the example implementation, the risk calculation parameter values ​​entered / selected by the user need to comply with the pre-set risk calculation parameter configuration rules (e.g., they must be pure numbers (supporting integer and floating-point types)).

[0089] According to some embodiments, refer to Figure 4 The risk factor configuration unit 220 also includes a risk weight calculator 330.

[0090] The Risk Weight Calculator 330 is used to display target risk categories and / or target risk factors. Based on the first weight value and / or the second weight value, it constructs a target risk category matrix and / or a target risk factor matrix, and calculates the category weight and / or factor weight according to the target risk category matrix and / or the target risk factor matrix.

[0091] The Risk Weight Calculator 330 displays the selected risk category (i.e., target risk category) and / or risk factor (i.e., target risk factor). During the display process, the specific content shown (i.e., target risk category, target risk factor, or both) can be selected according to the actual situation.

[0092] The embodiments of this application use a matrix approach to display the target risk categories and / or target risk factors.

[0093] Specifically, based on the selected target risk categories and their first weight values, a target risk category matrix is ​​constructed, where each element of the matrix represents the importance of each pair of target risk categories. And / or based on the selected target risk factors and their second weight values, a target risk factor matrix is ​​constructed, where each element of the matrix represents the importance of each pair of target risk factors.

[0094] The matrix size is determined based on the number of risk categories or risk factors.

[0095] Based on the displayed data, the Risk Weight Calculator 330 can calculate category weights from the target risk category matrix and factor weights from the target risk factor matrix. The resulting category weights and factor weights can be displayed in a preset format.

[0096] According to the example embodiment, the weighting results of risk category weights are displayed as percentages; the weighting results of risk factor weights are displayed as decimals.

[0097] Furthermore, in some embodiments, the configuration interface of the weight configuration subunit 310 can be displayed based on the target risk category matrix / target risk factor matrix.

[0098] Based on the above embodiments, users only need to enter the first weight value / second weight value in the multiple input boxes in the lower triangular area (or upper triangular area) of the matrix, and the system will automatically fill in the reciprocal of the symmetrical position (for example, if the user enters that A is 3 times B, then the system will automatically fill in that B is 1 / 3 times A).

[0099] According to some embodiments, the risk weight calculator 330 is also used for: Perform a consistency check on category weights and factor weights.

[0100] Based on the Risk Weight Calculator 330, the system uses the Analytic Hierarchy Process (AHP) in the background to ensure the logical consistency of weight configuration.

[0101] To provide a more detailed explanation of the risk weight calculator 330, a specific embodiment is given.

[0102] 1) During use, when a user clicks on the risk category or risk factor calculator function entry, the selected risk category matrix or risk factor item matrix will be displayed. The matrix size is based on the number of risk categories or risk factors.

[0103] 2) The first and second weight values ​​input boxes on the interface display default values. Users only need to enter values ​​in the multiple input boxes in the lower triangular area. Numeric input is supported, and the system automatically fills in the reciprocal of the symmetrical position (for example, if the user enters that A is 3 times B, then it will automatically fill in that B is 1 / 3 times A). The input boxes have format validation, allowing only the input of 1-9 and their reciprocals. The main diagonal is fixed at 1 (comparing itself to itself). The scale of the weight values ​​is explained in Table 3.

[0104] Table 3 Scale Explanation

[0105] 3) Trigger weight calculation and consistency check via button.

[0106] This embodiment uses the consistent matrix method (square root method) to calculate the weights.

[0107] In calculating weights using the consistent matrix method (square root method), the m-th power of the product of each row of the matrix is ​​first calculated to obtain an m-dimensional vector. : .

[0108] in, It is the matrix number i The unnormalized weights of the elements in the row, where j is the column label. Let be the element in the i-th row and j-th column of the matrix.

[0109] Will Standardization yields the weights of the corresponding risk categories / risk factors for that bank: .

[0110] The calculated risk category weights and risk factor weights are displayed.

[0111] In this embodiment, the weighting results of risk category weights are displayed as percentages, and the weighting results of risk factor weights are displayed as decimals.

[0112] 4) Perform a consistency check.

[0113] In this embodiment of the application, when the matrix order is less than or equal to 2, the test is passed by default; when the order is greater than 3, a test is required.

[0114] The consistency verification steps include: Construct a weight matrix based on the calculated weights, and then calculate the maximum eigenvalue of the weight matrix. .

[0115] .

[0116] in, n The number of dimensions, for example, n=5; AW This is the cumulative weight of the standardized risk category matrix / risk factor item matrix, row by row.

[0117] Based on the largest eigenvalue Calculate the consistency index (CI) and the consistency ratio (CR): ; .

[0118] RI is a random consistency index, whose value is obtained by looking up a table (as shown in Table 4) and is related to n.

[0119] Table 4 Random Consistency Index

[0120] Consistency is determined based on the consistency ratio (CR). If CR ≤ 0.1, the matrix passes the consistency check, the weights are valid, and a success message is generated (e.g., the consistency check result is passed, and the weight result can be applied); if CR > 0.1, the matrix is ​​inconsistent, and a modification message is generated to prompt the user to adjust the matrix input (e.g., the consistency check result is failed, indicating that there is a logical error in the matrix, please modify it again).

[0121] The system supports modifying the matrix and recalculating the weights until the consistency requirements are met.

[0122] 5) When the user clicks the "Apply" button, the calculated weight values ​​will be filled back into the corresponding fields of the risk configuration model template.

[0123] According to some embodiments, the risk assessment module 130 is used for: Select risk assessment models from the model management module 110 that match the business type and are currently active, as candidate risk assessment model groups.

[0124] Based on the business type, select risk assessment models that match the application business scope and are currently in effect to form a candidate risk assessment model group.

[0125] Obtain the target risk assessment model selected by the user from the candidate risk assessment model group.

[0126] Users select from a group of candidate risk assessment models, and the selected model is denoted as the target risk assessment model.

[0127] Based on the target risk assessment model, a risk assessment is performed on the flight application to be evaluated, and the risk assessment results are output.

[0128] The target risk assessment model is used to quantitatively assess the risk of the flight application to be evaluated, and the results are output and recorded as the risk assessment results.

[0129] This application solidifies the configuration results into a reusable risk assessment model, which is then invoked in the approval process to quantitatively assess the risks of flight activities or takeoff applications. This solves the technical problems of existing low-altitude risk assessment methods being rigid and unable to adapt to the dynamic management needs of different jurisdictions and business scenarios. This application comprehensively considers multi-dimensional risk factors such as environment, aircraft, and human factors, and allows for fine-tuning of key parameters, making the risk assessment results more comprehensive and accurate.

[0130] The following describes an apparatus embodiment of this application, which can be used to perform the method embodiment of this application. For details not disclosed in the apparatus embodiment of this application, please refer to the method embodiment of this application.

[0131] Figure 5 A flowchart illustrating a risk assessment method for low-altitude flight based on a risk assessment model according to an exemplary embodiment is shown.

[0132] Figure 5 The method shown can control the aforementioned risk assessment system for low-altitude flight based on a risk assessment model according to an embodiment of this application.

[0133] like Figure 5 As shown, a risk assessment method for low-altitude flight based on a risk assessment model may include steps S510-S530.

[0134] In step S510, a new risk assessment model is created based on the model name and the scope of the application business.

[0135] A new risk assessment model is created based on the model name and application scope. The model name and application scope can be input or selected by the user. For details, please refer to the aforementioned risk assessment system for low-altitude flight based on a risk assessment model according to an embodiment of this application.

[0136] According to the example implementation, users access the "Risk Assessment Configuration" function through the system's front-end interface, where the system displays a data list page by default. Users click the "Create Model" button to navigate to the configuration page. On the configuration page, users can enter or select a model name and the scope of application business to create a new risk assessment model.

[0137] In step S520, based on the model name and application business scope, multiple pre-set risk categories and their risk factors are displayed to the user, and the newly created risk assessment model is configured according to the user's selection and / or input.

[0138] The system displays multiple pre-set risk categories and specific risk factors under each category to the user; it receives selection instructions from the user among the risk categories and risk factors, and configures the newly created risk assessment model according to the selection instructions. For details, please refer to the aforementioned risk assessment system for low-altitude flight based on a risk assessment model according to an embodiment of this application.

[0139] According to the example embodiment, the risk category includes at least one of airspace risk, ground risk, weather risk, planning risk, operator risk, and social risk.

[0140] The configuration also includes category weight configuration, factor weight configuration, and risk calculation parameter configuration.

[0141] Category weight configuration includes: receiving the weight value assigned by the user to each selected risk category, and verifying that the sum of the weights of all selected risk categories is 100%.

[0142] The factor weight configuration includes: receiving the weight values ​​assigned by the user to the selected risk factors under each selected risk category, and verifying that the sum of the weights of all selected risk factors under each risk category is 100%.

[0143] The risk calculation parameter configuration includes: receiving risk calculation parameter values ​​input by the user for risk factors with preset configurable parameters.

[0144] According to the example implementation, risk factors for configurable parameters include wind speed, visibility, precipitation, ground obstacles, densely populated areas, infrastructure, and airspace restrictions.

[0145] Save the configured model information, including basic information, selected risk factors, weights of each category and factor, and risk factor parameters, to the corresponding database; and set the model status to "pending release", "in effect", or "offline".

[0146] In step S530, based on the business type of the flight application to be evaluated, the target risk assessment model selected by the user from the configured risk assessment model and the historically constructed risk assessment model is obtained, and the risk assessment of the flight application to be evaluated is performed based on the target risk assessment model.

[0147] When approving applications for drone flight activities or takeoffs (i.e., applications for flight to be evaluated), the target risk assessment model is called from both the configured risk assessment model and historically constructed risk assessment models to perform risk assessment calculations. For specific details, please refer to the aforementioned risk assessment system for low-altitude flight based on a risk assessment model according to an embodiment of this application.

[0148] According to the example implementation, a risk assessment model in an "active" state is called as the target risk assessment model from the risk assessment models configured in the database and the historically built risk assessment models.

[0149] The device performs functions similar to those described above; other functions are described in the preceding descriptions and will not be repeated here.

[0150] This application discloses an electronic device, including: a processor; and a memory storing a computer program, which, when executed by the processor, causes the processor to execute the above-described instruction generation method.

[0151] For example, refer to Figure 6 , Figure 6 The illustrated electronic device 600 includes a processor 601 and a memory 603. The processor 601 and the memory 603 are connected, for example, via a bus 602. Optionally, the electronic device 600 may also include a transceiver 604. It should be noted that in practical applications, the transceiver 604 is not limited to one type, and the structure of this electronic device 600 does not constitute a limitation on the embodiments of this application.

[0152] Processor 601 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in this application. Processor 601 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0153] Bus 602 may include a pathway for transmitting information between the aforementioned components. Bus 602 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 602 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0154] The memory 603 may be a ROM (Read Only Memory) or other type of static storage device capable of storing static information and instructions, RAM (Random Access Memory) or other type of dynamic storage device capable of storing information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other storage medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0155] The memory 603 stores application code that executes the scheme of this application, and its execution is controlled by the processor 601. The processor 601 executes the application code stored in the memory 603 to implement the content shown in the foregoing method embodiments.

[0156] Figure 6 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0157] This application discloses a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, causes the processor to execute an instruction generation method.

[0158] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0159] The above are only some embodiments of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A risk assessment system for low-altitude flight based on a risk assessment model, characterized in that, include: The model management module is used to create new risk assessment models based on model name and application business scope, and to manage newly created risk assessment models and historically built risk assessment models. The model configuration module is used to display multiple pre-set risk categories and their risk factors to the user based on the model name and the application business scope, configure the newly created risk assessment model according to the user's selection and / or input, and send the configured risk assessment model to the model management module. The risk assessment module is used to obtain the target risk assessment model selected by the user from the model management module according to the business type of the flight application to be assessed, and to conduct a risk assessment on the flight application to be assessed based on the target risk assessment model.

2. The system according to claim 1, characterized in that, The model management module supports model creation, model query, model publishing, model decommissioning, model deletion, and / or model copying.

3. The system according to claim 1, characterized in that, The model management module includes: A model repository is used to store newly created risk assessment models and historically built risk assessment models.

4. The system according to claim 1, characterized in that, The model configuration module includes: The basic information configuration unit is used to configure the basic information of the newly created risk assessment model according to the model name and the application business scope; The risk factor configuration unit is used to display the multiple risk categories and their risk factors to the user, and to obtain the risk categories and risk factors selected and / or input by the user, as well as their corresponding weights, as the target risk categories and their category weights and target risk factors and their factor weights for the newly established risk assessment model.

5. The system according to claim 4, characterized in that, The risk factor configuration unit includes: A weight configuration subunit is used to provide a configuration interface to obtain the first weight value configured by the user for the target risk category, and the second weight value configured for the target risk factor; and / or The parameter setting subunit is used to provide a setting interface to obtain the risk calculation parameter values ​​set by the user for one or more of the target risk factors.

6. The system according to claim 5, characterized in that, The weight configuration subunit is also used for: The category weights and factor weights are verified according to the preset verification logic.

7. The system according to claim 6, characterized in that, The preset verification logic includes: The sum of the category weights of the multiple risk categories is 100%; and / or The sum of the factor weights for the risk factors in the aforementioned risk category is 100%.

8. A risk assessment method for low-altitude flight based on a risk assessment model, characterized in that, include: Create a new risk assessment model based on the model name and the scope of application. Based on the model name and the application business scope, multiple pre-set risk categories and their risk factors are displayed to the user, and the newly created risk assessment model is configured according to the user's selection and / or input; Based on the business type of the flight application to be evaluated, the target risk assessment model selected by the user from the configured risk assessment model and the historically constructed risk assessment model is obtained, and the risk assessment of the flight application to be evaluated is performed based on the target risk assessment model.

9. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the method as described in claim 8.

10. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by the processor, they implement the method as described in claim 8.

Images