A flight simulation training scene generation and switching method and system

Abstract

The application relates to the technical field of flight simulation training, and discloses a flight simulation training scene generation and switching method and system, which comprises the following steps: saving an airport configuration, an airspace route, operation rules, weather, ground vehicles, aircraft operation, teaching tasks and special situation events into a scene element library; receiving training requirements and splitting the training requirements into flight stages, operation targets, communication requirements, environmental disturbances, operation conflicts and disposal requirements, and generating candidate training scenes according to the training requirements; screening and loading the training scenes according to complexity, conflict types, teaching targets and training time lengths; controlling scene keeping, loading or switching according to instructor selection, training progress, student operation results and event conditions, and mapping the training state before switching to a target training scene; recording a training process and comparing the training process with current scene rules to form a training evaluation result, and determining subsequent processing according to deviation types. The application can realize dynamic generation, continuous switching and continuous keeping of training scenes.

Description

Technical Field

[0001] This invention relates to the field of flight simulation training technology, specifically to a method and system for generating and switching flight simulation training scenarios. Background Technology

[0002] Flight simulation training typically revolves around aircraft operation, instrument status, and fixed training procedures. For complex operational scenarios such as taxiing conflicts, runway occupancy, multi-aircraft communication, ground vehicle crossings, weather changes, and go-arounds and diversions, existing training methods often rely on temporary human intervention or pre-prepared fixed scripts.

[0003] Fixed scripts can play preset events, but they have limitations in scene preparation, lesson reuse, difficulty adjustment, and process recording. If training scenes are executed only in a preset order, it is usually difficult to combine different scene elements according to airport configuration, airspace rules, training stage, difficulty level, teaching objectives, and student operation results. It is also difficult to continuously switch scenes during training based on instructor selection, training progress, student operation results, or event triggering conditions.

[0004] Furthermore, when training scenarios change, if the aircraft's position, speed, altitude, heading, communication status, scenario event status, and mission progress cannot be continuously maintained, the training process is easily interrupted when trainees face complex situation pressures and special circumstances, and training records and evaluations are also difficult to keep intact.

[0005] Therefore, this application provides a method and system for generating and switching flight simulation training scenarios to solve the above-mentioned technical problems. Summary of the Invention

[0006] The purpose of this invention is to provide a method and system for generating and switching flight simulation training scenarios, in order to solve the technical problems in the prior art where fixed scripts are difficult to combine training scenarios according to training needs, difficult to load or switch scenarios according to the training process, and difficult to continuously connect training states before and after scenario switching.

[0007] To address the aforementioned technical problems, this invention provides a method for generating and switching flight simulation training scenarios, comprising: Save airport configuration, airspace routes, operating rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events as a scene element library; The system receives training requests that include training subjects, training stages, difficulty levels, teaching objectives, and special situation triggering conditions. The training requests are then broken down into flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements. Based on the flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements, the system retrieves scene elements from the scene element library and combines them into candidate training scenes. The candidate training scenarios are selected based on complexity, conflict type, teaching objectives, and training duration, and the selected training scenarios are then loaded. Based on instructor selection, training progress, student operation results and event conditions, control the maintenance, loading or switching of training scenarios, and map the training state before switching to the target training scenario. The training process is recorded to form a training record. The training record is compared with the rules of the current scene to obtain the training evaluation result. When the trainee's operation result does not meet the rules of the current scene, a deviation record is generated and the processing result of prompting, review, or entering the next training scene is determined. When the processing result is to enter the next training scene, the next training scene is loaded or switched.

[0008] In some specific embodiments, airport configuration, airspace routes, operational rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events are saved as a scene element library, further including: Store airport configurations and airspace routes according to accessible areas, restricted areas, and route connections; The operating rules are stored according to flight phase, communication clearance, and conflict avoidance conditions; Store meteorological, ground vehicle, aircraft operations, and special events according to triggering conditions and affected objects; Establish a searchable constraint relationship between the teaching tasks and the operating rules.

[0009] In some specific embodiments, a training request is received that includes training subjects, training stages, difficulty levels, teaching objectives, and special situation triggering conditions. The training request is then broken down into flight phases, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements, further including: Extract the course types and assessment actions from the training courses; Extract the flight phase from the training phase; Select the intensity of environmental disturbance and the density of operational conflicts based on the level of difficulty. The teaching objectives are broken down into operational objectives, communication requirements, and handling requirements. Write the special case trigger conditions into the scene generation constraints.

[0010] In some specific embodiments, retrieving scene elements from the scene element library based on flight phase, operational objective, communication requirements, environmental disturbances, operational conflicts, and handling requirements, and combining them into candidate training scenes, further includes: The airport configuration and airspace route search range are defined by the flight phase described above; The operation objective and the call request are matched with the operation rules and call permission; The environmental disturbances, operational conflicts, and handling requirements are used to screen meteorological, ground vehicle, aircraft operations, and special events. The matched scene elements are combined according to time sequence and spatial location to form the candidate training scene.

[0011] In some specific embodiments, the selection of candidate training scenarios based on complexity, conflict type, teaching objectives, and training duration further includes: For each candidate training scenario, read the number of participating objects, the order of event triggering, the type of conflict, and the estimated execution time; Eliminate candidate training scenarios that do not match the teaching objectives or exceed the training duration; The remaining candidate training scenarios are arranged according to the degree of coverage of the handling requirements by the conflict type, and the filtered training scenarios are output.

[0012] In some specific embodiments, loading the filtered training scenario further includes: Read the airport configuration, airspace routes, weather, aircraft operations, ground vehicles, operating rules, and special events from the filtered training scenario; The airport configuration and the airspace routes are loaded as training space boundaries; The weather, the aircraft operation, and the ground vehicles are loaded as moving object conditions; The operating rules and special case events are loaded as event triggering conditions to obtain the current training scenario.

[0013] In some specific embodiments, the training scene is maintained, loaded, or switched based on the instructor selection, training progress, student operation results, and event conditions, and the training state before the switch is mapped to the target training scene, further including: Compare instructor selection with manual trigger conditions, training progress with stage trigger conditions, student operation results with operation trigger conditions, and event conditions with event trigger conditions. When any comparison result meets the preset switching conditions, a target training scene matching the trigger source that meets the conditions is selected from the filtered training scenes and loaded or switched to the target training scene; If none of the comparison results meet the preset switching conditions, continue executing the current training scenario; The training status includes aircraft position, speed, altitude, heading, communication status, scenario event status, and mission progress; Before loading or switching, the aircraft position, speed, altitude, heading, communication status, scene event status, and task progress of the current training scene are temporarily stored. The stored content is then written into the target training scene to obtain the current training scene with continuous status.

[0014] In some specific embodiments, the training process is recorded to form a training record. The training record is compared with the rules of the current scene to obtain a training evaluation result. When the trainee's operation result does not meet the rules of the current scene, a deviation record is generated and a processing result of prompting, review, or entering the next training scene is determined. When the processing result is to enter the next training scene, the next training scene is loaded or switched. Further, this includes: Record key events, student actions, call responses, handling times, and rule compliance; Establish a time sequence record for key events, student operations, and call responses based on the current scenario rules; The processing time and rule compliance are written into the time sequence record to form a training record; The training records are compared with the current scene rules one by one to obtain the training evaluation results; When a student's operation results do not meet the rules of the current scenario, a deviation record is generated, and the processing result of prompting, review, or entering the next training scenario is determined according to the deviation type. When the processing result is to proceed to the next training scenario, load or switch to the next training scenario.

[0015] In some specific embodiments, before loading or switching, the aircraft position, speed, altitude, heading, communication status, scene event status, and task progress of the current training scene are temporarily stored, and the temporarily stored content is written into the target training scene to obtain a current training scene with continuous state, which further includes: Establish a switching temporary queue; The aircraft's position, speed, altitude, and heading constitute the aircraft's state; the communication state includes the number of communication rounds; the scenario event state includes triggered events; and the task progress includes completed task nodes. When the preset switching conditions are met, the aircraft status, call rounds, triggered events and completed task nodes of the current training scenario are written into the switching temporary queue in chronological order. When the target training scenario contains an event node that matches the triggered event, the switching temporary queue is written to the matching event node; When the target training scene lacks an event node that matches the triggered event, an event continuation node is generated in the target training scene and the switching temporary queue is written into the event continuation node, outputting the current training scene with continuous state.

