CN117216113A - User determination method, device, equipment and computer storage medium - Google Patents
User determination method, device, equipment and computer storage medium Download PDFInfo
- Publication number
- CN117216113A CN117216113A CN202311256132.6A CN202311256132A CN117216113A CN 117216113 A CN117216113 A CN 117216113A CN 202311256132 A CN202311256132 A CN 202311256132A CN 117216113 A CN117216113 A CN 117216113A
- Authority
- CN
- China
- Prior art keywords
- field
- name
- field name
- value
- field value
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000004590 computer program Methods 0.000 claims description 18
- 238000012360 testing method Methods 0.000 abstract description 16
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 230000007547 defect Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012216 screening Methods 0.000 description 2
- 206010033799 Paralysis Diseases 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012512 characterization method Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The application discloses a user determination method, device and equipment and a computer storage medium, and relates to the technical field of big data. The method comprises the following steps: acquiring transaction request information, wherein the transaction request information comprises at least one first field name, a field value of the first field name, a channel number and a transaction code; acquiring control rules in a control rule base corresponding to the list mark by using the channel number and the transaction code; and under the condition that the first field name and the field value of the first field name meet the control rule, determining the user corresponding to the transaction request information as the target user. In this way, the first control rule is obtained based on the channel number and the transaction code in the transaction request information, and under the condition that the field name and the field value corresponding to the field name in the transaction request information meet the first control rule, the user corresponding to the transaction request information is determined to be the target user, and then the test user of the new online function module of the transaction system is determined.
Description
Technical Field
The present application belongs to the technical field of big data, and in particular, relates to a method, an apparatus, a device, and a computer storage medium for determining a user.
Background
With the development of society, the organization is more and more complex in division of labor, the business development is faster, and in order to follow the time footsteps, a transaction system is always on line in advance or in emergency, but due to the fact that the function module on line in advance or in emergency possibly has some defects, a test user is required to test the function module. To determine whether a defect exists in a functional module, a test user needs to be determined, and the test user tries the functional module to find a possible defect in the functional module.
Disclosure of Invention
The embodiment of the application provides a method, a device, equipment and a computer storage medium for determining a user, which can determine a test user of a new online function module of a transaction system.
In a first aspect, an embodiment of the present application provides a method for determining a user, where the method includes:
acquiring transaction request information, wherein the transaction request information comprises at least one first field name, a field value of the first field name, a channel number and a transaction code;
acquiring control rules in a control rule base corresponding to the list mark by using the channel number and the transaction code;
under the condition that the first field name and the field value of the first field name meet the control rule, determining the user corresponding to the transaction request information as a target user;
The control rule base comprises a plurality of second field names, field values of each second field name and a first field value interval; the control rules include:
the plurality of second field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is in a first field value interval;
the plurality of second field names includes at least one first field name, and the field value of each second field name includes a field value corresponding to the first field name.
In a possible embodiment, the list flag includes a first list flag, the control rule base includes a first control rule base corresponding to the first list flag, and the first control rule base includes a plurality of third field names, a field value of each third field name, and a second field value interval; the second field name includes a third field name;
The control rules include:
the plurality of third field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is in the second field value interval;
the plurality of third field names includes at least one first field name, and a field value of each third field name includes a field value of a corresponding first field name.
In a possible implementation embodiment, the list mark includes a second list mark, the control rule base includes a second control rule base corresponding to the second list mark, and the second control rule base includes a plurality of fourth field names, a field value of each fourth field name, and a third field value interval; the second field name includes a fourth field name;
The control rules include:
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is in a third field value interval;
the plurality of fourth field names includes at least one first field name, and the field value of each fourth field name includes a field value corresponding to the first field name.
In one possible implementation embodiment, the method further includes:
and intercepting the transaction request information under the condition that the first field name and the field value corresponding to the first field name do not meet the control rule.
In one possible embodiment, before obtaining the control rule in the control rule base corresponding to the list mark by using the channel number and the transaction code, the method further includes:
and under the condition that the control rule does not exist, determining the user corresponding to the transaction request information as a target user.
In a second aspect, an embodiment of the present application provides a user determining apparatus, including:
the acquisition module is used for acquiring transaction request information, wherein the transaction request information comprises at least one first field name, a field value of the first field name, a channel number and a transaction code;
the acquisition module is also used for acquiring the control rules in the control rule base corresponding to the list mark by using the channel number and the transaction code;
the determining module is used for determining that the user corresponding to the transaction request information is a target user under the condition that the first field name and the field value of the first field name meet the control rule;
the control rule base comprises a plurality of second field names, field values of each second field name and a first field value interval; the control rules include:
the plurality of second field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding second field name;
The plurality of second field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is in a first field value interval;
the plurality of second field names includes at least one first field name, and the field value of each second field name includes a field value corresponding to the first field name.
In a possible embodiment, the list flag includes a first list flag, the control rule base includes a first control rule base corresponding to the first list flag, and the first control rule base includes a plurality of third field names, a field value of each third field name, and a second field value interval; the second field name includes a third field name;
The control rules include:
the plurality of third field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is in the second field value interval;
the plurality of third field names includes at least one first field name, and a field value of each third field name includes a field value of a corresponding first field name.
In a possible implementation embodiment, the list mark includes a second list mark, the control rule base includes a second control rule base corresponding to the second list mark, and the second control rule base includes a plurality of fourth field names, a field value of each fourth field name, and a third field value interval; the second field name includes a fourth field name;
The control rules include:
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is in a third field value interval;
the plurality of fourth field names includes at least one first field name, and the field value of each fourth field name includes a field value corresponding to the first field name.
In one possible implementation embodiment, the method further includes:
the interception module is used for intercepting the transaction request information under the condition that the first field name and the field value corresponding to the first field name do not meet the control rule.
In one possible implementation embodiment, the apparatus further includes:
the determining module is further configured to determine, before obtaining a control rule in the control rule base corresponding to the list mark by using the channel number and the transaction code, that a user corresponding to the transaction request information is a target user if the control rule does not exist.
In a third aspect, an embodiment of the present application provides an electronic device, including:
a processor and a memory storing computer program instructions;
the processor, when executing the computer program instructions, implements any of the above methods of determining at the user.
In a fourth aspect, embodiments of the present application provide a computer storage medium having stored thereon computer program instructions which, when executed by a processor, implement a method of determining a user of any of the above.
In a fifth aspect, an embodiment of the present application provides a computer program product, where instructions in the computer program product, when executed by a processor of an electronic device, enable the electronic device to perform a method of determining a user according to any one of the above.
The method, the device, the equipment and the computer storage medium for determining the user in the embodiment of the application comprise the following steps: acquiring transaction request information, wherein the transaction request information comprises at least one first field name, a field value of the first field name, a channel number and a transaction code; acquiring control rules in a control rule base corresponding to the list mark by using the channel number and the transaction code; and under the condition that the first field name and the field value of the first field name meet the control rule, determining the user corresponding to the transaction request information as the target user. In this way, the control rule is obtained based on the channel number and the transaction code in the transaction request information, and under the condition that the field name and the field value corresponding to the field name in the transaction request information meet the control rule, the user corresponding to the transaction request information is determined to be the target user, and then the test user of the new online functional module of the transaction system is determined.
Drawings
In order to more clearly illustrate the technical solution of the embodiments of the present application, the drawings that are needed to be used in the embodiments of the present application will be briefly described, and it is possible for a person skilled in the art to obtain other drawings according to these drawings without inventive effort.
FIG. 1 is a flow chart of a method of determining a user according to one embodiment of the present application;
FIG. 2 is a flow chart of a method for determining a user according to another embodiment of the present application;
FIG. 3 is a schematic structural view of a user determination device according to still another embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to still another embodiment of the present application.
Detailed Description
Features and exemplary embodiments of various aspects of the present application will be described in detail below, and in order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail below with reference to the accompanying drawings and the detailed embodiments. It should be understood that the particular embodiments described herein are meant to be illustrative of the application only and not limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the application by showing examples of the application.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
It should be noted that, in the embodiment of the present application, the data acquisition, storage, use, processing, etc. all conform to the relevant regulations of the national laws and regulations.
With the development of society, the organization is more and more complex in division of labor, the business development is faster, and in order to follow the time footsteps, a transaction system is always on line in advance or in emergency, but due to the fact that the function module on line in advance or in emergency possibly has some defects, a test user is required to test the function module. To determine whether a defect exists in a functional module, a test user needs to be determined, and the test user tries the functional module to find a possible defect in the functional module.
In order to solve the problems in the prior art, the embodiment of the application provides a user determination method, a user determination device, a user determination equipment and a computer storage medium. The following first describes a method for determining a user provided by an embodiment of the present application.
Fig. 1 is a flow chart of a method for determining a user according to an embodiment of the present application.
As shown in fig. 1, the method for determining a user provided by the embodiment of the application includes the following steps.
S110, acquiring transaction request information, wherein the transaction request information comprises at least one first field name, a field value of the first field name, a channel number and a transaction code.
In some embodiments, the transaction request information may be transaction request information sent by the user through the front-end system, and the transaction system may receive the transaction request information sent by the front-end system. Different channel number characterizations are sent through different head-end systems, one channel number corresponding to each head-end system. One transaction request message includes one transaction code, and the transaction code is different in different transaction request messages. The transaction code is the code of the smallest service unit that the transaction system provides for front-end system access.
In some embodiments, the format of the transaction request information may include, but is not limited to, JSON format, XML format.
In some embodiments, the channel number and transaction code may be in the request header of the transaction request information.
As one example, the field names may include, but are not limited to, field names associated with user ID, organization code, user type, and behavior information of the user.
S120, obtaining the control rules in the control rule base corresponding to the list mark by using the channel number and the transaction code.
In some embodiments, the control rules corresponding to the channel number and the transaction code are stored in the control rule library, and the channel number and the transaction code are used for combining the list mark to judge whether the corresponding control rules exist, if so, the corresponding control rules are obtained.
Here, the control rule base includes a field name matching the first field name and a field value corresponding to the field name. The control rule may also include a field value interval.
S130, determining a user corresponding to the transaction request information as a target user when the first field name and the field value of the first field name meet the control rule.
The control rule base comprises a plurality of second field names, field values of each second field name and a first field value interval; the control rules include:
the plurality of second field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding second field name;
The plurality of second field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is in a first field value interval;
the plurality of second field names includes at least one first field name, and the field value of each second field name includes a field value corresponding to the first field name.
In some embodiments, the first field name is compared with the field name in the control rule base, and when the first field name is matched with 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 the field value interval, so that a comparison result is obtained. And under the condition that the comparison result meets the control rule, determining the user corresponding to the transaction request information as a target user.
In some embodiments, the channel number and the transaction code are used to combine the list flag to determine whether a corresponding control rule exists, and if so, the corresponding control rule is obtained.
In some embodiments, the control rule base includes "and", "or", "not", "fuzzy match", "boundary value", and other basic rules, and different rules may be used in combination.
In some embodiments, the and rule characterizes that all of the field values corresponding to all of the first field names match the field values corresponding to the second fields, i.e., the plurality of second field names includes 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 characterizes that a field value of one of the at least one first field name matches a field value of a corresponding second field name, i.e. the plurality of second field names comprises the at least one first field name and the field value of one of the at least one first field name matches a field value of a corresponding second field name; alternatively, the or rule may also characterize that a field value of a first field name matches one of the field values of the corresponding second field name. The "not" rule characterizes that the field value of a first field name does not match the field value of a corresponding second field name, i.e. the plurality of second field names comprises at least one first field name and the field value of each first field name does not match the field value of a corresponding second field name. The "fuzzy match" rule characterizes a fuzzy match of a field value of a first field name with a field value of a corresponding second field name, i.e. the plurality of second field names comprises at least one first field name and the field value of each second field name comprises a field value of a corresponding first field name, it being understood that the field value of a first field name may match a field value of a corresponding second field name ending, that the field value of a first field name may also match a field value of a beginning of the field value of the corresponding second field name, and that the field value of a first field name may also match a field value intermediate the field value of the corresponding second field name. The "boundary value" rule corresponds to a field value of a numeric type, and characterizes a value range of the field values of the first field names, that is, the plurality of second field names include at least one first field name, and the field value of each first field name is within a first field value interval. Here, the first field value section may or may not correspond to the field value of the second field name (if the field value of the second field name is also a numeric value type, it may or may not correspond to the field value of the second field name).
In this way, the control rule is obtained based on the channel number and the transaction code in the transaction request information, and under the condition that the field name and the field value corresponding to the field name in the transaction request information meet the control rule, the user corresponding to the transaction request information is determined to be the target user, and then the test user of the new online function module of the transaction system is determined.
Based on this, in some embodiments, the list flag includes a first list flag, the control rule base includes a first control rule base corresponding to the first list flag, the first control rule base includes a plurality of third field names, a field value of each third field name, and a second field value interval; the second field name includes a third field name;
the control rules include:
the plurality of third field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding third field name;
The plurality of third field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is in the second field value interval;
the plurality of third field names includes at least one first field name, and a field value of each third field name includes a field value of a corresponding first field name.
In some embodiments, the channel number and the transaction code are used to combine the first list flag to determine whether a corresponding control rule exists, and if so, the corresponding control rule is obtained.
In some embodiments, the first control rule base includes "and", "or", "not", "fuzzy match", "boundary value", and other basic rules, and different rules may be used in combination.
In some embodiments, the and rule characterizes that all of the field values corresponding to all of the first field names match the field values corresponding to the second field, i.e., the plurality of third field names includes 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 characterizes that a field value of one of the at least one first field name matches a field value of a corresponding third field name, i.e. the plurality of third field names comprises the at least one first field name and the field value of one of the at least one first field name matches a field value of a corresponding third field name; alternatively, the or rule may also characterize that a field value of the first field name matches one of the field values of the corresponding third field name. The "not" rule characterizes that the field values of the first field names do not match the field values of the corresponding third field names, i.e. the plurality of third field names comprises 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 match" rule characterizes a fuzzy match of a field value of a first field name with a field value of a corresponding third field name, i.e. the plurality of third field names comprises at least one first field name and the field value of each third field name comprises a field value of a corresponding first field name, it being understood that the field value of the first field name may match a field value of an ending of the field value of the corresponding third field name, that the field value of the first field name may also match a field value of a beginning of the field value of the corresponding third field name, and that the field value of the first field name may also match a field value intermediate the field value of the corresponding third field name. The "boundary value" rule corresponds to a field value of a numeric type, and characterizes a value range of the field values of the first field names, that is, the plurality of third field names include at least one first field name, and the field value of each first field name is within a second field value interval. Here, the second field value section may or may not correspond to the field value of the third field name (if the field value of the third field name is also a numeric value type, it may or may not correspond to the field value of the third field name). The first field value interval may be a second field value interval.
As an example, in the case where the transaction request information includes two first field names, if the field value of the first field name X is aaa, the field value of the first field name Y is bbb, the field value of the control rule is the third field name X is aaa, and the field value of the third field name Y is bbb, the control rule is satisfied.
If the field value of the first field name X is aaa, the field value of the first field name Y is bbb, the control rule is that the field value of the third field name X is aaa, or the field value of the third field name Y is bbb, the control rule is satisfied.
If the field value of the first field name X is aaa, the field value of the first field name Y is ccc, the field value of the control rule is aaa, or the field value of the third field name Y is bbb, the control rule is satisfied.
If the field value of the first field name X is aaa, the field value of the first field name Y is bbb, and the control rule is that the field value of the third field name X is not aaa, the control rule is satisfied.
If the field value of the first field name X is aaa, the field value of the first field name Y is ccc, the field value of the control rule is aaac, and the field value of the third field name Y is ebbb, the control rule is satisfied.
If the field value of the first field name X is aaa, the field value of the first field name Y is ccc, the control rule is that the field value of the third field name X is aaca, and the field value of the third field name Y is ebbb, the control rule is satisfied.
If the field value of the first field name X is 2, the field value of the first field name Y is 2.5, and the control rule is that the second field value interval is [1,3], the control rule is satisfied.
Thus, the test user can be accurately screened out through the setting of the control rules in the first control rule base.
Based on this, in some embodiments, the list flag includes a second list flag, the control rule base includes a second control rule base corresponding to the second list flag, the second control rule base includes a plurality of fourth field names, a field value of each fourth field name, and a third field value interval; the second field name includes a fourth field name;
the control rules include:
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding fourth field name;
The plurality of fourth field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is in a third field value interval;
the plurality of fourth field names includes at least one first field name, and the field value of each fourth field name includes a field value corresponding to the first field name.
In some embodiments, the channel number and the transaction code are used to combine the second list flag to determine whether a corresponding control rule exists, and if so, the corresponding control rule is obtained.
In some embodiments, the second control rule base includes "and", "or", "not", "fuzzy match", "boundary value", and other basic rules, and different rules may be used in combination.
In some embodiments, the and rule characterizes that all of the field values corresponding to all of the first field names match the field values corresponding to the second field, i.e., the plurality of fourth field names includes 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 characterizes that a field value of one of the at least one first field name matches a field value of a corresponding fourth field name, i.e. the plurality of fourth field names includes the at least one first field name, and a field value of one of the at least one first field name matches a field value of a corresponding fourth field name; alternatively, the or rule may also characterize that a field value of the first field name matches one of the field values of the corresponding fourth field name. The "not" rule characterizes that the field value of the first field name does not match the field value of the corresponding fourth field name, i.e. the plurality of fourth field names comprises 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 characterizes a fuzzy match of the field value of the first field name with the field value of the corresponding fourth field name, i.e., the plurality of fourth field names includes 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. It will be appreciated that the field value of the first field name may match the field value corresponding to the end of the field value of the fourth field name, that the field value of the first field name may also match the field value corresponding to the beginning of the field value of the fourth field name, and that the field value of the first field name may also match the field value intermediate to the field value corresponding to the fourth field name. The "boundary value" rule corresponds to a field value of a numeric value type, and characterizes a value range of the field values of the first field names, that is, the plurality of fourth field names include at least one first field name, and the field value of each first field name is within a third field value interval. Here, the third field value section may or may not correspond to the field value of the fourth field name (if the field value of the fourth field name is also a numeric value type, it may or may not correspond to the field value of the fourth field name). The first field value interval may be a third field value interval.
As an example, in the case where the transaction request information includes two first field names, if the field value of the first field name Z is fff, the field value of the first field name M is ggg, the control rule is that the field value of the fourth field name Z is fff, and the field value of the fourth field name M is ggg, the control rule is satisfied.
If the field value of the first field name Z is fff, the field value of the first field name M is ggg, the control rule is that the field value of the fourth field name Z is fff, or the field value of the fourth field name M is ggg, the control rule is satisfied.
If the field value of the first field name Z is fff, the field value of the first field name M is ccc, the control rule is that the field value of the fourth field name Z is fff, or the field value of the fourth field name M is ggg, the control rule is satisfied.
If the field value of the first field name Z is fff, the field value of the first field name M is ggg, and the control rule is that the field value of the fourth field name Z is not fff, the control rule is satisfied.
If the field value of the first field name Z is fff, the field value of the first field name M is ccc, the field value of the control rule of the fourth field name Z is fffh, and the field value of the fourth field name M is mggg, the control rule is satisfied.
If the field value of the first field name Z is fff, the field value of the first field name M is ccc, the control rule is that the field value of the fourth field name Z is ffhf, and the field value of the fourth field name M is eggg, the control rule is satisfied.
If the field value of the first field name Z is 1.5, the field value of the first field name M is 2.3, and the control rule is that the third field value interval is [0,3], the control rule is satisfied.
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 the field values of the field names do not have a relationship.
Thus, the test user can be accurately screened out through setting the control rules in the second control rule base.
Based on this, in some embodiments, the method may further comprise:
and intercepting the transaction request information under the condition that the first field name and the field value corresponding to the first field name do not meet the control rule.
In some embodiments, after intercepting the transaction request information, the target information is sent to a front-end system that sent the transaction request information to alert the user that the transaction request information was intercepted.
Thus, users except the test user are prevented from accessing the newly-online functional module of the transaction system, and the problem caused by the use of a large number of users under the condition that the newly-online functional module is not tested is prevented from being caused, so that the system is paralyzed or the problem cannot be clearly found; while affecting the user experience.
Based on this, in some embodiments, before obtaining the control rule in the control rule base corresponding to the list mark by using the channel number and the transaction code, the method may further include:
and under the condition that the control rule does not exist, determining the user corresponding to the transaction request information as a target user.
In some embodiments, in the event that a user is a user that does not require control rule screening, control rules for such user will not be saved in the control rule base. For example, all first field names and field values of the first field names associated with a user sending a transaction request are known to be able to satisfy all control rules in the control rule base, and the control rules will no longer be set for that user.
In some embodiments, as shown in fig. 2, after the transaction request information is acquired, the channel number and the transaction code are used to combine the list flag to determine whether a corresponding control rule exists, and if so, the corresponding control rule is acquired. And judging whether the first field name and the field value of the first field name hit the control rule or not by utilizing the control rule, if hit, determining that the user corresponding to the transaction request information is a target user, and if miss, intercepting the transaction request. If the corresponding control rule does not exist, determining the user corresponding to the transaction request information as a target user.
In this way, the processing pressure of the screening test user process is reduced.
In the embodiment provided by the application, the input of the control rule by the user can be received in real time, and the control rule base is updated.
Based on the user determination method provided by the embodiment, correspondingly, the application further provides a specific implementation mode of the user determination device. Please refer to the following examples.
Referring to fig. 3, a user determining apparatus 300 provided in an embodiment of the present application includes:
an obtaining module 310, configured to obtain transaction request information, where the transaction request information includes at least one first field name, a field value of the first field name, a channel number, and a transaction code;
the obtaining module 310 is further configured to obtain a control rule in the control rule base corresponding to the list mark by using the channel number and the transaction code;
a determining module 320, configured to determine, when the first field name and the field value of the first field name satisfy the control rule, that the user corresponding to the transaction request information is a target user;
the control rule base comprises a plurality of second field names, field values of each second field name and a first field value interval; the control rules include:
the plurality of second field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding second field name;
The plurality of second field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding second field name;
the plurality of second field names comprise at least one first field name, and the field value of each first field name is in a first field value interval;
the plurality of second field names includes at least one first field name, and the field value of each second field name includes a field value corresponding to the first field name.
Based on this, in some embodiments, the list flag includes a first list flag, the control rule base includes a first control rule base corresponding to the first list flag, the first control rule base includes a plurality of third field names, a field value of each third field name, and a second field value interval; the second field name includes a third field name;
The control rules include:
the plurality of third field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding third field name;
the plurality of third field names comprise at least one first field name, and the field value of each first field name is in the second field value interval;
the plurality of third field names includes at least one first field name, and a field value of each third field name includes a field value of a corresponding first field name.
Based on this, in some embodiments, the list flag includes a second list flag, the control rule base includes a second control rule base corresponding to the second list flag, the second control rule base includes a plurality of fourth field names, a field value of each fourth field name, and a third field value interval; the second field name includes a fourth field name;
The control rules include:
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of one of the at least one first field name is matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is matched with one of the field values of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is not matched with the field value of the corresponding fourth field name;
the plurality of fourth field names comprise at least one first field name, and the field value of each first field name is in a third field value interval;
the plurality of fourth field names includes at least one first field name, and the field value of each fourth field name includes a field value corresponding to the first field name.
Based on this, in some embodiments, the apparatus 300 may further include:
the interception module is used for intercepting the transaction request information under the condition that the first field name and the field value corresponding to the first field name do not meet the control rule.
Based on this, in some embodiments, the apparatus 300 may further include:
the determining module 320 is further configured to determine, before obtaining the control rule in the control rule base corresponding to the list flag by using the channel number and the transaction code, that the user corresponding to the transaction request information is the target user if the control rule does not exist.
The modules of the user determining device provided by the embodiment of the application can realize the functions of the steps of the user determining method and achieve the corresponding technical effects, and are not described in detail for brevity.
Based on the same inventive concept, the embodiment of the application also provides electronic equipment.
Fig. 4 shows a schematic hardware structure of an electronic device according to an embodiment of the present application.
A processor 401 may be included in an electronic device as well as a memory 402 in which computer program instructions are stored.
In particular, the processor 401 described above may include a central processing unit (Central Processing Unit, CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured as one or more integrated circuits implementing embodiments of the present application.
Memory 402 may include mass storage for data or instructions. By way of example, and not limitation, memory 402 may comprise a Hard Disk Drive (HDD), floppy Disk Drive, flash memory, optical Disk, magneto-optical Disk, magnetic tape, or universal serial bus (Universal Serial Bus, USB) Drive, or a combination of two or more of the foregoing. 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, where appropriate. In a particular embodiment, the memory 402 is a non-volatile solid state memory.
The Memory may include Read Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk storage media devices, optical storage media devices, flash Memory devices, electrical, optical, or other physical/tangible Memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising 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 methods in accordance with aspects of the present disclosure.
The processor 401 implements the determination method of any one of the users of the above-described embodiments by reading and executing the computer program instructions stored in the memory 402.
In one example, the electronic device may also include a communication interface 403 and a bus 410. As shown in fig. 4, the processor 401, the memory 402, and the communication interface 403 are connected by a bus 410 and perform communication with each other.
The communication interface 403 is mainly used to implement communication between each module, device, unit and/or apparatus in the embodiment of the present application.
Bus 410 includes hardware, software, or both, coupling components of the electronic device to one another. By way of example, and not limitation, the buses may include an accelerated graphics port (Accelerated Graphics Port, AGP) or other graphics Bus, an enhanced industry standard architecture (Extended Industry Standard Architecture, EISA) Bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an industry standard architecture (Industry Standard Architecture, ISA) Bus, an Infiniband interconnect, a low pin count (Linear Predictive Coding, LPC) Bus, a memory Bus, a micro channel architecture (MicroChannel Architecture, MCa) Bus, a peripheral component interconnect (Peripheral Component Interconnect, PCI) Bus, a PCI-Express (Peripheral Component Interconnect-X, PCI-X) Bus, a serial advanced technology attachment (Serial Advanced Technology Attachment, SATA) Bus, a video electronics standards association Local Bus (VLB) Bus, or other suitable Bus, or a combination of two or more of these. Bus 410 may include one or more buses, where appropriate. Although embodiments of the application have been described and illustrated with respect to a particular bus, the application contemplates any suitable bus or interconnect. The electronic equipment can execute the user determining method in the embodiment of the application, thereby realizing the user determining method.
In addition, in combination with the user determination method in the above embodiment, the embodiment of the present application may be implemented by providing a computer storage medium. The computer storage medium has stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement a method of determining a user of any of the above embodiments.
The application also provides a computer program product, the instructions in which, when executed by a processor of an electronic device, cause the electronic device to perform the various processes implementing the above described embodiments of the user's determination method.
It should be understood that the application is not limited to the particular arrangements and instrumentality described above and shown in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between steps, after appreciating the spirit of the present application.
The functional blocks shown in the above-described structural block diagrams may be implemented in hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transfer information. Examples of machine-readable media include electronic circuitry, semiconductor Memory devices, read-Only Memory (ROM), flash Memory, erasable Read-Only Memory (Erasable Read Only Memory, EROM), floppy disks, compact discs (Compact Disc Read-Only Memory, CD-ROM), optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and the like. The code segments may be downloaded via computer networks such as the internet, intranets, etc.
It should also be noted that the exemplary embodiments mentioned in this disclosure describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, or may be performed in a different order from the order in the embodiments, or several steps may be performed simultaneously.
Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of 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 may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In the foregoing, only the specific embodiments of the present application are described, and it will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to the corresponding processes in the foregoing method embodiments, which are not repeated herein. It should be understood that the scope of the present application is not limited thereto, and any equivalent modifications or substitutions can be easily made by those skilled in the art within the technical scope of the present application, and they should be included in the scope of the present application.
Claims (13)
1. A method of determining a user, comprising:
acquiring transaction request information, wherein the transaction request information comprises at least one first field name, a field value of the first field name, a channel number and a transaction code;
acquiring control rules in a control rule base corresponding to the list mark by using the channel number and the transaction code;
under the condition that the first field name and the field value of the first field name meet the control rule, determining the user corresponding to the transaction request information as a target user;
the control rule base comprises a plurality of second field names, a field value of each second field name and a first field value interval, and the control rule comprises:
The plurality of second field names includes the at least one first field name, and a field value of each first field name matches a field value of a corresponding second field name;
the plurality of second field names comprise the at least one first field name, and a field value of one of the at least one first field name is matched with a field value of a corresponding second field name;
the plurality of second field names include the at least one first field name, and a 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 includes the at least one first field name, and a field value of each first field name does not match a field value of a corresponding second field name;
the plurality of second field names includes the at least one first field name, and a field value of each first field name is within the first field value interval;
the plurality of second field names includes the at least one first field name, and a field value of each second field name includes a field value of a corresponding first field name.
2. The method for determining a user according to claim 1, wherein the list flag includes a first list flag, the control rule base includes a first control rule base corresponding to the first list flag, the first control rule base includes a plurality of third field names, a field value of each third field name, and a second field value interval; the second field name includes the third field name;
The control rule includes:
the plurality of third field names includes the at least one first field name, and a field value of each first field name matches a field value of a corresponding third field name;
the plurality of third field names include the at least one first field name, and a field value of one of the at least one first field name matches a field value of a corresponding third field name;
the plurality of third field names include the at least one first field name, and a 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 includes the at least one first field name, and a field value of each first field name does not match a field value of a corresponding third field name;
the plurality of third field names includes the at least one first field name, and a field value of each first field name is within the second field value interval;
the plurality of third field names includes the at least one first field name, and a field value of each third field name includes a field value of a corresponding first field name.
3. The method for determining a user according to claim 1, wherein the list flag includes a second list flag, the control rule base includes a second control rule base corresponding to the second list flag, the second control rule base includes a plurality of fourth field names, a field value of each fourth field name, and a third field value interval; the second field name includes the fourth field name;
The control rule includes:
the plurality of fourth field names includes the at least one first field name, and a field value of each first field name matches a field value of a corresponding fourth field name;
the plurality of fourth field names comprise the at least one first field name, and a field value of one of the at least one first field name is matched with a field value of a corresponding fourth field name;
the plurality of fourth field names includes the at least one first field name, and a 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 includes the at least one first field name, and a field value of each first field name does not match a field value of a corresponding fourth field name;
the plurality of fourth field names includes the at least one first field name, and a field value of each first field name is within the third field value interval;
the plurality of fourth field names includes the at least one first field name, and a field value of each fourth field name includes a field value of a corresponding first field name.
4. The method of determining a user according to claim 1, further comprising:
And intercepting the transaction request information under the condition that the first field name and the field value corresponding to the first field name do not meet the control rule.
5. The method of claim 1, wherein before obtaining the control rule in the control rule base corresponding to the list flag using the channel number and the transaction code, the method further comprises:
and under the condition that the control rule does not exist, determining the user corresponding to the transaction request information as a target user.
6. A user determination apparatus, comprising:
the system comprises an acquisition module, a transaction request module and a transaction module, wherein the acquisition module is used for acquiring transaction request information, and the transaction request information comprises at least one first field name, a field value of the first field name, a channel number and a transaction code;
the acquisition module is further used for acquiring control rules in a control rule base corresponding to the list mark by utilizing the channel number and the transaction code;
the determining module is used for determining that the user corresponding to the transaction request information is a target user under the condition that the first field name and the field value of the first field name meet the control rule;
the control rule base comprises a plurality of second field names, a field value of each second field name and a first field value interval, and the control rule comprises:
The plurality of second field names includes the at least one first field name, and a field value of each first field name matches a field value of a corresponding second field name;
the plurality of second field names comprise the at least one first field name, and a field value of one of the at least one first field name is matched with a field value of a corresponding second field name;
the plurality of second field names include the at least one first field name, and a 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 includes the at least one first field name, and a field value of each first field name does not match a field value of a corresponding second field name;
the plurality of second field names includes the at least one first field name, and a field value of each first field name is within the first field value interval;
the plurality of second field names includes the at least one first field name, and a field value of each second field name includes a field value of a corresponding first field name.
7. The apparatus according to claim 6, wherein the list flag includes a first list flag, the control rule base includes a first control rule base corresponding to the first list flag, the first control rule base includes a plurality of third field names, a field value of each third field name, and a second field value interval; the second field name includes the third field name;
The control rule includes:
the plurality of third field names includes the at least one first field name, and a field value of each first field name matches a field value of a corresponding third field name;
the plurality of third field names include the at least one first field name, and a field value of one of the at least one first field name matches a field value of a corresponding third field name;
the plurality of third field names include the at least one first field name, and a 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 includes the at least one first field name, and a field value of each first field name does not match a field value of a corresponding third field name;
the plurality of third field names includes the at least one first field name, and a field value of each first field name is within the second field value interval;
the plurality of third field names includes the at least one first field name, and a field value of each third field name includes a field value of a corresponding first field name.
8. The apparatus according to claim 6, wherein the list flag includes a second list flag, the control rule base includes a second control rule base corresponding to the second list flag, the second control rule base includes a plurality of fourth field names, a field value of each of the fourth field names, and a third field value interval; the second field name includes the fourth field name;
The control rule includes:
the plurality of fourth field names includes the at least one first field name, and a field value of each first field name matches a field value of a corresponding fourth field name;
the plurality of fourth field names comprise the at least one first field name, and a field value of one of the at least one first field name is matched with a field value of a corresponding fourth field name;
the plurality of fourth field names includes the at least one first field name, and a 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 includes the at least one first field name, and a field value of each first field name does not match a field value of a corresponding fourth field name;
the plurality of fourth field names includes the at least one first field name, and a field value of each first field name is within the third field value interval;
the plurality of fourth field names includes the at least one first field name, and a field value of each fourth field name includes a field value of a corresponding first field name.
9. The user determination apparatus according to claim 6, further comprising:
And the interception module is used for intercepting the transaction request information under the condition that the first field name and the field value corresponding to the first field name do not meet the control rule.
10. The user determination apparatus according to claim 6, wherein the apparatus further comprises:
the determining module is further configured to determine, before obtaining a control rule in a control rule base corresponding to a list identifier by using the channel number and the transaction code, that a user corresponding to the transaction request information is a target user if the control rule does not exist.
11. An electronic device, the device comprising: a processor and a memory storing computer program instructions;
the processor, when executing the computer program instructions, implements a method of determining a user as claimed in any one of claims 1-5.
12. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon computer program instructions, which when executed by a processor, implement the user determination method according to any of claims 1-5.
13. A computer program product, characterized in that instructions in the computer program product, when executed by a processor of an electronic device, enable the electronic device to perform the user determination method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311256132.6A CN117216113A (en) | 2023-09-26 | 2023-09-26 | User determination method, device, equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311256132.6A CN117216113A (en) | 2023-09-26 | 2023-09-26 | User determination method, device, equipment and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117216113A true CN117216113A (en) | 2023-12-12 |
Family
ID=89049258
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311256132.6A Pending CN117216113A (en) | 2023-09-26 | 2023-09-26 | User determination method, device, equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117216113A (en) |
-
2023
- 2023-09-26 CN CN202311256132.6A patent/CN117216113A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN117216113A (en) | User determination method, device, equipment and computer storage medium | |
| CN116069751A (en) | Information processing method, apparatus, device and computer readable storage medium | |
| CN115604076A (en) | Information processing method, device, equipment and computer readable storage medium | |
| CN114372072A (en) | Data storage method, device, equipment, computer storage medium and program product | |
| CN115186741A (en) | Method, device and equipment for verifying POI fusion data | |
| CN115225170A (en) | Method and device for testing shielding effect of shielding device | |
| CN114417830A (en) | Risk evaluation method, device, equipment and computer readable storage medium | |
| CN114240446A (en) | Data processing method, device, equipment and computer storage medium | |
| CN116775110A (en) | Data synchronization method, device, equipment, medium and product | |
| CN116756219A (en) | Data processing method, device, equipment and computer storage medium | |
| CN116804996A (en) | Data processing method, device, equipment and computer storage medium | |
| CN114693417A (en) | Automatic data processing method, device and equipment for interest bearing and computer storage medium | |
| CN116151887A (en) | Information pushing method, device, equipment and computer storage medium | |
| CN117395136A (en) | Method, device, equipment and computer storage medium for determining call chain | |
| CN115409614A (en) | Data processing method, device, equipment, medium and product | |
| CN116846955A (en) | Service relationship determination method, device, equipment and computer storage medium | |
| CN116963151A (en) | Terminal determining method, device, equipment and computer storage medium | |
| CN115878873A (en) | Method, device and equipment for determining characteristics of abnormal user and storage medium | |
| CN114676290A (en) | Abnormal group identification method and device, equipment, readable storage medium and product thereof | |
| CN116028362A (en) | Data acquisition method, device, equipment and storage medium | |
| CN114637795A (en) | Report processing method, device, equipment, medium and product | |
| CN114661993A (en) | Information query method, device, equipment and computer readable storage medium | |
| CN116775673A (en) | Data integration method of multiple data sources and device, equipment, medium and product thereof | |
| CN116186063A (en) | Data query method, device, equipment and computer storage medium | |
| CN118132655A (en) | Information synchronization method, apparatus, device, storage medium, and program product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |