Information registration method, device, equipment, medium and product

Abstract

The invention provides an information registration method and device, equipment, a medium and a product, and relates to the field of financial science and technology or other related fields. The method comprises the following steps: receiving a log message sent by an application system managed by a data asset system; determining a function module in the application system for triggering the target database from the log message, and determining function information for describing functions of the target database according to related information of the function module; determining first registration information of the target database from a data source system which registers basic information of each database in the application system based on attribute information of the target database in the log message; and performing supplementary registration processing on the first registration information by using the function information to obtain second registration information of the target database. According to the product, the difficulty of determining the source data required by the business personnel by the data analysis personnel can be reduced.

Description

Technical Field

[0001] This application relates to the field of financial technology or other related fields, and in particular to an information registration method, apparatus, equipment, medium and product. Background Technology

[0002] Bank data assets refer to various types of data accumulated by banks during their operations. These assets can include customer information, transaction information, risk information, and more. Against the backdrop of the rapid development of the digital economy, data assets are playing an increasingly important role in the digital transformation of banks. Major banks are placing greater emphasis on the use and management of data assets, and the demand for data analysis and mining is gradually increasing.

[0003] When business personnel involved in data analysis and mining submit their requests, they often do so from the user's perspective, conveying their needs to data analysts. For the same business data (such as operational status data for a specific bank branch), evaluation can be conducted using different methods, each requiring different data. To ensure the accuracy of the acquired data, data analysts need to identify data sources that align with the business personnel's requirements.

[0004] However, in building a bank's data asset system, it's often simply a matter of identifying the application system to which each database belongs, without functionally labeling each database. This makes it difficult for data analysts to determine the source data needed by business personnel. Summary of the Invention

[0005] This application provides an information registration method, apparatus, equipment, medium, and product to reduce the difficulty for data analysts in determining the source data required by business personnel.

[0006] In a first aspect, this application provides an information registration method for a data asset system, the method comprising:

[0007] The system receives log messages sent by the application systems managed by the data asset system. These log messages are generated by the application systems during the process of accessing the target database by recording access events.

[0008] From the log messages, determine the functional modules in the application system that trigger the target database, and based on the relevant information of the functional modules, determine the functional information describing the function of the target database;

[0009] Based on the attribute information of the target database in the log message, the first registration information of the target database is determined from the data source system that registers the basic information of each database in the application system;

[0010] The first registration information is supplemented using the functional information to obtain the second registration information of the target database, so as to realize the search of the target database through the functional information in the second registration information.

[0011] Secondly, this application provides an information registration method for use in an application system, the method comprising:

[0012] During the process of the application system accessing the target database, access events are recorded and log messages corresponding to the access events are generated;

[0013] The log message is sent to the data asset system that manages the application system, so that the data asset system accepts the log message; from the log message, the functional module that triggers the target database is identified, and based on the relevant information of the functional module, the functional information of the target database is determined, wherein the functional module is a module in the application system; based on the attribute information of the target database in the log message, the first registration information of the target database is determined from the data source system that registers the basic information of each database in the application system; the first registration information is supplemented with the functional information to obtain the second registration information of the target database.

[0014] Thirdly, this application provides an information registration device for a data asset system, the device comprising:

[0015] The message receiving module is used to receive log messages sent by the application system managed by the data asset system. The log messages are generated by the application system recording access events during the process of accessing the target database.

[0016] The functional information module is used to determine, from the log message, the functional module in the application system that triggers the target database, and to determine, based on the relevant information of the functional module, functional information describing the function of the target database.

[0017] The first information module is used to determine the first registration information of the target database from the data source system that registers the basic information of each database in the application system, based on the attribute information of the target database in the log message;

[0018] The second information module is used to supplement the first registration information with the functional information to obtain the second registration information of the target database, so as to realize the search of the target database through the functional information in the second registration information.

[0019] Fourthly, this application provides an information registration device for use in an application system, the device comprising:

[0020] The message generation module is used to record access events and generate log messages corresponding to the access events during the process of the application system accessing the target database.

[0021] A message sending module is used to send the log message to the data asset system that manages the application system, so that the data asset system can accept the log message; determine the functional module that triggers the target database from the log message, and determine the functional information of the target database based on the relevant information of the functional module, wherein the functional module is a module in the application system; determine the first registration information of the target database from the data source system that registers the basic information of each database in the application system based on the attribute information of the target database in the log message; and use the functional information to supplement the first registration information to obtain the second registration information of the target database.

[0022] Fifthly, this application provides an electronic device, including: a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method described above.

[0023] Sixthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the above-described method.

[0024] In a seventh aspect, this application provides a computer program product, including a computer program that, when executed by a processor, is used to implement the method described above.

[0025] The information registration method, apparatus, equipment, medium, and product provided in this application generate log messages during the process of an application system accessing a target database. Functional modules are identified from these log messages, and then the functional information of the target database is determined based on the relevant information of the functional modules. This functional information is then used to supplement the first registration information of the target database, resulting in second registration information. This process enables real-time supplementary registration of the first registration information during the use of the application system. After obtaining the second registration information of the target database, data analysts can directly determine the required database based on the second registration information containing functional information. This reduces the difficulty for data analysts in determining the source data needed by business personnel, reduces the dependence of bank data analysis work on the work experience of data analysts, and facilitates the rapid development of the bank's data analysis team. Attached Figure Description

[0026] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0027] Figure 1 A flowchart illustrating an information registration method provided in an embodiment of this application;

[0028] Figure 2 This application provides a schematic diagram of the architecture of a data source system.

[0029] Figure 3 A flowchart illustrating another information registration method provided in this application embodiment;

[0030] Figure 4 This is a schematic diagram of the structure of an information registration device provided in an embodiment of this application;

[0031] Figure 5 This is a schematic diagram of another information registration device provided in an embodiment of this application;

[0032] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0033] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0034] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0035] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant countries and regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation portals for users to choose to authorize or refuse.

[0036] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning. The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise indicated. It should be understood that such terms can be used interchangeably where appropriate, for example, to be implemented in an order other than those given in the illustrations or descriptions of the embodiments of this application. The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application, are intended to be omnipresent but not exclusive. For example, a product or device that comprises a series of components is not necessarily limited to those components that are explicitly listed, but may include other components that are not explicitly listed or are inherent to such products or devices. The term "module" as used in this application refers to any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code capable of performing the functions associated with that element.

[0037] It should be noted that the information registration methods, devices, equipment, media and products provided in this application can be used in the field of fintech, or in any field other than fintech. The application fields of the information registration methods, devices, equipment, media and products in this application are not limited.

[0038] The banking industry is increasingly emphasizing the use and management of data assets, and the demand for data analysis and mining is gradually increasing. During the development of various application systems within a bank, data and functions are relatively independent; that is, the databases used by each application system are not individually labeled with their functions. This makes it difficult for data analysts to find source data that meets the needs of business personnel from the data involved in the business systems after the application systems are developed.

[0039] The technical content provided in this application aims to solve the aforementioned technical problems of the prior art. In the information registration method, apparatus, equipment, medium, and product of this application, during the process of an application system accessing a target database, log messages are generated. Functional modules are determined from the log messages, and then the functional information of the target database is determined based on the relevant information of the functional modules. This functional information is then used to supplement the first registration information of the target database, resulting in second registration information. In the above process, real-time supplementary registration processing of the first registration information is achieved during the use of the application system. This allows data analysts to directly determine the required database based on the second registration information containing functional information after obtaining the second registration information of the target database. This reduces the difficulty for data analysts in determining the source data required by business personnel, reduces the dependence of bank data analysis work on the work experience of data analysts, and facilitates the rapid development of the bank's data analysis team.

[0040] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0041] Example 1

[0042] Figure 1 This is a flowchart illustrating an information registration method provided in an embodiment of this application; as shown below. Figure 1 As shown, this method is used in a data asset system and includes:

[0043] Step 101: Receive log messages sent by the application systems managed by the data asset system.

[0044] The log messages are generated by the application system during the process of accessing the target database, recording access events. The target database is at least one database accessed by the application system after receiving user operation instructions. This target database can be a database dedicated to a single application system or a database shared by multiple application systems. This specification does not specifically limit the relationship between the target database and the application system; it can be determined based on the actual situation.

[0045] This log message may include the Structured Query Language (SQL) query statement used by the application system to access the database (SQL statement for short), the database address (Internet Protocol, IP), the name of the application system, and the functional module in the application system that accesses the database. This log message can be recorded in JSON string format.

[0046] Step 102: From the log message, determine the functional module in the application system that triggers the target database, and based on the relevant information of the functional module, determine the functional information describing the function of the target database.

[0047] The functional modules are those included in the application system, and each module can trigger at least one target database. For example, if it is necessary to find the operating data of Bank A for each quarter, the quarterly operating data module can be used to trigger the database containing the operating data for each quarter. Since the log messages recording access events record the quarterly operating data module, information about the quarterly operating data module (such as name, address, etc.) can be extracted from the log messages.

[0048] The relevant information includes the name of the functional module, its upstream and downstream modules (i.e., modules containing the functional module, and modules contained in the functional module), and the users who use the functional module. This information contains data describing the function of the functional module (i.e., functional information). Therefore, the functional information of the target database can be extracted from this information.

[0049] Step 103: Based on the attribute information of the target database in the log message, determine the first registration information of the target database from the data source system that registers the basic information of each database in the application system.

[0050] Step 104: Use the functional information to supplement the first registration information to obtain the second registration information of the target database, so as to realize the search of the target database through the functional information in the second registration information.

[0051] The first registration information refers to the information of the target database registered during the application system construction process. The data source system is a system for aggregating, registering, and managing information from databases belonging to multiple application systems. Specifically, during the construction of the data source system, the first registration information of each database managed by the data source system can be recorded based on a pre-defined data table. Table 1 shows the table for registering the first registration information. As shown in Table 1, the first registration information may include basic information such as the database number of the target database.

[0052] Table 1 First Registration Information Form

[0053]

[0054] As mentioned earlier, in addition to functional modules, log messages can also record attribute information such as the address of the target database. Since this attribute information is recorded in the first registration information, the corresponding first registration information of the target database can be found in the data source system using this attribute information.

[0055] After finding the first registration information, the functional information in step S102 can be used to supplement the first registration information, and the processed information becomes the second registration information. Since the second registration information includes functional information, after obtaining the second registration information, the target database can be searched in multiple databases under the data asset system through the functional information it contains.

[0056] Specifically, during the use of the application system, second registration information for each database accessed during the process can be recorded based on a preset data table. Table 2 shows the table for registering the second registration information. As shown in Table 2, in addition to the first registration information, the second registration information may include information related to the access event, such as the application system name and function name. The function name is a name obtained by further refining the function information; if the function information is concise, it can be directly used as the function name. In addition, the second registration information may also include the time of supplementary registration (i.e., the last update time).

[0057] Table 2 Second Registration Information Form

[0058]

[0059] In this example, during the application system's access to the target database, log messages are generated. Functional modules are identified from these log messages, and then the functional information of the target database is determined based on the relevant information of these modules. This functional information is then used to supplement the first registration information of the target database, resulting in second registration information. This process enables real-time supplementation of the first registration information during application system usage. After obtaining the second registration information of the target database, data analysts can directly determine the required database based on this second registration information, which includes functional information. This reduces the difficulty for data analysts in identifying the source data needed by business personnel, decreases the reliance on data analysts' experience in bank data analysis work, and facilitates the rapid development of the bank's data analysis team.

[0060] Besides functional modules, the application system and other modules that indicate the path to the functional module also indicate functional information. For example, for the information modification submodule under the account information module in the loan system corresponding to Bank A, the functional information of the target database corresponding to this information modification submodule could be "modify the account information of loan applicants in Bank A". It can be seen that, in addition to the relevant information of the information modification submodule, the relevant information of the application system and the account information module will help in determining the functional information. In one implementation, determining the functional information describing the function of the target database based on the relevant information of the functional module includes:

[0061] From the multiple modules included in the application system, determine at least one target module used by the access event to invoke the functional module;

[0062] Based on the relevant information of the application system, the target module, and the functional module, the functional information of the target database is determined.

[0063] The target module is a module in the application system required when calling the functional module. The target module can be a parent module of the functional module.

[0064] After determining the functional modules, at least one target module corresponding to each functional module can be identified. Then, based on relevant information from the application system, the target module, and the functional module, the functional information can be determined. This specification does not specify the content of the relevant information from the application system and the target module; these can be determined based on the actual situation.

[0065] In one example, similar to the information related to functional modules, the information related to the application system can include the name of the application system, and the information related to the target module can also include the name of the target module. In this way, the process supplements the functional information containing the relevant information of the functional modules by using the relevant information from the application system and the target module, improving the accuracy of the functional information. This, in turn, improves the accuracy with which users can find the required database based on the second registration information containing the functional information.

[0066] Because large language models (LLMs) have advantages such as fast training speed, good interpretability, and strong generalization ability, they can be used to extract information from the aforementioned relevant information to obtain functional information. In one implementation, the relevant information includes names, and determining the functional information of the target database based on the application system, the relevant information of the target module, and the functional module includes:

[0067] Based on the application name of the application system, the module name of the functional module, and the module name of the target module, generate descriptive text describing the event that calls the functional module;

[0068] The descriptive text is input into a large language model to obtain the functional information.

[0069] The description text describes the path to the called functional module. Specifically, the description text is obtained by concatenating the application name of the application system, the module name of the target module, and the module name of the functional module in sequence.

[0070] Furthermore, the descriptive text can be input into a large language model, which can then extract information from the text to obtain functional information. In this way, extracting functional information from the descriptive text using a large language model leverages the powerful processing capabilities of the model to enhance the accuracy of the functional information.

[0071] The data asset system aggregates a large number of databases, and the required database can be identified using its address and name. In one implementation, the attribute information includes address data and name data. The determination of the first registration information of the target database based on the attribute information of the target database in the log message, from the data source system that registers the basic information of each database in the application system, includes:

[0072] The log message is parsed to obtain the address data and the SQL query statement corresponding to the access event;

[0073] The SQL query statement is parsed to obtain the name data;

[0074] From the data source system, determine the first registration information that matches the name data and the address data.

[0075] Specifically, the address data of the target database and the SQL query statement corresponding to the access event can be directly parsed from the log message. Since the SQL query statement contains the name data of the target database, the SQL query statement can be parsed to obtain the name data of the target database.

[0076] After obtaining the name and address data, the name and address data can be used to accurately locate the first registration information in the data source system, thereby improving the accuracy of the information registration process.

[0077] Figure 2 This is a schematic diagram of the architecture of a data source system provided in an embodiment of this application. Figure 2As shown, the data source system manages N application systems, each corresponding to at least one database. Databases directly corresponding to application systems may be associated with other databases, such as database 1 and database M2 being related. Typically, associated databases have related functions. For example, a database related to loan operations is unlikely to be associated with a database related to deposit operations. Therefore, the functional information of the target database can be calibrated using the functional information of associated databases to correct potential errors in determining the functional information.

[0078] In one implementation, the step of using the functional information to supplement the first registration information to obtain the second registration information in the target database includes:

[0079] Obtain the cluster address to which the address data belongs, and determine the reference function information of the database corresponding to the cluster address;

[0080] The reference functional information is used to calibrate the functional information to obtain calibrated functional information.

[0081] The first registration information is supplemented using the calibrated functional information to obtain the second registration information of the target database.

[0082] Specifically, the address data of the target database can be used to determine the address of the parent database (i.e., the cluster address). The functional information of the database corresponding to this cluster address serves as reference functional information. This reference functional information can then be used to calibrate the functional information, resulting in calibrated functional information. This calibration process can involve correcting errors in the functional information (such as errors in the target module to which a functional module belongs).

[0083] Furthermore, the calibrated functional information can be used to supplement the first registration information to obtain the second registration information. In this way, determining the second registration information using the calibrated functional information improves the accuracy of the second registration information, enabling accurate retrieval of the target database.

[0084] After obtaining the second registration information, the second registration information can be used to search for the required database. In one implementation, after supplementing the first registration information with the functional information to obtain the second registration information of the target database, the method includes:

[0085] Receive the target application name and target function name input by the user;

[0086] Find the functional information that matches the target functional name from the second registration information corresponding to the application system with the target application name;

[0087] The database to which the matched functional information belongs is used as the database searched by the user.

[0088] Here, "user" refers to the user of the data asset system, "target application name" is the name of the application system to which the database the user is searching belongs, and "target function name" is the name of the function that the database the user is searching has.

[0089] By using the target application name, the database under the application system to which the database the user is looking for belongs can be found from the data source system. Furthermore, by using the target function name, the database the user is looking for can be found from these databases.

[0090] Since the second registration information already contains functional information, the functional information can be determined by using the target application name and the target function name, which enables a quick search for the required database in the data source system.

[0091] Example 2

[0092] Figure 3 A flowchart illustrating another information registration method provided in this application embodiment; as shown Figure 3 As shown, this method is used in an application system and includes:

[0093] Step 301: During the process of the application system accessing the target database, the access event is recorded and a log message corresponding to the access event is generated.

[0094] Step 302: Send the log message to the data asset system that manages the application system, so that the data asset system accepts the log message; determine the functional module that triggers the target database from the log message, and determine the functional information of the target database based on the relevant information of the functional module, wherein the functional module is a module in the application system; determine the first registration information of the target database from the data source system that registers the basic information of each database in the application system based on the attribute information of the target database in the log message; use the functional information to supplement the first registration information to obtain the second registration information of the target database.

[0095] The log messages are generated by the application system during the process of accessing the target database, recording access events. The target database is at least one database accessed by the application system after receiving user operation instructions. This target database can be a database dedicated to a single application system or a database shared by multiple application systems. This specification does not specifically limit the relationship between the target database and the application system; it can be determined based on the actual situation.

[0096] This log message may include the Structured Query Language (SQL) query statement used by the application system to access the database (SQL statement for short), the database address (Internet Protocol, IP), the name of the application system, and the functional module in the application system that accesses the database. This log message can be recorded in JSON string format.

[0097] A functional module is a module included in an application system that can trigger at least one target database. For example, if it is necessary to find the operating data of Bank A for each quarter, the quarterly operating data module can be used to trigger the database containing the operating data for each quarter. Since the log messages recording access events record the quarterly operating data module, information about the quarterly operating data module (such as name, address, etc.) can be extracted from the log messages.

[0098] The relevant information includes the name of the functional module, its upstream and downstream modules (i.e., modules containing the functional module, and modules contained in the functional module), and the users who use the functional module. This information contains data describing the function of the functional module (i.e., functional information). Therefore, the functional information of the target database can be extracted from this information.

[0099] The first registration information refers to the information of the target database registered during the application system construction process. The data source system is a system for summarizing, registering, and managing information from databases belonging to multiple application systems. Specifically, during the construction of the data source system, the first registration information of each database managed by the data source system can be recorded based on a pre-defined data table. Table 1 shows the table for registering the first registration information. As shown in Table 1, the first registration information may include basic information such as the database number of the target database.

[0100] As mentioned earlier, in addition to functional modules, log messages can also record attribute information such as the address of the target database. Since this attribute information is recorded in the first registration information, the corresponding first registration information of the target database can be found in the data source system using this attribute information.

[0101] After finding the first registration information, the functional information in step S102 can be used to supplement the first registration information, and the processed information becomes the second registration information. Since the second registration information includes functional information, after obtaining the second registration information, the target database can be searched in multiple databases under the data asset system through the functional information it contains.

[0102] Specifically, during the use of the application system, second registration information for each database accessed during the process can be recorded based on a preset data table. Table 2 shows the table for registering second registration information. As shown in Table 2, in addition to the first registration information, the second registration information may include information related to the access event, such as the application system name and function name. The function name is a name obtained by further refining the function information; if the function information is concise, it can be directly used as the function name. Furthermore, the second registration information may also include the time of supplementary registration.

[0103] In this example, during the application system's access to the target database, log messages are generated. Functional modules are identified from these log messages, and then the functional information of the target database is determined based on the relevant information of these modules. This functional information is then used to supplement the first registration information of the target database, resulting in second registration information. This process enables real-time supplementation of the first registration information during application system usage. After obtaining the second registration information of the target database, data analysts can directly determine the required database based on this second registration information, which includes functional information. This reduces the difficulty for data analysts in identifying the source data needed by business personnel, decreases the reliance on data analysts' experience in bank data analysis work, and facilitates the rapid development of the bank's data analysis team.

[0104] In one implementation, sending the log message to the data asset system that manages the application system includes:

[0105] The log message is sent to the data asset system via the QUIC protocol.

[0106] The Quick User Datagram Protocol Internet Connection (QUIC) is a secure and reliable transport protocol based on UDP (User Datagram Protocol). Compared to TCP (Transmission Control Protocol), QUIC integrates Transport Layer Security (TLS) for encrypted data transmission. Furthermore, QUIC supports multi-stream concurrency, resulting in faster transmission speeds, and requires only a single handshake to establish a connection, leading to low latency.

[0107] In one example, the QUIC protocol can be used to send log messages from the application system to the data asset system as a stream, thereby improving both the speed and security of log message transmission.

[0108] Example 3

[0109] Figure 4 This application provides a schematic diagram of the structure of an information registration device for use in a data asset system; as shown below. Figure 4 As shown, the device includes:

[0110] The message receiving module 41 is used to receive log messages sent by the application system managed by the data asset system. The log messages are generated by the application system recording access events during the process of accessing the target database.

[0111] The functional information module 42 is used to determine, from the log message, the functional module in the application system that triggers the target database, and to determine, based on the relevant information of the functional module, functional information describing the function of the target database.

[0112] The first information module 43 is used to determine the first registration information of the target database from the data source system that registers the basic information of each database in the application system, based on the attribute information of the target database in the log message;

[0113] The second information module 44 is used to supplement the first registration information with the functional information to obtain the second registration information of the target database, so as to realize the search of the target database through the functional information in the second registration information.

[0114] The log messages are generated by the application system during the process of accessing the target database, recording access events. The target database is at least one database accessed by the application system after receiving user operation instructions. This target database can be a database dedicated to a single application system or a database shared by multiple application systems. This specification does not specifically limit the relationship between the target database and the application system; it can be determined based on the actual situation.

[0115] This log message may include the Structured Query Language (SQL) query statement used by the application system to access the database (SQL statement for short), the database address (Internet Protocol, IP), the name of the application system, and the functional module in the application system that accesses the database. This log message can be recorded in JSON string format.

[0116] A functional module is a module included in an application system that can trigger at least one target database. For example, if it is necessary to find the operating data of Bank A for each quarter, the quarterly operating data module can be used to trigger the database containing the operating data for each quarter. Since the log messages recording access events record the quarterly operating data module, information about the quarterly operating data module (such as name, address, etc.) can be extracted from the log messages.

[0117] The relevant information includes the name of the functional module, its upstream and downstream modules (i.e., modules containing the functional module, and modules contained in the functional module), and the users who use the functional module. This information contains data describing the function of the functional module (i.e., functional information). Therefore, the functional information of the target database can be extracted from this information.

[0118] The first registration information refers to the information of the target database registered during the application system construction process. The data source system is a system for summarizing, registering, and managing information from databases belonging to multiple application systems. Specifically, during the construction of the data source system, the first registration information of each database managed by the data source system can be recorded based on a pre-defined data table. Table 1 shows the table for registering the first registration information. As shown in Table 1, the first registration information may include basic information such as the database number of the target database.

[0119] As mentioned earlier, in addition to functional modules, log messages can also record attribute information such as the address of the target database. Since this attribute information is recorded in the first registration information, the corresponding first registration information of the target database can be found in the data source system using this attribute information.

[0120] After finding the first registration information, the functional information in step S102 can be used to supplement the first registration information, and the processed information becomes the second registration information. Since the second registration information includes functional information, after obtaining the second registration information, the target database can be searched in multiple databases under the data asset system through the functional information it contains.

[0121] Specifically, during the use of the application system, second registration information for each database accessed during the process can be recorded based on a preset data table. Table 2 shows the table for registering second registration information. As shown in Table 2, in addition to the first registration information, the second registration information may include information related to the access event, such as the application system name and function name. The function name is a name obtained by further refining the function information; if the function information is concise, it can be directly used as the function name. Furthermore, the second registration information may also include the time of supplementary registration.

[0122] In this example, during the application system's access to the target database, log messages are generated. Functional modules are identified from these log messages, and then the functional information of the target database is determined based on the relevant information of these modules. This functional information is then used to supplement the first registration information of the target database, resulting in second registration information. This process enables real-time supplementation of the first registration information during application system usage. After obtaining the second registration information of the target database, data analysts can directly determine the required database based on this second registration information, which includes functional information. This reduces the difficulty for data analysts in identifying the source data needed by business personnel, decreases the reliance on data analysts' experience in bank data analysis work, and facilitates the rapid development of the bank's data analysis team.

[0123] Besides the functional modules, the application system and other modules that indicate the path to the functional module also indicate functional information. For example, for the information modification submodule under the account information module in the loan system corresponding to Bank A, the functional information of the target database corresponding to this information modification submodule could be "modify the account information of loan applicants in Bank A". It can be seen that, in addition to the relevant information of the information modification submodule, the relevant information of the application system and the account information module will help in determining the functional information. In one implementation, the functional information module 42 is used for:

[0124] From the multiple modules included in the application system, determine at least one target module used by the access event to invoke the functional module;

[0125] Based on the relevant information of the application system, the target module, and the functional module, the functional information of the target database is determined.

[0126] The target module is a module in the application system required when calling the functional module. The target module can be a parent module of the functional module.

[0127] After determining the functional modules, at least one target module corresponding to each functional module can be identified. Then, based on relevant information from the application system, the target module, and the functional module, the functional information can be determined. This specification does not specify the content of the relevant information from the application system and the target module; these can be determined based on the actual situation.

[0128] In one example, similar to the information related to functional modules, the information related to the application system can include the name of the application system, and the information related to the target module can also include the name of the target module. In this way, the process supplements the functional information containing the relevant information of the functional modules by using the relevant information from the application system and the target module, improving the accuracy of the functional information. This, in turn, improves the accuracy with which users can find the required database based on the second registration information containing the functional information.

[0129] Because large language models (LLMs) have advantages such as fast training speed, good interpretability, and strong generalization ability, they can be used to extract information from the aforementioned related information to obtain functional information. In one implementation, the related information includes a name. As an example, functional information module 42 is specifically used for:

[0130] Based on the application name of the application system, the module name of the functional module, and the module name of the target module, generate descriptive text describing the event that calls the functional module;

[0131] The descriptive text is input into a large language model to obtain the functional information.

[0132] The description text describes the path to the called functional module. Specifically, the description text is obtained by concatenating the application name of the application system, the module name of the target module, and the module name of the functional module in sequence.

[0133] Furthermore, the descriptive text can be input into a large language model, which can then extract information from the text to obtain functional information. In this way, extracting functional information from the descriptive text using a large language model leverages the powerful processing capabilities of the model to enhance the accuracy of the functional information.

[0134] The data asset system aggregates a large number of databases, and the required database can be identified using its address and name. In one implementation, the attribute information includes address data and name data, and the first information module 43 is used for:

[0135] The log message is parsed to obtain the address data and the SQL query statement corresponding to the access event;

[0136] The SQL query statement is parsed to obtain the name data;

[0137] From the data source system, determine the first registration information that matches the name data and the address data.

[0138] Specifically, the address data of the target database and the SQL query statement corresponding to the access event can be directly parsed from the log message. Since the SQL query statement contains the name data of the target database, the SQL query statement can be parsed to obtain the name data of the target database.

[0139] After obtaining the name and address data, the name and address data can be used to accurately locate the first registration information in the data source system, thereby improving the accuracy of the information registration process.

[0140] Figure 2 A schematic diagram of the data source system architecture is shown. For example... Figure 2 As shown, the data source system manages N application systems, each corresponding to at least one database. Databases directly corresponding to application systems may be associated with other databases, such as database 1 and database M2 being related. Typically, associated databases have related functions. For example, a database related to loan operations is unlikely to be associated with a database related to deposit operations. Therefore, the functional information of the target database can be calibrated using the functional information of associated databases to correct potential errors in determining the functional information.

[0141] In one implementation, the second information module 44 is used for:

[0142] Obtain the cluster address to which the address data belongs, and determine the reference function information of the database corresponding to the cluster address;

[0143] The reference functional information is used to calibrate the functional information to obtain calibrated functional information.

[0144] The first registration information is supplemented using the calibrated functional information to obtain the second registration information of the target database.

[0145] Specifically, the address data of the target database can be used to determine the address of the parent database (i.e., the cluster address). The functional information of the database corresponding to this cluster address serves as reference functional information. This reference functional information can then be used to calibrate the functional information, resulting in calibrated functional information. This calibration process can involve correcting errors in the functional information (such as incorrect attribution of functional modules).

[0146] Furthermore, the calibrated functional information can be used to supplement the first registration information to obtain the second registration information. In this way, determining the second registration information using the calibrated functional information improves the accuracy of the second registration information, enabling accurate retrieval of the target database.

[0147] After obtaining the second registration information, the second registration information can be used to search the required database. In one implementation, the apparatus includes:

[0148] The receiving module is configured to receive the target application name and target function name input by the user after the first registration information is supplemented by the function information to obtain the second registration information of the target database;

[0149] The information module is used to find the functional information that matches the target functional name from the second registration information corresponding to the application system with the target application name;

[0150] The matching module is used to identify the database to which the matched functional information belongs as the database searched by the user.

[0151] Here, "user" refers to the user of the data asset system, "target application name" is the name of the application system to which the database the user is searching belongs, and "target function name" is the name of the function that the database the user is searching has.

[0152] By using the target application name, the database under the application system to which the database the user is looking for belongs can be found from the data source system. Furthermore, by using the target function name, the database the user is looking for can be found from these databases.

[0153] Since the second registration information already contains functional information, the target application name and target function name can be used to quickly find the required database in the data source system.

[0154] Example 4

[0155] Figure 5 This is a schematic diagram of another information registration device provided in an embodiment of this application, used in an application system; as shown Figure 5 As shown, the device includes:

[0156] The message generation module 51 is used to record access events and generate log messages corresponding to the access events during the process of the application system accessing the target database.

[0157] The message sending module 52 is used to send the log message to the data asset system that manages the application system, so that the data asset system can accept the log message; determine the functional module that triggers the target database from the log message, and determine the functional information of the target database based on the relevant information of the functional module, wherein the functional module is a module in the application system; determine the first registration information of the target database from the data source system that registers the basic information of each database in the application system based on the attribute information of the target database in the log message; and use the functional information to supplement the first registration information to obtain the second registration information of the target database.

[0158] The log messages are generated by the application system during the process of accessing the target database, recording access events. The target database is at least one database accessed by the application system after receiving user operation instructions. This target database can be a database dedicated to a single application system or a database shared by multiple application systems. This specification does not specifically limit the relationship between the target database and the application system; it can be determined based on the actual situation.

[0159] This log message may include the Structured Query Language (SQL) query statement used by the application system to access the database (SQL statement for short), the database address (Internet Protocol, IP), the name of the application system, and the functional module in the application system that accesses the database. This log message can be recorded in JSON string format.

[0160] A functional module is a module included in an application system that can trigger at least one target database. For example, if it is necessary to find the operating data of Bank A for each quarter, the quarterly operating data module can be used to trigger the database containing the operating data for each quarter. Since the log messages recording access events record the quarterly operating data module, information about the quarterly operating data module (such as name, address, etc.) can be extracted from the log messages.

[0161] The relevant information includes the name of the functional module, its upstream and downstream modules (i.e., modules containing the functional module, and modules contained in the functional module), and the users who use the functional module. This information contains data describing the function of the functional module (i.e., functional information). Therefore, the functional information of the target database can be extracted from this information.

[0162] The first registration information refers to the information of the target database registered during the application system construction process. The data source system is a system for summarizing, registering, and managing information from databases belonging to multiple application systems. Specifically, during the construction of the data source system, the first registration information of each database managed by the data source system can be recorded based on a pre-defined data table. Table 1 shows the table for registering the first registration information. As shown in Table 1, the first registration information may include basic information such as the database number of the target database.

[0163] As mentioned earlier, in addition to functional modules, log messages can also record attribute information such as the address of the target database. Since this attribute information is recorded in the first registration information, the corresponding first registration information of the target database can be found in the data source system using this attribute information.

[0164] After finding the first registration information, the functional information in step S102 can be used to supplement the first registration information, and the processed information becomes the second registration information. Since the second registration information includes functional information, after obtaining the second registration information, the target database can be searched in multiple databases under the data asset system through the functional information it contains.

[0165] Specifically, during the use of the application system, second registration information for each database accessed during the process can be recorded based on a preset data table. Table 2 shows the table for registering second registration information. As shown in Table 2, in addition to the first registration information, the second registration information may include information related to the access event, such as the application system name and function name. The function name is a name obtained by further refining the function information; if the function information is concise, it can be directly used as the function name. Furthermore, the second registration information may also include the time of supplementary registration.

[0166] In this example, during the application system's access to the target database, log messages are generated. Functional modules are identified from these log messages, and then the functional information of the target database is determined based on the relevant information of these modules. This functional information is then used to supplement the first registration information of the target database, resulting in second registration information. This process enables real-time supplementation of the first registration information during application system usage. After obtaining the second registration information of the target database, data analysts can directly determine the required database based on this second registration information, which includes functional information. This reduces the difficulty for data analysts in identifying the source data needed by business personnel, decreases the reliance on data analysts' experience in bank data analysis work, and facilitates the rapid development of the bank's data analysis team.

[0167] In one implementation, the message sending module 52 is configured to:

[0168] The log message is sent to the data asset system via the QUIC protocol.

[0169] The Quick User Datagram Protocol Internet Connection (QUIC) is a secure and reliable transport protocol based on UDP (User Datagram Protocol). Compared to TCP (Transmission Control Protocol), QUIC integrates Transport Layer Security (TLS) for encrypted data transmission. Furthermore, QUIC supports multi-stream concurrency, resulting in faster transmission speeds, and requires only a single handshake to establish a connection, leading to low latency.

[0170] In one example, the QUIC protocol can be used to send log messages from the application system to the data asset system as a stream, thereby improving both the speed and security of log message transmission.

[0171] Example 5

[0172] Figure 6 This application provides a schematic diagram of the structure of an electronic device, which includes:

[0173] The device includes a processor 691 and a memory 692; it may also include a communication interface 693 and a bus 694. The processor 691, memory 692, and communication interface 693 can communicate with each other via the bus 694. The communication interface 693 can be used for information transmission. The processor 691 can invoke logical instructions stored in the memory 692 to execute the methods described in the example above.

[0174] Furthermore, the logic instructions in the aforementioned memory 692 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium.

[0175] The memory 692, as a computer-readable storage medium, can be used to store software programs and computer-executable programs, such as program instructions / modules corresponding to the methods in the embodiments of this application. The processor 691 executes functional applications and data processing by running the software programs, instructions, and modules stored in the memory 692, that is, it implements the methods in the above method examples.

[0176] The memory 692 may include a program storage area and a data storage area. The program storage area may store the operating system and application programs required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 692 may include high-speed random access memory and may also include non-volatile memory.

[0177] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method in any of the embodiments.

[0178] This application also provides a computer program product, including a computer program that, when executed by a processor, is used to implement the method in any of the embodiments.

[0179] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0180] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0181] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0182] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0183] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0184] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0185] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0186] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0187] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. An information registration method, characterized in that, For use in a data asset system, the method includes: The system receives log messages sent by the application systems managed by the data asset system. These log messages are generated by the application systems during the process of accessing the target database by recording access events. From the log messages, determine the functional modules in the application system that trigger the target database, and based on the relevant information of the functional modules, determine the functional information describing the function of the target database; Based on the attribute information of the target database in the log message, the first registration information of the target database is determined from the data source system that registers the basic information of each database in the application system; The first registration information is supplemented using the functional information to obtain the second registration information of the target database, so as to realize the search of the target database through the functional information in the second registration information.

2. The method according to claim 1, characterized in that, The step of determining the functional information describing the target database function based on the relevant information of the functional module includes: From the multiple modules included in the application system, determine at least one target module used by the access event to invoke the functional module; Based on the relevant information of the application system, the target module, and the functional module, the functional information of the target database is determined.

3. The method according to claim 2, characterized in that, The relevant information includes names, and the functional information of determining the target database based on the application system, the target module, and the functional modules includes: Based on the application name of the application system, the module name of the functional module, and the module name of the target module, generate descriptive text describing the event that calls the functional module; The descriptive text is input into a large language model to obtain the functional information.

4. The method according to any one of claims 1-3, characterized in that, The attribute information includes address data and name data. Based on the attribute information of the target database in the log message, the first registration information of the target database is determined from the data source system that registers the basic information of each database in the application system, including: The log message is parsed to obtain the address data and the SQL query statement corresponding to the access event; The SQL query statement is parsed to obtain the name data; From the data source system, determine the first registration information that matches the name data and the address data.

5. The method according to claim 4, characterized in that, The process of supplementing the first registration information with the functional information to obtain the second registration information in the target database includes: Obtain the cluster address to which the address data belongs, and determine the reference function information of the database corresponding to the cluster address; The reference functional information is used to calibrate the functional information to obtain calibrated functional information. The first registration information is supplemented using the calibrated functional information to obtain the second registration information of the target database.

6. The method according to any one of claims 1-3, characterized in that, After supplementing the first registration information with the functional information to obtain the second registration information in the target database, the method includes: Receive the target application name and target function name input by the user; Find the functional information that matches the target functional name from the second registration information corresponding to the application system with the target application name; The database to which the matched functional information belongs is used as the database searched by the user.

7. An information registration method, characterized in that, For use in an application system, the method includes: During the process of the application system accessing the target database, access events are recorded and log messages corresponding to the access events are generated; The log message is sent to the data asset system that manages the application system, so that the data asset system accepts the log message; from the log message, the functional module that triggers the target database is identified, and based on the relevant information of the functional module, the functional information of the target database is determined, wherein the functional module is a module in the application system; based on the attribute information of the target database in the log message, the first registration information of the target database is determined from the data source system that registers the basic information of each database in the application system; the first registration information is supplemented with the functional information to obtain the second registration information of the target database.

8. The method according to claim 7, characterized in that, Sending the log message to the data asset system that manages the application system includes: The log message is sent to the data asset system via the QUIC protocol.

9. An information registration device, characterized in that, For a data asset system, the apparatus includes: The message receiving module is used to receive log messages sent by the application system managed by the data asset system. The log messages are generated by the application system recording access events during the process of accessing the target database. The functional information module is used to determine, from the log message, the functional module in the application system that triggers the target database, and to determine, based on the relevant information of the functional module, functional information describing the function of the target database. The first information module is used to determine the first registration information of the target database from the data source system that registers the basic information of each database in the application system, based on the attribute information of the target database in the log message; The second information module is used to supplement the first registration information with the functional information to obtain the second registration information of the target database, so as to realize the search of the target database through the functional information in the second registration information.

10. An information registration device, characterized in that, For use in an application system, the device includes: The message generation module is used to record access events and generate log messages corresponding to the access events during the process of the application system accessing the target database. A message sending module is used to send the log message to the data asset system that manages the application system, so that the data asset system can accept the log message; determine the functional module that triggers the target database from the log message, and determine the functional information of the target database based on the relevant information of the functional module, wherein the functional module is a module in the application system; determine the first registration information of the target database from the data source system that registers the basic information of each database in the application system based on the attribute information of the target database in the log message; and use the functional information to supplement the first registration information to obtain the second registration information of the target database.

11. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 8.

13. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 8.

Images