WO2019134232A1 - 核保校验的方法、装置、存储介质及终端 - Google Patents

核保校验的方法、装置、存储介质及终端 Download PDF

Info

Publication number
WO2019134232A1
WO2019134232A1 PCT/CN2018/077309 CN2018077309W WO2019134232A1 WO 2019134232 A1 WO2019134232 A1 WO 2019134232A1 CN 2018077309 W CN2018077309 W CN 2018077309W WO 2019134232 A1 WO2019134232 A1 WO 2019134232A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration table
verification
rule
insurance
code
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.)
Ceased
Application number
PCT/CN2018/077309
Other languages
English (en)
French (fr)
Inventor
付舒婷
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2019134232A1 publication Critical patent/WO2019134232A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • the present application belongs to the field of communications technologies, and in particular, to a method, an apparatus, a storage medium, and a terminal for core verification.
  • the sales process of insurance products involves many underwriting rules, such as insurance coverage, number of copies, age, and occupational information. It is usually necessary to check the five basic information of the customer and the selected protection information before the calculation of the premium or the execution of the underwriting, to confirm whether the purchase requirements are met.
  • the underwriting rules in an insurance product the prior art adopts the method of hard code support. In the process of writing the verification program, which product or which type of insurance is fixed to be written, what kind of underwriting rules are verified, there is no law. Sex, and the code is difficult to understand. When the business needs to add new underwriting rules, it can only be listed on the basis of the existing procedures of the insurance products, and the code coupling degree is high, which is not conducive to the management and development of the underwriting rules.
  • the embodiment of the present invention provides a method, a device, a storage medium, and a terminal for verifying the verification of the insurance product, so as to solve the problem that the verification procedure of the insurance product prepared by the prior art has no regularity, difficulty in understanding, and difficulty in management.
  • An embodiment of the present application provides a method for verifying a checksum, where the method includes:
  • the insurance product code and the underwriting rules are classified into the configuration table according to the service configuration instruction;
  • the constructing the configuration table in the database based on the category of the underwriting rules includes:
  • fine class configuration table Forming a fine class configuration table in the database based on the large class configuration table, where the fine class configuration table is used to record a rule code of the underwriting rule, a rule content, a check class name, and a correspondence relationship with a large class code;
  • the insurance configuration table is constructed in the database based on the fine class configuration table, and the insurance configuration table is used to record the insurance code and the rule code and rule carry-in value of the underwriting rules related thereto.
  • the storing, according to the service configuration instruction, the insurance product classification and the underwriting rules into the configuration table includes:
  • the insurance code and the rule code are associated and added to the insurance configuration table.
  • the preset reflection mechanism is a java reflection mechanism.
  • the checking according to the check-in rule to be verified and the check-class name thereof, calling the verification method by using a preset reflection mechanism, and performing the verification method to complete verification of the customer information includes:
  • the verification method is performed to complete verification of the customer information.
  • the embodiment of the present application further provides a device for verifying the verification, the device comprising:
  • a building block for constructing a configuration table in a database based on categories of underwriting rules
  • a classification module configured to store, according to the service configuration instruction, the insurance product classification code and the underwriting protection rule into the configuration table
  • a first obtaining module configured to acquire a insurance type code of the insured insurance product when performing verification verification on the customer information
  • a second acquiring module configured to obtain, from the configuration table, a check-in rule to be verified and a check-class name thereof according to the service type code
  • the verification module is configured to invoke the verification method by using a preset reflection mechanism based on the underwriting rule to be verified and the check class name thereof, and execute the verification method to complete verification of the customer information.
  • the building module includes:
  • a first building unit configured to build a large class configuration table in a database according to a category of the underwriting rules, where the large class configuration table is used to record a correspondence between a rule class and a large class code;
  • a second building unit configured to build a fine class configuration table in the database based on the large class configuration table, where the fine class configuration table is used to record rule code, rule content, check class name, and class of the underwriting rule Correspondence between codes;
  • a third building unit configured to build a insurance configuration table in the database based on the fine-class configuration table, where the insurance configuration table is used to record the insurance code and the rule encoding and rule-input value of the underwriting rules related thereto.
  • classification module includes:
  • a first obtaining unit configured to acquire a insurance code of the insurance product to be added based on the input operation on the management interface
  • a second obtaining unit configured to acquire, according to a selection operation on the management interface, a rule code of the underwriting rule corresponding to the insurance product to be added from the large class configuration table and the fine class configuration table;
  • an association unit configured to associate the insurance code and the rule code, and add to the insurance configuration table.
  • the embodiment of the present application further provides a computer readable storage medium having stored thereon computer readable instructions, which are executed by a processor to implement the following steps:
  • the insurance product code and the underwriting rules are classified into the configuration table according to the service configuration instruction;
  • the embodiment of the present application further provides a terminal, where the terminal includes a memory, a processor, and computer readable instructions stored on the memory and executable on the processor, when the processor executes the computer readable instructions.
  • the insurance product code and the underwriting rules are classified into the configuration table according to the service configuration instruction;
  • the embodiment of the present application constructs a configuration table in a database based on the category of the underwriting rules, and then stores the insurance product insurance code and the underwriting insurance classification into the configuration table according to the service configuration instruction, and implements
  • the classification and storage of the underwriting rules is beneficial to the management of the program code of the underwriting rules; when the customer information is under-checked, the insurance code of the insurance products insured is obtained, and the configuration is based on the insurance code.
  • the check rule and the checksum class name are obtained in the table, and then the check method is invoked by using a preset reflection mechanism, and the check method is executed to complete verification of the customer information, thereby implementing a configuration table based
  • the verification method of the underwriting rules the verification program is easy to read and understand, effectively reduces the coupling degree of the code, and facilitates the management and development of the underwriting rules by the business personnel.
  • FIG. 1 is a first implementation flowchart of a method for verification verification provided by an embodiment of the present application
  • FIG. 2 is a second implementation flowchart of a method for verification verification provided by an embodiment of the present application
  • FIG. 3 is a third implementation flowchart of a method for verification verification provided by an embodiment of the present application.
  • FIG. 4 is a fourth implementation flowchart of a method for verification verification provided by an embodiment of the present application.
  • FIG. 5 is a structural diagram of a device for verifying verification provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a terminal provided by an embodiment of the present application.
  • FIG. 1 shows a first implementation flow of a method for verification verification provided by an embodiment of the present application.
  • the method for verifying the checksum provided by the embodiment of the present application is applied to a background server.
  • the method includes:
  • step S101 a configuration table is built in the database based on the category of the underwriting rules.
  • the verification targets of the underwriting rules include, but are not limited to, the amount of insurance, premiums, shares, payment methods, occupations, ages, etc.; for the amount of insurance, for example, most insurance types of life insurance have rules that cannot be lower than the amount of insurance.
  • the number of requirements for the requirement or the insured amount is a multiple.
  • the embodiment of the present application classifies the underwriting rules based on different check objects, and then constructs a configuration table corresponding to different categories in the database according to the categories of the underwriting rules.
  • Each of the underwriting rules categories corresponds to at least one configuration table to classify and store the underwriting rules by using the configuration table.
  • step S102 the insurance product code and the underwriting rules are classified into the configuration table according to the service configuration instruction.
  • the configuration table is used to record the insurance product code of the insurance product and the underwriting policy involved in the insurance product.
  • an insurance product corresponds to a insurance code, which is identification information of the insurance product, and is used to distinguish different insurance products.
  • the underwriting rules of the insurance products are classified and stored.
  • the underwriting developer can enter the underwriting rules in a coded manner on the background server, or the front-end business personnel can enter the underwriting rules in a selective manner on the front-end device.
  • the business personnel complete the category division in the early stage, and then hand it to the developer code entry.
  • the background server obtains the underwriting rules of the insurance products based on the code information, and stores them in the corresponding configuration table.
  • the business personnel can input the service configuration instructions on the front-end device through the operation management interface, and the background server obtains the underwriting rules of the insurance products based on the service configuration instructions, and stores them in the corresponding configuration.
  • the management interface loads the display content according to the content recorded in the configuration table.
  • the hard code support is adopted.
  • the embodiment of the present application adds a configuration table, and classifies and manages different underwriting rules based on the configuration table, so that developers and business personnel browse the underwriting rules more intuitively, which is beneficial to the core.
  • the program code of the insurance rules is managed; and the underwriting rules are entered from the perspective of the business personnel through the configuration table, which facilitates the management and development of the underwriting rules by the business personnel.
  • step S103 when the customer information is under-checked, the insurance type code of the insured insurance product is acquired.
  • the embodiment of the present application obtains the insurance code according to the insurance product insured by the customer.
  • the customer information may be obtained according to the input operation of the business person.
  • the customer information may also be retrieved from the database according to the selection instruction input by the business personnel on the management page.
  • step S104 the underwriting rule to be verified and its check class name are obtained from the configuration table according to the insurance code.
  • the verification parameter and the verification class name of each underwriting rule are also recorded in the configuration table.
  • the checksum class name refers to the name of the rule check class, such as the name of the class class in java.
  • step S105 based on the under-checking rule to be verified and its check-class name, the verification method is invoked by a preset reflection mechanism, and the verification method is executed to complete verification of the customer information.
  • the reflection mechanism means that in the running state of the program, for any class, all the properties and methods of the class can be known; for any object, any method and property of the object can be called, and the dynamic information and dynamics are obtained.
  • the function of the method that called the object Compared with the non-reflective method, to obtain the information of the object, the existing non-reflective way is to create an object through a class, the process includes introducing the name of the "package.class", then performing the new instantiation operation, and finally instantiating the object. Object; and reflection is to find the information of the class through an object, the above process becomes the first instantiated object, execute the getClass() method, and finally get the name of the complete "package.class".
  • the embodiment of the present application acquires a program instruction segment corresponding to the verification class name by using a preset reflection mechanism, instantiates an object, and then calls a verification method, and runs the verification method to complete the information about the client. check.
  • the embodiment of the present application implements the verification of the underwriting rules by means of reflection, reduces the coupling degree of the underwriting verification code, and the code is easy to understand and easy to read, and the logic is more concise and clear.
  • the embodiment of the present application constructs a configuration table in a database based on the category of the underwriting rules, and then stores the insurance product insurance code and the underwriting rules into the configuration table, thereby realizing the classification of the underwriting rules.
  • Storage is beneficial for managing the verification code of the underwriting rules; when the customer information is under-checked, the insured insurance products, the rules to be verified and their schools are obtained from the configuration table by the insurance code.
  • the configuration table includes, but is not limited to, a large class configuration table, a fine class configuration table, and a insurance configuration table.
  • the step S101 constructing the configuration table in the database based on the category of the underwriting rules includes:
  • step S1011 a large class configuration table is built in the database based on the category of the underwriting rules.
  • the large class configuration table is used to record the correspondence between the rule class and the big class code.
  • the rules are classified into upper classes classified according to rule check objects; as described above, the check objects include, but are not limited to, insured amount, premium, number of copies, payment method, occupation, age, and accordingly,
  • the general categories of rules include, but are not limited to, insurance, premiums, shares, payment methods, occupations, and age.
  • Each check object is a large class of rules, corresponding to a large class code.
  • the large class code is identification information of a rule class or a check object.
  • Table 1 shows a schematic diagram of a large class configuration table provided by an embodiment of the present application.
  • the large-category configuration table shown in Table 1 is only an example of the present application, and is not used to limit the present application.
  • the large-category configuration table may further include more rule categories and categories. Encoding, large class encoding is not limited to the example in Table 1.
  • step S1012 a fine class configuration table is built in the database based on the large class configuration table.
  • each of the rule categories can be divided into a variety of refinement rules.
  • the embodiment of the present application further creates a fine class configuration table in the database, where the fine class configuration table is used to record rule code, rule content, and check class name of the underwriting rule. And the large class code of the general category of the rule. It can be seen that the large class configuration table and the fine class configuration table are relative.
  • a general rule class can correspond to one or more fine class configuration tables.
  • the rule of the underwriting rule is encoded as the identification information of the underwriting rule; the content of the rule is a definition of the underwriting rule, such as a multiple of the amount of the insurance; the verification class is a verification class of the underwriting rule.
  • the name is a code that specifies a verification class of the underwriting rule.
  • Table 2 shows a detailed configuration table provided by the embodiment of the present application.
  • the table 2 is a detailed configuration table of the insured amount, and includes two refinement rules: a multiplier and a minimum insured amount.
  • the detailed configuration table shown in Table 2 is only an example of the present application, and is not used to limit the present application.
  • the detailed configuration table may further include more detailed rules, the foregoing Rule coding, rule content is not limited to the example of Table 2.
  • step S1013 a insurance configuration table is built in the database based on the fine class configuration table.
  • the insurance configuration table is used to record the insurance code and the rule coding and rule carry-in value of the underwriting rules related thereto.
  • an insurance product usually includes a plurality of different types of underwriting rules; the rules carry values are specific parameter values in the underwriting rules.
  • Table 2 it is assumed that there is insurance product A and insurance product B, and the same applies to the underwriting code of R0101 under the large class code R01.
  • the insurance product A has a rule entry value of 10000, that is, insurance product A.
  • the insurance multiple is required to be a multiple of 10,000; the insurance product B has a rule entry value of 100, that is, the insurance product B has a multiple of 100.
  • Table 3 shows the insurance configuration table provided by the embodiment of the present application.
  • the table 3 includes two types of insurance products, the insurance products coded as P0121 and the insurance products coded as P0122.
  • P0121 involves refining the rule's insured multiple, and the rule brings in a value of 500
  • P0122 involves the refinement rule minimum insured amount, and the rule brings in a value of 10,000.
  • Serial number Insurance code Rule coding Rules bring in values Prompt message 1 P0121 R0101 500 The amount of insurance must be a multiple of 500 2 P0122 R0102 10000 The minimum insured amount is 10000
  • the service configuration table shown in Table 3 is only an example of the present application, and is not used to limit the present application.
  • the insurance configuration table may further include more insurance codes and related underwriting rules.
  • the rule code is not limited to the example in Table 3.
  • the above-mentioned insurance configuration table is used to query the underwriting rules included in each insurance product and the specific requirements of the parameters in the underwriting rules when performing the underwriting verification.
  • the step S104 obtains, from the configuration table, the underwriting rule to be verified according to the service code and the check class name thereof, including: obtaining a rule code from the insurance configuration table according to the insurance code, and obtaining insurance
  • the underwriting rules included in the product; the check class name is obtained from the fine class configuration table for each rule code. Therefore, the underwriting rules are extracted from the verification program, and it is not necessary to fix which product or which type of underwriting verification is performed during the verification process.
  • the embodiment of the present application divides the configuration table by the foregoing manner, including a large-category configuration table, a fine-class configuration table, and a insurance configuration table, and implements classification and storage of the underwriting rules, and regulates management of the underwriting rules;
  • the configuration table, the detailed configuration table, and the insurance configuration table are interlocked.
  • the background server can query the specific parameter information of the underwriting rules by reading the configuration table, and obtain the underwriting rules without the need to verify the program. Which type of product or which type of insurance is used to check which underwriting rules are verified, which solves the problem that the existing hard support coding method leads to difficult rule management.
  • the business personnel can input the service configuration instruction through the operation management interface on the front-end device, and the background server obtains the underwriting rules of the insurance product based on the service configuration instruction, and The classification is stored in the corresponding configuration table. Further, based on the second implementation flow of the method for verification verification provided in FIG. 2, a third implementation flow of the method for verification verification provided by the embodiment of the present application is proposed.
  • FIG. 3 it is a schematic diagram of a third implementation process of the method for verification verification provided by the embodiment of the present application.
  • the step S102 according to the service configuration instruction, storing the underwriting rules of the insurance product into the configuration table includes:
  • step S1021 based on the entry operation on the management interface, the insurance type code of the insurance product to be added is obtained.
  • the entry function of the insurance product is provided on the management page.
  • the business person can classify the underwriting rules of the insurance product into the configuration table by triggering the entry function.
  • the management page may pop up an input box according to a trigger operation of the user to prompt for inputting the insurance code of the insurance product to be added.
  • step S1022 based on the selection operation on the management interface, the rule code of the underwriting policy corresponding to the insurance product to be added is obtained from the large class configuration table and the fine class configuration table.
  • the list of the underwriting rules includes the underwriting rules corresponding to the categories selected by the business personnel from the list of rule categories.
  • a rule large list is output based on the large category selection table, and the rule large class list may be as shown in Table 5.
  • the list of the underwriting rules is output based on the detailed configuration table. Assume that the detailed configuration table is as shown in Table 2, that is, the insurance coverage category includes the insurance multiple and the minimum insurance amount, and the output underwriting rules list may be as shown in Table 6.
  • the embodiment of the present application may further mark the underwriting rules selected by the service personnel from the list of the underwriting rules to record the underwriting rules selected by the service personnel, so as to facilitate the service personnel from the list of the underwriting rules.
  • the underwriting rules of the insurance products to be added are configured in batches.
  • step S1023 the insurance code and the rule code are associated and added to the insurance configuration table.
  • a new row is created in the insurance configuration table according to the number of rule codes, and the rule codes are respectively filled into each row, and the insurance code and rule band of each row are filled. Enter the value to complete the entry operation of the underwriting rules for the insurance product.
  • the embodiment of the present application implements the entry of the underwriting rules from the perspective of the business personnel, and solves the problem that the code caused by the addition of the underwriting rules by the prior art adopts the hard code support method is difficult to understand and has no regularity. It is convenient for business personnel to add and modify according to the business requirements underwriting rules.
  • FIG. 4 it is a schematic diagram of a fourth implementation process of the method for verification verification provided by the embodiment of the present application.
  • the preset reflection mechanism is a java reflection mechanism
  • the step S105 calls the verification method by using a preset reflection mechanism based on the underwriting rule to be verified and its verification class name.
  • Performing the verification method to complete verification of the customer information includes:
  • step S1051 an object is created according to the check class name.
  • the embodiment of the present application adopts a java reflection mechanism, and the so-called java reflection mechanism refers to obtaining information of a class according to a specified class name at runtime, and the functions provided by the method include: determining a class to which any object belongs at runtime; Constructs an object of any class; determines the member variables and methods of any class at runtime; calls any object's methods at runtime; generates a dynamic proxy. Therefore, the embodiment of the present application obtains the verification class name from the verification parameter, and then instantiates the object based on the verification class name.
  • step S1052 the rule content and the rule carry value are acquired.
  • the attribute information is a rule content and a rule carry value.
  • the embodiment of the present application obtains the rule code and the rule carry value from the insurance configuration table according to the insurance code, and then obtains the rule content from the fine class configuration table according to the rule code.
  • the manner in which the rule content and the rule are brought into the value includes: but is not limited to: obtaining a named public field by Field getField (String name); obtaining all common fields of the class by Field[] getFields(); getDeclaredField(String name) Gets the named field of the class declaration; gets all the fields of the class declaration via Field[]getDeclaredFields().
  • step S1053 the verification method is invoked by the created object according to the rule content and the rule-input value.
  • the method of calling the verification method includes, but is not limited to, obtaining a named public method by using a specific parameter type by Method getMethod(String name, Class[]params); obtaining all the classes by Method[]getMethods() Public method; obtains the method of naming the class declaration by using Method closeDeclaredMethod(String name, Class[]params) using the close-up parameter type; obtaining all methods of the class declaration by Method[]getDeclaredMethods().
  • step S1054 the verification method is executed to complete verification of the customer information.
  • the verification method is performed.
  • the validation class is named ruleclass, you can pass:
  • the verification method verifies the customer information according to the attribute information of the ruleclass class. For example, if the rule content is a multiple of the policy, and the rule carries a value of 500, it is checked whether the amount of the insurance in the customer information is It is a multiple of 500.
  • the embodiment of the present application adopts a reflection mechanism and a configuration table to implement verification of the underwriting rules, and achieves the effect of separating the program code from the configuration file during the program development process, and the verification program is easy to read and understand, and the rule code is
  • the low coupling degree facilitates the management and development of the underwriting rules by business personnel. When you need to switch from one verification method to another, you don't need to modify the code or recompile. You only need to modify the configuration file, that is, the configuration table, and then run it.
  • the size of the serial number of each step does not mean the order of execution order, and the order of execution of each step should be determined by its function and internal logic, and should not constitute any implementation process of the embodiment of the present application. limited.
  • FIG. 5 is a structural diagram of a device for verifying the verification provided by the embodiment of the present application. For the convenience of description, only parts related to the embodiment of the present application are shown.
  • the device for verifying the checksum is used to implement the method for verifying the checksum described in the foregoing embodiments of FIG. 1, FIG. 2, FIG. 3, and FIG. 4, and may be software built in the server. Unit, hardware unit or unit combining software and hardware,
  • the device for verifying the checksum includes:
  • a building module 51 configured to build a configuration table in the database based on the category of the underwriting rules
  • a classification module 52 configured to store, according to the service configuration instruction, the insurance product classification and the underwriting rules into the configuration table;
  • the first obtaining module 53 is configured to acquire the insurance type code of the insured insurance product when performing the underwriting verification on the customer information;
  • the second obtaining module 54 is configured to obtain, from the configuration table, a check-in rule to be verified and a check-class name thereof according to the service type code;
  • the verification module 55 is configured to invoke a verification method by using a preset reflection mechanism based on the underwriting rule to be verified and its verification class name, and execute the verification method to complete verification of the customer information. .
  • the building module 51 includes:
  • a first building unit 511 configured to build a large class configuration table in a database according to a category of the underwriting rules, where the large class configuration table is used to record a correspondence between a rule class and a large class code;
  • a second building unit 512 configured to build a fine class configuration table in the database based on the large class configuration table, where the fine class configuration table is used to record rule encoding, rule content, check class name, and large Correspondence between class codes;
  • the third constructing unit 513 is configured to construct a insurance configuration table in the database based on the fine-class configuration table, where the insurance configuration table is used to record the insurance code and the rule encoding and rule-input value of the underwriting rules related thereto.
  • the classification module 52 includes:
  • the first obtaining unit 521 is configured to acquire a service type code of the insurance product to be added based on the input operation on the management interface;
  • the second obtaining unit 522 is configured to obtain, according to a selection operation on the management interface, a rule code of the underwriting policy corresponding to the insurance product to be added from the large class configuration table and the fine class configuration table;
  • the association unit 523 is configured to associate the service code and the rule code, and add to the service configuration table.
  • the preset reflection mechanism is a java reflection mechanism.
  • the verification module 55 includes:
  • An attribute obtaining unit 552 configured to acquire a rule content and a rule carry-in value
  • the method invoking unit 553 is configured to invoke the verification method by using the created object according to the rule content and the rule to bring in a value;
  • the method execution unit 554 is configured to execute the verification method to complete verification of the customer information.
  • each module/unit in the embodiment of the present application may be used to implement all the technical solutions in the foregoing method embodiments, and the specific working process may refer to the corresponding process in the foregoing method embodiments, and details are not described herein again. .
  • the embodiment provides a computer readable storage medium, where the computer readable storage medium is stored with a computer readable instruction, and when the computer readable instruction is executed by the processor, the method for verifying the verification in Embodiment 1 is implemented. I won't go into details here. Alternatively, when the computer readable instructions are executed by the processor, the functions of the modules/units in the apparatus for verifying the verification in the embodiment 2 are implemented. To avoid repetition, details are not described herein again.
  • FIG. 6 is a schematic diagram of a terminal according to an embodiment of the present disclosure, where the terminal includes but is not limited to a server and a mobile terminal.
  • the terminal 6 of this embodiment includes a processor 60, a memory 61, and computer readable instructions 62 stored in the memory 61 and operable on the processor 60.
  • the steps in the method embodiment of the above-mentioned core verification check when the processor 60 executes the computer readable instructions 62 such as steps S101 to S105 shown in FIG. 1, step S1011 described in the embodiment of FIG. S1013, steps S1021 to S1023 described in the embodiment of FIG. 3 and steps S1051 to S1054 described in the embodiment of FIG. 4; or, when the processor 60 executes the computer readable instructions 62, the above-mentioned nuclear protection is implemented.
  • the functions of the modules/units in the device embodiment such as the functions of modules 51 through 55 shown in FIG.
  • the computer readable instructions 62 may be partitioned into one or more modules/units that are stored in the memory 61 and executed by the processor 60, To complete this application.
  • the one or more modules/units may be an instruction segment of a series of computer readable instructions capable of performing a particular function, the instruction segments being used to describe the execution of the computer readable instructions 62 in the terminal 6.
  • the computer readable instructions 62 may be divided into a construction module, a classification module, a first acquisition module, a second acquisition module, and a verification module, and the specific functions of each module are as follows:
  • a building block for constructing a configuration table in a database based on categories of underwriting rules
  • a classification module configured to store, according to the service configuration instruction, the insurance product classification code and the underwriting protection rule into the configuration table
  • a first obtaining module configured to acquire a insurance type code of the insured insurance product when performing verification verification on the customer information
  • a second acquiring module configured to obtain, from the configuration table, a check-in rule to be verified and a check-class name thereof according to the service type code
  • the verification module is configured to invoke the verification method by using a preset reflection mechanism based on the underwriting rule to be verified and the check class name thereof, and execute the verification method to complete verification of the customer information.
  • the terminal 6 can be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server.
  • the terminal may include, but is not limited to, a processor 60, a memory 61. It will be understood by those skilled in the art that FIG. 6 is merely an example of the terminal 6, and does not constitute a limitation of the terminal 6, and may include more or less components than those illustrated, or combine some components, or different components, such as
  • the terminal may also include an input/output device, a network access device, a bus, and the like.
  • the so-called processor 60 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like, which is a control center of the terminal, and connects various parts of the entire terminal using various interfaces and lines.
  • the memory 61 can be used to store the computer readable instructions and/or modules by running or executing computer readable instructions and/or modules stored in the memory, and recalling data stored in the memory Implementing various functions of the terminal.
  • the memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored. Data created based on the use of the terminal, etc.
  • the memory may include a high-speed random access memory, and may also include non-volatile memory such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), and a secure digital card (Secure Digital, SD). , Flash Card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
  • non-volatile memory such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), and a secure digital card (Secure Digital, SD).
  • SD Secure Digital
  • Flash Card at least one disk storage device, flash memory device, or other volatile solid-state storage device.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated modules/units if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions, which may be stored in a computer readable storage medium.
  • the computer readable instructions when executed by a processor, may implement the steps of the various method embodiments described above.
  • the computer readable instructions comprise computer readable instruction code, which may be in the form of source code, an object code form, an executable file or some intermediate form or the like.
  • the computer readable storage medium may include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read only memory (ROM, Read- Only Memory), Random Access Memory (RAM), electrical carrier signals, telecommunications signals, and software distribution media. It should be noted that the content contained in the computer readable storage medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in a jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer readable The storage medium does not include an electrical carrier signal and a telecommunication signal.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本申请适用于通信技术领域，提供了一种核保校验的方法，所述方法包括：基于核保规则的类别在数据库中构建配置表；根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。本申请实现了对核保规则的分类存储，且通过配置表结合反射机制实现了校验程序与配置文件相互分离，校验程序易读易懂，有效地降低了代码的耦合度，方便了业务人员对核保规则进行管理、开发。

