User determination methods, devices, equipment, and computer storage media

Abstract

This application discloses a method, apparatus, device, and computer storage medium for user identification, relating to the field of big data technology. The method includes: acquiring transaction request information, the transaction request information including at least one first field name, a field value of the first field name, a channel number, and a transaction code; using the channel number and transaction code, acquiring control rules from a control rule base corresponding to a list identifier; and, if the first field name and its corresponding field value satisfy the control rules, determining the user corresponding to the transaction request information as a target user. Thus, by acquiring the first control rule based on the channel number and transaction code in the transaction request information, and if the field name and its corresponding field value in the transaction request information satisfy the first control rule, the user corresponding to the transaction request information is determined as a target user, thereby identifying test users for newly launched functional modules of the transaction system.

Description

Technical Field

[0001] This application belongs to the field of big data technology, and in particular relates to a method, apparatus, device and computer storage medium for determining users. Background Technology

[0002] As society develops, the division of labor within organizations becomes increasingly complex, and business development accelerates. To keep pace with the times, transaction systems often need to launch new functional modules ahead of schedule or urgently. However, these prematurely launched or urgently deployed functional modules may have some defects, requiring test users to test them. To determine whether defects exist in a functional module, test users need to be identified and try out the functional module to discover any potential flaws. Summary of the Invention

[0003] This application provides a method, apparatus, device, and computer storage medium for determining users, which can identify test users for newly launched functional modules of a trading system.

[0004] In a first aspect, embodiments of this application provide a method for determining a user, the method comprising:

[0005] Obtain transaction request information, which includes at least one first field name, the field value of the first field name, the channel number, and the transaction code;

[0006] Use the channel number and transaction code to obtain the control rules in the control rule base corresponding to the list identifier;

[0007] If the first field name and its value satisfy the control rules, the user corresponding to the transaction request information is determined to be the target user.

[0008] The control rule base includes multiple second field names, field values ​​for each second field name, and a range of first field values; the control rules include:

[0009] Multiple second field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding second field name;

[0010] Multiple second field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding second field name;

[0011] Multiple second field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding second field name;

[0012] Multiple second field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding second field name;

[0013] Multiple second field names include at least one first field name, and the field value of each first field name is within the range of first field values;

[0014] Multiple second field names include at least one first field name, and the field value of each second field name includes the field value of the corresponding first field name.

[0015] In one possible implementation, the list identifier includes a first list identifier, the control rule base includes a first control rule base corresponding to the first list identifier, the first control rule base includes multiple third field names, the field value of each third field name and the range of second field values; the second field name includes the third field name;

[0016] The control rules include:

[0017] Multiple third field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding third field name;

[0018] Multiple third field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding third field name;

[0019] Multiple third field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding third field name;

[0020] Multiple third field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding third field name;

[0021] Multiple third field names include at least one first field name, and the field value of each first field name is within the range of second field values;

[0022] Multiple third field names include at least one first field name, and the field value of each third field name includes the field value of the corresponding first field name.

[0023] In one possible implementation, the list identifier includes a second list identifier, the control rule base includes a second control rule base corresponding to the second list identifier, and the second control rule base includes multiple fourth field names, field values ​​for each fourth field name, and a range of third field values; the second field name includes the fourth field name;

[0024] The control rules include:

[0025] Multiple fourth field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding fourth field name;

[0026] Multiple fourth field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding fourth field name;

[0027] Multiple fourth field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding fourth field name;

[0028] Multiple fourth field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding fourth field name;

[0029] Multiple fourth field names include at least one first field name, and the field value of each first field name is within the range of third field values;

[0030] Multiple fourth field names include at least one first field name, and the field value of each fourth field name includes the field value of the corresponding first field name.

[0031] In one possible implementation embodiment, it further includes:

[0032] If the first field name and the corresponding field value do not meet the control rules, the transaction request information is intercepted.

[0033] In one possible implementation, before retrieving the control rules from the control rule base corresponding to the list identifier using the channel number and transaction code, the method further includes:

[0034] In the absence of control rules, the user corresponding to the transaction request information is identified as the target user.

[0035] Secondly, embodiments of this application provide a user determination device, including:

[0036] The acquisition module is used to acquire transaction request information, which includes at least one first field name, the field value of the first field name, the channel number, and the transaction code.

[0037] The acquisition module is also used to obtain the control rules in the control rule library corresponding to the list flag using the channel number and transaction code;

[0038] The determination module is used to determine the user corresponding to the transaction request information as the target user if the first field name and the field value of the first field name meet the control rules.

[0039] The control rule base includes multiple second field names, field values ​​for each second field name, and a range of first field values; the control rules include:

[0040] Multiple second field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding second field name;

[0041] Multiple second field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding second field name;

[0042] Multiple second field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding second field name;

[0043] Multiple second field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding second field name;

[0044] Multiple second field names include at least one first field name, and the field value of each first field name is within the range of first field values;

[0045] Multiple second field names include at least one first field name, and the field value of each second field name includes the field value of the corresponding first field name.

[0046] In one possible implementation, the list identifier includes a first list identifier, the control rule base includes a first control rule base corresponding to the first list identifier, the first control rule base includes multiple third field names, the field value of each third field name and the range of second field values; the second field name includes the third field name;

[0047] The control rules include:

[0048] Multiple third field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding third field name;

[0049] Multiple third field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding third field name;

[0050] Multiple third field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding third field name;

[0051] Multiple third field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding third field name;

[0052] Multiple third field names include at least one first field name, and the field value of each first field name is within the range of second field values;

[0053] Multiple third field names include at least one first field name, and the field value of each third field name includes the field value of the corresponding first field name.

[0054] In one possible implementation, the list identifier includes a second list identifier, the control rule base includes a second control rule base corresponding to the second list identifier, and the second control rule base includes multiple fourth field names, field values ​​for each fourth field name, and a range of third field values; the second field name includes the fourth field name;

[0055] The control rules include:

[0056] Multiple fourth field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding fourth field name;

[0057] Multiple fourth field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding fourth field name;

[0058] Multiple fourth field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding fourth field name;

[0059] Multiple fourth field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding fourth field name;

[0060] Multiple fourth field names include at least one first field name, and the field value of each first field name is within the range of third field values;

[0061] Multiple fourth field names include at least one first field name, and the field value of each fourth field name includes the field value of the corresponding first field name.

[0062] In one possible implementation embodiment, it further includes:

[0063] The interception module is used to intercept transaction request information when the first field name and the field value corresponding to the first field name do not meet the control rules.

[0064] In one possible implementation, the apparatus further includes:

[0065] The determination module is also used to determine the user corresponding to the transaction request information as the target user in the absence of control rules, before obtaining the control rules in the control rule base corresponding to the list identifier using the channel number and transaction code.

[0066] Thirdly, embodiments of this application provide an electronic device, the device comprising:

[0067] Processor and memory storing computer program instructions;

[0068] The method determined by the user when the processor executes computer program instructions to implement any of the above.

[0069] Fourthly, embodiments of this application provide a computer storage medium on which computer program instructions are stored, and a method for determining a user that implements any of the above-mentioned methods when the computer program instructions are executed by a processor.

[0070] Fifthly, embodiments of this application provide a computer program product, characterized in that, when the instructions in the computer program product are executed by the processor of an electronic device, the electronic device is able to execute any of the above-mentioned user determination methods.

[0071] This application discloses a user determination method, apparatus, device, and computer storage medium. The method includes: acquiring transaction request information, which includes at least one first field name, a field value of the first field name, a channel number, and a transaction code; using the channel number and transaction code, acquiring control rules from a control rule base corresponding to a list identifier; and determining the user corresponding to the transaction request information as a target user if the first field name and its corresponding field value satisfy the control rules. Thus, by acquiring control rules based on the channel number and transaction code in the transaction request information, and determining the user corresponding to the transaction request information as a target user if the field name and its corresponding field value satisfy the control rules, the method further identifies test users for newly launched functional modules in the transaction system. Attached Figure Description

[0072] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0073] Figure 1 This is a flowchart illustrating a user determination method provided in one embodiment of this application;

[0074] Figure 2 This is a flowchart illustrating a user determination method provided in another embodiment of this application;

[0075] Figure 3 This is a schematic diagram of the structure of a user determination device provided in another embodiment of this application;

[0076] Figure 4 This is a schematic diagram of the structure of an electronic device provided in another embodiment of this application. Detailed Implementation

[0077] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0078] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0079] It should be noted that the acquisition, storage, use, and processing of data in this application embodiment all comply with the relevant provisions of national laws and regulations.

[0080] As society develops, the division of labor within organizations becomes increasingly complex, and business development accelerates. To keep pace with the times, transaction systems often need to launch new functional modules ahead of schedule or urgently. However, these prematurely launched or urgently deployed functional modules may have some defects, requiring test users to test them. To determine whether defects exist in a functional module, test users need to be identified and try out the functional module to discover any potential flaws.

[0081] To address the problems of the prior art, embodiments of this application provide a method, apparatus, device, and computer storage medium for determining a user. The method for determining a user provided in this application embodiment will be described first below.

[0082] Figure 1 A flowchart illustrating a user determination method provided in one embodiment of this application is shown.

[0083] like Figure 1 As shown in the embodiments of this application, the method for determining users includes the following steps.

[0084] S110. Obtain transaction request information, which includes at least one first field name, the field value of the first field name, the channel number, and the transaction code.

[0085] In some embodiments, the transaction request information can be a transaction request sent by a user through a front-end system, and the transaction system can receive the transaction request information sent by the front-end system. Different channel numbers indicate that the request was sent through different front-end systems, with one channel number corresponding to one front-end system. A transaction request includes a transaction code, and the transaction code is different in different transaction request messages. The transaction code is the encoding of the smallest service unit provided by the transaction system for front-end system access.

[0086] In some embodiments, the format of the transaction request information may include, but is not limited to, JSON or XML formats.

[0087] In some embodiments, the channel number and transaction code can be in the request header of the transaction request information.

[0088] As an example, field names may include, but are not limited to, field names related to user ID, organization code, user type, and user behavior information.

[0089] S120. Using the channel number and transaction code, obtain the control rules in the control rule base corresponding to the list identifier.

[0090] In some embodiments, the control rule base stores the control rules corresponding to the channel number and transaction code. The channel number and transaction code are combined with the list flag to determine whether the corresponding control rule exists. If it exists, the corresponding control rule is obtained.

[0091] Here, the control rule base includes field names that match the first field name and the corresponding field values. Control rules may also include ranges of field values.

[0092] S130. If the first field name and the field value of the first field name satisfy the control rules, determine the user corresponding to the transaction request information as the target user.

[0093] The control rule base includes multiple second field names, field values ​​for each second field name, and a range of first field values; the control rules include:

[0094] Multiple second field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding second field name;

[0095] Multiple second field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding second field name;

[0096] Multiple second field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding second field name;

[0097] Multiple second field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding second field name;

[0098] Multiple second field names include at least one first field name, and the field value of each first field name is within the range of first field values;

[0099] Multiple second field names include at least one first field name, and the field value of each second field name includes the field value of the corresponding first field name.

[0100] In some embodiments, a first field name is compared with field names in a control rule base. If the first field name matches the field name in the control rule base, the field value of the first field name is compared with the field value of the corresponding field name in the control rule base, or the field value of the first field name is compared with a range of field values ​​to obtain a comparison result. If the comparison result satisfies the control rules, the user corresponding to the transaction request information is determined to be the target user.

[0101] In some embodiments, the channel number and transaction code are combined with the list identifier to determine whether a corresponding control rule exists. If it exists, the corresponding control rule is obtained.

[0102] In some embodiments, the control rule base includes basic rules such as "AND", "OR", "NOT", "fuzzy matching", and "boundary value", and different rules can be used in combination.

[0103] In some embodiments, the "AND" rule indicates that all field values ​​corresponding to the first field names match the field values ​​of the corresponding second field names, i.e., multiple second field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding second field name. The "OR" rule indicates that the field value of one of the at least one first field name matches the field value of the corresponding second field name, i.e., multiple second field names include at least one first field name, and the field value of one of the at least one first field name matches the field value of the corresponding second field name; alternatively, the "OR" rule may also indicate that the field value of a first field name matches the field value of one of the field values ​​of the corresponding second field name. The "NOT" rule indicates that the field value of a first field name does not match the field value of the corresponding second field name, i.e., multiple second field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding second field name. The "fuzzy matching" rule represents a fuzzy match between the field value of a first field name and the field value of a corresponding second field name. That is, multiple second field names include at least one first field name, and the field value of each second field name includes the field value of the corresponding first field name. In other words, the field value of the first field name can match the field value at the end of the corresponding second field name's field value, the field value of the first field name can match the field value at the beginning of the corresponding second field name's field value, and the field value of the first field name can match the field value in the middle of the corresponding second field name's field value. The "boundary value" rule corresponds to numeric field values ​​and represents the range of values ​​for the field value of a first field name. That is, multiple second field names include at least one first field name, and the field value of each first field name falls within the range of the first field value. Here, the range of the first field value can correspond to the field value of the second field name (if the field value of the second field name is also numeric, then they can correspond), or they can not correspond.

[0104] In this way, based on the channel number and transaction code in the transaction request information, control rules are obtained. If the field name and the corresponding field value in the transaction request information meet the control rules, the user corresponding to the transaction request information is identified as the target user, and thus the test user for the newly launched functional module of the transaction system is determined.

[0105] Based on this, in some embodiments, the list identifier includes a first list identifier, the control rule base includes a first control rule base corresponding to the first list identifier, the first control rule base includes multiple third field names, the field value of each third field name and the range of second field values; the second field name includes the third field name;

[0106] The control rules include:

[0107] Multiple third field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding third field name;

[0108] Multiple third field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding third field name;

[0109] Multiple third field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding third field name;

[0110] Multiple third field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding third field name;

[0111] Multiple third field names include at least one first field name, and the field value of each first field name is within the range of second field values;

[0112] Multiple third field names include at least one first field name, and the field value of each third field name includes the field value of the corresponding first field name.

[0113] In some embodiments, the channel number and transaction code are combined with the first list identifier to determine whether a corresponding control rule exists. If it exists, the corresponding control rule is obtained.

[0114] In some embodiments, the first control rule base includes basic rules such as "AND", "OR", "NOT", "fuzzy matching", and "boundary value", and different rules can be used in combination.

[0115] In some embodiments, the "AND" rule indicates that all field values ​​corresponding to the first field names match the field values ​​of the corresponding second field names, i.e., multiple third field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding third field name. The "OR" rule indicates that the field value of one of the at least one first field name matches the field value of the corresponding third field name, i.e., multiple third field names include at least one first field name, and the field value of one of the at least one first field name matches the field value of the corresponding third field name; alternatively, the "OR" rule can also indicate that the field value of a first field name matches the field value of one of the field values ​​of the corresponding third field name. The "NOT" rule indicates that the field value of a first field name does not match the field value of the corresponding third field name, i.e., multiple third field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding third field name. The "fuzzy matching" rule represents a fuzzy match between the field value of the first field name and the field value of the corresponding third field name. That is, multiple third field names include at least one first field name, and the field value of each third field name includes the field value of the corresponding first field name. In other words, the field value of the first field name can match the field value at the end of the corresponding third field name's field value, the field value of the first field name can match the field value at the beginning of the corresponding third field name's field value, and the field value of the first field name can also match the field value in the middle of the corresponding third field name's field value. The "boundary value" rule corresponds to numeric field values ​​and represents the range of values ​​for the first field name's field value. That is, multiple third field names include at least one first field name, and the field value of each first field name is within the range of the second field value. Here, the range of the second field value can correspond to the field value of the third field name (if the field value of the third field name is also numeric, then they can correspond), or they can not correspond. The range of the first field value can be the range of the second field value.

[0116] As an example, if the transaction request information includes two first field names, and the field value of the first field name X is aaa and the field value of the first field name Y is bbb, then the control rule is satisfied if the field value of the third field name X is aaa and the field value of the third field name Y is bbb.

[0117] If the value of the first field name X is aaa and the value of the first field name Y is bbb, then the control rule is satisfied if the value of the third field name X is aaa or the value of the third field name Y is bbb.

[0118] If the value of the first field name X is aaa and the value of the first field name Y is ccc, then the control rule is satisfied if the value of the third field name X is aaa or the value of the third field name Y is bbb.

[0119] If the value of the first field name X is aaa and the value of the first field name Y is bbb, then the control rule is satisfied if the value of the third field name X is not aaa.

[0120] If the value of the first field name X is aaa, the value of the first field name Y is ccc, and the control rule is that the value of the third field name X is aaac and the value of the third field name Y is ebbb, then the control rule is satisfied.

[0121] If the value of the first field name X is aaa and the value of the first field name Y is ccc, and the control rule is that the value of the third field name X is aaca and the value of the third field name Y is ebbb, then the control rule is satisfied.

[0122] If the value of the first field name X is 2, the value of the first field name Y is 2.5, and the control rule is that the value of the second field is in the range [1,3], then the control rule is satisfied.

[0123] In this way, by setting control rules in the first control rule base, test users can be accurately screened out.

[0124] Based on this, in some embodiments, the list identifier includes a second list identifier, the control rule base includes a second control rule base corresponding to the second list identifier, and the second control rule base includes multiple fourth field names, field values ​​for each fourth field name, and a range of third field values; the second field name includes the fourth field name;

[0125] The control rules include:

[0126] Multiple fourth field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding fourth field name;

[0127] Multiple fourth field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding fourth field name;

[0128] Multiple fourth field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding fourth field name;

[0129] Multiple fourth field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding fourth field name;

[0130] Multiple fourth field names include at least one first field name, and the field value of each first field name is within the range of third field values;

[0131] Multiple fourth field names include at least one first field name, and the field value of each fourth field name includes the field value of the corresponding first field name.

[0132] In some embodiments, the channel number and transaction code are combined with a second list identifier to determine whether a corresponding control rule exists. If it exists, the corresponding control rule is obtained.

[0133] In some embodiments, the second control rule base includes basic rules such as "AND", "OR", "NOT", "fuzzy matching", and "boundary value", and different rules can be used in combination.

[0134] In some embodiments, the "AND" rule indicates that all field values ​​corresponding to the first field names match the field values ​​of the corresponding second field, i.e., multiple fourth field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding fourth field name. The "OR" rule indicates that the field value of one of the at least one first field name matches the field value of the corresponding fourth field name, i.e., multiple fourth field names include at least one first field name, and the field value of one of the at least one first field name matches the field value of the corresponding fourth field name; alternatively, the "OR" rule may also indicate that the field value of a first field name matches the field value of one of the field values ​​of the corresponding fourth field name. The "NOT" rule indicates that the field value of a first field name does not match the field value of the corresponding fourth field name, i.e., multiple fourth field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding fourth field name. The "fuzzy match" rule indicates that the field value of a first field name matches the field value of the corresponding fourth field name fuzzily, i.e., multiple fourth field names include at least one first field name, and the field value of each fourth field name includes the field value of the corresponding first field name. Understandably, the value of the first field name can match the field value at the end of the corresponding fourth field name's field value, the field value of the first field name can match the field value at the beginning of the corresponding fourth field name's field value, and the field value of the first field name can also match the field value in the middle of the corresponding fourth field name's field value. The "boundary value" rule corresponds to numeric field values, representing the range of values ​​for the first field name's field value; that is, multiple fourth field names include at least one first field name, and the field value of each first field name is within the range of the third field value. Here, the range of the third field value can correspond to the field value of the fourth field name (if the field value of the fourth field name is also numeric, then they can correspond), or they can not correspond. The range of the first field value can be the range of the third field value.

[0135] As an example, if the transaction request information includes two first field names, and the field value of the first field name Z is fff and the field value of the first field name M is ggg, then the control rule is satisfied if the field value of the fourth field name Z is fff and the field value of the fourth field name M is ggg.

[0136] If the value of the first field name Z is fff and the value of the first field name M is ggg, then the control rule is satisfied if the value of the fourth field name Z is fff or the value of the fourth field name M is ggg.

[0137] If the value of the first field name Z is fff, the value of the first field name M is ccc, and the control rule is that the value of the fourth field name Z is fff, or the value of the fourth field name M is ggg, then the control rule is satisfied.

[0138] If the value of the first field name Z is fff and the value of the first field name M is ggg, then the control rule is satisfied if the value of the fourth field name Z is not fff.

[0139] If the value of the first field name Z is fff, the value of the first field name M is ccc, and the control rule is that the value of the fourth field name Z is fffh and the value of the fourth field name M is mggg, then the control rule is satisfied.

[0140] If the value of the first field name Z is fff, the value of the first field name M is ccc, and the control rule is that the value of the fourth field name Z is ffhf and the value of the fourth field name M is eggg, then the control rule is satisfied.

[0141] If the value of the first field name Z is 1.5, the value of the first field name M is 2.3, and the control rule is that the value of the third field is in the range of [0,3], then the control rule is satisfied.

[0142] It should be noted that the first control rule base and the second control rule base do not affect each other, and the field names and field values ​​within them are not related.

[0143] In this way, by setting control rules in the second control rule base, test users can be accurately screened out.

[0144] Based on this, in some embodiments, the method may further include:

[0145] If the first field name and the corresponding field value do not meet the control rules, the transaction request information is intercepted.

