Data processing methods, apparatus, electronic devices and storage media
By acquiring user data and behavioral data, and establishing merging rules for user screening, the problem of complex and time-consuming rule configuration in existing technologies is solved, thereby improving data processing efficiency and the accuracy of risk level judgment.
Patent Information
- Application Number
- CN202410298870.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-03-15
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2044-03-15
AI Technical Summary
In existing technologies, configuring data processing rules for user groups is complex and time-consuming, leading to inaccurate risk level assessments.
By acquiring user operation behavior data and user data, user attribute tags and objective functions are determined, merging rules corresponding to risk levels are established, user screening processes are performed, and target user sets under different risk levels are obtained.
This simplifies rule configuration, improves data processing efficiency, and ensures the accuracy of risk level assessment and refined filtering effects.
Smart Images

Figure CN118113916B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data processing technology, and in particular to a data processing method, apparatus, electronic device, and storage medium. Background Technology
[0002] In order to conduct refined user operations, user groups can be segmented and filtered based on corresponding rules to achieve segmented operations for different user groups.
[0003] Currently, existing technologies primarily configure different rules for different user groups. However, this approach suffers from complex and time-consuming rule configuration. Furthermore, due to the large number of rules configured, omissions or errors may occur, leading to inaccuracies in determining user risk levels based on these rules. Summary of the Invention
[0004] This invention provides a data processing method, apparatus, electronic device, and storage medium. By using merging rules to process data, target user sets corresponding to different risk levels are obtained, thereby improving the efficiency of data processing.
[0005] According to one aspect of the present invention, a data processing method is provided, the method comprising:
[0006] Acquire at least one user's operational behavior data and user data on the target program, and treat the operational behavior data and user data as data to be processed;
[0007] Determine the user attribute label of at least one user corresponding to each piece of data to be processed, as well as the objective function corresponding to the user attribute label, and use the user attribute label as the objective label;
[0008] Based on at least one target label and corresponding objective function for each piece of data to be processed, at least one merging rule is determined, wherein the merging rule is a rule corresponding to the risk level;
[0009] For at least one merging rule, at least one user is filtered according to the current merging rule to obtain a target user set under the risk level corresponding to the current merging rule, so as to obtain target user sets under different risk levels.
[0010] According to another aspect of the present invention, a data processing apparatus is provided, the apparatus comprising:
[0011] The data acquisition module is used to acquire at least one user's operation behavior data and user data on the target program, and to treat the operation behavior data and user data as data to be processed.
[0012] The label and function determination module is used to determine the user attribute label of at least one user corresponding to each piece of data to be processed and the target function corresponding to the user attribute label, and to use the user attribute label as the target label;
[0013] The merging rule determination module is used to determine at least one merging rule based on at least one target label and corresponding objective function for each piece of data to be processed, wherein the merging rule is a rule corresponding to the risk level;
[0014] The target user set determination module is used to filter at least one user according to the current merging rule for at least one merging rule, so as to obtain the target user set under the risk level corresponding to the current merging rule, so as to obtain the target user set under different risk levels.
[0015] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:
[0016] At least one processor; and
[0017] A memory that is communicatively connected to at least one processor; wherein,
[0018] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor is able to perform the data processing method of any embodiment of the present invention.
[0019] According to another aspect of the present invention, a computer-readable storage medium is provided that stores computer instructions for causing a processor to execute and implement the data processing method of any embodiment of the present invention.
[0020] The technical solution of this invention involves acquiring operational behavior data and user data of at least one user on a target program, and using this data as data to be processed; determining the user attribute tags and corresponding objective functions for at least one user corresponding to each piece of data to be processed, and using these user attribute tags as target tags; determining at least one merging rule based on the at least one target tag and corresponding objective function for each piece of data to be processed, wherein the merging rule is a rule corresponding to a risk level; for each merging rule, filtering is performed on at least one user according to the current merging rule to obtain a target user set under the risk level corresponding to the current merging rule, thereby obtaining target user sets under different risk levels. This achieves data processing using merging rules to determine the target user set under each risk level, achieving the purpose of fine-grained filtering of at least one user, solving the problem of complex and time-consuming rule configuration, and improving the efficiency of data processing.
[0021] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description
[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0023] Figure 1 This is a flowchart of a data processing method provided in an embodiment of the present invention;
[0024] Figure 2 This is a flowchart of a data processing method provided in an embodiment of the present invention;
[0025] Figure 3 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present invention;
[0026] Figure 4 This is a schematic diagram of the structure of an electronic device that implements the data processing method of the present invention. Detailed Implementation
[0027] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0029] Example 1
[0030] Figure 1 This is a flowchart of a data processing method provided in an embodiment of the present invention. This embodiment is applicable to situations where at least one user is screened and filtered according to merging rules to determine target user sets corresponding to different risk levels. This method can be executed by a data processing device, which can be implemented in hardware and / or software and can be configured in electronic devices such as mobile phones, computers, or servers. Figure 1 As shown, the method includes:
[0031] S110. Obtain at least one user's operation behavior data and user data on the target program, and treat the operation behavior data and user data as data to be processed.
[0032] In determining the risk level of at least one user for subsequent resource allocation, data analysis of at least one user is required. Since this process involves a large amount of data, to ensure efficiency and accuracy, tags and rules can be established for at least one user. This allows for further data processing based on these tags and rules upon subsequent data acquisition. The target program can be one or more applications or apps related to risk level assessment. Users generate a large amount of data during account activation and usage within the corresponding program or app. This data can be categorized into operational behavior data and user data. Operational behavior data includes whether a user has activated an account in the target program, whether a user has used a specific function of the target program, and the duration of user access to the target program. This is merely an example and not a limitation in this embodiment. User data can include user identity information such as age, education level, contact information, and the location of the user's mobile phone number. Furthermore, the aforementioned operational behavior data and user data can be treated as pending data for subsequent tag setting and rule establishment.
[0033] Specifically, based on the registration and related operational behavior of at least one user on the target program, operational behavior data and user data are obtained from the corresponding database, and the operational behavior data and user data are used as data to be processed, so as to determine the target user set with different risk levels through subsequent data processing based on the data to be processed.
[0034] Optionally, at least one user's operation behavior data and user data on the target program are obtained, and the operation behavior data and user data are used as data to be processed, including: retrieving the associated data corresponding to at least one business to be processed based on the target program, wherein the associated data includes at least one of operation behavior data and user data, and the business to be processed is a business related to the risk level; cleaning and processing the associated data to determine the data to be processed.
[0035] Users may conduct transactions related to risk levels based on target procedures, from which relevant user data and operational behavior data can be obtained. These transactions can then be considered pending transactions. The user data and operational behavior data from these pending transactions are considered associated data; that is, the associated data includes at least one type of user data and operational behavior data from at least one pending transaction.
[0036] Specifically, the relevant data corresponding to the pending business is retrieved from the target program. Since there may be at least one pending business, the relevant data corresponding to one or more pending businesses can be retrieved. Based on the retrieved relevant data, data cleaning is performed, such as checking the consistency of the relevant data, handling missing values, and deleting duplicate values. This cleaned relevant data is then used as the pending data for determining the risk level of the corresponding user.
[0037] S120. Determine the user attribute label of at least one user corresponding to each piece of data to be processed and the objective function corresponding to the user attribute label, and use the user attribute label as the objective label.
[0038] The target label is a label determined from at least one user attribute label. Depending on the business, the data obtained after data cleaning of the corresponding related data will differ. Therefore, at least one user attribute label can be pre-determined based on different business and corresponding data. That is, the user attribute label can be an attribute label abstracted from user data and operational behavior data. For example, user attributes can be user category, education level, user age, etc. Correspondingly, the label corresponding to the currently processed data can be determined from the user attribute labels and used as the target label. The objective function can be a function used to calculate the target label. For example, if the target label is user age, the objective function could be user age > 18 years old. If the target label is the location of the user's mobile phone number, the objective function could be user mobile phone number location = province A.
[0039] Specifically, after determining the data to be processed, a target label can be determined for each piece of data based on at least one user attribute label. Then, a corresponding objective function is determined based on the target label and the corresponding data to be processed. The objective function includes the target label and operations performed on that target label.
[0040] For example, the data to be processed can have multiple target labels, such as user category, education level, and user age. Correspondingly, the data can be analyzed to obtain the objective functions corresponding to the target labels. For example, the objective function could be: user category = student user; education level = bachelor's degree; user age > 18 years old, etc. Based on this, it is convenient to subsequently merge the various obtained objective functions to obtain corresponding merging rules, thereby enabling filtering of at least one user and determining the target user corresponding to each risk level.
[0041] Optionally, determine at least one user attribute label for each piece of data to be processed and the target function corresponding to the user attribute label, and use the user attribute label as the target label, including: based on at least one business to be processed, determine at least one preset label and a preset function corresponding to the preset label, wherein the preset label is a pre-set user attribute label; for each piece of data to be processed, determine at least one preset label corresponding to the data to be processed and the preset function corresponding to the preset label, and use it as the target label and the target function.
[0042] In this embodiment of the invention, the preset function can be a function that performs corresponding calculation rules on each preset tag.
[0043] Specifically, each pending business transaction is pre-defined with corresponding user attribute tags, known as preset tags. The corresponding calculation rules for each preset tag are then defined according to requirements, forming preset functions. For each piece of data to be processed, its corresponding tag can be found among at least one preset tag; this is the target tag. Accordingly, the data to be processed can determine the function that meets its actual needs from at least one preset function corresponding to the preset tag, based on the requirements of its corresponding pending business transaction; this function serves as the target function.
[0044] S130. Based on at least one target label and corresponding objective function corresponding to each data to be processed, determine at least one merging rule, wherein the merging rule is a rule corresponding to the risk level.
[0045] The merging rule can be determined by combining at least one target label and its corresponding objective function. The merging rule corresponds to the risk level; that is, different merging rules correspond to different risk levels.
[0046] Specifically, after determining the target label and objective function corresponding to each piece of data to be processed, common target labels and objective functions can be determined based on at least one target label and at least one objective function. Merging rules can then be determined based on these common target labels and objective functions, so that at least one user can be divided according to the merging rules, and the risk level corresponding to each user can be determined.
[0047] Optionally, based on at least one target label and corresponding objective function corresponding to each piece of data to be processed, at least one merging rule is determined, including: based on at least one target label corresponding to each piece of data to be processed, determining a label with the same user attribute as the at least one target label, as a common label; based on the common label and the corresponding objective function of the common label, determining the data value to be filtered in the objective function; based on the data value to be filtered and a preset data threshold, determining the common data value that is the same as the preset data threshold and the common function corresponding to the common data value; merging the common label and the common function to determine at least one merging rule.
[0048] In this context, if two target labels share the same user attribute, they are denoted as common labels. The data values to be filtered can be data selected from the data to be processed based on the objective function. The preset data threshold can be a standard value corresponding to the data to be filtered, defined according to actual needs. Common data values can be data in the data to be filtered that are identical to the preset data threshold. The common function can be a function selected from the objective function that corresponds to the common data values. The merging rule is a rule composed of at least one common label and a common function.
[0049] Specifically, after obtaining at least one target label and corresponding objective function for each piece of data to be processed, labels with the same user attributes, i.e., common labels, can be determined from among the at least one target label. Then, based on the objective function corresponding to the common label, it is determined whether the data values to be filtered corresponding to the objective function are consistent with a preset data threshold. If they are consistent, these data values to be filtered are taken as common data values. Further, the function corresponding to the common data value, i.e., the common function, is determined from the objective function. The common function and common label are then merged according to actual needs to obtain at least one merging rule, so that each merging rule corresponds to a risk level.
[0050] It should also be noted that after determining the common labels, a suitable function can be selected from the objective function corresponding to the common labels as the common function, so as to determine the merging rules based on the common labels and the common function.
[0051] For example, if the target tags for the first piece of data to be processed can include: user category, education level, and whether an account on the first app is active, the objective function could be: User category = non-student user; Education level = Bachelor's degree; Whether an account on the first app is active = Active account on the first app. The target tags for the second piece of data to be processed can include: user category, education level, and whether an account on the second app is active, with the objective function being: User category = non-student user; Education level = Bachelor's degree; Whether an account on the second app is active = Active account on the second app. The target tags for the third piece of data to be processed are user category, education level, and user age, with the objective function being: User category = non-student user; Education level = Bachelor's degree; Age > 18 years old. Based on these multiple pieces of data to be processed, the common tags are determined to be: user category and education level. The common functions under these common tags are: User category = non-student user and Education level = Bachelor's degree. These two common functions can then be used as the merging rule, i.e., Merging rule A: (User category = non-student user) and (Education level = Bachelor's degree).
[0052] For example, if the target labels for the fourth piece of data to be processed are user category, education level, user age, and the location of the user's mobile phone number, the corresponding objective functions are: User category = non-student user; Education level = Bachelor's degree; Age > 18 years old; Location of user's mobile phone number = Province A. If the target labels for the fifth piece of data to be processed are also user category, education level, user age, and the location of the user's mobile phone number, the corresponding objective functions are: User category = non-student user; Education level = Bachelor's degree; Age > 18 years old; Location of user's mobile phone number = Province B. Accordingly, based on the fourth and fifth pieces of data to be processed, the common labels can be determined as: user category, education level, user age, and location of the user's mobile phone number. The common functions under these common labels are: User category = non-student user, Education level = Bachelor's degree, and Age > 18 years old. These three common functions can then be used as the merging rule, i.e., Merging Rule B: (User category = non-student user) and (Education level = Bachelor's degree) and (Age > 18 years old).
[0053] S140. For at least one merging rule, at least one user is filtered according to the current merging rule to obtain a target user set under the risk level corresponding to the current merging rule, so as to obtain a target user set under different risk levels.
[0054] The target user set can be the set of users corresponding to each risk level, determined according to the merging rules. The risk level can be the degree of risk a user may pose. For example, risk levels can include: low risk, medium risk, high risk, etc., but this embodiment does not impose such limitations.
[0055] Specifically, the merging rules corresponding to each risk level are determined, and the data to be processed for at least one user is processed according to at least one merging rule to obtain the target user set corresponding to each risk level.
[0056] Furthermore, upon receiving new business requests related to risk levels, the risk level of the corresponding user can be determined using at least one merging rule, based on the user data and operational behavior data associated with that business. This allows for tiered filtering of users, achieving the effect of segmented operations for different user groups.
[0057] It should be noted that after obtaining the merging rules, the merging rules can be associated with other level judgments so that when other business requests for level filtering of users are received, at least one merging rule can be used to perform level filtering of users, thereby realizing tiered operation of users of different levels.
[0058] For example, after processing a new business request based on merging rules, the rule corresponding to the business request can be rule X = merge rule A and merge rule B, or rule Y = merge rule A or merge rule B. Therefore, based on the determined rules X and Y corresponding to the business request, the data of the corresponding user is evaluated to obtain the first-level target user set corresponding to rule X and the second-level target user set corresponding to rule Y.
[0059] It should be noted that if the content of merge rule A needs to be changed, only the content of merge rule A needs to be changed. There is no need to update multiple places for nested merge rule A rules X and Y, so as to save data processing time.
[0060] The technical solution of this embodiment obtains operation behavior data and user data of at least one user on the target program, and uses the operation behavior data and user data as data to be processed; determines the user attribute tags of at least one user corresponding to each piece of data to be processed and the objective function corresponding to the user attribute tags, and uses the user attribute tags as target tags; determines at least one merging rule based on at least one target tag and corresponding objective function corresponding to each piece of data to be processed, wherein the merging rule is a rule corresponding to the risk level; for at least one merging rule, at least one user is filtered according to the current merging rule to obtain the target user set under the risk level corresponding to the current merging rule, so as to obtain the target user set under different risk levels. This realizes the use of merging rules for data processing, thereby determining the target user set under each risk level, achieving the purpose of fine filtering of at least one user, solving the problem of complex and time-consuming rule configuration, and improving the efficiency of data processing.
[0061] Example 2
[0062] Figure 2 This is a flowchart of a data processing method provided in an embodiment of the present invention. Based on the above embodiments, after determining the merging rules, it is also necessary to determine the mapping relationship between the merging rules and the data to be called, so as to determine the target data to be called based on the mapping relationship, thereby obtaining the target user set under different risk levels. For specific implementation details, please refer to the technical solution of this embodiment. Technical terms that are the same as or corresponding to those in the above embodiments will not be repeated here. Figure 2 As shown, the method includes:
[0063] S210. Obtain at least one user's operation behavior data and user data on the target program, and treat the operation behavior data and user data as data to be processed.
[0064] S220. Determine the user attribute label of at least one user corresponding to each piece of data to be processed and the objective function corresponding to the user attribute label, and use the user attribute label as the objective label.
[0065] S230. Based on at least one target label and corresponding objective function corresponding to each data to be processed, determine at least one merging rule, wherein the merging rule is a rule corresponding to the risk level.
[0066] S240. Determine and store the data to be invoked corresponding to at least one merge rule.
[0067] The data to be retrieved can be user attribute data stored in a database.
[0068] Specifically, after obtaining the merging rules, the user attribute data that needs to be judged can be used as the data to be retrieved. Simultaneously, the data to be retrieved is stored in the appropriate location. That is, using the data to be retrieved and the merging rules, the risk level of relevant users can be determined, thereby achieving the purpose of tiered filtering of users. The location of the data to be retrieved can be determined according to actual needs; this embodiment does not impose any restrictions on this.
[0069] S250. Establish a mapping relationship between the merging rules and the storage location of the corresponding data to be called, so as to call the corresponding target data based on the mapping relationship.
[0070] The storage location can be determined based on actual needs, representing the corresponding location of the data to be retrieved. The mapping relationship can be the correspondence between the merging rules and the storage locations of the data to be retrieved. The target data can be understood as the data selected from at least one piece of data to be retrieved based on the mapping relationship and the merging rules.
[0071] Specifically, after determining the merging rules, a mapping relationship can be established based on the merging rules and the storage locations of the data to be retrieved. This mapping relationship characterizes the correspondence between the merging rules and their respective storage locations. Based on this, it becomes convenient to subsequently retrieve the data to be retrieved related to the merging rules, i.e., the target data, according to the mapping relationship.
[0072] S260. Upon receiving a business processing request, the business processing request is parsed and processed to determine at least one common tag corresponding to the business processing request, and the common tag is used as the tag to be invoked.
[0073] In this embodiment of the invention, the business processing request can be a request for processing the current business. The tag to be invoked can be a tag determined from common tags and associated with the business processing request.
[0074] Specifically, after relevant business personnel trigger the corresponding button to issue a business processing request, the corresponding server can receive the request. The server then parses and processes the request, identifying the tag to be invoked from at least one common tag. For example, upon receiving the request, the server analyzes it and determines that the corresponding tags to be invoked are tag 1, tag 2, and tag 3.
[0075] S270. Determine the call merging rule based on at least one callable tag.
[0076] In this embodiment of the invention, the merging rule to be invoked can be a merging rule determined based on at least one tag to be invoked.
[0077] Specifically, after identifying at least one tag to be invoked, at least one corresponding merging rule can be determined based on the tag to be invoked and the corresponding objective function, which is the merging rule to be invoked.
[0078] It should be noted that the rules corresponding to business requests are associated with risk levels, and the rules corresponding to business requests may include at least one rule to be merged.
[0079] For example, referring to the above example, after determining that the tags to be invoked are tag 1, tag 2, and tag 3, the corresponding invocation merging rules are determined according to the objective functions corresponding to the tags to be invoked. The invocation merging rules are: Invocation merging rule 1: (tag 1 > 18 years old) and (tag 2 = Province A) and (tag 3 < 0). Invocation merging rule 2: tag 1 < 30 years old.
[0080] S280. Determine the target storage location of the data to be called corresponding to the merging rule to be called based on the mapping relationship, so as to retrieve the target data to be called from the target storage location.
[0081] In this embodiment of the invention, the target storage location may be the storage location of the data to be invoked corresponding to the merging rule to be invoked. The target invocation data may be data selected from at least one piece of data to be invoked based on the mapping relationship and the business processing request.
[0082] Specifically, based on the established mapping relationship between the merging rules and the storage locations of the data to be retrieved, the target storage location of the data to be retrieved corresponding to the merging rule is determined. Then, the target data to be retrieved is determined from the data to be investigated stored at the target storage location.
[0083] For example, based on the above example, the corresponding data of tags 1, 2, and 3 in the following merge rule 1 to be invoked is determined according to the mapping relationship: (tag 1 > 18 years old) and (tag 2 = province A) and (tag 3 < 0), which is the target invoked data. For example, if tag 1 represents the user's age, then the target invoked data could be the current user's actual age.
[0084] S290. Based on the target call data, at least one user corresponding to the business processing request is filtered to obtain a set of target users under different risk levels.
[0085] Specifically, after determining the target call data, it is input into the rule corresponding to the business request to obtain the result of that rule, thereby determining whether the target call data meets the rule. If it does, the risk level corresponding to the user is determined according to the correspondence between the rule and the risk level, thus obtaining the risk level corresponding to each user, and thus obtaining the target user set under different risk levels.
[0086] Optionally, it also includes: determining unfiltered labels based on the labels in the merge rules to be invoked and at least one label to be invoked; removing some data based on the unfiltered labels and the labels corresponding to the target invoked data to obtain data to be filtered again; determining target data from the data to be filtered again based on the objective function in at least one label to be invoked; and determining the risk level corresponding to at least one user based on the target data to obtain a set of target users under different risk levels.
[0087] In this embodiment of the invention, the unfiltered label may be a duplicate label in at least one merge rule to be invoked. The partial data may be data in the target invoked data corresponding to a label that matches the unfiltered label. The data to be filtered again may be data obtained after removing a portion of the data from the target invoked data.
[0088] Specifically, a business processing request may correspond to at least one rule to be invoked and merged. Duplicate tags may exist within these rules. Therefore, duplicate tags (i.e., unfiltered tags) can be identified by comparing the tags in the rules with at least one rule to be invoked. After identifying unfiltered tags, they are compared with tags in the target data, thus removing the data corresponding to tags that match the unfiltered tags to obtain data for further filtering. Further, the data required for the target function is determined from the data to be filtered again based on the target function in at least one rule to be invoked; this is the target data. After obtaining the target data, the result of the rule corresponding to the business processing request can be calculated using relevant expressions to determine whether the current user meets the rule. If so, the target user at different risk levels can be determined based on the correspondence between the rule and risk levels, thus achieving stratified filtering of user groups.
[0089] For example, referring to the above example, a business processing request can correspond to two rules to be merged. Based on these two rules, the rule corresponding to the business processing request is determined, such as: the rule is: rule to be merged 1 and rule to be merged 2. Correspondingly, the rule is: ((Label 1 > 18 years old) and (Label 2 = Province A) and (Label 3 < 0)) and (Label 1 < 30 years old). Then, in at least one rule to be merged, i.e., the rule corresponding to the business processing request, the labels include: label 1, label 2, label 3, and label 1. The labels to be merged are label 1, label 2, and label 3. Therefore, label 1 is an unfiltered label. Data corresponding to duplicate labels 1 in the target call data can be removed based on the unfiltered labels to obtain data to be filtered again. Thus, the target data is determined from the data to be filtered again based on the target function in at least one label to be merged. According to the example, the target data obtained at this time is the data corresponding to labels 1, 2, and 3. When obtaining the target data, asynchronous concurrent processing can be used, simultaneously querying the data corresponding to labels 1, 2, and 3. Correspondingly, the final processing time depends on the longest time taken to acquire the data corresponding to tag 1, tag 2, and tag 3 in parallel. Furthermore, after obtaining the target data, the aviator expression can be used to calculate the result of the rule corresponding to the business processing request, to determine whether the current user meets the rule. If so, the target users under different risk levels can be determined based on the correspondence between the rule and the risk level, thus achieving stratified filtering of user groups.
[0090] It should be noted that aviator is an expression engine used to execute and parse mathematical and logical expressions.
[0091] The technical solution of this embodiment, after determining the merging rules, identifies and stores the data to be invoked corresponding to at least one merging rule; and establishes a mapping relationship between the merging rules and the storage locations of the corresponding data to be invoked, so as to invoke the corresponding target data based on the mapping relationship. Thus, when a business processing request is received, the business processing request is parsed and processed to determine at least one common tag corresponding to the business processing request, and this common tag is used as the tag to be invoked; based on at least one tag to be invoked, the merging rule to be invoked is determined; based on the mapping relationship, the target storage location of the data to be invoked corresponding to the merging rule to be invoked is determined, so as to retrieve the target invoked data from the target storage location; and based on the target invoked data, at least one user corresponding to the business processing request is filtered to obtain a target user set under different risk levels. By determining the merging rules to be invoked, the redundant configuration of rules can be reduced, and data processing can be conveniently performed using at least one merging rule to be invoked, solving the problem of complex and time-consuming rule configuration and improving the efficiency of data processing.
[0092] Example 3
[0093] Figure 3 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present invention. Figure 3 As shown, the device includes: a data acquisition module 310, a tag and function determination module 320, a merging rule determination module 330, and a target user set determination module 340.
[0094] The data acquisition module 310 is used to acquire at least one user's operation behavior data and user data on the target program, and use the operation behavior data and user data as data to be processed; the label and function determination module 320 is used to determine the user attribute label and the target function corresponding to the user attribute label for each piece of data to be processed, and use the user attribute label as the target label; the merging rule determination module 330 is used to determine at least one merging rule based on at least one target label and the corresponding target function for each piece of data to be processed, wherein the merging rule is a rule corresponding to the risk level; the target user set determination module 340 is used to filter at least one user according to the current merging rule for at least one merging rule, to obtain the target user set under the risk level corresponding to the current merging rule, so as to obtain the target user set under different risk levels.
[0095] The technical solution of this embodiment obtains operation behavior data and user data of at least one user on the target program, and uses the operation behavior data and user data as data to be processed; determines the user attribute tags of at least one user corresponding to each piece of data to be processed and the objective function corresponding to the user attribute tags, and uses the user attribute tags as target tags; determines at least one merging rule based on at least one target tag and corresponding objective function corresponding to each piece of data to be processed, wherein the merging rule is a rule corresponding to the risk level; for at least one merging rule, at least one user is filtered according to the current merging rule to obtain the target user set under the risk level corresponding to the current merging rule, so as to obtain the target user set under different risk levels. This realizes the use of merging rules for data processing, thereby determining the target user set under each risk level, achieving the purpose of fine filtering of at least one user, solving the problem of complex and time-consuming rule configuration, and improving the efficiency of data processing.
[0096] Based on the above embodiments, the data acquisition module includes: a related data determination unit, which retrieves related data corresponding to at least one pending business based on the target program, wherein the related data includes at least one of operation behavior data and user data, and the pending business is a business related to the risk level; and a data cleaning unit, which cleans the related data to determine the pending data.
[0097] Optionally, the tag and function determination module includes: a preset tag and preset function determination unit, used to determine at least one preset tag and a preset function corresponding to the preset tag based on at least one business to be processed, wherein the preset tag is a pre-set user attribute tag; and a target tag and target function determination unit, used to determine at least one preset tag and a preset function corresponding to the data to be processed for each piece of data to be processed, and use them as the target tag and target function.
[0098] Optionally, the merging rule determination module includes: a common label determination unit, used to determine, based on at least one target label corresponding to each piece of data to be processed, a label that has the same user attribute as at least one target label, as a common label; a data value to be filtered unit, used to determine the data value to be filtered corresponding to the target function based on the common label and the target function corresponding to the common label; a common function determination unit, used to determine the common data value that is the same as the preset data threshold and the common function corresponding to the common data value based on the data value to be filtered and the preset data threshold; and a merging rule determination unit, used to merge the common label and the common function to determine at least one merging rule.
[0099] Optionally, the device further includes: a mapping relationship determination module, which is used to determine and store the data to be called corresponding to at least one merging rule; and to establish a mapping relationship between the merging rule and the storage location of the corresponding data to be called, so as to call the corresponding target data based on the mapping relationship.
[0100] Optionally, the device further includes a data processing module, comprising: a tag determination unit, configured to parse and process a business processing request upon receiving it, determine at least one common tag corresponding to the business processing request, and use the common tag as the tag to be called; a merging rule determination unit, configured to determine a merging rule based on at least one tag to be called; a target storage location determination unit, configured to determine the target storage location of the data to be called corresponding to the merging rule based on a mapping relationship, so as to retrieve the target data to be called from the target storage location; and a user filtering unit, configured to filter at least one user corresponding to the business processing request based on the target data to obtain a target user set under different risk levels.
[0101] Optionally, the device further includes a risk level determination module, which includes: an unfiltered label determination unit, used to determine unfiltered labels based on the labels in the merge rule to be invoked and at least one label to be invoked; a data to be re-filtered determination unit, used to remove some data based on the unfiltered labels and the labels corresponding to the target invoked data to obtain data to be re-filtered; a target data determination unit, used to determine target data from the data to be re-filtered based on the objective function in at least one label to be invoked; and a risk level determination unit, used to determine the risk level corresponding to at least one user based on the target data to obtain a target user set under different risk levels.
[0102] The data processing apparatus provided in the embodiments of the present invention can execute the data processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.
[0103] Example 4
[0104] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.
[0105] like Figure 4 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0106] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0107] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as data processing methods.
[0108] In some embodiments, the data processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the data processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the data processing method by any other suitable means (e.g., by means of firmware).
[0109] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0110] Computer programs for implementing the data processing methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0111] Example 5
[0112] This invention also provides a computer-readable storage medium storing computer instructions for causing a processor to execute a data processing method, the method comprising:
[0113] Acquire at least one user's operational behavior data and user data on the target program, and treat the operational behavior data and user data as data to be processed; determine the user attribute labels and the objective functions corresponding to at least one user for each piece of data to be processed, and treat the user attribute labels as target labels; based on at least one target label and the corresponding objective function for each piece of data to be processed, determine at least one merging rule, wherein the merging rule is a rule corresponding to the risk level; for at least one merging rule, perform screening processing on at least one user according to the current merging rule to obtain the target user set under the risk level corresponding to the current merging rule, so as to obtain the target user set under different risk levels.
[0114] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0115] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0116] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.
[0117] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.
[0118] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.
[0119] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.
Claims
1. A data processing method, characterized in that, include: Acquire at least one user's operational behavior data and user data on the target program, and treat the operational behavior data and user data as data to be processed; Determine the user attribute labels of at least one user corresponding to each piece of data to be processed, as well as the objective function corresponding to the user attribute labels, and use the user attribute labels as the objective labels; Based on at least one target label and a corresponding objective function corresponding to each of the data to be processed, at least one merging rule is determined, wherein the merging rule is a rule corresponding to the risk level; For the at least one merging rule, the at least one user is filtered according to the current merging rule to obtain a target user set under the risk level corresponding to the current merging rule, so as to obtain a target user set under different risk levels; The step of determining at least one merging rule based on at least one target label and a corresponding objective function for each of the data to be processed includes: Based on at least one target tag corresponding to each piece of data to be processed, tags with the same user attributes as the at least one target tag are determined as common tags; based on the common tags and the corresponding objective functions, the data values to be filtered in the objective functions are determined; based on the data values to be filtered and a preset data threshold, common data values that are the same as the preset data threshold and common functions corresponding to the common data values are determined; the common tags and the common functions are merged to determine the at least one merging rule.
2. The method according to claim 1, characterized in that, The step of acquiring at least one user's operational behavior data and user data on the target program, and treating the operational behavior data and user data as data to be processed, includes: Based on the target program, at least one related data corresponding to a pending business is retrieved, wherein the related data includes at least one of the operation behavior data and the user data, and the pending business is a business related to the risk level. The associated data is cleaned and processed to determine the data to be processed.
3. The method according to claim 1, characterized in that, The step of determining the user attribute label of at least one user corresponding to each piece of data to be processed and the objective function corresponding to the user attribute label, and using the user attribute label as the objective label, includes: Based on at least one pending service, at least one preset tag and a preset function corresponding to the preset tag are determined, wherein the preset tag is a pre-set user attribute tag; For each piece of data to be processed, at least one preset label corresponding to the data to be processed and a preset function corresponding to the preset label are determined, and these are used as the target label and the target function.
4. The method according to claim 1, characterized in that, Also includes: Determine and store the data to be invoked corresponding to the at least one merging rule; Establish a mapping relationship between the merging rules and the storage location of the corresponding data to be called, so as to call the corresponding target data based on the mapping relationship.
5. The method according to claim 4, characterized in that, Also includes: Upon receiving a business processing request, the business processing request is parsed and processed to determine at least one common tag corresponding to the business processing request, and the common tag is used as the tag to be invoked. Based on at least one of the tags to be invoked, determine the rules for merging the calls; Based on the mapping relationship, determine the target storage location of the data to be called corresponding to the merging rule to be called, so as to retrieve the target data to be called from the target storage location; Based on the target call data, at least one user corresponding to the business processing request is filtered to obtain a set of target users under different risk levels.
6. The method according to claim 5, characterized in that, Also includes: Based on the tags in the merge rule to be invoked and at least one of the tags to be invoked, determine the unfiltered tags; Based on the unfiltered tags and the tags corresponding to the target call data, some data is removed to obtain data to be filtered again; Target data is determined from the data to be filtered again based on at least one of the target functions in the tag to be invoked; Based on the target data, the risk level corresponding to the at least one user is determined to obtain a target user set under different risk levels.
7. A data processing apparatus, characterized in that, include: The data acquisition module is used to acquire at least one user's operation behavior data and user data on the target program, and to treat the operation behavior data and user data as data to be processed. The tag and function determination module is used to determine the user attribute tag of at least one user corresponding to each piece of data to be processed and the target function corresponding to the user attribute tag, and to use the user attribute tag as the target tag; The merging rule determination module is used to determine at least one merging rule based on at least one target label and a corresponding objective function for each of the data to be processed, wherein the merging rule is a rule corresponding to the risk level; The target user set determination module is used to filter the at least one user according to the current merging rule for the at least one merging rule, so as to obtain the target user set under the risk level corresponding to the current merging rule, so as to obtain the target user set under different risk levels. The merging rule determination module includes: a common tag determination unit, used to determine tags with the same user attributes as the at least one target tag corresponding to each piece of data to be processed, as common tags; a data value to be filtered unit, used to determine the data value to be filtered corresponding to the target function based on the common tags and the target function corresponding to the common tags; a common function determination unit, used to determine common data values that are the same as the preset data threshold and common functions corresponding to the common data values based on the data values to be filtered and a preset data threshold; and a merging rule determination unit, used to perform merging processing on the common tags and the common functions to determine the at least one merging rule.
8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data processing method according to any one of claims 1-6.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the data processing method according to any one of claims 1-6.
Citation Information
Patent Citations
User operation management method and device
CN113762994A
Payment method, apparatus, computer device and storage medium of vending machine
SG11201806277PA
