Unmanned aerial vehicle finished product data processing method, device and equipment and storage medium

Abstract

The invention discloses an unmanned aerial vehicle finished product data processing method and device, equipment and a storage medium, which are applied to the technical field of unmanned aerial vehicles, and the method comprises the steps: carrying out the hierarchy division of a to-be-stored finished product based on a preset rule, and generating a unique code containing a hierarchy and a hierarchy association relationship for each level of finished product; storing the unique codes and the hierarchical association relationship in a database to form a hierarchical mapping database association table, binding the attribute data of the finished products at all levels with the corresponding unique codes, and storing the attribute data and the corresponding unique codes in a finished product basic data table; based on the unique code, hierarchical bidirectional association is carried out on the to-be-stored finished product through the database association table, and a bidirectional tracing data chain is formed; and when a change instruction is received, querying the bidirectional tracing data chain based on a target finished product code in the change instruction to determine a to-be-changed finished product, and changing attribute data of the to-be-changed finished product in the finished product basic data table and hierarchical association relationship data in the database association table. The problems of finished product dispersion and low treatment efficiency are solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of unmanned aerial vehicles, and in particular to a method and device for processing finished product data of unmanned aerial vehicles, an equipment and a storage medium. BACKGROUND

[0002] With the vigorous development of the unmanned aerial vehicle industry, the processing level of the unmanned aerial vehicle on-board data is becoming more and more important. In the process of processing the unmanned aerial vehicle on-board data, the existing data processing method based on the EXCEL table excessively relies on manual work, and due to the large amount of data and the dispersion of the data of the unmanned aerial vehicle on-board data, it is easy to cause waste of human resources, and the reliability and accuracy of the data are difficult to guarantee. The existing processing method for the unmanned aerial vehicle on-board data based on the two-dimensional bar code does not completely break through the limitations of the traditional table mode for data processing, resulting in that the details related to the finished product technology state (such as the installation position of the digital-analog converter, the performance parameters, etc.) are scattered and fuzzy, which is not convenient for later use.

[0003] Therefore, how to solve the problems of low manual processing efficiency and difficult data dispersion association for the finished product data of the unmanned aerial vehicle, and form an efficient and comprehensive data processing system is a technical problem to be solved at present. SUMMARY

[0004] Therefore, the purpose of the present application is to provide a method and device for processing finished product data of unmanned aerial vehicles, an equipment and a storage medium, which solve the problems of low manual processing efficiency and difficult data dispersion association in the prior art.

[0005] To solve the above technical problems, the present application provides a method for processing finished product data of unmanned aerial vehicles, comprising:

[0006] The finished products to be warehoused are hierarchically divided based on a preset rule, and a unique code containing the hierarchy and the hierarchy association relationship is generated for each level of finished product; the preset rule is a rule formulated based on the physical composition logic of the unmanned aerial vehicle finished product;

[0007] The unique code and the hierarchy association relationship are stored in a database to form a hierarchy-mapped database association table, and the attribute data of each level of finished product is bound to the corresponding unique code and stored in a finished product basic data table;

[0008] Based on the unique code, the finished products to be warehoused are hierarchically and bidirectionally associated through the database association table to form a bidirectional traceability data chain;

[0009] When a change instruction is received, the bidirectional traceability data chain is queried based on the target finished product code in the change instruction to determine the finished product to be changed, and the attribute data of the finished product to be changed in the finished product basic data table and the hierarchy association relationship data in the database association table are synchronously changed.

[0010] Optionally, the finished products to be put into storage are hierarchically divided based on preset rules, and a unique code containing the hierarchy and hierarchical relationship is generated for each level of finished product, including:

[0011] The finished products to be put into the warehouse, as determined by the technical agreement documents, are classified into protocol-level finished products, and a protocol-level code with the protocol identifier as a prefix is ​​generated for the protocol-level finished products.

[0012] All finished products awaiting warehousing in the protocol-level finished products without a clear assembly position relationship are divided into sub-component-level finished products, and a sub-component-level code containing the corresponding protocol-level code prefix is ​​generated for the sub-component-level finished products;

[0013] Finished products awaiting warehousing that have a relative positional relationship and assembly relationship with the sub-component-level finished products are classified as accessory-level finished products, and accessory-level codes containing the prefix of the sub-component-level codes are generated for the accessory-level finished products.

[0014] Optionally, the database association table includes at least: a parent product code field, a child product code field, and an association type field; the parent product code field stores the unique code of the parent product; the child product code field stores the unique code of the child product; and the association type field stores an identifier character indicating a relationship or subordinate relationship.

[0015] Optionally, the finished product basic data table is provided with a primary key containing a unique coding field, and the primary key is associated with the parent product coding field and the child product coding field in the database association table as a foreign key.

[0016] Optionally, the bidirectional traceability data chain is stored in a tree structure, including a root node, intermediate nodes, and leaf nodes; the root node corresponds to the protocol-level finished product and stores the protocol-level code and protocol-level identifier; the intermediate node corresponds to the sub-component-level finished product and stores the sub-component-level code, a first parent node, and a sub-component-level identifier, wherein the first parent node is the protocol-level finished product to which the sub-component-level finished product belongs; the leaf node corresponds to the attachment-level finished product and stores the attachment-level code, a second parent node, and an attachment-level identifier, wherein the second parent node is the sub-component-level finished product to which the attachment-level finished product belongs.

[0017] Optionally, based on the target finished product code in the change instruction, the bidirectional traceability data chain is queried to determine the finished product to be changed, including:

[0018] In the bidirectional traceability data chain, the corresponding target node type and parent node code are determined according to the target finished product code;

[0019] Based on the target node type and the parent node code, upward and downward tracing are performed to obtain the finished product to be modified;

[0020] The upward tracing comprises: if the target node is an intermediate node, tracing to the corresponding root node in a tree structure with the parent node code as an index; if the target node is a leaf node, tracing to the corresponding intermediate node with the parent node code as an index, and tracing to the corresponding root node through the parent node code of the intermediate node;

[0021] The downward tracing comprises: if the target node is a root node, traversing all the intermediate nodes directly subordinate to the root node, and traversing the leaf nodes subordinate to each intermediate node; if the target node is an intermediate node, traversing all the leaf nodes directly subordinate to the intermediate node.

[0022] Optionally, after storing the unique code and the hierarchical association relationship into a database to form a hierarchical mapping database association table, and binding attribute data of products at each level with the corresponding unique code and storing into a product basic data table, the method further comprises:

[0023] setting a numerical model association field and a technical parameter field for the sub-component level product and the accessory level product in the product basic data table respectively;

[0024] binding the numerical model association field and the technical parameter field with the unique code of the corresponding product, and associating to the technical parameter field of the protocol level product through the unique code of the corresponding product;

[0025] The numerical model association field is used for storing a numerical model file path and numerical model parameters of the corresponding product, and the technical parameter field is used for storing performance indicators and material attributes of the corresponding product.

[0026] The application further provides a product data processing device of an unmanned aerial vehicle, comprising:

[0027] a division and coding module configured to divide products to be stored into products at different levels based on a preset rule, and generate a unique code containing the levels and the hierarchical association relationship for the products at different levels; the preset rule is a rule formulated based on the physical composition logic of the products of the unmanned aerial vehicle;

[0028] a mapping and binding module configured to store the unique code and the hierarchical association relationship into a database to form a hierarchical mapping database association table, and bind attribute data of the products at different levels with the corresponding unique code and store into a product basic data table;

[0029] a bidirectional association module configured to perform bidirectional association of the products to be stored in a hierarchical manner through the database association table based on the unique code, and form a bidirectional tracing data chain;

[0030] A product change module is configured to, when a change instruction is received, query the bidirectional tracing data chain based on a target product code in the change instruction, determine a product to be changed, and synchronously change attribute data of the product to be changed in the product basic data table and hierarchical association relationship data in the database association table.

[0031] The application further provides a UAV product data processing device, which comprises:

[0032] A memory is configured to store a computer program.

[0033] A processor is configured to execute the computer program to implement the UAV product data processing method.

[0034] The application further provides a computer readable storage medium, which stores computer executable instructions.

[0035] It can be seen that the application divides products to be stored into different levels based on preset rules, and generates unique codes containing levels and hierarchical association relationship for products in different levels; the preset rules are rules formulated based on the physical composition logic of UAV products; the unique codes and the hierarchical association relationship are stored into a database to form a hierarchical mapping database association table, and attribute data of products in different levels are bound to corresponding unique codes and stored into a product basic data table; based on the unique codes, the products to be stored are hierarchically bidirectionally associated through the database association table to form a bidirectional tracing data chain; when a change instruction is received, the bidirectional tracing data chain is queried based on a target product code in the change instruction to determine a product to be changed, and attribute data of the product to be changed in the product basic data table and hierarchical association relationship data in the database association table are synchronously changed. The application realizes the transformation of product data from manual association to automatic association by hierarchical division and unique code generation based on the physical composition logic of UAVs, combined with the structured storage of the database association table and the product basic data table, effectively solves the problem of low efficiency in traditional manual processing; the tracing data chain formed by hierarchical bidirectional association breaks the scattered state of product data in different levels, supports fast forward query and reverse tracing of products in different levels, and solves the pain point of difficult data association; and the synchronous updating mechanism based on the tracing data chain during change ensures the consistency of attribute data and hierarchical relationship, avoids the omission or mismatch that may occur during manual change, and overall improves the accuracy, efficiency and traceability of UAV product data management.

[0036] In addition, the application further provides a UAV product data processing device, equipment and computer readable storage medium, which also have the above beneficial effects. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0038] Figure 1 A flowchart of a method for processing finished UAV data provided in an embodiment of the present invention;

[0039] Figure 2 This is a schematic diagram of the structure of a UAV finished product data processing device provided in an embodiment of the present invention;

[0040] Figure 3 This is a schematic diagram of the structure of a UAV finished product data processing device provided in an embodiment of the present invention. Detailed Implementation

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

[0042] Please refer to Figure 1 , Figure 1 A flowchart illustrating a method for processing finished drone data according to an embodiment of the present invention. The method may include:

[0043] S101: Based on preset rules, the finished products to be put into the warehouse are divided into levels, and a unique code containing the level and the relationship between levels is generated for each level of finished product; the preset rules are rules formulated based on the physical composition logic of the UAV finished products.

