A knowledge base generation method and device, electronic equipment and storage medium

Abstract

Embodiments of the present application provide a knowledge base generation method and device, electronic equipment and storage medium, and relate to the field of databases, and include: obtaining to-be-created business shelf information; obtaining parameter values corresponding to the target business object, and determining general master data tags in the target knowledge tag according to matching of the target knowledge tag and existing general knowledge tags in a database, and obtaining a specific business object; finding a corresponding existing hierarchical framework in the database; obtaining the existing hierarchical framework and adding the specific business object to the existing hierarchical framework; associating nodes in the added existing hierarchical framework with corresponding parameter values to obtain a target hierarchical framework; and generating a sub-knowledge base corresponding to the business shelf information based on the target hierarchical framework. In the embodiments of the present application, the construction of a sub-knowledge base can be supported according to user requirements and selected tags, thereby reducing development costs.

Description

Technical Field

[0001] This invention relates to the field of databases, and more particularly to a method, apparatus, electronic device, and storage medium for generating a knowledge base. Background Technology

[0002] In the automotive industry, after years of product design, development, and information technology construction, a massive amount of data has been accumulated in all aspects of vehicle research and development.

[0003] In related technologies, separate knowledge base platforms are generated for various business processes in vehicle R&D, resulting in low efficiency and high development costs for knowledge sharing. Summary of the Invention

[0004] Embodiments of the present invention provide a knowledge base generation method, apparatus, electronic device, and storage medium, which can reuse at least a portion of existing business data through a specially established tagging system, and can support the selection of relevant business data to construct new sub-knowledge bases corresponding to business shelves according to user needs.

[0005] To achieve the above objectives, the embodiments of the present invention adopt the following technical solutions:

[0006] Firstly, a knowledge base generation method is provided, including:

[0007] Obtain the business shelf information to be created; the vehicle business shelf information to be created includes the target vehicle business object and at least one target knowledge tag;

[0008] If the database contains business master data corresponding to the target vehicle business object, obtain the parameter value corresponding to the target business object, and determine the general master data tag in the target knowledge tag by matching the target knowledge tag with the existing general knowledge tag in the database, and obtain the proprietary business object.

[0009] Based on the vehicle business object and the general master data tag, search for the corresponding existing hierarchical framework in the database;

[0010] If the existing hierarchical framework exists, obtain the existing hierarchical framework and add the proprietary business object to the existing hierarchical framework;

[0011] The nodes in the existing hierarchical framework after the addition are associated with the corresponding parameter values ​​to obtain the target hierarchical framework;

[0012] Based on the target hierarchical framework, a sub-knowledge base corresponding to the business shelf information is generated.

[0013] Optionally, associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​after the addition includes:

[0014] Based on the general master data tags, determine the corresponding first target data model.

[0015] Based on the first target data model, the first knowledge topic corresponding to the first target data model is invoked;

[0016] Using the first knowledge topic, obtain the parameter values ​​corresponding to the general master data tags from the data pool;

[0017] Associate the parameter value with the general master data label in the hierarchical framework.

[0018] Optionally, associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​after the addition includes:

[0019] Receive parameter values ​​input for the proprietary service object and associate the parameter values ​​with the proprietary service object.

[0020] Optionally, after searching the database for the corresponding existing hierarchical framework based on the vehicle business object and the general master data tag, the method further includes:

[0021] If the at least one target knowledge tag includes a proprietary tag other than the general master data tag, the proprietary tag shall be added to the existing hierarchical framework.

[0022] The step of associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​to obtain the target hierarchical framework includes:

[0023] Based on the proprietary tags, determine the corresponding second target data model.

[0024] Based on the second target data model, the second knowledge topic corresponding to the second target data model is invoked;

[0025] The parameter values ​​corresponding to the proprietary tags are obtained from the data pool using the second knowledge topic.

[0026] Associate the parameter value with the proprietary tag in the hierarchical framework.

[0027] Optionally, after obtaining the business shelf information to be created, the process further includes:

[0028] If the database does not contain business master data corresponding to the shelf name, create the business master data corresponding to the shelf information to be created.

[0029] Optionally, after searching the database for the corresponding existing hierarchical framework based on the vehicle business object and the general master data tag, the method further includes:

[0030] In the absence of the existing hierarchical framework, a new hierarchical framework is created based on the vehicle business object and the general master data tag.

[0031] Optionally, after generating a sub-knowledge base corresponding to the business shelf information based on the target hierarchical framework, the method further includes:

[0032] Based on the user's corresponding user tag, push data from the sub-knowledge base that matches the user tag to the user.

[0033] Secondly, embodiments of this application provide a knowledge base generation apparatus, including:

[0034] The business shelf acquisition module is used to acquire business shelf information to be created; the vehicle business shelf information to be created includes the target vehicle business object and at least one target knowledge tag;

[0035] The first data acquisition module is used to acquire the parameter value corresponding to the target business object when the database contains the business master data corresponding to the target vehicle business object, and to determine the general master data tag in the target knowledge tag by matching the target knowledge tag with the existing general knowledge tag in the database, and to acquire the proprietary business object.

[0036] The hierarchical framework lookup module is used to search for the corresponding existing hierarchical framework in the database based on the vehicle business object and the general master data tag.

[0037] The hierarchical framework operation module is used to obtain the existing hierarchical framework when it exists, and to add the proprietary business object to the existing hierarchical framework.

[0038] The association module is used to associate the nodes in the existing hierarchical framework after they have been added with the corresponding parameter values ​​to obtain the target hierarchical framework.

[0039] The module is used to generate a sub-knowledge base corresponding to the business shelf information based on the target hierarchical framework.

[0040] Thirdly, embodiments of this application provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor executes the computer program to implement the steps of the aforementioned method.

[0041] Fourthly, embodiments of this application provide a computer-readable storage medium storing a program that, when executed by a processor, implements the steps of the aforementioned method.

[0042] This application provides a knowledge base generation method. It allows setting corresponding tags for various knowledge items in a data pool. For developers, targeting a specific vehicle business object, target knowledge tags can be selected based on requirements. If corresponding business master data exists in the database based on the target vehicle business object, reusable general master data tags can be determined based on these target knowledge tags. Then, based on the vehicle business object and the general master data tags, existing reusable hierarchical frameworks can be found. A new target hierarchical framework corresponding to the target vehicle business object is then constructed within this existing framework. Sub-knowledge bases can then be built and published based on these target hierarchical frameworks, allowing other personnel to perform related operations. Thus, the tag system enables the reuse of existing knowledge and hierarchical frameworks, reusing at least some existing business data, and supports the selection of tags for sub-knowledge base construction based on user needs, reducing development costs. Attached Figure Description

[0043] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings:

[0044] Figure 1 A flowchart illustrating the steps of a knowledge base generation method provided in an embodiment of the present invention;

[0045] Figure 2 A structural block diagram of a database system provided in an embodiment of the present invention;

[0046] Figure 3 This is a structural block diagram of another database system provided in an embodiment of the present invention;

[0047] Figure 4 A flowchart illustrating the steps of another knowledge base generation method provided in this embodiment of the invention;

[0048] Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0049] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0050] Unless the context otherwise requires, throughout the specification and claims, the term "comprising" is interpreted as open-ended and encompassing, meaning "including, but not limited to." In the description of the specification, terms such as "one embodiment," "some embodiments," "exemplary embodiment," "example," "specific example," or "some examples" are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this application. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific feature, structure, material, or characteristic may be included in any suitable manner in any one or more embodiments or examples.

[0051] Additionally, it should be noted that when describing the elements and embodiments thereof in this application, the articles “a,” “an,” “the,” and “the” are intended to indicate the presence of one or more elements; unless otherwise stated, “multiple” means two or more; the terms “comprising,” “including,” “containing,” and “having” are intended to be inclusive and indicate that additional elements may exist besides those listed; the terms “first,” “second,” “third,” etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or order of formation.

[0052] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0053] Reference Figure 1 This application provides a knowledge base generation method, which includes:

[0054] Step S102: Obtain the business shelf information to be created; the vehicle business shelf information to be created includes the target vehicle business object and at least one target knowledge tag;

[0055] It should be noted that, in the embodiments of this application, a database system can be pre-set, referring to... Figure 2 The system may include: a middle platform layer 1 and a business unit model layer 2;

[0056] The middle platform layer 1 may include a shelf label management module 11, a shelf template management module 12, a shelf structure management module 13, and a shelf knowledge management module 14;

[0057] The shelf label management module 11 is used to manage labels in the database through the business unit model layer 2; for example, the shelf label management module 11 can be used to add, delete or modify at least one of the database system labels.

[0058] The database system's tags include tags for various knowledge such as parts, vehicle models, personnel, and business operations. It can also include user tags, which may include user role tags, user behavior tags, etc.

[0059] The shelf template management module 12 is used to manage templates in the database through the business unit model layer 2;

[0060] In this embodiment, the shelf template management module 12 is used to manage templates in the database. For example, the shelf template management module 12 can be used to add templates to the database, delete templates from the sub-knowledge base 2, and modify at least one of the templates in the database.

[0061] Shelf structure management module 13 is used to manage the structure of each sub-knowledge base through business unit model layer 2;

[0062] In this embodiment, the shelf structure management module 13 is used to manage the structure of the sub-knowledge base 2. For example, the shelf structure management module 13 can be used to add to the structure of the sub-knowledge base 2, delete from the structure of the sub-knowledge base 2, or modify at least one of the following:

[0063] The structure and template can be part of a hierarchical framework. The structure can be various levels divided for business, and each structure can be at least one level. For example, taking the engine business as an example, it can be divided into level one: engine; level two: 1.5 displacement engine, 2.0 displacement engine, naturally aspirated engine, turbocharged engine, etc. Under level two, templates can be set for each node. For example, under turbocharged engine, templates such as gear and electric motor can be set as nodes.

[0064] The shelf knowledge management module 14 is used to create new sub-knowledge bases or modify knowledge in existing knowledge bases;

[0065] In this embodiment, the shelf knowledge management module 14 can execute steps S102-S112 to create a new sub-knowledge base 2. The shelf knowledge management module 14 can also be used to input, validate, and manipulate data, and manage the data relationships between data.

[0066] The sub-knowledge base is used to store vehicle R&D business data for the corresponding business.

[0067] Optional, refer to Figure 2 The business unit model layer 2 includes:

[0068] Business model design module 21, theme accumulation module 22, and data ingestion module 23;

[0069] The business model design module 21 is used to design the business model of the sub-knowledge base 2; the business model design module 21 can be used to add the business model of the sub-knowledge base 2, modify the business model of the sub-knowledge base 2, and delete the business model of the sub-knowledge base 2 at least one of these.

[0070] A business model can call at least one data topic. For example, a business model can include one data topic, such as an external brand data model that can call an external brand topic; or, a data model can call multiple data topics, such as a parts data model library that can call a parts name topic, a parts size parameter data topic, and a parts test data topic.

[0071] The theme accumulation module 22 is used to manage various themes, such as adding, deleting or modifying data themes.

[0072] The data theme can collect specific business data. For example, the theme accumulation module 22 can collect data from the online business data based on the data theme; or, the theme accumulation module 22 can collect data from other business data based on the data theme.

[0073] A data topic acquires data from at least one business data source and transmits it upwards. For example, the evaluation item topic can collect data from rating data, evaluation point data, recommended content data, and evaluation image data; each business data source includes a large amount of knowledge and corresponding tags.

[0074] In some implementations, the business model includes both a data model and an algorithm rule model.

[0075] The data entry module 23 is used to store vehicle R&D business data in the database.

[0076] The data entry module 23 stores the vehicle R&D business data collected by the theme sedimentation module 22 in the sub-data pool.

[0077] For the business unit model layer 2, it can include a business model design module, a theme accumulation module, and a data lake entry module. The structure of the business unit model layer 2 is a tree structure, which is subdivided sequentially from the business model design module to the theme accumulation module and then to the data lake entry module.

[0078] Optional, refer to Figure 3 The business model includes a data model and an algorithm rule model;

[0079] The data model includes at least one of the following: component data model, vehicle model data model, whole vehicle structure model, self-service analysis model, common data comparison model, shelf label model, external brand data model, and internal and external brand correspondence model;

[0080] Each data model is called by the middle platform to implement corresponding data processing functions. For example, the component data model is used to call the corresponding component topic to obtain component-related data and analyze and process the data according to the first preset rule. Similarly, the vehicle model data model is used to call the corresponding vehicle topic to obtain vehicle-related data and analyze and process the data according to the second preset rule. The vehicle structure model is used to call the corresponding vehicle structure topic to obtain vehicle structure-related data and analyze and process the data according to the third preset rule. The self-service analysis model is used to call the corresponding self-service analysis topic to obtain data and analyze the query results according to the fourth preset rule. The common data comparison model is used to compare the commonalities among multiple vehicle models or multiple business objects according to the fifth preset rule. The shelf label model is used to call the label topic to manage the labels of various business data according to the sixth preset rule. Finally, the external brand data model is used to call the external brand topic to obtain external brand-related data and analyze and process the data according to the seventh preset rule. For example, the internal and external brand correspondence model is used to call the internal and external brand theme to obtain relevant data on internal and external brands, and to analyze and process the data according to the eighth preset rule.

[0081] The algorithm rule model includes at least one of the following: retrieval algorithm rule model, tag algorithm rule model, and recommendation algorithm rule model.

[0082] Each data model is called by the middle platform to implement corresponding algorithm processing functions. For example, the retrieval algorithm rule model is used to query the sub-knowledge base according to preset rules and return the corresponding results when a query field is received. Another example is the tag algorithm rule model, which is used to find corresponding tags according to preset rules based on keywords entered by the user. Yet another example is the recommendation algorithm rule model, where at least one of the models recommends knowledge from various sub-knowledge bases to the user based on their user tags.

[0083] It should be noted that the above data models are only a partial list, and users can create new data models according to their actual needs.

[0084] Among them, reference Figure 3 The component data model can call the component name data topic, and the component name data topic can obtain data from the component name business data;

[0085] The vehicle model data model calls the vehicle model data topic, which can obtain data from the vehicle model data business data.

[0086] The vehicle structure model can call the vehicle structure data topic, and the vehicle structure data topic can obtain the vehicle structure function layer name from the business data of the vehicle structure function name;

[0087] The self-service analytics model can call self-service analytics topics, and self-service analytics topics can obtain data from business data such as self-service analytics data;

[0088] The external brand data model can call the external brand theme, which can obtain data from the business data of the specific name of the external brand.

[0089] The same principle applies to other cases, and will not be elaborated upon here.

[0090] In some embodiments, the data subject also includes:

[0091] The evaluation items include ratings, evaluation points, recommended content, and evaluation images;

[0092] The topic of dimensional parameters includes rearview mirror length and steering wheel diameter;

[0093] Functional definition themes include central locking and electric child locks.

[0094] Of course, the above-mentioned topics allow you to set parsing rules for various formats of business data, extracting data from that data according to the corresponding rules. This eliminates the need to use business data from existing data sources, further reducing development costs.

[0095] Of course, for newly added business data, it can be specified that it be generated in a standard format, which can reduce subsequent maintenance costs.

[0096] Of course, if new formats of business data are added, parsing rules for the new formats can be added to each topic.

[0097] This application provides several data models and algorithm rule models. The database can systematically store data, unify the management of various business data in vehicle R&D, reduce the cost of data management and application, and improve the efficiency of knowledge sharing.

[0098] Optionally, the middle platform layer 1 also includes an update module 15;

[0099] Update module 15 is used to add functionality to the middleware layer 1.

[0100] Among them, the update module 15 can also be called the continuous accumulation module. During the use of the database system, with the development of technology, the middle platform layer 1 may need to add other functional modules. The update module 15 can be used to add functions to the middle platform layer 1 and improve the applicability of the database system.

[0101] It should be noted that the middle platform layer 1 may also include at least one of the following: information query module 16, retrieval and recommendation module 17, single sign-on authentication module 18, personnel permission management module 19, process processing module 110, master data query module 111, and document management module 112.

[0102] The information query module 16 is used to query the data stored in all sub-knowledge bases; for example, the information query module 16 can be used to query the vehicle structure information or part information of the Bill of Material (BOM).

[0103] The search recommendation module 17 is used to push relevant knowledge matching the user's search behavior. This relevant knowledge may be different from the search results of the search behavior, or it may include the search results.

[0104] For example, the retrieval recommendation module 17 can be used to perform a retrieval based on a single tag, or the retrieval recommendation module can also be used to perform a retrieval based on multiple tags. This application embodiment does not specifically limit this.

[0105] In some embodiments, the retrieval and recommendation module 17 can proactively recommend relevant knowledge to users based on role tags and behavior tags. For example, if a user has the role tag of a vehicle R&D engineer and the behavior tag of developing a vehicle rearview mirror, the module can proactively push relevant information about vehicle rearview mirrors to the user, thereby improving the efficiency of knowledge reuse.

[0106] The single sign-on authentication module 18 is used to authenticate the user's login information. For example, for multiple sub-knowledge bases 2, a user only needs to log in sequentially to access all sub-knowledge bases 2; or, it can mutually authenticate with other systems, and after logging into other mutually authenticated systems, the user can directly access sub-knowledge base 2.

[0107] The personnel access control module 19 is used to configure user permissions. For example, the personnel access control module 19 can be used to configure access permissions for a user's sub-knowledge base 2.

[0108] The process processing module 110 is used to process the processes of the database system.

[0109] The master data query module 111 is used to query the master data of the database system. In some embodiments, the master data includes user information, customer information, organizational structure, supplier information, etc.

[0110] The document management module 112 is used to manage documents in the database system. In some embodiments, the documents include log documents, and the document management module 112 can be used to manage log documents.

[0111] After constructing the database system described above, steps S102-S112 can be executed to create the sub-knowledge base.

[0112] It should be noted that the vehicle business object may include business objects such as vehicle R&D, vehicle styling R&D, vehicle powertrain R&D, transmission R&D, computer-aided engineering R&D, and prototype testing, etc., and this application embodiment does not limit it. Therefore, the target vehicle business object can be a specific business object targeted by the technical personnel.

[0113] In this embodiment, a technician can open a business shelf information entry interface in the database system interface of the electronic device, and then enter the business shelf information to be created in the business shelf information entry interface. Specifically, the target vehicle business object and at least one target knowledge tag can be entered, and the electronic device obtains the business shelf information to be created based on the user's input.

[0114] In the aforementioned data input module, the knowledge tags correspond to knowledge stored in the data pool. Taking a component as an example, the component name can be used as a knowledge tag, and then the component's shape, size, and other parameters can be stored accordingly.

[0115] In practical applications, a knowledge tag query control can be set up in the business shelf information entry interface. Technicians can enter keywords in the control and then click the knowledge tag query control. The knowledge tag query control then calls the shelf tag model to query the database to see if there is a knowledge tag corresponding to the keyword and displays at least one candidate knowledge tag that matches the keyword. The user can then select one or more of the candidate tags, and the electronic device will determine the target knowledge tag based on the user's selection.

[0116] Step S104: If the database contains business master data corresponding to the target vehicle business object, obtain the parameter value corresponding to the target business object, and determine the general master data tag in the target knowledge tag by matching the target knowledge tag with the existing general knowledge tag in the database, and obtain the proprietary business object.

[0117] In this embodiment of the application, the business master data can be a main object that runs through the business, such as a project identifier, which corresponds to the project source code of the general data of the business.

[0118] In this embodiment, after step S102, a technician can determine whether the target vehicle business object exists. If it exists, the technician can click the confirmation control. After receiving the confirmation, the electronic device proceeds to step S104, where the business shelf information entry interface can jump to the data confirmation interface. Alternatively, the electronic device can automatically analyze whether the business master data corresponding to the target vehicle business object exists.

[0119] Of course, the target vehicle business object entered by the technician can be text, such as "engine". The technician can then determine whether the target vehicle business object exists based on the list of business master data. Alternatively, electronic devices can also match the text of the target vehicle business object with the text corresponding to the project code to determine whether the target vehicle business object exists.

[0120] Then, if the database contains the business master data corresponding to the target vehicle business object, the parameter values ​​of the target vehicle business object can be obtained. For example, for the engine business object, its project identifier can be obtained. In practice, the parameter values ​​can be entered by technical personnel, who can then input the parameter values ​​into the input controls corresponding to the target vehicle business object on the data confirmation interface.

[0121] Furthermore, these target knowledge tags can be checked to see if any general knowledge tags exist and to identify those general knowledge tags. It should be noted that this confirmation process can be performed manually by technicians based on a list of general knowledge tags, or automatically by electronic devices. In the case of manual identification, technicians can select and confirm on the data confirmation interface. In the case of automatic identification by electronic devices, the electronic device can store general knowledge tags in a preset list, and then match the target knowledge tag against this preset list to confirm the general knowledge tag.

[0122] The knowledge corresponding to the general knowledge tag is general data. General data is data that can be shared by two or more sub-knowledge bases. Reusing general data can save development costs. General data can be data that affects the parameters of the whole vehicle, such as displacement data, which can be used by engine R&D and also by the whole vehicle structure.

[0123] In addition, it is possible to create a dedicated business object and parameter values ​​for the business to which the business shelf information to be created belongs, based on the characteristics of the business.

[0124] For example, in the business of engine research and development, the key teeth of the engine are a proprietary business object that is not used in other businesses and is unique to the engine business. In this case, the technicians can create the proprietary business object and its parameter values ​​through the proprietary business object creation control in the data confirmation interface.

[0125] For example, the concentration of fragrance is unique to the vehicle air conditioning R&D business. The concentration parameters of fragrances such as light, standard and strong are not used in other businesses. The fragrance concentration is proprietary business data of vehicle air conditioning R&D. Technicians can create the fragrance concentration and its parameter values ​​through the proprietary business object creation control in the data confirmation interface.

[0126] Step S106: Based on the vehicle business object and the general master data tag, search for the corresponding existing hierarchical framework in the database;

[0127] It should be noted that, as mentioned earlier, this hierarchical framework may include a structure and / or templates. The structure can be divided into at least two layers, with the target vehicle business object as the root node. The template is the layer below the leaf nodes of the last layer of the structure. It can be understood that the structure and templates can be combined to form a hierarchical framework.

[0128] Once the parameter values, general master data tags, and proprietary business objects corresponding to the target business object are determined, it can be determined whether there is a usable hierarchical framework in the project source code corresponding to the project identifier.

[0129] In practical applications, template knowledge tags can serve as node identifiers for the template layer, templates can be associated with specific knowledge, and hierarchical structure facilitates querying. Of course, in this case, the vehicle business object and the aforementioned general master data tags can be matched with an existing hierarchical framework. If a match is found, a reusable hierarchical framework exists, eliminating the need to create a new one and saving development costs.

[0130] Of course, target knowledge tags can also serve as stage identifiers for intermediate levels, or correspond to knowledge at corresponding levels. In this case, structures and templates can be matched separately. If these tags match a structure, the structure can be reused; if no template is matched, a new template can be created, or a template associated with the structure can be used directly. If these tags match some templates, the templates can be reused, but the structure is not matched, so the structure needs to be recreated. If both match, both can be reused.

[0131] Taking engine R&D as an example of vehicle business objects, by using the keywords of engine R&D and matching with common master data tags such as 1.5 displacement, 2.0 displacement, turbocharged, and naturally aspirated, we can match the root node of engine R&D and the secondary nodes of 1.5 displacement, 2.0 displacement, turbocharged, and naturally aspirated.

[0132] For example, in the vehicle air conditioning R&D business, by using keywords related to vehicle air conditioning R&D and matching them with tags such as tube-plate type, tube-strip type, water-cooled type, and air-cooled type, it is possible to match the structural root node of vehicle air conditioning R&D with the secondary nodes of tube-plate type, tube-strip type, water-cooled type, and air-cooled type.

[0133] For example, in the R&D of vehicle air conditioning systems, tags such as shell-and-tube condenser and shell-and-tube condenser can be used to match the condenser category template of water-cooled secondary nodes.

[0134] Alternatively, if there is no condenser category template in the water-cooled secondary node, you can add the corresponding professional business objects for shell-and-tube condensers and tubular condensers in the water-cooled secondary node.

[0135] Step S108: If the existing hierarchical framework exists, obtain the existing hierarchical framework and add the proprietary business object to the existing hierarchical framework.

[0136] As described above, if an existing hierarchical framework exists, it can be reused. However, if an existing hierarchical framework is reused, it may not meet the current business requirements. Therefore, for proprietary business objects, they can be added to the existing hierarchical framework using the proprietary business object as a node identifier. For example, if a structure matches but the template is insufficient, the proprietary business object can be added as a child node of the structure.

[0137] In this embodiment, the aforementioned data confirmation interface can redirect to a hierarchical framework settings interface, where users can add proprietary business objects to the existing hierarchical framework. For example, if a structure is reused, the user can add a proprietary business object to a leaf node of the structure that is compatible with that proprietary business object. The electronic device can then add the proprietary business object to the existing hierarchical framework based on the user's addition operation.

[0138] Step S110: Associate the nodes in the existing hierarchical framework after the addition with the corresponding parameter values ​​to obtain the target hierarchical framework;

[0139] After completing step S108, the hierarchical framework is set up. At this point, each node can be associated with its corresponding parameter value. Of course, if the knowledge is only in the child nodes of the set hierarchical framework, the knowledge data corresponding to the knowledge tags of the child nodes can be obtained, and then associated with the child nodes to obtain the target hierarchical framework.

[0140] Step S112: Based on the target hierarchical framework, generate a sub-knowledge base corresponding to the business shelf information.

[0141] Finally, since the target hierarchical framework has both a knowledge architecture hierarchy and related specific data, a sub-knowledge base corresponding to the business shelf information can be generated based on this architecture and then published.

[0142] Once the sub-knowledge base is published, the data can be applied. For example, it can be provided to other developers for querying, analysis, and tracking. It should be noted that this sub-knowledge base can also serve as the source code for the project corresponding to the target vehicle business object.

[0143] This application provides a knowledge base generation method. It allows setting corresponding tags for various knowledge items in a data pool. For developers, targeting a specific vehicle business object, target knowledge tags can be selected based on requirements. If corresponding business master data exists in the database based on the target vehicle business object, reusable general master data tags can be determined based on these target knowledge tags. Then, based on the vehicle business object and the general master data tags, existing reusable hierarchical frameworks can be found. A new target hierarchical framework corresponding to the target vehicle business object is then constructed within this existing framework. Sub-knowledge bases can then be built and published based on these target hierarchical frameworks, allowing other personnel to perform related operations. Thus, the tag system enables the reuse of existing knowledge and hierarchical frameworks, reusing at least some existing business data, and supports the selection of tags for sub-knowledge base construction based on user needs, reducing development costs.

[0144] Reference Figure 4 This application provides another method for generating a knowledge base, which includes:

[0145] Step S202: Obtain the business shelf information to be created; the vehicle business shelf information to be created includes the target vehicle business object and at least one target knowledge tag;

[0146] This step is the same as step S102 mentioned above, and will not be described in detail here.

[0147] Step S204: If the database does not contain business master data corresponding to the shelf name, create business master data corresponding to the business shelf information to be created.

[0148] In this application embodiment, there may be situations where the current business lacks reusable business master data. In such cases, a common master data creation interface can be provided, where technicians can edit the data. The interface can then call up different functions based on the edited content. Figure 3 The system includes modules such as shelf label management and shelf knowledge management. These modules then call the business unit model layer to create general business master data for reuse by other businesses in the future.

[0149] For example, the business master data for the engine object can be reused in both engine R&D and vehicle R&D. However, the corresponding sub-databases for both engine R&D and vehicle R&D are not generated, and the business master data for the engine object is also not generated. In this case, technical personnel can open the common master data creation interface and edit it, such as compiling the source code of the engine object-related project. The interface can then call the appropriate functions based on the edited content. Figure 3 The system includes modules such as shelf label management and shelf knowledge management. These modules then call the business unit model layer to create business master data for a common engine object, which can then be reused by other business processes.

[0150] Step S206: If the database contains business master data corresponding to the target vehicle business object, obtain the parameter value corresponding to the target business object, and determine the general master data tag in the target knowledge tag by matching the target knowledge tag with the existing general knowledge tag in the database, and obtain the proprietary business object.

[0151] This step is the same as step S104 mentioned above, and will not be described in detail here.

[0152] Step S208: Based on the vehicle business object and the general master data tag, search for the corresponding existing hierarchical framework in the database;

[0153] This step is the same as step S106 mentioned above, and will not be described in detail here.

[0154] Step S210: If the existing hierarchical framework does not exist, create a new hierarchical framework based on the vehicle business object and the general master data tag.

[0155] In this embodiment of the application, as described above, if there is no reusable hierarchical framework, a new hierarchical framework can be created based on the vehicle business object and the general master data tag.

[0156] For example, if there is a non-reusable structure, a new structure can be created, such as by calling the shelving structure management module.

[0157] For example, if there are non-reusable templates, you can create new ones, such as by calling the shelf template management module.

[0158] Step S212: If the existing hierarchical framework exists, obtain the existing hierarchical framework and add the proprietary business object to the existing hierarchical framework.

[0159] This step is the same as step S108 mentioned above, and will not be described in detail here.

[0160] Step S214: Associate the nodes in the existing hierarchical framework after the addition with the corresponding parameter values ​​to obtain the target hierarchical framework;

[0161] This step is the same as step S110 mentioned above, and will not be described in detail here.

[0162] Step S216: Based on the target hierarchical framework, generate a sub-knowledge base corresponding to the business shelf information.

[0163] This step is the same as step S112 mentioned above, and will not be described in detail here.

[0164] Step S218: Based on the user tag corresponding to the user, push data from the sub-knowledge base that matches the user tag to the user.

[0165] In this embodiment, user tags may include role tags and behavior tags. After a user performs a certain behavior, a behavior tag can be assigned to that user. Then, the electronic device can search for knowledge matching the role tag and / or behavior tag from various sub-knowledge bases based on the role tag and / or behavior tag and recommend it to the user, making it easier for the user to understand the knowledge and indirectly improving the reuse rate of knowledge.

[0166] Optionally, in step S214, associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​after the addition includes:

[0167] Sub-step A11: Determine the corresponding first target data model based on the general master data label;

[0168] Sub-step A12: Based on the first target data model, call the first knowledge topic corresponding to the first target data model;

[0169] Sub-step A13: Obtain the parameter value corresponding to the general master data tag from the data pool through the first knowledge topic;

[0170] Sub-step A14: Associate the parameter value with the general master data label in the hierarchical framework.

[0171] In this embodiment, the data lake module stores various business data and the correspondence between tags and knowledge. To read business data from various data sources, this application employs a three-layer structure: a business model layer, a main data accumulation layer, and a data lake layer. The business model layer provides services to the middle platform algorithm, which in turn provides services to the front end. Each topic can read data from one or more business data sources. A model can call one or more topics.

[0172] Therefore, for a general master data tag, the corresponding first target data model is determined based on the general master data tag. For example, if the general master data tag is a component tag, then based on the correspondence between the model and the topic, the first target data model is determined to be a component data model. Then, based on the component data model, the component name topic corresponding to the component data model is called. Then, based on the correspondence between the topic and business data, the parameter values ​​corresponding to the general master data tag in the component name topic are read from the data pool through the component name topic. The topic then returns the read data to the model for processing. If necessary, the model then returns the processed data to the middle platform for further processing. This reduces the traversal scope and improves efficiency.

[0173] Optionally, in step 214, associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​includes:

[0174] Sub-step A21: Receive parameter values ​​input for the proprietary service object and associate the parameter values ​​with the proprietary service object.

[0175] In this embodiment, the parameter value of a proprietary business object may not exist in the data pool. Therefore, a proprietary business object parameter input control can be provided to receive user input, obtain the parameter value of the proprietary business object, and then associate the parameter value with the proprietary business object. This provides a more flexible parameter setting method.

[0176] Optionally, in step 208, after searching the database for the corresponding existing hierarchical framework based on the vehicle business object and the general master data tag, the method further includes:

[0177] Step 209: If the at least one target knowledge tag includes a proprietary tag other than the general master data tag, add the proprietary tag to the existing hierarchical framework.

[0178] In this embodiment, there may be target knowledge tags that users need but are not general master data tags. In such cases, this approach can add proprietary tags other than general data tags to the aforementioned hierarchical framework. Of course, these proprietary tags can be added as templates under the corresponding leaf nodes of the structure.

[0179] In step 214, associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​to obtain the target hierarchical framework includes:

[0180] Sub-step A31: Determine the corresponding second target data model based on the proprietary tag.

[0181] Sub-step A32: Based on the second target data model, call the second knowledge topic corresponding to the second target data model;

[0182] Sub-step A33: Obtain the parameter value corresponding to the proprietary tag from the data pool through the second knowledge topic;

[0183] Sub-step A34: Associate the parameter value with the proprietary tag in the hierarchical framework.

[0184] Similar to the data acquisition method of general data tags mentioned above, since the data pool already contains proprietary tags and their knowledge, a similar method can be used to determine the second target data model corresponding to the proprietary tag. Then, the second target data model calls the second knowledge topic corresponding to the second target data model, and the second knowledge topic reads data from the corresponding business data and returns it.

[0185] This application provides a knowledge base generation method. It allows setting corresponding tags for various knowledge items in a data pool. For developers, targeting a specific vehicle business object, target knowledge tags can be selected based on requirements. If corresponding business master data exists in the database based on the target vehicle business object, reusable general master data tags can be determined based on these target knowledge tags. Then, based on the vehicle business object and the general master data tags, existing reusable hierarchical frameworks can be found. A new target hierarchical framework corresponding to the target vehicle business object is then constructed within this existing framework. A sub-knowledge base can then be built and published based on this target hierarchical framework, allowing other personnel to perform related operations. Thus, the tag system enables the reuse of existing knowledge and hierarchical frameworks, reusing at least a portion of existing business data. It also supports the selection of tags for sub-knowledge base construction based on user needs, reducing development costs. This application also allows for flexible recommendation of relevant knowledge based on user tags, improving knowledge reuse efficiency. This application embodiment constructs a sub-knowledge base generation framework, which can provide users with knowledge input, approval, query, comparison and self-service analysis functions to meet the business management data accumulation knowledge needs, and at the same time provide a research and development knowledge page to provide unified knowledge retrieval and recommendation services.

[0186] Based on the above embodiments, this invention also provides a knowledge base generation apparatus, comprising:

[0187] The business shelf acquisition module is used to acquire business shelf information to be created; the vehicle business shelf information to be created includes the target vehicle business object and at least one target knowledge tag;

[0188] The first data acquisition module is used to acquire the parameter value corresponding to the target business object when the database contains the business master data corresponding to the target vehicle business object, and to determine the general master data tag in the target knowledge tag by matching the target knowledge tag with the existing general knowledge tag in the database, and to acquire the proprietary business object.

[0189] The hierarchical framework lookup module is used to search for the corresponding existing hierarchical framework in the database based on the vehicle business object and the general master data tag.

[0190] The hierarchical framework operation module is used to obtain the existing hierarchical framework when it exists, and to add the proprietary business object to the existing hierarchical framework.

[0191] The association module is used to associate the nodes in the existing hierarchical framework after they have been added with the corresponding parameter values ​​to obtain the target hierarchical framework.

[0192] The module is used to generate a sub-knowledge base corresponding to the business shelf information based on the target hierarchical framework.

[0193] Optionally, the associated module includes:

[0194] The first model determination submodule is used to determine the corresponding first target data model based on the general master data label.

[0195] The first subject determination submodule is used to call the first knowledge topic corresponding to the first target data model based on the first target data model.

[0196] The first parameter acquisition module is used to obtain the parameter value corresponding to the general master data tag from the data pool through the first knowledge topic;

[0197] The first association submodule is used to associate the parameter value with the general master data label in the hierarchical framework.

[0198] Optionally, the associated module includes:

[0199] The parameter receiving submodule is used to receive parameter values ​​input for the proprietary business object and associate the parameter values ​​with the proprietary business object.

[0200] Optionally, following the hierarchical framework operation module, the following module may also be included:

[0201] A proprietary tag adding module is used to add proprietary tags to the existing hierarchical framework when the at least one target knowledge tag includes proprietary tags other than the general master data tags.

[0202] The associated module includes:

[0203] The second determining submodule is used to determine the corresponding second target data model based on the proprietary label.

[0204] The second subject determination submodule is used to call the second knowledge topic corresponding to the second target data model based on the second target data model.

[0205] The second parameter determination submodule is used to obtain the parameter value corresponding to the proprietary tag from the data pool through the second knowledge topic;

[0206] The second sub-association module is used to associate the parameter value with the proprietary tag in the hierarchical framework.

[0207] Optionally, after the business shelf acquisition module, the system further includes:

[0208] The master data creation module is used to create the business master data corresponding to the business shelf information to be created when the database does not have the business master data corresponding to the shelf name.

[0209] Optionally, after the hierarchical framework lookup module, the system further includes:

[0210] The hierarchical framework creation module is used to create a new hierarchical framework based on the vehicle business object and the general master data tag when the existing hierarchical framework does not exist.

[0211] Optionally, following the building blocks, the following may also be included:

[0212] The push module is used to push data from the sub-knowledge base that matches the user's tag to the user.

[0213] In summary, this application provides a knowledge base generation method that allows setting corresponding tags for various knowledge in a data pool. For developers, for a target vehicle business object, target knowledge tags can be selected according to requirements. Then, based on the target vehicle business object and the existence of corresponding business master data in the database, reusable general master data tags can be determined based on these target knowledge tags. Next, based on the vehicle business object and the general master data tags, a reusable existing hierarchical framework can be found. Under this existing hierarchical framework, a new target hierarchical framework corresponding to the target vehicle business object is constructed. A sub-knowledge base can then be built and published based on this target hierarchical framework, allowing other personnel to perform related operations based on this sub-knowledge base. Thus, the tag system enables the reuse of existing knowledge and hierarchical frameworks, reuse of at least some existing business data, and supports the selection of tags for sub-knowledge base construction according to user needs, reducing development costs.

[0214] This invention also provides a readable storage medium, which, when the instructions in the readable storage medium are executed by the processor of the vehicle controller, enables the vehicle controller to execute the above-described vehicle power supply method.

[0215] This invention also provides a vehicle including the aforementioned vehicle controller.

[0216] Reference Figure 5 This application provides an electronic device 501, including a memory 502, a processor 503, and a computer program stored in the memory 502 and executable on the processor 503. The processor 503 executes the computer program to implement the steps of the method described in any of the above-mentioned embodiments.

[0217] This application provides a computer-readable storage medium, characterized in that: a program is stored on the computer-readable storage medium, and when a processor executes the program, it implements the steps of the method described in any of the above claims, and has the beneficial effects of the method described in any of the above claims.

[0218] The computer-readable storage medium provided in this application embodiment implements the steps of the method described in any of the above claims when the processor executes the program. In this way, multiple sub-knowledge bases for different vehicle R&D businesses can be systematically generated, thereby enabling unified management of data from various vehicle R&D businesses and reducing the cost of data management and application.

[0219] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

[0220] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing device embodiments, and will not be repeated here.

[0221] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

[0222] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for generating a knowledge base, characterized in that, include: Retrieve information about the business shelf to be created; The business shelf information to be created includes the target vehicle business object and at least one target knowledge tag; If the database contains business master data corresponding to the target vehicle business object, obtain the parameter value corresponding to the target business object, and determine the general master data tag in the target knowledge tag by matching the target knowledge tag with the existing general knowledge tag in the database, and obtain the proprietary business object. Based on the vehicle business object and the general master data tag, search for the corresponding existing hierarchical framework in the database; If the existing hierarchical framework exists, obtain the existing hierarchical framework and add the proprietary business object to the existing hierarchical framework; The nodes in the existing hierarchical framework after the addition are associated with the corresponding parameter values ​​to obtain the target hierarchical framework; Based on the target hierarchical framework, a sub-knowledge base corresponding to the business shelf information is generated.

2. The method according to claim 1, characterized in that, Associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​after the addition includes: Based on the general master data tags, determine the corresponding first target data model. Based on the first target data model, the first knowledge topic corresponding to the first target data model is invoked; Using the first knowledge topic, obtain the parameter values ​​corresponding to the general master data tags from the data pool; Associate the parameter value with the general master data label in the hierarchical framework.

3. The method according to claim 1, characterized in that, Associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​after the addition includes: Receive parameter values ​​input for the proprietary service object and associate the parameter values ​​with the proprietary service object.

4. The method according to claim 1, characterized in that, After searching the database for the corresponding existing hierarchical framework based on the vehicle business object and the general master data tag, the method further includes: If the at least one target knowledge tag includes a proprietary tag other than the general master data tag, the proprietary tag shall be added to the existing hierarchical framework. The step of associating the nodes in the existing hierarchical framework with their corresponding parameter values ​​to obtain the target hierarchical framework includes: Based on the proprietary tags, determine the corresponding second target data model; Based on the second target data model, the second knowledge topic corresponding to the second target data model is invoked; The parameter values ​​corresponding to the proprietary tags are obtained from the data pool using the second knowledge topic. Associate the parameter value with the proprietary tag in the hierarchical framework.

5. The method according to claim 1, characterized in that, After obtaining the information of the business shelf to be created, the process also includes: If the database does not contain business master data corresponding to the shelf name, create the business master data corresponding to the shelf information to be created.

6. The method according to claim 1, characterized in that, After searching the database for the corresponding existing hierarchical framework based on the vehicle business object and the general master data tag, the process further includes: In the absence of the existing hierarchical framework, a new hierarchical framework is created based on the vehicle business object and the general master data tag.

7. The method according to claim 1, characterized in that, After generating a sub-knowledge base corresponding to the business shelf information based on the target hierarchical framework, the method further includes: Based on the user's corresponding user tag, push data from the sub-knowledge base that matches the user tag to the user.

8. A knowledge base generation device, characterized in that, include: The business shelf acquisition module is used to acquire information about the business shelves to be created. The business shelf information to be created includes the target vehicle business object and at least one target knowledge tag; The first data acquisition module is used to acquire the parameter value corresponding to the target business object when the database contains the business master data corresponding to the target vehicle business object, and to determine the general master data tag in the target knowledge tag by matching the target knowledge tag with the existing general knowledge tag in the database, and to acquire the proprietary business object. The hierarchical framework lookup module is used to search for the corresponding existing hierarchical framework in the database based on the vehicle business object and the general master data tag. The hierarchical framework operation module is used to obtain the existing hierarchical framework when it exists, and to add the proprietary business object to the existing hierarchical framework. The association module is used to associate the nodes in the existing hierarchical framework after they have been added with the corresponding parameter values ​​to obtain the target hierarchical framework. The module is used to generate a sub-knowledge base corresponding to the business shelf information based on the target hierarchical framework.

9. An electronic device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, A program is stored on the computer-readable storage medium, which, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 7.

Images