Task planning method and device, electronic equipment and storage medium

Abstract

The invention discloses a task planning method and device, electronic equipment and a storage medium, and relates to the technical field of task simulation deduction, and the method comprises the steps: constructing a mind map ontology model according to a task level and an initial node contained in the task level; and performing logic verification on the mind map editing information of the user, if the logic verification is passed, adjusting the mind map ontology model according to the mind map editing information, and generating a target task file according to the obtained target mind map. The problems that in the task planning process, the logic relation and the overall conception among multiple tasks are difficult to visually reflect, and task errors are likely to occur can be solved. According to the method, the mind map is used as a front-end carrier, and the logic relationship is displayed through the mind map, so that a user can quickly view the whole task planning process from macroscopic to microscopic, and the planning efficiency is greatly improved. In addition, the method verifies editing information in real time, information missing or information conflict is avoided, and completeness and executable performance of the task are ensured.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of task simulation deduction, and in particular to a task planning method and device, an electronic device and a storage medium. BACKGROUND

[0002] In complex task simulation deduction, task planning is a key link in the preparation stage of the deduction scene, directly affecting the authenticity of the simulation process and the training effect. The traditional task planning method usually relies on text scripts or table inputs, which are filled in by the planning personnel one by one. However, the above-mentioned task planning method is not only tedious to operate, but also difficult to intuitively reflect the logical relationship between multiple tasks and the overall concept. Although some task simulation platforms have introduced graphical editing tools, the structure of the graphical editing tools is linear and single-level, which cannot effectively support the hierarchical decomposition from complex task intentions to tactical tasks, and it is also difficult to intuitively reflect the logical relationship between multiple tasks. In addition, in complex scenes such as joint complex tasks and multi-domain cooperation, the above-mentioned task planning method is prone to problems such as task omission, time sequence conflict, and unclear responsibilities.

[0003] Therefore, the related art has the problem that it is difficult to intuitively reflect the logical relationship between multiple tasks and the overall concept in the task planning process, and task errors are prone to occur. SUMMARY

[0004] Therefore, the present application provides a task planning method, device, electronic device and storage medium to solve the problem that it is difficult to intuitively reflect the logical relationship between multiple tasks and the overall concept in the task planning process, and task errors are prone to occur.

[0005] In a first aspect, the present application provides a task planning method, which comprises: obtaining a preset number of task levels and initial nodes contained in the task levels; constructing a mind map ontology model according to the task levels and the initial nodes; obtaining mind map editing information of a user, and performing logical verification on the mind map editing information, wherein the logical verification is used to determine whether the mind map editing information is complete, and whether there is information in the mind map editing information that conflicts with the mind map ontology model; if the logical verification of the mind map editing information is passed, adjusting the mind map ontology model according to the mind map editing information to obtain a target mind map; obtaining a target task file according to the target mind map.

[0006] In a second aspect, the present application provides a task planning device, which comprises: a node obtaining module configured to obtain a preset number of task levels and initial nodes contained in the task levels; The model construction module is configured to construct a mind map ontology model according to the task hierarchy and the initial nodes. The information checking module is configured to acquire mind map editing information of the user, and perform logical checking on the mind map editing information. The logical checking is configured to determine whether the mind map editing information is complete, and whether there is information in the mind map editing information that conflicts with the mind map ontology model. The model adjustment module is configured to adjust the mind map ontology model according to the mind map editing information to obtain a target mind map, if the logical checking on the mind map editing information is passed. The file generation module is configured to obtain a target task file according to the target mind map.

[0007] In a third aspect, the present application provides an electronic device, comprising a memory and a processor, which are communicatively connected with each other, and the memory stores computer instructions. The processor executes the computer instructions to perform the task planning method of the first aspect or any of the corresponding embodiments.

[0008] In a fourth aspect, the present application provides a computer readable storage medium, which stores computer instructions. The computer instructions are used to make a computer execute the task planning method of the first aspect or any of the corresponding embodiments.

[0009] In a fifth aspect, the present application provides a computer program product, which comprises computer instructions. The computer instructions are used to make a computer execute the task planning method of the first aspect or any of the corresponding embodiments.

[0010] According to the present application, the mind map ontology model is constructed according to the task hierarchy and the initial nodes contained in the task hierarchy. The logical checking is performed on the mind map editing information of the user. If the logical checking is passed, the mind map ontology model is adjusted according to the mind map editing information to obtain a target mind map. The target task file is obtained according to the target mind map. The problem that it is difficult to intuitively reflect the logical relationship between multiple tasks and the overall concept in the task planning process, and the problem that the task error is prone to occur can be solved. The method takes the mind map as a front-end carrier. The creation, decomposition and attribute configuration of all tasks in the task planning process are completed in the same mind map model. The logical relationship is displayed through the mind map, so that the user can quickly review the entire task planning process from a macroscopic view to a microscopic view, and the planning efficiency is greatly improved. In addition, the editing information is checked in real time to avoid missing information or information conflict, and the completeness and executability of the task are ensured. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the specific embodiments or the related art of the present application, the drawings needed to be used in the specific embodiments or the related art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0012] Figure 1 is a flowchart of a task planning method according to an embodiment of the present application; Figure 2 is an architecture diagram of a multi-user-oriented task construction method based on a mind map according to an embodiment of the present application; Figure 3 is a task planning flowchart according to an embodiment of the present application; Figure 4 is a multi-user coordination sequence diagram according to an embodiment of the present application; Figure 5 is a structural block diagram of a task planning device according to an embodiment of the present application; Figure 6 is a hardware structure schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0013] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0014] It can be understood that before using the technical solutions disclosed in the embodiments of the present application, the type, use range, use scenario and the like of the personal information involved in the present application should be informed to the user and the authorization of the user should be obtained through appropriate means according to relevant laws and regulations.