[0044] The execution subject in this embodiment is a terminal. This embodiment does not limit the type of terminal, as long as it can perform the operation of the UAV finished product data processing method. The purpose of this step is to establish a clear hierarchical and identifiable basic identification system for the finished products to be stored, based on the rules of the UAV's physical structure. This ensures that the hierarchy and coding accurately map the physical composition of the UAV, providing a basic framework consistent with the actual product structure for subsequent data association and traceability.

[0045] Further, the above-mentioned preset rule-based hierarchical division of the to-be-warehoused finished product, and the generation of a unique code containing the hierarchy and hierarchy association relationship for each level of finished product, can specifically include:

[0046] Step 11: The to-be-warehoused finished product determined by the technical protocol file is divided into a protocol-level finished product, and a protocol-level code with a protocol identifier as a prefix is generated for the protocol-level finished product.

[0047] Step 12: All to-be-warehoused finished products in the protocol-level finished product that have no explicit assembly location relationship are divided into sub-assembly-level finished products, and a sub-assembly-level code containing the prefix of the corresponding protocol-level code is generated for the sub-assembly-level finished product.

[0048] Step 13: The to-be-warehoused finished product that has a relative position relationship and an assembly relationship with the sub-assembly-level finished product is divided into an accessory-level finished product, and an accessory-level code containing the prefix of the corresponding sub-assembly-level code is generated for the accessory-level finished product.

[0049] Specifically, according to the actual physical composition logic of the finished product of the unmanned aerial vehicle (such as the assembly relationship of “whole machine-core component-accessory part”), the to-be-warehoused finished product is divided into different levels. For example, it can be generally divided into a protocol level (a finished product determined by a separate signed finished product technical protocol / joint research and development protocol / finished product technical requirement / contract, etc. file, which is the highest level), a sub-assembly level (all entity finished products in the same protocol that have no explicit assembly location relationship, which belong to the protocol level), and an accessory level (accessory finished products of the sub-assembly, which have an explicit relative position relationship and an assembly relationship with the sub-assembly-level finished product, such as finished product cables, structural parts, assembly accessories, etc., which belong to the sub-assembly level), to ensure that the hierarchical division is consistent with the actual physical structure of the finished product of the unmanned aerial vehicle, rather than being arbitrarily classified. A unique code is generated for each level of finished product, and the code itself needs to directly reflect two layers of information: one is the self-level (such as the protocol level identified by the “XY-” prefix, the sub-assembly level identified by the “ZJ-” prefix, and the accessory level identified by the “FJ-” prefix); and the other is the association relationship with the upper-level finished product (such as the sub-assembly-level code containing the code prefix of the corresponding protocol level, and the accessory-level code containing the code prefix of the corresponding sub-assembly level). For example, the protocol-level finished product code is “XY-12345678”, the sub-assembly-level finished product code thereof can be “ZJ-XY-12345678-01”, and the accessory-level finished product code of the sub-assembly can be “FJ-ZJ-XY-12345678-01-01”, so that the level of a finished product and its upper-level belonging can be directly determined through the code.

[0050] S102: Store the unique code and the hierarchy association relationship to a database to form a database association table of the hierarchical mapping, and bind the attribute data of each level of finished product to the corresponding unique code and store it to a finished product basic data table.

[0051] The step is implemented by sub-table storage to realize the structured management of the unmanned aerial vehicle finished product data, and the hierarchical relationship is clear and the attribute information is completely saved. It needs to be explained that the database association table in the embodiment at least includes: a superior finished product code field, a subordinate finished product code field and an association type field; the superior finished product code field stores the unique code of the upper level finished product; the subordinate finished product code field stores the unique code of the lower level finished product; and the association type field stores the identification character of the containing relationship or the accessory relationship. Specifically, the core field of the table is around the “unique code”, for example, containing “superior finished product code”, “subordinate finished product code”, “association type” (such as “contains” and “accessory”) and the like, which directly maps the membership relationship of each level of finished product. For example, the “containing relationship” between the protocol level finished product “XY-12345678” and the subcomponent level finished product “ZJ-XY-12345678-01”, and the “accessory relationship” between the accessory level finished product “FJ-ZJ-XY-12345678-01” and the subcomponent level finished product, are stored in the form of code correspondence in this table. Its role is like a “hierarchical relationship dictionary”, which quickly queries who the upper level of a finished product is and what the lower level is, and provides a direct relationship basis for subsequent bidirectional tracing.

[0052] It needs to be explained that the finished product basic data table in the embodiment is provided with a unique code field as a primary key, and the primary key and the superior finished product code field and the subordinate finished product code field in the database association table form a foreign key association. Specifically, the attribute data is the detailed characteristics of the finished product, such as the approval record of the protocol level finished product, the technical index threshold, the performance parameter (such as working temperature) of the subcomponent level finished product, the digital-analog path, the material of the accessory level finished product, the installation parameter and the like; and the binding with the unique code means that these attribute data are associated with the corresponding finished product (for example, the attribute data of “ZJ-XY-12345678-01” will be explicitly bound to the code), so as to ensure that each attribute data can be accurately corresponded to a specific finished product. The role of this table is like a “finished product archive”, which stores the detailed information of all finished products for query or change. The two tables are linked through the unique code: the database association table is responsible for recording who belongs to the hierarchical relationship, and the finished product basic data table is responsible for recording which attributes each finished product has, so that the division of labor is clear and related, which not only avoids the relationship confusion or data redundancy caused by single table storage, but also provides a structured data basis for subsequent bidirectional tracing and synchronous change.

[0053] S103: Based on the unique code, the finished product to be stored is bidirectionally associated in a hierarchical manner through the database association table, and a bidirectional tracing data chain is formed.

[0054] The step utilizes the previously stored codes and hierarchical relationships to construct a bidirectional queryable association chain to realize fast tracing of the superior-inferior relationship between finished products. Specifically, the database association table of the previous hierarchical mapping (which stores the corresponding relationship of "superior code-inferior code-association type") is used to directly obtain the superior-inferior association information of a certain finished product. For example, to know which sub-components the protocol-level finished product "XY-12345678" contains, the record of "superior code = XY-12345678" in the association table can be queried to directly obtain all corresponding sub-component codes. To know which sub-component the accessory-level finished product "FJ-ZJ-XY-12345678-01-01" belongs to, the record of "inferior code = the accessory code" in the association table can be queried to obtain the corresponding sub-component code. Bidirectional tracing of the data chain refers to constructing two tracing directions: forward association: tracing from the superior finished product to the inferior finished product (such as protocol level -> sub-component level -> accessory level), and finding all subordinate finished products through the database association table layer by layer to form an "upward" association path; reverse association: tracing from the inferior finished product to the superior finished product (such as accessory level -> sub-component level -> protocol level), and finding all superior finished products through the association table layer by layer to form a "downward" association path. Bidirectional tracing of the data chain refers to integrating the above forward and reverse hierarchical association paths into a complete chain, and each node (finished product) in the chain is bound to the superior and inferior nodes through a unique code and can be directly jumped and queried. For example, the data chain can quickly locate the upstream protocol-level finished product and all downstream accessories of a certain sub-component from any finished product (such as a certain sub-component), realizing the effect of one-key tracing of the whole chain.

[0055] It should be noted that the bidirectional tracing data chain in the embodiment is stored in a tree structure, which can include root nodes, intermediate nodes, and leaf nodes; the root nodes correspond to the protocol-level finished products and store the protocol-level codes and protocol-level identifiers; the intermediate nodes correspond to the sub-component-level finished products and store the sub-component-level codes, first parent nodes, and sub-component-level identifiers, and the first parent nodes are the protocol-level finished products to which the sub-component-level finished products belong; the leaf nodes correspond to the accessory-level finished products and store the accessory-level codes, second parent nodes, and accessory-level identifiers, and the second parent nodes are the sub-component-level finished products to which the accessory-level finished products belong. Specifically, the bidirectional tracing data chain in the embodiment is stored in a tree structure, which directly reflects the hierarchical association of the finished products: the root nodes correspond to the protocol-level finished products, store the protocol-level codes and identifiers, and are the top of the entire tree; the intermediate nodes correspond to the sub-component-level finished products, store the sub-component codes, identifiers, and first parent nodes (i.e., the information of the protocol-level finished products to which they belong), and are associated with the root nodes; the leaf nodes correspond to the accessory-level finished products, store the accessory codes, identifiers, and second parent nodes (i.e., the information of the sub-component-level finished products to which they belong), and are associated with the intermediate nodes. This structure associates the superior and inferior finished products through the parent nodes layer by layer, so that the affiliation relationship between the superior and inferior finished products is clear at a glance, facilitating fast tracing.

[0056] S104: When receiving the change instruction, based on the target product code in the change instruction, the two-way trace data chain is queried to determine the to-be-changed product, and the attribute data of the to-be-changed product in the product basic data table and the hierarchical association relationship data in the database association table are synchronously changed.

[0057] When receiving the change instruction, first, the target product code in the instruction is used to query the two-way trace data chain to find all to-be-changed products related to the target product (including the associated products at the upper and lower levels); then, the attribute information (such as performance parameters, digital model paths, etc.) of the to-be-changed products in the product basic data table and the hierarchical relationship (such as the upper and lower level attribution relationship) in the database association table are synchronously updated, to ensure that the data is consistent after the change.

[0058] Further, when receiving the change instruction, based on the target product code in the change instruction, the two-way trace data chain is queried to determine the to-be-changed product, which can specifically include: in the two-way trace data chain, the corresponding target node type and parent node code are determined according to the target product code; the target node type and the parent node code are used for upward tracing and downward tracing to obtain the to-be-changed product. The upward tracing includes: if the target node is an intermediate node, the parent node code is used as an index to trace to the corresponding root node in the tree structure; if the target node is a leaf node, the parent node code is used as an index to trace to the corresponding intermediate node, and the parent node code of the intermediate node is used to trace to the corresponding root node; the downward tracing includes: if the target node is a root node, all direct subordinates of the intermediate node of the root node are traversed, and the leaf nodes subordinate to each intermediate node are traversed; if the target node is an intermediate node, all direct subordinates of the leaf node of the intermediate node are traversed.

[0059] Specifically, it can be divided into two steps: first, in the two-way trace data chain, the corresponding node (root node, intermediate node, or leaf node) of the target product is found according to the code of the target product, and the parent node code (i.e. the code of the direct superior) is found. Second, according to the node type and the parent node code, the associated products are found in two directions: upward tracing (finding the superior): if it is an intermediate node (sub-assembly level), the parent node code is used to find the corresponding root node (protocol level); if it is a leaf node (accessory level), the sub-assembly level code is used to find the intermediate node first, and then the parent node code of the intermediate node is used to find the root node (protocol level). Downward tracing (finding the subordinate): if it is a root node (protocol level), all subordinates of the intermediate node (sub-assembly level) and the leaf nodes subordinate to these intermediate nodes (accessory level) are found; if it is an intermediate node (sub-assembly level), all subordinates of the leaf node (accessory level) are found. Through the two steps, all products that need to be changed together can be determined.

[0060] Further, after storing the unique code and the hierarchical relationship to the database, forming the hierarchical mapping database association table, and binding the attribute data of each level of finished product with the corresponding unique code and storing it to the finished product basic data table, it can further include: setting a digital model association field and a technical parameter field for the sub-component level finished product and the accessory level finished product in the finished product basic data table respectively; binding the digital model association field and the technical parameter field with the unique code of the corresponding finished product, and associating to the technical parameter field of the corresponding protocol level finished product through the unique code of the corresponding finished product; wherein the digital model association field is used to store the digital model file path and the digital model parameter of the corresponding finished product; the technical parameter field is used to store the performance index and the material attribute of the corresponding finished product. This embodiment further improves the finished product basic data table, which can also be divided into two steps: first, add two fields in the table for the sub-component level and the accessory level finished product respectively: the digital model association field (store the digital model file path and the digital model parameter), and the technical parameter field (store the performance index and the material attribute). Second, bind the two fields with the unique code of the corresponding sub-component / accessory (ensure the correct data ownership), and associate to the technical parameter field of the protocol level finished product to which the sub-component / accessory belongs through the code of the sub-component / accessory, so as to ensure that the parameters of the sub-component and the accessory correspond to the technical requirements of the upper protocol level. In this way, by specially setting the digital model association field and the technical parameter field, the digital model information (such as file path and parameter) and the technical characteristics (such as performance and material) of the sub-component and the accessory have fixed storage positions, avoiding data mixing and facilitating quick query and call; by binding the fields with the corresponding finished product through the unique code and then associating to the technical parameters of the corresponding protocol level, it is ensured that the digital model and the technical data of the sub-component and the accessory can be accurately corresponded to the specific finished product, and the technical requirements of the upper protocol level form a "upper and lower level checking relationship", avoiding parameter mismatch (such as sub-component performance not meeting the protocol level index); if necessary in the future, to check the digital model version and verify the compliance of the technical parameters, or to update the related data synchronously when changing, the corresponding sub-component, accessory and protocol level finished product can be directly located through the code, without cross-table scattered query, improving the accuracy and efficiency of data management.

[0061] The unmanned aerial vehicle finished product data processing method provided by the embodiment of the application comprises the following steps: S101: performing hierarchical division on to-be-warehoused finished products based on a preset rule, and generating a unique code containing the hierarchy and a hierarchy association relationship for each level of finished products; the preset rule is a rule formulated based on the physical composition logic of the unmanned aerial vehicle finished products; S102: storing the unique code and the hierarchy association relationship into a database, forming a hierarchical mapping database association table, and binding attribute data of each level of finished products with the corresponding unique code and storing the attribute data into a finished product basic data table; S103: performing hierarchical bidirectional association on the to-be-warehoused finished products based on the unique code through the database association table, and forming a bidirectional traceability data chain; and S104: when a change instruction is received, querying the bidirectional traceability data chain based on a target finished product code in the change instruction, determining to-be-changed finished products, and synchronously changing attribute data of the to-be-changed finished products in the finished product basic data table and hierarchy association relationship data in the database association table. Through hierarchical division and unique code generation based on the physical composition logic of the unmanned aerial vehicle, combined with the structured storage of the database association table and the finished product basic data table, the finished product data is changed from manual to automatic association, effectively solving the problem of low efficiency in traditional manual processing; the traceability data chain formed through hierarchical bidirectional association breaks the scattered state of the finished product data of each level, supports fast forward query and reverse tracing of the finished products of each level, and solves the pain point of data association difficulty; and the synchronous updating mechanism based on the traceability data chain during the change ensures the consistency of the attribute data and the hierarchy relationship, avoids the omission or mismatch that may occur during manual change, and overall improves the accuracy, efficiency and traceability of unmanned aerial vehicle finished product data management.

[0062] The unmanned aerial vehicle finished product data processing device provided by the embodiment of the application will be introduced below, and the unmanned aerial vehicle finished product data processing device described below can be correspondingly referred to with the unmanned aerial vehicle finished product data processing method described above.

[0063] For details, please refer to Figure 2 , Figure 2 A structure diagram of the unmanned aerial vehicle finished product data processing device provided by the embodiment of the application can comprise:

[0064] The division and coding module 100 is configured to perform hierarchical division on to-be-warehoused finished products based on a preset rule, and generate a unique code containing the hierarchy and a hierarchy association relationship for each level of finished products; the preset rule is a rule formulated based on the physical composition logic of the unmanned aerial vehicle finished products;

[0065] The mapping and binding module 200 is configured to store the unique code and the hierarchy association relationship into a database, form a hierarchical mapping database association table, and bind attribute data of each level of finished products with the corresponding unique code and store the attribute data into a finished product basic data table;

[0066] The bidirectional association module 300 is configured to perform hierarchical bidirectional association on the products to be warehoused based on the unique codes and the database association table, and form a bidirectional traceability data chain.

[0067] The product change module 400 is configured to query the bidirectional traceability data chain based on a target product code in a change instruction when the change instruction is received, determine a product to be changed, and synchronously change attribute data of the product to be changed in the product basic data table and hierarchical association relationship data in the database association table.

[0068] Based on the above embodiment, the dividing and coding module 100 can include:

[0069] The first dividing unit is configured to divide the products to be warehoused determined by the technical protocol file into protocol-level products, and generate protocol-level codes with a protocol identifier as a prefix for the protocol-level products.

[0070] The second dividing unit is configured to divide all the products to be warehoused without an explicit assembly position relationship in the protocol-level products into sub-assembly-level products, and generate sub-assembly-level codes containing a prefix of the protocol-level code to which the sub-assembly-level products belong.

[0071] The third dividing unit is configured to divide the products to be warehoused having a relative position relationship and an assembly relationship with the sub-assembly-level products into accessory-level products, and generate accessory-level codes containing a prefix of the sub-assembly-level code to which the accessory-level products belong.

[0072] Based on the above embodiment, the database association table at least includes: a superior product code field, a subordinate product code field, and an association type field; the superior product code field stores a unique code of a superior product; the subordinate product code field stores a unique code of a subordinate product; and the association type field stores an identification character of a containing relationship or an accessory relationship.

[0073] Based on the above embodiment, the product basic data table is provided with a primary key of a unique code field, and the primary key forms a foreign key association with the superior product code field and the subordinate product code field in the database association table.

[0074] Based on the above embodiment, the bidirectional traceability data chain is stored in a tree structure, including a root node, an intermediate node, and a leaf node; the root node corresponds to a protocol-level product, and stores a protocol-level code and a protocol-level identifier; the intermediate node corresponds to a sub-assembly-level product, and stores a sub-assembly-level code, a first parent node, and a sub-assembly-level identifier, the first parent node being a protocol-level product to which the sub-assembly-level product belongs; and the leaf node corresponds to an accessory-level product, and stores the accessory-level code, a second parent node, and an accessory-level identifier, the second parent node being a sub-assembly-level product to which the accessory-level product belongs.

[0075] Based on the above embodiments, the finished product changing module 400 can include:

[0076] A determination unit is configured to determine a corresponding target node type and a parent node code according to the target finished product code in the bidirectional traceability data chain.

[0077] A to-be-changed finished product determination unit is configured to perform upward and downward tracing according to the target node type and the parent node code to obtain the to-be-changed finished product. The upward tracing includes: if the target node is an intermediate node, indexing the parent node code to trace to a corresponding root node in a tree structure; if the target node is a leaf node, indexing the parent node code to trace to a corresponding intermediate node, and tracing to a corresponding root node through the parent node code of the intermediate node. The downward tracing includes: if the target node is a root node, traversing all direct subordinate intermediate nodes of the root node and traversing leaf nodes subordinate to each intermediate node; if the target node is an intermediate node, traversing all direct subordinate leaf nodes of the intermediate node.

[0078] Based on the above embodiments, the unmanned aerial vehicle finished product data processing apparatus can further include:

[0079] A field setting module is configured to, after storing the unique codes and the hierarchical association relationship into a database to form a hierarchical mapping database association table and binding attribute data of finished products at each level with corresponding unique codes and storing the attribute data into a finished product basic data table, set a digital model association field and a technical parameter field for sub-component level finished products and accessory level finished products in the finished product basic data table, respectively.

[0080] A binding module is configured to bind the digital model association field and the technical parameter field with unique codes of corresponding finished products and associate the unique codes of the corresponding finished products to technical parameter fields of protocol level finished products. The digital model association field is configured to store a digital model file path and digital model parameters of corresponding finished products. The technical parameter field is configured to store performance indicators and material properties of corresponding finished products.

[0081] It should be noted that the order of the modules and units in the above unmanned aerial vehicle finished product data processing apparatus can be changed without affecting the logic.

[0082] The unmanned aerial vehicle finished product data processing device provided by the embodiment of the application comprises a division and coding module 100, which is configured to divide the to-be-warehoused finished product into different levels based on a preset rule and generate a unique code for each level of finished product, wherein the preset rule is a rule formulated based on the physical composition logic of the unmanned aerial vehicle finished product; a mapping and binding module 200, which is configured to store the unique code and the level correlation into a database to form a database correlation table of level mapping and bind the attribute data of each level of finished product with the corresponding unique code and store the attribute data into a finished product basic data table; a bidirectional correlation module 300, which is configured to perform bidirectional correlation of the to-be-warehoused finished product in a hierarchical manner based on the unique code through the database correlation table to form a bidirectional traceability data chain; and a finished product change module 400, which is configured to, when a change instruction is received, query the bidirectional traceability data chain based on the target finished product code in the change instruction, determine the to-be-changed finished product, and synchronously change the attribute data of the to-be-changed finished product in the finished product basic data table and the level correlation data in the database correlation table. The device realizes the change of finished product data from manual to automatic correlation by hierarchical division and unique code generation based on the physical composition logic of the unmanned aerial vehicle, combined with the structured storage of the database correlation table and the finished product basic data table, effectively solves the problem of low efficiency in traditional manual processing, the traceability data chain formed by the hierarchical bidirectional correlation breaks the dispersed state of the finished product data at different levels, supports fast forward query and reverse tracing of the finished product at different levels, solves the pain point of data correlation difficulty, and the synchronous updating mechanism based on the traceability data chain during the change ensures the consistency of the attribute data and the level correlation, avoids the omission or mismatch that may occur during manual change, and overall improves the accuracy, efficiency and traceability of the unmanned aerial vehicle finished product data management.

[0083] The unmanned aerial vehicle finished product data processing device provided by the embodiment of the application is described below, and the unmanned aerial vehicle finished product data processing device described below can be correspondingly referred to the unmanned aerial vehicle finished product data processing method described above.

[0084] Please refer to Figure 3 , Figure 3 The structure diagram of the unmanned aerial vehicle finished product data processing device provided by the embodiment of the application can comprise:

[0085] The memory 10 is configured to store a computer program.

[0086] The processor 20 is configured to execute the computer program to implement the unmanned aerial vehicle finished product data processing method described above.

[0087] The memory 10, the processor 20 and the communication interface 31 can communicate with each other through the communication bus 32.

[0088] In the embodiment of the present application, the memory 10 stores one or more programs, which can include program codes including computer operation instructions. In the embodiment of the present application, the memory 10 can store programs for implementing the following functions:

[0089] The to-be-warehoused finished products are hierarchically divided based on preset rules, and unique codes containing the hierarchy and the hierarchy association relationship are generated for the finished products of each level; the preset rules are rules formulated based on the physical composition logic of the unmanned aerial vehicle finished products;

[0090] The unique codes and the hierarchy association relationship are stored into a database to form a database association table of hierarchy mapping, and the attribute data of the finished products of each level is bound to the corresponding unique codes and stored into a finished product basic data table;

[0091] Based on the unique codes, the to-be-warehoused finished products are hierarchically and bidirectionally associated through the database association table to form a bidirectional traceability data chain;

[0092] When receiving a change instruction, the bidirectional traceability data chain is queried based on the target finished product code in the change instruction to determine the to-be-changed finished product, and the attribute data of the to-be-changed finished product in the finished product basic data table and the hierarchy association relationship data in the database association table are synchronously changed.

[0093] In a possible implementation, the memory 10 can include a program storage area and a data storage area. The program storage area can store an operating system and at least one application required by a function, etc. The data storage area can store data created in the use process.

[0094] In addition, the memory 10 can include a read-only memory and a random access memory, and provide instructions and data for the processor. Part of the memory can also include an NVRAM. The memory stores an operating system and operation instructions, executable modules or data structures, or subsets thereof, or an extended set thereof, wherein the operation instructions can include various operation instructions for implementing various operations. The operating system can include various system programs for implementing various basic tasks and processing hardware-based tasks.

[0095] The processor 20 can be a central processing unit (CPU), an application-specific integrated circuit, a digital signal processor, a field programmable gate array or other programmable logic device. The processor 20 can be a microprocessor or any conventional processor, etc. The processor 20 can invoke the program stored in the memory 10.

[0096] The communication interface 31 can be an interface of a communication module, used for connecting with other devices or systems.

[0097] Of course, it needs to be explained that Figure 3 The structure shown does not constitute a limitation on the unmanned aerial vehicle finished product data processing device in the embodiments of the application, and in actual application, the unmanned aerial vehicle finished product data processing device can include more or fewer components than Figure 3 those shown, or combine certain components.

[0098] The computer readable storage medium provided by the embodiments of the application is introduced below, and the computer readable storage medium described below can be referred to each other corresponding to the unmanned aerial vehicle finished product data processing method described above.

[0099] The application also provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to realize the steps of the unmanned aerial vehicle finished product data processing method described above.

[0100] The computer readable storage medium can include a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0101] The embodiments in the specification are described in a progressive manner, and each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other. For the device disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple, and the related parts can be referred to the method part.

[0102] The professional person can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed in the present application can be realized by electronic hardware, computer software or combination of the two, in order to clearly show the interchangeability of hardware and software, the composition and steps of each example have been described in the above description. The functions are described in general. Whether the functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. The professional person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0103] Finally, it needs to be explained that, in this document, relationships such as first and second, and the like, are intended to distinguish one entity or action from another, without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises", "comprising", or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus.

[0104] The unmanned aerial vehicle finished product data processing method, device, equipment and computer readable storage medium provided by the present application are introduced in detail above, the principle and implementation mode of the present application are described in this document, the above embodiment is only used to help understand the method and core idea of the present application; At the same time, for those skilled in the art, according to the idea of the present application, the specific implementation mode and application range will be changed; In view of the above, the content of the specification should not be understood as a limitation of the present application.

Claims

1. A method for processing finished UAV data, characterized in that, include: Based on preset rules, the finished products to be put into the warehouse are divided into levels, and a unique code containing the level and the relationship between the levels is generated for each level of finished products. The preset rules are rules formulated based on the physical composition logic of the finished UAV product; The unique code and the hierarchical relationship are stored in the database to form a hierarchical mapping database association table, and the attribute data of each level of finished product are bound to the corresponding unique code and stored in the finished product basic data table. Based on the unique code, the finished products to be put into the warehouse are hierarchically linked in a bidirectional manner through the database association table to form a bidirectional traceability data chain. When a change instruction is received, the bidirectional traceability data chain is queried based on the target finished product code in the change instruction to determine the finished product to be changed, and the attribute data of the finished product to be changed in the finished product basic data table and the hierarchical relationship data in the database association table are changed synchronously.

