Label configuration system and device

Abstract

The invention relates to the technical field of data processing, in particular to a label configuration system and equipment, and the system comprises a data processing layer which is used for obtaining a label value of each first label field of each target object through corresponding search logic based on at least one determined target object and at least one newly added first label field, based on each target object, adding the corresponding first label field and the label value to the initial portrait wide table; the metadata configuration layer is used for receiving a second label field and a label processing strategy configured by a user, associating the second label field and the label processing strategy and then storing the second label field and the label processing strategy into the label configuration table; and the label dynamic generation layer is used for loading the portrait data from the portrait wide table based on any second label field in the label configuration table, processing the portrait data by using a corresponding label processing strategy and generating target portrait information of a preset data structure. Therefore, the label development efficiency is improved, and the maintenance cost and the risk level are reduced.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a tag configuration system and device. Background Technology

[0002] With the increasing demand for refined operations, business units need to continuously add, modify, and delete user profile tags. For example, in the financial industry, user profile tags include "enterprise risk level," "customer value segmentation," and "date of most recent loan." The traditional process for adding, modifying, and deleting user profile tags includes: 1) The big data side writes offline or real-time processing logic for newly added tags; 2) The backend needs to add a new interface or modify the interface logic for the newly added field; 3) The front-end develops and displays the UI for the new fields.

[0003] However, this implementation process has the following drawbacks: Each tag change requires parallel development across data, front-end, and back-end, resulting in long development cycles and high costs; frequent changes to production environment interfaces pose stability and compatibility risks; and business personnel cannot independently complete tag deployment, requiring deep reliance on R&D. Summary of the Invention

[0004] In view of this, the present application provides a tag configuration system and device, which can effectively solve the problems of low development efficiency, high maintenance cost and high risk in the implementation of user profile tag addition, modification and deletion operations in the prior art.

[0005] In a first aspect, embodiments of this application provide a tag configuration system, which includes: a data processing layer, a metadata configuration layer, and a tag dynamic generation layer; The data processing layer is used to obtain the tag value of each first tag field of each target object based on at least one determined target object and at least one newly added first tag field through the corresponding search logic, and add the corresponding first tag field and tag value to the initial portrait wide table based on each target object. The metadata configuration layer is used to receive the second tag field and tag processing strategy configured by the user, and store the second tag field and the tag processing strategy in the tag configuration table after associating them. The dynamic tag generation layer is used to load portrait data from the portrait wide table based on any second tag field in the tag configuration table, process the portrait data using the corresponding tag processing strategy, and generate target portrait information with a preset data structure.

[0006] In some embodiments, the data processing layer is specifically used to: generate corresponding search logic based on the first tag field configured by the user, the determined target object, and the corresponding target data table; obtain the tag values ​​of the first tag field of all target objects from the big data platform through the corresponding search logic; and add the first tag field and the corresponding tag values ​​to the initial profile wide table based on the target object.

[0007] In some embodiments, the search logic includes a field query strategy and a field offline calculation strategy; When the data processing layer generates the corresponding search logic based on the user-configured first tag field, the determined target object, and the corresponding target data table, it is specifically used for: When the search logic includes a query strategy, a structured query statement is generated based on the first tag field, target object, target data table, and structured query statement keywords input by the user from the data processing interface, and according to the statement syntax. When the search logic includes an offline field calculation strategy, a structured query statement is generated based on the target object, target data table, structured query statement keywords, and calculation logic selected from a variety of preset calculation logics, combined according to the statement syntax, as input by the user from the logic configuration interface.

[0008] In some embodiments, the label dynamic generation layer is specifically used for: Based on any second tag field in the tag configuration table, a corresponding first tag field is matched from the image width table to obtain the target field; each row of image data containing the tag value of the target field is obtained from the image width table; each row of image data includes the target field, multiple other tag fields and corresponding tag values; The corresponding tag processing strategy is used to process the tag value of the target field, and the target profile information with a preset data structure is generated based on multiple other tag fields in the row of profile data.

[0009] In some embodiments, the metadata configuration layer is further configured to: Receive multiple level category fields and their display order configured by the user for the second tag field, and store the second tag field, the multiple level category fields, and their display order in the tag configuration table; The dynamic tag generation layer is specifically used for: After processing the tag values ​​of the target field using the corresponding tag processing strategy, multiple level category fields are used as data objects of the corresponding level. Each tag field in the row of profile data is grouped according to the level category, and the tag fields in each group are stored in an array. Based on the level size, each data object and the corresponding array are combined using key-value pairs to generate multi-level JSON data.

[0010] In some embodiments, the plurality of level category fields include a first-level tab and a plurality of second-level information modules; the tab includes a plurality of types, and the information modules include a plurality of types; a tab includes at least one information module; the JSON data has a three-level structure.

[0011] In some embodiments, the tag configuration system further includes a dynamic rendering layer; The dynamic rendering layer is used to obtain the target image information using a rendering interface provided by a third party, generate UI components based on the target image information, and display them according to the display order.

[0012] In some embodiments, the metadata configuration layer is specifically used to cache the tag configuration table to an intermediate message queue in response to the completion of saving the tag configuration table; The tag dynamic generation layer is specifically used to: obtain the initial profile wide table and the tag configuration table from the intermediate message queue through a unified generation interface, and generate the target profile information.

[0013] In some embodiments, the tag processing strategy includes desensitization methods, formatting methods, and numerical precision standardization methods for various tags; The metadata configuration layer is also specifically used to: receive the configured data type, initial value of the tag field, desensitization method, numerical precision and tag value display format, and generate the tag processing strategy based on at least two of them; The dynamic tag generation layer is specifically used to achieve at least two of the following three items: The first item: Desensitize the tag value of the target field according to the desensitization category included in the desensitization method and the data type; The second step: Adjust the precision of the label value of the target field according to the numerical precision and the data type; The third item: Adjust the representation format of the tag value of the target field according to the tag value display format and the data type.

[0014] Secondly, embodiments of this application provide a terminal device, the terminal device including a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the functions of various modules in a tag configuration system provided in the first aspect of this application.

[0015] The embodiments of this application have the following beneficial effects: The tag configuration system in this application includes: a data processing layer, a metadata configuration layer, and a tag dynamic generation layer. The data processing layer is used to obtain the tag value of each first tag field of each target object based on at least one determined target object and at least one newly added first tag field through corresponding search logic, and to add the corresponding first tag field and tag value to the initial profile wide table for each target object. The metadata configuration layer is used to receive the second tag field and tag processing strategy configured by the user, associate the second tag field and tag processing strategy, and store them in the tag configuration table. The tag dynamic generation layer is used to load profile data from the profile wide table based on any second tag field in the tag configuration table, process the profile data using the corresponding tag processing strategy, and generate target profile information with a preset data structure. Therefore, this application can effectively solve the problems of low development efficiency, high maintenance costs, and high risks in the implementation methods of adding and modifying user profile tags in existing technologies. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 A structural block diagram of a tag configuration system according to an embodiment of this application is shown; Figure 2 A schematic diagram of the metadata configuration interface of the tag configuration system according to an embodiment of this application is shown; Figure 3 A schematic diagram of a label editing window of a label configuration system according to an embodiment of this application is shown; Figure 4 This illustration shows a schematic diagram of a tab editing window of a tab configuration system according to an embodiment of this application; Figure 5 This paper shows a schematic diagram of a module editing window of a label configuration system according to an embodiment of the present application; Figure 6 This illustration shows a schematic diagram of the structure of JSON data in a tag configuration system according to an embodiment of this application; Figure 7 Another structural block diagram of the tag configuration system according to an embodiment of this application is shown; Figure 8 This illustration shows a schematic diagram of the profile interface of an object in the tag configuration system of this application embodiment.

[0018] Explanation of key component symbols: 100 - Tag configuration system; 110 - Data processing layer; 120 - Metadata configuration layer; 130 - Tag dynamic generation layer; 140 - Dynamic rendering layer; 200 - Big data platform; 300 - Business system. Detailed Implementation

[0019] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0020] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0021] In the following text, the terms "comprising," "having," and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as primarily excluding the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more combinations thereof. Furthermore, the terms "first," "second," "third," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0022] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.

[0023] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0024] The following describes the label configuration system using specific examples.

[0025] Figure 1 A structural block diagram of a tag configuration system according to an embodiment of this application is shown. Exemplarily, the tag configuration system 100 includes: a data processing layer 110, a metadata configuration layer 120, and a tag dynamic generation layer 130.

[0026] The data processing layer 110 is used to obtain the tag value of each first tag field of each target object through corresponding search logic based on at least one determined target object and at least one newly added first tag field, and add the corresponding first tag field and tag value to the initial portrait wide table based on each target object.

[0027] In this embodiment, the tag value of the first tag field is obtained from the big data platform 200. The original data is generated by the business system 300, such as data generated by users performing operations such as registration, real-name authentication, credit granting, and borrowing in the business system. This data is synchronized to the big data platform 200 in real time.

[0028] A profile wide table refers to an ultra-wide database table with "User.no" as the primary key, each field (column) representing a user tag, and each row recording all or part of a user's tag values. Each time a new tag is added (such as "recent loan amount"), a new column (such as the `last_loan_amount` field) is added to this table. In this embodiment, the profile wide table uses "horizontally expanded columns" rather than "vertically arranged rows" for storage, with each column representing a tag.

[0029] The profile information includes various tag fields. The first tag field is the tag that needs to be added. For example, the tag fields in the profile information of existing customers include User.no, name, age, birthday (abbreviated as bday), customer value segmentation (abbreviated as CS), registration date (abbreviated as Reg.date), credit limit, and company number (abbreviated as Co.no), as shown in Table 1.

[0030] Table 1 Initial Image Width Table

[0031] Now, add a risk level (RL) tag to all customers (target objects). The risk level field is then defined as riskLevel. Identify each target object that needs a risk level tag. Determine the search logic for each object and its corresponding risk level tag. Retrieve the tag value based on the search logic. Add the corresponding risk level tag field and tag value to the initial profile wide table based on the target object's user ID (unique identifier), as shown in Table 2. Each field in the initial profile wide table can be added in this way.

[0032] Table 2. Basic Profile Wide Table for Newly Added Risk Level Labels

[0033] In one implementation, to facilitate independent tag configuration by sales personnel, this application embodiment also provides a data processing interface. The data processing interface includes configuration items for configuring the first tag field, target object configuration items, target data table configuration items to which the first tag field belongs, and target business system configuration items.

[0034] Understandably, the data processing layer 110 is specifically used to: generate corresponding search logic based on the first tag field configured by the user, the determined target object, and the corresponding target data table; obtain the tag values ​​of the first tag field of all target objects from the big data platform 200 through the corresponding search logic; and add the first tag field and the corresponding tag values ​​to the initial profile wide table based on the target object.

[0035] In the data processing interface, configuration items for the first tag field, target object, target data table to which the first tag field belongs, and target business system are configured. The data processing layer 110 generates search logic based on the first tag field, target object, target data table to which the first tag field belongs, and target business system. The search logic is a structured query statement. The search logic retrieves the tag value of the first tag field from the big data platform 200, and adds the first tag field and its corresponding tag value to the initial profile wide table based on the target object. As shown in Table 1, all tag field information for a target object is stored based on the user ID.

[0036] Furthermore, to broaden the applicability of the tag fields, embodiments of this application include both directly queried field information and field information that needs to be calculated. Exemplarily, the search logic includes a field query strategy and a field offline calculation strategy.

[0037] When the data processing layer 110 generates the corresponding search logic based on the user-configured first tag field, the determined target object, and the corresponding target data table, it is specifically used for: When the search logic includes a query strategy, a structured query statement is generated based on the first tag field, target object, target data table, and structured query statement keywords entered by the user from the data processing interface, according to the statement syntax. For example, the structured query statement keywords "select" and "from" are configured, the first tag field "name" is configured, the target data table "user_info" is configured, and the target object "user_no" (customer unique identifier) ​​is configured. A structured query statement is generated according to the statement syntax, such as "select name from user_info where user_no = 'XXX'".

[0038] When the search logic includes an offline field calculation strategy, a structured query statement is generated based on the target object, target data table, structured query statement keywords, and a combination of preset calculation logics input by the user from the logic configuration interface, according to the statement syntax. For example, some profile tag fields cannot be calculated in real time, such as customer value stratification, which can be determined based on customer activity level, loan amount, credit limit, etc. This application embodiment incorporates calculation logic for various tag fields according to requirements, for example, determining customer value stratification based on customer activity level, loan amount, credit limit, etc.

[0039] The metadata configuration layer 120 is used to receive the second tag field and tag processing strategy configured by the user, and store the second tag field and the tag processing strategy in the tag configuration table.

[0040] The second label field can be any of the first label fields. For example, the second label field could be the risk level in Table 2, with the riskLevel field being the unique identifier for the risk level. The label processing strategy is a description of some preprocessing steps applied to the label field. The second label field and its corresponding label processing strategy are associated and stored in the label configuration table. Understandably, the label configuration table includes the second label field and the associated label processing strategy.

[0041] The system in this application embodiment provides a metadata configuration interface, such as... Figure 2 As shown, the metadata configuration interface includes a "Add Profile" button. Clicking the "Add Profile" button will bring up a tag editing window, where users can configure the tag fields to be added (second tag fields) and the tag processing strategy.

[0042] The tag dynamic generation layer 130 is used to load portrait data from the portrait wide table based on any second tag field in the tag configuration table, process the portrait data using the corresponding tag processing strategy, and generate target portrait information with a preset data structure.

[0043] In one implementation, to facilitate real-time updates of newly added tags, this application embodiment also includes a hot update function. Exemplarily, the metadata configuration layer 120 is specifically used to cache the tag configuration table to an intermediate message queue in response to the completion of saving the tag configuration table. The data processing layer 110 caches the initial profile wide table to the intermediate message queue. The intermediate message queue is used for caching data, including but not limited to using RabbitMQ.

[0044] The tag dynamic generation layer 130 is specifically used to: obtain the initial portrait wide table and the tag configuration table from the intermediate message queue through a unified generation interface, load portrait data from the portrait wide table based on any second tag field in the tag configuration table, process the portrait data using the corresponding tag processing strategy, and generate target portrait information with a preset data structure.

[0045] This application refreshes the modified tag configuration table and the initial image wide table to the intermediate message queue in real time, and the tag dynamic generation layer 130 then pulls data from the intermediate message queue. This application embodiment takes effect without restarting.

[0046] Exemplary, the label dynamic generation layer 130 is specifically used for: S131, based on any second tag field in the tag configuration table, match a corresponding first tag field from the portrait width table to obtain the target field; retrieve each row of portrait data containing the tag value of the target field from the portrait width table; each row of portrait data includes the target field, multiple other tag fields, and corresponding tag values. The multiple other tag fields are specifically set according to requirements. For example, if the second tag field is riskLevel, then a row of portrait data in Table 1 includes multiple tag fields. Each row in Table 1 contains the tag value of the risk level riskLevel, so retrieving the portrait data for each row yields the portrait data for Zhang Yi, Zhang Er, Zhang San, and Zhang Si.

[0047] S132, the tag value of the target field is processed using the corresponding tag processing strategy, and target profile information with a preset data structure is generated based on multiple other tag fields within the row of profile data. For example, the second tag field is riskLevel, and the tag value of riskLevel is processed using the tag processing strategy.

[0048] In one implementation, to facilitate the display of tags, the metadata configuration layer 120 is further configured to: The system receives multiple level category fields and their display order configured by the user for the second tag field. It then associates the second tag field with these level category fields and the display order, storing the associations in the tag configuration table. The multiple level category fields are used to categorize the tag field into different levels. For example, levels can be categorized based on the target object and business category. The display order is used to define the arrangement order of the profile data for the target object to which the target field belongs.

[0049] like Figure 3 As shown, the multiple level category fields include first-level tabs and multiple information modules at the second level; the tabs include multiple types, with tabs created according to object categories and third-level tags created according to data attributes.

[0050] For example, tabs include individuals and enterprises. The information modules include multiple types, established according to business categories, such as basic information, behavioral information, business information, and risk information. Each tab includes at least one information module. Tags are established based on data attributes. The tag configuration table includes Tab.name (tab name), Module.name (information module name), Profile.name (tag name), Profile.en (tag English name, a unique tag field corresponding to the initial profile wide table), Format.strategy (tag processing strategy), and Order.no (display order), as shown in Table 3. Table 3. Image Tag Configuration Table

[0051] Furthermore, new types can be added to tabs and information modules, such as... Figure 2 As shown, the metadata configuration interface includes a "Add Tab" button and a "Add Information Module" button. Clicking the "Add Tab" button will bring up a tab editing window, as follows: Figure 4 As shown. Clicking the "Add Information Module" button will bring up the module editing window. Figure 5 As shown.

[0052] Furthermore, the label dynamic generation layer 130 is specifically used for: After processing the tag values ​​of the target field using the corresponding tag processing strategy, multiple level category fields are treated as data objects of corresponding levels. Each tag field within a row of profile data is grouped according to its level category, and the tag fields within each group are stored in an array. Combining the level size with each data object and its corresponding array, multi-level JSON data is generated through key-value pair combinations. This JSON data has a three-level structure: tabs, information modules, and tags. For example, the level category is used as the key in the key-value pair, and the sub-level categories belonging to that level category and the tag fields are used as the values. The key-value pairs are stored in array format.

[0053] Exemplary, the metadata configuration layer 120 receives the user's configuration for the second tag field, specifying its associated tab, information module, display order, and tag processing strategy. It then associates the second tag field with the tab, information module, display order, and tag processing strategy and stores this association in the tag configuration table. The layer uses tabs as the first level, information modules as the second level, and tags as the third level, with tabs as the first-level key and information modules and their tag fields as key-value pairs, generating a three-level JSON data structure, such as... Figure 6 As shown, tabInfo represents the tab, and tabName represents the tab name.

[0054] In one implementation, to improve security, the tag processing strategy includes desensitization methods, formatting methods, and numerical precision standardization methods for various tags.

[0055] The metadata configuration layer 120 is also specifically used to: receive the configured data type, initial value of the tag field, desensitization method, numerical precision (including decimal place field, date precision field, etc.) and tag value display format, and generate the tag processing strategy based on at least two of them.

[0056] The information within the tag processing strategy includes at least two of the following: data type, initial value of the tag field, desensitization method, numerical precision, and tag value display format. For example, the tag processing strategy can be any of the following: Item 1: {"strategy":"STR","defaultValue":"","sensitive":"NAME"}; Item 2: {"strategy":"STR","defaultValue":"","sensitive":"COMPANYNAME"}; Item 3: {"strategy":"DECIMAL","defaultValue":"","scale":"0","mode":""}; Item 4: {"strategy":"DECIMAL","defaultValue":"","scale":"2","mode":"UP"}; Item 5: {"strategy":"DATE","defaultValue":"","format":"yyyy.Md"}; Item 6: {"strategy":"DATETIME","defaultValue":"","format":"yyyy.M.dhh:mm:ss"}.

[0057] Here, strategy represents the data type, including STR (string), DATE (date), DATETIME (time), and DECIMAL (numeric).

[0058] defaultValue represents the initial value (default value) of the tag field. For example, if some tag fields do not have a value, a default value can be configured to indicate that the field does not have a value for the time being.

[0059] Sensitive indicates the data masking method. Data masking can be performed based on the information within the masking field. For example, NAME represents name masking; for instance, [Zhang San] is displayed as [Zhang*] on the UI, and [Zhou Yi Er] is displayed as [Zhou*Tue]. COMPANYNAME represents company name masking; [Yi Er San Co., Ltd.] is displayed as [Yi **** Co., Ltd.]. PHONE represents mobile phone number masking; for example, [18600000000] is displayed as [186*****000]. ADDRESS represents address masking; [Shenzhen Yi Yi District Enterprise Park, Building 00, Floor 00] is displayed as [Shenzhen *** Enterprise Park ****]. Scale indicates numerical precision, specifying the number of decimal places: 0 for integers and 2 for decimals. Mode indicates date precision, where DOWN rounds down, UP rounds up, and ROUND rounds to the nearest whole number. The format indicates the formatting method. For example, the formatted date is yyyy.Md, which corresponds to 2025.8.28, or the formatted date is yyyy.Md hh:mm:ss, which corresponds to 2025.8.2816:36:36.

[0060] In this embodiment, the label configuration table includes information on how to display, de-identify, and sort the declared fields.

[0061] Understandably, the label dynamic generation layer 130 is specifically used for: The tag value of the target field is desensitized according to the desensitization category included in the desensitization processing method and the data type.

[0062] The precision of the label value of the target field is adjusted according to the numerical precision and the data type.

[0063] Adjust the representation format of the tag value for the target field according to the tag value display format and the data type.

[0064] In one implementation, such as Figure 7 As shown, the tag configuration system 100 also includes a dynamic rendering layer 140.

[0065] The dynamic rendering layer 140 is used to obtain the target profile information using a third-party rendering interface, generate UI components based on the target profile information, and display them according to the display order. For example, Vue can be used to dynamically render JSON data. Because the JSON data is retrieved in real time through the interface, newly added tag fields can take effect immediately. This application embodiment also includes a profile interface, such as... Figure 8 As shown, the profile interface can display individual profile data or profile data based on enterprises. For example, if an individual can be linked to all enterprises under that individual's name by their enterprise ID, the profile interface will also display the profile data of those linked enterprises. Field-level anonymization is implemented, with different anonymization rules applied to different sensitive fields.

[0066] In this embodiment, runtime formatting is performed, and all tag processing is completed in real time on the server side. The front end is only responsible for rendering the automatically generated image tags based on JSON.

[0067] Taking the addition of 10 tags as an example, in the traditional development model, the big data, backend, and frontend teams would each spend 2 days, 2 days, and 1 day respectively on development, requiring a total of 5 days. However, in this embodiment, business users can configure the interface through the data processing layer 110 and metadata configuration layer 120, which takes 2.5 days. The tag dynamic generation layer 130 automatically generates JOSN data, and the dynamic rendering layer 140 directly generates UI components, requiring no frontend modifications, thus shortening development time by 50%. Furthermore, this embodiment features zero interface changes, significantly improving system stability; the decoupling of business, data, development, and testing responsibilities enables true "business self-service."

[0068] This application also provides a terminal device, exemplary of which includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program to enable the terminal device to perform the functions of the various modules in the tag configuration system 100 described above.

[0069] The processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including at least one of a Central Processing Unit (CPU), Graphics Processing Unit (GPU), Network Processor (NP), Digital Signal Processor (DSP), Application-Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application.

[0070] The memory can be, but is not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory is used to store computer programs, and the processor can execute the computer programs accordingly after receiving execution instructions.

[0071] This application also provides a computer-readable storage medium for storing the computer program used in the aforementioned terminal device. For example, the computer-readable storage medium may include, but is not limited to, various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0072] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that, in alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0073] In addition, the functional modules or units in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0074] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a smartphone, personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0075] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A label configuration system, characterized in that, The tag configuration system includes: a data processing layer, a metadata configuration layer, and a tag dynamic generation layer; The data processing layer is used to obtain the tag value of each first tag field of each target object based on at least one determined target object and at least one newly added first tag field through the corresponding search logic, and add the corresponding first tag field and tag value to the initial portrait wide table based on each target object. The metadata configuration layer is used to receive the second tag field and tag processing strategy configured by the user, and store the second tag field and the tag processing strategy in the tag configuration table after associating them. The dynamic tag generation layer is used to load portrait data from the portrait wide table based on any second tag field in the tag configuration table, process the portrait data using the corresponding tag processing strategy, and generate target portrait information with a preset data structure.

2. The label configuration system according to claim 1, characterized in that, The data processing layer is specifically used to: generate corresponding search logic based on the first tag field configured by the user, the determined target object, and the corresponding target data table; obtain the tag values ​​of the first tag field of all target objects from the big data platform through the corresponding search logic; and add the first tag field and the corresponding tag values ​​to the initial profile wide table based on the target object.

3. The label configuration system according to claim 2, characterized in that, The search logic includes field query strategies and field offline calculation strategies; When the data processing layer generates the corresponding search logic based on the user-configured first tag field, the determined target object, and the corresponding target data table, it is specifically used for: When the search logic includes a query strategy, a structured query statement is generated based on the first tag field, target object, target data table, and structured query statement keywords input by the user from the data processing interface, and according to the statement syntax. When the search logic includes an offline field calculation strategy, a structured query statement is generated based on the target object, target data table, structured query statement keywords, and calculation logic selected from a variety of preset calculation logics input by the user from the logic configuration interface, and according to the statement syntax.

4. The label configuration system according to claim 1, characterized in that, The dynamic tag generation layer is specifically used for: Based on any second tag field in the tag configuration table, a corresponding first tag field is matched from the image width table to obtain the target field; each row of image data containing the tag value of the target field is obtained from the image width table; each row of image data includes the target field, multiple other tag fields and corresponding tag values; The corresponding tag processing strategy is used to process the tag value of the target field, and the target profile information with a preset data structure is generated based on multiple other tag fields in the row of profile data.

5. The label configuration system according to claim 4, characterized in that, The metadata configuration layer is also used for: Receive multiple level category fields and their display order configured by the user for the second tag field, and store the second tag field, the multiple level category fields, and their display order in the tag configuration table; The dynamic tag generation layer is specifically used for: After processing the tag value of the target field using the corresponding tag processing strategy, Multiple grade category fields are used as data objects for corresponding levels. Each label field in the row of profile data is grouped according to the grade category, and the label fields in each group are stored in an array. Based on the grade size, each data object and the corresponding array are combined using key-value pairs to generate multi-level JSON data.

6. The label configuration system according to claim 5, characterized in that, The multiple level category fields include a first-level tab and multiple second-level information modules; the tabs include multiple types, and the information modules include multiple types; each tab includes at least one information module; the JSON data has a three-level structure.

7. The label configuration system according to claim 5, characterized in that, The label configuration system also includes a dynamic rendering layer; The dynamic rendering layer is used to obtain the target image information using a rendering interface provided by a third party, generate UI components based on the target image information, and display them according to the display order.

8. The label configuration system according to claim 1, characterized in that, The metadata configuration layer is specifically used to cache the tag configuration table to an intermediate message queue in response to the completion of saving the tag configuration table; The tag dynamic generation layer is specifically used to: obtain the initial profile wide table and the tag configuration table from the intermediate message queue through a unified generation interface, and generate the target profile information.

9. The label configuration system according to claim 1, characterized in that, The label processing strategy includes desensitization methods, formatting methods, and numerical precision standardization methods for various labels; The metadata configuration layer is also specifically used to: receive the configured data type, initial value of the tag field, desensitization method, numerical precision and tag value display format, and generate the tag processing strategy based on at least two of them; The dynamic tag generation layer is specifically used to achieve at least two of the following three items: The first item: Desensitize the tag value of the target field according to the desensitization category included in the desensitization method and the data type; The second step: Adjust the precision of the label value of the target field according to the numerical precision and the data type; The third item: Adjust the representation format of the tag value of the target field according to the tag value display format and the data type.

10. A terminal device, characterized in that, The terminal device includes a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the functions of each module in the tag configuration system according to any one of claims 1-9.

Images