Description

核保校验的方法、装置、存储介质及终端
本专利申请以2018年01月08日提交的申请号为201810014124.3，名称为“核保校验的方法、装置、存储介质及终端”的中国发明专利申请为基础，并要求其优先权。
技术领域
本申请属于通信技术领域，尤其涉及一种核保校验的方法、装置、存储介质及终端。
背景技术
保险产品的销售流程涉及到很多的核保规则，比如保额、份数、年龄、职业信息等。通常需要在计算保费或者执行承保环节前，对客户的五项基本信息以及选择的保障信息进行核保校验，确认是否符合购买要求。对于一个保险产品中的核保规则，现有技术采用硬代码支持的方式，在校验程序的编写过程中，固定写死哪款产品或者哪个险种进行什么样的核保规则校验，没有规律性，且代码晦涩难懂。当业务需要添加新的核保规则时，只能在保险产品已有程序的基础上不断罗列，代码耦合度高，不利于对核保规则进行管理、开发。
发明内容
本申请实施例提供了一种核保校验的方法、装置、存储介质及终端，以解决现有技术编写的保险产品的校验程序没有规律性、晦涩难懂、管理困难的问题。
本申请实施例提供了一种核保校验的方法，所述方法包括：
基于核保规则的类别在数据库中构建配置表；
根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
进一步地，所述基于核保规则的类别在数据库中构建配置表包括：
基于核保规则的类别在数据库中构建大类配置表，所述大类配置表用于记录规则大类与大类编码之间的对应关系；
基于所述大类配置表在数据库中构建细类配置表，所述细类配置表用于记录核保规则 的规则编码、规则内容、校验类名及与大类编码之间的对应关系；
基于所述细类配置表在数据库中构建险种配置表，所述险种配置表用于记录险种编码及与其相关的核保规则的规则编码、规则带入值。
进一步地，所述根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中包括：
基于管理界面上的录入操作，获取待添加的保险产品的险种编码；
基于管理界面上的选择操作，从所述大类配置表和细类配置表中获取所述待添加的保险产品对应的核保规则的规则编码；
关联所述险种编码和所述规则编码，并添加至所述险种配置表中。
进一步地，所述预设的反射机制为java反射机制。
进一步地，所述基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验包括：
根据所述校验类名创建对象；
获取规则内容和规则带入值；
通过所创建的对象根据所述规则内容和规则带入值调用校验方法；
执行所述校验方法，以完成对所述客户信息的校验。
本申请实施例还提供了一种核保校验的装置，所述装置包括：
构建模块，用于基于核保规则的类别在数据库中构建配置表；
分类模块，用于根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
第一获取模块，用于在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
第二获取模块，用于根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
校验模块，用于基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
进一步地，所述构建模块包括：
第一构建单元，用于基于核保规则的类别在数据库中构建大类配置表，所述大类配置表用于记录规则大类与大类编码之间的对应关系；
第二构建单元，用于基于所述大类配置表在数据库中构建细类配置表，所述细类配置表用于记录核保规则的规则编码、规则内容、校验类名及与大类编码之间的对应关系；
第三构建单元，用于基于所述细类配置表在数据库中构建险种配置表，所述险种配置表用于记录险种编码及与其相关的核保规则的规则编码、规则带入值。
进一步地，所述分类模块包括：
第一获取单元，用于基于管理界面上的录入操作，获取待添加的保险产品的险种编码；
第二获取单元，用于基于管理界面上的选择操作，从所述大类配置表和细类配置表中获取所述待添加的保险产品对应的核保规则的规则编码；
关联单元，用于关联所述险种编码和所述规则编码，并添加至所述险种配置表中。
本申请实施例还提供了一种计算机可读存储介质，其上存储有计算机可读指令，该计算机可读指令由处理器执行时实现如下步骤：
基于核保规则的类别在数据库中构建配置表；
根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
本申请实施例还提供了一种终端，所述终端包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
基于核保规则的类别在数据库中构建配置表；
根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
与现有技术相比，本申请实施例基于核保规则的类别在数据库中构建配置表，然后根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中，实现了对核保规则的分类存储，有利于对核保规则的程序代码进行管理；当对客户信息进行核保校验时，获取所投保的保险产品的险种编码，根据所述险种编码从所述配置表中获取待校验规则及其校验类名，然后通过预设的反射机制调用校验方法，执行所述校验方法以完成对所述客户信息的校验，从而实现了基于配置表的核保规则校验方式，校验程序易读易懂，有效地降低了代码的耦合度，方便了业务人员对核保规则进行管理、开发。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他附图。
图1是本申请实施例提供的核保校验的方法的第一实现流程图；
图2是本申请实施例提供的核保校验的方法的第二实现流程图；
图3是本申请实施例提供的核保校验的方法的第三实现流程图；
图4是本申请实施例提供的核保校验的方法的第四实现流程图；
图5是本申请实施例提供的核保校验的装置的组成结构图；
图6是本申请实施例提供的终端的示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
图1示出了本申请实施例提供的核保校验的方法的第一实现流程。本申请实施例提供的所述核保校验的方法应用于后台服务器。参阅图1，所述方法包括：
在步骤S101中，基于核保规则的类别在数据库中构建配置表。
目前，核保规则的校验对象包括但不限于保额、保费、份数、缴费方式、职业、年龄等；以保额为例，寿险的大部分险种都有保额不能低于多少的规则要求或者保额是多少倍数的规则要求。本申请实施例基于不同的校验对象对核保规则划分类别，然后根据核保规则的类别，在数据库中构建不同类别对应的配置表。其中，每种核保规则类别对应至少一个配置表，以通过所述配置表来对核保规则进行分类、存储。
在步骤S102中，根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中。
可选地，在本申请实施例中，所述配置表用于记录保险产品的险种编码、保险产品涉及的核保规则。在这里，一个保险产品对应一个险种编码，为所述保险产品的标识信息，用于区分不同的保险产品。
在数据库构建配置表之后，要对保险产品的核保规则进行分类存储。在这里，可以通过后台开发人员在后台服务器上以编码的方式录入核保规则，也可以通过前端业务人员在前端设备上以选择的方式录入核保规则。对于已有核保规则，前期由业务人员完成类别划分，然后交给开发人员编码录入，后台服务器基于代码信息获取保险产品的核保规则，并分类存储至对应的配置表中。对于业务需求新增的核保规则，可以由业务人员在前端设备上通过操作管理界面输入业务配置指令，后台服务器基于所述业务配置指令获取保险产品的核保规则，并分类存储至对应的配置表中。其中，所述管理界面根据所述配置表记录的内容加载显示内容。
相对于现有技术采用硬代码支持的方式，本申请实施例增加配置表，基于该配置表来分类管理不同的核保规则，使得开发人员和业务人员浏览核保规则更加直观，有利于对核保规则的程序代码进行管理；且通过配置表实现了从业务人员的角度录入核保规则，方便了业务人员对核保规则进行管理、开发。
在步骤S103中，在对客户信息进行核保校验时，获取所投保的保险产品的险种编码。
在对客户信息进行核保校验时，本申请实施例根据客户所投保的保险产品获取险种编码。可选地，对于新客户，可以根据业务人员的录入操作获取所述客户信息，对于老顾客，还可以根据业务人员在管理页面上输入的选择指令从数据库中调出所述客户信息。
在步骤S104中，根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名。
在本申请实施例中，所述配置表中还记录了每一条核保规则的校验参数及校验类名。其中所述校验类名是指规则校验类的名称，比如java中class类的名称。在获取到险种编码之后，基于所述险种编码查询数据库中的配置表，得到所述险种编码对应的保险产品所包括的核保规则、每一条核保规则的校验类名。可选地，查询的方式可以采用结构化查询语言SQL完成，SQL语言简洁高效，有利于提高配置表查询的效率。
在步骤S105中，基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
所述反射机制是指在程序运行状态中，对于任意一个类，都能够知道这个类的所有属性和方法；对于任意一个对象，都能够调用对象的任意方法和属性，这种动态获取信息以及动态调用对象的方法的功能。与非反射的方式相比，要获取对象的信息，现有的非反射的方式是通过一个类创建对象，过程包括引入“包.类”的名称，然后执行new实例化操作，最后取得实例化对象；而反射是通过一个对象找到类的信息，上述过程变成先实例化对象，执行getClass()方法，最后得到完整“包.类”的名称。在这里，本申请实施例通过预设的反射机 制获取所述校验类名对应的程序指令段，实例化对象，然后调用校验方法，运行所述校验方法，完成对所述客户信息的校验。本申请实施例通过反射的方式来实现对核保规则的校验，降低了核保校验代码的耦合度，代码易懂易读，实现逻辑上更加简洁明了。
综上所述，本申请实施例基于核保规则的类别在数据库中构建配置表，然后将保险产品的险种编码及核保规则分类存储至所述配置表中，实现了对核保规则的分类存储，有利于对核保规则的校验代码进行管理；当对客户信息进行核保校验时，则通过险种编码从所述配置表中获取所投保的保险产品、待校验规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法以完成对所述客户信息的校验，从而实现了基于配置表的核保规则校验方式，校验程序易读易懂，有效地降低了代码的耦合度；且配置表与反射机制相结合的方式，极大地方便了业务人员根据需求增添核保规则，有效地规范了核保规则的配置方式。
进一步地，基于图1提供的核保校验的方法的第一实现流程的基础上，提出本申请实施例提供的核保校验的方法的第二实现流程。
如图2所示，是本申请实施例提供的核保校验的方法的第二实现流程示意图。在本申请实施例中，所述配置表包括但不限于大类配置表、细类配置表以及险种配置表。所述步骤S101基于核保规则的类别在数据库中构建配置表包括：
在步骤S1011中，基于核保规则的类别在数据库中构建大类配置表。
其中，所述大类配置表用于记录规则大类与大类编码之间的对应关系。所述规则大类为根据规则的校验对象划分的上位类别；如前所述，所述校验对象包括但不限于保额、保费、份数、缴费方式、职业、年龄，相应地，所述规则大类包括但不限于保险、保费、份数、缴费方式、职业、年龄。每一个校验对象作为一种规则大类，对应一个大类编码。所述大类编码为规则大类或者校验对象的标识信息。示例性地，表1示出了本申请实施例提供的大类配置表示意图。
序号 大类编码 规则大类
1 R01 保额
2 R02 保费
表1
应当理解，表1所示的大类配置表仅为本申请的一个示例，并不用于限制本申请，在其他实施例中，大类配置表中还可以包括更多的规则大类及大类编码，大类编码并不限制于表1的示例。
在步骤S1012中，基于所述大类配置表在数据库中构建细类配置表。
以保额为例，寿险的大部分险种都有保额不能低于多少的规则要求或者保额是多少倍数 的规则要求。因此，每一种规则大类下面可以划分出多种细化规则。在这里，基于所述大类配置表，本申请实施例在所述数据库中进一步创建细类配置表，所述细类配置表用于记录核保规则的规则编码、规则内容、校验类名及所属的规则大类的大类编码。可见，所述大类配置表和细类配置表是相对的。一种规则大类可以对应一个或多个细类配置表。所述核保规则的规则编码为该核保规则的标识信息；所述规则内容为核保规则的定义，比如保额是多少的倍数；所述校验类名为核保规则的校验类的名称。
示例性地，表2示出了本申请实施例提供的细类配置表，该表2为保额的细类配置表，包括两条细化规则：保额倍数及最低保额。
Figure PCTCN2018077309-appb-000001
表2
应当理解，表2所示的细类配置表仅为本申请的一个示例，并不用于限制本申请，在其他实施例中，细类配置表中还可以包括更多的细化规则，上述的规则编码、规则内容并不限制于表2的示例。
在步骤S1013中，基于所述细类配置表在数据库中构建险种配置表。
在本申请实施例中，所述险种配置表用于记录险种编码及与其相关的核保规则的规则编码、规则带入值。其中，一个保险产品通常包括多种不同类别的核保规则；所述规则带入值为核保规则中的具体参数值。以表2为例，假设存在保险产品A和保险产品B，同样涉及大类编码R01下的规则编码为R0101的核保规则，然而保险产品A的规则带入值要求为10000，即保险产品A的保额倍数要求是10000的倍数；保险产品B的规则带入值要求为100，即保险产品B的保额倍数要求是100的倍数。
示例性地，表3示出了本申请实施例提供的险种配置表。该表3中包括两种保险产品，险种编码为P0121的保险产品和险种编码为P0122的保险产品。其中，P0121涉及细化规则保额倍数，规则带入值为500；P0122涉及细化规则最低保额，规则带入值为10000。
序号 险种编码 规则编码 规则带入值 提示信息
1 P0121 R0101 500 保额必须500的倍数
2 P0122 R0102 10000 最低保额为10000
表3
应当理解，表3所示的险种配置表仅为本申请的一个示例，并不用于限制本申请，在其 他实施例中，险种配置表中还可以包括更多险种编码及与其相关的核保规则的规则编码，并不限制于表3的示例。
在本申请实施例中，上述险种配置表用于在进行核保校验时查询出每一种保险产品所包括的核保规则，以及所述核保规则中参数的具体要求。具体地，所述步骤S104根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名包括：根据所述险种编码从险种配置表中获取规则编码，得到保险产品所包括的核保规则；针对每一个规则编码从所述细类配置表中获取校验类名。从而将核保规则从校验程序中抽离出来，无需在校验程序的编写过程中固定写死哪款产品或者哪个险种进行什么样的核保规则校验。
本申请实施例通过上述方式对配置表的划分，包括大类配置表、细类配置表以及险种配置表，实现了对核保规则的分类存储，规范了对核保规则的管理；上述大类配置表、细类配置表以及险种配置表之间环环相扣，后台服务器通过读取配置表即可查询核保规则的具体参数信息，得到核保规则，而无需在校验程序的编写过程中固定写死哪款产品或者哪个险种进行什么样的核保规则校验，解决了现有硬支持的编码方式导致规则管理困难的问题。
如前所述，对于新增的核保规则的分类存储，可以由业务人员在前端设备上通过操作管理界面输入业务配置指令，后台服务器基于所述业务配置指令获取保险产品的核保规则，并分类存储至对应的配置表中。进一步地，基于图2提供的核保校验的方法的第二实现流程的基础上，提出本申请实施例提供的核保校验的方法的第三实现流程。
如图3所示，是本申请实施例提供的核保校验的方法的第三实现流程示意图。在本申请实施例中，所述步骤S102根据业务配置指令将保险产品的核保规则分类存储至所述配置表中包括：
在步骤S1021中，基于管理界面上的录入操作，获取待添加的保险产品的险种编码。
在本申请实施例中，所述管理页面上提供了保险产品的录入功能。业务人员可以通过触发所述录入功能来将保险产品的核保规则分类存储至所述配置表中。示例性地，所述管理页面可以根据用户的触发操作，弹出输入框以提示用于输入待添加的保险产品的险种编码。
在步骤S1022中，基于管理界面上的选择操作，从所述大类配置表和细类配置表中获取所述待添加的保险产品对应的核保规则的规则编码。
在获取到险种编码后，基于所述大类配置表在管理页面上输出规则大类列表，以供业务人员选取所述待添加的保险产品的核保规则类别，然后基于所述细类配置表输出核保规则列表。在这里，所述核保规则列表中包括业务人员从规则大类列表中所选择的类别对应的核保规则。在业务人员从所述核保规则列表中选取核保规则后，从所述细类配置表中获取所述核 保规则的规则编码；然后根据所述核保规则的规则内容，弹出规则带入值输入框。
示例性地，在获取到险种编码后，基于所述大类选择表输出规则大类列表，所述规则大类列表可以如表5所示。
若用户选择了保额类别，则基于所述细类配置表输出核保规则列表。假设所述细类配置表如表2所示，即所述保额类别包括保额倍数和保额最低，则输出的核保规则列表可以如表6所示。
R01保额
R02保费
R03份数
……
表5
R01保额 R0101保额倍数
…… R0102保额最低
表6
根据业务人员从所述核保规则列表中选取的核保规则，比如保额倍数，从所述细类配置表中获取所述核保规则的规则编码和规则内容，保额倍数对应的规则编码为R0101，然后根据所述核保规则的规则内容，弹出规则带入值输入框。
可选地，本申请实施例还可以对业务人员从所述核保规则列表中选取的核保规则进行标记，以记录业务人员所选择的核保规则，方便业务人员从所述核保规则列表中批量配置所述待添加的保险产品的核保规则。
在步骤S1023中，关联所述险种编码和所述规则编码，并添加至所述险种配置表中。
在获取到险种编码和规则编码后，根据规则编码的个数在所述险种配置表中新建相应的行，将所述规则编码分别填充至每一行中，并填充每一行的险种编码、规则带入值，以完成对所述保险产品的核保规则的录入操作。
本申请实施例基于所述配置表，实现了从业务人员的角度录入核保规则，解决了现有技术采用硬代码支持的方式添加核保规则导致的代码晦涩难懂、没有规律性的问题，方便了业务人员根据业务需求核保规则进行添加、修改。
进一步地，基于图1提供的核保校验的方法的第一实现流程的基础上，提出本申请实施 例提供的核保校验的方法的第四实现流程。
如图4所示，是本申请实施例提供的核保校验的方法的第四实现流程示意图。在本申请实施例中，所述预设的反射机制为java反射机制，所述步骤S105基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验包括：
在步骤S1051中，根据所述校验类名创建对象。
在这里，本申请实施例采用java反射机制，所谓java反射机制是指在运行时根据指定的类名获得类的信息，其提供的功能包括：在运行时判断任意一个对象所属的类；在运行时构造任意一个类的对象；在运行时判断任意一个类所具有的成员变量和方法；在运行时调用任意一个对象的方法；生成动态代理。因此，本申请实施例从校验参数中获取校验类名，然后基于所述校验类名实例化对象。
示例性地，假设校验类名为ruleclass，则可以通过Class ruleCla＝Class.forName(ruleClass)从细类配置表中找到类，然后通过Object instanceObj＝ruleCla.newInstance()实例化对象。
在步骤S1052中，获取规则内容和规则带入值。
在这里，使用反射的方式，需要从配置文件中取出类的属性信息。在本申请实施例中，所述属性信息为规则内容和规则带入值。实例化对象后，本申请实施例根据所述险种编码从所述险种配置表中获取规则编码及规则带入值，然后根据所述规则编码从细类配置表中获取规则内容。
可选地，所述获取规则内容和规则带入值的方式包括但不限于：通过Field getField(String name)获得命名的公共字段；通过Field[]getFields()获得类的所有公共字段；通过Field getDeclaredField(String name)获得类声明的命名的字段；通过Field[]getDeclaredFields()获得类声明的所有字段。
在步骤S1053中，通过所创建的对象根据所述规则内容和规则带入值调用校验方法。
可选地，调用校验方法的方式包括但不限于：通过Method getMethod(String name,Class[]params)使用特定的参数类型，获得命名的公共方法；通过Method[]getMethods()获得类的所有公共方法；通过Method getDeclaredMethod(String name,Class[]params)使用特写的参数类型，获得类声明的命名的方法；通过Method[]getDeclaredMethods()获得类声明的所有方法。
在步骤S1054中，运行所述校验方法，以完成对所述客户信息的校验。
在得到校验方法后，执行所述校验方法。示例性地，如前所述，假设校验类名为ruleclass，则可以通过：
Method setDefaultInfo＝ruleCla.getMethod("setDefaultInfoDTO",
new Class[]{DefaultInfoDTO.class})；
setDefaultInfo.invoke(instanceObj,defaultInfoDTO)；
来执行校验方法。所述校验方法根据所述ruleclass类的属性信息对所述客户信息的校验，比如，若规则内容为保额倍数，规则带入值为500，则检验所述客户信息中的保额是否为500的倍数。
本申请实施例采用反射机制并结合配置表的方式来实现核保规则的校验，达到了在程序开发过程中程序代码与配置文件相分离的效果，校验程序易读易懂，规则代码的耦合度低，方便了业务人员对核保规则进行管理、开发。当需要从一个校验方法切换到另一个校验方法时，无需修改代码，也无需重新编译，只需要修改配置文件，即配置表，再运行即可。
应理解，在上述实施例中，各步骤的序号的大小并不意味着执行顺序的先后，各步骤的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
实施例2
图5示出了本申请实施例提供的核保校验的装置的组成结构图，为了便于说明，仅示出了与本申请实施例相关的部分。
在本申请实施例中，所述核保校验的装置用于实现上述图1、图2、图3、图4实施例中所述的核保校验的方法，可以是内置于服务器的软件单元、硬件单元或者软硬件结合的单元、
参阅图5，所述核保校验的装置包括：
构建模块51，用于基于核保规则的类别在数据库中构建配置表；
分类模块52，用于根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
第一获取模块53，用于在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
第二获取模块54，用于根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
校验模块55，用于基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
可选地，所述构建模块51包括：
第一构建单元511，用于基于核保规则的类别在数据库中构建大类配置表，所述大类配置表用于记录规则大类与大类编码之间的对应关系；
第二构建单元512，用于基于所述大类配置表在数据库中构建细类配置表，所述细类配置表用于记录核保规则的规则编码、规则内容、校验类名及与大类编码之间的对应关系；
第三构建单元513，用于基于所述细类配置表在数据库中构建险种配置表，所述险种配置表用于记录险种编码及与其相关的核保规则的规则编码、规则带入值。
可选地，所述分类模块52包括：
第一获取单元521，用于基于管理界面上的录入操作，获取待添加的保险产品的险种编码；
第二获取单元522，用于基于管理界面上的选择操作，从所述大类配置表和细类配置表中获取所述待添加的保险产品对应的核保规则的规则编码；
关联单元523，用于关联所述险种编码和所述规则编码，并添加至所述险种配置表中。
可选地，所述预设的反射机制为java反射机制。
可选地，所述校验模块55包括：
对象创建单元551，用于根据所述校验类名创建对象；
属性获取单元552，用于获取规则内容和规则带入值；
方法调用单元553，用于通过所创建的对象根据所述规则内容和规则带入值调用校验方法；
方法执行单元554，用于执行所述校验方法，以完成对所述客户信息的校验。
需要说明的是，本申请实施例中的各模块/单元可以用于实现上述方法实施例中的全部技术方案，其具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
实施例3
本实施例提供一计算机可读存储介质，该计算机可读存储介质上存储有计算机可读指令，该计算机可读指令被处理器执行时实现实施例1中核保校验的方法，为避免重复，这里不再赘述。或者，该计算机可读指令被处理器执行时实现实施例2中核保校验的装置中各模块/单元的功能，为避免重复，这里不再赘述。
实施例4
图6是本申请实施例提供的一种终端的示意图，所述终端包括但不限于服务器、移动终端。如图6所示，该实施例的终端6包括：处理器60、存储器61以及存储在所述存储器 61中并可在所述处理器60上运行的计算机可读指令62。所述处理器60执行所述计算机可读指令62时实现上述核保校验的方法实施例中的步骤，例如图1所示的步骤S101至S105，图2实施例中所述的步骤S1011至S1013，图3实施例中所述的步骤S1021至S1023以及图4实施例中所述的步骤S1051至步骤S1054；或者，所述处理器60执行所述计算机可读指令62时实现上述核保校验的装置实施例中各模块/单元的功能，例如图5所示模块51至55的功能。
示例性的，所述计算机可读指令62可以被分割成一个或多个模块/单元，所述一个或者多个模块/单元被存储在所述存储器61中，并由所述处理器60执行，以完成本申请。所述一个或多个模块/单元可以是能够完成特定功能的一系列计算机可读指令的指令段，该指令段用于描述所述计算机可读指令62在所述终端6中的执行过程。例如，所述计算机可读指令62可以被分割成构建模块、分类模块、第一获取模块、第二获取模块、校验模块，各模块具体功能如下：
构建模块，用于基于核保规则的类别在数据库中构建配置表；
分类模块，用于根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
第一获取模块，用于在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
第二获取模块，用于根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
校验模块，用于基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
所述终端6可以是桌上型计算机、笔记本、掌上电脑及云端服务器等计算设备。所述终端可包括，但不仅限于，处理器60、存储器61。本领域技术人员可以理解，图6仅仅是终端6的示例，并不构成对终端6的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件，例如所述终端还可以包括输入输出设备、网络接入设备、总线等。
所称处理器60可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等，所述处理器是所述终端的控制中心，利用各种接口和线路连接整个终端的各个部分。
所述存储器61可用于存储所述计算机可读指令和/或模块，所述处理器通过运行或执行存储在所述存储器内的计算机可读指令和/或模块，以及调用存储在存储器内的数据，实现所述终端的各种功能。所述存储器可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据终端的使用所创建的数据等。此外，存储器可以包括高速随机存取存储器，还可以包括非易失性存储器，例如硬盘、内存、插接式硬盘、智能存储卡(Smart Media Card，SMC)、安全数字卡(Secure Digital，SD)、闪存卡(Flash Card)，至少一个磁盘存储器件、闪存器件或其他易失性固态存储器件。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的模块/单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读存储介质中。基于这样的理解，本申请实现上述实施例方法中的全部或部分流程，也可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一计算机可读存储介质中，该计算机可读指令在被处理器执行时，可实现上述各个方法实施例的步骤。其中，所述计算机可读指令包括计算机可读指令代码，所述计算机可读指令代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读存储介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读存储介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可读存储介质不包括是电载波信号和电信信号。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种核保校验的方法，其特征在于，所述方法包括：
    基于核保规则的类别在数据库中构建配置表；
    根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
    在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
    根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
    基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
  2. 如权利要求1所述的核保校验的方法，其特征在于，所述基于核保规则的类别在数据库中构建配置表包括：
    基于核保规则的类别在数据库中构建大类配置表，所述大类配置表用于记录规则大类与大类编码之间的对应关系；
    基于所述大类配置表在数据库中构建细类配置表，所述细类配置表用于记录核保规则的规则编码、规则内容、校验类名及与大类编码之间的对应关系；
    基于所述细类配置表在数据库中构建险种配置表，所述险种配置表用于记录险种编码及与其相关的核保规则的规则编码、规则带入值。
  3. 如权利要求2所述的核保校验的方法，其特征在于，所述根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中包括：
    基于管理界面上的录入操作，获取待添加的保险产品的险种编码；
    基于管理界面上的选择操作，从所述大类配置表和细类配置表中获取所述待添加的保险产品对应的核保规则的规则编码；
    关联所述险种编码和所述规则编码，并添加至所述险种配置表中。
  4. 如权利要求1至3任一项所述的核保校验的方法，其特征在于，所述预设的反射机制为java反射机制。
  5. 如权利要求4所述的核保校验的方法，其特征在于，所述基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验包括：
    根据所述校验类名创建对象；
    获取规则内容和规则带入值；
    通过所创建的对象根据所述规则内容和规则带入值调用校验方法；
    执行所述校验方法，以完成对所述客户信息的校验。
  6. 一种核保校验的装置，其特征在于，所述装置包括：
    构建模块，用于基于核保规则的类别在数据库中构建配置表；
    分类模块，用于根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
    第一获取模块，用于在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
    第二获取模块，用于根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
    校验模块，用于基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
  7. 如权利要求6所述的核保校验的装置，其特征在于，所述构建模块包括：
    第一构建单元，用于基于核保规则的类别在数据库中构建大类配置表，所述大类配置表用于记录规则大类与大类编码之间的对应关系；
    第二构建单元，用于基于所述大类配置表在数据库中构建细类配置表，所述细类配置表用于记录核保规则的规则编码、规则内容、校验类名及与大类编码之间的对应关系；
    第三构建单元，用于基于所述细类配置表在数据库中构建险种配置表，所述险种配置表用于记录险种编码及与其相关的核保规则的规则编码、规则带入值。
  8. 如权利要求7所述的核保校验的装置，其特征在于，所述分类模块包括：
    第一获取单元，用于基于管理界面上的录入操作，获取待添加的保险产品的险种编码；
    第二获取单元，用于基于管理界面上的选择操作，从所述大类配置表和细类配置表中获取所述待添加的保险产品对应的核保规则的规则编码；
    关联单元，用于关联所述险种编码和所述规则编码，并添加至所述险种配置表中。
  9. 如权利要求6至8任一项所述的核保校验的装置，其特征在于，所述预设的反射机制为java反射机制。
  10. 如权利要求9所述的核保校验的装置，其特征在于，所述校验模块包括：
    对象创建单元，用于根据所述校验类名创建对象；
    属性获取单元，用于获取规则内容和规则带入值；
    方法调用单元，用于通过所创建的对象根据所述规则内容和规则带入值调用校验方法；
    方法执行单元，用于执行所述校验方法，以完成对所述客户信息的校验。
  11. 一种计算机可读存储介质，其上存储有计算机可读指令，其特征在于，该计算机可 读指令被处理器执行时实现如下步骤：
    基于核保规则的类别在数据库中构建配置表；
    根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
    在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
    根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
    基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
  12. 如权利要求11所述的计算机可读存储介质，其特征在于，所述基于核保规则的类别在数据库中构建配置表包括：
    基于核保规则的类别在数据库中构建大类配置表，所述大类配置表用于记录规则大类与大类编码之间的对应关系；
    基于所述大类配置表在数据库中构建细类配置表，所述细类配置表用于记录核保规则的规则编码、规则内容、校验类名及与大类编码之间的对应关系；
    基于所述细类配置表在数据库中构建险种配置表，所述险种配置表用于记录险种编码及与其相关的核保规则的规则编码、规则带入值。
  13. 如权利要求12所述的计算机可读存储介质，其特征在于，所述根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中包括：
    基于管理界面上的录入操作，获取待添加的保险产品的险种编码；
    基于管理界面上的选择操作，从所述大类配置表和细类配置表中获取所述待添加的保险产品对应的核保规则的规则编码；
    关联所述险种编码和所述规则编码，并添加至所述险种配置表中。
  14. 如权利要求11至13任一项所述的计算机可读存储介质，其特征在于，所述预设的反射机制为java反射机制。
  15. 如权利要求14所述的计算机可读存储介质，其特征在于，所述基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验包括：
    根据所述校验类名创建对象；
    获取规则内容和规则带入值；
    通过所创建的对象根据所述规则内容和规则带入值调用校验方法；
    执行所述校验方法，以完成对所述客户信息的校验。
  16. 一种终端，所述终端包括存储器、处理器及存储在存储器上并可在处理器上运行的 计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    基于核保规则的类别在数据库中构建配置表；
    根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中；
    在对客户信息进行核保校验时，获取所投保的保险产品的险种编码；
    根据所述险种编码从所述配置表中获取待校验的核保规则及其校验类名；
    基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验。
  17. 如权利要求16所述的终端，其特征在于，所述基于核保规则的类别在数据库中构建配置表包括：
    基于核保规则的类别在数据库中构建大类配置表，所述大类配置表用于记录规则大类与大类编码之间的对应关系；
    基于所述大类配置表在数据库中构建细类配置表，所述细类配置表用于记录核保规则的规则编码、规则内容、校验类名及与大类编码之间的对应关系；
    基于所述细类配置表在数据库中构建险种配置表，所述险种配置表用于记录险种编码及与其相关的核保规则的规则编码、规则带入值。
  18. 如权利要求17所述的终端，其特征在于，所述根据业务配置指令将保险产品的险种编码及核保规则分类存储至所述配置表中包括：
    基于管理界面上的录入操作，获取待添加的保险产品的险种编码；
    基于管理界面上的选择操作，从所述大类配置表和细类配置表中获取所述待添加的保险产品对应的核保规则的规则编码；
    关联所述险种编码和所述规则编码，并添加至所述险种配置表中。
  19. 如权利要求16至18任一项所述的终端，其特征在于，所述预设的反射机制为java反射机制。
  20. 如权利要求19所述的终端，其特征在于，所述基于所述待校验的核保规则及其校验类名，通过预设的反射机制调用校验方法，执行所述校验方法完成对所述客户信息的校验包括：
    根据所述校验类名创建对象；
    获取规则内容和规则带入值；
    通过所创建的对象根据所述规则内容和规则带入值调用校验方法；
    执行所述校验方法，以完成对所述客户信息的校验。