[0015] The terms "first", "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features limited by "first", "second" can explicitly or implicitly include one or more of the features. In the description of the present application, the meaning of "multiple" is two or more than two, unless otherwise specifically limited.

[0016] In complex task simulation deduction, task planning is a key link in the preparation stage of deduction scene, which directly affects the authenticity of task simulation process and training effect. The traditional task planning often depends on text script or table input, and the task parameters are filled in by the planning personnel one by one. Such method is not only cumbersome to operate, but also difficult to intuitively reflect the logical relationship and overall concept among multiple tasks. Especially in complex scenes such as joint complex tasks and multi-domain cooperation, it is easy to have problems such as task omission, time sequence conflict and unclear responsibility. In addition, although some task simulation platforms introduce graphical editing tools such as flowchart or timeline view, their structure is linear and single level, which cannot effectively support the decomposition of complex task intention to tactical task layer by layer. At the same time, in the multi-user collaborative environment, participants of different troops and levels often need to work together in the same task system. The existing system lacks a unified collaboration framework, leading to information fragmentation and version confusion, which seriously affects the efficiency and consistency of task planning.

[0017] It can be seen that the following technical problems exist in the above task planning process: the task structure is not clear, and it is difficult to intuitively show the hierarchical relationship and logical context of the task. There is a lack of effective multi-user collaboration mechanism, and different users are prone to repeated definition, overlapping responsibilities or information isolation in task design. The task planning process lacks visual guidance, and the traditional input method is boring and easy to miss key nodes.

[0018] Mind map is a non-linear knowledge organization tool with clear hierarchy, flexible organization and strong visualization. It has been preliminarily applied in the fields of decision support and scheme deduction. However, existing applications mostly stay at the level of thinking aid, and have not realized the deep integration with complex task simulation system, which cannot directly convert the logical structure in mind map into executable task data.

[0019] Based on the above, the embodiment of the application provides a task planning method which can take a mind map as a core carrier, support multi-user collaborative editing, and effectively convert into a simulation task input task script. The method takes the mind map as a main construction interface of the task, realizes visual decomposition and multi-user collaborative management of the task structure. The mind map ontology modeling facing the complex task semantics: a special task mind map model is constructed, a four-level standard structure of "complex task purpose-complex task target-complex task action-complex task details" is defined, the complex task details node binds force entities, space regions, execution time limits, task types and other simulation required attributes, and a structured and analyzable task framework is formed. The multi-user collaborative editing mechanism based on role permission: multi-users such as planning personnel are supported to operate on the same mind map in parallel, the system allocates editing permissions according to user roles, and multi-user collaborative editing of the task is realized. The method improves the task planning efficiency: compared with the traditional table input, the task structure construction time is significantly shortened; enhances the task logic integrity: the four-level structure guide makes the task omission probability decrease, and the key node coverage rate significantly improves; optimizes the multi-user collaboration experience: the permission isolation and real-time synchronization mechanism makes the multi-seat multi-user collaboration efficiency significantly improved; reduces the data error rate: attribute checking and conflict detection significantly reduce the task script error rate.

[0020] According to the embodiment of the application, a task planning method embodiment is provided. It should be noted that the steps shown in the flowchart of the drawing can be executed in a computer system such as a group of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from here.

[0021] In the embodiment, a task planning method is provided, Figure 1 is a flowchart of the task planning method according to the embodiment of the application, as Figure 1 shown, the flow includes the following steps: Step S101, obtaining a preset number of task levels and initial nodes contained in the task levels.

[0022] Specifically, the task planning method of the embodiment is executed by Figure 2 the multi-user task construction architecture based on the mind map as shown, the user can initiate the task planning process according to the mind map editor in the user interaction layer.

[0023] The preset number is, for example, 4, 5 or other integers that meet the actual demand. After the task planning process is initiated, the business logic layer obtains the preset number of task levels, for example: the complex task purpose layer, the complex task target layer, the complex task action layer and the complex task details layer. The task levels can be set by the user, or the task levels used in the historical task planning process can be determined. For example, as Figure 3As shown, user A can create a new task through the system service, and in the new task, the task level can be determined, and the system service responds to user A with success.

[0024] The business logic layer obtains the initial nodes contained in the task level. For example, the initial nodes contained in the complex task objective level are the "protect the safety of important targets in a certain place" node, the initial nodes contained in the complex task target level are the "destroy the enemy's attack system" node and the "delay the enemy's combat action" node, the initial nodes contained in the complex task action level are the "reduce the early warning detection capability" node and the "weaken the sustained combat capability" node, and the initial nodes contained in the complex task detail level are the "attack the enemy's A radar station" node and the "attack the enemy's B radar station" node.

[0025] In step S102, a mind map ontology model is constructed according to the task level and the initial nodes.

[0026] Specifically, the embodiment can take the mind map as the core carrier, support multi-user collaborative editing, and effectively convert into a simulation task input task script. The method takes the mind map as the main construction interface of the task, realizes the visual decomposition of the task structure and the multi-user collaborative management.

[0027] The task generation engine of the business logic layer constructs a mind map ontology model according to the task level and the initial nodes. For example, a mind map ontology modeling oriented to complex task semantics is constructed, and a special task mind map model is constructed. In the case where the task level contains the complex task objective level, the complex task target level, the complex task action level, and the complex task detail level, the constructed mind map ontology model is a four-level standard structure of "complex task objective-complex task target-complex task action-complex task detail".

[0028] In step S103, the mind map editing information of the user is obtained, and logical verification is performed on the mind map editing information. The logical verification is used to determine whether the mind map editing information is complete, and whether there is information in conflict with the mind map ontology model in the mind map editing information.

[0029] Specifically, this step is used to support the demand of multi-position and multi-user collaborative design of tasks in a joint complex task environment. The business logic layer can receive the mind map editing information of different users, and adjust the mind map ontology model according to the mind map editing information. The mind map editing information of the user, for example, decomposes the initial nodes in the task level, and binds attribute information to the initial nodes.

[0030] To prevent user editing from causing conflicts in the mind map ontology model, the conflict detection service in the business logic layer needs to perform logical verification on the mind map editing information. This includes verifying the completeness of the edited information, determining if it contains all key fields such as the execution subject, spatial region, time parameter, task type, and priority fields; verifying whether the edited information conflicts with existing information in the mind map ontology model, such as preventing two tasks from being executed by the same initial node within the same time period; ensuring that the previous level in the four-level standard hierarchy serves as the parent node for the next level, and that the start time of tasks in child nodes is not earlier than the start time of the parent node; and ensuring that the task execution area of ​​the initial node is within the boundary of the complex task operational area, which is the operational boundary determined by the command organization.

[0031] Furthermore, this embodiment can be designed with permission isolation and real-time synchronization mechanisms to significantly improve the efficiency of multi-seat, multi-user collaboration. For example, a role-based permission management interface can be set up in the user interaction layer. After receiving the mind map editing information input by the user, the permission control module in the business logic layer will check whether the user has the corresponding editing permissions. Only when the user has the corresponding editing permissions will the mind map editing information be logically verified and executed.

[0032] Step S104: If the logic verification of the mind map editing information passes, adjust the mind map ontology model according to the mind map editing information to obtain the target mind map.

[0033] Specifically, if the logic verification of the mind map editing information passes, the mind map ontology model is adjusted based on the editing information. For example, based on the editing information, the initial nodes in the mind map ontology model are bound with simulation-required attributes such as troop entities, spatial regions, execution time limits, and task types, forming a structured and parsable task framework. The initial nodes are also decomposed based on the editing information; for instance, the initial node "protecting the security of an important target in a certain area" in the complex task objective layer is decomposed into two nodes under the complex task objective layer: "disrupting the enemy's offensive system" and "delaying the enemy's combat operations." After the adjustment of the mind map ontology model is completed, the target mind map is obtained.

[0034] Step S105: Obtain the target task file based on the target mind map.

[0035] Specifically, the information in the target mind map is integrated into a target task file, which includes: task hierarchy, the relationship between different levels, initial nodes, the relationship between initial nodes at different levels, as well as basic task information, task system structure information, task execution area, and other information.

[0036] like Figure 3As shown, upon receiving a request from user A to export a task script, the system service generates a task script (JSON) and sends it to user A. The target task file is then stored in the solution library of the data support layer.

[0037] The task planning method provided in this embodiment constructs a mind map ontology model based on the task hierarchy and the initial nodes contained within the task hierarchy; it performs logical verification on the user's mind map editing information; if the logical verification passes, it adjusts the mind map ontology model according to the mind map editing information to obtain the target mind map; and it obtains the target task file based on the target mind map. This method uses the mind map as the front-end carrier, and the creation, decomposition, and attribute configuration of all tasks during the task planning process are completed within the same mind map model. By displaying logical relationships through the mind map, users can quickly review the entire task planning process from macro to micro, significantly improving planning efficiency. Furthermore, this method verifies editing information in real time, avoiding omissions or information conflicts, ensuring the integrity and executability of the task. It solves the problem that it is difficult to intuitively represent the logical relationships and overall conception between multiple tasks during the task planning process, and that task errors are prone to occur.

[0038] As an optional embodiment, obtaining the user's mind map editing information includes: Upon receiving a user's task editing request, obtain the user's editing permissions; Verify user permissions based on task editing requests and editing permissions; If the permission verification is successful, the node to be edited corresponding to the task editing request is locked, where the node to be edited is contained in the mind map ontology model; Obtain the mind map editing information input by the user for the node to be edited.

[0039] Specifically, this embodiment designs a multi-user collaborative editing mechanism based on role permissions. This mechanism supports multiple users, such as planners, to operate in parallel on the same mind map. The system assigns editing permissions according to user roles to realize multi-user collaborative editing of tasks.

[0040] This embodiment achieves a collaborative model with clear division of labor and overall unity through access control and a collaborative editing framework. Upon receiving a user's task editing request, the system acquires the user's editing permissions. Based on the task editing request and editing permissions, the system verifies the user's permissions. For example, if the task editing request indicates that the user needs to edit node x in task level X, and the user's permissions include editing node x in task level X, then the user's permission verification is successful.

[0041] The embodiment designs an edit lock mechanism. When a user starts editing a node, the system locks the node, and other users can only view but cannot modify, to prevent concurrent conflicts. Therefore, under the condition that the permission verification is passed, the task editing request of the mind map ontology model is locked.

[0042] After locking the to-be-edited node, the mind map editing information input by the user for the to-be-edited node is obtained.

[0043] The above process is as shown in Figure 3 After the system service creates the mind map ontology model, the system service broadcasts a task creation event to user B, to notify user B that there is currently a mind map ontology model; user B can request the system service to edit the task. After the system service verifies the permission of user B, the edit lock is activated, user B submits a new node (containing mind map editing information), the system service checks the mind map editing information, and after the check is passed, the mind map ontology model is adjusted according to the mind map editing information to obtain a target mind map.

