Label query method and device

Abstract

The invention discloses a label query method and device. In order to deal with the characteristics that label data is large in volume and high in sparsity and metadata is used for describing label attributes, a strategy of separately storing the labels and the label metadata is adopted, and the storage space is saved. And a corresponding relation between the two is established, and preparation for high-performance query and loading is made on a storage level. According to query data input by a user, a target tag and target tag metadata corresponding to the query data are obtained. In order to meet the requirements of authority control and flexible customization of query, the query data comprises a customer number to be queried and a template number / a tag number to be queried of a target scene. And when the target label and the target label metadata do not exist, obtaining a preset default label value and returning the preset default label value to the user so as to realize service degradation. According to the method, management operations such as efficient storage and quick query are supported for a huge number of customers and various customer types.

Description

Technical Field

[0001] The present application relates to the field of data management technology, and in particular to a tag query method and device. Background Art

[0002] In the field of data management, tags are a way to associate data with metadata (such as categories, attributes, keywords, etc.). By adding tags to data, it is easier to categorize, filter, and search it. Large banks often have tag management systems that assign tags to customers and associate these tags with specific data or services. When sales staff connect with customers, they can respond quickly through tags and provide corresponding data or services.

[0003] In the existing technology, facing a large number of customers and customer types, tags have the characteristics of large data volume and sparseness. For example, a bank has a total of 6,000 tags for customers. For a customer, only 1,000 tags may have values, and the remaining 5,000 tags are empty. A large number of sparse tags require a certain amount of storage space, query and loading performance, and there may be problems such as insufficient response time and insufficient real-time tag updates during operation. Therefore, how to efficiently store, query and manage massive customer tags has become an urgent problem to be solved. Summary of the invention

[0004] Based on the above problems, the present application provides a method and device for label query to efficiently perform management operations such as storage and query on massive customer labels.

[0005] The present application discloses a tag query method, the method comprising:

[0006] Storing tags, tag metadata, and the corresponding relationship between the tag metadata and the tags;

[0007] According to the query data input by the user, a target tag and target tag metadata corresponding to the query data are obtained; the query data includes a customer number to be queried, and a template number / tag number to be queried of the target scene;

[0008] When the target tag and the target tag metadata do not exist, a default tag value is obtained and returned to the user.

[0009] Optionally, the storage tag, tag metadata, and the corresponding relationship between the tag metadata and the tag include:

[0010] Access tags from the data lake warehouse and write the tags into the tag library; the tags include batch tags and streaming tags;

[0011] The corresponding relationship between the tag and the tag metadata is preset, and the tag metadata and the corresponding relationship are written into a cache library and a configuration library.

[0012] Optionally, acquiring, according to the query data input by the user, a target tag and target tag metadata corresponding to the query data, includes:

[0013] Obtaining the module number of the module used by the user when calling the online interface;

[0014] receiving query data input by the user from the online interface;

[0015] Querying a target tag corresponding to the query data;

[0016] Querying target tag metadata that has a corresponding relationship with the target tag;

[0017] The target tag and the target tag metadata are used as query results and returned to the user through the online interface.

[0018] Optionally, when the query data includes the tag number to be queried, the receiving the query data input by the user from the online interface includes:

[0019] The tag numbers to be queried input by the user are received one by one, or the tag numbers to be queried selected by the user from fixed tag numbers provided by a tag template are received.

[0020] Optionally, after obtaining the default tag value and returning it to the user, the method further includes:

[0021] The module displays preset information corresponding to the default tag value to the user.

[0022] Based on the above-mentioned tag query method, the present application also discloses a tag query device, including: a storage unit, a query unit and a default unit;

[0023] The storage unit is used to store tags, tag metadata, and the corresponding relationship between the tag metadata and the tags;

[0024] The query unit is used to obtain the target tag and target tag metadata corresponding to the query data according to the query data input by the user; the query data includes the customer number to be queried and the template number / tag number to be queried of the target scene;

[0025] The default unit is used to obtain a default tag value and return it to the user when the target tag and the target tag metadata do not exist.

