A method, device, equipment and medium for managing drone software status

Abstract

The present application discloses a method, apparatus, device and medium for managing the state of unmanned aerial vehicle software, which relates to the technical field of software configuration management. The method comprises: obtaining and traversing several software configuration lists of target unmanned aerial vehicle software to count the occurrence frequency of each software configuration item; filtering and sorting each software configuration item based on the occurrence frequency, encoding according to the sorting result, and obtaining an encoded list set to be mined; if the current mining situation does not meet a preset switching condition, iteratively mining the software configuration items in the list set to be mined using a first preset frequent item mining method, and switching to a second preset frequent item mining method to traverse and mine the currently mined frequent items when it is detected that the preset switching condition is met during the mining process; determining the steady-state items in the list set to be mined based on the mining result, and solidifying the steady-state software package containing the steady-state items into a software baseline core layer, so as to perform state management of the target unmanned aerial vehicle software.

Description

Technical Field

[0001] The present invention relates to the technical field of software configuration management, and in particular to a method, device, equipment and medium for managing the software status of an unmanned aerial vehicle (UAV). Background Art

[0002] The current drone software ecosystem is highly complex and fragmented. The drone software state typically consists of hundreds of software manifests, each of which uniquely identifies a software module through a triplet of "finished product code - software configuration item identifier - software version." Current practices rely on manual coordination, with software engineering managers required to individually confirm the version and status of each finished software item through cross-departmental and cross-section phone calls. However, because the information collection cycle is positively correlated with the frequency of software changes, manual tracking efficiency plummets as the number of changes increases. The error rate of manual verification increases linearly with the number of software configuration items. Furthermore, each software baseline build requires a complete reconstruction, making existing methods time-consuming and inefficient for handling software baselines for large-scale, complex systems. Accuracy cannot be guaranteed, resulting in low efficiency.

[0003] To sum up, how to improve the efficiency of software baseline construction of drone software to improve the efficiency of drone software status management is a technical problem that needs to be solved urgently. Summary of the Invention

[0004] In view of this, the present invention aims to provide a method, apparatus, device, and medium for managing the state of drone software, which can improve the efficiency of building a software baseline for drone software and thereby improve the efficiency of drone software state management. The specific solution is as follows:

[0005] In a first aspect, the present application provides a method for managing drone software status, comprising:

[0006] Obtaining a plurality of software configuration lists of the input target drone software, and traversing the plurality of software configuration lists to count the occurrence frequency of each software configuration item in the plurality of software configuration lists;

[0007] Filtering and sorting the software configuration items in the plurality of software configuration lists based on the occurrence frequencies, encoding the software configuration items according to the sorting results, and obtaining an encoded list set to be mined;

[0008] If the current mining situation does not meet the preset switching condition, the software configuration items in the to-be-mined list set are iteratively mined using the first preset frequent item mining method, and during the mining process, when it is detected that the current mining situation meets the preset switching condition, the second preset frequent item mining method is switched to perform traversal mining on the currently mined frequent items to obtain corresponding mining results; the frequent items are software configuration items whose occurrence frequency is higher than a preset occurrence frequency threshold;

[0009] According to the mining results, steady-state items in the to-be-mined list set are determined, and the steady-state software package containing the steady-state items is solidified as the software baseline core layer of the target UAV software, so as to perform status management of the target UAV software based on the software baseline core layer.

[0010] Optionally, filtering and sorting the software configuration items in the plurality of software configuration lists based on the occurrence frequency, encoding the software configuration items according to the sorting result, and obtaining an encoded list set to be mined, includes:

[0011] removing the software configuration items whose occurrence frequency is not higher than the preset occurrence frequency threshold from the software configuration lists to obtain a plurality of filtered software configuration lists;

[0012] sorting the software configuration items in the filtered software configuration lists in descending order based on the frequencies of occurrence, and in the sorting process, sorting the software configuration items with consistent frequencies of occurrence in ascending order according to the triple dictionary of the software configuration items to obtain a number of sorted software configuration items;

[0013] Sorting the plurality of filtered software configuration lists in ascending order according to their corresponding list identifiers to obtain a plurality of sorted software configuration lists;

[0014] Software configuration item encoding is performed according to the sorting results of the plurality of sorted software configuration items, and list encoding is performed according to the sorting results of the plurality of sorted software configuration lists, so as to obtain an encoded list set to be mined.

[0015] Optionally, if the current mining situation does not meet the preset switching condition, iteratively mining the software configuration items in the to-be-mined list set using a first preset frequent item mining method, and during the mining process, when it is detected that the current mining situation meets the preset switching condition, switching to a second preset frequent item mining method to traverse and mine the currently mined frequent items to obtain corresponding mining results, including:

[0016] Determine the number of the first type of software configuration items in the to-be-mined list set and the current memory status;

[0017] If the number of the first type is greater than a preset type number threshold, or the memory condition indicates that the current available memory capacity is lower than a preset capacity threshold, it is determined that the current mining condition does not meet the preset switching condition, and the software configuration items in the to-be-mined list set are iteratively mined using a first preset frequent item mining method;

[0018] During the mining process, the memory status and the number of the second type of frequent items currently mined are continuously monitored;

[0019] If it is monitored that the number of the second type is not greater than the preset type number threshold, and the memory situation indicates that the current available memory capacity is not less than the preset capacity threshold, it is determined that the current mining situation meets the preset switching condition, and the second preset frequent item mining method is switched to perform traversal mining on the currently mined frequent items to obtain corresponding mining results.

[0020] Optionally, the iterative mining of the software configuration items in the to-be-mined list set using the first preset frequent item mining method includes:

[0021] Combining the plurality of software configuration lists in the set of lists to be mined in pairs to obtain a plurality of corresponding list pairs;

[0022] Determining a plurality of intersections corresponding to the plurality of list pairs respectively, determining a maximum common intersection corresponding to each of the plurality of list pairs based on the plurality of intersections, and determining the software configuration items in the maximum common intersection as the currently mined frequent items, so as to determine whether the current mining situation meets the preset switching condition based on the frequent items;

[0023] Determine the plurality of maximum common intersections as the plurality of software configuration lists for the next iteration, and jump to the step of combining the plurality of software configuration lists in the set of lists to be mined in pairs to obtain corresponding plurality of list pairs, until the number of intersections of the maximum common intersections is one, or the number of software configuration items in the maximum common intersections is lower than a preset software configuration item number threshold.

[0024] Optionally, the switching to the second preset frequent item mining method to traverse and mine the currently mined frequent items to obtain corresponding mining results includes:

[0025] Combining the plurality of maximum common intersections currently mined by the first preset frequent item mining method in pairs to obtain a plurality of corresponding intersection pairs;

[0026] Using a preset binary traversal method to traverse the maximum common intersections corresponding to the plurality of intersection pairs, so as to generate a plurality of non-empty subsets of the plurality of intersection pairs;

[0027] Determine the same software configuration items in the several non-empty subsets, and merge and count the software configuration lists associated with the same software configuration items to obtain the number of occurrences of the several non-empty subsets and the associated list of lists; the mining results include the number of occurrences of the several non-empty subsets and the associated list of lists.

[0028] Optionally, determining steady-state items in the to-be-mined list set based on the mining results, and solidifying the steady-state software package containing the steady-state items as the software baseline core layer of the target drone software, so as to perform state management of the target drone software based on the software baseline core layer, includes:

[0029] According to the mining results, the software configuration items in the to-be-mined list set that meet a preset steady-state item determination condition are determined as steady-state items; the preset steady-state item determination condition is a condition that the coverage rate of the plurality of software configuration lists is higher than a preset coverage rate threshold;

[0030] The determined steady-state items are encapsulated into a steady-state software package, and the encapsulated steady-state software package is solidified into a software baseline core layer of the target UAV software, so as to perform state management of the target UAV software based on the software baseline core layer.

[0031] Optionally, after solidifying the steady-state software package containing the steady-state item as the software baseline core layer of the target UAV software, the method further includes:

[0032] The software status of the target drone software is monitored in real time through a preset distributed messaging system, so that after a software configuration item change event of the target drone software is detected and captured, a changed software configuration item corresponding to the software configuration item change event and a plurality of software configuration lists to be updated related to the changed software configuration item are determined;

[0033] Saving the current version of the stable software package so that when an exception occurs during the update process for the software configuration item change event, the stable software package can be rolled back based on the current version;

[0034] The changed software configuration item is used to replace the original version software configuration item corresponding to the changed software configuration item in the several software configuration lists to be updated, and the obtained replaced software configuration list is used as the several software configuration lists for the next round of mining, and the step of traversing the several software configuration lists to count the frequency of occurrence of each software configuration item in the several software configuration lists is jumped to, so as to update the software baseline core layer according to the software configuration item change event.

[0035] In a second aspect, the present application provides a drone software status management device, comprising:

[0036] a list traversal module, configured to obtain a plurality of software configuration lists of the input target drone software, and traverse the plurality of software configuration lists to count the occurrence frequency of each software configuration item in the plurality of software configuration lists;

[0037] a software configuration item sorting module, configured to filter and sort the software configuration items in the plurality of software configuration lists based on the occurrence frequencies, and encode the software configuration items according to the sorting results to obtain an encoded list set to be mined;

[0038] a traversal mining module configured to iteratively mine the software configuration items in the to-be-mined list set using a first preset frequent item mining method if the current mining situation does not satisfy a preset switching condition, and, during the mining process, switch to a second preset frequent item mining method to perform traversal mining on the currently mined frequent items when it is detected that the current mining situation satisfies the preset switching condition, so as to obtain corresponding mining results; the frequent items are software configuration items whose occurrence frequency is higher than a preset occurrence frequency threshold;

[0039] The software package solidification module is used to determine the steady-state items in the to-be-mined list set based on the mining results, and solidify the steady-state software package containing the steady-state items into the software baseline core layer of the target UAV software, so as to perform status management of the target UAV software based on the software baseline core layer.

[0040] In a third aspect, the present application provides an electronic device, comprising:

[0041] Memory, used to store computer programs;

[0042] A processor is used to execute the computer program to implement the aforementioned drone software status management method.

[0043] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned drone software status management method is implemented.

[0044] In the present application, several software configuration lists of the target drone software are obtained as input, and the several software configuration lists are traversed to count the occurrence frequencies of each software configuration item in the several software configuration lists; the software configuration items in the several software configuration lists are filtered and sorted based on the occurrence frequencies, and the software configuration items are encoded according to the sorting results to obtain an encoded list set to be mined; if the current mining situation does not meet the preset switching condition, the software configuration items in the list set to be mined are iteratively mined using a first preset frequent item mining method, and during the mining process, when it is monitored that the current mining situation meets the preset switching condition, the second preset frequent item mining method is switched to traverse mining of the currently mined frequent items to obtain corresponding mining results; the frequent items are software configuration items whose occurrence frequency is higher than a preset occurrence frequency threshold; based on the mining results, steady-state items in the list set to be mined are determined, and the steady-state software package containing the steady-state items is solidified as the software baseline core layer of the target drone software, so that the state management of the target drone software is performed based on the software baseline core layer. As can be seen from the above, this application first obtains multiple software configuration lists of the target UAV software, counts the frequency of occurrence of each software configuration item, filters, sorts and encodes the software configuration items according to the frequency of occurrence, and forms a set of lists to be mined. Subsequently, in the mining process of frequent items, the first and second preset frequent item mining methods are flexibly switched based on whether the mining situation meets the preset switching conditions to obtain the mining results. Finally, the steady-state items in the set of lists to be mined are determined based on the mining results, and the steady-state software package containing the steady-state items is solidified as the software baseline core layer for software status management. In this way, through the above process of this application, the software configuration items in several software configuration lists are filtered, sorted, encoded and other pre-processing operations, which can eliminate noise interference, reduce the subsequent calculation scale, and improve mining efficiency. At the same time, the data volume is compressed by encoding, the data structure is unified, and subsequent mining calculations can be accelerated; by judging whether the mining situation meets the preset switching conditions, the mining method is dynamically switched, and the algorithm is adaptively switched through quantitative indicators, which can not only ensure the calculation accuracy, but also avoid the exponential complexity problem, and ensure that the calculation feasibility can still be maintained in resource-constrained scenarios; the steady-state software package corresponding to the mined steady-state item is solidified into the software baseline core layer, which can reduce the instability factors of the software caused by configuration changes, so as to facilitate efficient drone software status management, thereby improving the software baseline construction efficiency of the drone software to improve the efficiency of drone software status management. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0046] Figure 1 This is a flow chart of a method for managing the software status of a drone disclosed in this application;

[0047] Figure 2 This is a timing diagram of a method for managing the software status of a drone disclosed in this application;

[0048] Figure 3 A schematic diagram of a dynamic switching process of a frequent item mining method disclosed in this application;

[0049] Figure 4 This is a schematic diagram of the structure of a drone software status management device disclosed in this application;

[0050] Figure 5 This is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION

[0051] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. 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 making creative efforts are within the scope of protection of the present invention.

[0052] The current drone software ecosystem is highly complex and fragmented. The drone software state typically consists of hundreds of software manifests, each of which uniquely identifies a software module through a triplet of "finished product code - software configuration item identifier - software version." Current practices rely on manual coordination, with software engineering managers required to individually confirm the version and status of each finished software item through cross-departmental and cross-section phone calls. However, because the information collection cycle is positively correlated with the frequency of software changes, manual tracking efficiency plummets as the number of changes increases. The error rate of manual verification increases linearly with the number of software configuration items. Furthermore, each software baseline build requires a complete reconstruction, making existing methods time-consuming and inefficient for handling software baselines for large-scale, complex systems. Accuracy cannot be guaranteed, resulting in low efficiency.

[0053] In order to overcome the above technical problems, the present application provides a drone software status management method to improve the software baseline construction efficiency of drone software and improve the efficiency of drone software status management.

[0054] See also Figure 1 As shown, an embodiment of the present invention discloses a method for managing the software status of a drone, including:

[0055] Step S11: obtaining a plurality of software configuration lists of the input target drone software, and traversing the plurality of software configuration lists to count the occurrence frequency of each software configuration item in the plurality of software configuration lists.

[0056] In this embodiment, several software configuration lists of the target drone software are obtained as input and traversed to count the frequency of occurrence of each software configuration item in each of the software configuration lists. The software configuration lists include several software configuration items, each uniquely identified by a triplet of "product code - software item identifier - software version." Table 1 below shows a schematic diagram of a software configuration list and the software configuration items therein provided by this application. Code represents the product code, Id represents the software item identifier, and V represents the software version.

[0057] Table 1

[0058]

[0059] It should be pointed out that if Figure 2 The figure shows a timing diagram of a drone software state management method provided by this application. Specifically, the drone software state management method of this application includes six steps: composite coding preprocessing, software frequent item mining, dynamic switching strategy execution, establishment of stable and unstable software packages, dynamic software package maintenance and real-time updates, and software baseline release. Frequent item data mining and analysis techniques are used to identify the inherent association rules of software configuration items in order to perform state management on the target drone software. Thus, after obtaining several input software configuration lists, this embodiment traverses them to calculate the frequency of occurrence of software configuration items therein, so as to mine frequent items based on the frequency of occurrence and improve the efficiency of subsequent frequent item mining.

[0060] Step S12: filtering and sorting the software configuration items in the plurality of software configuration lists based on the occurrence frequencies, encoding the software configuration items according to the sorting results, and obtaining an encoded list set to be mined.

[0061] In this embodiment, the software configuration items in the plurality of software configuration lists are filtered and sorted according to the occurrence frequencies, and the software configuration items are encoded according to the obtained sorting results to obtain an encoded set of lists to be mined.

[0062] Specifically, the software configuration items whose occurrence frequency is not higher than the preset occurrence frequency threshold in the several software configuration lists are removed from the several software configuration lists to obtain several filtered software configuration lists; the software configuration items in the several filtered software configuration lists are sorted in descending order based on the occurrence frequency, and in the sorting process, the software configuration items with the same occurrence frequency are sorted in ascending order according to the triple dictionary of the software configuration items to obtain several sorted software configuration items; the several filtered software configuration lists are sorted in ascending order according to their respective corresponding list identifiers to obtain several sorted software configuration lists; software configuration item encoding is performed according to the sorting results of the several sorted software configuration items, and list encoding is performed according to the sorting results of the several sorted software configuration lists to obtain an encoded set of lists to be mined. That is, it is determined that the frequency of occurrence in the several software configuration lists is not higher than the preset frequency threshold. For example, a software configuration item that appears only once cannot constitute a frequent item set, so it can be eliminated to obtain several filtered software configuration lists. Taking Table 1 above as an example, the software configuration items therein are filtered. Table 2 is a schematic table of a filtered software configuration list provided by this application.

[0063] Table 2

[0064]

[0065] That is, the retained software configuration items are A, D, and B. Then, the software configuration items in the filtered software configuration lists are sorted in descending order based on the frequency of occurrence, so as to facilitate subsequent frequent item mining. In the sorting process, the software configuration items with the same frequency of occurrence are sorted in ascending order according to the triple dictionary of the software configuration items to ensure stable sorting, and several sorted software configuration items are obtained, for example, D(6)>A(5)>B(3). At the same time, the filtered software configuration lists are sorted in ascending order according to their corresponding list identifiers to obtain several sorted software configuration lists. Finally, the software configuration items are encoded according to the obtained sorting results, for example, D is encoded as 1, A is encoded as 2, and B is encoded as 3. The sorted software configuration lists are encoded to obtain an encoded list set to be mined. Table 3 is a schematic table of a list set to be mined provided by this application using Table 1 as an example.

[0066] Table 3

[0067]

[0068] In this way, this embodiment maps the software configuration items of each triple to a unique integer code, which can eliminate the interference of low-frequency noise data on frequent item set mining, thereby reducing the subsequent calculation scale and improving the efficiency of the algorithm; sorting the software configuration items in descending order according to the frequency of occurrence can ensure that high-frequency items participate in the calculation first, optimize the storage structure and calculation order, reduce the time complexity of the algorithm, and lay the foundation for the subsequent efficient intersection algorithm; mapping high-frequency software configuration items to short codes and forcing them to be stored in ascending order of codes in the list can compress the data volume and unify the data structure to accelerate subsequent intersection calculations and improve mining efficiency.

[0069] Step S13: If the current mining situation does not meet the preset switching condition, iteratively mine the software configuration items in the to-be-mined list set using the first preset frequent item mining method. During the mining process, if it is detected that the current mining situation meets the preset switching condition, switch to the second preset frequent item mining method to traverse and mine the currently mined frequent items to obtain corresponding mining results; the frequent items are software configuration items whose occurrence frequency is higher than a preset occurrence frequency threshold.

[0070] In this embodiment, if the current mining situation is determined not to satisfy a preset switching condition, a first preset frequent item mining method is used to iteratively mine the software configuration items in the to-be-mined list set. Simultaneously, during the mining process, the current mining situation is continuously monitored. When it is determined that the mining situation satisfies the preset switching condition, the method switches to a second preset frequent item mining method to perform traversal mining on the currently mined frequent items, thereby obtaining corresponding mining results. The frequent items are software configuration items whose occurrence frequency exceeds a preset occurrence frequency threshold; the mining situation includes memory status and the current number of to-be-mined software configuration items; the first preset frequent item mining method may be an optimized intersection iteration method; and the second preset frequent item mining method may be an enhanced combinatorial traversal method.

[0071] Specifically, determine the first type number of software configuration items in the list set to be mined, and the current memory situation; if the first type number is greater than the preset type number threshold, or the memory situation indicates that the current available memory capacity is lower than the preset capacity threshold, then determine that the current mining situation does not meet the preset switching condition, and use the first preset frequent item mining method to iteratively mine the software configuration items in the list set to be mined; during the mining process, continuously monitor the memory situation and the second type number of the frequent items currently mined; if it is monitored that the second type number is not greater than the preset type number threshold, and the memory situation indicates that the current available memory capacity is not lower than the preset capacity threshold, then determine that the current mining situation meets the preset switching condition, switch to the second preset frequent item mining method to traverse and mine the frequent items currently mined to obtain the corresponding mining results. That is, if Figure 3 FIG2 is a schematic diagram of a dynamic switching process of a frequent item mining method provided by the present application. After obtaining the list set to be mined, the number of first-type software configuration items and the current memory status are determined. If the number of the first-type software configuration items is greater than a preset type number threshold, or the memory status indicates that the current available memory capacity is less than a preset capacity threshold, it is determined that the current mining situation does not meet the preset switching condition. The software configuration items in the list set to be mined are iteratively mined using the first preset frequent item mining method. Meanwhile, during the mining process, if it is monitored that the number of the second-type software configuration items is not greater than the preset type number threshold, and the memory status indicates that the current available memory capacity is not less than the preset capacity threshold, it is determined that the current mining situation meets the preset switching condition. The method switches to the second preset frequent item mining method to perform traversal mining on the currently mined frequent items to obtain corresponding mining results.

[0072] It should be noted that the processing flow of iterative mining using the first preset frequent item mining method is as follows: the several software configuration lists in the list set to be mined are combined in pairs to obtain corresponding list pairs; the corresponding several intersections of the several list pairs are determined respectively, so as to determine the maximum common intersection corresponding to each of the several list pairs based on the several intersections, and the software configuration items in the maximum common intersections are determined as the frequent items currently mined, so as to determine whether the current mining situation meets the preset switching condition based on the frequent items; the several maximum common intersections are determined as the several software configuration lists for the next round of iteration, and jump to the step of combining the several software configuration lists in the list set to be mined in pairs to obtain corresponding list pairs, until the number of intersections of the maximum common intersections is one, or the number of software configuration items in the maximum common intersection is lower than the preset software configuration item number threshold. That is, the set of lists to be mined is used as input, and the several software configuration lists therein are combined two by two to obtain the intersections corresponding to the several list pairs. Based on the several intersections, the corresponding maximum common intersections (i.e., Maximum Common Subsets) are generated, and the software configuration items in the maximum common intersections are determined as the frequent items currently mined, so as to determine whether the current mining situation meets the preset switching conditions based on the frequent items. If the preset switching conditions are not met, the several maximum common intersections are determined as the several software configuration lists for the next iteration, and the process jumps to the step of combining the several software configuration lists in the set of lists to be mined two by two to obtain the corresponding several list pairs. Iterations are repeated until the number of intersections of the maximum common intersections is one, that is, no new maximum common intersection can be generated, or the number of software configuration items in the maximum common intersection is lower than a preset software configuration item number threshold, for example, lower than 2. Table 4 shows a schematic diagram of the mining iteration process of a first preset frequent item mining method provided in this application using Table 3 as an example.

[0073] Table 4

[0074]

[0075] in, Represents the intersection, and b represents the number of frequent item types currently mined.

[0076] It should be further pointed out that the processing flow of switching to the second preset frequent item mining method for traversal mining is as follows: the plurality of maximum common intersections currently mined by the first preset frequent item mining method are combined in pairs to obtain a corresponding plurality of intersection pairs; the maximum common intersections corresponding to each of the plurality of intersection pairs are traversed using the preset binary traversal method to generate a plurality of non-empty subsets of the plurality of intersection pairs; the same software configuration items in the plurality of non-empty subsets are determined, and the software configuration lists associated with the same software configuration items are merged and counted to obtain the number of occurrences of the plurality of non-empty subsets and the associated list list; the mining results include the number of occurrences of the plurality of non-empty subsets and the associated list list. That is, the plurality of maximum common intersections currently mined by the first preset frequent item mining method are used as input, and are combined in pairs to calculate the maximum common intersection of a plurality of intersection pairs, and then the obtained maximum common intersections are traversed using the preset binary traversal method to obtain all permutations and combinations of the maximum common intersections of the plurality of intersection pairs, and generate a plurality of non-empty subsets. The following Table 5 is a schematic diagram of the traversal process of a second preset frequent item mining method provided in the present application.

[0077] Table 5

[0078]

[0079] Then, the software configuration lists associated with the same software configuration items in the non-empty subsets are combined and counted, and the number of occurrences of each permutation and combination and the corresponding list are counted. The list that has appeared is counted only once, and duplicates are removed to obtain the number of occurrences of the non-empty subsets and the associated list. Table 6 below is a schematic table of statistical results of a second preset frequent item mining method provided by this application.

[0080] Table 6

[0081]

[0082] In this way, this embodiment uses multiple rounds of iterative calculations, takes the maximum common intersection generated by the pairwise intersection of the lists as a new input, and continuously generates higher-order common subsets until no new results can be generated, thereby improving computing efficiency; a dynamic switching strategy is implemented based on the element number threshold and real-time memory monitoring, and algorithm adaptive switching is achieved through quantitative indicators, which can not only ensure computing accuracy but also avoid exponential complexity problems, ensuring that computing feasibility can still be maintained in resource-constrained scenarios.

[0083] Step S14: Determine the steady-state items in the to-be-mined list set based on the mining results, and solidify the steady-state software package containing the steady-state items into the software baseline core layer of the target UAV software, so as to perform status management of the target UAV software based on the software baseline core layer.

[0084] In this embodiment, the steady-state items in the to-be-mined list set are determined based on the obtained mining results, and the steady-state items are encapsulated into a dynamically evolving steady-state software package, and the steady-state software package is solidified as the software baseline core layer of the target UAV software, so that the state management of the target UAV software can be performed based on the software baseline core layer. For example, when updating the software status, due to the stability of the steady-state items in the software baseline core layer, the relevant staff only need to consider other software configuration items other than the steady-state items, so as to achieve the purpose of improving management efficiency. It should be pointed out that this embodiment can determine the software configuration items that are not determined as the steady-state items in the various software configuration items as non-steady-state items, so as to conduct human subjective analysis, including two types of changes: component addition and deletion and version change.

[0085] Specifically, based on the mining results, software configuration items in the to-be-mined list set that meet a preset steady-state item determination condition are determined as steady-state items; the preset steady-state item determination condition is that the coverage rate for the plurality of software configuration lists is greater than a preset coverage threshold; the determined steady-state items are packaged into a steady-state software package, and the packaged steady-state software package is solidified as the software baseline core layer of the target UAV software, so that the state of the target UAV software is managed based on the software baseline core layer. That is, software configuration items in the mining results that meet the preset steady-state item determination condition, i.e., software configuration items with a coverage rate for the plurality of software configuration lists greater than a preset coverage threshold, are determined as steady-state items, the determined steady-state items are packaged into a steady-state software package, and the packaged steady-state software package is solidified as the software baseline core layer of the target UAV software, while ensuring version consistency of basic functions, so that the software engineering manager can make adaptive adjustments based on the software baseline core layer on the constructed initial software baseline. After confirmation by the heads of the respective software disciplines, the software baseline is released, completing the state management of the target UAV software.

[0086] It should be noted that, in this embodiment, after the steady-state software package is solidified as the software baseline core layer of the target drone software, the processing flow is as follows: the software status of the target drone software is monitored in real time through a preset distributed messaging system, so that after detecting and capturing a software configuration item change event of the target drone software, the changed software configuration item corresponding to the software configuration item change event and several software configuration lists to be updated related to the changed software configuration item are determined; the current version of the steady-state software package is saved so that when an exception occurs during the update process for the software configuration item change event, a rollback is performed based on the current version of the steady-state software package; the original version software configuration item corresponding to the changed software configuration item in the several software configuration lists to be updated is replaced with the changed software configuration item, and the obtained replaced software configuration list is used as the several software configuration lists for the next round of mining; and the step of traversing the several software configuration lists to count the occurrence frequency of each software configuration item in the several software configuration lists is performed, so as to update the software baseline core layer in response to the software configuration item change event. That is, a preset distributed messaging system is used to monitor the software status of the target drone software in real time. After detecting and capturing a software configuration item change event of the target drone software, the software configuration item corresponding to the software configuration item change event and several software configuration lists to be updated related to the changed software configuration item are determined to ensure that the changed software configuration item can enter the processing flow in a timely manner. The current version of the steady-state software package is then saved so that when an exception occurs during the update process for the software configuration item change event, a rollback is performed based on the current version of the steady-state software package. At the same time, the baseline service is not interrupted during the update process. When an exception is detected in the changed software configuration item, the software configuration item is re-evaluated, eliminated, or supplemented. The original version of the software configuration item corresponding to the changed software configuration item in the several software configuration lists to be updated is replaced with the changed software configuration item, and the obtained replaced software configuration list is used as the several software configuration lists for the next round of mining. The process then jumps to the step of traversing the several software configuration lists to count the occurrence frequency of each software configuration item in the several software configuration lists, so as to update the software baseline core layer in response to the software configuration item change event. In this way, the steady-state software package of this embodiment will dynamically evolve according to recent changes, so that the baseline construction is always based on the latest and most stable software configuration, avoiding the lag of manual collection, ensuring that the baseline version is synchronized with R&D progress, and improving accuracy.

[0087] As can be seen from the above, the embodiment of the present application first obtains multiple software configuration lists of the target drone software, counts the frequency of occurrence of each software configuration item therein, filters, sorts and encodes the software configuration items according to the frequency of occurrence, and forms a set of lists to be mined. Subsequently, in the mining process of frequent items, the first and second preset frequent item mining methods are flexibly switched based on whether the mining situation meets the preset switching conditions to obtain the mining results. Finally, the steady-state items in the set of lists to be mined are determined based on the mining results, and the steady-state software package containing the steady-state items is solidified as the software baseline core layer for software status management. In this way, through the above process of the embodiment of the present application, on the one hand, the software configuration items of each triple are mapped to a unique integer code, which can eliminate the interference of low-frequency noise data on frequent item set mining, reduce the subsequent calculation scale, and improve the efficiency of the algorithm; on the other hand, the software configuration items are sorted in descending order according to the frequency of occurrence, which can ensure that high-frequency items participate in the calculation first, optimize the storage structure and calculation order, reduce the time complexity of the algorithm, and lay the foundation for the subsequent efficient intersection algorithm; on the one hand, the high-frequency software configuration items are mapped to short codes, and the list is forced to be stored in ascending order of the codes, which can compress the data volume and unify the data structure to accelerate the subsequent intersection calculation and improve the mining efficiency; on the one hand, through multiple rounds of iterative calculations, the maximum common intersection generated by the intersection of the two lists is used as a new input, and higher-order common subsets are continuously generated until no new results can be generated. It can improve computing efficiency; on the one hand, it implements a dynamic switching strategy based on the element number threshold and real-time memory monitoring, and realizes adaptive switching of algorithms through quantitative indicators, which can not only ensure computing accuracy but also avoid exponential complexity problems, ensuring that computing feasibility can be maintained in resource-constrained scenarios; on the other hand, the steady-state software package will dynamically evolve according to recent changes, so that the baseline construction is always based on the latest and most stable software configuration, avoiding the lag of manual collection, ensuring that the baseline version is synchronized with the R&D progress, and improving accuracy; on the other hand, the steady-state software package corresponding to the mined steady-state item is solidified as the software baseline core layer, which can reduce the instability factors caused by configuration changes in the software, so as to facilitate efficient drone software status management, thereby improving the software baseline construction efficiency of drone software and improving the efficiency of drone software status management.

[0088] Accordingly, see Figure 4 As shown, the embodiment of the present application also provides a drone software status management device, including:

[0089] A list traversal module 11 is used to obtain a plurality of software configuration lists of the input target drone software and traverse the plurality of software configuration lists to count the occurrence frequency of each software configuration item in the plurality of software configuration lists;

[0090] a software configuration item sorting module 12 for filtering and sorting the software configuration items in the plurality of software configuration lists based on the occurrence frequencies, encoding the software configuration items according to the sorting results, and obtaining an encoded list set to be mined;

[0091] The traversal mining module 13 is configured to iteratively mine the software configuration items in the to-be-mined list set using a first preset frequent item mining method if the current mining situation does not satisfy a preset switching condition, and, during the mining process, switch to a second preset frequent item mining method to perform traversal mining on the currently mined frequent items when it is detected that the current mining situation satisfies the preset switching condition, so as to obtain corresponding mining results; the frequent items are software configuration items whose occurrence frequency is higher than a preset occurrence frequency threshold;

[0092] The software package solidification module 14 is used to determine the steady-state items in the to-be-mined list set based on the mining results, and solidify the steady-state software package containing the steady-state items into the software baseline core layer of the target UAV software, so as to perform status management of the target UAV software based on the software baseline core layer.

[0093] As can be seen from the above, the embodiment of the present application first obtains multiple software configuration lists of the target drone software, counts the frequency of occurrence of each software configuration item therein, filters, sorts and encodes the software configuration items according to the frequency of occurrence, and forms a set of lists to be mined. Subsequently, in the mining process of frequent items, the first and second preset frequent item mining methods are flexibly switched based on whether the mining situation meets the preset switching conditions to obtain the mining results. Finally, the steady-state items in the set of lists to be mined are determined based on the mining results, and the steady-state software package containing the steady-state items is solidified as the software baseline core layer for software status management. In this way, through the above process of the embodiment of the present application, pre-processing operations such as filtering, sorting, and encoding are performed on the software configuration items in several software configuration lists, which can eliminate noise interference, reduce the subsequent calculation scale, and improve mining efficiency. At the same time, the data volume is compressed by encoding, the data structure is unified, and subsequent mining calculations can be accelerated; by judging whether the mining situation meets the preset switching conditions, the mining method is dynamically switched, and the algorithm is adaptively switched through quantitative indicators, which can not only ensure the calculation accuracy, but also avoid the exponential complexity problem, and ensure that the calculation feasibility can still be maintained in resource-constrained scenarios; the steady-state software package corresponding to the mined steady-state item is solidified as the software baseline core layer, which can reduce the instability factors of the software caused by configuration changes, so as to facilitate efficient drone software status management, thereby improving the software baseline construction efficiency of the drone software to improve the efficiency of drone software status management.

[0094] In some specific implementations, the software configuration item sorting module 12 may specifically include:

[0095] a configuration item elimination unit, configured to eliminate, from the plurality of software configuration lists, software configuration items whose occurrence frequency is not higher than the preset occurrence frequency threshold, to obtain a plurality of filtered software configuration lists;

[0096] a configuration item sorting unit, configured to sort the software configuration items in the filtered software configuration lists in descending order based on the frequencies of occurrence, and in the sorting process, sort the software configuration items with the same frequencies of occurrence in ascending order according to the triple dictionary of the software configuration items, so as to obtain a plurality of sorted software configuration items;

[0097] a list sorting unit, configured to sort the plurality of filtered software configuration lists in ascending order according to their corresponding list identifiers to obtain a plurality of sorted software configuration lists;

[0098] The list encoding unit is used to encode the software configuration items according to the sorting results of the plurality of sorted software configuration items, and to encode the lists according to the sorting results of the plurality of sorted software configuration lists, so as to obtain an encoded list set to be mined.

[0099] In some specific implementations, the traversal mining module 13 may specifically include:

[0100] a situation determination unit, configured to determine the number of the first type of software configuration items in the to-be-mined list set and the current memory situation;

[0101] an iterative mining unit, configured to determine that the current mining situation does not satisfy a preset switching condition if the number of the first type is greater than a preset type number threshold, or if the memory situation indicates that the current available memory capacity is less than a preset capacity threshold, and iteratively mine the software configuration items in the to-be-mined list set using a first preset frequent item mining method;

[0102] The data monitoring unit is used to continuously monitor the memory status and the number of the second type of frequent items currently mined during the mining process;

[0103] The traversal mining unit is configured to, if it is monitored that the number of the second type is not greater than the preset type number threshold, and the memory situation indicates that the current available memory capacity is not less than the preset capacity threshold, determine that the current mining situation meets the preset switching condition, and switch to the second preset frequent item mining method to perform traversal mining on the currently mined frequent items to obtain corresponding mining results.

[0104] In some specific implementations, the traversal mining module 13 may specifically include:

[0105] a list combining unit, configured to combine the plurality of software configuration lists in the set of lists to be mined in pairs to obtain a plurality of corresponding list pairs;

[0106] a first configuration item determination unit, configured to respectively determine a plurality of intersections corresponding to the plurality of list pairs, determine a maximum common intersection corresponding to each of the plurality of list pairs based on the plurality of intersections, and determine the software configuration item in the maximum common intersection as a currently mined frequent item, so as to determine whether the current mining situation meets the preset switching condition based on the frequent item;

[0107] A step jump unit is used to determine the several maximum common intersections as the several software configuration lists for the next round of iteration, and jump to the step of combining the several software configuration lists in the set of lists to be mined in pairs to obtain corresponding several list pairs, until the number of intersections of the maximum common intersections is one, or the number of software configuration items in the maximum common intersection is lower than the preset software configuration item number threshold.

[0108] In some specific implementations, the traversal mining module 13 may specifically include:

[0109] an intersection combining unit, configured to combine two by two of the plurality of maximum common intersections currently mined by the first preset frequent item mining method to obtain a plurality of corresponding intersection pairs;

[0110] An intersection traversal unit, configured to traverse the maximum common intersections corresponding to the plurality of intersection pairs using a preset binary traversal method to generate a plurality of non-empty subsets of the plurality of intersection pairs;

[0111] A merging and statistical unit is used to determine the same software configuration items in the several non-empty subsets, and merge and count the software configuration lists associated with the same software configuration items to obtain the number of occurrences of the several non-empty subsets and the associated list; the mining results include the number of occurrences of the several non-empty subsets and the associated list.

[0112] In some specific implementations, the software package curing module 14 may specifically include:

[0113] a second configuration item determination unit, configured to determine, based on the mining result, software configuration items in the to-be-mined list set that meet a preset steady-state item determination condition as steady-state items; the preset steady-state item determination condition being a condition that a coverage rate of the plurality of software configuration lists is higher than a preset coverage rate threshold;

[0114] The software package solidification unit is used to encapsulate the determined steady-state items into a steady-state software package, and solidify the encapsulated steady-state software package into the software baseline core layer of the target UAV software, so as to perform state management of the target UAV software based on the software baseline core layer.

[0115] In some specific implementations, the drone software status management device may further include:

[0116] a status monitoring unit, configured to monitor the software status of the target drone software in real time through a preset distributed messaging system, so as to, after detecting and capturing a software configuration item change event of the target drone software, determine a changed software configuration item corresponding to the software configuration item change event and a plurality of software configuration lists to be updated related to the changed software configuration item;

[0117] a software package saving unit, configured to save the current version of the stable software package, so as to roll back the stable software package based on the current version when an exception occurs during the update process for the software configuration item change event;

[0118] A core layer updating unit is configured to replace the original version software configuration item corresponding to the changed software configuration item in the plurality of software configuration lists to be updated with the changed software configuration item, and use the obtained replaced software configuration list as the plurality of software configuration lists for the next round of mining, and jump to the step of traversing the plurality of software configuration lists to count the frequency of occurrence of each software configuration item in the plurality of software configuration lists, so as to update the software baseline core layer in response to the software configuration item change event.

[0119] Furthermore, the embodiment of the present application also discloses an electronic device, Figure 5 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of this diagram should not be construed as limiting the scope of application of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps of the drone software status management method disclosed in any of the aforementioned embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0120] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device. The communication protocol it follows is any communication protocol that can be applied to the technical solution of this application and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world. Its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0121] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or CD, etc. The resources stored thereon can include an operating system 221, a computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0122] The operating system 221 is used to manage and control the hardware devices on the electronic device 20 and the computer program 222, and can be Windows Server, Netware, Unix, Linux, etc. In addition to including computer programs capable of implementing the drone software status management method executed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0123] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when executed by a processor, the computer program implements the aforementioned method for managing the software state of a drone. The specific steps of this method can be found in the corresponding contents disclosed in the aforementioned embodiments and will not be further described here.

[0124] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. Reference can be made to the descriptions of the identical or similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and the relevant parts can be referred to the descriptions of the methods.

[0125] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0126] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0127] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0128] The above is a detailed introduction to the technical solution provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the ideas of the present application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for managing the software status of an unmanned aerial vehicle, characterized in that: include: Obtaining a plurality of software configuration lists of the input target drone software, and traversing the plurality of software configuration lists to count the occurrence frequency of each software configuration item in the plurality of software configuration lists; Filtering and sorting the software configuration items in the plurality of software configuration lists based on the occurrence frequencies, encoding the software configuration items according to the sorting results, and obtaining an encoded list set to be mined; If the current mining situation does not meet the preset switching condition, the software configuration items in the to-be-mined list set are iteratively mined using the first preset frequent item mining method, and during the mining process, when it is detected that the current mining situation meets the preset switching condition, the second preset frequent item mining method is switched to perform traversal mining on the currently mined frequent items to obtain corresponding mining results; The frequent items are software configuration items whose occurrence frequency is higher than a preset occurrence frequency threshold; Determine steady-state items in the to-be-mined list set based on the mining results, and solidify the steady-state software package containing the steady-state items into a software baseline core layer of the target UAV software, so as to perform state management of the target UAV software based on the software baseline core layer; The iterative mining of the software configuration items in the to-be-mined list set using the first preset frequent item mining method includes: Combining the plurality of software configuration lists in the set of lists to be mined in pairs to obtain a plurality of corresponding list pairs; Determining a plurality of intersections corresponding to the plurality of list pairs respectively, determining a maximum common intersection corresponding to each of the plurality of list pairs based on the plurality of intersections, and determining the software configuration items in the maximum common intersection as the currently mined frequent items, so as to determine whether the current mining situation meets the preset switching condition based on the frequent items; Determining the plurality of maximum common intersections as the plurality of software configuration lists for the next iteration, and jumping to the step of combining the plurality of software configuration lists in the set of lists to be mined, to obtain corresponding plurality of list pairs, until the number of intersections of the maximum common intersections is one, or the number of software configuration items in the maximum common intersections is lower than a preset software configuration item number threshold; The switching to the second preset frequent item mining method to traverse and mine the currently mined frequent items to obtain corresponding mining results includes: Combining the plurality of maximum common intersections currently mined by the first preset frequent item mining method in pairs to obtain a plurality of corresponding intersection pairs; Using a preset binary traversal method to traverse the maximum common intersections corresponding to the plurality of intersection pairs, so as to generate a plurality of non-empty subsets of the plurality of intersection pairs; Determine the same software configuration items in the several non-empty subsets, and merge and count the software configuration lists associated with the same software configuration items to obtain the number of occurrences of the several non-empty subsets and the associated list of lists; the mining results include the number of occurrences of the several non-empty subsets and the associated list of lists.

2. The method for managing the software status of a UAV according to claim 1, wherein: The filtering and sorting operations are performed on each software configuration item in the plurality of software configuration lists based on the occurrence frequency, and each software configuration item is encoded according to the sorting result to obtain an encoded list set to be mined, including: removing the software configuration items whose occurrence frequency is not higher than the preset occurrence frequency threshold from the software configuration lists to obtain a plurality of filtered software configuration lists; sorting the software configuration items in the filtered software configuration lists in descending order based on the frequencies of occurrence, and in the sorting process, sorting the software configuration items with consistent frequencies of occurrence in ascending order according to the triple dictionary of the software configuration items to obtain a number of sorted software configuration items; Sorting the plurality of filtered software configuration lists in ascending order according to their corresponding list identifiers to obtain a plurality of sorted software configuration lists; Software configuration item encoding is performed according to the sorting results of the plurality of sorted software configuration items, and list encoding is performed according to the sorting results of the plurality of sorted software configuration lists, so as to obtain an encoded list set to be mined.

3. The method for managing the software status of a UAV according to claim 1, wherein: If the current mining situation does not meet the preset switching condition, the software configuration items in the to-be-mined list set are iteratively mined using the first preset frequent item mining method, and during the mining process, when it is detected that the current mining situation meets the preset switching condition, the second preset frequent item mining method is switched to perform traversal mining on the currently mined frequent items to obtain corresponding mining results, including: Determine the number of the first type of software configuration items in the to-be-mined list set and the current memory status; If the number of the first type is greater than a preset type number threshold, or the memory condition indicates that the current available memory capacity is lower than a preset capacity threshold, it is determined that the current mining condition does not meet the preset switching condition, and the software configuration items in the to-be-mined list set are iteratively mined using a first preset frequent item mining method; During the mining process, the memory status and the number of the second type of frequent items currently mined are continuously monitored; If it is monitored that the number of the second type is not greater than the preset type number threshold, and the memory situation indicates that the current available memory capacity is not less than the preset capacity threshold, it is determined that the current mining situation meets the preset switching condition, and the second preset frequent item mining method is switched to perform traversal mining on the currently mined frequent items to obtain corresponding mining results.

4. The method for managing the software status of a UAV according to claim 1, wherein: The method further comprises: determining steady-state items in the to-be-mined list set according to the mining results, and solidifying the steady-state software package containing the steady-state items into the software baseline core layer of the target UAV software, so as to perform state management of the target UAV software based on the software baseline core layer, including: According to the mining results, the software configuration items in the to-be-mined list set that meet a preset steady-state item determination condition are determined as steady-state items; the preset steady-state item determination condition is a condition that the coverage rate of the plurality of software configuration lists is higher than a preset coverage rate threshold; The determined steady-state items are encapsulated into a steady-state software package, and the encapsulated steady-state software package is solidified into a software baseline core layer of the target UAV software, so as to perform state management of the target UAV software based on the software baseline core layer.

5. The method for managing the software status of a drone according to any one of claims 1 to 4, characterized in that: After solidifying the steady-state software package containing the steady-state items as the software baseline core layer of the target UAV software, the method further includes: The software status of the target drone software is monitored in real time through a preset distributed messaging system, so that after a software configuration item change event of the target drone software is detected and captured, a changed software configuration item corresponding to the software configuration item change event and a plurality of software configuration lists to be updated related to the changed software configuration item are determined; Saving the current version of the stable software package so that when an exception occurs during the update process for the software configuration item change event, the stable software package can be rolled back based on the current version; The changed software configuration item is used to replace the original version software configuration item corresponding to the changed software configuration item in the several software configuration lists to be updated, and the obtained replaced software configuration list is used as the several software configuration lists for the next round of mining, and the step of traversing the several software configuration lists to count the frequency of occurrence of each software configuration item in the several software configuration lists is jumped to, so as to update the software baseline core layer according to the software configuration item change event.

6. A drone software status management device, characterized in that: include: a list traversal module, configured to obtain a plurality of software configuration lists of the input target drone software, and traverse the plurality of software configuration lists to count the occurrence frequency of each software configuration item in the plurality of software configuration lists; a software configuration item sorting module, configured to filter and sort the software configuration items in the plurality of software configuration lists based on the occurrence frequencies, and encode the software configuration items according to the sorting results to obtain an encoded list set to be mined; a traversal mining module configured to iteratively mine the software configuration items in the to-be-mined list set using a first preset frequent item mining method if the current mining situation does not satisfy a preset switching condition, and, during the mining process, switch to a second preset frequent item mining method to perform traversal mining on the currently mined frequent items when it is detected that the current mining situation satisfies the preset switching condition, so as to obtain corresponding mining results; The frequent items are software configuration items whose occurrence frequency is higher than a preset occurrence frequency threshold; a software package solidification module, configured to determine steady-state items in the to-be-mined list set based on the mining results, and solidify the steady-state software package containing the steady-state items into the software baseline core layer of the target UAV software, so as to perform state management of the target UAV software based on the software baseline core layer; Wherein, the traversal mining module includes: a list combining unit, configured to combine the plurality of software configuration lists in the set of lists to be mined in pairs to obtain a plurality of corresponding list pairs; a first configuration item determination unit, configured to respectively determine a plurality of intersections corresponding to the plurality of list pairs, determine a maximum common intersection corresponding to each of the plurality of list pairs based on the plurality of intersections, and determine the software configuration item in the maximum common intersection as a currently mined frequent item, so as to determine whether the current mining situation meets the preset switching condition based on the frequent item; a step jump unit, configured to determine the plurality of maximum common intersections as the plurality of software configuration lists for the next iteration, and jump to the step of combining the plurality of software configuration lists in the set of lists to be mined, to obtain corresponding plurality of list pairs, until the number of intersections of the maximum common intersections is one, or the number of software configuration items in the maximum common intersections is lower than a preset software configuration item number threshold; Wherein, the traversal mining module includes: an intersection combining unit, configured to combine two by two of the plurality of maximum common intersections currently mined by the first preset frequent item mining method to obtain a plurality of corresponding intersection pairs; An intersection traversal unit, configured to traverse the maximum common intersections corresponding to the plurality of intersection pairs using a preset binary traversal method to generate a plurality of non-empty subsets of the plurality of intersection pairs; A merging and statistical unit is used to determine the same software configuration items in the several non-empty subsets, and merge and count the software configuration lists associated with the same software configuration items to obtain the number of occurrences of the several non-empty subsets and the associated list; the mining results include the number of occurrences of the several non-empty subsets and the associated list.

7. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the drone software status management method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that Used to store a computer program; wherein, when the computer program is executed by a processor, the drone software status management method according to any one of claims 1 to 5 is implemented.

Images