[0044] In the embodiment of the present application, in order to support the demand of multi-position and multi-user collaborative design of tasks in a joint complex task environment, a role-based access control mechanism is adopted to ensure clear division of labor and safe operation. Multiple people can edit the same mind map at the same time, and through the edit lock, real-time synchronization and permission control mechanism, multiple users can efficiently, consistently and accurately complete the structured task planning from strategic intent to tactical task on an intuitive and friendly visual platform during task planning.

[0045] As an optional embodiment, adjusting the mind map ontology model according to the mind map editing information to obtain a target mind map comprises: Obtaining node attribute information and node decomposition information in the mind map editing information; Binding the node attribute information to the to-be-edited node in the mind map ontology model, decomposing the to-be-edited node according to the node decomposition information, and obtaining a target mind map; Generating a task change event and broadcasting the task change event to the client of other users, wherein the task change event is used to synchronize the target mind map to the client of other users; Obtaining user information of the user, and generating an operation log according to the user information and the mind map editing information.

[0046] Specifically, the node attribute information and the node decomposition information are acquired in the mind map editing information. The node attribute information is for example: a task execution subject, a task space area, a task time parameter, a task type of the task, and a task priority. The node decomposition information is for example: decomposing a complex task objective "defend the safety of an important target in a certain place" node into two complex task objectives "destroy the enemy attack system" node and "delay the enemy combat action" node; decomposing the complex task objective "destroy the enemy attack system" node into two task actions "reduce the early warning detection capability" node and "weaken the sustained combat capability" node; and decomposing the complex task action "reduce the early warning detection capability" node into two specific combat tasks "attack the enemy M radar station" node and "attack the enemy N radar station" node. In addition, the system can automatically give a weapon and ammunition use suggestion based on the target property, and a commander determines a required force unit based on the weapon and ammunition, sets a task type, a task execution area, a start and end time, and the like, and completes the task planning at the tactical level.

[0047] The node attribute information is bound to the to-be-edited node in the mind map ontology model, and the to-be-edited node is decomposed according to the node decomposition information to obtain the target mind map.

[0048] The embodiment designs a real-time synchronization updating mechanism, realizes real-time synchronization of multi-terminal information through a transmission control protocol (TCP) protocol, and ensures information consistency. A task change event is generated according to the TCP protocol, and the task change event is broadcast to a client of another user, and the target mind map is synchronized to the client of the other user through the task change event. As shown in Figure 3 illustrated, the system service broadcasts the task change event, and the client of user A automatically refreshes the view to complete synchronization of the target mind map.

[0049] User information of the user is acquired, and an operation log is generated according to the user information and the mind map editing information. For example, all adding, deleting, and modifying operations are recorded in the operation log, including an operator, a time stamp, and change details, to support process tracing.

[0050] In the embodiment of the application, task structured construction and attribute binding are realized, multi-user real-time synchronization is guaranteed through the TCP protocol, operation logs support process tracing, and collaboration efficiency and task planning accuracy are improved.

[0051] As an optional embodiment, the node attribute information is bound to the to-be-edited node in the mind map ontology model, including: The execution subject field, the space area field, the time parameter field, the task type field and the priority field are obtained in the node attribute information, wherein the execution subject field is determined according to idle resources for executing a task, and the space area field is determined according to a geographic information system service or input space coordinates; The execution subject field, the space area field, the time parameter field, the task type field and the priority field are bound to the node to be edited.

[0052] Specifically, after each hierarchical node is created, the user can bind structured attributes to the node, and the system automatically performs integrity and rationality checking when saving.

[0053] The execution subject field, the space area field, the time parameter field, the task type field and the priority field are obtained in the node attribute information. The execution subject field contains a task execution subject, and the execution subject field is determined according to idle resources for executing a task, for example, the idle resources for executing a task are force resources that can execute a task, and the execution subject field is selected from a force unit library, and the force unit library is idle force resources that can execute a task. The space area field contains a task space area, which is determined by selecting a geographic information system (GIS) tool box or importing user input space coordinates. The idle resources can be determined by a resource library in a data support layer, and the GIS tool box can be implemented by a GIS service in the data support layer. The time parameter field contains a task time parameter, for example, an absolute time or a relative offset for executing a task. The task type field contains a task type, which lists specific task types, such as air patrol. The priority field contains a task priority, for example, high, medium and low. Figure 2 The execution subject field, the space area field, the time parameter field, the task type field and the priority field are obtained in the node attribute information. The execution subject field contains a task execution subject, and the execution subject field is determined according to idle resources for executing a task, for example, the idle resources for executing a task are force resources that can execute a task, and the execution subject field is selected from a force unit library, and the force unit library is idle force resources that can execute a task. The space area field contains a task space area, which is determined by selecting a geographic information system (GIS) tool box or importing user input space coordinates. The idle resources can be determined by a resource library in a data support layer, and the GIS tool box can be implemented by a GIS service in the data support layer. The time parameter field contains a task time parameter, for example, an absolute time or a relative offset for executing a task. The task type field contains a task type, which lists specific task types, such as air patrol. The priority field contains a task priority, for example, high, medium and low. Figure 2 The execution subject field, the space area field, the time parameter field, the task type field and the priority field are obtained in the node attribute information. The execution subject field contains a task execution subject, and the execution subject field is determined according to idle resources for executing a task, for example, the idle resources for executing a task are force resources that can execute a task, and the execution subject field is selected from a force unit library, and the force unit library is idle force resources that can execute a task. The space area field contains a task space area, which is determined by selecting a geographic information system (GIS) tool box or importing user input space coordinates. The idle resources can be determined by a resource library in a data support layer, and the GIS tool box can be implemented by a GIS service in the data support layer. The time parameter field contains a task time parameter, for example, an absolute time or a relative offset for executing a task. The task type field contains a task type, which lists specific task types, such as air patrol. The priority field contains a task priority, for example, high, medium and low.

[0054] In the embodiments of the present application, the node multi-dimensional structured attribute binding is implemented, the execution subject is taken from the idle force resource library, the space area is determined by the GIS tool or coordinates, and the time, type, priority and other information are clear. The system automatically performs attribute integrity and rationality checking, avoids missing of key information and parameter conflicts, unifies task attribute specifications, and makes data accurate and reliable, thereby laying a solid foundation for subsequent task execution and cooperation, and improving the standardization and effectiveness of task planning.

[0055] As an optional embodiment, logical checking is performed on the mind map editing information, including: determining whether the mind map editing information contains a target field; In the case where the mind map editing information contains the target field, a first time field and a task execution area field are obtained in the mind map editing information; In the mind map ontology model, the second time field of the to-be-edited node, the parent node of the to-be-edited node, and the third time field of the parent node are determined. In the case that the first time field and the second time field do not contain a time overlap part, it is judged whether the start time of the to-be-edited node is earlier than the start time of the parent node according to the first time field and the third time field. In the case that the start time of the to-be-edited node is not earlier than the start time of the parent node, it is judged whether the task execution area of the to-be-edited node is within the preset area boundary according to the task execution area field. If the task execution area of the to-be-edited node is within the preset area boundary, it is determined that the mind map editing information logical verification is passed.

[0056] Specifically, after each hierarchical node is created, the user can bind structured attributes to it, and the system automatically performs integrity and rationality verification when saving. The automatic verification content of the system includes: 1. Mandatory item integrity: ensure that the key field has been filled in; 2. Resource conflict detection: the same complex task unit cannot execute two tasks in the same time period; 3. Time logic rationality: the previous layer of the four-level standard hierarchy serves as the parent node of the next layer, and the child node time cannot be earlier than the parent node start time, etc.; 4. Spatial validity: the selected task execution area should be within the complex task operational area boundary, which is the operational boundary determined by the command authority.

[0057] The embodiment is used for logical verification of mind map editing information. First, it is judged whether the target field is contained in the mind map editing information, such as the execution subject field, the space area field, the time parameter field, the task type field, and the priority field. If the mind map editing information does not contain the target field, it is determined that the mind map editing information logical verification is not passed.

[0058] In the case that the target field is contained in the mind map editing information, the first time field and the task execution area field that the user needs to bind to the to-be-edited node are obtained in the mind map editing information. The first time field is, for example, i hours and j minutes to i+2 hours and j minutes, and i and j are any natural numbers. The task execution area field is, for example, P area.

[0059] In the mind map ontology model, the second time field of the to-be-edited node, the parent node of the to-be-edited node, and the third time field of the parent node are determined. For example, the to-be-edited node is the "destroy enemy attack system" node, the "destroy enemy attack system" node is the parent node of the "destroy enemy attack system" node, the second time field of the to-be-edited node is, for example, i+3 hours and j minutes to i+4 hours and j minutes, and the third time field of the parent node is, for example, i-1 hours and j minutes to i+4 hours and j minutes.

[0060] Determine if the first and second time fields contain overlapping time portions. For example: if the first time field is from i+3:j to i+4:j, and the second time field is from i+3:j to i+5:j, then the overlapping portion of i+3:j to i+4:j is included. If the first time field is from i+3:j to i+4:j, and the second time field is from i+5:j to i+6:j, then the overlapping portion is not included. If the first and second time fields contain overlapping time portions, the mind map editing information logic validation fails.

[0061] If the first and second time fields do not overlap, determine whether the start time of the node to be edited is earlier than the start time of its parent node based on the first and third time fields. For example: if the first time field is from i+3:j to i+4:j, and the third time field is from i+4:j to i+6:j, then the start time of the node to be edited is earlier than the start time of its parent node; if the first time field is from i+3:j to i+4:j, and the third time field is from i+2:j to i+6:j, then the start time of the node to be edited is not earlier than the start time of its parent node. If the start time of the node to be edited is earlier than the start time of its parent node, the logical validation of the mind map editing information fails.

[0062] If the start time of the node to be edited is not earlier than the start time of its parent node, the task execution area field is used to determine whether the task execution area of ​​the node to be edited is within the preset area boundary. The preset area boundary is the boundary of the complex mission operational area, which is the operational boundary determined by the command organization. For example, if the boundary of the complex mission operational area includes areas P and Q, and the task execution area of ​​the node to be edited is area P, then the task execution area is determined to be within the preset area boundary.

[0063] If the task execution area of ​​the node to be edited is not within the preset area boundary, the logic verification of the mind map editing information will fail.

[0064] If the task execution area of ​​the node to be edited is within the preset area boundary, the logic verification of the mind map editing information is confirmed to be successful.

[0065] The above process is as follows Figure 4 As shown, the mind map is subject to task validation, which includes verifying the completeness of required fields, detecting resource conflicts, checking the rationality of time logic, and checking the validity of space. The validation is then judged to determine whether it passes. If it passes, a task script can be generated.

[0066] In this embodiment, by verifying required fields, time logic, spatial boundaries, and resource conflicts, key information omissions and parameter contradictions are prevented, ensuring that task editing information is compliant and reasonable, reducing data error rates, and laying a solid foundation for smooth task execution.

[0067] As an optional embodiment, the target task file is obtained according to the target mind map, and the target task file includes: The task structure information and the task execution information are obtained according to the target mind map. The task script is generated according to the preset format, the task structure information and the task execution information, and the task script is contained in the target task file.

[0068] Specifically, the embodiment is used for generating a task script according to a mind map. The task script is a complex task system sequence constructed in a standard JSON format script. The task script can be used as a front-end input for driving simulation deduction. For example, a data export component of a middle business logic layer is used to export the task script. Figure 2 The data export component of the middle business logic layer is used to export the task script.

[0069] The task structure information and the task execution information are obtained according to the target mind map. The task structure information includes task basic information, task system structure information, task levels, relationships between different levels, initial nodes, relationships between initial nodes at different levels and the like. The task execution information includes task execution area information and the like.

[0070] The preset format is, for example, a standard JSON format. The task structure information and the task execution information are converted into the task script in the preset format.

[0071] In the embodiment of the application, the task structure and execution information are extracted from the target mind map, and the task script is generated according to the preset format. The script can be directly used as a front-end input for simulation deduction, realizes seamless conversion of task planning to executable data, and improves task landing efficiency and adaptability.

[0072] As an optional embodiment, a preset number of task levels and initial nodes contained in the task levels are obtained, and the method includes: The mind map sample is obtained. The task levels and the level relationships between the task levels are determined according to the mind map sample, wherein the task levels include a task purpose layer, a task target layer, a task action layer and a task detail layer. The initial nodes contained in the task levels and the node relationships of the initial nodes are determined according to the mind map sample and the task levels, wherein the level relationships and the node relationships are used to determine parent nodes and child nodes of the initial nodes.

[0073] Specifically, the mind map sample is obtained. The mind map sample is, for example, a mind map generated in a historical task planning process, a mind map created in advance by a commander and the like.

[0074] The task levels and the level relationships between the task levels are determined according to the mind map sample. The task levels include a task purpose layer, a task target layer, a task action layer and a task detail layer.

[0075] The task purpose layer is a complex task purpose layer, representing the highest level of complex task intention of this action, embodying the final appeal of the complex task. The highest level of complex task intention is not simply to achieve a goal, but to integrate military goals and political purposes. The initial node contained in the task purpose layer is the "protect the safety of important targets in a certain place" node.

[0076] The task target layer is a complex task target layer, which is used to decompose the overall complex task purpose into several key complex task targets, each of which has a clear achievement standard as a subsequent evaluation basis. The initial nodes contained in the task target layer are the "destroy enemy attack system" node and the "delay enemy combat action" node, wherein "destroy enemy attack system" and "delay enemy combat action" are obtained by decomposing the complex task purpose "protect the safety of important targets in a certain place".

[0077] The task action layer is a complex task action layer, which plans specific complex task activities for each complex task target, embodies force deployment and tactical arrangement, and decomposes a single complex task target into a complex task action based on a mind map. The initial nodes contained in the task action layer are the "reduce early warning detection capability" node and the "weaken sustained combat capability" node. The two task actions "reduce early warning detection capability" and "weaken sustained combat capability" are obtained by decomposing the complex task target "destroy enemy attack system".

[0078] The task detail layer is a complex task detail layer, which further refines complex task actions into specific tasks that can be assigned and executed based on a mind map, directly corresponding to the execution entities in the simulation system. Each task needs to bind simulation required parameters such as execution force unit, spatial position, start and end time, task type, etc. The initial nodes contained in the task detail layer are the "attack enemy M radar station" node and the "attack enemy N radar station" node. The two specific combat tasks "attack enemy M radar station" and "attack enemy N radar station" are obtained by refining the complex task action "reduce early warning detection capability". In addition, the system automatically gives weapon and ammunition usage suggestions based on the nature of the target, and the commander determines the required force unit based on the weapon and ammunition, sets the task type, task execution area, start and end time, etc., and completes the task planning of the tactical layer.

[0079] The hierarchical relationship is, for example, the task purpose layer is the upper level of the task target layer, the task action layer is the lower level of the task target layer, the task action layer is the upper level of the task detail layer, and the task detail layer is the lowest level.

[0080] The node relationship is, for example, that the node of "protecting the safety of important targets in a certain place" is the parent node of the node of "destroying the enemy's attack system"; the node of "delaying the enemy's combat operation" is the child node of the node of "protecting the safety of important targets in a certain place"; and the node of "destroying the enemy's attack system" is the parent node of the node of "destroying the enemy's attack system". The previous layer of the four-level standard hierarchy is the parent node of the next layer.

[0081] The above process is shown in FIG. 1, in which a mind map is initialized; a node of "combat purpose" is created; a node of "combat target" is added; a node of "combat action" is added; a node of "combat task" is added; and attributes of the node of "combat action" can be bound, such as 1 execution subject, 2 spatial region, 3 time parameter, and the like. Multiple users can edit the above nodes in parallel. Figure 4

[0082] In the embodiments of the present application, the four-level task hierarchy and initial nodes are explicitly defined, the hierarchy and node association are clarified, and the structured decomposition of tasks from core intent to specific execution is realized. The logic is clear and normative, supports multi-user parallel editing, reduces the risk of task omission, and improves the systematicness and efficiency of complex task planning.

[0083] In the embodiments of the present application, a task planning device is also provided, which is used to realize the above embodiments and preferred embodiments, and has been described above. As used below, the term "module" can be a combination of software and / or hardware that realizes a predetermined function. Although the device described in the following embodiments is preferably realized in software, hardware, or a combination of software and hardware is also possible and contemplated.

[0084] The embodiments of the present application provide a task planning device, as shown in FIG. 1, which comprises: Figure 5 A node acquisition module 501 is configured to acquire a preset number of task hierarchies and initial nodes contained in the task hierarchies. A model construction module 502 is configured to construct a mind map ontology model according to the task hierarchies and the initial nodes. An information verification module 503 is configured to acquire mind map editing information of a user, and perform logical verification on the mind map editing information. The logical verification is used to determine whether the mind map editing information is complete, and whether there is information in the mind map editing information that conflicts with the mind map ontology model. A model adjustment module 504 is configured to, if the logical verification of the mind map editing information is passed, adjust the mind map ontology model according to the mind map editing information to obtain a target mind map. A file generation module 505 is configured to obtain a target task file according to the target mind map.

[0085] In some optional embodiments, the information verification module 503 comprises: ​​The first obtaining unit is configured to obtain an editing permission of the user in a case where the task editing request of the user is received. The permission verification unit is configured to perform permission verification on the user according to the task editing request and the editing permission. The node locking unit is configured to lock a to-be-edited node corresponding to the task editing request in a case where the permission verification is passed, wherein the to-be-edited node is contained in the mind map ontology model. The second obtaining unit is configured to obtain mind map editing information input by the user for the to-be-edited node.

[0086] In some optional embodiments, the model adjusting module 504 comprises: The third obtaining unit is configured to obtain node attribute information and node decomposition information in the mind map editing information. The adjusting unit is configured to bind the node attribute information to the to-be-edited node in the mind map ontology model, and decompose the to-be-edited node according to the node decomposition information to obtain a target mind map. The first generating unit is configured to generate a task change event, and broadcast the task change event to a client of another user, wherein the task change event is used to synchronize the target mind map to the client of the other user. The second generating unit is configured to obtain user information of the user, and generate an operation log according to the user information and the mind map editing information.

[0087] In some optional embodiments, the adjusting unit comprises: The obtaining sub-module is configured to obtain an execution subject field, a space area field, a time parameter field, a task type field and a priority field in the node attribute information, wherein the execution subject field is determined according to an idle resource used for executing a task, and the space area field is determined according to a geographic information system service or an input space coordinate. The binding sub-module is configured to bind the execution subject field, the space area field, the time parameter field, the task type field and the priority field to the to-be-edited node.

[0088] In some optional embodiments, the information checking module 503 comprises: The first judging unit is configured to judge whether the target field is contained in the mind map editing information. The fourth obtaining unit is configured to obtain a first time field and a task execution area field in the mind map editing information in a case where the target field is contained in the mind map editing information. The first determining unit is configured to determine a second time field of the to-be-edited node, a parent node of the to-be-edited node and a third time field of the parent node in the mind map ontology model. The second judgment unit is used to determine, based on the first time field and the third time field, whether the start time of the node to be edited is earlier than the start time of the parent node, when the first time field and the second time field do not contain any time overlap. The third judgment unit is used to determine whether the task execution area of ​​the node to be edited is within the preset area boundary based on the task execution area field, provided that the start time of the node to be edited is not earlier than the start time of the parent node. The second determining unit is used to determine that the mind map editing information logic verification passes if the task execution area of ​​the node to be edited is within the preset area boundary.

[0089] In some alternative implementations, the document generation module 505 includes: The unit is used to obtain task structure information and task execution information based on the target mind map; The third generation unit is used to generate a task script based on a preset format, task structure information, and task execution information. The task script is contained in the target task file.

[0090] In some optional implementations, the node acquisition module 501 includes: The fifth acquisition unit is used to acquire mind map samples; The third determining unit is used to determine the task level and the hierarchical relationship between the task levels based on the mind map sample. The task level includes the task purpose level, the task objective level, the task action level, and the task details level. The fourth determining unit is used to determine the initial nodes and node relationships of the task level based on the mind map sample and task level. The hierarchical relationship and node relationship are used to determine the parent node and child node of the initial node.

[0091] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0092] In this embodiment, the task planning device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0093] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention.

[0094] The following is a detailed reference. Figure 6which shows a structural schematic diagram suitable for use to implement an electronic device in embodiments of the present application. The electronic device can include a processor (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 602 or programs loaded from a memory 608 into a random access memory (RAM) 603. Various programs and data required for operation of the electronic device are also stored in the RAM 603. The processor 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0095] Generally, the following devices can be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a memory 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 can allow the electronic device to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 The electronic device with various devices is shown, but it should be understood that all of the shown devices are not required to be implemented or possessed, and more or less devices can be alternatively implemented or possessed.

[0096] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program according to embodiments of the present application. For example, embodiments of the present application include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for executing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network through the communication device 609, or installed from the memory 608, or installed from the ROM 602. When the computer program is executed by the processor 601, the above-described functions defined in the task planning method of embodiments of the present application are performed.

[0097] Figure 6 The electronic device shown is merely an example and should not bring any limitation to the functions and use range of embodiments of the present application.

[0098] The embodiments of the present application further provide a computer readable storage medium, and the method according to the embodiments of the present application can be implemented in hardware, firmware, or recorded in a storage medium, or stored in a remote storage medium or a non-transitory machine readable storage medium and downloaded to a local storage medium through network, so that the method described herein can be processed by such software on a storage medium using a general purpose computer, a special purpose processor, or programmable or special hardware. The storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid state disk, etc. Further, the storage medium can also include a combination of the above-mentioned memories. It can be understood that the computer, the processor, the microprocessor controller, or the programmable hardware includes a storage component that can store or receive software or computer code, when the software or computer code is accessed and executed by the computer, the processor, or the hardware, the task planning method shown in the above embodiments is implemented.

[0099] Part of the present application can be applied as a computer program product, for example, computer program instructions, when executed by a computer, the operation of the computer can invoke or provide the method and / or technical solutions according to the present application. Those skilled in the art should understand that the form of computer program instructions in computer readable medium includes but is not limited to source file, executable file, installation package file, etc. Correspondingly, the way of computer program instructions executed by computer includes but is not limited to: the computer directly executes the instructions, or the computer compiles the instructions and then executes the corresponding compiled program, or the computer reads and executes the instructions, or the computer reads and installs the instructions and then executes the corresponding installed program. Here, the computer readable medium can be any available computer readable storage medium or communication medium accessible to the computer.

[0100] Although the embodiments of the present application are described in conjunction with the accompanying drawings, various modifications and changes can be made by those skilled in the art without departing from the spirit and scope of the present application, and such modifications and changes fall within the scope defined by the appended claims.

Claims

1. A task planning method characterized by, The method comprises: acquiring a preset number of task levels and initial nodes contained in the task levels; constructing a mind map ontology model according to the task levels and the initial nodes; acquiring mind map editing information of a user, and performing logical verification on the mind map editing information, wherein the logical verification is used to determine whether the mind map editing information is complete and whether there is information conflicting with the mind map ontology model in the mind map editing information; if the logical verification of the mind map editing information is passed, adjusting the mind map ontology model according to the mind map editing information to obtain a target mind map; obtaining a target task file according to the target mind map.

2. The method of claim 1, wherein, The acquiring of the mind map editing information of the user comprises: acquiring editing authority of the user in the case of receiving a task editing request of the user; performing authority verification on the user according to the task editing request and the editing authority; locking a to-be-edited node corresponding to the task editing request in the case of passing the authority verification, wherein the to-be-edited node is contained in the mind map ontology model; acquiring mind map editing information input by the user for the to-be-edited node.

3. The method of claim 2, wherein, The adjusting of the mind map ontology model according to the mind map editing information to obtain a target mind map comprises: acquiring node attribute information and node decomposition information in the mind map editing information; binding the node attribute information to the to-be-edited node in the mind map ontology model, decomposing the to-be-edited node according to the node decomposition information, and obtaining the target mind map; generating a task change event and broadcasting the task change event to clients of other users, wherein the task change event is used to synchronize the target mind map to the clients of the other users; acquiring user information of the user, and generating an operation log according to the user information and the mind map editing information.

4. The method of claim 3, wherein, The binding of the node attribute information to the to-be-edited node in the mind map ontology model comprises: acquiring an execution subject field, a space area field, a time parameter field, a task type field and a priority field in the node attribute information, wherein the execution subject field is determined according to an idle resource used for executing a task, and the space area field is determined according to a geographic information system service or an input space coordinate; binding the execution subject field, the space area field, the time parameter field, the task type field and the priority field to the to-be-edited node.

5. The method of claim 2, wherein, The logical verification on the mind map editing information comprises: determining whether a target field is contained in the mind map editing information; acquiring a first time field and a task execution area field in the mind map editing information in the case that the target field is contained in the mind map editing information; determining a second time field of the to-be-edited node, a parent node of the to-be-edited node and a third time field of the parent node in the mind map ontology model; In a case that the first time field and the second time field do not contain a time overlapping part, it is judged whether the start time of the node to be edited is earlier than the start time of the parent node according to the first time field and the third time field; In a case that the start time of the node to be edited is not earlier than the start time of the parent node, it is judged whether the task execution area of the node to be edited is within a preset area boundary according to the task execution area field; If the task execution area of the node to be edited is within the preset area boundary, it is determined that the mind map editing information logical check is passed.

6. The method of claim 1, wherein, The target task file is obtained according to the target mind map, including: Task structure information and task execution information are obtained according to the target mind map; A task script is generated according to a preset format, the task structure information and the task execution information, wherein the task script is contained in the target task file.

7. The method of claim 1, wherein, The preset number of task levels and initial nodes contained in the task levels include: A mind map sample is obtained; The task levels and the hierarchical relationship between the task levels are determined according to the mind map sample, wherein the task levels include a task purpose layer, a task target layer, a task action layer and a task detail layer; The initial nodes contained in the task levels and the node relationship of the initial nodes are determined according to the mind map sample and the task levels, wherein the hierarchical relationship and the node relationship are used to determine the parent node and the child node of the initial node.

8. A task planning apparatus characterized by comprising: The device includes: A node obtaining module is configured to obtain a preset number of task levels and initial nodes contained in the task levels; A model constructing module is configured to construct a mind map ontology model according to the task levels and the initial nodes; An information checking module is configured to obtain mind map editing information of a user, and perform logical check on the mind map editing information, wherein the logical check is used to determine whether the mind map editing information is complete, and whether there is information conflicting with the mind map ontology model in the mind map editing information; A model adjusting module is configured to adjust the mind map ontology model according to the mind map editing information to obtain a target mind map if the mind map editing information logical check is passed; A file generating module is configured to obtain a target task file according to the target mind map.

9. An electronic device, comprising: It includes: A memory and a processor are communicatively connected, the memory stores computer instructions, and the processor executes the computer instructions to perform the task planning method in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, and the computer instructions are used to make a computer execute the task planning method in any one of claims 1 to 7.

Images