Tagged Data Management Method, Device, Equipment and Computer Readable Storage Medium

Abstract

The present invention relates to the technical field of financial technology (Fintech). The present invention discloses a method, device, equipment and computer-readable storage medium for managing tagged data; the method includes: when receiving a request message uploaded by a third-party service platform, invoking a tagged data management component; according to the registry configuration information in the tagged data management component, performing format conversion on each piece of service data in the request message to obtain formatted service data; constructing data tags for the formatted service data, and saving the formatted service data to a tagged data storage table according to the data tags; when receiving a data query request, querying the tagged data storage table according to the primary key value in the data query request, and outputting a data query table. The present invention presets a tagged data management component, and performs unified management of data from different service platforms through the tagged data management component, which facilitates data querying.

Description

Technical Field

[0001] The present invention relates to the technical field of financial technology (Fintech), and particularly to a method, an apparatus, a device and a computer-readable storage medium for managing tagged data. Background Art

[0002] With the rapid development of Internet technology, especially Internet financial technology (Fintech), more and more technologies (big data, distributed, blockchain, artificial intelligence, etc.) are applied in the financial field, resulting in an explosive growth of financial services and business data related to financial services.

[0003] Currently, a financial service platform usually sets up a data storage table to store business data, so as to promote the development of financial services through effective management of business data. However, the financial service platform is not an isolated business system. A third-party business platform will call an external interface to interact with the financial service platform to process actual financial services. Due to the different business forms of the third-party business platform, the business data received by the financial service platform is also very different. Therefore, the current financial service platform needs to negotiate with the third-party business platform in advance and set up a data storage table according to the agreement content to store the received data. Such a data storage management method, due to the relatively fixed data storage table, when the business of the financial service platform or the third-party business platform changes, it is necessary to change the structure of the storage table, which cannot adapt to the rapid update of the financial service platform and the third-party business platform, and the later maintenance of the data storage table is inconvenient, and the business data management method is relatively troublesome. Summary of the Invention

[0004] The main purpose of the present invention is to propose a method, an apparatus, a device and a computer-readable storage medium for managing tagged data, aiming to solve the technical problems that the current data storage table is relatively fixed, when the business of the business platform changes, it is necessary to change the structure of the storage table, which cannot adapt to the rapid update of the business platform, the later maintenance of the data storage table is inconvenient, and the business data management method is relatively troublesome.

[0005] To achieve the above object, the present invention provides a method for managing tagged data, the method for managing tagged data includes the following steps:

[0006] When receiving a request message uploaded by a third-party business platform, call a tagged data management component;

[0007] According to the registry configuration information in the tagged data management component, perform format conversion on each business data in the request message to obtain formatted business data;

[0008] Construct data tags for the formatted business data, and save the formatted business data to a tagged data storage table according to the data tags;

[0009] When a data query request is received, query the tagged data storage table according to the primary key value in the data query request, and output a data query table.

[0010] Optionally, before the step of calling the tagged data management component when a third-party business platform upload request message is received, the method includes:

[0011] When a component configuration request is received, obtain the third-party platform identifier associated with the component configuration request, and obtain the component configuration page corresponding to the third-party platform identifier;

[0012] Obtain the registry configuration information input based on the component configuration page;

[0013] Import the registry configuration information into a preset common management component to generate a tagged data management component.

[0014] Optionally, after the step of importing the registry configuration information into a preset common management component to generate a tagged data management component, the method includes:

[0015] When it is detected that the generation of the tagged data management component is completed, determine whether the registry configuration information in the tagged data management component conforms to the component configuration rules;

[0016] When the registry configuration information does not conform to the component configuration rules, output a configuration error prompt;

[0017] When the registry configuration information conforms to the component configuration rules, output a storage table configuration prompt;

[0018] Receive the storage table configuration information input based on the storage table configuration prompt, and generate a tagged data storage table according to the storage table configuration information.

[0019] Optionally, the step of performing format conversion on each business data in the request message according to the registry configuration information in the tagged data management component to obtain formatted business data includes:

[0020] Import the registry configuration information in the tagged data management component into a registry factory class in the memory, load and call objects through the registry factory method to traverse the request message, and determine the data type of each business data according to the fields of each business data in the request message;

[0021] Check whether each piece of the service data conforms to the field check rules in the registry configuration information according to the data type, where the field check rules refer to the rules for detecting the field type, length, mandatory input, data format, and nesting relationship of the service data;

[0022] When the service data conforms to the field check rules, perform format conversion on the service data according to the data type of the service data to obtain formatted service data.

[0023] Optionally, the step of constructing a data label for the formatted service data and saving the formatted service data to a labeled data storage table according to the data label includes:

[0024] Find the primary key value associated with the request information through the registry factory method, obtain the data label corresponding to the primary key value, and the fields of the data label;

[0025] Compare the formatted service data with the fields corresponding to each data label, obtain the target fields that match the service data, and use the data label corresponding to the target fields as the data label of the service data;

[0026] Associate the service data according to the data label of the service data and the nesting relationship of the data label, and save it to the labeled data storage table.

[0027] Optionally, the step of querying the labeled data storage table according to the primary key value in the data query request and outputting a data query table when receiving a data query request includes:

[0028] When receiving a data query request, obtain the primary key value in the data query request;

[0029] Query the labeled data storage table to obtain each data label associated with the primary key value, the nesting relationship corresponding to each data label, and the service data corresponding to the data label;

[0030] Construct a data display template according to the data label and the nesting relationship, and output the service data to the data display template to generate a data query table.

[0031] Optionally, the step of calling a labeled data management component when receiving upload request information from a third-party service platform includes:

[0032] When receiving upload request information from a third-party service platform, obtain the service data in the request information and the data type of the service data;

[0033] Judge whether the data type of the service data is a new data type;

[0034] When the data type of the service data is a new data type, a component configuration request is triggered;

[0035] When the data type of the service data is not a new data type, a tagged data management component is called.

[0036] In addition, to achieve the above object, the present invention further provides a tagged data management device, the tagged data management device includes:

[0037] A component call module, configured to call a tagged data management component when receiving upload request information from a third-party service platform;

[0038] A format conversion module, configured to perform format conversion on each service data in the request information according to the registry configuration information in the tagged data management component to obtain formatted service data;

[0039] A data storage module, configured to construct data tags for the formatted service data and save the formatted service data to a tagged data storage table according to the data tags;

[0040] A data query module, configured to query the tagged data storage table according to the primary key value in the data query request when receiving a data query request, and output a data query table.

[0041] In addition, to achieve the above object, the present invention further provides a tagged data management device, the tagged data management device includes: a memory, a processor, and a tagged data management program stored on the memory and executable on the processor, and when the tagged data management program is executed by the processor, the steps of the above-mentioned tagged data management method are implemented.

[0042] In addition, to achieve the above object, the present invention further provides a computer-readable storage medium, on which a tagged data management program is stored, and when the tagged data management program is executed by a processor, the steps of the above-mentioned tagged data management method are implemented.

[0043] The present invention provides a method, apparatus, device, and computer-readable storage medium for managing tagged data. In an embodiment of the present invention, when a request message is uploaded from a third-party service platform, a tagged data management component is invoked; according to the registry configuration information in the tagged data management component, the format of each service data in the request message is converted to obtain formatted service data, and data format conversion is performed through a pre-customized tagged data management component, and corresponding data tags are added for storage. During later data query, the tagged data management device extracts the service data corresponding to the data identifier of the query request from the data storage table, and forms these service data into a data query table for convenient viewing and operation by the user. The tagged data management method in the embodiment of the present invention facilitates the later maintenance of the data storage table and the query operation of the user; at the same time, the data storage table is flexibly associated with the service platform. When the service of the financial service platform or the third-party service platform changes, by adjusting the configuration information of the tagged data management component, the data storage table can be updated without reconstructing the data storage table. Such a data management method supports the rapid update of the versions of the financial service platform and the third-party service platform, making the business data management method more reasonable. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present invention;

[0045] Figure 2 is a schematic flowchart of the construction of the tagged data management component in the first embodiment of the tagged data management method of the present invention;

[0046] Figure 3 is a schematic diagram of a specific component configuration page of the tagged data management component in the first embodiment of the tagged data management method of the present invention;

[0047] Figure 4 is a schematic diagram of the specific structure of the tagged data management component in the first embodiment of the tagged data management method of the present invention;

[0048] Figure 5 is a schematic flowchart of the configuration of the tagged data storage table in the first embodiment of the tagged data management method of the present invention;

[0049] Figure 6 is a schematic diagram of the process of the first embodiment of the tagged data management method of the present invention;

[0050] Figure 7 is a schematic diagram of the scenario of data format conversion in step S20 in the first embodiment of the tagged data management method of the present invention;

[0051] Figure 8Schematic diagram of the scenario of data query and output in step S40 in the first embodiment of the labeled data management method of the present invention;

[0052] Figure 9 Schematic diagram of the functional modules of an embodiment of the labeled data management device of the present invention.

[0053] The implementation, functional features, and advantages of the object of the present invention will be further described with reference to the embodiments and the accompanying drawings. Detailed implementation manners

[0054] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0055] As Figure 1 shown, Figure 1 is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment solution of the present invention.

[0056] The labeled data management device in the embodiment of the present invention may be a PC or a server.

[0057] As Figure 1 shown, the labeled data management device may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and optionally, the user interface 1003 may further include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may optionally be a storage device independent of the aforementioned processor 1001.

[0058] Those skilled in the art can understand that Figure 1 the device structure shown in

[0059] does not constitute a limitation on the device, and may include more or fewer components than shown in the figure, or combine some components, or arrange different components. Figure 1 As

[0060] In Figure 1In the device shown, the network interface 1004 is mainly used to connect to the background server and communicate with the background server for data; the user interface 1003 is mainly used to connect to the client (user side) and communicate with the client for data; and the processor 1001 can be used to call the tagged data management program stored in the memory 1005 and perform the operations in the following tagged data management method.

[0061] Based on the above hardware structure, an embodiment of the tagged data management method of the present invention is proposed.

[0062] Based on

[0063] When receiving the upload request information from the third-party service platform, call the tagged data management component;

[0064] According to the registry configuration information in the tagged data management component, perform format conversion on each service data in the request information to obtain formatted service data;

[0065] Construct a data tag for the formatted service data, and save the formatted service data to the tagged data storage table according to the data tag;

[0066] When receiving a data query request, query the tagged data storage table according to the primary key value in the data query request, and output a data query table.

[0067] The tagged data management method of this embodiment is applied to a tagged data management device. The tagged data management device is the hardware carrier of the tagged data management platform. The tagged data management platform in this embodiment can be used as an intermediate platform to connect to the financial service platform and the third-party service platform. In addition, the tagged data management platform in this embodiment can also be set on the financial service platform.

[0068] For the convenience of understanding, in this embodiment, the tagged data management platform is used as an intermediate platform to connect to the financial service platform and the third-party service platform as an example for description.

[0069] Before the steps of the first embodiment of the tagged data management method of the present invention, a tagged data management component is pre-constructed, and the service data is managed through the tagged data management component. Refer to Figure 2 , Figure 2 is a schematic flow chart for constructing the tagged data management component in the first embodiment of the tagged data management method of the present invention. The steps for constructing the tagged data management component in this embodiment include:

[0070] Step S01, when receiving a component configuration request, obtain the third-party platform identifier associated with the component configuration request, and obtain the component configuration page corresponding to the third-party platform identifier;

[0071] Step S02, obtain the registry configuration information input based on the component configuration page;

[0072] Step S03, import the registry configuration information into a preset common management component to generate a tagged data management component.

[0073] The tagged data management device receives a component configuration request. The triggering method of the component configuration request is not specifically limited. When the tagged data management device receives the component configuration request, the tagged data management device obtains the third-party platform identifier associated with the component configuration request (the third-party platform identifier refers to the identifier information that uniquely identifies the third-party business platform. For example, the network address information of the third-party business platform). The tagged data management device pre-sets multiple component configuration pages. For example, the first component configuration page of the vehicle product business platform and the second component configuration page of the house product business platform; the tagged data management device obtains the component configuration page corresponding to the third-party platform identifier, and the tagged data management device outputs the corresponding component configuration page according to the third-party platform identifier to facilitate users to perform component information configuration operations.

[0074] Refer to Figure 3 , Figure 3 , which is a schematic diagram of a specific component configuration page of the tagged data management component in the first embodiment of the tagged data management method of the present invention; the tagged data management device obtains the registry configuration information input based on the component configuration page. Among them, the registry configuration information refers to the information related to business data processing. The registry configuration information includes: data type, field name, field Chinese, field type, field check rule, field type, field format, field relationship, and / or primary key value.

[0075] The preset common management component in the tagged data management device. The preset common management component refers to the code template pre-set by developers. The preset common management component contains configuration file information, common code information, etc. The tagged data management device imports the registry configuration information into the preset common management component to generate a tagged data management component.

[0076] In this example, the registry configuration information is visually configured. After the registry information configuration is completed, the tagged data management device uses the template technology to automatically generate a set of tagged data transmission layers (the data transmission layer mainly contains fields with business meanings for easy use) and an adapted data processing layer (the adapted data processing layer is used for data-related operations such as data saving, updating, and querying) with one key, and then the generated files are imported into the tagged data management component for the use of the third-party business platform; the generated code structure is as Figure 4 shown Figure 4 , which is a schematic diagram of the specific structure of the tagged data management component in the first embodiment of the tagged data management method of the present invention,Figure 4 In the figure, the third-party service platform can be a cash service platform, a vehicle service platform, and a housing service platform. The tagged data management device receives the set registry configuration information and performs adaptation and transformation to generate tagged data management components.

[0077] In this embodiment, the tagged data management device realizes the maintenance of the registry configuration information through a visual component configuration page, mainly adding, modifying, and deleting tagged data types, as well as field definitions. In this embodiment, the registry configuration information of the visual interface configuration component can ensure efficient configuration, facilitate maintenance, and reduce errors.

[0078] Further, referring to Figure 5 , Figure 5 is a schematic flowchart of the configuration of the tagged data storage table in the first embodiment of the tagged data management method of the present invention. In this embodiment, the steps of configuring the tagged data storage table include:

[0079] Step S04, when it is detected that the tagged data management component is generated, determine whether the registry configuration information in the tagged data management component conforms to the component configuration rules;

[0080] Step S05, when the registry configuration information does not conform to the component configuration rules, output a configuration error prompt;

[0081] Step S06, when the registry configuration information conforms to the component configuration rules, output a storage table configuration prompt; receive the storage table configuration information input based on the storage table configuration prompt, and generate a tagged data storage table according to the storage table configuration information.

[0082] Component configuration rules are preset in the tagged data management device, and the content of the component configuration rules is not specifically limited. In this embodiment, when the tagged data management device detects that the tagged data management component is generated, the tagged data management device determines whether the registry configuration information in the tagged data management component conforms to the component configuration rules; the tagged data management device performs configuration management according to the component configuration rules. In order to prevent configuration problems, at the same time, regular checks are performed through the component configuration rules. For all configuration records, each record mainly includes field tagging field definitions, whether the supported field types, lengths, data formats are all supported, whether the nested relationship is reasonable, and whether the hierarchical relationship exists, etc. are checked; through the range of preset parameters.

[0083] When the registry configuration information does not conform to the component configuration rules, the tagged data management device outputs a configuration error prompt to prompt the user to change the configuration information, and after the check is completed, a check report email will be sent to relevant personnel. When the registry configuration information conforms to the component configuration rules, the tagged data management device outputs a storage table configuration prompt to prompt the user to configure the relevant information of the tagged data storage table. That is, the tagged data management device receives the storage table configuration information input based on the storage table configuration prompt. The storage table configuration information includes: tag primary key, tag type, tag field, and / or tag field length. The tagged data management device generates a tagged data storage table according to the storage table configuration information to save the stored data using the tagged data storage table.

[0084] In this embodiment, the tagged data management device verifies the registry configuration information, and through visual configuration maintenance, automatically checks to prevent configuration maintenance errors, ensuring the security and effectiveness of the configuration data. At the same time, it can generate a corresponding tagged data storage table, making the steps of the tagging process correspond to the tagged data storage table.

[0085] Refer to Figure 6 , Figure 6 is a schematic flowchart of the first embodiment of the tagged data management method of the present invention. The method includes:

[0086] Step S10, when receiving the upload request information from the third-party business platform, call the tagged data management component.

[0087] In this embodiment, when the tagged data management device receives the upload request information from the third-party business platform, the tagged data management device calls the tagged data management component. That is, the third-party business platform calls the external interface provided by the tagged data management device, and the third-party business platform uploads the request information through the external interface. When the tagged data management device receives the upload request information from the third-party business platform, the tagged data management device calls the tagged data management component, and processes the request information through the tagged data management component to obtain the business data in the request information, so as to store the business data according to the data tags. Specifically:

[0088] Step S20, according to the registry configuration information in the tagged data management component, perform format conversion on each piece of business data in the request information to obtain formatted business data.

[0089] The tagged data management device performs format conversion on each piece of service data in the request information according to the registry configuration information in the tagged data management component to obtain formatted service data. That is, the tagged data management device needs to perform validity checks on the fields. It traverses all fields in the request information through the request, matches the field definition configuration of the data field key registry, finds the check class object in the FiledDef object of the field definition in the registry, and then calls the check method of all FiledCheckor objects at once. Then, it checks the field type, length, whether it is required, format legality, etc. in sequence according to the data type. If the check fails, the field is not saved or an error prompt is processed. The check mainly ensures that the service data conforms to the predefined field data type and storage requirements. When the service data passes the check, the tagged data management device performs format conversion on each piece of service data in the request information to obtain formatted service data.

[0090] Refer to Figure 7 , Figure 7 This is a schematic diagram of the scenario of data format conversion in step S20 of the first embodiment of the tagged data management method of the present invention. That is, the tagged data management device checks the request information (request data in the figure) through the data detector in the tagged data management component, and performs formatting conversion on the service data when the service data in the request information passes the check.

[0091] Step S30: Construct a data tag for the formatted service data, and save the formatted service data to the tagged data storage table according to the data tag.

[0092] The tagged data management device constructs a data tag for the formatted service data, and the tagged data management device saves the formatted service data to the tagged data storage table according to the data tag for convenient later query. Specifically:

[0093] Step a1: Find the primary key value associated with the request information in the way of the registry factory, obtain the data tag corresponding to the primary key value, and the fields of the data tag.

[0094] Step a2: Compare the formatted service data with the fields corresponding to each data tag, obtain the target field that matches the service data, and use the data tag corresponding to the target field as the data tag of the service data.

[0095] Step a3: Associate the service data according to the data tag of the service data and the nested relationship of the data tag, and save it to the tagged data storage table.

[0096] The tagged data management device finds the primary key value associated with the request information through the registry factory method. That is, the tagged data management device obtains the query keyword in the query request, determines the key value corresponding to the keyword according to the type of the keyword, and combines all the key values associated with the key value to obtain the primary key value. For example, the query keyword is insurance policy number: 20200730xxxx165. The tagged data management device determines that the first key value is the insurance policy number according to the query keyword, and obtains other key values related to the insurance policy number. For example, the signing date of 2020-07-30 is the second key value, and the insurance type 1 corresponding to vehicle insurance is the third key value. The tagged data management device combines each key value to obtain the primary key value; the tagged data management device obtains the data tag corresponding to the primary key value and the fields of the data tag; the tagged data management device compares the formatted business data with the fields corresponding to each data tag, obtains the target field that matches the business data, and uses the data tag corresponding to the target field as the data tag of the business data; associates the business data according to the data tag of the business data and the nested relationship of the data tag, and saves it to the tagged data storage table.

[0097] Step S40, when receiving a data query request, query the tagged data storage table according to the primary key value in the data query request, and output a data query table.

[0098] When the tagged data management device receives a data query request, the tagged data management device queries the tagged data storage table according to the primary key value in the data query request. That is, the tagged data management device obtains the data tag corresponding to the query primary key value, obtains the business data corresponding to the data tag in the data storage table, constructs a display table according to the nested relationship of the business data, and adds the business data to the display table to obtain a data query table and output it.

[0099] In the embodiment, when receiving the upload request information from the third-party service platform, the tagged data management component is called; according to the registry configuration information in the tagged data management component, the format of each service data in the request information is converted to obtain formatted service data. The data format is converted through a pre-customized tagged data management component, and corresponding data tags are added for storage. During subsequent data queries, the tagged data management device extracts the service data corresponding to the data identifier of the query request from the data storage table, and forms these service data into a data query table for the user to view and operate conveniently. The tagged data management method in the embodiment of the present invention facilitates the later maintenance of the data storage table and the user query operation; at the same time, the data storage table is flexibly associated with the service platform. When the services of the financial service platform or the third-party service platform change, by adjusting the configuration information of the tagged data management component, the data storage table can be updated without reconstructing the data storage table. Such a data management method supports the rapid update of the versions of the financial service platform and the third-party service platform, making the service data management method more reasonable.

[0100] Further, based on the first embodiment of the tagged data management method of the present invention, the second embodiment of the tagged data management method of the present invention is proposed.

[0101] This embodiment is a refinement of step S20 in the first embodiment. A specific implementation method for service data conversion is given in this embodiment, including:

[0102] Import the registry configuration information in the tagged data management component into the registry factory class in the memory, load and call the object through the registry factory method to traverse the request information, and determine the data type of each service data according to the fields of each service data in the request information;

[0103] Check whether each service data conforms to the field check rules in the registry configuration information according to the data type, where the field check rules refer to the rules for detecting the field type, length, mandatory input, data format, and nesting relationship of the service data;

[0104] When the service data conforms to the field check rules, convert the format of the service data according to the data type of the service data to obtain formatted service data.

[0105] The tagged data management device imports the registry configuration information in the tagged data management component into the registry factory class in the memory, loads and calls the object traversal request information through the registry factory method, and determines the data types of each business data according to the fields of each business data in the request information; that is, the tagged data management device imports the registry configuration information in the tagged data management component into the memory, performs information analysis in the memory, improves the information processing efficiency. Further, loading and calling the object traversal request information through the registry factory method can make data processing more convenient and accurate.

[0106] The tagged data management device checks whether each business data conforms to the field check rules in the registry configuration information according to the data type, where the field check rules refer to the rules for detecting the field type, length, whether it is required, data format, and nesting relationship of the business data; for example, when the tagged data management device determines that the business data is the user contact information, the tagged data management device determines whether the length of the business data is 11 digits, whether the business data is all numbers, whether the first digit of the business data is 1, etc. When the business data conforms to the field check rules, the tagged data management device performs format conversion on the business data according to the data type of the business data to obtain the formatted business data. For example, the tagged data management device adjusts the user contact information in the business data to the text format. Specifically, refer to Figure 7 , Figure 7 is a schematic diagram of the scenario of data format conversion in step S20 in the first embodiment of the tagged data management method of the present invention.

[0107] It can be understood that the tagged data management device loads the registry configuration information (the registry configuration information can be configured in different ways, for example, db configuration or xml configuration) in the tagged data management component into the memory cache. The controller of the tagged data management device takes N * 60 * 1000ms (N is time) timing, and the independent thread update task updates and downloads the full amount of registry configuration information to the memory once. The registry configuration information uses the weak java reference method, and the tagged data management device will automatically recycle the registry configuration information that has not been used for a long time and release the memory.

[0108] In this embodiment, all registry configuration information is managed through the registry factory. By uniformly storing the registry configuration information in the registry factory class in the memory, the object information in the registry can be loaded and called through the factory method later, making data processing more convenient to manage.

[0109] Further, based on the above embodiments of the tagged data management method of the present invention, the third embodiment of the tagged data management method of the present invention is proposed.

[0110] This embodiment is a refinement of step S40 in the first embodiment. In this embodiment, a specific implementation manner of a data query table is given, including:

[0111] When receiving a data query request, obtain the primary key value in the data query request;

[0112] Query the tagged data storage table to obtain each data tag associated with the primary key value, the nested relationship corresponding to each data tag, and the business data corresponding to the data tag;

[0113] Construct a data display template according to the data tag and the nested relationship, output the business data to the data display template, and generate a data query table.

[0114] When the tagged data management device receives a data query request, the tagged data management device obtains the primary key value in the data query request (the primary key value can be set according to the business platform. For example, when the business platform is a vehicle insurance business platform, the primary key value is the policy number); the tagged data management device queries the tagged data storage table to obtain each data tag associated with the primary key value, the nested relationship corresponding to each data tag, and the business data corresponding to the data tag; the tagged data management device constructs a data display template according to the data tag and the nested relationship, and the tagged data management device outputs the business data to the data display template to generate a data query table.

[0115] When the tagged data management device receives a data query request, the tagged data management device obtains the primary key value in the data query request. The tagged data management device finds the data tag corresponding to the primary key value through the registry factory method (the number of data tags can be one or more, and there is no specific limit). The tagged data management device determines the business data nested relationship according to the data tag, splits the combined keys into single keys, and requests to find the value corresponding to the key in the data, and then combines the values corresponding to the combined keys. For field mapping conversion processing, if the data type is Map, all fields in the Map need to be traversed. After checking the legality and format processing of all fields, map them to the general TagDto object. If the corresponding business TagDto data object (such as CashTagDto) is also converted into a general standard through reflection to generate a data query table.

[0116] Refer to Figure 8 , Figure 8This is a scenario schematic diagram of the data query and output in step S40 of the first embodiment of the labeled data management method of the present invention. In the labeled data table of the labeled data management device, business data a, b, c, d, e, f, g, and h are stored. A data query table is generated based on the labels and relationships of a, b, c, d, e, f, g, and h, facilitating user viewing and operation. In this embodiment, the labeled data management device uniformly stores business data in the labeled data storage table, and then generates a data query table according to the data relationships and data labels, facilitating user viewing and operation.

[0117] Further, based on the above embodiments of the labeled data management method of the present invention, a fourth embodiment of the labeled data management method of the present invention is proposed.

[0118] The steps in this embodiment are refinement steps of step S10 in the first embodiment. The difference between this embodiment and the above embodiments is as follows:

[0119] When receiving the upload request information from the third-party business platform, obtain the business data in the request information and the data type of the business data.

[0120] Determine whether the data type of the business data is a new data type.

[0121] When the data type of the business data is a new data type, trigger a component configuration request.

[0122] When the data type of the business data is not a new data type, call the labeled data management component.

[0123] When the labeled data management device receives the upload request information from the third-party business platform, the labeled data management device obtains the business data in the request information and the data type of the business data; the labeled data management device determines whether the data type of the business data is a new data type; when the data type of the business data is a new data type, the labeled data management device determines that the business platform has been updated, and the labeled data management device triggers a component configuration request; perform the configuration operation of the labeled data management component, so that the version update in the business platform does not require developers to modify the code. Further, reconstruct the data storage table, making the system update of the business platform more convenient.

[0124] When the data type of the business data is not a new data type, the labeled data management device calls the labeled data management component and executes the steps of the first embodiment.

[0125] Refer to Figure 9 Furthermore, the present invention also provides a labeled data management device, and the labeled data management device includes:

[0126] The component call module 10 is used to call the tagged data management component when receiving the upload request information from the third-party business platform;

[0127] The format conversion module 20 is used to perform format conversion on each business data in the request information according to the registry configuration information in the tagged data management component to obtain formatted business data;

[0128] The data storage module 30 is used to construct data tags for the formatted business data and save the formatted business data to the tagged data storage table according to the data tags;

[0129] The data query module 40 is used to query the tagged data storage table according to the primary key value in the data query request when receiving the data query request, and output the data query table.

[0130] In one embodiment, the tagged data management device includes:

[0131] The page output module is used to obtain the third-party platform identifier associated with the component configuration request and obtain the component configuration page corresponding to the third-party platform identifier when receiving the component configuration request;

[0132] The information acquisition module is used to acquire the registry configuration information input based on the component configuration page;

[0133] The component generation module is used to import the registry configuration information into a preset common management component to generate a tagged data management component.

[0134] In one embodiment, the tagged data management device includes:

[0135] The rule judgment module is used to judge whether the registry configuration information in the tagged data management component conforms to the component configuration rules when detecting that the tagged data management component is generated;

[0136] The error prompt module is used to output a configuration error prompt when the registry configuration information does not conform to the component configuration rules;

[0137] The storage configuration module is used to output a storage table configuration prompt when the registry configuration information conforms to the component configuration rules;

[0138] The receiving and generation module is used to receive the storage table configuration information input based on the storage table configuration prompt and generate a tagged data storage table according to the storage table configuration information.

[0139] In one embodiment, the format conversion module includes:

[0140] A type determination unit for importing the registry configuration information in the tagged data management component into the registry factory class in the memory, loading and calling objects through the registry factory method to traverse the request information, and determining the data types of the respective business data based on the fields of the respective business data in the request information;

[0141] A rule judgment unit for checking whether each of the business data conforms to the field check rules in the registry configuration information according to the data type, where the field check rules refer to the rules for detecting the field type, length, mandatory input, data format, and nested relationship of the business data;

[0142] A format conversion unit for performing format conversion on the business data according to the data type of the business data when the business data conforms to the field check rules to obtain formatted business data.

[0143] In one embodiment, the data storage module includes:

[0144] A search and acquisition unit for searching for the primary key value associated with the request information through the registry factory method, acquiring the data tag corresponding to the primary key value, and the fields of the data tag;

[0145] A data comparison unit for comparing the formatted business data with the fields corresponding to each of the data tags to obtain the target field that matches the business data, and using the data tag corresponding to the target field as the data tag of the business data;

[0146] A data saving unit for associating the business data according to the data tag of the business data and the nested relationship of the data tag, and saving it to the tagged data storage table.

[0147] In one embodiment, the data query module includes:

[0148] A request receiving unit for acquiring the primary key value in the data query request when receiving a data query request;

[0149] A query and acquisition unit for querying the tagged data storage table to acquire each data tag associated with the primary key value, the nested relationship corresponding to each of the data tags, and the business data corresponding to the data tag;

[0150] A table generation unit for constructing a data display template according to the data tag and the nested relationship, outputting the business data to the data display template, and generating a data query table.

[0151] In one embodiment, the component call module includes:

[0152] An acquisition unit, configured to acquire service data in the request information and the data type of the service data when receiving an upload request information from a third-party service platform;

[0153] Determine whether the data type of the service data is a new data type;

[0154] When the data type of the service data is a new data type, trigger a component configuration request;

[0155] When the data type of the service data is not a new data type, call a tagged data management component.

[0156] In this embodiment, when the tagged data management device receives an upload request information from a third-party service platform, it calls the tagged data management component; according to the registry configuration information in the tagged data management component, it performs format conversion on each service data in the request information to obtain formatted service data, performs data format conversion through a pre-customized tagged data management component, adds corresponding data tags for storage. During later data query, the tagged data management device extracts the service data corresponding to the data identifier of the query request from the data storage table and forms these service data into a data query table for the user to view and operate. The tagged data management method in the embodiments of the present invention facilitates the later maintenance of the data storage table and the user query operation; at the same time, the data storage table is flexibly associated with the service platform. When the services of the financial service platform or the third-party service platform change, by adjusting the configuration information of the tagged data management component, the data storage table can be updated without reconstructing the data storage table. Such a data management method supports the rapid update of the financial service platform and the third-party service platform versions, making the service data management method more reasonable.

[0157] The methods executed by the above program modules can refer to the respective embodiments of the tagged data management method of the present invention, which will not be elaborated here.

[0158] The present invention also provides a computer-readable storage medium.

[0159] The computer-readable storage medium of the present invention stores a tagged data management program, and when the tagged data management program is executed by a processor, it implements the steps of the tagged data management method as described above.

[0160] Among them, the method implemented when the tagged data management program running on the processor is executed can refer to the respective embodiments of the tagged data management method of the present invention, which will not be elaborated here.

[0161] It should be noted that, in this document, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, such that a process, method, article or system comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or system. Without further limitation, an element defined by the statement "comprising a..." does not exclude the presence of additional identical elements in the process, method, article or system comprising such element.

[0162] The serial numbers of the above embodiments of the present invention are only for description and do not represent the superiority or inferiority of the embodiments.

[0163] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on such an understanding, the technical solution of the present invention, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium as described above (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of the present invention.

[0164] The above are only the preferred embodiments of the present invention and do not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the description and drawings of the present invention, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present invention.

Claims

1. A method for managing tagged data, characterized in that, The described tagged data management method includes the following steps: When the tagged data management device receives a component configuration request, it obtains the third-party platform identifier associated with the component configuration request, and obtains the component configuration page corresponding to the third-party platform identifier. The third-party platform identifier refers to the identification information that uniquely identifies a third-party business platform. The tagged data management device is pre-set with component configuration pages for different platforms; Obtain the registry configuration information input based on the component configuration page; Import the registry configuration information into a preset common management component to generate a tagged data management component; When receiving a third-party business platform upload request message, call the tagged data management component; According to the registry configuration information in the tagged data management component, perform format conversion on the data types of each business data in the request message to match the corresponding format to obtain formatted business data. The format conversion includes at least one of the following: date formatting, time formatting, amount formatting, string formatting; Find the primary key value associated with the request message in the way of a registry factory, and obtain the Tag field corresponding to the primary key value and the fields of the Tag field; Compare the formatted business data with the fields corresponding to each Tag field to obtain the target field that matches the business data, and use the Tag field corresponding to the target field as the Tag field of the business data; Associate the business data according to the Tag field of the business data and the nesting relationship of the Tag field, and save it to a tagged data storage table. The tagged data storage table includes the Tag field; When receiving a data query request, obtain the primary key value in the data query request; Query the tagged data storage table to obtain each Tag field associated with the primary key value, the nesting relationship corresponding to each Tag field, and the business data corresponding to the Tag field; Construct a data display template according to the Tag field and the nesting relationship, output the business data to the data display template, and generate a data query table; When the business of the third-party business platform changes, adjust the registry configuration information of the tagged data management component to update the tagged data storage table without reconstructing the tagged data storage table.

2. The tagged data management method according to claim 1, wherein After the step of importing the registry configuration information into a preset common management component to generate a tagged data management component, the method includes: When it is detected that the tagged data management component is generated, determine whether the registry configuration information in the tagged data management component conforms to the component configuration rules; When the registry configuration information does not conform to the component configuration rules, output a configuration error prompt; When the registry configuration information conforms to the component configuration rules, output a storage table configuration prompt; Receive the storage table configuration information input based on the storage table configuration prompt, and generate a tagged data storage table according to the storage table configuration information.

3. The tagged data management method according to claim 1, wherein The step of performing format conversion on the data types of the service data in the request information to match the corresponding formats according to the registry configuration information in the labeled data management component to obtain formatted service data includes: Import the registry configuration information in the labeled data management component into the registry factory class in the memory, load and call the object through the registry factory method to traverse the request information, and determine the data types of the service data according to the fields of the service data in the request information; Check whether each piece of service data conforms to the field check rules in the registry configuration information according to the data type, where the field check rules refer to the rules for detecting the field type, length, mandatory input, data format, and nested relationship of the service data; When the service data conforms to the field check rules, perform format conversion on the service data according to the data type of the service data to obtain formatted service data.

4. The labeled data management method according to any one of claims 1-3, characterized in that, The step of calling the labeled data management component when receiving the upload request information from the third-party service platform includes: When receiving the upload request information from the third-party service platform, obtain the service data in the request information and the data type of the service data; Determine whether the data type of the service data is a new data type; When the data type of the service data is a new data type, trigger a component configuration request; When the data type of the service data is not a new data type, call the labeled data management component.

5. A tagged data management device, characterized in that, The labeled data management device includes: A page output module, which is used for the labeled data management device to obtain the third-party platform identifier associated with the component configuration request and the component configuration page corresponding to the third-party platform identifier when receiving the component configuration request. The third-party platform identifier refers to the identifier information that uniquely identifies the third-party service platform, and the labeled data management device is pre-set with component configuration pages for different platforms; An information acquisition module, which is used to acquire the registry configuration information input based on the component configuration page; A component generation module, which is used to import the registry configuration information into a preset common management component to generate a labeled data management component; A component call module, which is used to call the labeled data management component when receiving the upload request information from the third-party service platform; A format conversion module, which is used to perform format conversion on the data types of the service data in the request information to match the corresponding formats according to the registry configuration information in the labeled data management component to obtain formatted service data. The format conversion includes at least one of the following: date formatting, time formatting, amount formatting, and string formatting; A data storage module, which is used to construct the Tag field in the registry configuration information for the formatted service data according to the registry configuration information, and save the formatted service data to the labeled data storage table according to the Tag field. The labeled data storage table includes the Tag field; A data query module, which is used to query the tagged data storage table according to the primary key value in the data query request when receiving the data query request, and output a data query table; Among them, the data query module includes: A request receiving unit, which is used to obtain the primary key value in the data query request when receiving the data query request; A query and acquisition unit, which is used to query the tagged data storage table, obtain each Tag field associated with the primary key value, the nested relationship corresponding to each Tag field, and the business data corresponding to the Tag field; A table generation unit, which is used to construct a data display template according to the Tag field and the nested relationship, output the business data to the data display template, and generate a data query table; The data storage module includes: A search and acquisition unit, which is used to search for the primary key value associated with the request information in the way of the registry factory, and obtain the Tag field corresponding to the primary key value and the field of the Tag field; A data comparison unit, which is used to compare the formatted business data with the fields corresponding to each Tag field, obtain the target field that matches the business data, and use the Tag field corresponding to the target field as the Tag field of the business data; A data saving unit, which is used to associate the business data according to the Tag field of the business data and the nested relationship of the Tag field, and save it to the tagged data storage table; The device is also used for: when the business of the third-party business platform changes, adjusting the registry configuration information of the tagged data management component to update the tagged data storage table without reconstructing the tagged data storage table.

6. A tagged data management device, characterized in that, The tagged data management device includes: a memory, a processor, and a tagged data management program stored on the memory and executable on the processor. When the tagged data management program is executed by the processor, the steps of the tagged data management method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium, characterized in that, A tagged data management program is stored on the computer-readable storage medium. When the tagged data management program is executed by the processor, the steps of the tagged data management method according to any one of claims 1 to 4 are implemented.

Images