CN106875156B - A generalized intelligent audit platform and audit method thereof - Google Patents
A generalized intelligent audit platform and audit method thereof Download PDFInfo
- Publication number
- CN106875156B CN106875156B CN201710078245.XA CN201710078245A CN106875156B CN 106875156 B CN106875156 B CN 106875156B CN 201710078245 A CN201710078245 A CN 201710078245A CN 106875156 B CN106875156 B CN 106875156B
- Authority
- CN
- China
- Prior art keywords
- audit
- data
- auditing
- task
- business
- 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 OR CALCULATING; 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/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- General Business, Economics & Management (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Computing Systems (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Debugging And Monitoring (AREA)
Abstract
本发明公开了一种通用化智能审核平台及其审核方法,审核平台包括项目构建模块和智能审核模块;所述的项目构建模块用于管理项目库;所述的项目库中包括至少一个实例化项目;所述的项目构建模块包括业务数据单元、业务数据库单元、业务JavaBean单元和业务规则单元。本发明在审核平台开发和部署时将业务数据和业务审核逻辑进行无关化处理,提高系统的可用性和稳定性,降低审核平台的开发、运营和维护成本;并且进一步的,本发明支持不同的审核应用场景,本审核平台支持事中审核和事后审核两种审核方式,业务审核方式根据实时性、响应速度和数据量的不同审核要求,相应处理方式也不同。
The invention discloses a generalized intelligent auditing platform and an auditing method thereof. The auditing platform includes a project building module and an intelligent auditing module; the project building module is used to manage a project library; the project library includes at least one instance of Project; the project building module includes a business data unit, a business database unit, a business JavaBean unit and a business rule unit. The present invention conducts irrelevant processing of business data and business audit logic during the development and deployment of the audit platform, improves the usability and stability of the system, and reduces the development, operation and maintenance costs of the audit platform; and further, the present invention supports different audits. In the application scenario, this audit platform supports two audit methods: in-process audit and post-event audit. The business audit methods are processed differently according to the different audit requirements of real-time, response speed and data volume.
Description
技术领域technical field
本发明涉及业务数据智能审核技术领域,还涉及面向医疗保险报销审核、企业报销审核以及行政审批等数据审核领域,尤其涉及一种通用化智能审核平台及其审核方法。The invention relates to the technical field of intelligent auditing of business data, and also relates to the fields of data auditing for medical insurance reimbursement auditing, enterprise reimbursement auditing, administrative approval and the like, in particular to a generalized intelligent auditing platform and an auditing method thereof.
背景技术Background technique
国家经济下行压力不断加大,市场竞争越发激烈,企业运营风险不断增加的环境下,企业和机构为了提高自身市场竞争力,在优胜劣汰的市场竞争中优胜,普遍做法是开源节流,减少不必要的日常运营开销,提高资源管理水平,提高投入资源产出率。在市场需求推动下,业务数据审核进入了快速增长期。但是现有业务数据审核模式存在以下问题:In an environment where the downward pressure on the national economy is increasing, market competition is becoming more intense, and enterprise operational risks are constantly increasing, in order to improve their market competitiveness, enterprises and institutions will win the market competition of the survival of the fittest. Operational expenses, improve resource management level, and increase the output rate of input resources. Driven by market demand, business data auditing has entered a period of rapid growth. However, the existing business data audit mode has the following problems:
面对大量业务数据审核任务,传统人工审核模式,不仅审核时间长、审核效率低,异常数据甄别能力低,同时造成审核人员工作负担过大,影响身心健康。随着数据时代到来,业务数据审核需求越来越大,审核要求越来越高,传统人工审核模式的问题将异常突出。Faced with a large number of business data review tasks, the traditional manual review mode not only takes a long time to review, but also has low review efficiency and low ability to identify abnormal data. With the advent of the data age, business data auditing requirements are increasing, and auditing requirements are getting higher and higher, and the problems of the traditional manual auditing mode will be extremely prominent.
目前,市场上存在一些业务数据审核平台,比如申请号为CN201510464287.8、名称为“一种大病医保智能化审核系统及审核算法” 的发明专利,该发明提供一种大病医保智能化审核系统,包括数据库模块、智能审核引擎以及基础信息库管理模块,所述数据库模块,用于获取大病医保数据;所述智能审核引擎,其用于对所述大病医保数据的各属性项的关联匹配度进行审核处理;所述基础信息库管理模块,其存储基础数据的各项属性信息,其中,所述智能审核引擎分别与所述数据库模块、所述基础信息库管理模块连接,并给予所述数据库模块、所述基础信息库管理模块的数据完成所述审核处理。但这审核平台业务审核范围单一,审核领域局限,只能处理特定审核领域,无法扩展审核范围和审核领域。虽然可以满足当前业务数据审核需求,但是市场是动态不断变化的,实际业务需求也随之不断变化,这些审核范围单一、审核领域局限的数据审核平台,终将在残酷的市场竞争中淘汰。At present, there are some business data auditing platforms on the market, such as the invention patent with the application number CN201510464287.8 and the title of "An Intelligent Auditing System and Auditing Algorithm for Critical Illness Medical Insurance", which provides an intelligent auditing system for critical illness medical insurance. Including a database module, an intelligent auditing engine and a basic information base management module, the database module is used to obtain critical illness medical insurance data; the intelligent auditing engine is used to perform the correlation matching degree of each attribute item of the critical illness medical insurance data. Audit processing; the basic information base management module stores various attribute information of basic data, wherein the intelligent audit engine is respectively connected with the database module and the basic information base management module, and gives the database module . The data of the basic information base management module completes the auditing process. However, this audit platform has a single business audit scope and limited audit areas. It can only handle specific audit areas, and cannot expand the audit scope and audit areas. Although it can meet the current business data audit needs, the market is constantly changing, and the actual business needs are constantly changing. These data audit platforms with a single audit scope and limited audit areas will eventually be eliminated in the brutal market competition.
同时,现有技术在审核平台开发时关心实际处理的业务数据,具体地:现在大多数审核平台,在开发时已经默认设置需要处理的业务数据结构,部署后只能解析与默认设置的业务数据结构相对应的业务数据,突出审核平台处理业务数据范围的局限性,导致这种审核平台存在缺陷。因为实际的业务数据结构总是随着市场的不断变化而动态变化,所以审核平台的业务数据结构也需要随之改变,但是这种审核平台已经在开发时将需求方提供的业务数据结构固化在代码。平台部署后想要修改业务数据结构,则需要修改审核平台源代码,加大了审核平台的维护成本和风险。当审核平台部署发布后,修改源代码风险极高,极有可能在修改代码过程中影响其他部分功能模块,从而留下隐蔽Bug。为了规避这些风险,需要测试人员投入大量精力对审核平台稳定性进行测试,这无疑加大审核平台的开发、运营和维护成本。At the same time, the existing technology cares about the actual business data processed during the development of the audit platform. Specifically, most audit platforms have already set the business data structure to be processed by default during development, and can only parse the business data with the default settings after deployment. The business data corresponding to the structure highlights the limitations of the scope of business data processed by the audit platform, resulting in defects in this audit platform. Because the actual business data structure always changes dynamically with the continuous change of the market, the business data structure of the audit platform also needs to be changed accordingly, but this audit platform has solidified the business data structure provided by the demander during development. code. If you want to modify the business data structure after the platform is deployed, you need to modify the source code of the audit platform, which increases the maintenance cost and risk of the audit platform. When the audit platform is deployed and released, the risk of modifying the source code is extremely high, and it is very likely that other functional modules will be affected in the process of modifying the code, thus leaving hidden bugs. In order to avoid these risks, testers need to invest a lot of energy to test the stability of the audit platform, which undoubtedly increases the development, operation and maintenance costs of the audit platform.
另外,市面上大多数审核平台,需要在开发时确定具体的业务审核逻辑,并在开发过程中固化在代码里。这样大大降低了系统的扩展性和灵活性,实际业务审核逻辑并不是一成不变的,而是随着市场需求的变化而变化。这种预先把业务审核逻辑的固化到系统里的设计模式终将在优胜劣汰的市场中,暴露出巨大的缺陷,从而慢慢被残酷的市场所淘汰。如果为了弥补这一缺陷去修改源代码,不仅加大了开发、测试和维护成本,而且降低了系统的可用性和稳定性。In addition, most audit platforms on the market need to determine the specific business audit logic during development and solidify it in the code during the development process. This greatly reduces the scalability and flexibility of the system, and the actual business audit logic is not static, but changes with changes in market demand. This design pattern that solidifies the business audit logic into the system in advance will eventually expose huge defects in the market of survival of the fittest, and thus will be gradually eliminated by the cruel market. If the source code is modified in order to make up for this defect, it will not only increase the development, testing and maintenance costs, but also reduce the availability and stability of the system.
最后,现在市面上大多数审核平台,只支持单一的审核方式,本应有所区分的审核应用场景,由于设计开发时没有考虑有选择的审核方式,导致对于所有的审核请求,都采取单一审核方式,显然这样是不合理的。Finally, most auditing platforms on the market now only support a single auditing method. There should be different auditing application scenarios. Because the selective auditing method is not considered in the design and development, a single auditing method is adopted for all auditing requests. way, obviously this is unreasonable.
发明内容SUMMARY OF THE INVENTION
本发明的目的在于克服现有技术的不足,提供一种通用化智能审核平台及其审核方法,在审核平台开发和部署时将业务数据和业务审核逻辑进行无关化处理,提高系统的可用性和稳定性,降低审核平台的开发、运营和维护成本。The purpose of the present invention is to overcome the deficiencies of the prior art, to provide a generalized intelligent audit platform and an audit method thereof, and to conduct irrelevant processing of business data and business audit logic during the development and deployment of the audit platform, so as to improve the usability and stability of the system It can reduce the development, operation and maintenance costs of the audit platform.
本发明的目的是通过以下技术方案来实现的:一种通用化智能审核平台,包括项目构建模块和智能审核模块;The purpose of the present invention is to achieve through the following technical solutions: a generalized intelligent auditing platform, comprising a project building module and an intelligent auditing module;
所述的项目构建模块用于管理项目库;所述的项目库中包括至少一个实例化项目;所述的项目构建模块包括业务数据单元、业务数据库单元、业务JavaBean单元和业务规则单元;所述的业务数据单元用于构建实例化项目的业务数据结构,所述的业务数据结构由数据表信息和字段信息组成,为解析审核请求方上传JSON数据包提供支持,同时为业务数据库单元、业务JavaBean单元和业务规则单元提供支持;所述的业务数据库单元用于构建基于所述实例化项目的业务数据结构的业务数据库,为持久化审核数据提供物理存储支持;所述的业务JavaBean单元用于构建基于所述实例化项目的业务数据结构的业务JavaBean集,当智能审核模块的审核请求到达时,将审核数据转换为实例化业务JavaBean对象;所述的业务规则单元用于构建基于所述实例化项目的业务数据结构的业务规则库,包括将实例化项目的业务审核逻辑转换为Drools规则引擎支持的规则和规则流;The project building module is used to manage a project library; the project library includes at least one instantiated project; the project building module includes a business data unit, a business database unit, a business JavaBean unit and a business rule unit; the The business data unit is used to construct the business data structure of the instantiated project. The business data structure is composed of data table information and field information, which provides support for parsing and reviewing the requester to upload JSON data packets, and provides support for the business database unit, business JavaBean The unit and the business rule unit provide support; the business database unit is used to construct a business database based on the business data structure of the instantiated project, and provides physical storage support for persistent audit data; the business JavaBean unit is used to construct Based on the business JavaBean set of the business data structure of the instantiated project, when the audit request of the intelligent audit module arrives, the audit data is converted into the instantiated business JavaBean object; the business rule unit is used to construct the instantiation based on the instantiation. The business rule library of the project's business data structure, including converting the business audit logic of the instantiated project into the rules and rule flows supported by the Drools rule engine;
所述的智能审核模块用于实现审核平台的业务数据审核。The intelligent auditing module is used to implement business data auditing of the auditing platform.
所述的智能审核模块包括事中审核单元和事后审核单元;所述的事中审核单元用于实时性高、响应速度快、数据量小的业务审核应用场景,所述的事后审核单元用于实时性低、响应速度较快、数据量大的业务审核应用场景;The intelligent audit module includes an in-event audit unit and a post-event audit unit; the in-event audit unit is used for business audit application scenarios with high real-time performance, fast response speed and small data volume, and the post-event audit unit is used for Business audit application scenarios with low real-time performance, fast response speed and large amount of data;
所述的事中审核单元包括第一审核数据接口子单元、第一任务管理子单元和事中审核引擎,所述的第一审核数据接口子单元负责管理审核平台和审核请求方之间的数据通信,包括监听审核请求、解析审核请求和审核结果传回;所述的第一任务管理子单元负责管理审核任务,包括维护任务表、创建审核任务、更改任务状态和结束审核任务,所有审核任务信息记录在任务表中;所述的事中审核引擎负责处理事中审核的业务数据审核;The in-event audit unit includes a first audit data interface sub-unit, a first task management sub-unit and an in-event audit engine, and the first audit data interface sub-unit is responsible for managing the data between the audit platform and the audit requester. Communication, including monitoring audit requests, parsing audit requests, and returning audit results; the first task management subunit is responsible for managing audit tasks, including maintaining task tables, creating audit tasks, changing task status, and ending audit tasks, and all audit tasks. The information is recorded in the task table; the in-event audit engine is responsible for processing the business data audit of in-event audit;
所述的事后审核单元包括第二审核数据接口子单元、第二任务管理子单元和事后审核引擎,所述的第二审核数据接口子单元负责管理审核平台和审核请求方之间的数据通信,包括监听审核请求、解析审核请求和审核结果传回;所述的第二任务管理子单元负责管理审核任务,包括维护任务表、创建审核任务、更改任务状态和结束审核任务,所有审核任务信息记录在任务表中;所述的事后审核引擎负责处理事后审核的业务数据审核。The post-audit audit unit includes a second audit data interface sub-unit, a second task management sub-unit and a post-event audit engine, and the second audit data interface sub-unit is responsible for managing the data communication between the audit platform and the audit requester, Including monitoring audit requests, parsing audit requests and returning audit results; the second task management subunit is responsible for managing audit tasks, including maintaining task tables, creating audit tasks, changing task status, and ending audit tasks, and all audit task information records In the task table; the post-event review engine is responsible for processing post-event review business data review.
所述的事中审核引擎为线性执行的非流水线方式的审核引擎;所述的事中审核引擎包括业务数据审核组件、审核结果组装组件和审核任务持久化组件,所述的业务数据审核组件用于审核业务数据,所述的审核结果组装组件用于按返回结果标准格式组装审核结果,所述的审核任务持久化组件用于将审核任务信息、业务数据和审核结果持久化到物理数据库。The in-event audit engine is a linearly executed non-pipeline mode audit engine; the in-event audit engine includes a business data audit component, an audit result assembly component and an audit task persistence component, and the business data audit component uses For auditing business data, the audit result assembly component is used for assembling audit results in a standard format of returned results, and the audit task persistence component is used for persisting audit task information, business data and audit results to a physical database.
所述的事后审核引擎为并行执行的流水线方式的审核引擎;所述的事中审核引擎包括业务数据审核组件、审核结果组装组件、结果传回组件和审核任务持久化组件,所述的业务数据审核组件用于审核业务数据,所述的审核结果组装组件用于按返回结果标准格式组装审核结果,所述的结果传回组件基于第二审核数据接口子单元将组装的审核结果传回审核请求方,所述的审核任务持久化组件用于将审核任务信息、业务数据和审核结果持久化到物理数据库。The described post-event auditing engine is a parallel execution pipeline mode auditing engine; the described in-event auditing engine includes a business data auditing component, an auditing result assembling component, a result returning component and an auditing task persistence component, and the business data The auditing component is used for auditing business data, the auditing result assembling component is used for assembling auditing results in a standard format of returned results, and the result returning component transmits the assembled auditing result back to the auditing request based on the second auditing data interface subunit The audit task persistence component is used to persist audit task information, business data and audit results to a physical database.
一种通用化智能审核方法,包括项目构建步骤和智能审核步骤;所述的项目构建步骤包括对实例化项目的添加,所述的对实例化项目的添加包括以下子步骤:A generalized intelligent auditing method includes a project building step and an intelligent auditing step; the project building step includes adding an instantiated project, and the adding of the instantiated project includes the following sub-steps:
S11:添加实例化项目,对实例化项目的基本信息进行添加;S11: Add an instantiated project, and add the basic information of the instantiated project;
S12:添加至少一个业务数据结构,包括对数据表信息和字段信息的添加;同时在添加完成后,系统为所述业务数据结构添加任务编号字段和任务数据索引字段;S12: adding at least one business data structure, including adding data table information and field information; at the same time, after the addition is completed, the system adds a task number field and a task data index field to the business data structure;
S13:在步骤S12完成后,分别构建业务数据库、业务JavaBean集和业务规则库;其中,对于业务数据库的构建包括以下子步骤:S13: After the completion of step S12, build the business database, business JavaBean set and business rule library respectively; wherein, the construction of the business database includes the following sub-steps:
S1311:根据业务数据结构的数据表编号和与该数据表编号绑定的字段信息,构造数据表SQL语句;S1311: Construct a data table SQL statement according to the data table number of the business data structure and the field information bound to the data table number;
S1312:在实例化项目业务数据库中执行构造的SQL语句,完成业务数据表创建,更新该业务数据结构数据表信息的生成标志,表明业务数据表已生成;S1312: Execute the constructed SQL statement in the instantiated project business database, complete the creation of the business data table, and update the generation flag of the data table information of the business data structure, indicating that the business data table has been generated;
S1313:将实例化项目的所有业务数据结构一一生成对应的业务数据表;S1313: Generate corresponding business data tables one by one for all business data structures of the instantiated project;
对于业务JavaBean集的构建,包括以下子步骤:For the construction of the business JavaBean set, the following sub-steps are included:
S1321:根据该业务数据结构的数据表编号和与该数据表编号绑定的字段信息,构造对应业务JavaBean的java文件;S1321: According to the data table number of the business data structure and the field information bound to the data table number, construct a java file corresponding to the business JavaBean;
S1322:使用java语言编程编译器javac将java文件编译生成class文件,更新该业务数据结构数据表信息的生成标志,表明业务JavaBean已生成;S1322: Use the java language programming compiler javac to compile the java file to generate a class file, and update the generation flag of the data table information of the business data structure, indicating that the business JavaBean has been generated;
S1323:将实例化项目的所有业务数据结构一一生成对应的业务JavaBean,构建业务JavaBean集;S1323: Generate corresponding business JavaBeans one by one for all business data structures of the instantiated project, and construct a business JavaBean set;
对于业务规则库的构建,包括以下子步骤:For the construction of the business rule base, the following sub-steps are included:
S1331:构建规则部分,所述的规则部分包括属性部分、条件部分和结构部分;所述的属性部分用于定义当前规则执行的一些属性,包括是否可被重复执行、过期时间、生效时间;所述的条件部分用于定义当前规则的单个/多个条件;所述的结构部分用于定义满足当前条件部分后执行的操作;S1331: Build a rule part, the rule part includes an attribute part, a condition part and a structure part; the attribute part is used to define some attributes of the current rule execution, including whether it can be repeatedly executed, expiration time, and effective time; The condition part described is used to define the single/multiple conditions of the current rule; the structural part is used to define the operation performed after the current condition part is satisfied;
S1332:构建规则流,所述的规则流基于业务流程图实现,所述的业务流程图描述了一系列需要执行的审核业务的顺序,包括规则部分、条件分支和分支聚合三部分;S1332: Build a rule flow, where the rule flow is implemented based on a business flow chart, and the business flow chart describes a sequence of a series of audit services that need to be executed, including three parts: a rule part, a conditional branch, and a branch aggregation;
所述的智能审核步骤用于实现审核平台的业务数据审核。The intelligent auditing steps are used to implement business data auditing of the auditing platform.
所述的实例化项目的基本信息包括项目名、项目编号、项目介绍、业务数据库账号和密码;在提交添加申请后,在数据库创建对应的数据库账号,创建的数据库账号作为实例化项目的业务数据库,存储实例化项目的业务数据;The basic information of the instantiated project includes project name, project number, project introduction, business database account number and password; after submitting an application for addition, a corresponding database account is created in the database, and the created database account is used as the business database of the instantiated project. , which stores the business data of the instantiated project;
所述的数据表信息包括数据表编号和生成标志;所述的生成标志表示该数据表信息是否生成对应业务JavaBean,以及是否在数据库中生成对应业务数据表;所述的数据表编号作为业务数据表的表名和业务JavaBean的类名;Described data table information includes data table number and generation mark; Described generation mark indicates whether this data table information generates corresponding business JavaBean, and whether to generate corresponding business data table in database; Described data table number is used as business data The table name of the table and the class name of the business JavaBean;
所述的字段信息包括字段编号和关心标识,所述的字段编号作为业务数据表的字段名和业务JavaBean的类成员变量名,所述的关心标识表示该字段是否为关心数据,在业务审核时,当该数据表数据触发了业务规则,需要将关心标识的字段数据拼接在审核结果,返回给审核请求方。Described field information includes field number and care mark, described field number is used as the field name of business data table and the class member variable name of business JavaBean, described care mark indicates whether this field is care data, during business audit, When the data in the data table triggers the business rule, the field data of the concerned identifier needs to be spliced into the audit result and returned to the audit requester.
所述的项目构建步骤还包括对实例化项目的修改、查看与删除。The project building step also includes modifying, viewing and deleting the instantiated project.
所述的智能审核步骤包括事中审核子步骤和事后审核子步骤;所述的事中审核子步骤为线性执行的非流水线方式,所述的事后审核子步骤为并行执行的流水线方式。The intelligent auditing step includes an in-event auditing sub-step and a post-event auditing sub-step; the in-event auditing sub-step is a non-pipeline mode of linear execution, and the post-event audit sub-step is a pipeline mode that is executed in parallel.
所述的事中审核子步骤,包括以下子步骤:The in-process audit sub-steps described include the following sub-steps:
S211:事中审核数据接口捕获审核请求;其中所述的审核请求为审核请求方将验证信息、审核要求和业务数据封装成JSON数据包,然后加密压缩并设置为接口输入数据,传输到审核平台的事中审核数据接口的审核请求;S211: The in-process audit data interface captures the audit request; the audit request is that the audit requester encapsulates the verification information, audit requirements and business data into JSON data packets, then encrypts and compresses and sets them as interface input data, and transmits them to the audit platform The audit request of the audit data interface in the event;
S212:事中审核数据接口将上传数据解压解密,解析出验证信息,将验证信息与审核服务注册信息进行对比验证,如果验证通过,则进入步骤S213;否则,事中审核数据接口将审核服务受限提示信息返回审核请求方;S212: The in-event audit data interface decompresses and decrypts the uploaded data, parses out the verification information, and compares the verification information with the audit service registration information for verification. If the verification is passed, proceed to step S213; Restrict prompt information to be returned to the audit requester;
S213:事中审核数据接口解析审核要求,如果审核要求解析成功,则通过任务管理子单元创建审核任务、初始化审核任务、绑定请求方信息、设置审核要求,并进入步骤S214;否则,事中审核数据接口将错误信息返回审核请求方;S213: Analyze the audit request through the in-process audit data interface, and if the audit request is successfully resolved, create an audit task, initialize the audit task, bind the requester information, set the audit request through the task management subunit, and enter step S214; otherwise, in-process The audit data interface returns error information to the audit requester;
S214:事中审核数据接口基于业务数据结构解析业务数据,如果业务数据解析成功,事中审核数据接口将业务数据转换为实例化业务JavaBean对象,转入事中审核引擎进行业务审核;否则,任务管理子单元注销审核任务,事中审核数据接口将错误信息返回审核请求方;S214: The in-event audit data interface parses the business data based on the business data structure. If the business data is successfully parsed, the in-event audit data interface converts the business data into an instantiated business JavaBean object, and transfers it to the in-event audit engine for business audit; otherwise, the task The management subunit cancels the audit task, and the in-process audit data interface returns the error information to the audit requester;
S215:事中审核引擎根据审核任务的审核要求,从编译后的业务规则库提取本次审核涉及的业务规则包,并基于提取的业务规则包,创建审核会话,将业务数据JavaBean对象加载到审核会话中,执行审核会话;S215: The in-event audit engine extracts the business rule package involved in this audit from the compiled business rule library according to the audit requirements of the audit task, creates an audit session based on the extracted business rule package, and loads the business data JavaBean object into the audit session, perform an audit session;
S216:审核会话结束后,按返回结果标准格式组装审核结果;S216: After the audit session ends, assemble the audit results according to the standard format of returned results;
S217:组装完成后,事中审核数据接口模块根据审核任务绑定的请求方的地址,将组装结果加密压缩,发送给审核请求方;同时,在发送成功后,将审核相关数据和审核任务信息备份到数据库,实现审核任务持久化,任务管理更改任务审核状态为审核成功,审核线程结束并将审核线程返还线程池,整个事中审核完成。S217: After the assembly is completed, the in-process audit data interface module encrypts and compresses the assembly result according to the address of the requester bound to the audit task, and sends it to the audit requester; at the same time, after the sending is successful, the audit-related data and audit task information are sent to the audit requester. Backup to the database to achieve audit task persistence, task management changes the task audit status to audit success, the audit thread ends and the audit thread is returned to the thread pool, and the entire audit is completed.
所述的事后审核子步骤,包括以下子步骤:The post-review sub-steps described include the following sub-steps:
S221:事后审核数据接口捕获审核请求;其中所述的审核请求为审核请求方将验证信息、审核要求和业务数据封装成JSON数据包,然后加密压缩并设置为接口输入数据,传输到审核平台的审核请求;S221: The post-event audit data interface captures the audit request; the audit request is that the audit requester encapsulates the verification information, audit requirements and business data into JSON data packets, and then encrypts and compresses it and sets it as the interface input data, and transmits it to the audit platform. review requests;
S222:事后审核数据接口将上传数据解压解密,解析出验证信息,将验证信息与审核服务注册信息进行对比验证,如果验证通过,则进入步骤S223;否则,事后审核数据接口将审核服务受限提示信息返回审核请求方;S222: The post-audit data interface decompresses and decrypts the uploaded data, parses out the verification information, and compares the verification information with the audit service registration information for verification. If the verification is passed, go to step S223; otherwise, the post-audit data interface will prompt the audit service limited The information is returned to the audit requester;
S223:事后审核数据接口解析审核要求,如果审核要求解析成功,则任务管理子单元创建审核任务、初始化审核任务、绑定请求方信息、设置审核要求,设置任务状态为审核数据待解析,并进入步骤S224;否则,事后审核数据接口将错误信息返回给审核请求方,线程结束并将线程返还线程池;S223: After the audit data interface parses the audit request, if the audit request is successfully parsed, the task management subunit creates an audit task, initializes the audit task, binds the requester information, sets the audit request, sets the task status to audit data pending analysis, and enters the Step S224; otherwise, after the audit data interface returns the error information to the audit requester, the thread ends and the thread is returned to the thread pool;
S224:事后审核数据接口基于业务数据结构解析业务数据,如果解析业务数据成功,事后审核数据接口将业务数据转换为业务JavaBean对象,业务JavaBean对象绑定审核任务号,保存到内存缓存,将审核任务挂载到待审核队列,更改任务状态为待审核,转入事后审核引擎进行业务审核,返回审核任务号给审核请求方,线程结束并将线程返还线程池,进入步骤S225;否则,更改任务状态为审核数据解析失败,将错误信息返回给审核请求方,线程结束并将线程返还线程池;S224: The post-event audit data interface parses the business data based on the business data structure. If the parsing of the business data is successful, the post-event audit data interface converts the business data into a business JavaBean object, and the business JavaBean object binds the audit task number, saves it to the memory cache, and stores the audit task. Mount it to the pending review queue, change the task status to pending review, transfer it to the post-event review engine for business review, return the review task number to the review requester, end the thread and return the thread to the thread pool, and enter step S225; otherwise, change the task status In order to audit the data analysis failure, return the error information to the audit requester, the thread ends and the thread is returned to the thread pool;
S225:事后审核引擎的审核组件、组装组件、结果传回组件和备份组件分别对对应队列进行处理:S225: The audit component, assembly component, result return component and backup component of the post-event audit engine process the corresponding queues respectively:
(1)审核组件监听待审核队列是否有待审核任务,当监听到待审核队列有待审核任务时,从队头取出待审核任务,取出后从线程池取出空闲的线程执行待审核任务,任务管理子单元更改审核任务状态为审核中,事后审核引擎根据审核任务的审核要求,从编译后的业务规则库提取本次审核涉及的业务规则包;基于提取的业务规则包,创建审核会话,根据任务号从内存缓存中提取业务JavaBean对象,将业务JavaBean对象加载到审核会话中,执行审核会话;审核会话结束后,审核结果绑定任务号,保存到内存缓存,更改审核任务状态为待组装,将审核任务挂载到待组装队列,线程结束并将线程返还线程池;(1) The audit component monitors whether there are tasks to be audited in the queue to be audited. When it monitors the queue to be audited, it takes out the tasks to be reviewed from the head of the queue, and then takes out the idle threads from the thread pool to execute the tasks to be reviewed. The task manager The status of the unit change audit task is under review. The post-event audit engine extracts the business rule package involved in this audit from the compiled business rule library according to the audit requirements of the audit task. Based on the extracted business rule package, an audit session is created, and the task number Extract the business JavaBean object from the memory cache, load the business JavaBean object into the audit session, and execute the audit session; after the audit session ends, the audit result is bound to the task number, saved to the memory cache, and the audit task status is changed to pending assembly. The task is mounted to the queue to be assembled, the thread ends and the thread is returned to the thread pool;
(2)组装组件监听待组装队列是否有待组装的任务,当监听到待组装队列有待组装任务,从队头取出待组装任务,取出后从线程池取出空闲的线程执行待组装任务,更改审核任务状态为组装中,根据任务号从内存缓存中提取出审核结果,按返回结果标准格式组装审核结果,组装完成后,绑定任务号,将组装结果保存到内存缓存,更改审核任务状态为待传回,将审核任务挂载到待传回队列,线程结束并将线程返还线程池;(2) The assembly component monitors whether there are tasks to be assembled in the queue to be assembled. When it monitors the queue to be assembled, it takes out the tasks to be assembled from the head of the queue, and then takes out the idle threads from the thread pool to execute the tasks to be assembled, and changes the audit task. The status is assembling, extract the audit result from the memory cache according to the task number, and assemble the audit result according to the standard format of the returned result. After the assembly is completed, bind the task number, save the assembly result to the memory cache, and change the audit task status to pending. Back, mount the audit task to the queue to be returned, the thread ends and the thread is returned to the thread pool;
(3)结果传回组件监听待传回队列是否有待传回任务,当监听到待传回队列有待传回任务,从队头取出待传回任务,取出后从线程池取出空闲的线程执行待传回任务,更改审核任务状态为传回中,根据任务号从内存缓存中提取组装结果,事后审核数据接口根据审核任务绑定的请求方地址,将组装结果加密压缩,发送给请求方,发送成功后,更改审核任务状态为待备份,将审核任务挂载到待备份队列,线程结束并将线程返还线程池;(3) The result-returning component monitors whether the queue to be returned has tasks to be sent back. When it monitors the queue to be sent back, it takes out the tasks to be sent back from the head of the queue, and then takes out the idle threads from the thread pool for execution. Return the task, change the status of the audit task to returning, extract the assembly result from the memory cache according to the task number, and then the audit data interface encrypts and compresses the assembly result according to the requester address bound to the audit task, and sends it to the requester. After success, change the status of the audit task to be backed up, mount the audit task to the queue to be backed up, end the thread and return the thread to the thread pool;
(4)备份组件监听待备份队列是否有待备份任务,当监听到待备份队列有待备份任务,从队头取出待备份任务,取出后从线程池取出空闲的线程执行待备份任务,更改审核任务状态为备份中,将内存缓存中和该审核任务有关的所有数据持久化,保存到数据库,保存完成后,清除内存缓存中该审核任务的所有数据,降低内存缓存压力,更改审核任务状态为审核成功,线程结束并将线程返还线程池。(4) The backup component monitors whether there are tasks to be backed up in the queue to be backed up. When it monitors that there are tasks to be backed up in the queue to be backed up, it takes out the tasks to be backed up from the head of the queue, and then takes out the idle threads from the thread pool to execute the tasks to be backed up and changes the status of the audit tasks. For backup, persist all data related to the audit task in the memory cache and save it to the database. After saving, clear all data of the audit task in the memory cache, reduce the pressure on the memory cache, and change the audit task status to audit successful. , the thread ends and the thread is returned to the thread pool.
本发明的有益效果是:The beneficial effects of the present invention are:
(1)实现平台审核领域通用化,审核领域不局限于特定领域(财务报销、行政审批等),审核平台运行时的审核领域,是用户从项目库中选择的一个实例化项目涉及的领域,因为项目库可以包含多个领域的实例化项目,因此本审核平台方案支持多个审核领域,实现了审核领域通用化。(1) Realize the generalization of the platform audit field. The audit field is not limited to specific fields (financial reimbursement, administrative approval, etc.). The audit field when the audit platform is running is the field involved in an instantiated project selected by the user from the project library. Because the project library can contain instantiated projects in multiple fields, this audit platform solution supports multiple audit fields and realizes the generalization of audit fields.
(2)业务数据无关性,审核平台开发时不关心实际处理的业务数据,解决现有技术在开发时已经默认设置需要处理的业务数据结构,部署后只能解析与默认设置的业务数据结构相对应的业务数据,突出审核平台处理业务数据范围的局限性,导致这种审核平台存在缺陷的问题。(2) The business data is irrelevant. The review platform does not care about the business data actually processed during development, and solves the problem that the existing technology has set the business data structure to be processed by default during development. After deployment, it can only parse the business data structure that is related to the default setting. The corresponding business data highlights the limitations of the audit platform's processing of business data, which leads to the problem of defects in this audit platform.
(3)业务审核逻辑无关性,审核平台部署时不关心实际处理的业务审核逻辑,解决现有技术需要在开发时确定具体的业务审核逻辑,并在开发过程中固化在代码里,大大降低了系统的扩展性和灵活性的问题。(3) The business audit logic is irrelevant. When the audit platform is deployed, it does not care about the actual business audit logic. To solve the existing technology, it is necessary to determine the specific business audit logic during development and solidify it in the code during the development process, which greatly reduces the cost of The scalability and flexibility of the system.
(4)支持不同的审核应用场景,本审核平台支持事中审核和事后审核两种审核方式。业务审核方式根据实时性、响应速度和数据量的不同审核要求,相应处理方式也应不同。(4) Supporting different audit application scenarios, this audit platform supports two audit methods: in-process audit and post-event audit. The business audit method should be handled differently according to the different audit requirements of real-time, response speed and data volume.
附图说明Description of drawings
图1为审核平台模块层级结构示意图;Fig. 1 is a schematic diagram of the hierarchical structure of the audit platform module;
图2为项目构建模块基于B/S架构的示意图;Figure 2 is a schematic diagram of the project building module based on the B/S architecture;
图3为实例化项目示意图;Figure 3 is a schematic diagram of an instantiated project;
图4为项目库结构及审核平台实现方案示意图;Figure 4 is a schematic diagram of the project library structure and the implementation scheme of the audit platform;
图5为业务规则库单元示意图;5 is a schematic diagram of a business rule library unit;
图6为规则流的业务流程图组织结构图;Fig. 6 is the business flow chart organization chart of rule flow;
图7为事中审核流程图;Figure 7 is a flow chart of the in-process audit;
图8为事后审核流程图。Figure 8 is a flow chart of the post-event audit.
具体实施方式Detailed ways
下面结合附图进一步详细描述本发明的技术方案:The technical scheme of the present invention is described in further detail below in conjunction with the accompanying drawings:
实施例1的审核平台由项目构建模块和智能审核模块两部分构成,其中,项目构建模块实现审核领域通用化,为智能审核执行审核任务提供支持;智能审核模块实现业务数据审核,提供可选的审核应用场景。本实施例的模块层级结构如图1所示。The auditing platform of Embodiment 1 is composed of two parts: a project building module and an intelligent auditing module, wherein the project building module realizes the generalization of the auditing field and provides support for the intelligent auditing to perform auditing tasks; the intelligent auditing module realizes business data auditing and provides optional Review application scenarios. The module hierarchy structure of this embodiment is shown in FIG. 1 .
如图2所示,在本实施例中,项目构建模块是基于B/S架构,用户通过终端浏览器登录智能审核平台,管理项目库;采用该实施例的方式,使得用户可以快速管理项目库。在另外一个实施例中,项目构建模块是基于C/S架构,用户通过终端安装对应客户端后登录智能审核平台,管理项目库。As shown in Figure 2, in this embodiment, the project building module is based on the B/S architecture, and the user logs in to the intelligent audit platform through the terminal browser to manage the project library; the method of this embodiment enables the user to quickly manage the project library . In another embodiment, the project building module is based on the C/S architecture, and the user installs the corresponding client through the terminal and logs into the intelligent auditing platform to manage the project library.
项目构建实现平台审核领域通用化,审核领域不局限于特定领域(财务报销、行政审批等),审核平台运行时的审核领域,是用户从项目库中选择的一个实例化项目涉及的领域,因为项目库可以包含多个领域的实例化项目,因此本审核平台方案支持多个审核领域,实现了审核领域通用化。The project construction realizes the generalization of the platform audit field. The audit field is not limited to specific fields (financial reimbursement, administrative approval, etc.). The audit field when the audit platform is running is the field involved in an instantiated project selected by the user from the project library, because The project library can contain instantiated projects in multiple fields, so this audit platform solution supports multiple audit fields and realizes the generalization of audit fields.
项目构建模块负责管理项目库,如图4所示,项目库由零或多个实例化项目组成。The project building block is responsible for managing the project library, shown in Figure 4, which consists of zero or more instantiated projects.
如图3所示,实例化项目由业务数据单元、业务数据库单元、业务JavaBean单元和业务规则库单元组成。具体地:As shown in Figure 3, the instantiated project consists of a business data unit, a business database unit, a business JavaBean unit and a business rule library unit. specifically:
业务数据单元管理业务数据结构。其中,业务数据结构由数据表信息和字段信息组成,为解析审核请求方上传JSON数据包提供解析方案,为业务数据库单元、业务JavaBean单元和业务规则库单元管理提供支持。The business data unit manages business data structures. Among them, the business data structure is composed of data table information and field information, providing a parsing scheme for parsing and reviewing the requester uploading JSON data packets, and providing support for the management of business database units, business JavaBean units and business rule base units.
业务数据库单元基于业务数据结构,管理业务数据库,为持久化审核数据提供物理存储支持。Based on the business data structure, the business database unit manages the business database and provides physical storage support for persistent audit data.
业务JavaBean单元基于业务数据结构,管理业务JavaBean集。当审核请求到达时,为审核数据转换为实例化业务JavaBean对象提供支持。通过这种转换操作,审核平台可以操作审核数据,完成审核过程中的数据处理操作。The business JavaBean unit manages the business JavaBean set based on the business data structure. Provides support for the transformation of audit data into instantiated business JavaBean objects when audit requests arrive. Through this conversion operation, the audit platform can operate the audit data and complete the data processing operations in the audit process.
业务规则库单元将实例化项目的业务审核逻辑转换为Drools规则引擎能够识别的规则和规则流。当审核平台进行业务数据审核时,会依照用户定义的规则或规则流对审核数据进行审核。The business rule base unit converts the business audit logic of the instantiated project into rules and rule flows that can be recognized by the Drools rules engine. When the audit platform conducts business data audit, the audit data will be audited according to user-defined rules or rule flow.
在本实施例中,对项目库管理包括实例化项目添加、修改、查看和删除。In this embodiment, managing the project library includes adding, modifying, viewing and deleting instantiated projects.
具体地,对于实例化项目添加:Specifically, for instantiated items add:
在本实施例中,首先在实例化项目添加模板指导下,添加项目名、项目编号、项目介绍、业务数据库账号和密码等基本信息。In this embodiment, first, under the guidance of the instantiated project adding template, basic information such as project name, project number, project introduction, business database account and password is added.
其中,项目编号作为审核平台区分实例化项目标识,由英文、数字和下划线组成,且第一个位置为英文;业务数据库账号和密码,在提交添加申请后,在数据库创建对应的数据库账号,创建的数据库账号作为实例化项目的业务数据库,存储实例化项目的业务数据。Among them, the project number is used as the identification of the instantiated project for the audit platform, which is composed of English, numbers and underscores, and the first position is English; the business database account and password, after submitting the application for addition, create the corresponding database account in the database, create The database account of the instantiated project is used as the business database of the instantiated project to store the business data of the instantiated project.
当实例化项目添加成功后,进入实例化项目管理。实例化项目管理包括业务数据模块、业务数据库模块、业务JavaBean模块和业务规则模块。When the instantiation project is added successfully, enter the instantiation project management. The instantiation project management includes business data module, business database module, business JavaBean module and business rule module.
对于添加业务数据结构,需要分别对数据表信息和字段信息进行添加:For adding business data structures, data table information and field information need to be added separately:
在数据表信息添加模板指导下,添加数据表信息,数据表信息包括数据表名、数据表编号、数据表介绍和生成标志,其中:Under the guidance of the data table information adding template, add data table information. The data table information includes the data table name, data table number, data table introduction and generation flag, among which:
数据表名为中文,为该数据表的中文名;The data table name is Chinese, which is the Chinese name of the data table;
数据表介绍为中文,详细介绍该数据表;The data sheet is introduced in Chinese, and the data sheet is introduced in detail;
生成标志表示该数据表信息是否生成对应业务JavaBean,是否在数据库中生成对应业务数据表;The generation flag indicates whether the data table information generates the corresponding business JavaBean, and whether the corresponding business data table is generated in the database;
数据表编号由英文、数字和下划线组成,且第一个位置为英文,作为业务数据表的表名和业务JavaBean的类名。The data table number consists of English, numbers and underscores, and the first position is English, which is used as the table name of the business data table and the class name of the business JavaBean.
在数据表信息添加完成后,在字段信息添加模板指导下,添加该业务数据结构的所有字段信息,字段信息包括字段名、字段描述、字段编号、字段数据类型和大小、主键标志、可空标识、缺省值和关心标识,其中:After the data table information is added, under the guidance of the field information addition template, add all the field information of the business data structure. The field information includes field name, field description, field number, field data type and size, primary key flag, and nullable flag. , default and care flags, where:
字段名为中文,为该字段的中文名;The field name is Chinese, which is the Chinese name of the field;
字段描述为中文,详细介绍该字段;The field description is in Chinese, and the field is described in detail;
字段编号作为业务数据表的字段名和业务JavaBean的类成员变量名,由英文、数字和下划线组成,且第一个位置为英文;The field number is used as the field name of the business data table and the class member variable name of the business JavaBean, which consists of English, numbers and underscores, and the first position is English;
字段数据类型和大小对应数据库的字段数据类型和大小,比如varchar2(40)、number(10)和number(8,2)等,作为业务数据表该字段的数据类型和大小;根据与Java数据类型对应关系,作为业务JavaBean中该类成员变量的数据类型;The field data type and size correspond to the field data type and size of the database, such as varchar2(40), number(10) and number(8,2), etc., as the data type and size of the field in the business data table; Correspondence, as the data type of the member variable of this class in the business JavaBean;
主键标志表示该字段在业务数据表中是否为主键;The primary key flag indicates whether the field is the primary key in the business data table;
可空标识表示该字段在业务数据表中是否可以为空;The nullable flag indicates whether the field can be nullable in the business data table;
缺省值表示该字段为空时的缺省值;The default value indicates the default value when the field is empty;
关心标识表示该字段是否为关心数据,在业务审核时,当该数据表数据触发了业务规则,需要将为关心数据的字段数据拼接在审核结果,返回给审核请求方。The care flag indicates whether the field is the data of interest. During business audit, when the data in the data table triggers the business rule, the field data of the data of interest needs to be spliced into the audit result and returned to the audit requester.
在本实施例中,当业务数据结构的所有字段信息添加完成后,业务数据模块为该业务数据结构添加任务编号字段和任务数据索引字段,其中:In this embodiment, after all field information of the business data structure is added, the business data module adds a task number field and a task data index field to the business data structure, wherein:
任务编号字段记录该条数据属于哪个审核任务,将数据以任务编号进行聚类区分;The task number field records which audit task the piece of data belongs to, and the data is clustered and distinguished by the task number;
任务数据索引字段标识该条数据是审核任务的哪一条业务数据,便于区分定位审核任务的业务数据。The task data index field identifies which piece of business data of the audit task the piece of data is, so as to facilitate distinguishing and locating the business data of the audit task.
任务编号字段和任务数据索引字段对于用户不可见,为审核平台内部操作所需,每个业务数据结构添加时都会自动生成这两个字段。The task number field and the task data index field are not visible to users. They are required for auditing the internal operations of the platform. These two fields are automatically generated when each business data structure is added.
完成任务编号字段和任务数据索引字段自动生成后,业务数据模块会将该业务数据结构的数据表信息和字段信息进行关联,通过对每个字段信息绑定数据表编号,将该业务数据结构的数据表信息和字段信息关联起来。After completing the automatic generation of the task number field and the task data index field, the business data module will associate the data table information and field information of the business data structure, and bind the data table number to each field information. The data table information is associated with the field information.
经过上述一系列操作后,业务数据结构添加完成。After the above series of operations, the business data structure is added.
在添加业务数据结构过程中,可能存在数据表信息和字段信息的修改和删除。在没有生成对应业务数据表和业务JavaBean的条件下,实现流程如信息系统的修改和删除流程。During the process of adding business data structures, there may be modifications and deletions of data table information and field information. Under the condition that the corresponding business data table and business JavaBean are not generated, the process such as the modification and deletion process of the information system is realized.
实例化项目可能包括多个业务数据结构,每个业务数据结构的添加流程如上所述。An instantiated project may include multiple business data structures, and the process of adding each business data structure is described above.
在完成业务数据结构构建的前提下,业务数据库模块、业务JavaBean集模块和业务规则库模块的构建顺序没有关联,任意顺序进行。On the premise of completing the construction of the business data structure, the construction order of the business database module, the business JavaBean set module and the business rule library module is not related and can be carried out in any order.
在本实施例中,在业务数据结构成功添加前提下,业务数据库模块根据该业务数据结构的数据表编号和与该数据表编号绑定的字段信息,其中字段信息包括字段编号、字段数据类型和大小、主键标志、可空标识、缺省值,构造创建数据表SQL语句。构成完成后,在实例化项目业务数据库中执行构造的SQL语句,完成业务数据表创建,更新该业务数据结构数据表信息的生成标志,表明业务数据表已生成。In this embodiment, on the premise that the business data structure is successfully added, the business database module uses the data table number of the business data structure and the field information bound to the data table number, wherein the field information includes the field number, field data type and Size, primary key flag, nullable flag, default value, construct SQL statement to create data table. After the construction is completed, the constructed SQL statement is executed in the instantiated project business database to complete the creation of the business data table, and the generation flag of the data table information of the business data structure is updated, indicating that the business data table has been generated.
业务数据库模块将实例化项目的所有业务数据结构一一生成对应的业务数据表,构建业务数据库。The business database module will instantiate all business data structures of the project to generate corresponding business data tables one by one, and build a business database.
在本实施例中,在业务数据结构成功添加前提下,业务JavaBean模块根据该业务数据结构的数据表编号和与该数据表编号绑定的字段信息,其中字段信息包括字段编号、字段数据类型和大小,构造对应业务JavaBean的java文件。In this embodiment, on the premise that the business data structure is successfully added, the business JavaBean module uses the data table number of the business data structure and the field information bound to the data table number, wherein the field information includes the field number, field data type and Size, construct the java file corresponding to the business JavaBean.
构造方案为:数据表编号经过驼峰命名法处理后,将首字母大写,作为类名。字段编号经过驼峰命名法处理后,作为类成员变量名,根据字段数据类型和大小确定类成员变量的数据类型,比如number(4)为Integer,number(10)为Long,varchar2为String等。The construction scheme is: after the data table number is processed by camel case, the first letter is capitalized as the class name. After the field number is processed by camel case, it is used as the name of the class member variable, and the data type of the class member variable is determined according to the field data type and size. For example, number(4) is Integer, number(10) is Long, and varchar2 is String.
完成构造类成员变量后,为每个类成员变量构造对应的get和set存取方法。如类成员变量 userName 的存取方法为 setUserName和getUserName。After completing the construction of class member variables, construct corresponding get and set access methods for each class member variable. For example, the access methods of the class member variable userName are setUserName and getUserName.
业务JavaBean的java文件构造完成后,使用java语言编程编译器javac将java文件编译生成class文件,更新该业务数据结构数据表信息的生成标志,表明业务JavaBean已生成。审核平台启动时将生成的class文件加载到JVM,可以将上传的审核数据转换为实例化JavaBean对象,使平台能够在JVM中操作审核数据,同时审核数据JavaBean对象能插入审核会话中,作为审核引擎Work Memory中fact对象,去匹配业务规则进行审核。After the java file of the business JavaBean is constructed, use the java language programming compiler javac to compile the java file to generate a class file, and update the generation flag of the business data structure data table information, indicating that the business JavaBean has been generated. When the audit platform starts, the generated class file is loaded into the JVM, and the uploaded audit data can be converted into an instantiated JavaBean object, so that the platform can operate the audit data in the JVM, and the audit data JavaBean object can be inserted into the audit session as the audit engine. The fact object in Work Memory matches business rules for review.
业务JavaBean模块将实例化项目的所有业务数据结构一一生成对应的业务JavaBean,构建业务JavaBean集。The business JavaBean module will instantiate all business data structures of the project to generate corresponding business JavaBeans one by one, and build a business JavaBean set.
在本实施例中,完成实例化项目的业务数据结构添加后,添加业务规则库。In this embodiment, after adding the business data structure of the instantiated project, the business rule base is added.
如图5所示,基于Drools规则引擎的业务规则分为规则和规则流。As shown in Figure 5, business rules based on the Drools rule engine are divided into rules and rule flows.
其中,规则的结构如下:Among them, the structure of the rules is as follows:
rule "name" --规则名rule "name" -- rule name
attributes --属性部分attributes -- attributes section
whenwhen
LHS --条件部分LHS -- Conditions Section
then RHS --结果部分then RHS -- results section
endend
规则通常包括三个部分: 属性部分(attribute)、条件部分(LHS)和结果部分(RHS)。A rule usually consists of three parts: an attribute part, a condition part (LHS) and a result part (RHS).
属性部分(attribute): 定义当前规则执行的一些属性等,比如是否可被重复执行、过期时间、生效时间等。Attribute part: Define some attributes of the current rule execution, such as whether it can be executed repeatedly, expiration time, effective time, etc.
条件部分(LHS): 定义当前规则的条件,条件可以是单个, 也可以有多个。业务数据结构为条件部分构建提供支持。Condition Section (LHS): Defines the condition of the current rule. The condition can be single or multiple. Business data structures provide support for conditional part construction.
结果部分(RHS): 定义满足当前条件部分后执行的操作。业务数据结构为结果部分构建提供支持。Result Section (RHS): Defines what to do when the current condition section is met. The business data structure provides support for the result part construction.
如图6所示,规则流基于业务流程图实现。业务流程图描述了一系列需要执行的审核业务的顺序,它由规则、条件分支和分支聚合三部分组成。As shown in Figure 6, the rule flow is implemented based on the business flow chart. The business flow diagram describes a series of audit business sequences that need to be performed, and it consists of three parts: rules, conditional branches, and branch aggregation.
业务规则库模块负责管理业务规则库,包括业务规则的添加、修改、查看和删除。The business rule base module is responsible for managing the business rule base, including adding, modifying, viewing and deleting business rules.
在本实施例中,业务规则的添加/修改/查看/删除:基于Web浏览器方式,用户在业务规则添加模板指导下,添加/修改/查看/删除规则或者规则流,提交添加/修改/查看/删除后,审核平台在规则库中生成业务规则。In this embodiment, adding/modifying/viewing/deleting business rules: based on a web browser, the user adds/modifies/views/deletes a rule or rule flow under the guidance of a business rule adding template, and submits the addition/modification/view / After deletion, the audit platform generates business rules in the rule base.
完成业务数据结构、业务数据库、业务JavaBean集和业务规则库添加后,实例化项目添加流程完成。After the business data structure, business database, business JavaBean set and business rule library are added, the instantiation project adding process is completed.
在本实施例中,对于实例化项目修改:In this example, for instantiated item modifications:
在实例化项目修改模板指导下,可以修改项目名和项目介绍,项目编号、业务数据库账号和密码不能修改。Under the guidance of the instantiated project modification template, the project name and project introduction can be modified, but the project number, business database account number and password cannot be modified.
通过业务数据模块修改业务数据结构,其中包括数据表信息修改和字段信息修改。Modify the business data structure through the business data module, including data table information modification and field information modification.
数据表信息的数据表名和数据表介绍可以修改,数据表编号和生成标志不能修改。The data table name and data table description of the data table information can be modified, but the data table number and generation flag cannot be modified.
字段信息的字段名、字段描述和关心标识可以修改,不影响业务数据库和业务JavaBean集。The field name, field description and care identifier of the field information can be modified without affecting the business database and business JavaBean set.
字段信息的字段编号不能修改,字段数据类型和大小、主键标志、可空标识和缺省值可以修改。The field number of field information cannot be modified, but the field data type and size, primary key flag, nullable flag and default value can be modified.
当字段数据类型和大小被修改时,会触发业务数据库模块修改业务数据库和业务JavaBean模块修改业务JavaBean集。When the field data type and size are modified, the business database module will be triggered to modify the business database and the business JavaBean module will be triggered to modify the business JavaBean set.
当主键标志、可空标识和缺省值被修改时,会触发业务数据库模块修改业务数据库。When the primary key flag, the nullable flag and the default value are modified, the business database module will be triggered to modify the business database.
对于字段数据类型和大小、可空标识和缺省值被修改的情况,业务数据库模块根据绑定的数据表编号和字段编号,获取最新的字段数据类型和大小、可空标识和缺省值,然后构造修改数据库字段SQL语句,在实例化项目业务数据库执行构造的SQL语句,完成对应业务数据表修改。When the field data type and size, nullable flag and default value are modified, the business database module obtains the latest field data type and size, nullable flag and default value according to the bound data table number and field number. Then construct the SQL statement to modify the database field, execute the constructed SQL statement in the instantiated project business database, and complete the modification of the corresponding business data table.
对于主键标志被修改的情况,业务数据库模块根据绑定的数据表编号遍历其绑定的字段信息,查询出所有为主键的字段编号,构造创建主键SQL语句,在实例化项目业务数据库先执行删除已有主键操作,再执行构造的SQL语句,完成对应业务数据表主键修改。For the case where the primary key flag is modified, the business database module traverses the bound field information according to the bound data table number, queries all the field numbers of the primary key, constructs the SQL statement to create the primary key, and executes the delete first in the instantiated project business database If there is a primary key operation, execute the constructed SQL statement to complete the primary key modification of the corresponding business data table.
对于字段数据类型和大小被修改的情况,业务JavaBean模块根据绑定的数据表编号和与该数据表编号绑定的字段信息,其中字段信息包括字段编号、字段数据类型和大小,构造对应业务JavaBean的java文件,构造方案如上文。java文件构造完成后,覆盖替换已有的java文件,使用java语言编程编译器javac将新的java文件编译生成新的class文件,覆盖替换已有的class文件。In the case where the field data type and size are modified, the business JavaBean module constructs the corresponding business JavaBean according to the bound data table number and the field information bound to the data table number, where the field information includes the field number, field data type and size The java file, the construction scheme is as above. After the java file is constructed, overwrite and replace the existing java file, use the java language programming compiler javac to compile the new java file to generate a new class file, and overwrite and replace the existing class file.
业务规则库可以通过业务规则模块修改。The business rule base can be modified through the business rules module.
在本实施例中,对于实例化项目修改:In this example, for instantiated item modifications:
发起实例化项目删除后,审核平台会把所有和该项目有关的数据删除,包括项目信息、业务数据结构、业务规则库、业务JavaBean集和业务数据库等。注销业务数据库账号。After initiating deletion of an instantiated project, the audit platform will delete all data related to the project, including project information, business data structure, business rule library, business JavaBean set, and business database. Log out of the business database account.
项目构建的核心操作如上所述。The core operation of a project build is as described above.
平台审核领域通用化实现方案如图4所示,审核平台启动时根据用户配置信息,从项目库中选择一个实例化项目部署启动。The generalized implementation scheme in the field of platform auditing is shown in Figure 4. When the auditing platform is started, according to the user configuration information, an instantiated project is selected from the project library to be deployed and started.
智能审核有事中审核和事后审核两种审核方式。Smart auditing has two auditing methods: in-process auditing and post-event auditing.
事中审核适用于实时性要求高、响应速度快、数据量小的审核任务,由第一审核数据接口、第一任务管理和事中审核引擎组成。其中:第一审核数据接口负责管理审核平台和审核请求方之间的数据通信,包括监听审核请求、解析审核请求和审核结果传回等;第一任务管理负责维护任务表、创建审核任务、更改任务状态和结束审核任务等,所有审核任务信息记录在任务表中,便于审核平台管理审核任务;事中审核引擎负责处理事中审核,包括业务数据审核、审核结果组装和审核任务持久化。The in-event audit is suitable for audit tasks with high real-time requirements, fast response speed and small data volume, and consists of the first audit data interface, the first task management and the in-process audit engine. Among them: the first audit data interface is responsible for managing the data communication between the audit platform and the audit requester, including monitoring audit requests, parsing audit requests, and returning audit results; the first task management is responsible for maintaining the task table, creating audit tasks, changing Task status and end audit tasks, etc. All audit task information is recorded in the task table, which is convenient for the audit platform to manage audit tasks; the in-process audit engine is responsible for processing in-process audit, including business data audit, audit result assembly, and audit task persistence.
事中审核引擎包括业务数据审核组件、审核结果组装组件和审核任务持久化组件。其中,业务数据审核组件审核业务数据;审核结果组装组件按返回结果标准格式组装审核结果;核任务持久化组件将审核任务信息、业务数据和审核结果等持久化到物理数据库。The in-event audit engine includes a business data audit component, an audit result assembly component, and an audit task persistence component. Among them, the business data audit component audits business data; the audit result assembly component assembles audit results according to the standard format of returned results; the core task persistence component persists audit task information, business data and audit results to the physical database.
在本实施例中,事中审核的审核流程是一个非流水线方式,线性执行,同步过程。事中审核流程如图7所示:In this embodiment, the review process of the in-event review is a non-pipeline, linear execution, and synchronous process. The in-process review process is shown in Figure 7:
S11:审核请求方将验证信息、审核要求和业务数据封装成JSON数据,然后加密压缩,设置为接口输入数据,调用事中审核接口发起请求,审核请求通过Internet传输到审核平台。S11: The audit requester encapsulates the verification information, audit requirements and business data into JSON data, then encrypts and compresses it, sets it as the interface input data, calls the in-process audit interface to initiate a request, and transmits the audit request to the audit platform through the Internet.
S12:第一审核数据接口捕获到审核请求,将上传数据解压解密,解析出验证信息,将验证信息与审核服务注册信息进行对比验证:如果验证通过,进入步骤S13;如果验证不通过,第一审核数据接口返回审核服务受限提示信息,并结束。S12: The first audit data interface captures the audit request, decompresses and decrypts the uploaded data, parses the verification information, and compares the verification information with the audit service registration information for verification: if the verification passes, go to step S13; if the verification fails, the first The audit data interface returns the prompt message that the audit service is restricted, and ends.
S13:第一审核数据接口解析审核要求:如果审核要求解析成功,第一任务管理创建审核任务,初始化审核任务,绑定请求方信息,设置审核要求,并进入步骤S14;如果审核要求解析不成功,第一审核数据接口将错误信息返回请求方。S13: The first audit data interface parses the audit request: if the audit request is successfully parsed, the first task management creates an audit task, initializes the audit task, binds the requester information, sets the audit request, and proceeds to step S14; if the audit request parsing is unsuccessful , the first audit data interface returns error information to the requester.
S14:第一审核数据接口基于业务数据结构解析业务数据,如果业务数据解析成功,数据接口将业务数据转换为实例化业务JavaBean对象,转入事中审核引擎进行业务审核即步骤S15;反之第一任务管理注销审核任务,第一审核数据接口将错误信息返回请求方;S14: The first audit data interface parses the business data based on the business data structure. If the business data parsing is successful, the data interface converts the business data into an instantiated business JavaBean object, and transfers it to the in-process audit engine for business audit, that is, step S15; otherwise, the first The task management cancels the audit task, and the first audit data interface returns the error information to the requester;
S15:事中审核引擎根据审核任务的审核要求,从编译后的业务规则库提取本次审核涉及的业务规则包。基于提取的业务规则包,创建审核会话,将业务数据JavaBean对象加载到审核会话中,执行审核会话。S15: The in-process audit engine extracts the business rule package involved in this audit from the compiled business rule library according to the audit requirements of the audit task. Based on the extracted business rule package, an audit session is created, the business data JavaBean object is loaded into the audit session, and the audit session is executed.
S16:审核会话结束后,按返回结果标准格式组装审核结果,组装完成后,第一审核数据接口根据审核任务绑定的请求方的地址,将组装结果加密压缩,发送给审核请求方。发送成功后,将审核相关数据和审核任务信息备份到数据库,实现审核任务持久化,第一任务管理更改任务审核状态为审核成功,审核线程结束并将审核线程返还线程池,整个事中审核完成。S16: After the audit session ends, assemble the audit result according to the standard format of the returned result. After the assembly is completed, the first audit data interface encrypts and compresses the assembly result according to the address of the requester bound to the audit task, and sends it to the audit requester. After the sending is successful, the audit-related data and audit task information are backed up to the database to achieve audit task persistence. The first task management changes the task audit status to audit successful, the audit thread ends and the audit thread is returned to the thread pool, and the entire in-process audit is completed. .
事后审核适用于实时性要求低、响应速度较快、数据量大的审核任务,由第二审核数据接口、第二任务管理和事后审核引擎组成。The post-event audit is suitable for audit tasks with low real-time requirements, fast response speed and large amount of data. It consists of the second audit data interface, the second task management and the post-event audit engine.
其中:第二审核数据接口负责管理审核平台和审核请求方之间的数据通信,包括监听审核请求、解析审核请求和审核结果传回等;第二任务管理负责维护任务表、创建审核任务、更改任务状态和结束审核任务等,所有审核任务信息记录在任务表中,便于审核平台管理审核任务;事中审核引擎负责处理事中审核,包括业务数据审核、审核结果组装和审核任务持久化。Among them: the second audit data interface is responsible for managing the data communication between the audit platform and the audit requester, including monitoring the audit request, parsing the audit request and returning the audit result, etc.; the second task management is responsible for maintaining the task table, creating audit tasks, changing Task status and end audit tasks, etc. All audit task information is recorded in the task table, which is convenient for the audit platform to manage audit tasks; the in-process audit engine is responsible for processing in-process audit, including business data audit, audit result assembly, and audit task persistence.
事后审核引擎包括业务数据审核组件、审核结果组装组件、结果传回组件和审核任务持久化组件。其中,业务数据审核组件审核业务数据;审核结果组装组件按返回结果标准格式组装审核结果;结果传回组件基于第二审核数据接口,将组装的审核结果传回审核请求方;任务持久化组件将审核任务信息、业务数据和审核结果等持久化到物理数据库。The post-event audit engine includes a business data audit component, an audit result assembly component, a result return component, and an audit task persistence component. Among them, the business data audit component audits the business data; the audit result assembly component assembles the audit results according to the standard format of returned results; the result return component transmits the assembled audit results back to the audit requester based on the second audit data interface; the task persistence component will Audit task information, business data and audit results are persisted to the physical database.
在本实施例中,事后审核的审核流程是一个流水线方式,并行执行,异步过程。具体流程如图8所示:In this embodiment, the review process of the post-event review is a pipeline method, executed in parallel, and an asynchronous process. The specific process is shown in Figure 8:
S201:审核请求方将验证信息、审核要求和业务数据封装成JSON数据,加密压缩,设置为接口输入数据,调用事后审核接口发起请求,审核请求通过Internet传输到审核平台。S201: The audit requester encapsulates the verification information, audit requirements and business data into JSON data, encrypts and compresses it, sets it as the interface input data, calls the post-event audit interface to initiate a request, and transmits the audit request to the audit platform through the Internet.
S202:第二审核数据接口模块捕获到审核请求,将上传数据解压解密,解析出验证信息,将验证信息与审核服务注册信息进行对比验证:验证通过,则进入步骤S203;否则,验证不通过,数据接口返回访问审核服务受限提示信息;S202: The second audit data interface module captures the audit request, decompresses and decrypts the uploaded data, parses out the verification information, and compares the verification information with the audit service registration information for verification: if the verification is passed, proceed to step S203; otherwise, if the verification fails, The data interface returns a message indicating that the access audit service is restricted;
S203:第二审核数据接口解析审核要求:如果审核要求解析成功,任务管理创建审核任务,初始化审核任务,绑定请求方信息,设置审核要求,设置任务状态为审核数据待解析,并进入步骤S204;反之数据接口将错误信息返回给请求方,线程结束并将线程返还线程池。S203: The second audit data interface parses the audit request: if the audit request is successfully parsed, the task management creates an audit task, initializes the audit task, binds the requester information, sets the audit request, sets the task status as audit data pending analysis, and proceeds to step S204 ; On the contrary, the data interface returns the error information to the requester, the thread ends and the thread is returned to the thread pool.
S204:第二审核数据接口基于业务数据结构解析业务数据:如果解析业务数据成功,第二审核数据接口将业务数据转换为业务JavaBean对象,业务JavaBean对象绑定审核任务号,保存到内存缓存,将审核任务挂载到待审核队列,更改任务状态为待审核,转入事后审核引擎进行业务审核,返回审核任务号给审核请求方(便于审核请求方查看、管理审核任务进程),线程结束并将线程返还线程池,并进入步骤S205;反之,更改任务状态为审核数据解析失败,将错误信息返回给请求方,线程结束并将线程返还线程池。S204: The second audit data interface parses the business data based on the business data structure: if the parsing of the business data is successful, the second audit data interface converts the business data into a business JavaBean object, and the business JavaBean object binds the audit task number, saves it to the memory cache, and stores the The audit task is mounted to the pending audit queue, changes the task status to pending audit, transfers it to the post-event audit engine for business audit, returns the audit task number to the audit requester (for the audit requester to view and manage the audit task process), the thread ends and the The thread returns to the thread pool and proceeds to step S205; otherwise, the task status is changed to audit data analysis failure, an error message is returned to the requester, the thread ends and the thread is returned to the thread pool.
S205:事后审核引擎的业务数据审核组件、审核结果组装组件、结果传回组件和审核任务持久化组件分别对对应队列进行处理:S205: The business data audit component, audit result assembly component, result return component and audit task persistence component of the post-event audit engine process the corresponding queues respectively:
(1)业务数据审核组件监听待审核队列是否有待审核任务,当监听到待审核队列有待审核任务时,从队头取出待审核任务,取出后从线程池取出空闲的线程执行待审核任务,第二任务管理更改审核任务状态为审核中,事后审核引擎根据审核任务的审核要求,从编译后的业务规则库提取本次审核涉及的业务规则包。基于提取的业务规则包,创建审核会话,根据任务号从内存缓存中提取业务JavaBean对象,将业务JavaBean对象加载到审核会话中,执行审核会话。审核会话结束后,审核结果绑定任务号,保存到内存缓存,更改审核任务状态为待组装,将审核任务挂载到待组装队列,线程结束并将线程返还线程池。(1) The business data audit component monitors whether there are tasks to be audited in the queue to be audited. When it monitors the queue to be audited, it takes out the tasks to be reviewed from the head of the queue, and then takes out the idle threads from the thread pool to execute the tasks to be reviewed. The second task management changes the review task status to reviewing, and the post-event review engine extracts the business rule package involved in this review from the compiled business rule library according to the review requirements of the review task. Based on the extracted business rule package, an audit session is created, the business JavaBean object is extracted from the memory cache according to the task number, the business JavaBean object is loaded into the audit session, and the audit session is executed. After the audit session ends, the audit result is bound to the task number, saved to the memory cache, the audit task status is changed to pending assembly, the audit task is mounted to the pending assembly queue, the thread ends and the thread is returned to the thread pool.
(2)审核结果组装组件监听待组装队列是否有待组装的任务,当监听到待组装队列有待组装任务,从队头取出待组装任务,取出后从线程池取出空闲的线程执行待组装任务,更改审核任务状态为组装中,根据任务号从内存缓存中提取出审核结果,按返回结果标准格式组装审核结果,组装完成后,绑定任务号,将组装结果保存到内存缓存,更改审核任务状态为待传回,将审核任务挂载到待传回队列,线程结束并将线程返还线程池。(2) Audit results The assembly component monitors whether there are tasks to be assembled in the queue to be assembled. When it monitors the queue to be assembled, it takes out the tasks to be assembled from the head of the queue, and then takes out the idle threads from the thread pool to execute the tasks to be assembled. Change The audit task status is assembling, extract the audit result from the memory cache according to the task number, and assemble the audit result according to the standard format of the returned result. After the assembly is completed, bind the task number, save the assembly result to the memory cache, and change the audit task status to To be returned, the audit task is mounted to the queue to be returned, the thread ends and the thread is returned to the thread pool.
(3)结果传回组件监听待传回队列是否有待传回任务,当监听到待传回队列有待传回任务,从队头取出待传回任务,取出后从线程池取出空闲的线程执行待传回任务,更改审核任务状态为传回中,根据任务号从内存缓存中提取组装结果,数据接口模块根据审核任务绑定的请求方地址,将组装结果加密压缩,发送给请求方,发送成功后,更改审核任务状态为待备份,将审核任务挂载到待备份队列,线程结束并将线程返还线程池。(3) The result-returning component monitors whether the queue to be returned has tasks to be sent back. When it monitors the queue to be sent back, it takes out the tasks to be sent back from the head of the queue, and then takes out the idle threads from the thread pool for execution. Return the task, change the status of the audit task to returning, and extract the assembly result from the memory cache according to the task number. The data interface module encrypts and compresses the assembly result according to the address of the requester bound to the audit task, and sends it to the requester, and the transmission is successful. After that, change the status of the audit task to be backed up, mount the audit task to the queue to be backed up, end the thread and return the thread to the thread pool.
(4)审核任务持久化组件监听待备份队列是否有待备份任务,当监听到待备份队列有待备份任务,从队头取出待备份任务,取出后从线程池取出空闲的线程执行待备份任务,更改审核任务状态为备份中,将内存缓存中和该审核任务有关的所有数据持久化,保存到数据库,保存完成后,清除内存缓存中该审核任务的所有数据,降低内存缓存压力,更改审核任务状态为审核成功,线程结束并将线程返还线程池,整个事后审核完成。(4) The audit task persistence component monitors whether there are tasks to be backed up in the queue to be backed up. When it detects that there are tasks to be backed up in the queue to be backed up, it takes out the tasks to be backed up from the head of the queue, and then takes out the idle threads from the thread pool to execute the tasks to be backed up. Change The audit task status is in backup. All data related to the audit task in the memory cache is persisted and saved to the database. After the saving is completed, all data of the audit task in the memory cache is cleared, the pressure on the memory cache is reduced, and the audit task status is changed. For the audit to succeed, the thread ends and the thread is returned to the thread pool, and the entire post-mortem audit is completed.
医疗保险报销审核,比如病人一次住院产生的所有费用报销审核,首先审核数据量大,允许秒级审核时间,对实时性要求不高,可以采用事后审核方式执行审核。业务办理审核,比如在柜台办理业务申请时,首先需要审核业务申请者是否具有办理该业务的资格,然后才能进入业务办理流程,这种实时性高、响应速度快、数据量小的审核应用场景,可以采用事中审核方式执行审核。Medical insurance reimbursement review, such as the review of reimbursement of all expenses incurred by a patient in one hospitalization, requires a large amount of data to be reviewed first, allowing second-level review time, and does not require high real-time performance. Business processing review. For example, when processing a business application at the counter, it is first necessary to check whether the business applicant is qualified to handle the business, and then enter the business processing process. This kind of review application scenario with high real-time performance, fast response speed and small amount of data , the audit can be performed in the way of in-event audit.
Claims (9)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710078245.XA CN106875156B (en) | 2017-02-14 | 2017-02-14 | A generalized intelligent audit platform and audit method thereof |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710078245.XA CN106875156B (en) | 2017-02-14 | 2017-02-14 | A generalized intelligent audit platform and audit method thereof |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106875156A CN106875156A (en) | 2017-06-20 |
CN106875156B true CN106875156B (en) | 2020-09-08 |
Family
ID=59167534
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710078245.XA Active CN106875156B (en) | 2017-02-14 | 2017-02-14 | A generalized intelligent audit platform and audit method thereof |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN106875156B (en) |
Families Citing this family (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107527185B (en) * | 2017-08-04 | 2020-11-20 | 昆明理工大学 | A Parallel Implementation Method for Compiling and Reviewing Construction Project Cost Documents |
CN107644323B (en) * | 2017-09-30 | 2020-09-15 | 成都莲合软件科技有限公司 | Intelligent auditing system for business flow |
CN107944999A (en) * | 2017-11-09 | 2018-04-20 | 用友网络科技股份有限公司 | A kind of automatic execution method and device of audit expenses project |
CN107895286B (en) * | 2017-11-13 | 2021-11-26 | 天津幸福生命科技有限公司 | Claim amount determining method and device, storage medium and electronic equipment |
CN108022080A (en) * | 2017-11-24 | 2018-05-11 | 深圳市买买提乐购金融服务有限公司 | One kind complaint processing method and relevant device |
CN108648810B (en) * | 2018-05-11 | 2024-04-02 | 平安医疗健康管理股份有限公司 | Data processing method and device for medical audit and computer readable storage medium |
CN108805521A (en) * | 2018-05-21 | 2018-11-13 | 中国平安人寿保险股份有限公司 | Survey tasks processing method, device, computer equipment and storage medium |
CN109375907B (en) * | 2018-10-29 | 2022-06-07 | 恒生电子股份有限公司 | Audit flow development method, service audit method, device, equipment and medium |
CN109767320A (en) * | 2018-12-17 | 2019-05-17 | 深圳壹账通智能科技有限公司 | Order review method, apparatus, computer equipment and storage medium |
CN110221833A (en) * | 2019-06-05 | 2019-09-10 | 浙江魔豆科技有限公司 | A kind of wisdom enterprise platform based on no code development |
CN110765102B (en) * | 2019-09-25 | 2022-11-08 | 苏宁云计算有限公司 | Service data processing method and device, computer equipment and storage medium |
CN110888646B (en) * | 2019-11-28 | 2021-11-12 | 京东数字科技控股有限公司 | Deployment method, device, system and storage medium |
CN111935090B (en) * | 2020-07-07 | 2021-04-06 | 上海微亿智造科技有限公司 | Big data transmission and persistence method and system for industrial intelligent Internet of things |
CN112596865B (en) * | 2020-12-22 | 2024-08-16 | 航天信息股份有限公司企业服务分公司 | System for pushing message to be handled based on workflow transaction |
CN113077241B (en) * | 2021-04-21 | 2024-06-18 | 北京沃东天骏信息技术有限公司 | Approval processing method, device, equipment and storage medium |
CN113468205B (en) * | 2021-06-29 | 2023-09-12 | 杭州每刻科技有限公司 | Custom expense checking method and system |
CN113487294B (en) * | 2021-07-23 | 2023-06-09 | 重庆富民银行股份有限公司 | On-line business noninductive verification method based on list mechanism |
CN113312504A (en) * | 2021-07-30 | 2021-08-27 | 北京远鉴信息技术有限公司 | Management method, device, equipment and medium for content audit project |
CN113807955B (en) * | 2021-09-29 | 2025-02-07 | 腾讯科技(深圳)有限公司 | Information auditing methods and related equipment |
CN114077714B (en) * | 2022-01-07 | 2022-04-22 | 湖南湘生网络信息有限公司 | A universal content audit configuration method and system |
CN114090305B (en) * | 2022-01-19 | 2022-04-26 | 飞狐信息技术(天津)有限公司 | Business auditing method and device |
CN115293750A (en) * | 2022-10-08 | 2022-11-04 | 珠海金智维信息科技有限公司 | AI (AI) middle desk-based intelligent auditing system, method and device |
CN119090461B (en) * | 2024-11-07 | 2025-05-16 | 九一金融信息服务(北京)有限公司 | Financial business auditing and processing method based on large model |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103455325A (en) * | 2013-07-24 | 2013-12-18 | 北京起步科技有限公司 | Business-model-based architecture platform |
CN104217276A (en) * | 2013-06-05 | 2014-12-17 | 上海宝信软件股份有限公司 | Rule-based automatic auditing method and system |
CN105630617A (en) * | 2015-12-28 | 2016-06-01 | 山东中创软件工程股份有限公司 | Business processing method and system based on rule engine |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8666851B2 (en) * | 2011-06-06 | 2014-03-04 | Bizequity Llc | Engine, system and method of providing cloud-based business valuation and associated services |
-
2017
- 2017-02-14 CN CN201710078245.XA patent/CN106875156B/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104217276A (en) * | 2013-06-05 | 2014-12-17 | 上海宝信软件股份有限公司 | Rule-based automatic auditing method and system |
CN103455325A (en) * | 2013-07-24 | 2013-12-18 | 北京起步科技有限公司 | Business-model-based architecture platform |
CN105630617A (en) * | 2015-12-28 | 2016-06-01 | 山东中创软件工程股份有限公司 | Business processing method and system based on rule engine |
Non-Patent Citations (1)
Title |
---|
基于规则的医保智能审核系统的研究;俞丽颖;《万方数据知识服务平台学术论文数据库》;20161103;第1-91页 * |
Also Published As
Publication number | Publication date |
---|---|
CN106875156A (en) | 2017-06-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106875156B (en) | A generalized intelligent audit platform and audit method thereof | |
US7313575B2 (en) | Data services handler | |
CN109101652B (en) | Label creating and managing system | |
US8060863B2 (en) | Conformance control module | |
US20050243604A1 (en) | Migrating integration processes among data integration platforms | |
CN106569801A (en) | Complex parameter-based configuration display control system | |
US20040230667A1 (en) | Loosely coupled intellectual capital processing engine | |
CN108920659A (en) | Data processing system and its data processing method, computer readable storage medium | |
CN110377595A (en) | A kind of vehicle data management system | |
CN114638160B (en) | Knowledge service method for complex equipment digital twin model | |
WO2006026659A2 (en) | Services oriented architecture for data integration services | |
US7428756B2 (en) | Access control over dynamic intellectual capital content | |
US20160321036A1 (en) | Dynamically monitoring code execution activity to identify and manage inactive code | |
CN107103064A (en) | Data statistical approach and device | |
US20210365457A1 (en) | Graph database and methods with improved functionality | |
CN112130894B (en) | Gray scale release management system, method and equipment applying characteristic switch | |
US20190073600A1 (en) | Skipping maintenance mode of applications | |
US20040230982A1 (en) | Assembly of business process using intellectual capital processing | |
CN117251253A (en) | Cloud management platform design method based on multi-source heterogeneous | |
CN117056569A (en) | SQL blood margin influence analysis method and system | |
EP1815349A2 (en) | Methods and systems for semantic identification in data systems | |
CN114675812B (en) | A data table processing method, device, computer equipment and storage medium | |
CN114281494A (en) | Data life cycle management method, system, terminal device and storage medium | |
CN114936130A (en) | A data flow rule engine | |
US20040230691A1 (en) | Evolutionary development of intellectual capital in an intellectual capital management system |
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 |