Method for quickly changing business model definition into agent DB Description knowledge base

Abstract

The invention relates to the technical field of information technology, in particular to a method for quickly converting a business model definition into an intelligent agent DB Description knowledge base. Business data of a plurality of target businesses are collected, a business model is created for each target business based on the business data, then a plurality of model features of each business model are extracted, standardization processing is carried out on the model features, and knowledge base structure standards of a knowledge base are defined based on the model features. According to the method and the device, the intelligent agent DB Description knowledge base is created on the basis of the knowledge base structure standard, finally the triggering condition of the intelligent agent DB Description knowledge base is set, and the intelligent agent DB Description knowledge base is maintained on the basis of the triggering condition, the corresponding knowledge base carriers are set on the basis of different user levels, so that the creation efficiency of the knowledge base is improved, and the user experience is improved. And the appropriate target model is selected for the to-be-updated business model, so that the updating efficiency of the knowledge base is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of information technology, in particular to a method for quickly converting a business model definition into an agent DB Description knowledge base. BACKGROUND

[0002] DB Description (Database Description) is a systematic description document or metadata set of information about the structure, logical design, physical implementation and usage rules of a database. Its core goal is to clearly define the "blueprint" of the database, ensuring that developers, administrators, users and other roles have consistent understanding of the database, supporting the design, development, maintenance and expansion of the database. Converting models (such as conceptual models, logical models, physical models) into DB Description knowledge bases essentially structures and standardizes abstract model information and integrates it into a searchable and maintainable knowledge system.

[0003] Chinese patent CN117972046A discloses a private knowledge base integration method based on a large model, including the following steps: S1, determining the main purpose and use scenario of the private knowledge base, and establishing a private knowledge base system; S2, collecting data and storing it in a private database, and preprocessing the collected data to obtain text data, and classifying the collected text data; S3, the private database uses vector database technology to vectorize the text data in the private knowledge base, and stores the vectorized data in the vector database; S4, the private knowledge base system integrates a Transformer model, and trains the Transformer model with the collected text data, and separately trains the text data in the private knowledge base. However, in the prior art, it is difficult to determine the appropriate database carrier for different types of target data in a timely manner, resulting in low efficiency of updating and maintaining the database. SUMMARY

[0004] The present application aims to provide a method for quickly converting a business model definition into an agent DB Description knowledge base to solve the problems raised in the background art.

[0005] To solve the above technical problems, one of the purposes of the present application is to provide a method for quickly converting a business model definition into an agent DB Description knowledge base, comprising: Collecting business data of a plurality of target businesses, and creating a business model for each target business based on the business data; Extracting a plurality of model features of each business model, and performing standardization processing on the model features; A knowledge base structure standard of the knowledge base is defined based on the model features, and an agent DB Description knowledge base is created based on the knowledge base structure standard. A trigger condition of the agent DB Description knowledge base is set, and the agent DB Description knowledge base is maintained based on the trigger condition.

[0006] Preferably, the business data includes user information of the target business and business information of the target business.

[0007] Preferably, the model features include table names and annotations, field names and data types, primary and foreign key relationships, and index strategies of the business model.

[0008] Preferably, the plurality of model features of each business model are extracted, and the model features are standardized, including the following steps: selecting and connecting a business model; opening a model file of the business model and exporting a table structure of the business model; extracting a plurality of model features of the business model based on the table structure; respectively standardizing each model feature to unify the data types.

[0009] Preferably, the knowledge base structure standard of the knowledge base is defined based on the model features, and the agent DB Description knowledge base is created based on the knowledge base structure standard, including the following steps: obtaining user information corresponding to the business model; calculating a user level corresponding to the business model based on the user information; setting a knowledge base carrier of the business model based on the user level.

[0010] Preferably, the knowledge base carrier includes a document type knowledge base, a structured database, an automated document library, and a low-code platform.

[0011] Preferably, the trigger condition of the agent DB Description knowledge base is set, and the agent DB Description knowledge base is maintained based on the trigger condition, including the following steps: obtaining a user level of the business model; setting a corresponding trigger condition based on the knowledge base carrier corresponding to the user level to update the trigger condition; determining whether the target business model meets the update trigger condition; if the target business model meets the update trigger condition, updating the knowledge base.

[0012] Preferably, the determination of whether the target business model meets the update trigger condition includes the following steps: Get the business model to be updated; Based on user information, cluster analysis is performed between the business model to be updated and the business models in the knowledge base to obtain the business model corresponding to the business model to be updated; the business model corresponding to the business model to be updated is denoted as the target model. Update the business model to be updated to the agent DB Description knowledge base where the target model is located.

[0013] On the other hand, this application also provides a system for quickly converting business model definitions into intelligent agent DB Description knowledge bases, and a method for quickly converting business model definitions into intelligent agent DB Description knowledge bases as described in any of the foregoing statements. The system includes a data acquisition component and a knowledge base component. The data acquisition component acquires business data of the target business. The knowledge base component is communicatively connected to the data acquisition component. All data information acquired by the data acquisition component is input into the knowledge base component. The knowledge base component converts the business model into an intelligent agent DB Description knowledge base and continuously updates the intelligent agent DB Description knowledge base based on triggering conditions, thereby realizing the creation and maintenance of the intelligent agent DB Description knowledge base.

[0014] Preferably, the acquisition component includes a user data acquisition module and a business data acquisition module. The user data acquisition module acquires user information of the target business, and the business data acquisition module acquires business information of the target business.

[0015] Compared with the prior art, the beneficial effects of the present invention are as follows: By collecting business data from multiple target businesses, creating a business model for each target business based on the business data, extracting multiple model features from each business model, standardizing the model features, defining the knowledge base structure standard based on the model features, creating an agent DB Description knowledge base based on the knowledge base structure standard, setting the trigger conditions for the agent DB Description knowledge base, and maintaining the agent DB Description knowledge base based on the trigger conditions, this application improves the efficiency of knowledge base creation by setting corresponding knowledge base carriers based on different user levels, and selects appropriate target models for the business models to be updated, thereby improving the efficiency of knowledge base updates. Attached Figure Description

[0016] Figure 1 A flowchart illustrating the method for quickly converting business model definitions into an agent DB Description knowledge base; Figure 2A connection diagram of a system for quickly converting business model definitions into an agent DB Description knowledge base; The reference numerals are as follows: 100, Data Acquisition Component; 101, User Data Acquisition Module; 102, Business Data Acquisition Module; 200. Knowledge Base Components. Detailed Implementation

[0017] 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.

[0018] Example 1 like Figure 1 As shown, one of the objectives of this invention is to provide a method for quickly converting business model definitions into an agent DB Description knowledge base, including: S100 collects business data from multiple target businesses and creates a business model for each target business based on the business data. S200 extracts multiple model features from each business model and standardizes the model features. Specifically, extracting table structure and constraints is a key step in building a DB Description knowledge base. Information needs to be obtained from model files, database instances, or design documents and organized in a standardized format. Before extracting model features, the specific dimensions of table structure and constraints need to be clarified. When extracting model features, the business model can be started through software such as PowerDesigner, and the table structure can be exported. Then, the model features can be extracted. S300 is a knowledge base structure standard based on model feature definition, and an agent DB Description knowledge base is created based on the knowledge base structure standard. S400: Set the triggering conditions for the agent DB Description knowledge base, and maintain the agent DB Description knowledge base based on the triggering conditions; Specifically, the DB Description knowledge base includes basic database information (such as name and purpose), table structure definitions (table name, primary key, foreign key and index), relational model, physical storage information and business rules and constraints. It is the "instruction manual" of the database, which runs through the entire life cycle of the database (design → development → operation and maintenance → iteration). A complete DB Description can significantly improve team collaboration efficiency and system maintainability, and is an indispensable part of database engineering.

[0019] It should be noted that by collecting business data from multiple target businesses, a business model is created for each target business based on the business data. Then, multiple model features of each business model are extracted and standardized. Based on the model features, a knowledge base structure standard is defined for the knowledge base. Based on the knowledge base structure standard, an agent DB Description knowledge base is created. Finally, the triggering conditions for the agent DB Description knowledge base are set, and the agent DB Description knowledge base is maintained based on the triggering conditions. This application improves the efficiency of knowledge base creation by setting corresponding knowledge base carriers based on different user levels, and selects appropriate target models for the business models to be updated, thereby improving the efficiency of knowledge base updates.

[0020] In one embodiment of this application, the business data includes user information of the target business and business information of the target business.

[0021] It should be noted that user information can be used to identify the target of the business operation. The target includes the specific executor and the executing company. Therefore, when the target is the executor, the user information includes data such as gender and address. When the target is the executing company, it can also include the company's operating data and financial data.

[0022] The target information in this application is mainly to extract business entities and business relationships. Therefore, it is necessary to extract business lists (such as business products and business orders), business attributes, and business relationships (including related fields).

[0023] In one embodiment of this application, the model features include the table name and comments, field names and data types, primary and foreign key relationships, and indexing strategies of the business model.

[0024] It should be noted that the table names include user information table (user_info), order details table (order_detail), etc., and the data types include (INT and VARCHAR (255)). The primary and foreign key relationships include primary key fields, foreign key association tables and fields. The indexing strategies include creating a unique index with username and creating a regular index for order.create_tune, etc.

[0025] Different databases may have different data types, so a unified standard is needed after extraction. This application uses methods such as target model export and database SQL query to extract structural information from the business model, laying the foundation for the subsequent creation of a knowledge base.

[0026] In one embodiment of this application, S200 includes: S210, Select and connect a business model; S220, Open the model file of this business model and export the table structure of this business model; S230, Extract multiple model features of the business model based on the table structure; S240 standardizes each model feature to unify the data type.

[0027] It should be noted that...

[0028] In one embodiment of this application, S300 includes: S310, obtain user information corresponding to the business model; S320, calculate the user level corresponding to the business model based on the user information; S330 is the knowledge base carrier for setting up this business model based on user level.

[0029] It should be noted that the user level corresponding to the business model is calculated using Formula 1; Formula 1; in, It refers to the user level corresponding to the business model. It is the i-th user information in the business model. is the weight corresponding to the i-th user information, and N is the total number of user information items included in the business model.

[0030] User level is a numerical value used to reflect the complexity of the target business. Generally speaking, the higher the user level, the higher the complexity. Therefore, for target businesses with different user levels, it is necessary to select the appropriate knowledge base carrier to improve the efficiency of creating or updating the knowledge base. For example, for a target business like a design manual, the main goal is for non-technical personnel to read, so creating a knowledge base for it only requires selecting a document-type knowledge base.

[0031] In one embodiment of this application, the knowledge base carrier includes a document-based knowledge base, a structured database, an automated document library, and a low-code platform.

[0032] It should be noted that document-based knowledge bases are suitable for human reading, including documents from Confluence, Notion, etc., and are easy to edit. Structured databases are suitable for program calls, including MySQL, which support API queries and can be integrated with other systems. Automated document libraries are suitable for efficient maintenance, including Screw, which can directly generate documents from the database. Low-code platforms are suitable for rapid deployment, requiring no development and allowing interactive knowledge bases to be quickly built using forms and dashboards.

[0033] In one embodiment of this application, S400 includes: S410, obtain the user level of the business model; S420, set the corresponding trigger conditions and update trigger conditions based on the knowledge base carrier corresponding to the user level; S430, determine whether the target business model meets the update trigger conditions; S440, If the target business model meets the update trigger conditions, then update the knowledge base; Optionally, in addition to setting trigger conditions, it is also possible to set audit conditions for the knowledge base, thereby periodically deleting outdated information in the knowledge base.

[0034] It should be noted that the trigger condition is to update the knowledge base synchronously when the database structure changes. Therefore, setting different trigger conditions for different types of target business can effectively reduce the maintenance cost of the knowledge base and improve the update efficiency of the knowledge base. Since the core steps of converting the business model into a knowledge base are "feature extraction - carrierization - maintenance", setting trigger conditions can reduce repetitive work in the maintenance process and ultimately form a shareable and traceable database system to improve system maintainability.

[0035] In one embodiment of this application, S430 includes: S431, retrieve the business model to be updated; S432, Based on user information, perform cluster analysis on the business model to be updated and the business models in the knowledge base to obtain the business model corresponding to the business model to be updated; denote the business model corresponding to the business model to be updated as the target model; S433, update the business model to be updated to the agent DB Description knowledge base where the target model is located.

[0036] It should be noted that the triggering condition set in this application is to update the business model to be updated to the knowledge base of the target model that is similar to it in terms of user information. Therefore, this application can use the K-means clustering method to cluster the business model to be updated. The K-means clustering method is an iterative clustering analysis algorithm. Its steps are: first, divide the data into K groups, then randomly select K objects as initial cluster centers, then calculate the distance between each object and each seed cluster center, and assign each object to the cluster center closest to it. The cluster center and the objects assigned to them represent a cluster. Therefore, the target model obtained by clustering is the business model that is closest to the target model to be updated. Since this application selects the appropriate knowledge base carrier based on the user level corresponding to the business model, setting the clustering method as the triggering condition can effectively reduce the re-judgment process of the business model to be updated, thereby reducing the update steps and improving the update efficiency.

[0037] like Figure 2 As shown, in one embodiment of this application, a system for quickly converting a business model definition into an agent DB Description knowledge base is also provided. This system, applied to the method described above for quickly converting a business model definition into an agent DB Description knowledge base, includes a data acquisition component 100 and a knowledge base component 200. The data acquisition component 100 acquires business data of the target business. The knowledge base component 200 is communicatively connected to the data acquisition component 100. All data information acquired by the data acquisition component 100 is input into the knowledge base component 200. The knowledge base component 200 converts the business model into an agent DB Description knowledge base and continuously updates the agent DB Description knowledge base based on trigger conditions, thereby realizing the creation and maintenance of the agent DB Description knowledge base.

[0038] It should be noted that the business data of the target business is collected by the acquisition component 100, and the model features of the business model are extracted by the knowledge base component 200. Based on the model features, the knowledge base structure standard of the knowledge base is defined, and the intelligent agent DB Description knowledge base is created. Then, the trigger conditions for creating the intelligent agent DB Description knowledge base are set, thereby improving the update efficiency of the knowledge base.

[0039] In one embodiment of this application, the acquisition component 100 includes a user data acquisition module 101 and a business data acquisition module 102. The user data acquisition module 101 acquires user information of the target business, and the business data acquisition module 102 acquires business information of the target business.

[0040] It should be noted that different types of data information from the target business are collected through different acquisition modules to avoid cross-leakage of different types of data information and improve data security.

[0041] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely preferred examples and are not intended to limit the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for quickly converting business model definitions into an agent database description knowledge base, characterized in that, include: Collect business data from multiple target businesses, and create a business model for each target business based on the business data. Extract multiple model features from each business model and standardize the model features; The knowledge base structure standard is defined based on model features, and the intelligent agent DBDescription knowledge base is created based on the knowledge base structure standard. Set the trigger conditions for the agent's DB Description knowledge base, and maintain the agent's DBDescription knowledge base based on the trigger conditions.

2. The method for quickly converting business model definitions into an agent DB Description knowledge base according to claim 1, characterized in that, The business data includes user information and business information of the target business.

3. The method for quickly converting a business model definition into an agent DB Description knowledge base according to claim 2, characterized in that, The model features include table names and comments, field names and data types, primary and foreign key relationships, and indexing strategies.

4. The method for quickly converting a business model definition into an agent DB Description knowledge base according to claim 3, characterized in that: The process of extracting multiple model features for each business model and standardizing these features includes the following steps: Select and connect a business model; Open the model file for this business model and export its table structure; Extract multiple model features of this business model based on the table structure; Each model feature is standardized to unify the data type.

5. The method for quickly converting a business model definition into an agent DB Description knowledge base according to claim 4, characterized in that: The knowledge base structure standard based on model feature definition, and the creation of an agent DB Description knowledge base based on the knowledge base structure standard, include the following steps: Obtain user information corresponding to the business model; The user level corresponding to the business model is calculated based on this user information; The knowledge base carrier of this business model is set based on user level.

6. The method for quickly converting a business model definition into an agent DB Description knowledge base according to claim 5, characterized in that, The knowledge base carriers include document-based knowledge bases, structured databases, automated document libraries, and low-code platforms.

7. The method for quickly converting a business model definition into an agent DB Description knowledge base according to claim 6, characterized in that: Setting the trigger conditions for the agent DB Description knowledge base and maintaining the agent DB Description knowledge base based on the trigger conditions includes the following steps: Obtain the user level of the business model; Set corresponding trigger conditions and update trigger conditions based on the knowledge base carrier corresponding to the user level; Determine whether the target business model meets the update trigger conditions; If the target business model meets the update trigger conditions, then update the knowledge base.

8. The method for quickly converting a business model definition into an agent DB Description knowledge base according to claim 7, characterized in that: The process of determining whether the target business model meets the update trigger conditions includes the following steps: Get the business model to be updated; Based on user information, cluster analysis is performed between the business model to be updated and the business models in the knowledge base to obtain the business model corresponding to the business model to be updated; the business model corresponding to the business model to be updated is denoted as the target model. Update the business model to be updated to the agent DB Description knowledge base where the target model is located.

9. A system for rapidly converting business model definitions into an agent DB Description knowledge base, applied to the method for rapidly converting business model definitions into an agent DB Description knowledge base as described in any one of claims 1 to 8, characterized in that, include: Data acquisition components; The acquisition component collects business data for the target service. Knowledge base component; The knowledge base component is communicatively connected to the acquisition component. All data information acquired by the acquisition component is input into the knowledge base component. The knowledge base component converts the business model into an agent DBDescription knowledge base and continuously updates the agent DBDescription knowledge base based on trigger conditions, thereby realizing the creation and maintenance of the agent DBDescription knowledge base.

10. The system for quickly converting business model definitions into an agent DB Description knowledge base according to claim 9, characterized in that, The data acquisition component includes a user data acquisition module and a business data acquisition module. The user data acquisition module acquires user information of the target business, and the business data acquisition module acquires business information of the target business.

Images