Simulation scenario generation method for ship surface aviation guarantee task scheme evaluation
By using XML Schema and mission parser to describe and parse the aircraft aviation assurance mission scheme on the ship surface, generate simulation concept files, solving the problem that it is difficult to provide a comprehensive simulation deduction environment in the existing technology, achieving efficient and accurate simulation evaluation, and improving aviation assurance efficiency.
Patent Information
- Application Number
- CN202411969673.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-30
- Publication Date
- 2025-05-06
AI Technical Summary
The existing technology is difficult to provide a comprehensive, standard, and simulation deduction environment for ship-surface aviation assurance mission scheduling schemes, especially in complex maritime ship-surface environments.
Using XML Schema as the definite description language, a ship-side aviation support task plan is used to specifically describe the ship-side aviation support task plan to form a ship-side aviation support task plan, and a task parser is used to parse the Gantt chart-formation task plan into XML format, initialize the definite information and environmental information, generate a simulation definite file, and perform simulation deduction and evaluation.
The comprehensive, standard and practical simulation deduction environment generation of the ship-side aviation support task scheduling plan is achieved, the efficiency and accuracy of the simulation method is improved, the actual training cost is reduced, and the aviation support efficiency is improved.
Smart Images

Figure CN119941060A_ABST
Abstract
Description
Technical Field
[0001] The invention relates to the technical field of marine deck aviation support training, testing and evaluation simulation, and in particular to a simulation scenario generation method for evaluating a deck aviation support mission plan. Background Art
[0002] The simulation scenario method for evaluating the shipboard aviation support mission plan is a simulation of the actual combat training system. Corresponding to the military scenario, the concept of simulation scenario is proposed. Military scenarios are mainly used by military personnel to imagine and assume the situation of combat and military exercises in the form of scenario documents. Simulation scenarios require the initialization data required by the simulation system and the setting data of some events during the simulation operation. The analysis and design of simulation scenarios refers to determining the description content and description method of simulation scenarios.
[0003] XML is an extensible markup language that can be used to mark data and define data types. It is a source language that allows users to define their own markup languages. XML is a standard general-purpose markup language with good scalability, separation of content and form, and strict grammatical requirements. XML's custom description method facilitates data exchange between different fields, different platforms, and different systems. It has a good hierarchy and tree structure, and can clearly express the logical and hierarchical relationship of the hypothetical content. Compared with the XML language, the use of XML Schema for hypothetical description can flexibly implement the tagging and constraints of hypothetical content, effectively describe complex hypothetical content and organization, and can be parsed by XML parser. XML Schema has strong scalability, can support more data types, and can be constrained in a more standardized manner.
[0004] Carrier-based aircraft are the main source of surface ship combat capability and an important means of gaining control of the sea and the air. However, due to the complex physical structure of the surface ship deck, aviation support operation scheduling has become a key technology for realizing carrier-based aircraft combat capability and an important factor in measuring carrier-based aircraft combat capability. At present, there are endless plans for aviation support operation scheduling. How to simulate and deduce the scheduling plan and give a correct evaluation is a huge challenge currently facing carrier-based aircraft operations. The present invention is a simulation scenario generation method for evaluating the scheduling plan of shipboard aviation support tasks, which aims to provide a comprehensive, standard, and real-life simulation scenario generation for the evaluation of the scheduling plan of shipboard aviation support tasks.
[0005] In general, the shipboard aviation support is quite different from the existing combat scenarios in terms of training environment, training entities, etc. The existing scenario descriptions lack a specific description of the aviation support system scenario elements and the input analysis of the tested scheduling plan. In order to solve the above problems, this patent proposes a simulation scenario generation method for shipboard aviation support mission plan evaluation. Summary of the invention
[0006] The purpose of the present invention is to provide a simulation scenario generation method for evaluating shipboard aviation support mission plans to solve the problems raised in the above-mentioned background technology.
[0007] To achieve the above object, the present invention provides the following technical solution: a simulation scenario generation method for evaluating a shipboard aviation support mission plan, comprising the following steps:
[0008] S1, based on XML Schema markup language, specifically describe the assumption elements involved in the simulation and deduction of the shipboard aviation support mission plan evaluation, and form a shipboard aviation support assumption generation information database;
[0009] S2, the shipboard aviation support task plan is a Gantt chart generated by the scheduling algorithm. The scheduling task plan is used as an evaluation object, input into the task parser, and output as a scheduling task plan in XML format, which is saved as scheduling task scenario information in the shipboard aviation support scenario generation information library;
[0010] S3, based on the shipboard aviation support scenario generation information database, initialize the scenario information, including scenario background, scenario description, shipboard environment, weather conditions, sea conditions, scheduling task plan, and the initial position and status of each entity, and generate a simulation scenario file;
[0011] S4, establish a ship deck aviation support system model, initialize the assumption information based on the ship deck aviation support assumption generation information library in the computer simulation environment, and input the parsed scheduling task plan, simulate the actual ship deck aviation support system through computer models and algorithms, and each entity performs ship deck aviation support simulation deduction according to the scheduling plan, outputs corresponding data information, and evaluates the input scheduling task plan based on the simulation results and the data information obtained by deduction, so as to realize the evaluation of the ship deck aviation support task plan.
[0012] Preferably, the step S1 includes setting up a scenario information base; using Altova XMLSpy to describe the scenario elements of the shipboard aviation support, wherein the scenario elements include entity elements, mission elements, and environment elements;
[0013] The hypothetical description of the entity element includes information: basic attributes, spatial attributes, and state attributes; the basic attributes provide overall data of the entity, the spatial attributes describe the spatial position of the entity in the simulation environment; and the state attributes characterize the characteristics presented by the entity;
[0014] The scenario description of the task element includes information: number of entities, entity number, task name, task number, start time of each task, end time of each task, and duration of each task;
[0015] The hypothetical description of the environmental elements includes information: ship surface environment, weather conditions, and sea state levels.
[0016] Preferably, the hypothetical elements of the deck aviation support include: physical elements including ships, decks, catapults, tractors, elevators, arresting cables, carrier-based aircraft, and weapons;
[0017] The basic attributes include the type, length, width, height, etc. of each entity, and each element of the basic attribute is defined as a sub-element of the basic attribute;
[0018] The spatial attribute includes location information of the entity, which is described as longitude, latitude, altitude, etc. of the location, and each element of the spatial attribute is defined as a sub-element of the spatial attribute;
[0019] The state attributes include mounts, weapons, fuel, engines, etc., and each element of the state attribute is defined as a sub-element of the state attribute;
[0020] The ship deck environment includes a take-off area, a docking area, a landing area and an island area;
[0021] The weather conditions include temperature, air pressure, sky cloudiness, precipitation, wind speed and wind direction information;
[0022] The sea condition level is divided into 10 levels: 0-9 according to the sea surface conditions within the field of vision, the shape of the wave crest and its degree of breaking, and the amount of wave foam.
[0023] Preferably, S2 includes completing the parsing of the input task plan, inputting the task plan in the form of a Gantt chart, and extracting information including the number of carrier-based aircraft, the type of carrier-based aircraft, the carrier-based aircraft number, the task number, the task name, the task start time, the task end time, the task duration, etc. from the task plan through a task parser; and parsing the extracted information into a document in XML format, and storing it in the task scenario of the scenario generation information.
[0024] Preferably, S3 initializes assumption information based on S1 and S2;
[0025] The method for initializing the scenario background and the scenario description includes: parsing the corresponding part of the XML Schema scenario markup language file, loading the scenario background and the scenario description, the scenario background is what kind of task is performed for what event, and the scenario description includes background time, duration, and scenario goal, and the goal is to describe the effect to be achieved through this task;
[0026] The method for initializing the deck environment, weather conditions, and sea state information of the deck aviation support includes: parsing the corresponding part of the XMLSchema assumption markup language, loading and initializing, loading different deck environments according to the flight deck type; displaying different weather conditions according to temperature, air pressure, sky cloudiness, precipitation, wind speed and wind direction; and loading the sea state level of the marine environment in real time according to the size of wind and waves;
[0027] The method for initializing the scheduling task plan includes: parsing the corresponding part of the task element of the XML Schema scenario markup language file, and selecting which scheduling task plan to simulate and deduce according to which the shipboard aviation support is based;
[0028] The method for initializing the position, state and other information of each entity includes: parsing the corresponding part of the XML Schema assumption markup language file, loading entity parameters, including initial state value, mount, weapon, fuel volume, etc., controlling the entity position information through longitude and latitude, etc.
[0029] Preferably, S4 follows the scheduling task plan in S2 and the initialization assumption information of S3, on the simulation platform of the shipboard aviation support system, with entities as carriers, and each entity performs corresponding tasks according to the scheduling plan, completes the shipboard aviation support simulation and generates corresponding data, and evaluates the input scheduling task plan based on the simulation results and the simulation data.
[0030] Compared with the prior art, the present invention has the following beneficial effects:
[0031] 1. The present invention adopts XML Schema as the scenario description language. XML Schema uses XML syntax to define Schema elements, achieving consistency from the inside out, and can flexibly implement the marking and constraints of the scenario content, effectively describe complex content and organization, and has strong extensibility. In addition, XML parsers can also be used to parse XMLSchema. XML Schema supports comprehensive namespaces, can support more data types, and can constrain in a more standardized manner. The present invention summarizes and analyzes the various component elements of the shipboard aviation support simulation scenario based on the XML Schema scenario markup language, and performs a relatively complete scenario description for the simulation of the shipboard aviation support mission plan evaluation. The scenario description can be expanded according to demand; the existing scenario descriptions currently lack a specific description of the aviation support scenario elements, and the present invention supplements this, making the simulation scenario under the shipboard environment more comprehensive, standardized, and closer to reality;
[0032] 2. The present invention introduces a task parser, which can realize the input of aviation support task scheduling plans in complex shipboard environments. Since there are many plans for scheduling carrier-based aircraft aviation support operations, the task parser can be used to input different shipboard aviation support task scheduling plans. By simulating and deducing different shipboard aviation support task scheduling plans, different task plans can be evaluated and the optimal task execution strategy can be obtained. The task parser is a key part of the input of the entire shipboard aviation support task plan simulation assumption method, which improves the efficiency of the simulation assumption method.
[0033] 3. The present invention provides a simulation scenario generation method for evaluating the shipboard aviation support task plan, which provides a comprehensive, standard, and practical simulation scenario generation environment for evaluating the shipboard aviation support task scheduling plan. In view of the complex marine shipboard environment, different physical equipment, environmental conditions, support conditions, etc. are generated, and the input multiple aviation support task scheduling plans are analyzed, and simulation scenario deduction and evaluation are performed on them, so as to realize the evaluation of multiple aviation support scheduling plans in a complex environment, so that the operation scheduling tasks in the marine shipboard environment are more standardized and hierarchical, reducing the actual training cost, and comprehensively improving the efficiency of shipboard aviation support. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Figure 1 A flow chart of a simulation scenario development method in an embodiment of the present invention;
[0035] Figure 2 is an XML Schema structure diagram of a physical carrier-based aircraft in an embodiment of the present invention;
[0036] Figure 3 is a flowchart of a task parser in an embodiment of the present invention;
[0037] Figure 4 This is an example diagram of a task parser in an embodiment of the present invention, divided into Figure (a) and Figure (b). DETAILED DESCRIPTION
[0038] In order to make the technical means, creative features, objectives and effects achieved by the present invention easy to understand, the present invention is further explained below in conjunction with specific implementation methods.
[0039] In the description of the present invention, it should be noted that the terms "upper", "lower", "inner", "outer", "front end", "rear end", "two ends", "one end", "the other end" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance.
[0040] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "provided with", "connected", etc. should be understood in a broad sense. For example, "connected" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.
[0041] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0042] See also Figure 1The present invention provides a simulation scenario generation method for evaluating the task plan of shipboard aviation support. The core of the method is scenario generation and task parser, wherein the scenario elements are specifically described based on the XML Schema scenario markup language, including entity scenario, environment scenario and task scenario, which provides a relatively complete scenario description for shipboard aviation support and is the basis of the entire simulation scenario method; the simulation scenario includes the scenario of the simulation environment and the input of the measured scheduling task, and the scheduling task plan is in the form of a Gantt chart, which is input into the task parser and outputs the task plan in XML format, and the task parser can input and parse a variety of carrier-based aircraft aviation support scheduling task plans; a series of initialization scenario generation is performed for the scenario generation information and the output information of the task parser, including scenario background, environmental information, the position and status of each entity, etc.; after the scenario is generated, the simulation scenario deduction is performed, and the input task plan is evaluated according to the deduction result, so as to provide a comprehensive, standard and practical simulation scenario generation environment for the evaluation of the scheduling plan of the shipboard aviation support task.
[0043] The present invention is implemented comprising the following steps:
[0044] Step 1: Based on the XML Schema markup language, describe the assumption elements of the shipboard aviation support in detail;
[0045] Step 1.1: Set the entity element;
[0046] The scenario description of entity elements includes information: basic attributes, spatial attributes, and state attributes; basic attributes provide overall data of the entity, spatial attributes describe the spatial position of the entity in the simulation environment; state attributes represent the characteristics presented by the entity; hierarchical attributes of entity elements are written in XML Schema markup language and stored in the entity scenario element of the scenario element;
[0047] Physical elements include carrier-based aircraft, ships, decks, tractors, elevators, catapults, arresting cables, and weapons;
[0048] See also Figure 2, the sub-elements of the basic attributes of carrier-based aircraft in the entity element include: category, type, number, length, height, wingspan, aircraft size, empty weight, maximum weight, maximum load weight, average climb rate, instantaneous climb rate, take-off distance, and landing distance; the spatial attributes include longitude, latitude, and altitude; the sub-elements of state attributes include sensors, aircraft mounts, aircraft-mountable weapons, propulsion system, performance indicators, and fuel; the sub-elements of sensors include model and maximum distance; the sub-elements of aircraft mounts include mount name, combat radius, and sortie preparation time; the sub-elements of aircraft-mountable weapons include name, speed requirements for carrier-based aircraft for weapon launch, and height requirements for carrier-based aircraft for weapon launch; the sub-elements of propulsion system include engine, type, and maximum cruising speed; the sub-elements of performance indicators include fuel consumption in four modes: low speed, cruise, full speed, and maximum speed; the sub-elements of fuel include type and quantity;
[0049] The sub-elements of the basic attributes of the ship in the entity element include: type, length, width, height, draft, empty displacement, standard displacement, full load displacement, maximum sea state, damage point, defense capability, hangar volume, maximum recovery capability; the spatial attributes include longitude and latitude; the sub-elements of the state attributes include: propulsion system, performance index, fuel; the sub-elements of the propulsion system include engine, type, maximum sailing speed; the sub-elements of the performance index include fuel consumption in four modes: low speed, cruising, full speed and maximum speed; the sub-elements of fuel include type and quantity;
[0050] The sub-elements of the basic attributes of the deck in the entity element include: type, length, width, area, maximum number of aircraft deployed, and maximum impact load; the spatial attributes include longitude and latitude;
[0051] The sub-elements of the basic attributes of the tractor in the entity element include: type, number, quantity, size, traction method, turning radius; the spatial attributes include longitude and latitude;
[0052] The sub-elements of the basic attributes of the elevator in the entity element include: length, width, capacity, quantity, maximum transport weight, and lifting cycle; the spatial attributes include longitude and latitude;
[0053] The sub-elements of the basic attributes of the catapult in the entity element include: type, quantity, number, and ejection cycle; the sub-elements of the ejection cycle include preparation time, ejection take-off time, and reset time; the spatial attributes include longitude and latitude;
[0054] The sub-elements of the basic attributes of the arresting cable in the entity element include: number, quantity, interval, maximum bearing tension, maximum number of uses, and arresting cycle; the spatial attributes include longitude and latitude; the sub-elements of the state attribute include the number of interceptions;
[0055] The sub-elements of the basic attributes of weapons in the entity element include type, number, length, width, diameter, weight, warhead weight, climb rate, launch altitude, launch speed, target altitude, target speed, range, and effective attack targets; the sub-elements of range include air targets, surface targets, ground targets, and underwater targets; spatial attributes include longitude, latitude, and altitude.
[0056] Step 1.2: Set up task elements;
[0057] The hierarchical attributes of the task element are written in XML markup language and stored in the task scenario element of the scenario element; the sub-elements of the task element include: entity quantity, entity number, task name, task number, task start time, task end time, and task duration;
[0058] Step 1.3: Set up environmental elements;
[0059] The hierarchical attributes of the environment element are written in XML Schema markup language and stored in the environment scenario element of the scenario element;
[0060] The sub-elements of the ship surface environment in the environmental element include: take-off area, landing area, parking area and island area; the basic attributes of the three areas of take-off area, landing area and island area include length, width and area, the sub-elements of the parking area include left parking area and right parking area, and the sub-elements of the parking areas on both sides include length, width and the number of aircraft that can be parked; the spatial attributes include longitude and latitude;
[0061] The sub-elements of weather conditions in the environmental element include: temperature, air pressure, sky cloud cover, precipitation, wind speed, and wind direction; among which, the temperature range is -50° to 50°, the air pressure range is 950hPa-1050hPa, the sky cloud cover level is divided into five levels: clear, few clouds, cloudy, overcast, and foggy; the precipitation level is divided into five levels: no rain, light rain, moderate rain, heavy rain, and rainstorm; the wind speed level is divided into thirteen levels: no wind, soft wind, light wind, breeze, gentle breeze, light wind, strong wind, gust, gale, gale, storm, and hurricane; the wind direction is divided into eight directions: due north, due south, due east, due west, northeast, northwest, southeast, and southwest;
[0062] The sea condition level in the environmental elements is divided into 10 levels according to the sea surface conditions within the field of vision, the shape of the wave crest and its degree of rupture, and the amount of wave spray and foam: Level 0: no waves, Level 1: light waves, Level 2: small waves, Level 3: light waves, Level 4: medium waves, Level 5: big waves, Level 6: huge waves, Level 7: raging waves, Level 8: raging waves, and Level 9: furious waves.
[0063] Step 2: The deck aviation support task plan is a Gantt chart generated by the scheduling algorithm. The scheduling task plan is used as an evaluation object, input into the task parser, and output as a scheduling task plan in XML format, which is saved in the deck aviation support scenario generation information library as scheduling task scenario information.
[0064] Input the mission plan in the form of a Gantt chart, and extract information including the number of carrier-based aircraft, the type of carrier-based aircraft, the number of carrier-based aircraft, the mission number of each carrier-based aircraft, the mission start time, the mission end time, the mission duration, etc. through the mission parser; and convert the extracted information into a document in XML format and store it in the mission scenario element of the scenario element;
[0065] See also Figure 3 , Figure 3 It is a flowchart of the task parser, which parses the Gantt chart of the carrier-based aircraft aviation support scheduling plan into a document in XML format. The method flow includes the following steps:
[0066] The first step is information extraction: extract all carrier-based aircraft information and task information from the Gantt chart of the task plan; extract the number of each carrier-based aircraft, the number of each carrier-based aircraft, the number of task plans, the task number, the task start time, the task end time, the task duration, etc. by parsing the row objects, row numbers, column objects, column numbers, image blocks of each row, etc. of the Gantt chart;
[0067] According to the extracted information, the models, numbers, and quantities of each carrier-based aircraft, as well as the number, number, and corresponding content of each task are counted; the main tasks of the shipboard aviation support include carrier-based aircraft dispatch, carrier-based aircraft takeoff and landing, carrier-based aircraft support and maintenance, and carrier-based aircraft resource allocation; the support tasks of carrier-based aircraft mainly include pre-flight inspection, charging, fault inspection and maintenance, mounting ammunition, and replenishing gas, liquids, and fuel, etc.;
[0068] Step 2: Information analysis: Based on the information obtained from the first step, refer to Figure 3 The flowchart of the task parser numbers the carrier aircraft and tasks respectively. If the carrier aircraft No. i matches the task No. j, the task plan is claimed, and the start time, end time and duration of the task are obtained, and recorded and written in the XML document; if there is no match, it continues to pair with the next task until each carrier aircraft corresponds to each task, and the tasks of each carrier aircraft are listed in chronological order. After the XML document is completed, the loop ends and the document is saved. (This step is an innovation)
[0069] The third step is to write an XML document: Write an XML document for the mission information corresponding to the carrier-based aircraft parsed in the second step. The corresponding XML document has hierarchical attributes, including the mission plan name, information of each carrier-based aircraft, and the number of carrier-based aircraft; the sub-elements of each carrier-based aircraft information include the mission number, mission start time, mission end time, and mission duration;
[0070] Step 4: Document saving: Name the generated XML document and save it in the task scenario element of the initialization scenario element.
[0071] To explain the task parser more clearly, Figure 4 This is a task parser example diagram. For further explanation of the task parser using a simple example, please refer to Figure 4 , this example parses the carrier-based aircraft scheduling plan in the form of a Gantt chart into an XML format document; Figure (a) is a Gantt chart of a high-intensity task plan for carrier-based aircraft. As can be seen from the figure, the horizontal axis is the time axis, the time t ranges from 0 to 1080, and the task is performed for 18 hours every day. The vertical axis is the carrier-based aircraft number, and the carrier-based aircraft number is 1-42 from top to bottom. The task number is 1-6, which are task 1 (red) catapult takeoff, task 2 (green) flight, task 3 (blue) Marshall waiting route, task 4 (yellow) arrested landing, task 5 (pink) maintenance / shutdown, and task 6 (cyan) support station / refueling. The task start time, task end time, and task duration of each carrier-based aircraft can be clearly obtained from the figure; pass it through After parsing by the task parser, an XML document as shown in Figure (b) can be obtained, which has good hierarchy. The sub-elements of the output task plan include the number of carrier-based aircraft 42 and the carrier-based aircraft numbers 1-42. The sub-elements of the carrier-based aircraft numbers include the task number, task start time, task end time, and task duration. As can be seen from Figure (a), the first task number of carrier-based aircraft 1, carrier-based aircraft 2, and carrier-based aircraft 3 is 1, the start time of task 1 is 0, the end time is 10, and the duration is 10; the first task number of carrier-based aircraft 4 is 5, the start time of task 5 is 0, the end time is 12, and the duration is 12. Therefore, this example converts a Gantt chart of a high-intensity carrier-based aircraft task plan into a document in XML format.
[0072] Step 3: Initialize the scenario information and generate the simulation scenario file;
[0073] Step 3.1: Initialize scenario background and scenario description;
[0074] The method for initializing the scenario background and scenario description includes: parsing the corresponding part of the XML Schema scenario markup language file, loading the scenario background and scenario description, the scenario background is what kind of task is performed for what event, the scenario description includes background time, duration, and scenario goal, and the goal is to describe the effect to be achieved through this task.
[0075] Step 3.2: Initialize environment information;
[0076] The method for initializing the deck environment, weather conditions, and sea state information of the deck aviation support includes: parsing the corresponding part of the XML Schema assumption markup language, loading the initialization, loading different deck environments according to the deck type, including the basic attributes and spatial attributes of the four areas of the take-off area, landing area, parking area, and island area; displaying different weather conditions according to temperature, air pressure, sky cloud cover, precipitation, wind speed, and wind direction; and loading the sea state level of the marine environment in real time according to the size of wind and waves.
[0077] Step 3.3: Initialize entity information;
[0078] The method of initializing the position, state and other information of each entity includes: parsing the corresponding part of the XML Schema assumption markup language file, loading entity parameters, including initial state value, mount, weapon, fuel volume, etc., controlling the entity position information through longitude and latitude, etc.
[0079] Step 4: Perform simulation and evaluation of the shipboard aviation support mission plan.
[0080] In the computer simulation environment of the shipboard aviation support system, based on steps 2 and 3, the assumption information is initialized and the parsed mission plan information is input. With the entity as the carrier, the scheduling task operation is performed according to the action information at each moment, and the shipboard aviation support simulation assumption deduction is carried out. The scheduling task plan is evaluated according to the output data information, and the simulation assumption deduction and evaluation of the shipboard aviation support mission plan are realized.
[0081] The above describes the specific operation and main features of the present invention. Based on the XML Schems scenario markup language, the scenario description information of the shipboard aviation support is improved and enriched, the content and rule system of the aviation support scenario are clearly expressed, and it can be supplemented and expanded according to specific needs; a task parser is set to parse the input scheduling task plan into an XML document and store it in the task scenario element; for the complex marine shipboard environment, different physical equipment, environmental conditions, support conditions, etc. are generated by assumption, and a variety of shipboard aviation support task scheduling plans are input for simulation assumption deduction and evaluation, providing a comprehensive, standard, and real-life simulation deduction environment scenario generation for the evaluation of shipboard aviation support task scheduling plans, making the training tasks in the marine shipboard environment more standardized and hierarchical, making the training more orderly and more practical, reducing the cost required for actual training, and comprehensively improving the efficiency of aviation support.
[0082] The above is only an embodiment of the present invention, and the common sense such as the known specific structure and characteristics in the scheme is not described in detail here. For those skilled in the art, it is obvious that the present invention is not limited to the details of the above exemplary embodiments, and the present invention can be implemented in other specific forms without departing from the spirit or basic characteristics of the present invention. Therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-restrictive, and the scope of the present invention is defined by the attached claims rather than the above description, so it is intended to include all changes within the meaning and scope of the equivalent elements of the claims. Any figure mark in the claims should not be regarded as limiting the claims involved.
Claims
1. A simulation scenario generation method for evaluating shipboard aviation support mission plans, characterized by , including the following steps: S1, based on XML Schema markup language, specifically describe the assumption elements involved in the simulation and deduction of the shipboard aviation support mission plan evaluation, and form a shipboard aviation support assumption generation information database; S2, the shipboard aviation support task plan is a Gantt chart generated by the scheduling algorithm. The scheduling task plan is used as an evaluation object, input into the task parser, and output as a scheduling task plan in XML format, which is saved as scheduling task scenario information in the shipboard aviation support scenario generation information library; S3, based on the shipboard aviation support scenario generation information database, initialize the scenario information, including scenario background, scenario description, shipboard environment, weather conditions, sea conditions, scheduling task plan, and the initial position and status of each entity, and generate a simulation scenario file; S4, establish a ship deck aviation support system model, initialize the assumption information based on the ship deck aviation support assumption generation information library in the computer simulation environment, and input the parsed scheduling task plan, simulate the actual ship deck aviation support system through computer models and algorithms, and each entity performs ship deck aviation support simulation deduction according to the scheduling plan, outputs corresponding data information, and evaluates the input scheduling task plan based on the simulation results and the data information obtained by deduction, so as to realize the evaluation of the ship deck aviation support task plan.
2. The method for generating simulation scenarios for evaluating a warship aviation support mission plan according to claim 1, characterized in that ,The step S1 includes setting up a scenario information base; using Altova XMLSpy, describing the scenario elements of the shipboard aviation support, wherein the scenario elements include entity elements, task elements, and environment elements; The hypothetical description of the entity element includes information: basic attributes, spatial attributes, and state attributes; the basic attributes provide overall data of the entity, and the spatial attributes describe the spatial position of the entity in the simulation environment; The state attributes characterize the characteristics presented by the entity; The scenario description of the task element includes information: number of entities, entity number, task name, task number, start time of each task, end time of each task, and duration of each task; The hypothetical description of the environmental elements includes information: ship surface environment, weather conditions, and sea state levels.
3. The method for generating simulation scenarios for evaluating a warship aviation support mission plan according to claim 2, characterized in that ,The assumption elements of the ship surface aviation support include: the physical elements include ships, decks, catapults, tractors, elevators, arresting cables, carrier-based aircraft, and weapons; The basic attributes include the type, length, width, height, etc. of each entity, and each element of the basic attribute is defined as a sub-element of the basic attribute; The spatial attribute includes location information of the entity, which is described as longitude, latitude, altitude, etc. of the location, and each element of the spatial attribute is defined as a sub-element of the spatial attribute; The state attributes include mounts, weapons, fuel, engines, etc., and each element of the state attribute is defined as a sub-element of the state attribute; The ship deck environment includes a take-off area, a docking area, a landing area and an island area; The weather conditions include temperature, air pressure, sky cloudiness, precipitation, wind speed and wind direction information; The sea condition level is divided into 10 levels: 0-9 according to the sea surface conditions within the field of vision, the shape of the wave crest and its degree of breaking, and the amount of wave foam.
4. The method for generating simulation scenarios for evaluating a warship aviation support mission plan according to claim 1, characterized in that ,S2 includes completing the parsing of the input task plan, inputting the task plan in the form of a Gantt chart, and extracting information including the number of carrier-based aircraft, carrier-based aircraft type, carrier-based aircraft number, task number, task name, task start time, task end time, task duration, etc. from the task plan through the task parser; and parsing the extracted information into a document in XML format and storing it in the task scenario of the scenario generation information.
5. The method for generating simulation scenarios for evaluating a warship aviation support mission plan according to claim 1, characterized in that: S3 initializes the assumption information based on S1 and S2; The method for initializing the scenario background and the scenario description includes: parsing the corresponding part of the XML Schema scenario markup language file, loading the scenario background and the scenario description, the scenario background is what kind of task is performed for what event, and the scenario description includes background time, duration, and scenario goal, and the goal is to describe the effect to be achieved through this task; The method for initializing the deck environment, weather conditions, and sea state information of the deck aviation support includes: parsing the corresponding part of the XML Schema assumption markup language, loading and initializing, loading different deck environments according to the flight deck type; displaying different weather conditions according to temperature, air pressure, sky cloudiness, precipitation, wind speed and wind direction; and loading the sea state level of the marine environment in real time according to the size of wind and waves; The method for initializing the scheduling task plan includes: parsing the corresponding part of the task element of the XML Schema scenario markup language file, and selecting which scheduling task plan to simulate and deduce according to which the shipboard aviation support is based; The method for initializing the position, state and other information of each entity includes: parsing the corresponding part of the XML Schema assumption markup language file, loading entity parameters, including initial state value, mount, weapon, fuel volume, etc., controlling the entity position information through longitude and latitude, etc.
6. The method for generating simulation scenarios for evaluating a warship aviation support mission plan according to claim 1, characterized in that: The S4 is based on the scheduling task plan in S2 and the initialization assumption information of S3. On the simulation platform of the shipboard aviation support system, with entities as carriers, each entity performs corresponding tasks according to the scheduling plan, completes the shipboard aviation support simulation and generates corresponding data, and evaluates the input scheduling task plan based on the simulation results and the simulation data.
Citation Information
Cited By
Aircraft consumable management method based on XML language
CN120909992A