CN111681005A - Data interaction method and device and electronic equipment - Google Patents
Data interaction method and device and electronic equipment Download PDFInfo
- Publication number
- CN111681005A CN111681005A CN202010373229.5A CN202010373229A CN111681005A CN 111681005 A CN111681005 A CN 111681005A CN 202010373229 A CN202010373229 A CN 202010373229A CN 111681005 A CN111681005 A CN 111681005A
- Authority
- CN
- China
- Prior art keywords
- business object
- result
- auditing
- risk
- abnormal
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0635—Risk analysis of enterprise or organisation activities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06393—Score-carding, benchmarking or key performance indicator [KPI] analysis
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Accounting & Taxation (AREA)
- Game Theory and Decision Science (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the specification discloses a data interaction method, a data interaction device and an electronic device. The method comprises the following steps: receiving a risk analysis request, wherein the risk analysis request comprises a business object to be analyzed; determining a risk index of a business object; judging whether the business object hits an abnormal business object list or not; sending an auditing request to an auditing server according to the judgment result and the determination result; receiving an auditing result fed back by an auditing server; and feeding back the result of the trial and error as a risk analysis result. The data interaction method, the data interaction device and the electronic equipment in the embodiment of the specification can quickly identify whether the business object has risks.
Description
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a data interaction method and device and electronic equipment.
Background
With the development of the internet, it is necessary to identify whether a business object has a risk.
How to quickly identify whether a business object has risks is a technical problem which needs to be solved urgently at present.
Disclosure of Invention
The embodiment of the specification provides a data interaction method, a data interaction device and electronic equipment, so as to quickly identify whether a business object has a risk. The technical scheme of the embodiment of the specification is as follows.
In a first aspect of the embodiments of the present specification, a data interaction method is provided, which is applied to an analysis server, and includes: receiving a risk analysis request, wherein the risk analysis request comprises a business object to be analyzed; determining a risk index of a business object; judging whether the business object hits an abnormal business object list or not; sending an auditing request to an auditing server according to the judgment result and the determination result; receiving an auditing result fed back by an auditing server; and feeding back the result of the trial and error as a risk analysis result.
In a second aspect of the embodiments of the present specification, there is provided a data interaction method applied to an audit server, including: receiving an auditing request, wherein the auditing request comprises a judgment result and a determination result, the judgment result is obtained by judging whether a business object hits an abnormal business object list, and the determination result is obtained by determining a risk index of the business object; if the judgment result is that the abnormal business object list is hit and the determination result is a normal risk index, checking whether the business object really hits the abnormal business object list; and if the abnormal business object list is actually hit, the abnormality is used as an auditing result for feedback.
In a third aspect of the embodiments of the present specification, there is provided a data interaction method applied to an audit server, including: receiving an auditing request, wherein the auditing request comprises a judgment result and a determination result, the judgment result is obtained by judging whether a business object hits an abnormal business object list, and the determination result is obtained by determining a risk index of the business object; if the judgment result is that the abnormal business object list is not hit and the determination result is an abnormal risk index, checking whether the business object really has a risk or not; if the risk exists, the abnormity is used as an auditing result to be fed back; or if no risk exists, the normal condition is used as an auditing result for feedback; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
A fourth aspect of the embodiments of the present specification provides a data interaction method, which is applied to an auditing server, and includes: receiving an auditing request, wherein the auditing request comprises a judgment result and a determination result, the judgment result is obtained by judging whether a business object hits an abnormal business object list, and the determination result is obtained by determining a risk index of the business object; if the judgment result is that the abnormal business object list is hit and the determination result is the abnormal risk level, checking whether the business object really hits the abnormal business object list; and if the abnormal business object list is actually hit, the abnormality is used as an auditing result for feedback.
In a fifth aspect of the embodiments of the present specification, there is provided a data interaction apparatus applied to an analysis server, including: the system comprises a first receiving module, a risk analysis module and a second receiving module, wherein the first receiving module is used for receiving a risk analysis request which comprises a business object to be analyzed; the determining module is used for determining the risk index of the business object; the judging module is used for judging whether the business object hits the abnormal business object list or not; the sending module is used for sending an auditing request to the auditing server according to the judgment result and the determination result; the second receiving module is used for receiving the auditing result fed back by the auditing server; and the feedback module is used for feeding back the auditing result as a risk analysis result.
A sixth aspect of the embodiments of the present specification provides a data interaction apparatus, which is applied to an auditing server, and includes: the system comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for receiving an auditing request, the auditing request comprises a judging result and a determining result, the judging result is obtained by judging whether a business object hits an abnormal business object list, and the determining result is obtained by determining a risk index of the business object; the checking module is used for checking whether the business object really hits the abnormal business object list or not if the judging result is the hit abnormal business object list and the determining result is the normal risk index; and the feedback module is used for feeding back the exception as an auditing result if the exception service object list is actually hit.
A seventh aspect of the embodiments of the present specification provides a data interaction apparatus, which is applied to an auditing server, and includes: the system comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for receiving an auditing request, the auditing request comprises a judging result and a determining result, the judging result is obtained by judging whether a business object hits an abnormal business object list, and the determining result is obtained by determining a risk index of the business object; the investigation module is used for checking whether the business object really has a risk or not if the judgment result is that the abnormal business object list is not hit and the determination result is an abnormal risk index; the feedback module is used for feeding back the abnormity serving as an auditing result if the risk exists; or if no risk exists, the normal condition is used as an auditing result for feedback; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
An eighth aspect of the embodiments of the present specification provides a data interaction apparatus, which is applied to an auditing server, and includes: the system comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for receiving an auditing request, the auditing request comprises a judging result and a determining result, the judging result is obtained by judging whether a business object hits an abnormal business object list, and the determining result is obtained by determining a risk index of the business object; the auditing module is used for checking whether the business object really hits the abnormal business object list or not if the judging result is that the abnormal business object list is hit and the determining result is that the abnormal risk level is found; and the feedback module is used for feeding back the exception as an auditing result if the exception service object list is actually hit.
A ninth aspect of embodiments of the present specification provides an electronic device, including: at least one processor; a memory storing program instructions configured to be suitable for execution by the at least one processor, the program instructions comprising instructions for performing the method of the first, second, third or fourth aspect.
According to the technical scheme provided by the embodiment of the specification, after the risk analysis request is received, the analysis server can determine the risk index of the business object and can judge whether the business object hits an abnormal business object list or not; and the judgment result and the determination result can be combined to feed back the risk analysis result in a unified way. This facilitates a quick determination of whether a business object is at risk.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart illustrating a data interaction method according to an embodiment of the present disclosure;
FIG. 2 is a flow chart illustrating a data interaction method according to an embodiment of the present disclosure;
FIG. 3 is a flow chart illustrating a data interaction method according to an embodiment of the present disclosure;
FIG. 4 is a flow chart illustrating a data interaction method according to an embodiment of the present disclosure;
FIG. 5 is a flow chart illustrating a data interaction method according to an embodiment of the present disclosure;
FIG. 6 is a schematic structural diagram of a data interaction device in an embodiment of the present specification;
FIG. 7 is a schematic structural diagram of a data interaction device in an embodiment of the present specification;
FIG. 8 is a schematic structural diagram of a data interaction device in an embodiment of the present specification;
FIG. 9 is a schematic structural diagram of a data interaction device in an embodiment of the present specification;
fig. 10 is a schematic structural diagram of an electronic device in an embodiment of the present specification.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
In the related art, on one hand, it can be determined whether a business object is a sanctioned business object; if so, the judgment result can be examined to verify whether the business object is actually a sanctioned business object. On the other hand, a risk level of the business object may be determined; if the determination result is a high risk level, the determination result can be audited so as to verify whether the business object really has a risk. In the related art, two aspects of identifying whether a business object has a risk are performed independently, and have no relationship with each other. Thus, the judgment result and the determination result need to be examined and managed respectively. The time spent on carrying out two audits is long, so that the efficiency of identifying whether the business object has risks is low. In addition, two aspects of identifying whether the business object has risks are respectively and independently carried out, so that two risk identification results can be obtained. Thus, in some cases, it is possible to obtain two completely opposite risk identification results.
The embodiment of the specification provides a data interaction method. The implementation environment of the data interaction method can comprise a business server, an analysis server and an auditing server. The service server is used for providing service data for the analysis server. The analysis server is used for analyzing the risk condition of the business object related to the business data. And the examination server is used for examining and managing the risk condition of the business object. The auditing may refer to examining and verifying whether the business object is at risk for reality. The business server, the risk server and the auditing server can be a single server, a server cluster formed by a plurality of servers, or a server deployed at the cloud end. The data interaction method can be applied to business scenes of anti-money laundering. Of course, the data interaction method can also be applied to other service scenarios, such as anti-fraud service scenarios, anti-cyber-gambling service scenarios, and the like. Please refer to fig. 1. The data interaction method may include the following steps.
Step S102: and the business server sends a risk analysis request to the analysis server.
In some embodiments, the risk analysis request may include a business object to be analyzed, which may include an enterprise user, an individual user, an enterprise account, an individual account, and/or the like.
In practical applications, after obtaining the business data, the business server may send a risk analysis request to the analysis server, where the risk analysis request may include the business data, and the business object to be analyzed may include a business object related to the business data. The service server can receive service data input by a user at the terminal equipment. Of course, the service server may also obtain the service data in other manners, and this embodiment is not particularly limited.
For example, the business data may include transaction data, which may include payer, payee, transaction amount, transaction type, transaction time, geographical location and shipping address of the payer, and the like. The business object to which the transaction data relates may include a payer and/or a payee. Of course, the business data may also include other forms of data, such as commodity comment data or resident data. The docking data may include data submitted by the merchant while docking on the online platform, such as a business license, identification card, collection account, and the like. The online platform may include a tianmao, a sounning barnyard, a pindol, and the like.
Step S104: the analysis server receives a risk analysis request.
Step S106: and the analysis server determines the risk index of the business object and judges whether the business object hits an abnormal business object list.
In some embodiments, the risk analysis request may include business data. The analysis server can acquire a service object to be analyzed from the service data; the risk index of the business object can be determined, and a determination result is obtained; and judging whether the service object hits an abnormal service object list or not to obtain a judgment result.
In some embodiments, the risk indicator is used to characterize the likelihood that the business object is at risk, which may include money laundering risk, fraud risk, cyber gambling risk, and the like. The Risk indicator may comprise a Risk level, such as a Credit Risk level (CRR). The risk level may be taken from a set of risk levels, which may include at least two risk levels. For example, the set of risk levels may include a high risk level and a low risk level. As another example, the risk levels may include a low risk level, a medium risk level, and a high risk level. Of course, the risk indicator may also include other forms, such as a score.
The determination result may be a normal risk indicator or an abnormal risk indicator. The normal risk indicator and the abnormal risk indicator may be different according to different forms of the risk indicators. For example, the risk indicator may include a risk level, which may be taken from a set of risk levels, which may include a high risk level and a low risk level. Then the normal risk indicator may comprise said low risk level and the abnormal risk indicator may comprise said high risk level. As another example, the risk indicator may include a risk level, which may be taken from a set of risk levels, which may include a low risk level, a medium risk level, and a high risk level. Then a normal risk indicator may comprise said low risk level and said medium risk level and an abnormal risk indicator may comprise said high risk level. As another example, the risk indicator may include a score. Then, a normal risk indicator may include a score less than a certain threshold, and an abnormal risk indicator may include a score greater than the threshold.
The analysis server may determine the risk indicator of the business object by using the risk prediction rule to obtain a determination result. The risk prediction rules may include data processing logic constructed through expert experience. Alternatively, the risk prediction rule may further include a model trained by a machine learning method. For example, the analytics server may input the business data to the risk prediction rules to determine a risk indicator for the business object.
In some embodiments, the list of anomalous business objects may include at least one anomalous business object. The abnormal business object may refer to a business object having a risk, such as a sanctioned business object, and the sanctioned business object may include a business object suspected of money laundering, a business object suspected of fraud, a business object suspected of cyber gambling, and the like.
The judgment result can be a hit abnormal business object list or a miss abnormal business object list. Hitting an abnormal business object list may mean that the abnormal business object list hits an abnormal business object list that includes a match to the business object. A failure to hit the list of abnormal business objects may mean that the list of abnormal business objects hits a list of abnormal business objects that does not include a match to the business object.
The analysis server may match the business object in the abnormal business object list; if one or more abnormal business objects are successfully matched, the fact that the business objects hit an abnormal business object list can be judged; if one or more abnormal business objects are not matched, it can be judged that the business object does not hit the abnormal business object list.
In some embodiments, the process of determining the risk indicator of the business object and the process of determining whether the business object hits the abnormal business object list may be performed sequentially. For example, the analysis server may determine the risk indicator of the business object first, and then determine whether the business object hits the abnormal business object list. Or, the analysis server may further determine whether the service object hits the abnormal service object list first, and then determine whether the service object hits the abnormal service object list. Of course, the process of determining the risk indicator of the business object and the process of determining whether the business object hits the abnormal business object list may also be executed in parallel.
Step S108: and the analysis server feeds back the normal condition as a risk analysis result.
In some embodiments, the analysis server may determine the risk indicator of the business object and determine whether the business object hits the abnormal business object list, through step S106. If the determination result is a normal risk indicator and the determination result is that no abnormal business object list is hit, the analysis server may consider that no risk exists in the business object; the normal condition can be used as a risk analysis result, and the risk analysis result can be fed back to the business server.
Step S110: and the analysis server sends an examination and management request to the examination and management server.
In some embodiments, the analysis server may determine the risk indicator of the business object and determine whether the business object hits the abnormal business object list, through step S106. If the determination result is an abnormal risk indicator and the determination result is a hit of an abnormal business object list, or if the determination result is an abnormal risk indicator and the determination result is no hit of an abnormal business object list, or if the determination result is a normal risk indicator and the determination result is a hit of an abnormal business object list, the analysis server may consider that the business object is suspected to have a risk; an audit request can be sent to the audit server so that the audit server can audit and verify whether the business object is real or not at risk. The audit request may include the determination result and the judgment result. Of course, the audit request may also include other content. For example, the audit request may also include the business data.
Step S112: the audit server receives the audit request.
Step S114: and if the judgment result is that the abnormal business object list is hit and the determination result is a normal risk index, the auditing server checks whether the business object really hits the abnormal business object list.
In some embodiments, it is considered that although the analysis server determines that the business object hits the abnormal business object list, in some cases (for example, the user is renamed), the business object may actually hit the abnormal business object list, or may not actually hit the abnormal business object list. Therefore, after receiving the audit request, if the judgment result is that the abnormal business object list is hit and the determination result is a normal risk indicator, the audit server may check whether the business object actually hits the abnormal business object list.
In practical applications, there may be various ways to check whether the service object actually hits the abnormal service object list. For example, the auditing server may provide the business object and a list of abnormal business objects in a list of abnormal business objects that match the business object to an auditor. And checking whether the business object really hits the abnormal business object list by the auditor. Specifically, for example, the auditing server may send the business object and an abnormal business object list matching the business object in the abnormal business object list to a specific server; the result of the audit entered by the auditor at a particular server may be received.
Step S116: and if the abnormal business object list is actually hit, the auditing server takes the abnormality as an auditing result to feed back.
In some embodiments, the audit server may check whether the business object actually hits the abnormal business object list through step S114. If the abnormal business object list is actually hit, the auditing server can consider that the business object has risk; the exception may be taken as an audit result, and the audit result may be fed back to the analysis server.
Step S118: and if the list of the abnormal business objects is not hit really, the auditing server judges whether the business objects hit the list of the suspected abnormal business objects or not.
In some embodiments, the list of suspected abnormal business objects may include at least one suspected abnormal business object. The suspected abnormal business object may refer to a business object suspected of having a risk, such as a business object suspected of suspected money laundering, a business object suspected of suspected fraud, and a business object suspected of suspected network gambling. Specifically, for example, considering that a PEP (political Exposed Persons) belongs to a person with a high risk of money laundering, the suspected abnormal business object may include the PEP.
In some embodiments, the audit server may check whether the business object actually hits the abnormal business object list through step S114. If the list of the abnormal business objects is not really hit, the examination and management server can match the business objects in the list of the suspected abnormal business objects; if one or more abnormal business objects are successfully matched, the fact that the business objects hit a suspected abnormal business object list can be judged; if one or more abnormal business objects are not matched, it can be judged that the business object does not hit the suspected abnormal business object list.
Step S120: and if the list of suspected abnormal business objects is not hit, the auditing server feeds back the normal business objects as auditing results.
In some embodiments, the auditing server may determine whether the business object hits in the list of suspected abnormal business objects, via step S118. If the list of suspected abnormal business objects is not hit, the auditing server can consider that the business objects have no risk; the normal condition can be used as an auditing result, and the auditing result can be fed back to the analysis server.
Step S122: and if the suspected abnormal business object list is hit, the auditing server checks whether the business object really has risk.
In some embodiments, the auditing server may determine whether the business object hits in the list of suspected abnormal business objects, via step S118. If the suspected abnormal business object list is hit, the examination and management server can consider that the business object is suspected to have a risk; it can be checked whether the business object is really at risk.
In practical applications, there may be various implementation manners to check whether the business object really has a risk. For example, the audit server may provide the business object (or business data related to the business object) to an audit person. And checking whether the business object really has risk or not by using an auditor in an EDD (Enhanced Dual Diligence) mode. Specifically, for example, the auditing server may send the business object to a specific server; the result of the audit entered by the auditor at a particular server may be received.
Step S124: if the risk exists, the auditing server takes the abnormity as an auditing result to feed back; or if no risk exists, the auditing server feeds back the normal auditing result; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
In some embodiments, the audit server may check whether the business object is really at risk, through step S122, or through step S126, or through step S130. If the risk exists, the auditing server can take the abnormity as an auditing result and can feed back the auditing result to the analysis server. Or, if there is no risk, the auditing server may use the normal auditing result as the auditing result, and may feed back the auditing result to the analysis server. Or, in some cases, partial data (e.g., identification card, business license, etc.) may be missing, such that the auditing server cannot determine whether the business object is in fact at risk. Therefore, the auditing server can take the identification of the data to be supplemented as an auditing result and can feed back the auditing result to the analysis server. The identification of the data to be supplemented may include, for example, the name, number, etc. of the data to be supplemented.
Step S126: and if the judgment result is that the abnormal business object list is not hit and the judgment result is the abnormal risk index, the auditing server checks whether the business object really has risk or not.
In some embodiments, it is considered that although the analysis server determines that the risk indicator of the business object is an abnormal risk indicator, the business object may or may not have a risk. Therefore, after receiving the audit request, if the judgment result is that the abnormal business object list is not hit and the determination result is an abnormal risk indicator, the audit server may check whether the business object really has a risk. The process of checking whether the business object really has a risk may refer to the foregoing step S122, which is not described herein again.
Step S128: and if the judgment result is that the abnormal business object list is hit and the judgment result is the abnormal risk level, the auditing server checks whether the business object really hits the abnormal business object list.
In some embodiments, it is considered that although the analysis server determines that the business object hits the abnormal business object list, in some cases (for example, the user is renamed), the business object may actually hit the abnormal business object list, or may not actually hit the abnormal business object list. Therefore, after receiving the audit request, if the judgment result is that the abnormal business object list is hit and the judgment result is the abnormal risk level, the audit server can check whether the business object really hits the abnormal business object list. The process of checking whether the business object actually hits the abnormal business object list may refer to the foregoing step S114, and details are not described here.
Step S130: and if the abnormal business object list is not truly hit, the auditing server checks whether the business object really has risk or not.
In some embodiments, the audit server may check whether the business object actually hits the abnormal business object list, via step S128. If the abnormal business object list is not hit really, the auditing server can check whether the business object really has risk or not. The process of checking whether the business object really has a risk may refer to the foregoing step S122, which is not described herein again.
It should be noted that, if the abnormal business object list is not actually hit, the auditing server may directly check whether the business object is actually at risk. Or, if the list of the abnormal business objects is not hit really, the auditing server can also judge whether the business objects hit the list of the suspected abnormal business objects; if the suspected abnormal business object list is not hit, whether the business object really has risk can be checked; if the suspected abnormal business object list is hit, whether the business object really has risk can be checked. For a specific process, refer to step S118, which is not described herein again.
Step S132: and if the abnormal business object list is actually hit, the auditing server takes the abnormality as an auditing result to feed back.
In some embodiments, the audit server may check whether the business object actually hits the abnormal business object list, via step S128. If the abnormal business object list is actually hit, the auditing server can consider that the business object has risk; the exception may be taken as an audit result, and the audit result may be fed back to the analysis server.
Step S134: and the analysis server feeds back the audit result as a risk analysis result.
In some embodiments, the audit server may feed back the audit result to the analysis server through step S116, or through step S120, or through step S124, or through step S132. The analysis server may receive an audit result; the audit result can be used as a risk analysis result, and the risk analysis result can be fed back to the service server.
Step S136: and the business server receives the risk analysis result.
In some embodiments, the analysis server may feed back the risk analysis result to the business server through step S108, or through step S134. The business server can receive a risk analysis result. The service server may perform a corresponding operation according to the received risk analysis result. For example, the business data may include transaction data. And if the risk analysis result is normal, the business server can normally execute the transaction according to the transaction data. If the risk analysis result is abnormal, the business server can refuse to execute the transaction; a prompt may be sent to the user's terminal device denying execution of the transaction.
In the data interaction method in the embodiment of the present specification, the service server may send a risk analysis request to the analysis server. The analysis server may receive a risk analysis request; the risk index of the business object can be determined; whether the business object hits the abnormal business object list or not can be combined; and the risk analysis result can be fed back to the service server in a unified way according to the judgment result and the determination result. Thus, the business server can quickly obtain the risk analysis result. Therefore, the business server can quickly determine whether the business object has risks. In addition, the risk analysis results are fed back to the service server in a unified mode, and the service server can be prevented from obtaining two completely opposite risk analysis results.
The present specification also provides another embodiment of a data interaction method. The data interaction method may be implemented by the analysis server in the embodiment corresponding to fig. 1. Referring to fig. 2, the data interaction method may include the following steps.
Step S202: a risk analysis request is received.
In some embodiments, the risk analysis request may include a business object to be analyzed. Specifically, after obtaining the business data, the business server may send a risk analysis request to the analysis server. The analysis server may receive the risk analysis request. Wherein, the risk analysis request may include the business data, and the business object to be analyzed may include a business object to which the business data relates.
Step S204: a risk indicator for the business object is determined.
The process of determining the risk indicator for a business object can be seen in the previous step S106.
Step S206: and judging whether the business object hits the abnormal business object list.
The process of determining whether the business object hits the abnormal business object list may refer to the previous step S106.
Step S208: and sending an auditing request to an auditing server according to the judgment result and the determination result.
In some embodiments, if the determination result is an abnormal risk indicator and the determination result is a hit abnormal business object list, or if the determination result is an abnormal risk indicator and the determination result is no hit abnormal business object list, or if the determination result is a normal risk indicator and the determination result is a hit abnormal business object list, the analysis server may consider that the business object is suspected to have a risk; an audit request can be sent to the audit server so that the audit server can audit and verify whether the business object is real or not at risk. The audit request may include the determination result and the judgment result. Of course, the audit request may also include other content. For example, the audit request may also include the business data.
Step S210: and receiving an auditing result fed back by the auditing server.
In some embodiments, the audit server may receive an audit request; the auditing request can be processed to obtain an auditing result; the audit results may be fed back to the analysis server. The analysis server may receive the audit result. The obtaining process of the trial result may refer to an embodiment corresponding to fig. 1.
Step S212: and feeding back the result of the trial and error as a risk analysis result.
In some embodiments, the analysis server may receive an audit result; the audit result can be used as a risk analysis result, and the risk analysis result can be fed back to the service server.
In some embodiments, if the determination result is a normal risk indicator and the determination result is that no abnormal business object list is hit, the analysis server may feed back the normal risk indicator as a risk analysis result.
In the data interaction method in the embodiment of the present specification, the service server may send a risk analysis request to the analysis server. The analysis server may receive a risk analysis request; the risk index of the business object can be determined; whether the business object hits an abnormal business object list can be judged; and the risk analysis result can be fed back to the service server in a unified way by combining the judgment result and the determination result. Thus, the business server can quickly obtain the risk analysis result. Thereby facilitating a quick determination of whether a business object is at risk. In addition, the risk analysis results are fed back to the service server in a unified mode, and the service server can be prevented from obtaining two completely opposite risk analysis results.
The present specification also provides another embodiment of a data interaction method. The data interaction method can be implemented by the auditing server in the embodiment corresponding to fig. 1. Referring to fig. 3, the data interaction method may include the following steps.
Step S302: and receiving a request for auditing.
In some embodiments, the analysis server may send an audit request to the audit server. The audit server may receive the audit request. The audit request may include a determination result and a determination result. The judgment result can be obtained by judging whether the service object hits the abnormal service object list. The determination may be obtained by determining a risk indicator of the business object. The process of obtaining the judgment result and the determination result may refer to the foregoing step S106.
Step S304: and if the judgment result is that the abnormal business object list is hit and the determination result is a normal risk index, checking whether the business object really hits the abnormal business object list.
The process of checking whether the business object actually hits the abnormal business object list may refer to the previous step S114.
Step S306: and if the abnormal business object list is actually hit, the abnormality is used as an auditing result for feedback.
In some embodiments, if the list of the abnormal business objects is not hit really, the auditing server may determine whether the business object hits the list of the suspected abnormal business objects; if the list of suspected abnormal business objects is not hit, the normal business objects can be used as an examination result for feedback; if the suspected abnormal business object list is hit, whether the business object really has risk can be checked.
And if the risk exists, the auditing server can feed back the abnormity as an auditing result. Or if no risk exists, the auditing server can feed back the normal auditing result. Or, if the data to be supplemented is not determined, the auditing server can take the identifier of the data to be supplemented as an auditing result to feed back.
In the data interaction method in the embodiments of the present description, the analysis server may send an audit request to the audit server. The examination and management server can receive an examination and management request; and uniformly feeding back the auditing result to the analysis server according to the determination result and the judgment result in the auditing request. This facilitates a quick determination of whether a business object is at risk.
The present specification also provides another embodiment of a data interaction method. The data interaction method can be implemented by the auditing server in the embodiment corresponding to fig. 1. Referring to fig. 4, the data interaction method may include the following steps.
Step S402: and receiving a request for auditing.
In some embodiments, the analysis server may send an audit request to the audit server. The audit server may receive the audit request. The audit request may include a determination result and a determination result. The judgment result can be obtained by judging whether the service object hits the abnormal service object list. The determination may be obtained by determining a risk indicator of the business object. The process of obtaining the judgment result and the determination result may refer to the foregoing step S106.
Step S404: and if the judgment result is that the abnormal business object list is not hit and the determination result is an abnormal risk index, checking whether the business object really has a risk or not.
The process of checking whether the business object is really at risk can be referred to the previous step S122.
Step S406: if the risk exists, the abnormity is used as an auditing result to be fed back; or if no risk exists, the normal condition is used as an auditing result for feedback; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
In the data interaction method in the embodiments of the present description, the analysis server may send an audit request to the audit server. The examination and management server can receive an examination and management request; and uniformly feeding back the auditing result to the analysis server according to the determination result and the judgment result in the auditing request. This facilitates a quick determination of whether a business object is at risk.
The present specification also provides another embodiment of a data interaction method. The data interaction method can be implemented by the auditing server in the embodiment corresponding to fig. 1. Referring to fig. 5, the data interaction method may include the following steps.
Step S502: and receiving a request for auditing.
In some embodiments, the analysis server may send an audit request to the audit server. The audit server may receive the audit request. The audit request may include a determination result and a determination result. The judgment result can be obtained by judging whether the service object hits the abnormal service object list. The determination may be obtained by determining a risk indicator of the business object. The process of obtaining the judgment result and the determination result may refer to the foregoing step S106.
Step S504: and if the judgment result is that the abnormal business object list is hit and the determination result is the abnormal risk level, checking whether the business object really hits the abnormal business object list.
The process of checking whether the business object actually hits the abnormal business object list may refer to the previous step S114.
Step S506: and if the abnormal business object list is actually hit, the abnormality is used as an auditing result for feedback.
In some embodiments, if there is no real hit on the abnormal business object list, the audit server may check whether the business object is really at risk. And if the risk exists, the auditing server can feed back the abnormity as an auditing result. Or if no risk exists, the auditing server can feed back the normal auditing result. Or, if the data to be supplemented is not determined, the auditing server can take the identifier of the data to be supplemented as an auditing result to feed back.
In the data interaction method in the embodiments of the present description, the analysis server may send an audit request to the audit server. The examination and management server can receive an examination and management request; and uniformly feeding back the auditing result to the analysis server according to the determination result and the judgment result in the auditing request. This facilitates a quick determination of whether a business object is at risk.
Please refer to fig. 6. This specification also provides one embodiment of a data interaction device. The data interaction device can be applied to an analysis server, and particularly comprises the following module units.
A first receiving module 602, configured to receive a risk analysis request, where the risk analysis request includes a business object to be analyzed;
a determining module 604, configured to determine a risk indicator of a business object;
a judging module 606, configured to judge whether the service object hits the abnormal service object list;
a sending module 608, configured to send an audit request to an audit server according to the determination result and the determination result;
the second receiving module 610 is configured to receive an audit result fed back by the audit server;
and a feedback module 612, configured to feed back the audit result as a risk analysis result.
Please refer to fig. 7. This specification also provides one embodiment of a data interaction device. The data interaction device can be applied to an auditing server and specifically comprises the following module units.
A receiving module 702, configured to receive an audit request, where the audit request includes a determination result and a determination result, the determination result is obtained by determining whether a service object hits an abnormal service object list, and the determination result is obtained by determining a risk indicator of the service object;
a checking module 704, configured to check whether the service object actually hits the list of abnormal service objects if the determination result is a normal risk indicator and the determination result is a hit abnormal service object list;
and the feedback module 706 is configured to feed back the exception as an audit result if the exception service object list is actually hit.
Please refer to fig. 8. This specification also provides one embodiment of a data interaction device. The data interaction device can be applied to an auditing server and specifically comprises the following module units.
A receiving module 802, configured to receive an audit request, where the audit request includes a determination result and a determination result, the determination result is obtained by determining whether a service object hits an abnormal service object list, and the determination result is obtained by determining a risk indicator of the service object;
the investigation module 804 is configured to check whether the business object really has a risk if the determination result is that the abnormal business object list is not hit and the determination result is an abnormal risk indicator;
a feedback module 806, configured to feed back, if there is a risk, the exception as an audit result; or if no risk exists, the normal condition is used as an auditing result for feedback; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
Please refer to fig. 9. This specification also provides one embodiment of a data interaction device. The data interaction device can be applied to an auditing server and specifically comprises the following module units.
A receiving module 902, configured to receive an audit request, where the audit request includes a determination result and a determination result, the determination result is obtained by determining whether a service object hits an abnormal service object list, and the determination result is obtained by determining a risk indicator of the service object;
an auditing module 904, configured to check whether the service object actually hits the list of abnormal service objects if the determination result is that the list of abnormal service objects is hit and the determination result is an abnormal risk level;
and the feedback module 906 is configured to, if the abnormal service object list is hit really, feed back the abnormality as an audit result.
An embodiment of an electronic device of the present description is described below. Fig. 10 is a schematic diagram of a hardware configuration of the electronic apparatus in this embodiment. As shown in fig. 10, the electronic device may include one or more processors (only one of which is shown), memory, and a transmission module. Of course, it is understood by those skilled in the art that the hardware structure shown in fig. 10 is only an illustration, and does not limit the hardware structure of the electronic device. In practice the electronic device may also comprise more or fewer component elements than those shown in fig. 10; or have a different configuration than that shown in fig. 10.
The memory may comprise high speed random access memory; alternatively, non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory may also be included. Of course, the memory may also comprise a remotely located network memory. The remotely located network storage may be connected to the electronic device through a network such as the internet, an intranet, a local area network, a mobile communications network, or the like. The memory may be used to store program instructions or modules of application software, such as the program instructions or modules of the embodiments corresponding to fig. 2-5 of the present specification.
The processor may be implemented in any suitable way. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth. The processor may read and execute the program instructions or modules in the memory.
The transmission module may be used for data transmission via a network, for example via a network such as the internet, an intranet, a local area network, a mobile communication network, etc.
This specification also provides one embodiment of a computer storage medium. The computer storage medium includes, but is not limited to, a Random Access Memory (RAM), a Read-Only Memory (ROM), a Cache (Cache), a Hard Disk (HDD), a Memory Card (Memory Card), and the like. The computer storage medium stores computer program instructions. The computer program instructions when executed implement: the program instructions or modules of the embodiments corresponding to fig. 2-5 of this specification.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and the same or similar parts in each embodiment may be referred to each other, and each embodiment focuses on differences from other embodiments. In particular, apparatus embodiments, electronic device embodiments, and computer storage medium embodiments are substantially similar to method embodiments and therefore are described with relative ease, where reference may be made to some descriptions of method embodiments. In addition, it is understood that one skilled in the art, after reading this specification document, may conceive of any combination of some or all of the embodiments listed in this specification without the need for inventive faculty, which combinations are also within the scope of the disclosure and protection of this specification.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most popular applications. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
From the above description of the embodiments, it is clear to those skilled in the art that the present specification can be implemented by software plus a necessary general hardware platform. Based on such understanding, the technical solutions of the present specification may be essentially or partially implemented in the form of software products, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The description is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
While the specification has been described with examples, those skilled in the art will appreciate that there are numerous variations and permutations of the specification that do not depart from the spirit of the specification, and it is intended that the appended claims include such variations and modifications that do not depart from the spirit of the specification.
Claims (15)
1. A data interaction method is applied to an analysis server and comprises the following steps:
receiving a risk analysis request, wherein the risk analysis request comprises a business object to be analyzed;
determining a risk index of a business object;
judging whether the business object hits an abnormal business object list or not;
sending an auditing request to an auditing server according to the judgment result and the determination result;
receiving an auditing result fed back by an auditing server;
and feeding back the result of the trial and error as a risk analysis result.
2. The method of claim 1, the risk analysis request comprising business data, the business object to be analyzed comprising a business object to which the business data relates.
3. The method of claim 1, wherein sending an audit request to an audit server comprises:
if the determined result is an abnormal risk index and the judged result is a hit abnormal business object list, sending an examination request to an examination server; or if the determined result is an abnormal risk index and the judging result is that the abnormal business object list is not hit, sending an examination and management request to an examination and management server; or if the determined result is a normal risk index and the determined result is a hit abnormal business object list, sending an examination request to an examination server.
4. The method of claim 1, further comprising:
and if the determined result is a normal risk index and the judging result is that the abnormal business object list is not hit, feeding back the normal risk index as a risk analysis result.
5. A data interaction method is applied to an auditing server and comprises the following steps:
receiving an auditing request, wherein the auditing request comprises a judgment result and a determination result, the judgment result is obtained by judging whether a business object hits an abnormal business object list, and the determination result is obtained by determining a risk index of the business object;
if the judgment result is that the abnormal business object list is hit and the determination result is a normal risk index, checking whether the business object really hits the abnormal business object list;
and if the abnormal business object list is actually hit, the abnormality is used as an auditing result for feedback.
6. The method of claim 5, further comprising:
if the list of the abnormal business objects is not hit really, judging whether the business objects hit the list of the suspected abnormal business objects;
and if the suspected abnormal business object list is not hit, the normal business object list is used as an auditing result to be fed back.
7. The method of claim 5, further comprising:
if the list of the abnormal business objects is not hit really, judging whether the business objects hit the list of the suspected abnormal business objects;
if the suspected abnormal business object list is hit, checking whether the business object really has risk;
if the risk exists, the abnormity is used as an auditing result to be fed back; or if no risk exists, the normal condition is used as an auditing result for feedback; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
8. A data interaction method is applied to an auditing server and comprises the following steps:
receiving an auditing request, wherein the auditing request comprises a judgment result and a determination result, the judgment result is obtained by judging whether a business object hits an abnormal business object list, and the determination result is obtained by determining a risk index of the business object;
if the judgment result is that the abnormal business object list is not hit and the determination result is an abnormal risk index, checking whether the business object really has a risk or not;
if the risk exists, the abnormity is used as an auditing result to be fed back; or if no risk exists, the normal condition is used as an auditing result for feedback; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
9. A data interaction method is applied to an auditing server and comprises the following steps:
receiving an auditing request, wherein the auditing request comprises a judgment result and a determination result, the judgment result is obtained by judging whether a business object hits an abnormal business object list, and the determination result is obtained by determining a risk index of the business object;
if the judgment result is that the abnormal business object list is hit and the determination result is the abnormal risk level, checking whether the business object really hits the abnormal business object list;
and if the abnormal business object list is actually hit, the abnormality is used as an auditing result for feedback.
10. The method of claim 9, further comprising:
if the abnormal business object list is not truly hit, checking whether the business object really has risk or not;
if the risk exists, the abnormity is used as an auditing result to be fed back; or if no risk exists, the normal condition is used as an auditing result for feedback; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
11. A data interaction device is applied to an analysis server and comprises:
the system comprises a first receiving module, a risk analysis module and a second receiving module, wherein the first receiving module is used for receiving a risk analysis request which comprises a business object to be analyzed;
the determining module is used for determining the risk index of the business object;
the judging module is used for judging whether the business object hits the abnormal business object list or not;
the sending module is used for sending an auditing request to the auditing server according to the judgment result and the determination result;
the second receiving module is used for receiving the auditing result fed back by the auditing server;
and the feedback module is used for feeding back the auditing result as a risk analysis result.
12. A data interaction device is applied to an examination server and comprises:
the system comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for receiving an auditing request, the auditing request comprises a judging result and a determining result, the judging result is obtained by judging whether a business object hits an abnormal business object list, and the determining result is obtained by determining a risk index of the business object;
the checking module is used for checking whether the business object really hits the abnormal business object list or not if the judging result is the hit abnormal business object list and the determining result is the normal risk index;
and the feedback module is used for feeding back the exception as an auditing result if the exception service object list is actually hit.
13. A data interaction device is applied to an examination server and comprises:
the system comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for receiving an auditing request, the auditing request comprises a judging result and a determining result, the judging result is obtained by judging whether a business object hits an abnormal business object list, and the determining result is obtained by determining a risk index of the business object;
the investigation module is used for checking whether the business object really has a risk or not if the judgment result is that the abnormal business object list is not hit and the determination result is an abnormal risk index;
the feedback module is used for feeding back the abnormity serving as an auditing result if the risk exists; or if no risk exists, the normal condition is used as an auditing result for feedback; or if the data to be supplemented is uncertain, the identification of the data to be supplemented is used as an auditing result to be fed back.
14. A data interaction device is applied to an examination server and comprises:
the system comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for receiving an auditing request, the auditing request comprises a judging result and a determining result, the judging result is obtained by judging whether a business object hits an abnormal business object list, and the determining result is obtained by determining a risk index of the business object;
the auditing module is used for checking whether the business object really hits the abnormal business object list or not if the judging result is that the abnormal business object list is hit and the determining result is that the abnormal risk level is found;
and the feedback module is used for feeding back the exception as an auditing result if the exception service object list is actually hit.
15. An electronic device, comprising:
at least one processor;
a memory storing program instructions configured for execution by the at least one processor, the program instructions comprising instructions for performing the method of any of claims 1-10.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010373229.5A CN111681005A (en) | 2020-05-06 | 2020-05-06 | Data interaction method and device and electronic equipment |
| PCT/CN2021/091053 WO2021223657A1 (en) | 2020-05-06 | 2021-04-29 | Data exchange |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010373229.5A CN111681005A (en) | 2020-05-06 | 2020-05-06 | Data interaction method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111681005A true CN111681005A (en) | 2020-09-18 |
Family
ID=72451718
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010373229.5A Pending CN111681005A (en) | 2020-05-06 | 2020-05-06 | Data interaction method and device and electronic equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111681005A (en) |
| WO (1) | WO2021223657A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021223657A1 (en) * | 2020-05-06 | 2021-11-11 | 支付宝(杭州)信息技术有限公司 | Data exchange |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110106725A1 (en) * | 2009-10-30 | 2011-05-05 | Sap Ag | Financial instrument position and subposition management |
| CN102194177A (en) * | 2011-05-13 | 2011-09-21 | 南京柯富锐软件科技有限公司 | System for risk control over online payment |
| US20120158732A1 (en) * | 2010-12-17 | 2012-06-21 | Microsoft Corporation | Business application publication |
| CN107169857A (en) * | 2017-07-14 | 2017-09-15 | 成都农村商业银行股份有限公司 | The customer risk ranking method of anti money washing system |
| CN107767021A (en) * | 2017-09-12 | 2018-03-06 | 阿里巴巴集团控股有限公司 | A kind of risk control method and equipment |
| US20180316668A1 (en) * | 2017-04-27 | 2018-11-01 | Mastercard International Incorporated | Systems and methods for improved electronic data security |
| CN109472610A (en) * | 2018-11-09 | 2019-03-15 | 福建省农村信用社联合社 | A kind of bank transaction is counter to cheat method and system, equipment and storage medium |
| CN109918408A (en) * | 2019-03-01 | 2019-06-21 | 成都农村商业银行股份有限公司 | A kind of blacklist update method, device, equipment and computer readable storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279883B (en) * | 2013-05-02 | 2016-06-08 | 上海携程商务有限公司 | Electronic-payment transaction risk control method and system |
| US10572877B2 (en) * | 2014-10-14 | 2020-02-25 | Jpmorgan Chase Bank, N.A. | Identifying potentially risky transactions |
| CN107644340A (en) * | 2016-07-22 | 2018-01-30 | 阿里巴巴集团控股有限公司 | Risk Identification Method, client device and risk recognition system |
| CN110020769A (en) * | 2018-12-19 | 2019-07-16 | 阿里巴巴集团控股有限公司 | A kind of business risk monitoring method, device and equipment |
| CN109784934A (en) * | 2019-03-14 | 2019-05-21 | 浙江鲸腾网络科技有限公司 | A kind of transaction risk control method, apparatus and relevant device and medium |
| CN111681005A (en) * | 2020-05-06 | 2020-09-18 | 支付宝(杭州)信息技术有限公司 | Data interaction method and device and electronic equipment |
-
2020
- 2020-05-06 CN CN202010373229.5A patent/CN111681005A/en active Pending
-
2021
- 2021-04-29 WO PCT/CN2021/091053 patent/WO2021223657A1/en active Application Filing
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110106725A1 (en) * | 2009-10-30 | 2011-05-05 | Sap Ag | Financial instrument position and subposition management |
| US20120158732A1 (en) * | 2010-12-17 | 2012-06-21 | Microsoft Corporation | Business application publication |
| CN102194177A (en) * | 2011-05-13 | 2011-09-21 | 南京柯富锐软件科技有限公司 | System for risk control over online payment |
| US20180316668A1 (en) * | 2017-04-27 | 2018-11-01 | Mastercard International Incorporated | Systems and methods for improved electronic data security |
| CN107169857A (en) * | 2017-07-14 | 2017-09-15 | 成都农村商业银行股份有限公司 | The customer risk ranking method of anti money washing system |
| CN107767021A (en) * | 2017-09-12 | 2018-03-06 | 阿里巴巴集团控股有限公司 | A kind of risk control method and equipment |
| CN109472610A (en) * | 2018-11-09 | 2019-03-15 | 福建省农村信用社联合社 | A kind of bank transaction is counter to cheat method and system, equipment and storage medium |
| CN109918408A (en) * | 2019-03-01 | 2019-06-21 | 成都农村商业银行股份有限公司 | A kind of blacklist update method, device, equipment and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021223657A1 (en) * | 2020-05-06 | 2021-11-11 | 支付宝(杭州)信息技术有限公司 | Data exchange |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021223657A1 (en) | 2021-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11308497B2 (en) | Detecting fraud using machine-learning | |
| US11184380B2 (en) | Security weakness and infiltration detection and repair in obfuscated website content | |
| CN109347787B (en) | Identity information identification method and device | |
| US20230070833A1 (en) | Detecting fraud using machine-learning | |
| CN110442712B (en) | Risk determination method, risk determination device, server and text examination system | |
| CN110474900B (en) | Game protocol testing method and device | |
| CN103685307A (en) | Method, system, client and server for detecting phishing fraud webpage based on feature library | |
| US10990940B1 (en) | Server validation of website scraped data | |
| CN102866932A (en) | Method and device for providing and collecting data related to abnormal terminal | |
| CN114519568A (en) | Order examination method and device, electronic equipment and storage medium | |
| CN114139161A (en) | Method, device, electronic equipment and medium for batch vulnerability detection | |
| CN111681005A (en) | Data interaction method and device and electronic equipment | |
| CN116107789A (en) | Method for monitoring and analyzing application fault reasons and storage medium | |
| CN113609020A (en) | Test case recommendation method and device | |
| CN117272308A (en) | Software security test method, device, equipment, storage medium and program product | |
| CN112085611A (en) | Asynchronous data verification method and device, electronic equipment and storage medium | |
| CN110675136A (en) | Information processing method, device and equipment | |
| CN108205757B (en) | Method and device for verifying legality of electronic payment service | |
| CN112182502B (en) | Compliance auditing method, device and equipment | |
| Li et al. | COBRA: Interaction-Aware Bytecode-Level Vulnerability Detector for Smart Contracts | |
| CN110674491A (en) | Method and device for real-time evidence obtaining of android application and electronic equipment | |
| CN112084106B (en) | Method and device for selecting test data, computing equipment and computer storage medium | |
| CN110349025B (en) | Method and device for preventing loss of contract assets based on non-cost transaction output | |
| CN116471131B (en) | Processing method and processing device for logical link information asset | |
| CN112632056B (en) | Method and device for generating inspection rule |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200918 |