Data acquisition method and device, computer equipment and readable storage medium

Through user-defined selection and configuration rules configuration items, the target components and rendering target filter interface are automatically filtered out, which solves the problem of poor flexibility in existing data filtering solutions, realizes the flexibility and adaptability of data filtering, and improves data acquisition Efficiency and user experience.

CN119474488APending Publication Date: 2025-02-18GLODON CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411626926.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-14
Publication Date
2025-02-18

AI Technical Summary

Technical Problem

The existing data filtering schemes are poor in flexibility and cannot adapt to different user needs.

Method used

By loading a preset rule configuration interface, users can select and configure rule configuration items to automatically filter out target components and render target filter interfaces to obtain the required target data.

Benefits of technology

It realizes the flexibility and adaptability of data screening, and can dynamically adjust the screening interface and algorithms according to different user needs, improving the efficiency of data acquisition and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119474488A_ABST
    Figure CN119474488A_ABST
Patent Text Reader

Abstract

The invention discloses a data acquisition method and device, computer equipment and a computer readable storage medium, and can solve the technical problem that an existing data screening scheme is poor in flexibility and cannot adapt to different requirements of users. The method comprises the following steps: loading a preset rule configuration interface; wherein the rule configuration interface comprises a first type of rule configuration item group and a second type of rule configuration item group; receiving a selection instruction triggered by a target user in the rule configuration interface, determining a first rule configuration item from the first type of rule configuration item group, and determining a second rule configuration item from the second type of rule configuration item group; screening out a target component matched with the first rule configuration item from a preset component library; rendering a target screening interface based on the second rule configuration item and the target component; and obtaining target data required by the target user based on the target screening interface.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a data acquisition method, device, computer equipment and computer-readable storage medium. Background Art

[0002] In the data screening process, different participants have different concerns about aggregated data. However, the existing data screening solutions can only perform data queries in a hard-coded way in the front and back ends according to the specific demands of the participants, which leads to repeated adjustments to the hard-coded data.

[0003] There is currently no effective solution to the technical problems that existing data screening solutions have poor flexibility and cannot adapt to the different needs of users. Summary of the invention

[0004] The object of the present invention is to provide a data acquisition method, apparatus, computer device and computer-readable storage medium, which can solve the technical problems that existing data screening solutions have poor flexibility and cannot adapt to different user needs.

[0005] According to one aspect of the present invention, a data acquisition method is provided, the method comprising: Loading a preset rule configuration interface; wherein the rule configuration interface includes a first category rule configuration item grouping and a second category rule configuration item grouping; receiving a selection instruction triggered by a target user in the rule configuration interface, determining a first rule configuration item from the first category rule configuration item group, and determining a second rule configuration item from the second category rule configuration item group; Filtering out a target component matching the first rule configuration item from a preset component library; Rendering a target screening interface based on the second rule configuration item and the target component; The target data required by the target user is acquired based on the target screening interface.

[0006] Optionally, the acquiring target data required by the target user based on the target screening interface includes: Receiving target parameters input by the target user in the target screening interface; Generate a target screening rule based on the target parameter and the screening rule template defined by the target screening interface; Determining the target screening level to which the target screening rule belongs based on the complexity of the target screening rule; wherein the target screening level is a simple screening level or a complex screening level; Obtaining a target screening algorithm that matches the target screening level; The target data is acquired based on the target screening algorithm.

[0007] Optionally, determining the target screening level to which the target screening rule belongs based on the complexity of the target screening rule includes: Sending the target screening rule to a preset rule parser; Parsing the target screening rule by the rule parser to obtain a rule parsing result; Determining, by the rule parser, whether a rule configuration item of a preset type in the rule parsing result complies with the screening rule associated with the simple screening level; If yes, determining that the target screening level is a simple screening level; If not, it is determined that the target screening level is a complex screening level.

[0008] Optionally, acquiring a target screening algorithm that matches the target screening level includes: When the target screening level is a simple screening level, a data screening algorithm is determined from hard coding in the local package as the target screening algorithm; When the target screening level is a complex screening level, a first algorithm plug-in matching the target screening rule is called from external soft coding as the target screening algorithm.

[0009] Optionally, acquiring the target data based on the target screening algorithm includes: Filter out first target sub-data from the data screening range defined by the target screening rule based on the target screening algorithm; Reading a preset plug-in identifier, and determining whether there is a second algorithm plug-in including the plug-in identifier in the external soft coding; wherein the second algorithm plug-in is used to perform data screening within an extended screening range, and the extended screening range is a data range outside the data screening range; If yes, calling the second algorithm plug-in to filter out the second target sub-data from the extended screening range, and concatenating the first target sub-data and the second target sub-data to obtain the target data; If not, the first target sub-data is directly used as the target data.

[0010] Optionally, the method further comprises: receiving a tag adding instruction, and determining a parameter pointed to by the tag adding instruction from the target parameter as a target sub-parameter; The screening rule template and the target sub-parameter are created as a target user tag of the target user.

[0011] Optionally, the method further comprises: receiving a loading instruction for the target user tag, and acquiring a screening rule template and target sub-parameters associated with the target user tag; The target screening interface is reversely loaded based on the screening rule template, and the target sub-parameter is added to the target screening interface.

[0012] In order to achieve the above object, the present invention further provides a data acquisition device, characterized in that the device comprises: A loading module, used to load a preset rule configuration interface; wherein the rule configuration interface includes a first category rule configuration item grouping and a second category rule configuration item grouping; a determination module, configured to receive a selection instruction triggered by a target user in the rule configuration interface, determine a first rule configuration item from the first category rule configuration item group, and determine a second rule configuration item from the second category rule configuration item group; A screening module, used to screen out target components matching the first rule configuration item from a preset component library; A rendering module, used for rendering a target screening interface based on the second rule configuration item and the target component; The acquisition module is used to acquire the target data required by the target user based on the target screening interface.

[0013] In order to achieve the above-mentioned purpose, the present invention also provides a computer device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that when the processor executes the computer program, it is used to implement the steps of a data acquisition method introduced above.

[0014] In order to achieve the above object, the present invention also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, it is used to implement the steps of a data acquisition method introduced above.

[0015] A data acquisition method provided by the present invention introduces a rule-configured data acquisition mode, allowing users to flexibly select configuration items through a configuration interface according to their own concerns to meet their respective concerns; further, a target screening interface is automatically configured based on the configuration items selected by the user, and the target data required by the user is screened out based on the target screening interface; wherein, part of the rule configuration items selected by the user are used to select the target component, and part are used to generate the target screening interface together with the target component. The technical solution of the present application solves the technical problem that the existing data screening solution is poor in flexibility and cannot adapt to different user needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings: Figure 1 A flow chart of a data acquisition method provided in Example 1; Figure 2 A schematic diagram of rendering a target screening interface based on a target component provided in Example 1; Figure 3 This is a diagram showing the differences between the data acquisition solution provided in Example 1 and the prior art; Figure 4 A block diagram of a data acquisition device provided in Embodiment 2; Figure 5 A block diagram of a computer device suitable for implementing the data acquisition method provided in Example 3. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0018] Embodiment 1 The embodiment of the present invention provides a data acquisition method, such as Figure 1 As shown, the method includes steps S1 to S5, wherein: Step S1, loading a preset rule configuration interface; wherein the rule configuration interface includes a first category rule configuration item grouping and a second category rule configuration item grouping.

[0019] There are multiple areas set on the rule configuration interface, each area is set with several rule configuration items, and the categories of rule configuration items set in different areas are different. Among them, the types of rule configuration items in the rule configuration interface include: filter item selection (can represent the filtering field, such as the insurance policy field, bidding field, etc.), filter item name (specific scope of the filtering field, such as the life insurance policy named "First Life" and the bidding document named "First Project", etc.), filter item type selection (including text, date, time, number, single choice, multiple choice, drop-down single choice, drop-down checkbox, pop-up box, drop-down tree, etc., corresponding to the components in the component library, users can choose their favorite components), filtering logic (including greater than, greater than or equal to, less than, less than or equal to, equal to, fuzzy, interval, inclusion, rule range, etc., users can choose according to usage habits), filter item proxy interface (involving external structured dictionary data, external structured data can be directly used through the configuration interface), filter item value domain (for data in a smaller range, the option range can be directly defined), whether function filtering (can represent whether filtering is required from outside the field), whether global filtering (can represent whether it is used by specified users or shared by all users, which can be used to set user feature configuration), filtering sorting (the rendering position of the filtering conditions is determined by the user's usage habits).

[0020] The rule configuration items in the rule configuration interface can be divided into two groups: the first category rule configuration item grouping and the second category rule configuration item grouping; wherein, the first category rule configuration item grouping and the second category rule configuration item grouping both contain several types of rule configuration items, and the rule configuration items in the first category rule configuration item grouping are used to determine the components required for the filtering interface, and the rule configuration items in the second category rule configuration item grouping are used to generate the filtering interface together with the components.

[0021] For example, the first category of rule configuration item grouping includes all rule configuration items in the above filter item type selection; the second category of rule configuration item grouping includes all rule configuration items in the above "filter item selection, filter item name, filter logic, filter item proxy interface, filter item value range, whether function filtering, whether global filtering, and filter sorting".

[0022] Step S2, receiving a selection instruction triggered by a target user in the rule configuration interface, determining a first rule configuration item from the first category rule configuration item group, and determining a second rule configuration item from the second category rule configuration item group.

[0023] Step S3, screening out target components matching the first rule configuration item from a preset component library.

[0024] Step S4: Rendering a target screening interface based on the second rule configuration item and the target component.

[0025] The first rule configuration item and the second rule configuration item both include several types of rule configuration items, and each type of rule configuration item is one or more. Among them, the first rule configuration item is used to select the target component, and the second rule configuration item is used to render the target filtering interface together with the target component. When the second rule configuration item includes multiple types of rule configuration items, in the second rule configuration item: the rule configuration items belonging to the filter item selection and filter item name are used to determine the data filtering range; the rule configuration items belonging to the filtering logic, filter item proxy interface, filter item value domain and filtering sorting are used to determine the interface style with the first rule configuration item; the rule configuration items belonging to whether function filtering is used to determine whether filtering is only performed within the above-mentioned data filtering range; the rule configuration items belonging to whether global filtering is used to determine whether the filtered target data is only for target users or shared by all users.

[0026] The component library includes multiple components, which are used to determine the interface style, including: date component, date range component, time component, text component, drop-down single-select component, drop-down multiple-select component, drop-down tree component, redio single-select component, checkbox multiple-select component, number component, number range component and custom pop-up component. The component library can be dynamically expanded according to user needs. The target component is selected through the first rule configuration item, and the filtering interface that the user is concerned about is automatically rendered in combination with the second rule configuration item. Figure 2 As shown, the components contained in the form item control component are target components, and the advanced filtering form on the right is formed through the target components.

[0027] Step S5: acquiring target data required by the target user based on the target screening interface.

[0028] Specifically, the target parameters input by the target user in the target screening interface can be received; based on the target parameters and the screening rule template defined by the target screening interface, a target screening rule is generated; based on the target screening rule, the target data required by the target user is obtained. The specific screening method for obtaining the target data required by the target user based on the target screening rule can be implemented through existing solutions.

[0029] Among them, the target data can be data in any field. For example, the target data is the bid information data in the bidding field, the insurance data in the insurance field, etc. It should be noted that in the process of electronic bidding, different participants have different concerns about the aggregated information data. Based on this, the existing processing scheme can only deal with this scenario in a front-end and back-end hard-coding manner according to the specific demands of the management party involved in the transaction activity. There will often be repeated adjustments to the hard-coding, and it is difficult to perfectly handle the different demands of different users; finally, if there are inconsistent demands for different participants in electronic bidding transaction activities, the existing technology can only provide full-set support, which poses certain challenges to the performance of obtaining bid information and the experience of the participants. Through the present invention, both the tenderer and the bidder can flexibly configure the screening interface according to their own needs without repeatedly changing the hard-coding.

[0030] The present invention is a custom conditional data acquisition method based on rule configuration. The configuration end can perform flexible rule configuration, and the component library automatically matches the rule condition rendering style to achieve the user's required experience effect, ultimately achieving the purpose of data acquisition, and solving the technical problems of poor flexibility and inability to adapt to different user needs of existing data screening solutions.

[0031] As an optional embodiment, the acquiring the target data required by the target user based on the target screening interface includes: Receiving target parameters input by the target user in the target screening interface; Generate a target screening rule based on the target parameter and the screening rule template defined by the target screening interface; Determining the target screening level to which the target screening rule belongs based on the complexity of the target screening rule; wherein the target screening level is a simple screening level or a complex screening level; Obtaining a target screening algorithm that matches the target screening level; The target data is acquired based on the target screening algorithm.

[0032] Among them, the target screening interface defines a screening rule template, which has not yet formed a complete screening rule. It is necessary to enter specific parameters in the screening rule template to obtain the screening rule for data screening; wherein, the screening rule is also the data screening condition. In this embodiment, when the target user needs to perform data screening, the target parameter can be entered in the target screening interface. The system can obtain the target screening rule for screening out the target data by filling the target parameter into the screening rule template defined by the target screening interface.

[0033] Two screening levels are pre-set: simple screening level and complex screening level. Based on the complexity of the target screening rule, the target screening level to which the target screening rule belongs can be determined. For example, among the rule configuration items contained in the target screening rule, only one rule configuration item belongs to the category of screening logic, then it can be considered that the complexity of the target screening rule is low, and the screening level of the target screening rule is determined to be a simple screening level; otherwise, it is determined to be a complex screening level.

[0034] Different filtering levels correspond to different filtering algorithms. For example, the filtering algorithm corresponding to the simple filtering level is a hard-coded data filtering algorithm, and the filtering algorithm corresponding to the complex filtering level is an external soft-coded algorithm plug-in; executing the target filtering rules based on the target filtering algorithm can filter out the target data.

[0035] By setting different screening levels to correspond to different screening algorithms, the precision of screening is improved.

[0036] As an optional embodiment, determining the target screening level to which the target screening rule belongs based on the complexity of the target screening rule includes: Sending the target screening rule to a preset rule parser; Parsing the target screening rule by the rule parser to obtain a rule parsing result; Determining, by the rule parser, whether a rule configuration item of a preset type in the rule parsing result complies with the screening rule associated with the simple screening level; If yes, determining that the target screening level is a simple screening level; If not, it is determined that the target screening level is a complex screening level.

[0037] Based on the rule configuration selected by the target user on the configuration side, the component library will automatically render the target data acquisition style based on the rule configuration, and perform data retrieval based on the rule configuration. The rule-rendered style will bring the rules and corresponding target parameters back to the preset rule parsing engine. After the rule parser obtains the parameters involved in the rules, it will retrieve and parse the parameters according to the rule description, and finally complete the data acquisition.

[0038] The preset type may be the type of filtering logic, and the rule configuration items of the preset type are the rule configuration items in the filtering logic, for example, the rule configuration items of the preset type are greater than, greater than or equal to, less than, less than or equal to, equal to, and contain. The filtering rules associated with the simple filtering level are: including N rule configuration items in the filtering logic; or, the filtering rules associated with the simple filtering level are: including N rule configuration items in the filtering logic and the target filtering rule is to directly scan the target data from the data filtering range without the need for additional data conversion. N can be set according to user needs, for example, N is 1.

[0039] Since there are many types of complex screening levels, it is difficult to pre-write all of their screening rules, and the types of simple screening levels are limited, so the screening rules associated with the simple screening levels are pre-set to determine whether this screening is a simple screening level. If not, it must be a complex screening level.

[0040] As an optional embodiment, the acquiring a target screening algorithm matching the target screening level includes: When the target screening level is a simple screening level, a data screening algorithm is determined from hard coding in the local package as the target screening algorithm; When the target screening level is a complex screening level, a first algorithm plug-in matching the target screening rule is called from external soft coding as the target screening algorithm.

[0041] Among them, for the simple screening level, the data screening method encapsulated in the architecture can be used to screen the target data. Multiple algorithm plug-ins are set by external soft coding. For the complex screening level, the first algorithm plug-in that matches the target screening rule can be selected to screen the target data.

[0042] For logic involving multiple condition-associated mixed retrieval, it is necessary to associate and filter multiple related and unrelated conditions, and complete personalized function screening, which belongs to the complex screening level. For example, a schematic scenario of the complex screening level is: the contract estimated price interval screening in the bid section group scenario, which not only has different unit amount conversions, but also only has the contract estimated price in the bid section scenario, and the screening of the bid section group project needs to be skipped; another schematic scenario of the complex screening level is: the start time and the deadline for obtaining the bidding / qualification review documents, which requires considering both the screening of the dual data of the qualification review and the post-review, and the screening of the dual interval data.

[0043] Through screening grading, the breadth of screening scenarios is increased; and for complex screening levels, there is no need to change the device hard coding, but screening can be achieved by calling external soft coding.

[0044] As an optional embodiment, the acquiring the target data based on the target screening algorithm includes: Filter out first target sub-data from the data screening range defined by the target screening rule based on the target screening algorithm; Reading a preset plug-in identifier, and determining whether there is a second algorithm plug-in including the plug-in identifier in the external soft coding; wherein the second algorithm plug-in is used to perform data screening within an extended screening range, and the extended screening range is a data range outside the data screening range; If yes, calling the second algorithm plug-in to filter out the second target sub-data from the extended screening range, and concatenating the first target sub-data and the second target sub-data to obtain the target data; If not, the first target sub-data is directly used as the target data.

[0045] For more complex screening requirements, such as business data outside the field, the existing technology can only be handled by continuously adjusting the hard-coded method. However, this embodiment can introduce external plug-ins through reserved plug-in interfaces, thereby achieving the purpose of calling external plug-ins to perform data screening from outside the field.

[0046] As an optional embodiment, reading a preset plug-in identifier includes: When the target screening rule includes a rule configuration item that allows function screening, a preset plug-in identifier is read.

[0047] The method further comprises: When the target screening rule includes a rule configuration item for prohibiting function screening, reading the preset plug-in identifier is prohibited, and the first target sub-data is directly used as the target data.

[0048] Among them, if the user selects the rule configuration item "allow function filtering" when customizing the selection rule configuration item, it means that the user allows data selection from outside the domain during this screening. At this time, when filtering the target data based on the target screening algorithm, it can be considered whether the external plug-in has called the preset plug-in identifier. If so, the logic of the plug-in is executed to filter data from outside the domain. If the user selects the rule configuration item "prohibit function filtering" when customizing the selection rule configuration item, it means that the user prohibits data selection from outside the domain during this screening. At this time, when filtering the target data based on the target screening algorithm, regardless of whether the external plug-in has called the preset plug-in identifier, the logic of the external plug-in will not be executed. Therefore, reading the preset plug-in identifier is directly prohibited, and the first target sub-data filtered out from the domain is used as the required target data.

[0049] As an optional embodiment, the method further includes: receiving a tag adding instruction, and determining a parameter pointed to by the tag adding instruction from the target parameter as a target sub-parameter; The screening rule template and the target sub-parameter are created as a target user tag of the target user.

[0050] The target screening interface is provided with a label adding component; in response to the target user's selection instruction for the label adding component, the label adding interface is loaded; the parameter names corresponding to the parameters in the target parameters are displayed on the label adding interface; a label adding instruction is received; the label adding instruction carries the parameter names corresponding to the target sub-parameters; the parameters corresponding to the parameter names carried in the label adding instruction are determined from the target parameters, i.e., the target sub-parameters. It should be noted that the target sub-parameters can be all the target parameters or part of the target parameters, see Figure 2 Example.

[0051] By recording the user's data filtering rule conditions each time, or the user's customized collection, as a user tag, the user can better focus on the selected target data.

[0052] As an optional embodiment, the method further includes: receiving a loading instruction for the target user tag, and acquiring a screening rule template and target sub-parameters associated with the target user tag; The target screening interface is reversely loaded based on the screening rule template, and the target sub-parameter is added to the target screening interface.

[0053] By selecting a pre-cached user tag, the user's previously configured screening interface can be reversely loaded, and the target sub-parameters required by the user can be added to the target screening interface, saving the user extra configuration time. In addition, after the target screening interface is reversely loaded based on the screening rule template and the target sub-parameters are added to the target screening interface, the method further includes: receiving a parameter modification instruction, determining the parameter to be modified from the target sub-parameters, and replacing the parameter to be modified with the parameter carried in the parameter modification instruction. By setting the modification logic, users can modify the rule configuration based on the recommendation, reducing the user's manual configuration work and improving retrieval performance.

[0054] Figure 3 The similarities and differences between the present invention and the prior art are schematically pointed out.

[0055] Similarities: Both the present invention and the prior art have a screening interface at the application layer.

[0056] Differences: 1. The present invention and the prior art generate a different way of filtering interface. The prior art generates a filtering interface through fixed components, and the interface style is fixed and immutable; the present invention flexibly generates the filtering interface required by the user through user-defined selection components and rule configuration items, and the interface style can be customized. 2. The present invention is different from the prior art in specific filtering methods. First, the prior art uses fixed search rules; the present invention uses user-defined search rules or reverse calls pre-configured rules using user tags. Secondly, the prior art only relies on the hard-coded algorithm inside the system for data filtering; the present invention classifies the filtering, and only the simple filtering level uses the internal hard-coded algorithm, and the complex filtering level calls the external soft-coded algorithm. 3. The parsing logic of the present invention is different from that of the prior art. The prior art parses fixed search rules, while the present application parses user-defined rules. The parsing logic is complicated and far exceeds the calculation amount of the prior art. 4. The data screening range of the present invention is different from that of the prior art. The prior art can usually only search within the data screening range limited by the hard code. If you want to expand the screening range, you can only modify the hard code; the present invention reserves a plug-in interface, which can be customized to expand the data screening range without modifying the hard code inside the system.

[0057] Embodiment 2 The embodiment of the present invention provides a data acquisition device, such as Figure 4 As shown, the data acquisition device 40 specifically includes the following components: The loading module 401 is used to load a preset rule configuration interface; wherein the rule configuration interface includes a first category rule configuration item grouping and a second category rule configuration item grouping; The determination module 402 is used to receive a selection instruction triggered by a target user in the rule configuration interface, determine a first rule configuration item from the first category rule configuration item group, and determine a second rule configuration item from the second category rule configuration item group; A screening module 403 is used to screen out target components matching the first rule configuration item from a preset component library; A rendering module 404, configured to render a target screening interface based on the second rule configuration item and the target component; The acquisition module 405 is used to acquire the target data required by the target user based on the target screening interface.

[0058] As an optional embodiment, the acquisition module is specifically used for: Receiving target parameters input by the target user in the target screening interface; Generate a target screening rule based on the target parameter and the screening rule template defined by the target screening interface; Determining the target screening level to which the target screening rule belongs based on the complexity of the target screening rule; wherein the target screening level is a simple screening level or a complex screening level; Obtaining a target screening algorithm that matches the target screening level; The target data is acquired based on the target screening algorithm.

[0059] As an optional embodiment, when the acquisition module executes the step of determining the target screening level to which the target screening rule belongs based on the complexity of the target screening rule, it is specifically used to: Sending the target screening rule to a preset rule parser; Parsing the target screening rule by the rule parser to obtain a rule parsing result; Determining, by the rule parser, whether a rule configuration item of a preset type in the rule parsing result complies with the screening rule associated with the simple screening level; If yes, determining that the target screening level is a simple screening level; If not, it is determined that the target screening level is a complex screening level.

[0060] As an optional embodiment, when executing the step of acquiring the target screening algorithm matching the target screening level, the acquisition module is specifically configured to: When the target screening level is a simple screening level, a data screening algorithm is determined from hard coding in the local package as the target screening algorithm; When the target screening level is a complex screening level, a first algorithm plug-in matching the target screening rule is called from external soft coding as the target screening algorithm.

[0061] As an optional embodiment, when executing the step of acquiring the target data based on the target screening algorithm, the acquisition module is specifically used to: Filter out first target sub-data from the data screening range defined by the target screening rule based on the target screening algorithm; Reading a preset plug-in identifier, and determining whether there is a second algorithm plug-in including the plug-in identifier in the external soft coding; wherein the second algorithm plug-in is used to perform data screening within an extended screening range, and the extended screening range is a data range outside the data screening range; If yes, calling the second algorithm plug-in to filter out the second target sub-data from the extended screening range, and concatenating the first target sub-data and the second target sub-data to obtain the target data; If not, the first target sub-data is directly used as the target data.

[0062] As an optional embodiment, the method further includes: receiving a tag adding instruction, and determining a parameter pointed to by the tag adding instruction from the target parameter as a target sub-parameter; The screening rule template and the target sub-parameter are created as a target user tag of the target user.

[0063] As an optional embodiment, the method further includes: receiving a loading instruction for the target user tag, and acquiring a screening rule template and target sub-parameters associated with the target user tag; The target screening interface is reversely loaded based on the screening rule framework, and the target sub-parameters are added to the target screening interface.

[0064] Embodiment 3 This embodiment also provides a computer device, such as a smart phone, tablet computer, laptop computer, desktop computer, rack server, blade server, tower server or cabinet server (including an independent server or a server cluster composed of multiple servers) that can execute programs. Figure 5 As shown, the computer device 50 of this embodiment includes at least but not limited to: a memory 501 and a processor 502 that can communicate with each other via a system bus. It should be noted that Figure 5 Only computer device 50 is shown with components 501 - 502 , but it should be understood that implementing all of the components shown is not a requirement, and more or fewer components may alternatively be implemented.

[0065] In this embodiment, the memory 501 (i.e., readable storage medium) includes flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 501 can be an internal storage unit of the computer device 50, such as a hard disk or memory of the computer device 50. In other embodiments, the memory 501 can also be an external storage device of the computer device 50, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card, etc. equipped on the computer device 50. Of course, the memory 501 can also include both the internal storage unit of the computer device 50 and its external storage device. In this embodiment, the memory 501 is generally used to store the operating system and various application software installed on the computer device 50. In addition, the memory 501 can also be used to temporarily store various data that have been output or are to be output.

[0066] In some embodiments, the processor 502 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 502 is generally used to control the overall operation of the computer device 50 .

[0067] Specifically, in this embodiment, the processor 502 is used to execute the program of the data acquisition method stored in the memory 501, and the program of the data acquisition method implements the following steps when being executed: Loading a preset rule configuration interface; wherein the rule configuration interface includes a first category rule configuration item grouping and a second category rule configuration item grouping; receiving a selection instruction triggered by a target user in the rule configuration interface, determining a first rule configuration item from the first category rule configuration item group, and determining a second rule configuration item from the second category rule configuration item group; Filtering out a target component matching the first rule configuration item from a preset component library; Rendering a target screening interface based on the second rule configuration item and the target component; The target data required by the target user is acquired based on the target screening interface.

[0068] The specific implementation process of the above method steps can be found in Example 1, and this embodiment will not be repeated here.

[0069] Embodiment 4 This embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (for example, an SD or DX memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a disk, an optical disk, a server, an App application store, etc., on which a computer program is stored. When the computer program is executed by a processor, the following method steps are implemented: Loading a preset rule configuration interface; wherein the rule configuration interface includes a first category rule configuration item grouping and a second category rule configuration item grouping; receiving a selection instruction triggered by a target user in the rule configuration interface, determining a first rule configuration item from the first category rule configuration item group, and determining a second rule configuration item from the second category rule configuration item group; Filtering out a target component matching the first rule configuration item from a preset component library; Rendering a target screening interface based on the second rule configuration item and the target component; The target data required by the target user is acquired based on the target screening interface.

[0070] The specific implementation process of the above method steps can be found in Example 1, and this embodiment will not be repeated here.

[0071] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0072] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0073] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method.

[0074] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A data acquisition method, characterized in that: The method comprises: Loading a preset rule configuration interface; wherein the rule configuration interface includes a first category rule configuration item grouping and a second category rule configuration item grouping; receiving a selection instruction triggered by a target user in the rule configuration interface, determining a first rule configuration item from the first category rule configuration item group, and determining a second rule configuration item from the second category rule configuration item group; Filtering out a target component matching the first rule configuration item from a preset component library; Rendering a target screening interface based on the second rule configuration item and the target component; The target data required by the target user is acquired based on the target screening interface.

2. The method according to claim 1, characterized in that The acquiring target data required by the target user based on the target screening interface includes: Receiving target parameters input by the target user in the target screening interface; Generate a target screening rule based on the target parameter and the screening rule template defined by the target screening interface; Determining the target screening level to which the target screening rule belongs based on the complexity of the target screening rule; wherein the target screening level is a simple screening level or a complex screening level; Obtaining a target screening algorithm that matches the target screening level; The target data is acquired based on the target screening algorithm.

3. The method according to claim 2, characterized in that Determining the target screening level to which the target screening rule belongs based on the complexity of the target screening rule includes: Sending the target screening rule to a preset rule parser; Parsing the target screening rule by the rule parser to obtain a rule parsing result; Determining, by the rule parser, whether a rule configuration item of a preset type in the rule parsing result complies with the screening rule associated with the simple screening level; If yes, determining that the target screening level is a simple screening level; If not, it is determined that the target screening level is a complex screening level.

4. The method according to claim 2, characterized in that: The obtaining of a target screening algorithm matching the target screening level comprises: When the target screening level is a simple screening level, a data screening algorithm is determined from hard coding in the local package as the target screening algorithm; When the target screening level is a complex screening level, a first algorithm plug-in matching the target screening rule is called from external soft coding as the target screening algorithm.

5. The method according to claim 2, characterized in that: The acquiring the target data based on the target screening algorithm comprises: Filter out first target sub-data from the data screening range defined by the target screening rule based on the target screening algorithm; Reading a preset plug-in identifier, and determining whether there is a second algorithm plug-in including the plug-in identifier in the external soft coding; wherein the second algorithm plug-in is used to perform data screening within an extended screening range, and the extended screening range is a data range outside the data screening range; If yes, calling the second algorithm plug-in to filter out the second target sub-data from the extended screening range, and concatenating the first target sub-data and the second target sub-data to obtain the target data; If not, the first target sub-data is directly used as the target data.

6. The method according to claim 2, characterized in that The method further comprises: receiving a tag adding instruction, and determining a parameter pointed to by the tag adding instruction from the target parameter as a target sub-parameter; The screening rule template and the target sub-parameter are created as a target user tag of the target user.

7. The method according to claim 6, characterized in that The method further comprises: receiving a loading instruction for the target user tag, and acquiring a screening rule template and target sub-parameters associated with the target user tag; The target screening interface is reversely loaded based on the screening rule template, and the target sub-parameter is added to the target screening interface.

8. A data acquisition device, characterized in that: The device comprises: A loading module, used to load a preset rule configuration interface; wherein the rule configuration interface includes a first category rule configuration item grouping and a second category rule configuration item grouping; a determination module, configured to receive a selection instruction triggered by a target user in the rule configuration interface, determine a first rule configuration item from the first category rule configuration item group, and determine a second rule configuration item from the second category rule configuration item group; A screening module, used to screen out target components matching the first rule configuration item from a preset component library; A rendering module, used for rendering a target screening interface based on the second rule configuration item and the target component; The acquisition module is used to acquire the target data required by the target user based on the target screening interface.

9. A computer device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is used to implement the steps of the method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it is used to implement the steps of the method according to any one of claims 1 to 7.