PCT/CN2018/077309 2018-01-08 2018-02-27 核保校验的方法、装置、存储介质及终端 Ceased WO2019134232A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810014124.3A CN108460688A (zh) 2018-01-08 2018-01-08 核保校验的方法、装置、存储介质及终端
CN201810014124.3 2018-01-08

Publications (1)

Publication Number Publication Date
WO2019134232A1 true WO2019134232A1 (zh) 2019-07-11

Family

ID=63220494

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077309 Ceased WO2019134232A1 (zh) 2018-01-08 2018-02-27 核保校验的方法、装置、存储介质及终端

Country Status (2)

Country Link
CN (1) CN108460688A (zh)
WO (1) WO2019134232A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111161448B (zh) * 2018-11-07 2022-10-04 北京燧昀科技有限公司 数据存储方法、数据校验方法、装置、设备及存储介质
CN109712000A (zh) * 2018-11-27 2019-05-03 平安科技（深圳）有限公司 重复投保限制方法、装置、设备及可读存储介质
CN109816330B (zh) * 2018-12-15 2024-03-01 中国平安人寿保险股份有限公司 规则校验方法、装置、电子设备及计算机可读存储介质
CN109801174B (zh) * 2018-12-26 2023-11-17 平安科技（深圳）有限公司 理赔数据处理方法、装置、设备及计算机可读存储介质
CN109857450B (zh) * 2019-01-31 2024-05-31 平安科技（深圳）有限公司 一种校验服务编排方法及装置
CN110347691B (zh) * 2019-05-29 2023-10-31 平安科技（深圳）有限公司 证件类型校验方法、装置、计算机设备及存储介质
CN110502732A (zh) * 2019-07-09 2019-11-26 威富通科技有限公司 一种优惠券的规则生成方法、装置及服务器
CN110471934A (zh) * 2019-08-19 2019-11-19 泰康保险集团股份有限公司 业务数据的校验方法、装置、介质及电子设备
CN110689442A (zh) * 2019-09-02 2020-01-14 中国人民人寿保险股份有限公司 一种核保方法及系统
CN111461902B (zh) * 2020-03-31 2023-12-15 泰康保险集团股份有限公司 保费处理方法、装置、设备及计算机可读存储介质
CN112488855B (zh) * 2020-11-23 2024-02-13 中国人寿保险股份有限公司 一种基于规则模板的业务校验方法及设备
CN112651843A (zh) * 2020-12-30 2021-04-13 中国平安人寿保险股份有限公司 产品的交纳方式控制方法、装置、计算机设备及存储介质
CN113742329A (zh) * 2021-09-09 2021-12-03 中国平安人寿保险股份有限公司 数据核对方法、装置、设备及存储介质
CN113872163A (zh) * 2021-09-30 2021-12-31 国网河北省电力有限公司电力科学研究院 继电保护定值校验方法及终端设备
CN113935847A (zh) * 2021-11-23 2022-01-14 深圳壹账通科技服务有限公司 线上流程的风险处理方法、装置、服务器及介质
CN114925098A (zh) * 2022-05-25 2022-08-19 中国银行股份有限公司 一种确定产品可用性的方法及装置
CN117252715B (zh) * 2023-11-20 2024-02-23 南京华合信息科技有限公司 基于规则引擎的保险核保检查方法、系统
CN118963904A (zh) * 2024-10-16 2024-11-15 太平金融科技服务（上海）有限公司 一种规则的处理方法、装置、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090055227A1 (en) * 2008-10-30 2009-02-26 Bakos Thomas L Risk Assessment Company
CN105809549A (zh) * 2016-02-23 2016-07-27 平安科技（深圳）有限公司 医务智能核保方法和系统
CN106204284A (zh) * 2016-06-30 2016-12-07 北京未来付网络技术有限公司 一种预核保系统的未来付款产品的实现方法和装置
CN107203942A (zh) * 2016-03-15 2017-09-26 平安科技（深圳）有限公司 保险信息处理方法和系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030182159A1 (en) * 2001-12-31 2003-09-25 Bonissone Piero Patrone Process for summarizing information for insurance underwriting suitable for use by an automated system
CN102999868A (zh) * 2011-09-16 2013-03-27 美国友邦保险有限公司 基于云端运算的保险契约营运系统、方法及业务管理工具
US20130304514A1 (en) * 2012-05-08 2013-11-14 Elwha Llc Systems and methods for insurance based on monitored characteristics of an autonomous drive mode selection system
CN103095726A (zh) * 2013-02-07 2013-05-08 航天科工深圳（集团）有限公司 一种协议解析器的处理方法和装置
CN104375861B (zh) * 2014-11-04 2017-06-09 北京奇虎科技有限公司 基于安卓平台的应用程序免安装运行的方法、装置及终端
CN104966239A (zh) * 2015-06-30 2015-10-07 天津爱蔻科技有限公司 一种基于规则引擎的智能核保平台
CN106934718B (zh) * 2015-12-29 2021-02-26 平安科技（深圳）有限公司 投保单的自动承保方法及系统
CN106384222A (zh) * 2016-03-29 2017-02-08 平安科技（深圳）有限公司 保单回销方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090055227A1 (en) * 2008-10-30 2009-02-26 Bakos Thomas L Risk Assessment Company
CN105809549A (zh) * 2016-02-23 2016-07-27 平安科技（深圳）有限公司 医务智能核保方法和系统
CN107203942A (zh) * 2016-03-15 2017-09-26 平安科技（深圳）有限公司 保险信息处理方法和系统
CN106204284A (zh) * 2016-06-30 2016-12-07 北京未来付网络技术有限公司 一种预核保系统的未来付款产品的实现方法和装置

Also Published As

Publication number Publication date
CN108460688A (zh) 2018-08-28

Similar Documents

Publication Publication Date Title
WO2019134232A1 (zh) 核保校验的方法、装置、存储介质及终端
WO2020057016A1 (zh) 基于区块链的保险理赔方法、电子装置及存储介质
WO2022105135A1 (zh) 信息审核方法、装置、电子设备及存储介质
CN107784063B (zh) 算法的生成方法及终端设备
US8949138B2 (en) Managing an insurance product with an insurance value chain
US20210295223A1 (en) Cognitive automation based vendor compliance system
US12314232B2 (en) Shared hierarchical data design model for transferring data within distributed systems
US12242437B2 (en) Automated determination of accurate data schema
JP2024524094A (ja) データガバナンスシステム及び方法
CN108153877A (zh) 数据字典展示方法、装置、终端设备及存储介质
CN114840531A (zh) 基于血缘关系的数据模型重构方法、装置、设备及介质
US11593511B2 (en) Dynamically identifying and redacting data from diagnostic operations via runtime monitoring of data sources
CN110750530B (zh) 一种业务系统及其数据核对方法
CN119441261A (zh) 基于检索增强的语言转换方法、装置及存储介质
US20240086409A1 (en) Techniques for pre-assignment validation of data managed by a data processing system
CN114661803A (zh) 数据库服务接口发布方法、系统、计算机设备和存储介质
CN110110530B (zh) 基于bim平台的信息权限管理方法、装置以及存储装置
CN115391438A (zh) 数据仓库配置文档的生成方法、装置、设备和存储介质
CN111897728B (zh) 接口调试方法及相关设备
US10019763B2 (en) Extension ledger
CN115328990B (zh) 组织结构树的展示方法、装置、设备及存储介质
CN111986033B (zh) 一种等效表达式识别方法、识别装置及终端设备
CN117194425A (zh) 数据存储方法、装置、电子设备及存储介质
CN114782013A (zh) 用于流程建模的请求处理方法、装置及电子设备
CN116009889A (zh) 深度学习模型的部署方法、装置、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18897936

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC , EPO FORM 1205A DATED 13.10.2020.

122 Ep: pct application non-entry in european phase

Ref document number: 18897936

Country of ref document: EP

Kind code of ref document: A1