[0146] In some embodiments, after intercepting the transaction request information, target information is sent to the front-end system that sent the transaction request information to remind the user that the transaction request information has been intercepted.

[0147] This prevents users other than test users from accessing newly launched functional modules of the trading system, and prevents problems from occurring due to a large number of users using the newly launched functional modules before they have been tested, which could lead to system paralysis or make it impossible to identify the problem; at the same time, it can also affect the user experience.

[0148] Based on this, in some embodiments, before obtaining the control rules in the control rule base corresponding to the list identifier using the channel number and transaction code, the method may further include:

[0149] In the absence of control rules, the user corresponding to the transaction request information is identified as the target user.

[0150] In some embodiments, if a user is not subject to control rule filtering, control rules for such users will not be stored in the control rule base. For example, if it is known that all the first field names and their values ​​associated with the user who sent the transaction request satisfy all control rules in the control rule base, no further control rules will be set for that user.

[0151] In some embodiments, as Figure 2 As shown, after obtaining the transaction request information, the system uses the channel number and transaction code, combined with a list identifier, to determine if a corresponding control rule exists. If it does, the corresponding control rule is obtained. The system then uses this control rule to determine if the first field name and its value match the rule. If they match, the user corresponding to the transaction request information is identified as the target user; otherwise, the transaction request is blocked. If no corresponding control rule exists, the user corresponding to the transaction request information is identified as the target user.

[0152] This reduces the processing load on the user screening and testing process.

[0153] In the embodiments provided in this application, user input on control rules can be received in real time, and the control rule base can be updated.

[0154] Based on the user determination method provided in the above embodiments, this application also provides specific implementations of the user determination device. Please refer to the following embodiments.

[0155] See Figure 3 The user determination device 300 provided in this application embodiment includes:

[0156] The acquisition module 310 is used to acquire transaction request information, which includes at least one first field name, the field value of the first field name, the channel number, and the transaction code.

[0157] The acquisition module 310 is also used to acquire the control rules in the control rule library corresponding to the list flag using the channel number and transaction code;

[0158] The determination module 320 is used to determine the user corresponding to the transaction request information as the target user if the first field name and the field value of the first field name meet the control rules.

[0159] The control rule base includes multiple second field names, field values ​​for each second field name, and a range of first field values; the control rules include:

[0160] Multiple second field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding second field name;

[0161] Multiple second field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding second field name;

[0162] Multiple second field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding second field name;

[0163] Multiple second field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding second field name;

[0164] Multiple second field names include at least one first field name, and the field value of each first field name is within the range of first field values;

[0165] Multiple second field names include at least one first field name, and the field value of each second field name includes the field value of the corresponding first field name.

[0166] Based on this, in some embodiments, the list identifier includes a first list identifier, the control rule base includes a first control rule base corresponding to the first list identifier, the first control rule base includes multiple third field names, the field value of each third field name and the range of second field values; the second field name includes the third field name;

[0167] The control rules include:

[0168] Multiple third field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding third field name;

[0169] Multiple third field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding third field name;

[0170] Multiple third field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding third field name;

[0171] Multiple third field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding third field name;

[0172] Multiple third field names include at least one first field name, and the field value of each first field name is within the range of second field values;

[0173] Multiple third field names include at least one first field name, and the field value of each third field name includes the field value of the corresponding first field name.

[0174] Based on this, in some embodiments, the list identifier includes a second list identifier, the control rule base includes a second control rule base corresponding to the second list identifier, and the second control rule base includes multiple fourth field names, field values ​​for each fourth field name, and a range of third field values; the second field name includes the fourth field name;

[0175] The control rules include:

[0176] Multiple fourth field names include at least one first field name, and the field value of each first field name matches the field value of the corresponding fourth field name;

[0177] Multiple fourth field names include at least one first field name, and the field value of one of the first field names matches the field value of the corresponding fourth field name;

[0178] Multiple fourth field names include at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding fourth field name;

[0179] Multiple fourth field names include at least one first field name, and the field value of each first field name does not match the field value of the corresponding fourth field name;

[0180] Multiple fourth field names include at least one first field name, and the field value of each first field name is within the range of third field values;

[0181] Multiple fourth field names include at least one first field name, and the field value of each fourth field name includes the field value of the corresponding first field name.

[0182] Based on this, in some embodiments, the device 300 may further include:

[0183] The interception module is used to intercept transaction request information when the first field name and the field value corresponding to the first field name do not meet the control rules.

[0184] Based on this, in some embodiments, the device 300 may further include:

[0185] The determination module 320 is also used to determine the user corresponding to the transaction request information as the target user in the absence of any control rules, before obtaining the control rules in the control rule base corresponding to the list identifier using the channel number and transaction code.

[0186] Each module of the user determination device provided in this application embodiment can realize the functions of each step of the user determination method described above, and can achieve its corresponding technical effects. For the sake of brevity, it will not be described in detail here.

[0187] Based on the same inventive concept, embodiments of this application also provide an electronic device.

[0188] Figure 4 A schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application is shown.

[0189] An electronic device may include a processor 401 and a memory 402 storing computer program instructions.

[0190] Specifically, the processor 401 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0191] Memory 402 may include mass storage for data or instructions. For example, and not limitingly, memory 402 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 402 may include removable or non-removable (or fixed) media. Where appropriate, memory 402 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 402 is non-volatile solid-state memory.

[0192] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.

[0193] The processor 401 implements any of the user determination methods in the above embodiments by reading and executing computer program instructions stored in the memory 402.

[0194] In one example, the electronic device may also include a communication interface 403 and a bus 410. For example, Figure 4 As shown, the processor 401, memory 402, and communication interface 403 are connected through bus 410 and complete communication with each other.

[0195] The communication interface 403 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0196] Bus 410 includes hardware, software, or both, that couples components of an electronic device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Linear Predictive Coding (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (Peripheral Component Interconnect-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VESA Local Bus, VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 410 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application contemplates any suitable bus or interconnection. The electronic device can perform the user determination method described in the embodiments of the present invention, thereby implementing the user determination method described above.

[0197] Furthermore, in conjunction with the user determination methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the user determination methods in the above embodiments.

[0198] This application also provides a computer program product in which the instructions, when executed by a processor of an electronic device, cause the electronic device to perform various processes implementing any of the above-described user determination method embodiments.

[0199] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0200] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable read-only memory (EROM), floppy disks, compact disc read-only memory (CD-ROM), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0201] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0202] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0203] The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method for determining a user, characterized in that, include: Obtain transaction request information, which includes at least one first field name, the field value of the first field name, the channel number, and the transaction code; Using the channel number and the transaction code, obtain the control rules in the control rule base corresponding to the list identifier; If the first field name and the field value of the first field name satisfy the control rules, the user corresponding to the transaction request information is determined as the target user, and then the test user of the newly launched functional module of the transaction system is determined. The control rule base includes multiple second field names, field values ​​for each second field name, and a range of first field values. The control rules include: The plurality of second field names include the at least one first field name, and the field value of each first field name matches the field value of the corresponding second field name; The plurality of second field names include the at least one first field name, and the field value of one of the at least one first field names matches the field value of the corresponding second field name; The plurality of second field names include the at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding second field name; The plurality of second field names include the at least one first field name, and the field value of each first field name does not match the field value of the corresponding second field name; The plurality of second field names include the at least one first field name, and the field value of each first field name is within the range of the first field value; The plurality of second field names include the at least one first field name, and the field value of each second field name includes the field value of the corresponding first field name; Before using the channel number and the transaction code to obtain the control rules in the control rule base corresponding to the list identifier, the method further includes: In the absence of the aforementioned control rules, the user corresponding to the transaction request information is identified as the target user.

2. The user determination method according to claim 1, characterized in that, The list identifier includes a first list identifier, and the control rule base includes a first control rule base corresponding to the first list identifier. The first control rule base includes multiple third field names, field values ​​for each third field name, and a range of second field values. The second field name includes the third field name; The control rules include: The plurality of third field names include the at least one first field name, and the field value of each first field name matches the field value of the corresponding third field name; The plurality of third field names include the at least one first field name, and the field value of one of the at least one first field names matches the field value of the corresponding third field name; The plurality of third field names include the at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding third field name; The plurality of third field names include the at least one first field name, and the field value of each first field name does not match the field value of the corresponding third field name; The plurality of third field names include the at least one first field name, and the field value of each first field name is within the range of the second field value; The plurality of third field names include the at least one first field name, and the field value of each third field name includes the field value of the corresponding first field name.

3. The user determination method according to claim 1, characterized in that, The list identifier includes a second list identifier, and the control rule base includes a second control rule base corresponding to the second list identifier. The second control rule base includes multiple fourth field names, field values ​​for each fourth field name, and a range of third field values. The second field name includes the fourth field name; The control rules include: The plurality of fourth field names include the at least one first field name, and the field value of each first field name matches the field value of the corresponding fourth field name; The plurality of fourth field names include the at least one first field name, and the field value of one of the at least one first field names matches the field value of the corresponding fourth field name; The plurality of fourth field names include the at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding fourth field name; The plurality of fourth field names include the at least one first field name, and the field value of each first field name does not match the field value of the corresponding fourth field name; The plurality of fourth field names include the at least one first field name, and the field value of each first field name is within the range of the third field value; The plurality of fourth field names include the at least one first field name, and the field value of each fourth field name includes the field value of the corresponding first field name.

4. The user determination method according to claim 1, characterized in that, Also includes: If the first field name and the field value corresponding to the first field name do not meet the control rules, the transaction request information is intercepted.

5. A user determination device, characterized in that, include: The acquisition module is used to acquire transaction request information, which includes at least one first field name, the field value of the first field name, the channel number, and the transaction code. The acquisition module is also used to acquire control rules in the control rule base corresponding to the list flag using the channel number and the transaction code; The determination module is used to determine the user corresponding to the transaction request information as the target user when the first field name and the field value of the first field name satisfy the control rules, and then determine the test user of the newly launched functional module of the transaction system. The control rule base includes multiple second field names, field values ​​for each second field name, and a range of first field values. The control rules include: The plurality of second field names include the at least one first field name, and the field value of each first field name matches the field value of the corresponding second field name; The plurality of second field names include the at least one first field name, and the field value of one of the at least one first field names matches the field value of the corresponding second field name; The plurality of second field names include the at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding second field name; The plurality of second field names include the at least one first field name, and the field value of each first field name does not match the field value of the corresponding second field name; The plurality of second field names include the at least one first field name, and the field value of each first field name is within the range of the first field value; The plurality of second field names include the at least one first field name, and the field value of each second field name includes the field value of the corresponding first field name; The device further includes: The determining module is further configured to, before obtaining the control rules in the control rule library corresponding to the list identifier using the channel number and the transaction code, determine the user corresponding to the transaction request information as the target user in the absence of the control rules.

6. The user determination device according to claim 5, characterized in that, The list identifier includes a first list identifier, and the control rule base includes a first control rule base corresponding to the first list identifier. The first control rule base includes multiple third field names, field values ​​for each third field name, and a range of second field values. The second field name includes the third field name; The control rules include: The plurality of third field names include the at least one first field name, and the field value of each first field name matches the field value of the corresponding third field name; The plurality of third field names include the at least one first field name, and the field value of one of the at least one first field names matches the field value of the corresponding third field name; The plurality of third field names include the at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding third field name; The plurality of third field names include the at least one first field name, and the field value of each first field name does not match the field value of the corresponding third field name; The plurality of third field names include the at least one first field name, and the field value of each first field name is within the range of the second field value; The plurality of third field names include the at least one first field name, and the field value of each third field name includes the field value of the corresponding first field name.

7. The user determination device according to claim 5, characterized in that, The list identifier includes a second list identifier, and the control rule base includes a second control rule base corresponding to the second list identifier. The second control rule base includes multiple fourth field names, field values ​​for each fourth field name, and a range of third field values. The second field name includes the fourth field name; The control rules include: The plurality of fourth field names include the at least one first field name, and the field value of each first field name matches the field value of the corresponding fourth field name; The plurality of fourth field names include the at least one first field name, and the field value of one of the at least one first field names matches the field value of the corresponding fourth field name; The plurality of fourth field names include the at least one first field name, and the field value of each first field name matches one of the field values ​​of the corresponding fourth field name; The plurality of fourth field names include the at least one first field name, and the field value of each first field name does not match the field value of the corresponding fourth field name; The plurality of fourth field names include the at least one first field name, and the field value of each first field name is within the range of the third field value; The plurality of fourth field names include the at least one first field name, and the field value of each fourth field name includes the field value of the corresponding first field name.

8. The user determination device according to claim 5, characterized in that, Also includes: The interception module is used to intercept the transaction request information if the first field name and the field value corresponding to the first field name do not meet the control rules.

9. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the user determination method as described in any one of claims 1-4.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the user determination method as described in any one of claims 1-4.

11. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device is able to perform the user determination method as described in any one of claims 1-4.

Images