[0016] Based on the same concept, the present invention also provides a flight simulation training scenario generation and switching system, comprising: The scene element saving module is configured to save airport configuration, airspace routes, operating rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events as a scene element library; The training scenario generation module is configured to receive training requirements including training subjects, training stages, difficulty levels, teaching objectives, and special situation triggering conditions; break down the training requirements into flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements; and retrieve scenario elements from the scenario element library based on the flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements, and combine them into candidate training scenarios. The training scenario filtering and loading module is configured to filter the candidate training scenarios based on complexity, conflict type, teaching objectives, and training duration, and then load the filtered training scenarios. The training scene switching module is configured to control the maintenance, loading, or switching of the training scene based on the instructor selection, training progress, student operation results, and event conditions, and to map the training state before the switch to the target training scene. The training evaluation module is configured to record the training process to form a training record, compare the training record with the rules of the current scene to obtain the training evaluation result, and when the student's operation result does not meet the rules of the current scene, a deviation record is generated and the processing result of prompting, reviewing or entering the next training scene is determined. When the processing result is to enter the next training scene, the next training scene is loaded or switched.

[0017] Compared with existing technologies, its advantages are as follows: This invention discloses a method and system for generating and switching flight simulation training scenarios. It saves airport configuration, airspace routes, operating rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events as a scenario element library. It also breaks down training requirements into flight phases, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements. Training scenarios can be formed by combining reusable scenario elements, reducing the limitations of a single fixed script on training content.

[0018] Based on the decomposition results of training objectives, scenario elements are retrieved, and candidate training scenarios are selected according to complexity, conflict type, teaching objectives, and training duration. This allows for the formation of scenario combinations that match the teaching objectives among scenarios such as taxiing conflicts, runway occupation, multi-aircraft communication, ground vehicle crossing, weather changes, and go-around / alternate landing, ensuring that the training scenarios are consistent with the training stage, difficulty level, and handling requirements.

[0019] During the training process, the training scene can be maintained, loaded, or switched based on the instructor selection, training progress, student operation results, and event conditions. The training process can load or switch scenes according to the training progress and student response, making it suitable for building continuous and complex training processes.

[0020] When loading or switching training scenarios, the aircraft's position, speed, altitude, heading, communication status, scenario event status, and mission progress are temporarily stored and mapped. The target training scenario can inherit the training state before the switch, reducing the interruption of the training process caused by scenario switching.

[0021] The training process is recorded to form training records. These records are then compared with the rules of the current scenario to generate training evaluation results and deviation records. Based on the type of deviation, the system determines whether to provide prompts, conduct reviews, or proceed to the next training scenario, thus providing a data foundation for training evaluation, process review, and repeated training. Attached Figure Description

[0022] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is a flowchart illustrating some specific embodiments of the method for generating and switching flight simulation training scenarios according to the present invention; Figure 2 This is a schematic diagram of a flight simulation training scenario generation and switching system according to some specific embodiments of the present invention. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms "a," "the," and "the" as used in the embodiments of this application are also intended to include the plural forms, unless the context clearly indicates otherwise, and "multiple" generally includes at least two.

[0025] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0026] It should be understood that although the terms first, second, third, etc., may be used in the embodiments of this application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, first may also be referred to as second without departing from the scope of the embodiments of this application, and similarly, second may also be referred to as first.

[0027] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0028] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that an article or device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such an article or device. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the article or device that includes said element.

[0029] It should be noted that any symbols and / or numbers present in the specification that are not marked in the accompanying drawings are not reference numerals.

[0030] Reference Figure 1 A method for generating and switching flight simulation training scenarios, comprising: S101 saves airport configuration, airspace routes, operating rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events as a scene element library; S102, receive training requirements including training subjects, training stages, difficulty levels, teaching objectives and special situation triggering conditions, break down the training requirements into flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts and handling requirements, and retrieve scene elements in the scene element library according to the flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts and handling requirements and combine them into candidate training scenes. S103, Filter the candidate training scenarios according to complexity, conflict type, teaching objectives and training duration, and load the filtered training scenarios; S104 controls the maintenance, loading, or switching of the training scene based on the instructor selection, training progress, student operation results, and event conditions, and maps the training state before the switch to the target training scene. S105: Record the training process to form a training record. Compare the training record with the current scene rules to obtain the training evaluation result. When the student's operation result does not meet the current scene rules, generate a deviation record and determine the processing result of prompting, reviewing or entering the next training scene. When the processing result is to enter the next training scene, load or switch to the next training scene.

[0031] To provide a clearer explanation, the steps in the embodiments of the present invention are described in detail below: S101 saves airport configuration, airspace routes, operating rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events as a scene element library; In this embodiment, the scene element library is used to carry the basic elements required to generate training scenes. The scene element library can be pre-built or incrementally updated when training subjects are maintained, airport data is updated, operating rules are updated, or special events are added.

[0032] The airport configuration in the scenario element library can include runways, taxiways, parking stands, holding points, connecting taxiways, arrival and departure directions, and passable areas; airspace routes can include controlled area boundaries, air routes, approach paths, go-around paths, alternate landing paths, and restricted areas; operational rules can include release conditions, taxiing rules, runway occupancy rules, communication clearance rules, spacing rules, conflict avoidance rules, and special situation handling rules; weather can include visibility, wind direction and speed, cloud base height, precipitation, thunderstorms, low visibility operating conditions, and runway status; ground vehicles can include vehicle routes, vehicle occupancy areas, vehicle crossing opportunities, and vehicle avoidance rules; aircraft operations can include aircraft position, speed, altitude, heading, takeoff, approach, landing, go-around, alternate landing, taxiing, and holding status; teaching tasks can include training subjects, training phases, teaching objectives, assessment maneuvers, and communication requirements; special situation events can include runway occupancy, ground vehicle crossing, multi-aircraft communication, weather changes, go-around, alternate landing, low visibility, and runway changes.

[0033] In some embodiments, scene elements can be further organized and stored according to the target of action, so that data corresponding to airport space, airspace routes, moving objects, operating rules, teaching tasks and special events can be retrieved and combined separately.

[0034] In some specific embodiments, this step further includes: Store airport configurations and airspace routes according to accessible areas, restricted areas, and route connections; The operating rules are stored according to flight phase, communication clearance, and conflict avoidance conditions; Store meteorological, ground vehicle, aircraft operations, and special events according to triggering conditions and affected objects; Establish a searchable constraint relationship between the teaching tasks and the operating rules.

[0035] When storing airport configurations and airspace routes, airport configurations can be converted into data records composed of area objects and connection objects. Area objects record spatial extents such as runways, taxiways, parking stands, holding points, and restricted areas, while connection objects record reachability relationships, directions of travel, and entry conditions between areas. Airspace routes can be stored according to route segments, waypoints, approach segments, go-around segments, alternate landing segments, and restricted airspace boundaries.

[0036] By storing accessible areas, restricted areas, and route connections, the system can determine whether aircraft, ground vehicles, and special events in the training scenario can be configured in matching spatial locations when retrieving scenario elements later. For example, taxiing conflict training can simultaneously read taxiway connections, holding point locations, ground vehicle routes, and runway occupancy rules; go-around training can simultaneously read approach paths, go-around paths, weather conditions, and communication clearance rules.

[0037] Operating rules can be stored by flight phase, communication clearance, and conflict avoidance conditions. Flight phases can include ground taxiing, takeoff, climb, cruise, approach, landing, go-around, and diversion. Communication clearance can record the content of communications triggered by instructors or controllers in different flight phases, student response formats, permitted actions, and restricted actions. Conflict avoidance conditions can record the spatial and temporal occupancy relationships between multiple aircraft, between aircraft and vehicles, and between aircraft and runway occupants.

[0038] The operating rules can be saved in the scenario element library as searchable constraints, and can be retrieved later according to flight phase, operation objective and communication requirements. When forming training evaluation, the current scenario rules can also be used to compare the trainee operation and communication response in the training record.

[0039] Weather, ground vehicle, aircraft operations, and special events can be stored according to triggering conditions and affected objects. Triggering conditions can include training progress triggers, instructor selection triggers, student operation triggers, event time triggers, and rule violation triggers. Affected objects can include the aircraft itself, other aircraft, ground vehicles, runways, taxiways, airspace routes, communication procedures, and mission nodes.

[0040] Meteorological triggers can manifest as decreased visibility or wind direction changes after training reaches a preset stage; ground vehicle triggers can manifest as vehicles entering taxiways during the corresponding training period; aircraft operation triggers can manifest as other aircraft occupying the runway or entering the approach path; and special event triggers can manifest as go-arounds, diversions, runway changes, initiation of low visibility procedures, or conflict handling requirements. By analyzing the storage methods of triggers and affected objects, it is possible to determine whether to maintain, load, or switch training scenarios during training.

[0041] Searchable constraints can be established between teaching tasks and operational rules. Teaching tasks may include training subjects, training phases, difficulty levels, teaching objectives, and assessment actions. Searchable constraints can be implemented using key-value records, relational database tables, graph structure edge relationships, configuration file entries, or event script indexes. Constraints can record the flight phase, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements corresponding to the teaching task.

[0042] The scenario element library can be implemented using relational databases, configuration files, graph structure data, or event script sets. Relational databases are suitable for storing structured relationships between airport configurations, operating rules, and training records; configuration files are suitable for storing manually maintainable subject rules and triggering conditions; graph structure data is suitable for storing the connection relationships between airport areas, airway nodes, and event nodes; and event script sets are suitable for storing special events with a clear triggering order.

[0043] S102, receive training requirements including training subjects, training stages, difficulty levels, teaching objectives and special situation triggering conditions, break down the training requirements into flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts and handling requirements, and retrieve scene elements in the scene element library according to the flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts and handling requirements and combine them into candidate training scenes. In this embodiment, training requirements can be input by the instructor before training begins, or they can be provided by the training plan, subject configuration, or evaluation results of the previous training scenario.

[0044] Training subjects are used to define training themes, such as taxiing conflicts, runway occupancy, multi-aircraft communication, ground vehicle crossings, weather changes, go-arounds, and diversions. Training phases determine whether training occurs during taxiing, takeoff, approach, landing, go-arounds, diversions, or other flight phases. Difficulty levels determine the intensity of environmental disturbances, the number of conflicting entities, communication load, and time constraints for handling situations. Learning objectives define the operational actions, communication responses, rule compliance, and special situation handling that trainees need to complete. Special situation triggering conditions determine when events are introduced during training and what inputs can trigger scenario holding, loading, or switching.

[0045] For ease of explanation, the flight phases, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements resulting from the breakdown of training requirements will be collectively referred to as the training objective decomposition results.

[0046] In some specific embodiments, the breakdown of training requirements includes: Extract the course types and assessment actions from the training courses; Extract the flight phase from the training phase; Select the intensity of environmental disturbance and the density of operational conflicts based on the level of difficulty. The teaching objectives are broken down into operational objectives, communication requirements, and handling requirements. Write the special case trigger conditions into the scene generation constraints.

[0047] When extracting training subject types and assessment actions from training subjects, the subject type can serve as an index condition for subsequent retrieval of scenario elements, and the assessment actions can serve as a reference item for training evaluation. For example, when the subject type is runway occupancy, the assessment actions may include identifying runway occupancy, holding, performing communication confirmation, reviewing clearance, and replanning taxiing or takeoff maneuvers; when the subject type is go-around and diversion, the assessment actions may include identifying go-around conditions, performing go-around procedures, completing communication response, selecting an alternate landing path, and maintaining aircraft continuity.

[0048] When extracting flight phases from training phases, the training phases can be directly provided by the training plan or determined based on the training subjects and teaching objectives. When the training requirement includes low-visibility taxiing, the flight phase can be extracted as ground taxiing; when the training requirement includes runway changes during approach, the flight phase can be extracted as approach and landing; when the training requirement includes go-around and diversion before landing, the flight phase can be extracted as approach, go-around, and diversion. The resulting flight phases are used to subsequently limit the scope of retrieval for airport configuration, airspace routes, and operational rules.

[0049] When selecting environmental disturbance intensity and operational conflict density based on the difficulty level, environmental disturbance intensity can reflect the degree of weather changes, low visibility, crosswinds, runway status changes, or communication load changes; operational conflict density can reflect the quantity and timing of multiple aircraft, multiple vehicles, multiple communication tasks, or multiple events overlapping.

[0050] For example, the difficulty level, environmental disturbance intensity, and operational conflict density can be set to levels 1 to 5. When the difficulty level in the training requirement is level 3, medium environmental disturbance intensity and medium operational conflict density can be selected, and the corresponding results can be written into the scene generation constraints. The above values ​​are only used to illustrate one implementation method, and can be configured according to the training subject system in actual implementation.

[0051] When teaching objectives are broken down into operational objectives, communication requirements, and handling requirements, operational objectives constrain trainees' flight or ground operation actions in training scenarios; communication requirements constrain trainees' communication responses to instructors, controllers, or other simulated objects; and handling requirements constrain trainees' actions in handling special situations, operational conflicts, and environmental disturbances.

[0052] The learning objectives can be broken down into the correspondence between training target text, target keywords, rule indexes, and target entries. Target keywords can include terms such as taxiing, waiting, takeoff, landing, go-around, diversion, avoidance, communication, confirmation, and verification. The rule index is used to associate operational rules in the scene element library, and target entries are used to form operational objectives, communication requirements, and handling requirements, and can participate in subsequent scene element matching.

[0053] When special situation triggering conditions are written into scenario generation constraints, scenario generation constraints can include flight phase constraints, operational target constraints, communication requirement constraints, environmental disturbance constraints, operational conflict constraints, handling requirement constraints, and triggering condition constraints. Triggering condition constraints can record the trigger source, trigger time, trigger object, and the target scenario type after triggering.

[0054] When the training requirements do not explicitly specify special trigger conditions, preset trigger conditions can be retrieved based on the subject type and training stage. When the training requirements lack the subject type or training stage required to form a corresponding training scenario, requirement completion prompts can be output.

[0055] After completing the above training requirement decomposition, the training objective decomposition result is formed, which is used for subsequent scene element matching and candidate training scene generation.

[0056] In some embodiments, training objective decomposition results can be generated through a combination of manual selection and automatic recommendation. Instructors can first select the course type and training stage, and then receive recommendations for operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements based on the selected content. Instructors can also directly input training requirements in natural language, which are then broken down into corresponding searchable entries through keyword matching and rule indexing. Different input methods can all generate training objective decomposition results with the same structure, which are then processed in subsequent scene element matching.

[0057] In some specific embodiments, retrieving scene elements and generating candidate training scenes based on the training objective decomposition results includes: The airport configuration and airspace route search range are defined by the flight phase described above; The operation objective and the call request are matched with the operation rules and call permission; The environmental disturbances, operational conflicts, and handling requirements are used to screen meteorological, ground vehicle, aircraft operations, and special events. The matched scene elements are combined according to time sequence and spatial location to form the candidate training scene.

[0058] When limiting the search scope of airport configuration and airspace routes by flight phase, if the flight phase is ground taxiing, the search scope can be limited to parking positions, taxiways, holding points, runway thresholds, ground vehicle routes, and ground operating rules; if the flight phase is takeoff, the search scope can be limited to runways, departure routes, takeoff clearance, runway occupancy status, and takeoff abort conditions; if the flight phase is approach or landing, the search scope can be limited to approach paths, runway status, landing clearance, low visibility operating conditions, and go-around conditions; if the flight phase is go-around or diversion, the search scope can be limited to go-around routes, diversion routes, diversion airports, or diversion airspace rules.

[0059] When matching operational objectives and call requests with operational rules and call authorization, matching can be performed based on operational actions, authorization conditions, restrictions, and conflict avoidance conditions. For example, if the operational objective is taxiing and waiting, taxi authorization, waiting point rules, and vehicle avoidance rules can be matched; if the operational objective is a go-around, go-around calls, go-around paths, and altitude or heading maintenance rules after the go-around can be matched; if the operational objective is an alternate landing, alternate landing calls, alternate landing path selection, and next scenario loading rules can be matched. Call requests and call authorization can be matched based on the relationship between the call trigger time, the call recipient, the response content, and the operational actions.

[0060] When screening meteorological, ground vehicle, aircraft operation, and special events based on environmental disturbances, operational conflicts, and handling requirements, environmental disturbances can correspond to meteorological conditions such as low visibility, crosswinds, precipitation, and changes in runway status; operational conflicts can correspond to ground vehicle crossings, multi-aircraft communications, runway occupancy, en-route conflicts, and holding point conflicts; and handling requirements can correspond to actions such as verification, holding, avoidance, go-around, diversion, re-communication, or entering the next training scenario.

[0061] When filtering scene elements, you can first match based on the affected objects, then determine the event sequence based on the triggering conditions, and retain events that can form a complete training chain according to the handling requirements. When a certain type of handling requirement does not match a corresponding event, a candidate insufficient marker can be generated, and the corresponding candidate training scene can be processed in the subsequent candidate training scene filtering process.

[0062] The matched scene elements are combined according to time sequence and spatial location to form candidate training scenes. Candidate training scenes may include spatial configuration, operation rule configuration, weather configuration, moving object configuration, event trigger configuration, call configuration, and evaluation rule configuration.

[0063] Spatial configuration can be derived from airport configuration and airspace routes; operational rule configuration can be derived from operational rules and communication authorization; meteorological configuration can be derived from meteorological elements corresponding to environmental disturbances; moving object configuration can be derived from ground vehicle and aircraft operations; event triggering configuration can be derived from special situation events; evaluation rule configuration can be determined according to teaching tasks and handling requirements. Spatial location is used to limit whether an event can occur under corresponding spatial relationships, temporal sequence is used to limit the order of event triggering, and operational rules are used to determine the operation, communication, and handling requirements in the training scenario.

[0064] Candidate training scenarios can be generated using rule combinations, template combinations, constraint solving, or a combination of manual selection and automatic recommendation. Rule combinations are suitable for directly matching scenario elements based on flight phase, operational objectives, and operational conflicts; template combinations are suitable for saving common subjects as reusable scenario skeletons, and then replacing weather, vehicles, or events based on difficulty level and triggering conditions; constraint solving is suitable for forming scenario combinations that satisfy constraints among multiple conflict objects, training duration, and handling requirements; when combining manual selection and automatic recommendation, instructors can first lock in some scenario elements and then supplement other scenario elements.

[0065] S103, Filter the candidate training scenarios according to complexity, conflict type, teaching objectives and training duration, and load the filtered training scenarios; In this embodiment, candidate training scenarios may include different combinations of scenarios such as ground taxiing conflict scenarios, runway occupation scenarios, multi-aircraft communication scenarios, low visibility approach scenarios, go-around and diversion scenarios, and runway change scenarios.

[0066] By screening candidate training scenarios based on complexity, conflict type, teaching objectives, and training duration, the training scenarios entering the training environment can correspond to the training needs and can be executed within the corresponding training period.

[0067] In some specific embodiments, the screening of candidate training scenarios includes: For each candidate training scenario, read the number of participating objects, the order of event triggering, the type of conflict, and the estimated execution time; Eliminate candidate training scenarios that do not match the teaching objectives or exceed the training duration; The remaining candidate training scenarios are arranged according to the degree of coverage of the handling requirements by the conflict type, and the filtered training scenarios are output.

[0068] The number of participating entities can include the number of the aircraft itself, other aircraft, ground vehicles, communication partners, and event participants. The event triggering sequence can include the arrangement of events at nodes such as training start, taxiing, holding, release, approach, landing, go-around, and diversion. Conflict types can include runway occupancy conflicts, taxiway path conflicts, ground vehicle conflicts, multi-aircraft communication conflicts, weather disturbance conflicts, and special situation handling conflicts.

[0069] The estimated execution time can be determined based on the flight phase, number of events, number of call rounds, and number of actions to be taken in the scenario. For example, the estimated duration of each event and the estimated response time of each call can be calculated, and the estimated execution time of the candidate training scenario can be determined based on the cumulative results of the corresponding times.

[0070] Mismatched teaching objectives can include situations such as candidate training scenarios not including target operations, missing target call requirements, mismatch between conflict types and handling requirements, or special events not covering training needs. Exceeding training time can include the estimated execution time exceeding the available time in the training requirements, or the event triggering sequence preventing key assessment actions from occurring within the available time. For removed candidate training scenarios, the reasons for removal can be recorded for review of scenario configuration.

[0071] When arranging the remaining candidate training scenarios according to the coverage of the conflict type with the handling requirements, the coverage can be determined based on the coverage ratio of handling requirements, the matching ratio of key handling requirements, the matching ratio of conflict types, and the suitability of training duration.

[0072] Among them, the handling requirement coverage ratio is used to indicate the proportion of the number of handling requirements that have been covered by the candidate training scenario to the total number of handling requirements; the key handling requirement matching ratio is used to indicate the proportion of the number of key handling requirements that have been matched to the total number of key handling requirements; the conflict type matching ratio is used to indicate the proportion of the number of conflict types that have been matched by the candidate training scenario to the number of target conflict types; and the training duration adaptation degree is used to indicate the adaptation between the expected execution time and the training time.

[0073] For example, the coverage ratio of handling requirements, the matching ratio of key handling requirements, the matching ratio of conflict types, and the training duration adaptation can be weighted with weights of 0.4, 0.3, 0.2, and 0.1 respectively, and the sum of the weighted results can be used as the scenario ranking value. When the expected execution time does not exceed the training time, the training duration adaptation can be set to 1; when the expected execution time exceeds the training time, the training duration adaptation can be set to 0. The above weights are only used to illustrate one feasible ranking method, and can be configured according to the training subjects in actual implementation.

[0074] After sorting, you can choose the training scene with the higher sort value as the initial loading scene, or you can retain multiple training scenes with higher sort values ​​as subsequent switching candidates.

[0075] In some specific embodiments, sorting the remaining candidate training scenarios may further include: Establish a conflict resolution matching table that matches the types of operational conflicts with their resolution requirements; Match and label the order of conflict occurrence, call requirements, and handling actions in the remaining candidate training scenarios; When the same candidate training scenario lacks a target action in the handling requirements, a special case event matching the target action is added from the scenario element library or conflicting elements in the same candidate training scenario are deleted, and the filtered training scenario after matching correction is output.

[0076] The conflict resolution matching table can establish a correspondence between runway occupancy conflicts and holding, call confirmation and clearance review; between ground vehicle crossing conflicts and deceleration, holding and avoidance; between multi-aircraft call conflicts and call identification, call sequencing and clearance rephrase; and between low-visibility operation conflicts and instrument checks, speed control and approach review.

[0077] When matching and marking the order of conflict occurrence, call requirements, and handling actions in the remaining candidate training scenarios, the matching marks can include covered, partially covered, uncovered, and conflict overload.

[0078] When the target action is missing, if there is a special event in the scene element library that matches the target action, the special event can be added, and the scene combination can be re-formed according to the time sequence and spatial location. When the added event causes the training time to exceed the limit or there is an incompatible relationship between conflicting objects, conflicting elements with low relevance to the teaching objective in the same candidate training scene can be deleted, and the filtered training scene after matching correction can be output.

[0079] In some specific embodiments, the loaded, filtered training scenarios include: Read the airport configuration, airspace routes, weather, aircraft operations, ground vehicles, operating rules, and special events from the filtered training scenario; The airport configuration and the airspace routes are loaded as training space boundaries; The weather, the aircraft operation, and the ground vehicles are loaded as moving object conditions; The operating rules and special case events are loaded as event triggering conditions to obtain the current training scenario.

[0080] When reading the filtered training scenarios, spatial elements can be read first, followed by moving object elements, and then rule and event elements. Airport configuration and airspace routes are used to form the training space boundary; meteorology, aircraft operations, and ground vehicles are used to form the training environment and moving object conditions; operating rules and special events are used to form event triggering conditions and evaluation criteria.

[0081] When a necessary scene element is missing, it can be replaced by reading similar elements from other candidate training scenes; when all similar elements are missing, a loading failure record can be generated and a new filtered training scene can be selected.

[0082] Training space boundaries can include accessible ground areas, restricted areas, runway occupancy areas, holding points, taxiways, approach paths, go-around paths, and alternate landing paths. Airport configurations and airspace routes can be converted into visible areas, accessible paths, restricted boundaries, and triggering areas in the training environment.

[0083] The conditions of the moving object can include the aircraft's initial position, speed, altitude, heading, vehicle path, vehicle speed, the timing of weather changes, and the range of weather effects.

[0084] After loading the operating rules and special case events as event triggering conditions, the current training scenario is obtained. Event triggering conditions can include triggering relationships with instructor selection, training progress, student operation results, and event conditions.

[0085] In some specific embodiments, pre-load verification can also be performed on the selected training scenarios. Pre-load verification can check whether the spatial boundaries are closed, whether the initial position of the moving object is located in a passable area, whether the event triggering conditions have a triggering time point, whether the running rules correspond to the evaluation rules, and whether the training duration meets the requirements.

[0086] If the pre-load validation passes, the filtered training scene will be loaded as the current training scene; if the pre-load validation fails, the remaining candidate training scenes can be rearranged, or the missing elements can be replaced and added before validation again.

[0087] S104 controls the maintenance, loading, or switching of the training scene based on the instructor selection, training progress, student operation results, and event conditions, and maps the training state before the switch to the target training scene. In this embodiment, the instructor selection, training progress, student operation results, and event conditions are read during the execution of the current training scenario.

[0088] Instructor selection can include instructors actively choosing to switch scenarios, insert special events, reduce or increase difficulty, trigger review, or enter the next training scenario. Training progress can include the current training stage, completed task nodes, triggered events, remaining training time, and current call round. Trainee operation results can include flight operations, taxiing operations, call responses, review actions, waiting actions, go-around actions, diversion actions, and conflict handling actions. Event conditions can include weather changes, runway occupancy, ground vehicles crossing, multi-aircraft communication, other aircraft occupying the flight path, or trainee operations deviating from the current scenario rules.

[0089] The preset switching conditions can be determined based on special circumstances triggering conditions, event triggering conditions in the current training scenario, and current scenario rules.

[0090] In some specific embodiments, this step further includes: Compare instructor selection with manual trigger conditions, training progress with stage trigger conditions, student operation results with operation trigger conditions, and event conditions with event trigger conditions. When any comparison result meets the preset switching conditions, a target training scene matching the trigger source that meets the conditions is selected from the filtered training scenes and loaded or switched to the target training scene; If none of the comparison results meet the preset switching conditions, continue executing the current training scenario; The training status includes aircraft position, speed, altitude, heading, communication status, scenario event status, and mission progress; Before loading or switching, temporarily store the aircraft position, speed, altitude, heading, communication status, scene event status, and task progress of the current training scenario; The temporary content is written into the target training scenario to obtain the current training scenario with continuous state.

[0091] When performing comparisons for different trigger sources, the instructor can select and compare manual trigger conditions by reading the scene selection, special case selection, or difficulty adjustment selection in the instructor interface and matching them with the manual trigger conditions allowed in the current training scenario.

[0092] The comparison between training progress and stage trigger conditions can read the current flight stage, mission progress nodes, completed actions and remaining training time, and determine whether the stage conditions for switching to the next training scenario have been met.

[0093] By comparing the student's operation results with the operation trigger conditions, the system can read the student's operation actions, call responses, and handling actions, and determine whether the operation results meet the corresponding prompts, verification, or training scenario switching conditions.

[0094] The comparison between event conditions and event triggering conditions can read weather changes that have occurred or are about to occur, runway occupancy, vehicle crossing, multi-aircraft communication and operational conflicts, and determine whether the corresponding events meet the conditions for loading or switching the target training scenario.

[0095] When any comparison result meets the preset switching conditions, select the target training scene that matches the trigger source that meets the conditions from the filtered training scenes and load or switch to the target training scene.

[0096] When the trigger source is instructor selection, the target training scenario can be determined based on the instructor selection result; when the trigger source is training progress, the target training scenario can be determined based on the training scenario corresponding to the next training stage; when the trigger source is student operation result, the target training scenario can be determined based on deviation type, handling requirements, and review requirements; when the trigger source is event condition, the target training scenario can be determined based on special event type, affected object, and handling requirements.

[0097] When selecting a target training scene, prioritize those that are ranked higher and match the trigger source. If no matching scene is found among the selected training scenes, candidate training scenes can be recombined, or scene elements that can be added can be retrieved from the scene element library to form the target training scene.

[0098] If none of the comparison results meet the preset switching conditions, the current training scenario continues to be executed. The processing results of continuing to execute the current training scenario can record the current training scenario identifier, the current flight stage, the source of no trigger, the next comparison time, and the current task progress, and enter the subsequent execution loop of the current training scenario, so that the training environment continues to execute according to the already loaded airport configuration, airspace routes, weather, aircraft operations, ground vehicles, operating rules, and special events.

[0099] When the current training scenario is completed and no scenario switching conditions are generated, the execution completion result can be included in the training process recording and evaluation processing.

[0100] In some embodiments, different trigger priorities can be set. For example, the instructor can select a trigger priority higher than the event condition trigger, the event condition trigger priority can be higher than the training progress trigger, and the training progress trigger priority can be higher than the student operation result trigger; alternatively, the corresponding event condition can be set to the highest priority according to the training subject configuration.

[0101] When multiple comparison results simultaneously meet the preset switching conditions, the target training scenario can be selected based on the trigger priority, and the unselected trigger sources can be written into the pending trigger record. The pending trigger record can continue to participate in subsequent training scenario switching judgments after the target training scenario has been loaded.

[0102] You can also set switching cooldown conditions and repeated trigger filtering conditions. Switching cooldown conditions can be used to reduce the situation where the same trigger source repeatedly triggers scene switching within a short period of time. Repeated trigger filtering conditions can read the trigger source, target training scene, and event node of the most recent switch.

[0103] If the current trigger is the same as the most recent switch record and the task progress has not changed, the current training scenario continues to be executed; if the current trigger corresponds to a new task node or a new event condition, the target training scenario can be reselected.

[0104] In other implementations, training scene switching can also be triggered by timed events, events, instructor actions, or student actions. Different triggering methods are all used to establish conditions for maintaining, loading, or switching scenes during training.

[0105] Before the switch, the aircraft's position, speed, altitude, heading, communication status, scenario event status, and mission progress together constitute the training status.

[0106] Aircraft position can include ground position, runway position, route position, approach path position, or go-around path position; speed, altitude, and heading are used to describe the aircraft's motion status; communication status can include the current communication partner, communication round, clearance issued, completed response, and communication pending review; scenario event status can include triggered events, untriggered events, events in progress, completed events, and suspended events; mission progress can include completed mission nodes, current mission nodes, pending mission nodes, and evaluation nodes.

[0107] After determining the target training scenario, training state mapping can be performed. After the initial training scenario is loaded, corresponding state initialization can also be performed based on the initial training state.

[0108] Before loading or switching, temporarily save the aircraft position, speed, altitude, heading, communication status, scene event status, and task progress of the current training scenario.

[0109] The temporarily stored aircraft position can be represented by coordinates, airport area identifiers, route node identifiers, or runway / taxiway positions in the training environment; the temporarily stored speed, altitude, and heading can be represented by state variables in the training environment; the temporarily stored communication status can include the communication recipient, communication content identifier, clearance status, response status, and review status; the temporarily stored scenario event status can include the event identifier, event trigger time, affected objects, event completion status, and remaining actions of the event; the temporarily stored task progress can include the training phase, task nodes, completed actions, incomplete actions, and evaluation nodes.

[0110] During temporary storage, a timestamp or sequence number can be added to each type of state to restore the temporal relationship when writing to the target training scenario.

[0111] After writing the temporary content to the target training scenario, a current training scenario with continuous state is obtained. During the writing process, aircraft position, speed, altitude, and heading can be written to ensure that the aircraft's motion state in the target training scenario is consistent with the training state before the switch; communication state can be written to ensure that the communication rounds, permission states, and response states in the target training scenario continue; scenario event states can be written to ensure that triggered, executing, and completed events obtain matching nodes in the target training scenario; and task progress can be written to ensure that the current task node in the target training scenario is connected with the training state before the switch.

[0112] When the spatial boundary of the target training scene does not match the aircraft position before the switch, a passable area in the target training scene that is adjacent to the position before the switch and meets the operating rules can be selected as the mapping position, and the position mapping result can be recorded.

[0113] When the target training scenario lacks a matching call node or event node, a call continuation node or event continuation node can be generated, and the corresponding temporary content can be written to the corresponding node.

[0114] In some specific embodiments, the state storage and writing process further includes: Establish a switching temporary queue; The aircraft's position, speed, altitude, and heading constitute the aircraft's state; the communication state includes the number of communication rounds; the scenario event state includes triggered events; and the task progress includes completed task nodes. When the preset switching conditions are met, the aircraft status, call rounds, triggered events and completed task nodes of the current training scenario are written into the switching temporary queue in chronological order. When the target training scenario contains an event node that matches the triggered event, the switching temporary queue is written to the matching event node; When the target training scene lacks an event node that matches the triggered event, an event continuation node is generated in the target training scene and the switching temporary queue is written into the event continuation node, outputting the current training scene with continuous state.

[0115] The switching queue can use a first-in, first-out (FIFO) queue structure or an ordered set of timestamped records. Record fields in the switching queue can include aircraft status, call round number, triggered event, completed task node, and write target node.

[0116] The aircraft's position, speed, altitude, and heading can be categorized into the aircraft status field; the call recipient, call content, and response status can be categorized into the call round field; the event identifier, trigger time, and affected objects can be categorized into the triggered event field; and the training phase, assessment actions, and completion results can be categorized into the completed task node field.

[0117] When the target training scenario contains matching event nodes, the event status, call status, and task progress in the switching queue can be written to the matching event nodes, allowing the target training scenario to continue execution from the node connected to the triggered event.

[0118] When the target training scene lacks matching event nodes, an event continuation node can be generated based on the affected objects, trigger times, and task progress of the triggered events. Then, the switching temporary queue is written into the event continuation node, so that the target training scene can take over the events that have occurred and the task nodes that have been completed before the switch.

[0119] In some embodiments, state consistency checks can also be performed. State consistency checks may include spatial consistency checks, motion consistency checks, call consistency checks, event consistency checks, and task progress consistency checks.

[0120] Spatial consistency check is used to determine whether the aircraft's position is within the allowed spatial boundaries of the target training scenario; motion consistency check is used to determine whether the speed, altitude, and heading meet the operating rules of the target training scenario; call consistency check is used to determine whether the call status can access the call permission of the target training scenario; event consistency check is used to determine whether the triggered event has a receiving node in the target training scenario; task progress consistency check is used to determine whether the completed task node can enter the next task node of the target training scenario.

[0121] After the state consistency check passes, the current training scenario with continuous state continues to accept instructor selection, training progress, student operation results and event conditions, and enters the training process recording.

[0122] If the state consistency check fails, a check failure record can be generated, and the mapping position can be corrected, a call continuation node can be added, an event continuation node can be added, or a new target training scenario can be selected based on the failure type.

[0123] S105: Record the training process to form a training record. Compare the training record with the current scene rules to obtain the training evaluation result. When the student's operation result does not meet the current scene rules, generate a deviation record and determine the processing result of prompting, reviewing or entering the next training scene. When the processing result is to enter the next training scene, load or switch to the next training scene.

[0124] In this embodiment, the training process is recorded during the execution of the current training scenario, and a phased training record can also be formed when the scenario ends, the scenario switches, or a review is triggered.

[0125] Key events can include scene loading, scene switching, runway occupancy, vehicle crossing, weather changes, communication clearance, multi-aircraft communication, go-around, diversion, runway change, and rule violation events.

[0126] Trainee operations can include control inputs, speed control, heading control, altitude control, taxiing and holding, go-around maneuvers, emergency landing maneuvers, and conflict handling maneuvers.

[0127] Call responses can include the student's responses to instructions for permission, warning, review, waiting, and special circumstances.

[0128] The processing time can include the time from the time the event is triggered to the time the student begins to process the event, the time from the time the event is triggered to the time the student completes the processing, and the time from the time the call request is made to the time the student completes the response.

[0129] Rule compliance can include judgment results such as whether the operation action conforms to the current scenario rules, whether the call response conforms to the call permission, whether the processing time meets the preset time conditions, and whether the task node is completed.

[0130] In some specific embodiments, this step further includes: Record key events, student actions, call responses, handling times, and rule compliance; Establish a time sequence record for key events, student operations, and call responses based on the current scenario rules; The processing time and rule compliance are written into the time sequence record to form a training record; The training records are compared with the current scene rules one by one to obtain the training evaluation results; When a student's operation results do not meet the rules of the current scenario, a deviation record is generated, and the processing result of prompting, review, or entering the next training scenario is determined according to the deviation type. When the processing result is to proceed to the next training scenario, load or switch to the next training scenario.

[0131] When establishing a time sequence record for key events, student operations, and call responses based on the current scenario rules, the sorting criteria can be the training start time, scenario loading time, event trigger time, operation occurrence time, and call response time.

[0132] Record fields may include scene identifier, event identifier, event type, affected object, student operation type, student operation content, call object, call content, permission status, task node, and recording time.

[0133] The current scenario rules are used to define the events, operations, and call responses that need to be recorded. For example, the runway occupancy scenario can record runway occupancy events, waiting actions, call confirmations, and clearance verifications; the ground vehicle crossing scenario can record vehicle entry time, aircraft position, deceleration or waiting actions, and avoidance completion status; and the go-around and diversion scenario can record go-around triggering, go-around communication, aircraft status, and diversion route selection.

[0134] The processing time and rule compliance are recorded in a time sequence to form a training record. The processing time can be determined based on the time difference between the time the student completes the operation and the time the corresponding event is triggered; the call response time can be determined based on the time difference between the time the student completes the call response and the time the call request occurs.

[0135] Rule compliance can be recorded item by item based on the current scenario rules, indicating compliance, non-compliance, or requiring review. For processing times that require numerical judgment, corresponding thresholds can be set.

[0136] For example, the call response time threshold can be set to 8 seconds, and the handling time threshold can be set to 15 seconds. When the call request occurs at 00:03:20 and the student completes the call response at 00:03:26, the call response time is 6 seconds, which is less than 8 seconds, and the call response time item is recorded as compliant. When the special event trigger time is 00:05:10 and the student completes the handling at 00:05:30, the handling time is 20 seconds, which is greater than 15 seconds, and the handling time item is recorded as non-compliant. The above values ​​are used to illustrate one implementation method, and the actual thresholds can be configured according to the training subject.

[0137] The training evaluation results are obtained by comparing the training records with the rules of the current scenario item by item. Item-by-item comparison can include comparison of operation actions, call response, processing time, task nodes, and rule compliance.

[0138] Operational action comparison is used to determine whether the trainee has performed the actions required by the rules of the current scenario; call response comparison is used to determine whether the trainee's call content matches the call permission, repetition requirements, or review requirements; handling time comparison is used to determine whether the trainee's handling meets the preset time conditions; task node comparison is used to determine whether the training phase and assessment actions are completed as required; rule compliance comparison is used to summarize various compliance or non-compliance records.

[0139] Training evaluation results can include scenario identifiers, completed task nodes, incomplete task nodes, items that comply with the rules, items that do not comply with the rules, items requiring review, and suggestions for the next steps. Training evaluation results can be provided to instructors for review and can also be used to determine subsequent training scenario handling.

[0140] When a student's operation results do not meet the rules of the current scenario, a deviation record is generated, and the processing result of prompting, review, or entering the next training scenario is determined according to the deviation type.

[0141] Deviation types can include operational deviations, call deviations, time deviations, path deviations, rule deviations, and handling deviations. Deviation records can include deviation type, time of occurrence, affected object, current scenario rules, student operation result, comparison result, and suggested handling.

[0142] When the deviation type is suitable for immediate correction, the processing result of the prompt can be determined; when the deviation type requires instructor judgment, the processing result of review can be determined; when the deviation type corresponds to supplementary training, reinforcement training, or the next training phase, the processing result of entering the next training scenario can be determined.

[0143] When the processing result is to enter the next training scenario, load or switch to the next training scenario so that the subsequent processing results formed by the training evaluation continue to affect the flight simulation training scenario.

[0144] In other implementations, training evaluation can employ rule-based scoring, manual review, or a combination of both. Each evaluation method can generate corresponding training evaluation results based on key events recorded during the training process, student actions, call responses, handling times, and rule compliance.

[0145] In some embodiments, a runtime log can also be set. The runtime log can be generated during scene loading, scene switching, event triggering, state mapping, and evaluation output.

[0146] The fields of the operation record may include training requirement identifier, training target decomposition result identifier, candidate training scenario identifier, filtered training scenario identifier, target training scenario identifier, switching trigger source, aircraft status summary, call status summary, event status summary, task progress summary, training evaluation result, and deviation record.

[0147] The execution log can be saved as structured text, database records, or training environment logs. By reading the execution log, the processes of scene element library establishment, training requirement decomposition, candidate training scene generation, filtering and loading, scene preservation or switching, state mapping, and training evaluation can be reviewed. The training log can also be reused in subsequent training to form new training requirements or the next training scene.

[0148] The following description, using specific examples, elaborates on this embodiment.

[0149] For example, the training requirement is "runway occupation occurs in low visibility during the approach phase, and trainees are required to perform a go-around and communication verification", with a difficulty level of 3. The teaching objectives include identifying runway occupation, completing communication response, performing go-around maneuvers, and entering the alternate landing path.

[0150] The scene element library already stores airport runways, approach paths, go-around paths, low visibility weather, runway occupancy events of other aircraft, go-around call authorization, diversion paths, and evaluation rules.

[0151] After receiving the above training requirements, the training subjects and assessment actions corresponding to runway occupation and go-around / alternate landing are extracted from the training subjects. The flight phase "approach" is extracted from the training phase. The corresponding environmental disturbance intensity and operational conflict density are selected according to the three-level difficulty level. The teaching objectives are decomposed into the operational objective "execute go-around and maintain heading and altitude constraints", the communication requirement "reiterate go-around permission and confirm runway occupation information", and the handling requirements "identify occupation, stop landing, enter the go-around path and prepare for alternate landing".

[0152] Based on the "approach" phase of flight, the search scope is limited to approach paths, runways, go-around paths, and alternate landing paths; based on operational objectives and communication requirements, go-around operation rules, runway occupancy rules, and go-around communication authorization are matched; based on environmental disturbances, operational conflicts, and handling requirements, low visibility weather, runway occupancy aircraft events, and go-around and alternate landing events are screened.

[0153] The matched scene elements are combined into candidate training scenarios according to time sequence and spatial location. For example, after the training starts, the approach path is entered, low visibility weather is triggered at 00:04:00, runway occupation is triggered at 00:05:10, and after the runway occupation is triggered, the trainee waits for a call response and a go-around maneuver.

[0154] When screening this candidate training scenario, the participants included two aircraft. The event triggering order was low visibility event before runway occupation event. The conflict types included runway occupation conflict and call verification conflict. The estimated execution time was 12 minutes, and the training time was 15 minutes. Therefore, this candidate training scenario was not eliminated due to the training time.

[0155] The total number of handling requirements is 4, and the candidate training scenarios cover 4. The total number of critical handling requirements is 2, and the candidate training scenarios cover 2. The number of target conflict types is 2, and the candidate training scenarios match 2. Meanwhile, the expected execution time does not exceed the training time.

[0156] When weighted according to the following weights: coverage ratio of handling requirements (0.4), matching ratio of key handling requirements (0.3), matching ratio of conflict type (0.2), and training duration adaptation (0.1), all ratios and the training duration adaptation are 1, resulting in a scenario ranking value of 1. This candidate training scenario is then output as the filtered training scenario and loaded as the current training scenario.

[0157] During training, the system continuously reads the instructor selection, training progress, student operation results, and event conditions. When the training progress reaches the approach node and the event conditions indicate that the runway is occupied by other aircraft, if the comparison result between the event conditions and the event triggering conditions meets the preset switching conditions, the system selects the go-around and diversion target training scenario from the filtered training scenarios and loads or switches to that target training scenario.

[0158] Before loading or switching, temporarily store the aircraft position, speed, altitude, heading, communication status, scenario event status, and mission progress of the current training scenario. For example, the aircraft position is approach path node approach point 3, the speed is 140kt, the altitude is 500ft, the heading is in the runway direction, the communication status is waiting for go-around clearance, the scenario event status is that the runway occupancy event has been triggered, and the mission progress is that the approach check has been completed but the landing has not been completed.

[0159] The switching queue saves the above states in chronological order. When the target training scenario includes runway occupancy event nodes and go-around path nodes, the switching queue is written to the matching event nodes of the target training scenario, so that the loaded or switched target training scenario becomes the current training scenario with continuous state.

[0160] Record runway occupancy events, student go-around maneuvers, communication responses, handling times, and rule compliance in the current training scenario.

[0161] When the call request occurs at 00:05:10 and the student completes the call response at 00:05:16, the call response time is 6 seconds; when the go-around event is triggered at 00:05:10 and the student completes the go-around action at 00:05:28, the processing time is 18 seconds.

[0162] When the current scenario rules set the call response time threshold to 8 seconds and the go-around handling time threshold to 20 seconds, both the call response time and go-around handling time items are recorded as compliant. The training evaluation results can record information such as runway occupancy identification completed, call verification completed, go-around action executed, and entry into the alternate landing path.

[0163] When a trainee fails to repeat the go-around permission, a call deviation record can be generated, and the processing result for review can be determined based on the deviation type. When a trainee fails to perform the go-around action and needs to enter supplementary or intensive training, an operation deviation record can be generated, and the processing result for entering the next training scenario can be determined. Based on the processing result, the trainee can be loaded or switched to the corresponding next training scenario.

[0164] For the purpose of simplicity, the method steps disclosed in the above embodiments are described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0165] like Figure 2 As shown, the present invention also provides a flight simulation training scenario generation and switching system, comprising: The scene element storage module 201 is configured to save airport configuration, airspace routes, operating rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events as a scene element library; The training scenario generation module 202 is configured to receive training requirements including training subjects, training stages, difficulty levels, teaching objectives, and special situation triggering conditions, break down the training requirements into flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements, and retrieve scenario elements in the scenario element library based on the flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements and combine them into candidate training scenarios. The training scenario filtering and loading module 203 is configured to filter the candidate training scenarios based on complexity, conflict type, teaching objective, and training duration, and load the filtered training scenarios. The training scene switching module 204 is configured to control the maintenance, loading or switching of the training scene based on the instructor selection, training progress, student operation results and event conditions, and to map the training state before the switch to the target training scene. The training evaluation module 205 is configured to record the training process to form a training record, compare the training record with the current scene rules to obtain the training evaluation result, and when the student's operation result does not meet the current scene rules, generate a deviation record and determine the processing result of prompting, reviewing or entering the next training scene. When the processing result is to enter the next training scene, load or switch to the next training scene.

[0166] It is worth noting that although only some basic functional modules are disclosed in the embodiments of this invention, it does not mean that the composition of this system is limited to the above-mentioned basic functional modules. On the contrary, based on the above-mentioned basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with existing technology to form an infinite number of embodiments or technical solutions. That is to say, this system is open rather than closed. The fact that this embodiment only discloses a few basic functional modules should not be considered as the scope of protection of this invention being limited to the disclosed basic functional modules. At the same time, for the convenience of description, the above devices are described separately according to their functions as various units and modules. Of course, in implementing this invention, the functions of each unit and module can be implemented in one or more software and / or hardware.

[0167] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for generating and switching flight simulation training scenarios, characterized in that, include: Save airport configuration, airspace routes, operating rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events as a scene element library; The system receives training requests that include training subjects, training stages, difficulty levels, teaching objectives, and special situation triggering conditions. The training requests are then broken down into flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements. Based on the flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements, the system retrieves scene elements from the scene element library and combines them into candidate training scenes. The candidate training scenarios are selected based on complexity, conflict type, teaching objectives, and training duration, and the selected training scenarios are then loaded. Based on instructor selection, training progress, student operation results and event conditions, control the maintenance, loading or switching of training scenarios, and map the training state before switching to the target training scenario. The training process is recorded to form a training record. The training record is compared with the rules of the current scene to obtain the training evaluation result. When the trainee's operation result does not meet the rules of the current scene, a deviation record is generated and the processing result of prompting, review, or entering the next training scene is determined. When the processing result is to enter the next training scene, the next training scene is loaded or switched. The process includes state consistency checks, which encompass spatial consistency checks, motion consistency checks, communication consistency checks, event consistency checks, and task progress consistency checks. Spatial consistency checks determine whether the aircraft's position is within the permitted spatial boundaries of the target training scenario. Motion consistency checks determine whether the speed, altitude, and heading meet the operational rules of the target training scenario. Communication consistency checks determine whether the communication status is authorized to access the target training scenario. Event consistency checks determine whether triggered events have a successor node in the target training scenario. Task progress consistency checks determine whether completed task nodes can proceed to the next task node in the target training scenario. When a state consistency check fails, a failure record is generated, and the mapping position is corrected, a communication continuation node is added, an event continuation node is added, or a new target training scenario is selected based on the failure type.

2. The method for generating and switching flight simulation training scenarios according to claim 1, characterized in that, The airport configuration, airspace routes, operational rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events are saved as a scene element library, further including: Store airport configurations and airspace routes according to accessible areas, restricted areas, and route connections; The operating rules are stored according to flight phase, communication clearance, and conflict avoidance conditions; Store meteorological, ground vehicle, aircraft operations, and special events according to triggering conditions and affected objects; Establish a searchable constraint relationship between the teaching tasks and the operating rules.

3. The method for generating and switching flight simulation training scenarios according to claim 1, characterized in that, The system receives training requests that include training subjects, training phases, difficulty levels, teaching objectives, and special situation triggering conditions. These training requests are then broken down into flight phases, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements, further including: Extract the course types and assessment actions from the training courses; Extract the flight phase from the training phase; Select the intensity of environmental disturbance and the density of operational conflicts based on the level of difficulty. The teaching objectives are broken down into operational objectives, communication requirements, and handling requirements. Write the special case trigger conditions into the scene generation constraints.

4. The method for generating and switching flight simulation training scenarios according to claim 1, characterized in that, Based on flight phase, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements, scenario elements in the scenario element library are retrieved and combined into candidate training scenarios, further including: The airport configuration and airspace route search range are defined by the flight phase described above; The operation objective and the call request are matched with the operation rules and call permission; The environmental disturbances, operational conflicts, and handling requirements are used to screen meteorological, ground vehicle, aircraft operations, and special events. The matched scene elements are combined according to time sequence and spatial location to form the candidate training scene.

5. The method for generating and switching flight simulation training scenarios according to claim 1, characterized in that, The candidate training scenarios are selected based on complexity, conflict type, teaching objectives, and training duration, and further include: For each candidate training scenario, read the number of participating objects, the order of event triggering, the type of conflict, and the estimated execution time; Eliminate candidate training scenarios that do not match the teaching objectives or exceed the training duration; The remaining candidate training scenarios are arranged according to the degree of coverage of the handling requirements by the conflict type, and the filtered training scenarios are output.

6. The method for generating and switching flight simulation training scenarios according to claim 1, characterized in that, Loading the filtered training scenarios further includes: Read the airport configuration, airspace routes, weather, aircraft operations, ground vehicles, operating rules, and special events from the filtered training scenario; The airport configuration and the airspace routes are loaded as training space boundaries; The weather, the aircraft operation, and the ground vehicles are loaded as moving object conditions; The operating rules and special case events are loaded as event triggering conditions to obtain the current training scenario.

7. The method for generating and switching flight simulation training scenarios according to claim 1, characterized in that, The training scene is maintained, loaded, or switched based on instructor selection, training progress, student operation results, and event conditions, and the training state before the switch is mapped to the target training scene. Further, this includes: Compare instructor selection with manual trigger conditions, training progress with stage trigger conditions, student operation results with operation trigger conditions, and event conditions with event trigger conditions. When any comparison result meets the preset switching conditions, a target training scene matching the trigger source that meets the conditions is selected from the filtered training scenes and loaded or switched to the target training scene; If none of the comparison results meet the preset switching conditions, continue executing the current training scenario; The training status includes aircraft position, speed, altitude, heading, communication status, scenario event status, and mission progress; Before loading or switching, the aircraft position, speed, altitude, heading, communication status, scene event status, and task progress of the current training scene are temporarily stored. The stored content is then written into the target training scene to obtain the current training scene with continuous status.

8. The method for generating and switching flight simulation training scenarios according to claim 1, characterized in that, The training process is recorded to form a training record. The training record is compared with the rules of the current scenario to obtain the training evaluation result. When the trainee's operation result does not meet the rules of the current scenario, a deviation record is generated and the processing result of prompting, review, or entering the next training scenario is determined. When the processing result is to enter the next training scenario, the next training scenario is loaded or switched. This further includes: Record key events, student actions, call responses, handling times, and rule compliance; Establish a time sequence record for key events, student operations, and call responses based on the current scenario rules; The processing time and rule compliance are written into the time sequence record to form a training record; The training records are compared with the current scene rules one by one to obtain the training evaluation results; When a student's operation results do not meet the rules of the current scenario, a deviation record is generated, and the processing result of prompting, review, or entering the next training scenario is determined according to the deviation type. When the processing result is to proceed to the next training scenario, load or switch to the next training scenario.

9. The method for generating and switching flight simulation training scenarios according to claim 7, characterized in that, Before loading or switching, the aircraft position, speed, altitude, heading, communication status, scene event status, and task progress of the current training scene are temporarily stored. The stored content is then written into the target training scene to obtain a current training scene with continuous state, which further includes: Establish a switching temporary queue; The aircraft's position, speed, altitude, and heading constitute the aircraft's state; the communication state includes the number of communication rounds; the scenario event state includes triggered events; and the task progress includes completed task nodes. When the preset switching conditions are met, the aircraft status, call rounds, triggered events and completed task nodes of the current training scenario are written into the switching temporary queue in chronological order. When the target training scenario contains an event node that matches the triggered event, the switching temporary queue is written to the matching event node; When the target training scene lacks an event node that matches the triggered event, an event continuation node is generated in the target training scene and the switching temporary queue is written into the event continuation node, outputting the current training scene with continuous state.

10. A flight simulation training scenario generation and switching system, characterized in that, include: The scene element saving module is configured to save airport configuration, airspace routes, operating rules, weather, ground vehicles, aircraft operations, teaching tasks, and special events as a scene element library; The training scenario generation module is configured to receive training requirements including training subjects, training stages, difficulty levels, teaching objectives, and special situation triggering conditions; break down the training requirements into flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements; and retrieve scenario elements from the scenario element library based on the flight stages, operational objectives, communication requirements, environmental disturbances, operational conflicts, and handling requirements, and combine them into candidate training scenarios. The training scenario filtering and loading module is configured to filter the candidate training scenarios based on complexity, conflict type, teaching objectives, and training duration, and then load the filtered training scenarios. The training scene switching module is configured to control the maintenance, loading, or switching of the training scene based on the instructor selection, training progress, student operation results, and event conditions, and to map the training state before the switch to the target training scene. The training evaluation module is configured to record the training process to form a training record, compare the training record with the current scene rules to obtain the training evaluation result, and when the student's operation result does not meet the current scene rules, a deviation record is generated and the processing result of prompting, reviewing or entering the next training scene is determined. When the processing result is to enter the next training scene, the next training scene is loaded or switched. The process includes state consistency checks, which encompass spatial consistency checks, motion consistency checks, communication consistency checks, event consistency checks, and task progress consistency checks. Spatial consistency checks determine whether the aircraft's position is within the permitted spatial boundaries of the target training scenario. Motion consistency checks determine whether the speed, altitude, and heading meet the operational rules of the target training scenario. Communication consistency checks determine whether the communication status is authorized to access the target training scenario. Event consistency checks determine whether triggered events have a successor node in the target training scenario. Task progress consistency checks determine whether completed task nodes can proceed to the next task node in the target training scenario. When a state consistency check fails, a failure record is generated, and the mapping position is corrected, a communication continuation node is added, an event continuation node is added, or a new target training scenario is selected based on the failure type.

Images