CN116719751A - Method and system for checking service loss in real time - Google Patents
Method and system for checking service loss in real time Download PDFInfo
- Publication number
- CN116719751A CN116719751A CN202311011335.9A CN202311011335A CN116719751A CN 116719751 A CN116719751 A CN 116719751A CN 202311011335 A CN202311011335 A CN 202311011335A CN 116719751 A CN116719751 A CN 116719751A
- Authority
- CN
- China
- Prior art keywords
- service
- snapshot
- checking
- service node
- loss
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000012545 processing Methods 0.000 claims abstract description 31
- 238000003860 storage Methods 0.000 claims abstract description 15
- 230000000903 blocking effect Effects 0.000 claims description 8
- 230000001960 triggered effect Effects 0.000 claims description 4
- 230000001360 synchronised effect Effects 0.000 claims description 3
- 230000006735 deficit Effects 0.000 claims 3
- 238000004519 manufacturing process Methods 0.000 abstract description 5
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000012360 testing method Methods 0.000 description 14
- 238000004364 calculation method Methods 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 3
- 238000012550 audit Methods 0.000 description 3
- 238000013515 script Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- ZLIBICFPKPWGIZ-UHFFFAOYSA-N pyrimethanil Chemical compound CC1=CC(C)=NC(NC=2C=CC=CC=2)=N1 ZLIBICFPKPWGIZ-UHFFFAOYSA-N 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000005728 strengthening Methods 0.000 description 1
- 238000010998 test method Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/128—Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
Abstract
The invention relates to a service resource loss discovery technology, and discloses a method and a system for checking service resource loss in real time, wherein the method comprises the steps that key nodes of each service flow acquire service node snapshots generated by current service nodes; storing the obtained service node snapshot into a storage medium; defining a service trigger mechanism according to the generation mark of the service node snapshot; triggering real-time checking by loading data checking rules of different service nodes and service node snapshots; executing a comparison result of the service node snapshot through the check engine; synchronizing the comparison result to business resource loss processing when the comparison result has resource loss; otherwise, the business real-time check is finished; when checking and finding the service loss, the service loss is processed through the alarm notification. The method has real-time performance, can be synchronously executed in the production environment and the business software system, and can find the business resource loss capacity in real time, thereby greatly reducing the business loss caused by faults.
Description
Technical Field
The invention relates to a service resource loss discovery technology, in particular to a method and a system for checking service resource loss in real time.
Background
Business funds lost by a software system refers to funds lost in business due to logical errors or defects in a computer program.
This loss may be caused by:
error calculation logic: erroneous calculation logic in the computer code may result in funds calculation errors, such as erroneous profit calculations, erroneous cost calculations, and thus funds losses.
Data processing errors: data processing errors in the code logic may lead to inaccuracies in the funds data, such as erroneous account balance calculations, erroneous transaction data processing, and thus to lost funds or erroneous decisions.
Security vulnerabilities and fraud: security holes present in code logic may be exploited resulting in theft, manipulation, or transfer of funds. At the same time, fraud in the code logic may also result in funds loss, such as unauthorized funds transfer or transaction operations.
Transaction errors and system failures: errors in the code logic may cause transactions to execute incorrectly, e.g., incorrect transaction confirmation, incorrect settlement operations, and thus result in a loss of funds.
In addition, system failures or crashes may also result in transactions being unable to complete or data being lost, thereby resulting in a loss of funds. Third party interface integration problem: integration with third party interfaces in code logic may present problems such as data transmission errors, data format mismatches, resulting in funds transaction interruptions or errors.
To reduce the business funds lost by the computer code logic, the enterprise may take the following actions:
stringent code reviews and tests: code is subjected to strict examination and testing, including logic testing, boundary testing, exception handling testing, to ensure correctness and stability of code logic.
Strengthening safety measures: the code security audit and vulnerability scanning are enhanced, the potential security vulnerability is repaired, and the code security is ensured. In addition, authentication, authorization, and access control security measures are implemented to prevent unauthorized funding operations.
Real-time monitoring and alerting: a real-time monitoring and alarming system is established, abnormal transaction, abnormal data processing or system fault problems are found in time, and measures are rapidly taken to solve the problems, so that the fund loss is reduced.
And (3) establishing a strong internal control and audit system: internal control and audit regimes including rights management, data auditing, transaction auditing are established to ensure proper execution of code logic and security of funds. By taking the above measures, enterprises can reduce to some extent the risk of lost business funds caused by computer code logic.
As in the prior art, CN201911102295.2 cannot perform service resource discovery and check in real time.
Disclosure of Invention
Aiming at the expert experience of the test classmates in the prior art on the service loss technology, the invention constructs enough test case coverage after the test classmates fully analyze the test scene; in the process, the insufficient coverage of the service scene is probably caused by insufficient experience and analysis omission, and the service resource loss problem in certain scenes can not be found; hysteresis of production environment problem discovery: conventional testing methods may leave problems to the production environment due to test omission, and offline SQL verification has hysteresis at least at an hour level as a post-discovery means, thereby causing problems to be amplified in the production environment and causing huge business loss. The prior art is to find out the problem of service loss, but does not provide an effective loss stopping method, and provides a method and a system for checking service loss in real time.
In order to solve the technical problems, the invention is solved by the following technical scheme:
a method of real-time reconciling business costs, the method comprising:
acquiring service node snapshots, namely acquiring service node snapshots generated by a current service node at key nodes of each service flow;
storing the service node snapshot, and storing the acquired service node snapshot into a storage medium;
triggering the real-time checking service by loading data checking rules of different service nodes and service node snapshots;
comparing the service node snapshots, and executing a comparison result of acquiring the service node snapshots through a check engine; synchronizing the comparison result to business resource loss processing when the comparison result has resource loss; otherwise, the business real-time check is finished;
and (5) service loss processing, wherein when the check finds that the service loss processing is received, the service loss is processed through alarm notification.
Preferably, the method further comprises blocking of service execution, and when the comparison result is found to have resource loss, the service execution is blocked through automation.
Preferably, the storing of the service node snapshot includes:
receiving service node snapshot template information, and receiving a service node snapshot template information request;
writing in service nodes and service node snapshots, and writing in service nodes and service node snapshots;
inquiring the service node snapshot list, and inquiring the service node snapshot list for the written service node snapshot;
judging the synchronization state of the service node snapshots, judging the synchronization state of the service node snapshots for the queried service node snapshot list, and when all the node snapshots are in the synchronization state, adding a timing checking task and triggering; otherwise, checking the snapshot timeout time of the service node;
checking the service node snapshot timeout time, judging timeout for unsynchronized service node snapshots, outputting a warning when the service node snapshots timeout, otherwise, judging checking tasks; checking task judgment, and when the service node snapshot is not overtime and all nodes are synchronized, adding a checking task and triggering;
newly adding and triggering a checking timing task, and pulling a snapshot list and executing a checking rule after the checking timing task is triggered; after the checking rule is executed, if judging whether the business resource loss exists, sending out a warning and manually processing if the business resource loss exists; otherwise, checking the timing task to end.
Preferably, the triggering of the real-time check service includes:
acquiring a service node snapshot list, checking a service in real time and transmitting the service into a node type, thereby acquiring the service node snapshot list;
judging a service node snapshot list, determining whether service snapshots are collected according to the obtained service node snapshot list, and obtaining service snapshot template information when the service snapshots are collected; otherwise, giving out a warning;
acquiring service snapshot template information, wherein the service snapshot template information comprises service snapshot rules, service snapshot rule expression templates and service snapshot rule factors;
assembling the service snapshot template information, and assembling the acquired service snapshot template information;
executing the business snapshot rule, and executing the rule on the assembled business snapshot template information;
and judging the resource loss, judging the resource loss according to a service snapshot rule, triggering service blocking or sending alarm information and manually processing when the resource loss exists, and otherwise, checking that the triggering of the service is completed in real time.
Preferably, the service node snapshot is acquired through an SDK or API mode.
Preferably, the storage of the service node snapshot is stored in the form of a service node data structure.
Preferably, the comparison method of the service node snapshots adopts dynamic scripts.
In order to solve the above technical problems, the present invention also provides a system for checking service loss in real time, which includes a system for implementing a method for checking service loss in real time;
the service node snapshot acquiring unit acquires service node snapshots generated by the current service node at key nodes of each service flow;
the storage unit of the service node snapshot stores the acquired service node snapshot into a storage medium;
the triggering unit of the real-time checking service triggers the real-time checking service by loading data checking rules of different service nodes and service node snapshots;
the comparison unit of the service node snapshot is used for obtaining a comparison result of the service node snapshot through the execution of the check engine; synchronizing the comparison result to business resource loss processing when the comparison result has resource loss; otherwise, the business real-time check is finished;
and the service loss processing unit is used for processing the service loss through the alarm notification when checking and finding that the service loss processing is received.
The invention has the remarkable technical effects due to the adoption of the technical scheme:
the invention is based on the data check generated by the service system, and does not need to construct a complex service test scene and concurrent/distributed;
compared with service scene analysis and use case coverage, the method has the advantages that the required expert experience is less for analysis and coverage of software target data, the requirements on test classmates are lower, and the test cost is lower;
the invention has real-time performance, is synchronously executed in the production environment and the business software system, and compensates for the real-time discovery capability which is not possessed by the conventional test method, thereby greatly reducing the business loss caused by faults.
Drawings
Fig. 1 is a flow chart of the present invention.
Figure 2 is a flow chart of the storage of a snapshot of a service node of the present invention.
Fig. 3 is a flow chart of triggering of the real-time collation service of the present invention.
Fig. 4 is a flowchart of embodiment 4 of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples.
Example 1
A method of real-time reconciling business costs, the method comprising:
acquiring service node snapshots, namely acquiring service node snapshots generated by a current service node at key nodes of each service flow;
storing the service node snapshot, and storing the acquired service node snapshot into a storage medium;
triggering the real-time checking service by loading data checking rules of different service nodes and service node snapshots;
the comparison of the service node snapshots is carried out, and the comparison result of the service node snapshots is obtained through a checking engine; synchronizing the comparison result to business resource loss processing when the comparison result has resource loss; otherwise, the business real-time check is finished; analyzing the data snapshot to obtain an upstream and downstream data consistency comparison result. The collation engine uses dynamic scenario engine parsing tool to support dynamic loading execution of collation scripts. The implementation in this embodiment uses the Ali open source tool QLExPress, alternatively Groovy, scala or JRuby.
And processing the service loss, and when the service loss is received, processing the service loss.
Node types refer to different service types performed by service activities, such as in the insurance application service, the node types can be divided into: pricing, creation of insurance policy, underwriting, payment, and ordering.
The snapshot refers to service data generated during service execution.
Snapshot type: indicating the kind of service data. The types of snapshots generated by the insurance application process are classified as: policy information, product details, policy information, payment information, billing information.
Rules: business resource discovery rules.
The rule expression: code statements that are executed by the engine, such as QLExpress statements, SQL;
rule factor: dynamic data that requires values from a particular business snapshot in a regular expression is typically represented by a placeholder.
In fig. 2, the method for storing the service node snapshot includes:
receiving service node snapshot template information, and receiving a service node snapshot template information request;
writing in service nodes and service node snapshots, and writing in service nodes and service node snapshots;
inquiring the service node snapshot list, and inquiring the service node snapshot list for the written service node snapshot;
judging the synchronization state of the service node snapshots, judging the synchronization state of the service node snapshots for the queried service node snapshot list, and when all the node snapshots are in the synchronization state, adding a timing checking task and triggering; otherwise, checking the snapshot timeout time of the service node;
checking the service node snapshot timeout time, judging timeout for unsynchronized service node snapshots, outputting a warning when the service node snapshots timeout, otherwise, judging checking tasks; checking task judgment, and when the service node snapshot is not overtime and all nodes are synchronized, adding a checking task and triggering;
newly adding and triggering a checking timing task, and pulling a snapshot list and executing a checking rule after the checking timing task is triggered; after the checking rule is executed, if judging whether the business resource loss exists, sending out a warning and manually processing if the business resource loss exists; otherwise, checking the timing task to end.
In fig. 3, the triggering of the real-time collation service includes:
acquiring a service node snapshot list, checking a service in real time and transmitting the service into a node type, thereby acquiring the service node snapshot list;
judging a service node snapshot list, determining whether service snapshots are collected according to the obtained service node snapshot list, and obtaining service snapshot template information when the service snapshots are collected; otherwise, giving out a warning;
acquiring service snapshot template information, wherein the service snapshot template information comprises service snapshot rules, service snapshot rule expression templates and service snapshot rule factors;
assembling the service snapshot template information, and assembling the acquired service snapshot template information;
executing the business snapshot rule, and executing the rule on the assembled business snapshot template information;
and judging the resource loss, judging the resource loss according to a service snapshot rule, triggering service blocking or sending alarm information when the resource loss exists, and otherwise, checking that the triggering of the service is completed in real time.
The service node snapshot is acquired through an SDK or API mode.
The storage of the service node snapshots is stored in the form of a service node data structure.
The comparison method of the service node snapshot adopts dynamic scripts.
Example 2
Based on embodiment 1, this embodiment further includes blocking the execution of the service, and when the comparison result is found to have a resource loss, blocking the execution of the service in an automated manner.
Example 3
On the basis of the above embodiment, the present embodiment is a system for checking business resources in real time, which includes a system for implementing a method for checking business resources in real time; the method comprises the steps that a service node snapshot obtaining unit obtains service node snapshots generated by a current service node at key nodes of each service flow;
the storage unit of the service node snapshot stores the acquired service node snapshot into a storage medium;
the triggering unit of the real-time checking service triggers the real-time checking service by loading data checking rules of different service nodes and service node snapshots;
the comparison unit of the service node snapshot is used for obtaining a comparison result of the service node snapshot through the execution of the check engine; synchronizing the comparison result to business resource loss processing when the comparison result has resource loss; otherwise, the business real-time check is finished;
and the service loss processing unit is used for processing the service loss through the alarm notification when checking and finding that the service loss processing is received.
Example 4
On the basis of the above embodiment, the present embodiment is a service flow for application, and in fig. 4, the application service flow includes five nodes of user application, pricing, underwriting, payment and policy issuing; before paying after the check and protection process, the check and protection node sends out a snapshot message, and after receiving the snapshot message, the designed check system stores the snapshot in a storage medium, and for paying, a premium check task needs to be generated and a second-level task is triggered, so that whether snapshot data are complete or not, namely whether pricing, policy and payment snapshot exist or not is judged; when the snapshot data are complete, namely pricing, policy and payment snapshot exist, snapshot data are acquired; otherwise, checking data is incomplete.
The obtained snapshot data comprises pricing data snapshot acquisition, payment data acquisition and policy data acquisition; for pricing data snapshot collection, firstly collecting pricing record snapshots, and then storing the collected top-level record snapshots; for payment data acquisition, firstly acquiring payment snapshot data, and then storing the payment data; and for acquiring the policy data, acquiring the policy snapshot data and storing the acquired policy snapshot data.
Executing the premium checking rule after the snapshot data is acquired, then judging the pricing, the premium pricing and the payment amount, and whether the policy premium is consistent with the pricing or not, and finishing the service checking when the premium pricing and the payment amount are consistent and the policy premium is consistent with the pricing, and ending the issuing of the policy; when the premium pricing is inconsistent with the payment amount or the policy premium is inconsistent with the pricing, sending alarm information through nailing, short message or telephone; fusing the business flow, so that the user cannot continue to execute the third-step payment operation, and the problem of resource loss of the system is prevented; and the alarm information is received and then is manually processed by a technician. The check task scans the snapshot message, and the check engine finds out the data abnormality of the check node.
If the insurance amount of the product is 100 yuan during the insurance check, and the payment amount of the insurance policy is 50 yuan, the data are not matched, at the moment, the checking system can send an alarm to a nail, a flyer, a WeChat and a short message notification channel, and fuse the business flow, so that a user cannot continue to execute the third-step payment operation, and the problem of resource loss of the system is prevented.
Claims (8)
1. A method of real-time reconciling business costs, the method comprising:
acquiring service node snapshots, namely acquiring service node snapshots generated by a current service node at key nodes of each service flow;
storing the service node snapshot, and storing the acquired service node snapshot into a storage medium;
triggering the real-time checking service by loading data checking rules of different service nodes and service node snapshots;
comparing the service node snapshots, and executing a comparison result of acquiring the service node snapshots through a check engine; synchronizing the comparison result to business resource loss processing when the comparison result has resource loss; otherwise, the business real-time check is finished;
and (5) service loss processing, namely checking and finding that the service loss processing is received, and processing the service loss through alarm notification.
2. The method for real-time check of service loss according to claim 1, further comprising blocking of service execution, and automatically blocking the execution of service when the loss of service is found in the comparison result.
3. The method for real-time reconciling of service impairment according to claim 1, wherein the storing of the service node snapshots comprises:
receiving service node snapshot template information, and receiving a service node snapshot template information request;
writing in service nodes and service node snapshots, and writing in service nodes and service node snapshots;
inquiring the service node snapshot list, and inquiring the service node snapshot list for the written service node snapshot;
judging the synchronization state of the service node snapshots, judging the synchronization state of the service node snapshots for the queried service node snapshot list, and when all the node snapshots are in the synchronization state, adding a timing checking task and triggering; otherwise, checking the snapshot timeout time of the service node;
checking the service node snapshot timeout time, judging timeout for unsynchronized service node snapshots, outputting a warning when the service node snapshots timeout, otherwise, judging checking tasks; checking task judgment, and when the service node snapshot is not overtime and all nodes are synchronized, adding a checking task and triggering;
newly adding and triggering a checking timing task, and pulling a snapshot list and executing a checking rule after the checking timing task is triggered; after the checking rule is executed, if judging whether the business resource loss exists, sending out a warning and manually processing if the business resource loss exists; otherwise, checking the timing task to end.
4. The method for real-time reconciliation of service loss as defined in claim 1 wherein the triggering of the real-time reconciliation service comprises:
acquiring a service node snapshot list, checking a service in real time and transmitting the service into a node type, thereby acquiring the service node snapshot list;
judging a service node snapshot list, determining whether service snapshots are collected according to the obtained service node snapshot list, and obtaining service snapshot template information when the service snapshots are collected; otherwise, giving out a warning;
acquiring service snapshot template information, and acquiring the service snapshot template information for the collected service snapshots; the service snapshot template information comprises a service snapshot rule, a service snapshot rule expression template and a service snapshot rule factor;
assembling the service snapshot template information, and assembling the acquired service snapshot template information;
executing the business snapshot rule, and executing the rule on the assembled business snapshot template information;
and judging the resource loss, judging the resource loss according to a service snapshot rule, triggering service blocking or sending alarm information when the resource loss exists, and otherwise, checking that the triggering of the service is completed in real time.
5. The method for checking service loss in real time according to claim 1, wherein the snapshot of the service node is obtained by SDK or API.
6. A method of checking traffic loss in real time according to claim 1, in which the storage of the traffic node snapshot is stored in the form of a traffic node data structure.
7. A method for checking traffic loss in real time according to claim 1, wherein the comparison of the traffic node snapshots is performed by using dynamic scenarios.
8. A system for real-time reconciling of service impairment, comprising a system for implementing a method for real-time reconciling of service impairment as defined in any one of claims 1-7;
the service node snapshot acquiring unit acquires service node snapshots generated by the current service node at key nodes of each service flow;
the storage unit of the service node snapshot stores the acquired service node snapshot into a storage medium;
the triggering unit of the real-time checking service triggers the real-time checking service by loading data checking rules of different service nodes and service node snapshots;
the comparison unit of the service node snapshot is used for obtaining a comparison result of the service node snapshot through the execution of the check engine; synchronizing the comparison result to business resource loss processing when the comparison result has resource loss; otherwise, the business real-time check is finished;
and the service loss processing unit is used for processing the service loss through the alarm notification when checking and finding that the service loss processing is received.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311011335.9A CN116719751B (en) | 2023-08-11 | 2023-08-11 | Method and system for checking service loss in real time |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311011335.9A CN116719751B (en) | 2023-08-11 | 2023-08-11 | Method and system for checking service loss in real time |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116719751A true CN116719751A (en) | 2023-09-08 |
| CN116719751B CN116719751B (en) | 2023-11-03 |
Family
ID=87873875
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311011335.9A Active CN116719751B (en) | 2023-08-11 | 2023-08-11 | Method and system for checking service loss in real time |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116719751B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002230308A (en) * | 2001-02-05 | 2002-08-16 | Hamagin System Service Kk | Device and method for fund management, and program |
| US20050209876A1 (en) * | 2004-03-19 | 2005-09-22 | Oversight Technologies, Inc. | Methods and systems for transaction compliance monitoring |
| CN110018957A (en) * | 2019-02-14 | 2019-07-16 | 阿里巴巴集团控股有限公司 | A kind of money damage verification script detection method and device |
| CN110175916A (en) * | 2019-04-26 | 2019-08-27 | 阿里巴巴集团控股有限公司 | Cash flow checking method and device |
| CN110197430A (en) * | 2019-06-06 | 2019-09-03 | 深圳萨摩耶互联网金融服务有限公司 | A kind of fund business monitoring method and system based on fund operation system |
| WO2021129104A1 (en) * | 2019-12-25 | 2021-07-01 | 支付宝(杭州)信息技术有限公司 | Business information processing method and apparatus, and electronic device |
| CN113721950A (en) * | 2021-07-28 | 2021-11-30 | 北京阳光消费金融股份有限公司 | Resource loss prevention and control processing method and device |
| CN115456786A (en) * | 2022-09-21 | 2022-12-09 | 江苏苏宁银行股份有限公司 | Transaction link resource loss detection system, method and device based on big data |
| CN116245623A (en) * | 2023-02-20 | 2023-06-09 | 江苏苏宁银行股份有限公司 | Banking industry resource loss prevention and control method and device |
-
2023
- 2023-08-11 CN CN202311011335.9A patent/CN116719751B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002230308A (en) * | 2001-02-05 | 2002-08-16 | Hamagin System Service Kk | Device and method for fund management, and program |
| US20050209876A1 (en) * | 2004-03-19 | 2005-09-22 | Oversight Technologies, Inc. | Methods and systems for transaction compliance monitoring |
| CN110018957A (en) * | 2019-02-14 | 2019-07-16 | 阿里巴巴集团控股有限公司 | A kind of money damage verification script detection method and device |
| CN110175916A (en) * | 2019-04-26 | 2019-08-27 | 阿里巴巴集团控股有限公司 | Cash flow checking method and device |
| CN110197430A (en) * | 2019-06-06 | 2019-09-03 | 深圳萨摩耶互联网金融服务有限公司 | A kind of fund business monitoring method and system based on fund operation system |
| WO2021129104A1 (en) * | 2019-12-25 | 2021-07-01 | 支付宝(杭州)信息技术有限公司 | Business information processing method and apparatus, and electronic device |
| CN113721950A (en) * | 2021-07-28 | 2021-11-30 | 北京阳光消费金融股份有限公司 | Resource loss prevention and control processing method and device |
| CN115456786A (en) * | 2022-09-21 | 2022-12-09 | 江苏苏宁银行股份有限公司 | Transaction link resource loss detection system, method and device based on big data |
| CN116245623A (en) * | 2023-02-20 | 2023-06-09 | 江苏苏宁银行股份有限公司 | Banking industry resource loss prevention and control method and device |
Non-Patent Citations (1)
| Title |
|---|
| 韩晶;赵锡成;黄文良;: "运营商电商业务安全防护体系研究", 邮电设计技术, no. 04 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116719751B (en) | 2023-11-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110827032B (en) | Intelligent wind control decision method and system and service processing method and system | |
| CN108520464B (en) | Real-time automatic supervision reporting system based on traditional block chain | |
| US20220321440A1 (en) | Interface Service Function Monitoring Method and System Based on Data Acquisition | |
| CN110088744B (en) | Database maintenance method and system | |
| WO2020088098A1 (en) | Block chain-based quality data processing method and apparatus | |
| CN110969417A (en) | Government affair item synchronization method, device, system, computer equipment and storage medium | |
| CN110674145B (en) | Data consistency detection method, device, computer equipment and storage medium | |
| CN103440460A (en) | Application system change validation method and system | |
| CN112199277A (en) | Browser-based defect reproduction method, device, equipment and storage medium | |
| CN110020550B (en) | Assessment method, device and equipment for verification platform | |
| CN113177845A (en) | Business abnormity monitoring method based on supply chain finance | |
| CN116719751B (en) | Method and system for checking service loss in real time | |
| CN107835174B (en) | Account book anti-fraud system and method based on Internet of things | |
| KR102304237B1 (en) | compliance management system through automatic diagnosis of infrastructure asset threat and method therefor | |
| CN114327981A (en) | Safety verification system, method and device of function safety mechanism | |
| JP2022104888A (en) | Test information provision method, virtual cooperation device, and system | |
| CN114997987A (en) | Business information processing method, device, equipment and medium based on block chain system | |
| CN113282506A (en) | Test data acquisition method, device, equipment and computer readable storage medium | |
| CN111176975B (en) | Test method, device, equipment and computer readable storage medium | |
| Seehusen | A technique for risk-based test procedure identification, prioritization and selection | |
| CN116260640B (en) | Information interception control method and system for big data analysis based on artificial intelligence | |
| CN117272392B (en) | Data security protection and backup control method and system for terminal | |
| CN110347741B (en) | System for effectively improving output result data quality in big data processing process and control method thereof | |
| WO2023093573A1 (en) | Charging message processing method and apparatus, system, electronic device, and storage medium | |
| KR101883407B1 (en) | detecting methods and systems of prevention check for information system using agentless |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |