WO2019134232A1 - Procédé de réalisation d'une vérification de souscription, dispositif, support d'informations et terminal - Google Patents

Procédé de réalisation d'une vérification de souscription, dispositif, support d'informations et terminal 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
Application number
PCT/CN2018/077309
Other languages
English (en)
Chinese (zh)
Inventor
付舒婷
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019134232A1 publication Critical patent/WO2019134232A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • 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

La présente invention se rapporte au domaine technique des communications et concerne un procédé de réalisation d'une vérification de souscription. Le procédé consiste : à construire une table de configuration dans une base de données en fonction de catégories de règles de souscription ; à catégoriser et à mémoriser, en fonction d'une instruction de configuration de service, des numéros de série de types de police d'assurance de produits d'assurance et des règles de souscription de ces derniers dans la table de configuration ; à acquérir un numéro de série d'un type de police d'assurance d'un produit d'assurance à acheter lors de la réalisation d'une vérification de souscription sur des informations de client ; à acquérir, en fonction du numéro de série du type de police d'assurance et de la table de configuration, une règle de souscription à vérifier et un nom de catégorie de vérification de cette dernière ; et à invoquer, au moyen d'un mécanisme de réflexion prédéterminé, un procédé de vérification en fonction de la règle de souscription à vérifier et du nom de catégorie de vérification de cette dernière, et à exécuter le procédé de vérification afin d'effectuer la vérification des informations de client. La présente invention permet de réaliser une mémorisation catégorisée de règles de souscription et utilise la combinaison d'une table de configuration et d'un mécanisme de réflexion pour permettre à un programme de vérification d'être indépendant d'un fichier de configuration, de telle sorte qu'un programme de vérification est facile à lire et à comprendre, ce qui permet de réduire efficacement le niveau de couplage de code, et de faciliter la gestion et le développement de règles de souscription pour le personnel de service.
PCT/CN2018/077309 2018-01-08 2018-02-27 Procédé de réalisation d'une vérification de souscription, dispositif, support d'informations et terminal WO2019134232A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=63220494

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077309 WO2019134232A1 (fr) 2018-01-08 2018-02-27 Procédé de réalisation d'une vérification de souscription, dispositif, support d'informations et terminal

Country Status (2)

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

Families Citing this family (16)

* 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 深圳壹账通科技服务有限公司 线上流程的风险处理方法、装置、服务器及介质
CN117252715B (zh) * 2023-11-20 2024-02-23 南京华合信息科技有限公司 基于规则引擎的保险核保检查方法、系统

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 (fr) Procédé de réalisation d'une vérification de souscription, dispositif, support d'informations et terminal
CN107784063B (zh) 算法的生成方法及终端设备
WO2022105135A1 (fr) Procédé et appareil de vérification d'informations, et dispositif électronique et support d'enregistrement
CN108460068B (zh) 报表导入导出的方法、装置、存储介质及终端
CN110750530B (zh) 一种业务系统及其数据核对方法
US20240143561A1 (en) Shared hierarchical data design model for transferring data within distributed systems
CN108153877A (zh) 数据字典展示方法、装置、终端设备及存储介质
US20210295223A1 (en) Cognitive automation based vendor compliance system
US20220398337A1 (en) Data governance systems and methods
CN110110530B (zh) 基于bim平台的信息权限管理方法、装置以及存储装置
WO2009002901A2 (fr) Mappage basé sur un modèle d'objet
CN114840531A (zh) 基于血缘关系的数据模型重构方法、装置、设备及介质
CN114186961A (zh) 业务审批流程配置方法、装置、计算机设备和存储介质
US20150206250A1 (en) Managing an insurance product with an insurance value chain
US11593511B2 (en) Dynamically identifying and redacting data from diagnostic operations via runtime monitoring of data sources
US20140278820A1 (en) Managing the Topology of Software Licenses in Heterogeneous and Virtualized Environments
US10019763B2 (en) Extension ledger
CN114004542B (zh) 一种企业任务管理方法、系统、计算机设备及存储介质
US20230251959A1 (en) System and Method for Generating Synthetic Test Data
CN111897728B (zh) 接口调试方法及相关设备
CN114816392A (zh) 基于人工智能的组件参数自动封装方法及相关设备
US11222133B1 (en) User programmatic interface for supporting data access control in a database system
US20240086409A1 (en) Techniques for pre-assignment validation of data managed by a data processing system
US20230010147A1 (en) Automated determination of accurate data schema
US11900085B2 (en) System and method for semantic aware data science

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