2. The UAV finished product data processing method according to claim 1, characterized in that, Based on preset rules, the finished products to be put into storage are hierarchically divided, and a unique code containing the hierarchy and hierarchical relationship is generated for each level of finished product, including: The finished products to be put into the warehouse, as determined by the technical agreement documents, are classified into protocol-level finished products, and a protocol-level code with the protocol identifier as a prefix is ​​generated for the protocol-level finished products. All finished products awaiting warehousing in the protocol-level finished products without a clear assembly position relationship are divided into sub-component-level finished products, and a sub-component-level code containing the corresponding protocol-level code prefix is ​​generated for the sub-component-level finished products; Finished products awaiting warehousing that have a relative positional relationship and assembly relationship with the sub-component-level finished products are classified as accessory-level finished products, and accessory-level codes containing the prefix of the sub-component-level codes are generated for the accessory-level finished products.

3. The UAV finished product data processing method according to claim 1, characterized in that, The database association table includes at least: a parent product code field, a child product code field, and an association type field; the parent product code field stores the unique code of the parent product; the child product code field stores the unique code of the child product; and the association type field stores an identifier character that indicates a relationship or subordinate relationship.

4. The UAV finished product data processing method according to claim 3, characterized in that, The finished product basic data table has a primary key with a unique coding field, and the primary key is associated with the parent product coding field and the child product coding field in the database association table as a foreign key.

5. The UAV finished product data processing method according to claim 1, characterized in that, The bidirectional traceability data chain is stored in a tree structure, including a root node, intermediate nodes, and leaf nodes. The root node corresponds to the protocol-level finished product and stores the protocol-level code and protocol-level identifier. The intermediate node corresponds to the sub-component-level finished product and stores the sub-component-level code, the first parent node, and the sub-component-level identifier. The first parent node is the protocol-level finished product to which the sub-component-level finished product belongs. The leaf node corresponds to the attachment-level finished product and stores the attachment-level code, the second parent node, and the attachment-level identifier. The second parent node is the sub-component-level finished product to which the attachment-level finished product belongs.

6. The UAV finished product data processing method according to claim 5, characterized in that, Based on the target product code in the change instruction, the bidirectional traceability data chain is queried to determine the product to be changed, including: In the bidirectional traceability data chain, the corresponding target node type and parent node code are determined according to the target finished product code; Based on the target node type and the parent node code, upward and downward tracing are performed to obtain the finished product to be modified; The upward tracing includes: if the target node is an intermediate node, then tracing back to the corresponding root node in the tree structure using the parent node code as an index; if the target node is a leaf node, then tracing back to the corresponding intermediate node using the parent node code as an index, and tracing back to the corresponding root node through the parent node code of the intermediate node. The downward tracing includes: if the target node is the root node, then traversing all the directly subordinate intermediate nodes of the root node, and traversing the leaf nodes under each intermediate node; if the target node is an intermediate node, then traversing all the directly subordinate leaf nodes of the intermediate node.

7. The UAV finished product data processing method according to any one of claims 1 to 6, characterized in that, After storing the unique code and the hierarchical association in the database to form a hierarchical mapping database association table, and binding the attribute data of each level of finished product with the corresponding unique code and storing it in the finished product basic data table, the method further includes: In the finished product basic data table, set up a digital model association field and a technical parameter field for sub-component-level finished products and accessory-level finished products respectively; The digital model association field and the technical parameter field are bound to the unique code of the corresponding finished product, and the unique code of the corresponding finished product is associated with the technical parameter field of the finished product of the corresponding protocol level; The digital model association field is used to store the digital model file path and digital model parameters of the corresponding finished product; the technical parameter field is used to store the performance indicators and material properties of the corresponding finished product.

8. A data processing device for finished unmanned aerial vehicles (UAVs), characterized in that, include: The segmentation and coding module is used to segment finished products to be put into the warehouse into levels based on preset rules, and generate a unique code for each level of finished product that includes the level and the relationship between the levels. The preset rules are rules formulated based on the physical composition logic of the finished UAV product; The mapping and binding module is used to store the unique code and the hierarchical association relationship in the database to form a database association table of hierarchical mapping, and to bind the attribute data of each level of finished product with the corresponding unique code and store it in the finished product basic data table; The bidirectional association module is used to perform hierarchical bidirectional association of the finished products to be put into the warehouse based on the unique code and through the database association table to form a bidirectional traceability data chain. The finished product modification module is used to query the bidirectional traceability data chain based on the target finished product code in the modification instruction when a modification instruction is received, determine the finished product to be modified, and synchronously modify the attribute data of the finished product to be modified in the finished product basic data table and the hierarchical relationship data in the database association table.

9. A data processing device for finished unmanned aerial vehicles (UAVs), characterized in that, include: Memory, used to store computer programs; A processor is configured to implement the UAV finished product data processing method as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when loaded and executed by a processor, implement the UAV finished product data processing method as described in any one of claims 1 to 7.

Images