[0026] Optionally, the storage unit includes:

[0027] The tag writing subunit is used to access tags from the data lake warehouse and write the tags into the tag library; the tags include batch tags and streaming tags;

[0028] The relationship writing subunit is used to preset the corresponding relationship between the tag and the tag metadata, and write the tag metadata and the corresponding relationship into the cache library and the configuration library.

[0029] Optionally, the query unit includes:

[0030] An acquisition subunit, used to acquire the module number of the module used by the user when calling the online interface;

[0031] A receiving subunit, configured to receive query data input by the user from the online interface;

[0032] A tag query subunit, used to query a target tag corresponding to the query data;

[0033] A metadata query subunit, used to query target tag metadata that has a corresponding relationship with the target tag;

[0034] The return subunit is used to return the target tag and the target tag metadata as query results to the user through the online interface.

[0035] Optionally, when the query data includes the tag number to be queried, the receiving subunit is used to:

[0036] The tag numbers to be queried input by the user are received one by one, or the tag numbers to be queried selected by the user from fixed tag numbers provided by a tag template are received.

[0037] Optionally, the device further comprises:

[0038] A display unit is used for the module to display preset information corresponding to the default tag value to the user.

[0039] The present application discloses a method and device for tag query. In order to cope with the characteristics of large volume and strong sparsity of tag data and metadata used to describe tag attributes, the present application adopts a strategy of storing tags and tag metadata separately to save storage space. A corresponding relationship between them is established, and preparations for high-performance query and loading are made at the storage level. According to the query data input by the user, the target tag and target tag metadata corresponding to the query data are obtained. In order to meet the authority control and flexible customization requirements of the query, the query data includes the customer number to be queried, and the template number / tag number to be queried of the target scene. When the target tag and target tag metadata do not exist, a pre-set default tag value is obtained and returned to the user to achieve service degradation. When faced with a large number of customers and a variety of customer types, the present application supports management operations such as efficient storage and fast query. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0041] Figure 1 A flowchart of a tag query method disclosed in an embodiment of the present application;

[0042] Figure 2 A flowchart of another tag query method disclosed in an embodiment of the present application;

[0043] Figure 3 A schematic diagram of the structure of a label query device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0044] Before elaborating on the contents of this application, we first briefly introduce the professional terms involved to ensure consistency and accuracy of understanding.

[0045] Tags in the banking industry: Descriptive information such as attributes, characteristics, and behaviors that are constructed based on various data information and used for customer or product classification analysis. For example, there are transaction tags such as the amount of inter-bank transfer transactions and the number of wealth management transactions in the past year; attribute tags such as customer age, region, and occupation; asset tags such as the daily AUM balance, demand deposit balance, and monthly average balance of wealth management; product tags such as the number of products held, wealth management holding mark, and third-party payment holding mark; and risk tags such as the number of overdue months, principal, and interest.

[0046] Tag Metadata: Tag metadata is information about the tag itself, which describes the tag's attributes, definition, purpose, etc. Metadata is crucial to understanding and using tags, as it helps users understand the meaning and applicability of tags.

[0047] Service degradation: Service degradation refers to the simplification or shutdown of some non-core services to ensure the normal operation of core services when the system pressure is too high or a failure occurs. Service degradation is one of the important means of system high availability and fault tolerance.

[0048] Data Lake Warehouse: A data management and analysis system that combines the advantages of a data warehouse and a data lake. The system stores data in a distributed file system. It not only has the flexibility of a data lake to store massive and diverse data, but also provides functions similar to relational databases, including query, data aggregation, and association analysis. Data Lake Warehouse is widely used in multiple scenarios, such as business decision support, business analysis, personalized recommendation services, and risk control, and can provide powerful data processing and analysis capabilities.

[0049] Multidimensional mapping distributed database: It is a distributed and scalable column storage system. It has the characteristics of distributed storage, column storage, high reliability, high performance, etc., and is suitable for large-scale data storage and OLTP queries.

[0050] OLTP (Online Transaction Processing): Online transaction processing, usually used to process real-time, high-concurrency, and high-throughput transaction requests.

[0051] In the current market, the number of customers of large commercial banks has reached billions, and the customer volume can reach 8 billion by expanding in the dimensions of head office, branches, and institutions. The service objects include individual customers and corporate customers, covering various topics such as basic attributes, financial attributes, preference attributes, and thousands of tags for a single customer. The method described in this application can be used to solve the problem of high-performance label online services for billions of bank customers, head office / branch / institution dimensions, and thousands of tags. The method described in this application can effectively support the construction of accurate user portraits and product marketing and other service scenarios for multiple key customer contact points such as mobile banking, online banking, counter services, ATMs, etc., and can be regarded as an important reference and practical solution for large commercial banks to build data-friendly label online service systems in the field of big data.

[0052] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0053] Embodiment 1: This application discloses a tag query method.

[0054] For details, please refer to Figure 1 A tag query method disclosed in this embodiment includes the following steps:

[0055] Step 101: Store tags, tag metadata, and the corresponding relationship between the tag metadata and the tags.

[0056] In the method described in this embodiment, the tags may include batch tags and streaming tags, wherein batch tags can be used to uniformly identify and classify large-scale data, while streaming tags focus more on the real-time nature of tags.

[0057] The two types of tags are connected from the data lake warehouse, and the tags are written into the tag library through the data access component. The correspondence between tags and tag metadata is preset, and the data access component writes the tag metadata and the correspondence into the cache library and configuration library, and the tags and tag metadata are stored separately. Among them, the tag library can adopt a distributed database of the Key-Value class with multidimensional mapping for column family data (data organized into a set of related columns). The Key-Value database is a non-relational database whose data storage model is based on key-value pairs. Each data item consists of a unique key and an associated value. The configuration library can use a relational database, and the cache library can introduce an in-memory database as a cache of tags and corresponding relationships.

[0058] As an optional method, the change personnel can use the change management system to preset or modify the correspondence, or they can automatically set the correspondence for the labels and label metadata through the model. There is no limitation on how to set the correspondence and the specific content of the correspondence. It is sufficient to complete the steps described in this embodiment.

[0059] In the method described in this embodiment, two tag storage schemes are designed to adapt to the multi-dimensional mapping distributed database. Among them, the first scheme is to use the tag number as the column key to store a single tag value, as shown in the following table:

[0060] Table 1 Tag storage scheme 1

[0061]

[0062] Solution 2 uses the source table name as the column key and stores a set of label values, as shown in the following table:

[0063] Table 2 Schematic diagram of tag storage solution 2

[0064]

[0065] The above two solutions can be applied to different scenarios and play different advantages. Take the following scenario as an example: there are 1 million customers and 3,000 tags, and the query requirement is to query 50 tags at a time. When using solution 1, the number of storage columns is 3,000, each column stores 1 tag, and the tag values ​​of 50 columns are queried. When using solution 2, the number of storage columns is 150, each column stores 20 tags, 10 columns of data are selected, and 5 tags are queried from each column.

[0066] From the analysis of the examples of the above two solutions, it can be seen that when performing data query, Solution 1 directly reads 50 columns of label values, while Solution 2 needs to read 10 columns of complete label values ​​(a total of 200) before filtering. Compared with Solution 1, Solution 2 shows an increasing trend in both disk and network input and output (I / O). When writing data, Solution 2 converts the underlying storage file of the label library to occupy fewer bytes, which is smaller than Solution 1 in storage and takes less time to load. Therefore, Solution 1 has obvious advantages in average transaction response time, and Solution 2 has high storage efficiency and short label batch update time. This embodiment can switch between Solution 1 and Solution 2 according to different scenario requirements to achieve the best effect. For example, Solution 1 is used in scenarios with high response time requirements, and Solution 2 is used in scenarios with high storage efficiency and label update speed requirements.

[0067] Step 102: According to the query data input by the user, a target tag and target tag metadata corresponding to the query data are obtained.

[0068] In the method described in this embodiment, the user system can call the online interface and input the query data. The query data may include the customer number to be queried, and the template number of the target scene or the tag number to be queried. Among them, the template of the target scene is the information such as the tag corresponding to the scene that is preset under a specific scene (such as a business). The content of the template, how to set it, etc. are not specifically limited here, and it is sufficient to be able to implement the method in the steps of this embodiment.

[0069] In the method described in this embodiment, the module number of the module used by the user when calling the online interface, that is, the user's system number, is obtained. Receive the query data input by the user from the online interface. As an optional method, when the query data includes the tag number to be queried, this step can specifically be to receive the tag numbers to be queried input by the user one by one, or to receive the tag number to be queried selected by the user from the fixed tag numbers provided by the tag template. As another optional method, receive the template number input by the user from the online interface, and automatically obtain the template content according to the template number.

[0070] In the method described in this embodiment, the target tag corresponding to the query data is queried, and the target tag metadata corresponding to the target tag is queried. The target tag and the target tag metadata are used as query results and returned to the user through the online interface.

[0071] As an optional method, a unified service interface can be used for individual customers and corporate customers to solve the problem of multiple interfaces and difficult management on the user side. Specifically, the device described in this embodiment provides a unified interface to the outside, supporting the user to flexibly and quickly query the label according to the template number, the label number to be queried (one or more) or the label template to select the label number to be queried.

[0072] In the method described in this embodiment, the tag can be updated at a frequency of daily / weekly / monthly according to the needs of the user. When performing a tag query, in order to ensure the accuracy of the acquired tags, the date field can be used for filtering to meet scenarios such as monthly business. As an optional method, after the user enters the query data, the tag date corresponding to the target tag is obtained based on the target tag and target tag metadata.

[0073] For example, in the banking business scenario, as of September 30, the cumulative number of active customer tags for the month is 200 million. Starting October 1, the tags of active customers for the month should be recalculated. On that day, the newly added active customer tags in the upstream batch update are 10 million, while the tags of the remaining 190 million customers are still in the status of September. Therefore, filtering can be performed by date field to truly reflect the tags of active customers for the month on October 1.

[0074] In the method described in this embodiment, when updating labels, batch labels can be regularly loaded into the label library through batch jobs, and the date field of the label structure information table in the configuration library is updated when the loading is completed. At the same time, the label library can be set to save two versions of data, so as to play a checking role and ensure that the labels queried before and after the batch label loading are of the correct date. As an optional method, it can be specifically to generate an underlying storage file containing label information (such as metadata, corresponding relationships, etc.) through a batch task, load it in batches, and store it in the label library. Update the label structure information and label query template in the configuration library, and refresh the updated label structure information and label query template to the cache library. Finally, verify it in the actual application scenario to ensure that the updated labels can perform queries and other operations normally.

[0075] In the method described in this embodiment, the streaming tags can be written into the tag library in real time through the message queue at a controlled rate, and the date field of the tag structure information table in the configuration library is updated when the date changes, to ensure that the streaming tags are queried normally before and after the date changes. As an optional method, it can be specifically to stop writing tags to the message queue in real time, write these tags into the tag library, update the tag structure information and tag query template in the configuration library, and refresh the updated tag structure information and tag query template to the cache library. After the refresh is completed and it is verified that the data in the cache library has been updated to the latest, the real-time written tags are received again. And verification is performed in the pipeline process of data processing, and the updated tags can be queried normally.

[0076] In the method described in this embodiment, in order to meet the requirements of different business continuity and transaction response time, this embodiment adopts a hierarchical service design, which is divided into label important service and label general service. These two services adopt different solutions in terms of change frequency, query logic and label distribution.

[0077] First, in terms of change frequency, the label important service provides stable label online services for high-level businesses, and the label template and label structure are basically fixed, with low change frequency. The label general service is aimed at general-level businesses, such as scenarios with requirements for continuity and transaction response time, and supports flexible customization of label templates, which can quickly meet business pilot service scenarios. Label templates and label structures change frequently and are implemented through changes.

[0078] In terms of query logic, when querying online, the tag important service queries and returns the tag number and tag value. The user system completes the tag structure information as needed in the subsequent logical processing. When querying online, the tag general service obtains the tag structure information and returns it together with the target tag and target tag metadata, which the user system can directly use for subsequent logical processing.

[0079] In terms of label distribution, the number of labels at the national, provincial, and institutional levels can be adjusted as needed. The specific number is not limited here, as long as the number of labels corresponding to important services is less than the number of labels corresponding to general services.

[0080] Step 103: When the target tag and the target tag metadata do not exist, a default tag value is obtained and returned to the user.

[0081] In the method described in this embodiment, the module used when the user calls the online interface displays the preset information corresponding to the default tag value to the user. As an optional method, when an exception or other situation occurs in the back-end database of the tag online service, the corresponding default tag value can be directly returned. The tag value corresponds to various situations, and the module used when the user calls the online interface can respond and reply to the user's fixed policy, thereby ensuring the continuity of business services. The content of the default tag value and the corresponding situation are not specifically limited here, and it is sufficient to meet the method described in this embodiment.

[0082] In order to cope with the large volume and strong sparsity of tag data and the characteristics of metadata used to describe tag attributes, the method described in this embodiment adopts a strategy of storing tags and tag metadata separately to save storage space. A corresponding relationship between them is established, and preparations are made for high-performance query and loading at the storage level to achieve efficient storage and support fast query. It also supports the storage of two time versions of tags, which is convenient for verifying the accuracy of tags after the update is completed. Different design schemes are adopted for batch tags and streaming tags in terms of update process and structural changes. In order to meet the requirements of query permission control and flexible customization, the query data includes the customer number to be queried, and the template number / tag number to be queried of the target scenario, supports tag storage and query combined with actual business scenarios, and shortens the query link. When the target tag and target tag metadata do not exist, the preset default tag value is obtained and returned to the user to achieve service degradation. At the same time, a unified interface is designed to avoid management confusion caused by the increase in the number of interfaces. In addition, a hierarchical service is designed, and different designs are adopted in terms of change frequency, query logic and tag distribution, so as to have the service capability to cope with different business requirements.

[0083] Example 2: This application discloses another tag query method, please refer to Figure 2 , the method described in this embodiment introduces the whole process of label query.

[0084] Step 201: Import batch tags and streaming tags from the data lake warehouse and write them into the tag library.

[0085] Step 202: Write the tag metadata and the corresponding relationship between the tag metadata and the tag into the configuration library and the cache library.

[0086] Step 203: The user system calls the online interface and inputs query data.

[0087] Step 204: Determine whether the tag and the tag metadata corresponding to the tag can be obtained according to the query data. If yes, proceed to step 205. If yes, proceed to step 206.

[0088] Step 205: Assemble the tag and tag metadata and return them to the user system.

[0089] Step 206: Return the default tag value to the user system.

[0090] Based on the method for tag query disclosed in the above embodiment, this embodiment correspondingly discloses a device for tag query. Figure 3 , the label query device includes: a storage unit 301, a query unit 302 and a default unit 303;

[0091] The storage unit 301 is used to store tags, tag metadata, and the corresponding relationship between the tag metadata and the tags;

[0092] The query unit 302 is used to obtain the target tag and target tag metadata corresponding to the query data according to the query data input by the user; the query data includes the customer number to be queried and the template number / tag number to be queried of the target scene;

[0093] The default unit 303 is used to obtain a default tag value and return it to the user when the target tag and the target tag metadata do not exist.

[0094] Optionally, the storage unit 301 includes:

[0095] The tag writing subunit is used to access tags from the data lake warehouse and write the tags into the tag library; the tags include batch tags and streaming tags;

[0096] The relationship writing subunit is used to preset the corresponding relationship between the tag and the tag metadata, and write the tag metadata and the corresponding relationship into the cache library and the configuration library.

[0097] Optionally, the query unit 302 includes:

[0098] An acquisition subunit, used to acquire the module number of the module used by the user when calling the online interface;

[0099] A receiving subunit, configured to receive query data input by the user from the online interface;

[0100] A tag query subunit, used to query a target tag corresponding to the query data;

[0101] A metadata query subunit, used to query target tag metadata that has a corresponding relationship with the target tag;

[0102] The return subunit is used to return the target tag and the target tag metadata as query results to the user through the online interface.

[0103] Optionally, when the query data includes the tag number to be queried, the receiving subunit is used to:

[0104] The tag numbers to be queried input by the user are received one by one, or the tag numbers to be queried selected by the user from fixed tag numbers provided by a tag template are received.

[0105] Optionally, the device further comprises:

[0106] A display unit is used for the module to display preset information corresponding to the default tag value to the user.

[0107] The embodiments in this specification are described in a progressive manner. As for the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the methods.

[0108] 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, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0109] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

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

[0111] The features described in the embodiments of this specification can be replaced or combined with each other, so that professional and technical personnel in this field can implement or use the present application.

[0112] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A tag query method, characterized in that: include: Storing tags, tag metadata, and the corresponding relationship between the tag metadata and the tags; According to the query data input by the user, a target tag and target tag metadata corresponding to the query data are obtained; the query data includes a customer number to be queried, and a template number / tag number to be queried of the target scene; When the target tag and the target tag metadata do not exist, a default tag value is obtained and returned to the user.

2. The method according to claim 1, characterized in that The storage tag, tag metadata, and the corresponding relationship between the tag metadata and the tag include: Access tags from the data lake warehouse and write the tags into the tag library; the tags include batch tags and streaming tags; The corresponding relationship between the tag and the tag metadata is preset, and the tag metadata and the corresponding relationship are written into a cache library and a configuration library.

3. The method according to claim 1, characterized in that The step of acquiring a target tag and target tag metadata corresponding to the query data according to the query data input by the user includes: Obtaining the module number of the module used by the user when calling the online interface; receiving query data input by the user from the online interface; Querying a target tag corresponding to the query data; Querying target tag metadata that has a corresponding relationship with the target tag; The target tag and the target tag metadata are used as query results and returned to the user through the online interface.

4. The method according to claim 3, characterized in that When the query data includes the tag number to be queried, the receiving the query data input by the user from the online interface includes: The tag numbers to be queried input by the user are received one by one, or the tag numbers to be queried selected by the user from fixed tag numbers provided by a tag template are received.

5. The method according to claim 3, characterized in that: After obtaining the default tag value and returning it to the user, the method further includes: The module displays preset information corresponding to the default tag value to the user.

6. A label query device, characterized in that: include: storage unit, query unit and default unit; The storage unit is used to store tags, tag metadata, and the corresponding relationship between the tag metadata and the tags; The query unit is used to obtain the target tag and target tag metadata corresponding to the query data according to the query data input by the user; the query data includes the customer number to be queried and the template number / tag number to be queried of the target scene; The default unit is used to obtain a default tag value and return it to the user when the target tag and the target tag metadata do not exist.

7. The device according to claim 6, characterized in that The storage unit comprises: The tag writing subunit is used to access tags from the data lake warehouse and write the tags into the tag library; the tags include batch tags and streaming tags; The relationship writing subunit is used to preset the corresponding relationship between the tag and the tag metadata, and write the tag metadata and the corresponding relationship into the cache library and the configuration library.

8. The device according to claim 6, characterized in that The query unit comprises: An acquisition subunit, used to acquire the module number of the module used by the user when calling the online interface; A receiving subunit, configured to receive query data input by the user from the online interface; A tag query subunit, used to query a target tag corresponding to the query data; A metadata query subunit, used to query target tag metadata that has a corresponding relationship with the target tag; The return subunit is used to return the target tag and the target tag metadata as query results to the user through the online interface.

9. The device according to claim 8, characterized in that When the query data includes the tag number to be queried, the receiving subunit is used to: The tag numbers to be queried input by the user are received one by one, or the tag numbers to be queried selected by the user from fixed tag numbers provided by a tag template are received.

10. The device according to claim 8, characterized in that The device also includes: A display unit is used for the module to display preset information corresponding to the default tag value to the user.

Images