CN106897807B - Business risk control method and equipment - Google Patents
Business risk control method and equipment Download PDFInfo
- Publication number
- CN106897807B CN106897807B CN201510958421.XA CN201510958421A CN106897807B CN 106897807 B CN106897807 B CN 106897807B CN 201510958421 A CN201510958421 A CN 201510958421A CN 106897807 B CN106897807 B CN 106897807B
- Authority
- CN
- China
- Prior art keywords
- rule
- rules
- synchronous
- rule base
- risk
- 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.)
- Active
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
- 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
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Operations Research (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Educational Administration (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a business risk control method, which not only executes risk on the current business according to rules in a synchronous rule base and judges and outputs a risk result, but also records the hit condition of each rule in the synchronous rule base, and also executes risk judgment on the current business according to the rules in an asynchronous rule base and records the hit condition of each rule in the asynchronous rule base, when the hit condition of a certain rule in the recorded asynchronous rule base reaches a first preset condition, the rule is added into the synchronous rule base, and when the hit condition of a certain rule in the recorded synchronous rule base is lower than a second preset condition, the rule is removed from the synchronous rule base. Therefore, on the premise of ensuring that the risk is controllable, the processing efficiency of business risk judgment is improved, and the labor cost and hardware resources required by business rule adjustment are effectively reduced.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a constant traffic risk control method. The application also relates to a business risk control device.
Background
In the process of people using the internet to obtain or provide services, there are always things that cannot be controlled, and these uncontrollable factors are called risks. Risks accompany the entire process of project execution, risk events bring negative factors such as increased project cost, slowed project progress, and impact on project completion quality, thereby affecting the expected revenue of investors.
Since risks are always associated with activities of people, people need to take various measures to reduce the possibility of occurrence of risk events or to control possible losses within a certain range so as to avoid the loss which is hard to bear when the risk events occur. The risk control system is a very important system for a financial enterprise. If there is no good risk control system, the company is exposed to a huge bankruptcy risk.
As shown in fig. 1, a schematic diagram of a risk control solution in the prior art is shown, where a business risk judgment process includes the following steps:
step a) the business system calls a risk control system (for example, transfer operation) before doing a certain business, and consults whether the operation is risky;
and b) calling a rule platform by the risk control system to judge whether the risk exists or not, and if so, returning the risk. If not, continuing to operate other risk control systems;
and c) the service system judges whether the user can execute the operation according to the risk judgment result.
In the process, when a rule management process is involved, the business system increases or decreases the rule through the rule management system according to the business requirement of the business system.
However, in the process of implementing the present application, the inventor finds that with the continuous development of the current internet service, there will be more and more risk systems for the service provider or the platform operator to access the service system. The number of corresponding rules may increase substantially, even to a level of the order of magnitude of a sea. Accordingly, the time for the risk system to perform the risk judgment becomes longer and longer, which may cause that certain services (such as payment, transfer, authentication, and the like) with high real-time requirements spend too much time on the risk judgment, and the use experience of the user is seriously affected.
Therefore, risk control and user experience are contradictory, and how to improve consultation processing efficiency aiming at risk events on the premise of ensuring safety becomes a technical problem to be solved urgently by technical personnel in the field.
Disclosure of Invention
The application provides a business risk control method, which is used for solving the problems of overlong query time, overhigh maintenance cost and the like caused by massive business rules in the prior art, and is applied to a risk control system and comprises the following steps:
performing risk judgment on the current service according to rules in the synchronous rule base, outputting a risk result, and recording the hit condition of each rule in the synchronous rule base;
performing risk judgment on the current service according to rules in an asynchronous rule base, and recording the hit condition of each rule in the asynchronous rule base, wherein the rules in the asynchronous rule base are a complete rule set for performing the risk judgment;
when the hit condition of a certain rule in the recorded asynchronous rule base reaches a first preset condition, adding the rule into a synchronous rule base;
and when the hit condition of a certain rule in the recorded synchronous rule base is lower than a second preset condition, removing the rule from the synchronous rule base.
Preferably, the current business performing risk judgment according to the rules in the synchronization rule base is a business with high real-time requirement.
Preferably, if the current service to be subjected to risk judgment is a service with low real-time requirement, performing risk judgment on the current service according to the rules in the asynchronous rule base, and outputting a risk result.
Preferably, the hit condition is specifically a ratio of the number of times the rule is used to perform the risk judgment to the number of times the rule currently performs the risk judgment in total.
Preferably, the method further comprises the following steps:
when a synchronous rule adding request is received, adding a rule carried in the synchronous rule adding request into the synchronous rule base;
when a synchronous rule removing request is received, rules corresponding to the rules carried in the synchronous rule removing request are removed from a synchronous rule base.
Correspondingly, the present application also provides a business risk control device, which is applied to a risk control system, and the device includes:
the first execution module is used for executing risk judgment on the current service according to the rules in the synchronous rule base, outputting a risk result and recording the hit condition of each rule in the synchronous rule base;
the second execution module is used for executing risk judgment on the current service according to the rules in the asynchronous rule base and recording the hit condition of each rule in the asynchronous rule base, wherein the rules in the asynchronous rule base are a complete rule set for executing the risk judgment;
the adding module is used for adding a rule in the synchronous rule base when the hit condition of the recorded rule in the asynchronous rule base reaches a first preset condition;
and the removing module is used for removing a rule from the synchronous rule base when the hit condition of the rule in the recorded synchronous rule base is lower than a second preset condition.
Preferably, the current business performing risk judgment according to the rules in the synchronization rule base is a business with high real-time requirement.
Preferably, if the current service to be subjected to risk judgment is a service with low real-time requirement, performing risk judgment on the current service according to the rules in the asynchronous rule base, and outputting a risk result.
Preferably, the hit condition is specifically a ratio of the number of times the rule is used to perform the risk judgment to the number of times the rule currently performs the risk judgment in total.
Preferably, the method further comprises the following steps:
when the adding module receives a synchronous rule adding request, the adding module adds a rule carried in the synchronous rule adding request to the synchronous rule base;
when the removing module receives a synchronous rule removing request, the removing module removes rules corresponding to the rules carried in the synchronous rule removing request from a synchronous rule base.
Therefore, by applying the technical scheme of the application, in addition to performing risk on the current service according to the rules in the synchronous rule base and judging the hit condition of each rule in the synchronous rule base while outputting the risk result, the risk judgment on the current service is performed according to the rules in the asynchronous rule base, the hit condition of each rule in the asynchronous rule base is recorded, the rule is added to the synchronous rule base when the hit condition of a certain recorded rule in the asynchronous rule base reaches a first preset condition, and the rule is removed from the synchronous rule base when the hit condition of a certain recorded rule in the synchronous rule base is lower than a second preset condition. Therefore, on the premise of ensuring that the risk is controllable, the processing efficiency of business risk judgment is improved, and the labor cost and hardware resources required by business rule adjustment are effectively reduced.
Drawings
FIG. 1 is a schematic diagram of a prior art risk control solution;
fig. 2 is a schematic flow chart of a business risk control method proposed in the present application;
fig. 3 is a schematic diagram of a business risk control scheme according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a business risk control device according to the present application.
Detailed Description
As described in the background art, when the rules become more and more along with the development of the business, too many rules bring the disadvantage of too long consultation time, and how to adjust and maintain the massive business rules according to the consultation condition of the business is also a problem that technicians need to additionally consider. Especially, in the existing network operation platform, the long time for the service system risk judgment will cause a serious user experience degradation problem when the service is highly concurrent and the requirement on real-time performance is high.
In order to solve the technical problem, the application provides a business risk control method, which is based on the rules in the existing risk control system, and the method respectively sets a synchronous rule base and an asynchronous rule base aiming at all the rules currently used for executing risk judgment. The rules in the synchronous rule base are rules that are run in real time and are subsequently allowed to run when risk judgment is performed on the business, and the rules in the asynchronous rule base are a complete rule set for performing risk judgment, for example, all currently existing rules for performing risk judgment, or all rules specified by a technician and required for performing risk judgment, relative to the rules in the synchronous rule base. By dividing the business rules in the business rule base into the synchronous rule base and the asynchronous rule base, the business rules with different timeliness and importance can be effectively distinguished.
In a preferred embodiment of the present application, the rules in the synchronization rule base include both a rule that a hit condition reaches a first preset condition (the first preset condition may be a threshold value set by a technician according to an actual situation), and a rule that is specified in advance by a technician, on the basis of which the technician may further improve and expand the division and setting of the rule, which all belong to the scope of the present application.
Based on the above arrangement, as shown in fig. 2, a schematic flow diagram of a business risk control method provided by the present application is shown, where the method includes the following steps:
s201, according to the rules in the synchronous rule base, risk judgment is carried out on the current business, a risk result is output, and the hit condition of each rule in the synchronous rule base is recorded.
The risk control system is provided with a port capable of being connected with the existing service system, and can acquire services needing risk judgment (hereinafter collectively referred to as current services) from the service system according to different protocols. In a specific application scenario, when a business system needs to perform risk judgment for a certain business, the current business can be sent to the risk control system in a manner of a risk judgment request, and the risk control system can obtain the current business needing risk judgment by analyzing the risk judgment request.
In order to avoid the situation of hit judgment for all business rules in the prior art, the preferred embodiment additionally sets a synchronization rule base in the risk control system, and places some important rules in the existing rules in the synchronization rule base. The rules are inquired and hit in the conventional business risk judgment process, the respective hit conditions of the rules reach a first preset condition, and the first preset condition can be flexibly adjusted by technical personnel according to actual conditions, so that the quantity of all specific business rules in the synchronous rule base can be kept at a level which can be quickly executed in batches and can cover basic needs of users. Therefore, when the risk judgment is needed for the current service, the method and the device enable the relevant equipment (such as the server) to execute the rules in the synchronous rule base, so that the risk judgment result of the current service can be obtained on the basis of ensuring the safety and the operation efficiency.
It should be noted that, when the business risk control method provided by the present application is operated for the first time, the hit condition of each business rule in the business rule base may be set by a technician according to past experience, or set as an average value, and may be adjusted or kept unchanged according to the query result in the subsequent process. Compared with a scheme which remains unchanged, the method for dynamically adjusting the hit condition of each business rule according to the query result can undoubtedly adapt to the processing environment of diversified business, and the method belongs to the protection scope of the application.
S202, performing risk judgment on the current service according to rules in the asynchronous rule base, and recording the hit condition of each rule in the asynchronous rule base, wherein the rules in the asynchronous rule base are a complete rule set for performing the risk judgment.
The method and the device realize the fast hit processing of the business rules by only executing the rules in the synchronous rule base, but in order to adapt to the existing ever-changing business processing environment, the method and the device also adjust the hit conditions of all the rules based on all the rules in the current asynchronous rule base and the hit conditions of the current tasks, so after the rules in the synchronous rule base are operated, the step executes risk judgment according to all the rules currently existing in the asynchronous rule base, and records the hit conditions of all the rules in the asynchronous rule base. Therefore, a processing basis is provided for the adjustment of the rule in the service rule base.
Through S201 and S202, the current business is rapidly processed, and the accuracy of risk judgment is guaranteed. However, in practical application scenarios, services with high real-time performance (such as transfer services, payment services, etc.) and services with low real-time performance (such as inquiry, retrieval, etc.) are often included. In order to consider the processing efficiency and the accuracy of risk judgment, the preferred embodiment of the present application screens the current service that needs to perform risk judgment according to the rules in the synchronization rule base, so that the current service that performs risk judgment according to the rules in the synchronization rule base is a service with high real-time requirements. Further, when the current service to be subjected to risk judgment is a service with low real-time requirement, performing risk judgment on the current service according to the rules in the asynchronous rule base, and outputting a risk result.
S203, when the hit condition of a certain rule in the recorded asynchronous rule base reaches a first preset condition, adding the rule to a synchronous rule base;
s204, when the hit condition of a certain rule in the recorded synchronous rule base is lower than a second preset condition, the rule is removed from the synchronous rule base.
When the hit conditions of all currently existing business rules need to be adjusted according to the obtained result, a person skilled in the art may first update the hit times of the hit business rules, and then adjust the hit conditions of the business rules based on the ratio of the number of times that the business rules have been used for performing risk judgment in the past to the number of times that the business rules currently perform risk judgment in total. On the basis of the above, the person skilled in the art can adopt other solutions to achieve the same goal of adjusting the hit condition, and these solutions are all within the scope of protection of the present application.
After dynamically adjusting the hit conditions of all current business rules, the preferred embodiment of the present application further provides a specific scheme for adjusting the rules in the synchronization rule base: when a preset adjusting period is reached, adding a certain rule of which the hit condition in the recorded asynchronous rule base reaches a first preset condition into the synchronous rule base, and removing a certain rule of which the hit condition in the recorded synchronous rule base is lower than a second preset condition from the synchronous rule base.
It should also be noted that the adjustment of the rules based on the hit condition of each rule is only a preferred embodiment of the present application, and the adjustment may be performed at any time while the current business is processed or after the current business is processed, and does not conflict with the risk judgment of the current business, or may be performed uniformly after a certain processing period is separated, which all belong to the protection scope of the present application.
In addition, although the above embodiments of the present application propose a scheme for adjusting rules in the synchronization rule base according to a hit condition, in addition to automatically scheduling real-time online and offline rules by the monitoring system, the rules in the synchronization rule base may also be scheduled in a manual setting manner. Specifically, in a preferred embodiment of the present application, when a technician needs to set a certain rule as a rule running in real time, a rule adding request carrying the rule may be sent, and when a synchronization rule adding request is received, the rule carried in the synchronization rule adding request is added to the synchronization rule base; and when a synchronization rule removal request is received, rules corresponding to the rules carried in the synchronization rule removal request are removed from the synchronization rule base.
To further illustrate the technical idea of the present application, the technical solution of the present application will now be described with reference to a specific application scenario as shown in fig. 3. The following is an illustration of the various systems in FIG. 3:
a service system: various service systems, such as payment systems, fund management systems, and the like, provide various services.
A risk control system: and providing a risk judgment service for each business system.
The synchronization rule system comprises: the rule running system for the business operation with high real-time requirement is provided, and the running rules of the system only comprise partial rules.
An asynchronous rule system: the method is provided for a rule running system when business operation without real-time requirement is carried out. The system operation rules include all rules.
The rule monitoring system comprises: the system is used for monitoring the hit condition of each rule and scheduling and modifying whether the rule operates synchronously or asynchronously according to the hit condition of the rule.
Based on the above system, the dynamic adjustment for the business rule in this embodiment is divided into the following two aspects:
setting of rule monitoring system
And monitoring the hit condition of each rule through a rule monitoring system. If certain rules are hit more frequently when a risk occurs, then the rules are added to the system running synchronously. With the development of business, the number of times that the rule is hit in the synchronous system is reduced to 0, and the rule is moved back to the asynchronous system to run.
Second, operation setting of business rules
The rules are divided into synchronous and asynchronous systems to run: synchronous systems and asynchronous systems. When the real-time requirement is high, if the payment service is carried out, the risk judgment is carried out, and only the synchronous rule is operated. And returns the synchronous operation result to the service system immediately. But still hands the business consultation to the asynchronous rule system running to check if there is a rule hit. The monitoring system can adjust the real-time operation rule according to the hit condition conveniently. And when the requirement on real-time operation is not high, calling the asynchronous system.
By adopting the technical scheme of the embodiment, the whole risk judgment system is divided into the synchronous system and the asynchronous system, and only the business rules in the synchronous system are operated when the task of risk judgment is received, so that the problem caused by excessive business rules is solved.
In order to achieve the above technical objective, the present application further provides a business risk control device, as shown in fig. 4, the device is applied in a risk control system, and includes:
the first execution module 410 performs risk judgment on the current service according to the rules in the synchronous rule base, outputs a risk result, and records the hit condition of each rule in the synchronous rule base;
the second execution module 420 executes risk judgment on the current service according to rules in the asynchronous rule base, and records the hit condition of each rule in the asynchronous rule base, wherein the rules in the asynchronous rule base are a complete rule set for executing the risk judgment;
the adding module 430 is used for adding a rule in the recorded asynchronous rule base to the synchronous rule base when the hit condition of the rule reaches a first preset condition;
and the removing module 440 is configured to remove a rule from the synchronization rule base when the hit condition of the rule in the recorded synchronization rule base is lower than a second preset condition.
In a specific application scenario, the current service performing risk judgment according to the rule in the synchronous rule base is a service with high real-time requirement.
In a specific application scenario, if the current service to be subjected to risk judgment is a service with low real-time requirement, performing risk judgment on the current service according to rules in the asynchronous rule base, and outputting a risk result.
In a specific application scenario, the hit condition is specifically a ratio of the number of times that the rule is used to perform risk judgment to the number of times that the rule currently performs risk judgment in total.
In a specific application scenario, the method further includes:
when the adding module receives a synchronous rule adding request, the adding module adds a rule carried in the synchronous rule adding request to the synchronous rule base;
when the removing module receives a synchronous rule removing request, the removing module removes rules corresponding to the rules carried in the synchronous rule removing request from a synchronous rule base.
By applying the technical scheme of the application, in addition to executing risk on the current service according to the rules in the synchronous rule base and judging and outputting a risk result, the method records the hit condition of each rule in the synchronous rule base, also executes risk judgment on the current service according to the rules in the asynchronous rule base, records the hit condition of each rule in the asynchronous rule base, adds a certain rule in the synchronous rule base when the recorded hit condition of the certain rule in the asynchronous rule base reaches a first preset condition, and eliminates the rule from the synchronous rule base when the recorded hit condition of the certain rule in the synchronous rule base is lower than a second preset condition. Therefore, on the premise of ensuring that the risk is controllable, the processing efficiency of business risk judgment is improved, and the labor cost and hardware resources required by business rule adjustment are effectively reduced.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by hardware, and also by software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the implementation scenarios of the present application.
Those skilled in the art will appreciate that the figures are merely schematic representations of one preferred implementation scenario and that the blocks or flow diagrams in the figures are not necessarily required to practice the present application.
Those skilled in the art will appreciate that the modules in the devices in the implementation scenario may be distributed in the devices in the implementation scenario according to the description of the implementation scenario, or may be located in one or more devices different from the present implementation scenario with corresponding changes. The modules of the implementation scenario may be combined into one module, or may be further split into a plurality of sub-modules.
The above application serial numbers are for description purposes only and do not represent the superiority or inferiority of the implementation scenarios.
The above disclosure is only a few specific implementation scenarios of the present application, but the present application is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present application.
Claims (8)
1. A business risk control method is applied to a risk control system, and is characterized by comprising the following steps:
performing real-time synchronous risk judgment on the current service according to rules in a synchronous rule base, outputting a risk result, and recording the hit condition of each rule in the synchronous rule base;
executing asynchronous risk judgment on the current service according to rules in an asynchronous rule base, and recording the hit condition of each rule in the asynchronous rule base, wherein the rules in the asynchronous rule base are a complete rule set for executing risk judgment;
when the hit condition of a certain rule in the recorded asynchronous rule base reaches a first preset condition, adding the rule into a synchronous rule base;
when the hit condition of a certain rule in the recorded synchronous rule base is lower than a second preset condition, removing the rule from the synchronous rule base, wherein,
the rules in the synchronous rule base are partial rules which are important in the complete rule set, the rules are inquired and hit in the conventional business risk judgment process, the respective hit conditions of the rules reach the first preset condition, and the hit conditions are specifically the ratio of the times of executing risk judgment of the rules in the past to the times of executing the risk judgment at present in total.
2. The method of claim 1, wherein the current business that performs risk determination based on rules in the synchronization rule base is a business with high real-time requirements.
3. The method of claim 1, wherein if the current service to be subjected to risk judgment is a service with low real-time requirement, performing risk judgment on the current service according to rules in the asynchronous rule base, and outputting a risk result.
4. The method of claim 1, further comprising:
when a synchronous rule adding request is received, adding a rule carried in the synchronous rule adding request into the synchronous rule base;
when a synchronous rule removing request is received, rules corresponding to the rules carried in the synchronous rule removing request are removed from a synchronous rule base.
5. A business risk control device applied to a risk control system is characterized by comprising:
the first execution module executes real-time synchronous risk judgment on the current service according to the rules in the synchronous rule base, outputs a risk result and records the hit condition of each rule in the synchronous rule base;
the second execution module is used for executing asynchronous risk judgment on the current service according to the rules in the asynchronous rule base and recording the hit condition of each rule in the asynchronous rule base, wherein the rules in the asynchronous rule base are a complete rule set for executing risk judgment;
the adding module is used for adding a rule in the synchronous rule base when the hit condition of the recorded rule in the asynchronous rule base reaches a first preset condition;
a removing module for removing a rule from the synchronous rule base when the hit condition of the rule in the recorded synchronous rule base is lower than a second preset condition, wherein,
the rules in the synchronous rule base are partial rules which are important in the complete rule set, the rules are inquired and hit in the conventional business risk judgment process, the respective hit conditions of the rules reach the first preset condition, and the hit conditions are specifically the ratio of the times of executing risk judgment of the rules in the past to the times of executing the risk judgment at present in total.
6. The apparatus of claim 5, wherein the current business that performs risk determination based on rules in the synchronization rule base is a business with high real-time requirements.
7. The apparatus according to claim 5, wherein if the current service to be subjected to risk judgment is a service with low real-time requirement, performing risk judgment on the current service according to the rules in the asynchronous rule base, and outputting a risk result.
8. The apparatus of claim 5, further comprising:
when the adding module receives a synchronous rule adding request, the adding module adds a rule carried in the synchronous rule adding request to the synchronous rule base;
when the removing module receives a synchronous rule removing request, the removing module removes rules corresponding to the rules carried in the synchronous rule removing request from a synchronous rule base.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510958421.XA CN106897807B (en) | 2015-12-18 | 2015-12-18 | Business risk control method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510958421.XA CN106897807B (en) | 2015-12-18 | 2015-12-18 | Business risk control method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106897807A CN106897807A (en) | 2017-06-27 |
| CN106897807B true CN106897807B (en) | 2021-01-26 |
Family
ID=59189826
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510958421.XA Active CN106897807B (en) | 2015-12-18 | 2015-12-18 | Business risk control method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106897807B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107886431A (en) * | 2017-10-18 | 2018-04-06 | 上海瀚银信息技术有限公司 | Financial air control system based on big data and artificial intelligence |
| CN108985559A (en) * | 2018-06-08 | 2018-12-11 | 平安科技（深圳）有限公司 | Air control data processing method, device, computer equipment and storage medium |
| CN110798427A (en) * | 2018-08-01 | 2020-02-14 | 深信服科技股份有限公司 | Anomaly detection method, device and equipment in network security defense |
| CN110728436B (en) * | 2019-09-24 | 2022-06-10 | 支付宝(杭州)信息技术有限公司 | Risk identification method and device, electronic equipment and system |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101504745A (en) * | 2008-12-04 | 2009-08-12 | 阿里巴巴集团控股有限公司 | Risk regulation/model establishing and optimizing system and method based on network on-line service |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100088177A1 (en) * | 2008-10-02 | 2010-04-08 | Turn Inc. | Segment optimization for targeted advertising |
| CN101976419A (en) * | 2010-10-19 | 2011-02-16 | 中国工商银行股份有限公司 | Processing method and system for risk monitoring and controlling of transaction data |
| CN104376365B (en) * | 2014-11-28 | 2018-01-09 | 国家电网公司 | A kind of building method in the information system operation rule storehouse based on association rule mining |
-
2015
- 2015-12-18 CN CN201510958421.XA patent/CN106897807B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101504745A (en) * | 2008-12-04 | 2009-08-12 | 阿里巴巴集团控股有限公司 | Risk regulation/model establishing and optimizing system and method based on network on-line service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106897807A (en) | 2017-06-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106897807B (en) | Business risk control method and equipment | |
| WO2017096835A1 (en) | Service upgrade method and system for server group | |
| US20150254090A1 (en) | System and method for modifying allocated resources | |
| CN108197486A (en) | Big data desensitization method, system, computer-readable medium and equipment | |
| US20120128147A1 (en) | User-defined system-enforced session termination in a unified telephony environment | |
| CN106685894B (en) | Risk identification method, device and system | |
| CN111158926B (en) | Service request analysis method, device and equipment | |
| CN107872503B (en) | Firewall session number monitoring method and device | |
| CN115270187A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN109711666A (en) | A kind of technical supervision evaluation method and system based on criterion and quantity | |
| CN109726548B (en) | Application program behavior processing method, server, system and storage medium | |
| WO2019061999A1 (en) | Breakpoint call method, electronic device and computer-readable storage medium | |
| CN114529210A (en) | Evaluation method and device based on virtual reality | |
| CN108509560B (en) | User similarity obtaining method and device, equipment and storage medium | |
| CN106909832A (en) | The installation method and device of a kind of application program | |
| CN107566187B (en) | SLA violation monitoring method, device and system | |
| US10397312B2 (en) | Automated server deployment platform | |
| CN109492015A (en) | The method and apparatus of acquisition and show activity session complete information in real time | |
| Tamzil et al. | Security Utilization Of Cloud Computing In The World Of Business For Small Medium Enterprises (SMES) | |
| US9509578B1 (en) | Method and apparatus for determining a transaction parallelization metric | |
| CN108052922A (en) | A kind of intelligent security guard training method, apparatus and system | |
| CN109962938B (en) | Data updating and accessing method and device and cluster system | |
| CN110933624B (en) | Complaint processing method and device for unlimited package users | |
| US20220345472A1 (en) | Intelligent monitoring and logging platform | |
| CN106993297B (en) | Method and device for determining cell to be optimized |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200918 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200918 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |