WO2020107591A1 - 重复投保限制方法、装置、设备及可读存储介质 - Google Patents
重复投保限制方法、装置、设备及可读存储介质 Download PDFInfo
- Publication number
- WO2020107591A1 WO2020107591A1 PCT/CN2018/123189 CN2018123189W WO2020107591A1 WO 2020107591 A1 WO2020107591 A1 WO 2020107591A1 CN 2018123189 W CN2018123189 W CN 2018123189W WO 2020107591 A1 WO2020107591 A1 WO 2020107591A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- insurance
- verified
- type
- verification
- information
- 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
Links
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 relates to the technical field of insurance, and in particular to a method, device, device and readable storage medium for limiting repeated insurance.
- the main purpose of this application is to provide a method, device, equipment and readable storage medium for repeated insurance restrictions, which aims to solve the problem that the verification process of custom-developed insurance products in the prior art cannot meet the needs of the rapid development of insurance business, which reduces Technical issues of insurance verification efficiency.
- the present application provides a method for limiting repeated insurance, which includes:
- the information of the insurance type to be verified carried in the verification instruction and the type of insurance type to which the insurance type to be verified belongs are obtained;
- the target verification process is created based on preset configuration information
- the insurance type to be verified is repeatedly insured and verified, and the verification result is output.
- the method includes:
- the pre-stored target verification process is called to verify the insurance type to be verified;
- the verification of the insurance type to be verified includes the verification of the insurance time range of the insurance type to be verified and the number of insurance policies.
- the step of generating the target verification process based on preset configuration information includes:
- the combination order of the target metadata is acquired based on the configuration information, and the target metadata is combined according to the combination order to obtain a target verification process.
- the acquiring the combination order of the target metadata based on the configuration information, combining the target metadata according to the combination order, and obtaining the target verification process includes:
- the combination order of the target metadata is acquired based on the step attribute, and the target metadata is combined according to the combination order to obtain a target verification process.
- the step of obtaining each target metadata based on the risk element and the processing logic framework includes:
- the processing rules are set to the target metadata.
- the step of performing repeated insurance verification on the information of the insurance type to be verified based on the generated target verification process and outputting the verification result includes:
- time range information corresponding to each insurance policy to be verified is obtained from the information of the insurance type to be verified;
- the steps include:
- the present application also provides a repeated insurance restriction device, the repeated insurance restriction device includes:
- the detection module is used to obtain the information of the insurance type to be verified carried in the verification instruction and the type of insurance type to which the insurance type to be verified is carried when the repeated insurance verification instruction is detected;
- the judgment module is used for judging whether the target verification process corresponding to the insurance type belongs to the pre-stored;
- a generating module configured to create the target verification process based on preset configuration information if there is no target verification process corresponding to the insurance category to which it belongs;
- the verification module is configured to repeatedly insure and verify the insurance type to be verified based on the created target verification process and the information of the insurance type to be verified, and output the verification result.
- the present application also provides a readable storage medium that stores one or more programs, and the one or more programs may be executed by one or more processors to Used for:
- the information of the insurance type to be verified carried in the verification instruction and the type of insurance type to which the insurance type to be verified belongs are obtained;
- the target verification process is created based on preset configuration information
- the insurance type to be verified is repeatedly insured and verified, and the verification result is output.
- This application obtains the information of the insurance type to be verified carried in the verification instruction and the type of insurance type to which the insurance type to be checked is carried when a repeated insurance verification instruction is detected; it is determined whether the corresponding insurance type category is pre-stored Target verification process; if there is no target verification process corresponding to the insurance category, the target verification process is created based on preset configuration information; based on the created target verification process and the to-be-verified The information of the insurance type performs repeated insurance verification on the insurance type to be verified, and outputs the verification result.
- the main purpose of the present application is to provide a method, device, device and readable storage medium for limiting repeated insurance, aiming to solve the technical problem of multiple repeated insurance in the prior art and reducing the efficiency of insurance verification.
- FIG. 1 is a schematic flowchart of a first embodiment of a method for limiting repeated insurance application in this application
- FIG. 2 is a detailed flow diagram of the steps of generating the target verification process based on preset configuration information in the second embodiment of the repeated insurance restriction method of the present application;
- FIG. 3 is a schematic diagram of a device structure of a hardware operating environment involved in the method of an embodiment of the present application
- FIG. 4 is a schematic diagram of a module of a repeated insurance restriction device of the present application.
- the present application provides a method for limiting repeated insurance coverage.
- the method for limiting repeated insurance coverage includes:
- Step S10 When the repeated insurance verification instruction is detected, the information of the insurance type to be verified carried in the verification instruction and the type of insurance type to which the insurance type to be verified belongs are obtained;
- step S20 it is determined whether the target verification process corresponding to the insurance type belongs to the pre-stored
- Step S30 if there is no target verification process corresponding to the insurance category to which it belongs, the target verification process is created based on preset configuration information;
- Step S40 based on the created target verification process and the information of the insurance type to be verified, the insurance type to be verified is repeatedly insured and verified, and the verification result is output.
- Step S10 When the repeated insurance verification instruction is detected, the information of the insurance type to be verified carried in the verification instruction and the type of insurance type to which the insurance type to be verified belongs are obtained;
- the repetitive insurance restriction method is applied to a repetitive insurance restriction system.
- the repetitive insurance restriction system as long as the repetitive insurance verification instruction is detected, the information of the insurance type to be checked carried in the verification instruction and the to-be-checked
- the repeated insurance verification instruction triggering method includes: when a purchase instruction triggered by the user's purchase operation is detected, the repeated insurance verification instruction is triggered synchronously.
- the verification instruction carries the information of the type of insurance to be verified and the type of insurance to which the type of insurance to be verified belongs.
- the information of the type of insurance to be verified includes the name, code and user purchasing the type of insurance Information such as the user’s ID number, system registration number, etc.
- the type of insurance to be verified mainly refers to the type or category of the insurance policy purchased is accident insurance, deferred insurance or critical illness insurance.
- accident insurance It also includes aviation accident insurance, operational accident insurance and other types of insurance.
- Deferred insurance also includes aviation delay insurance and transportation delay insurance.
- step S20 it is determined whether the target verification process corresponding to the insurance type belongs to the pre-stored
- the method of determining whether the target verification process corresponding to the insurance category belongs to the following includes:
- Method 1 Judging based on the name of the type of insurance and the name of the verification process, for example, if the name of the type of insurance is the same as the name of the verification process, it is determined that the target verification process corresponding to the corresponding type of insurance is pre-stored, otherwise, If the name of the insurance type is not the same as the name of the verification process, it is determined that the target verification process corresponding to the belonging insurance type is not pre-stored.
- Method 2 Judging from the identification of the type of insurance and the identification of the verification process, for example, if the name of the type of insurance and the name of the verification process are both A, then it is determined that the target verification process corresponding to the corresponding type of insurance is pre-stored . Conversely, if the identification of the insurance type is not the same as the identification of the verification process, it is determined that the target verification process corresponding to the belonging insurance type is not pre-stored.
- Step S21 if the target verification process corresponding to the insurance type belongs to it is pre-stored, the pre-stored target verification process is called to verify the insurance type to be verified;
- the pre-stored target verification process is directly invoked through an interface or a corresponding script to verify the insurance type to be verified.
- the verification of the insurance type to be verified includes the verification of the insurance time range of the insurance type to be verified and the number of insurance policies.
- the verification of the insurance type to be verified includes the verification of the insured time range of the insurance type to be verified and the number of insured policies, and the verification of the insurance time range of the insured insurance type and the number of insured policies includes the treatment of the insurance Check the time range of each policy and the number of policies.
- the type of insurance to be verified involves 2 types of insurance, one type of insurance involves 5 types of policies, and the other type of insurance involves 10 types of policies.
- the time range of insurance coverage for the type of insurance to be verified and the number of insured policies include the verification of 5 policies
- Step S30 if there is no target verification process corresponding to the insurance category to which it belongs, the target verification process is created based on preset configuration information;
- the target verification process is created based on preset configuration information.
- the corresponding configuration information is already preset. For example, although the target verification process of accident insurance is not pre-stored, the configuration information of the target verification process of generating accident insurance is preset in the repeated insurance restriction.
- the step of generating the target verification process based on preset configuration information includes:
- Step S31 Parse the configuration information to obtain the risk type elements in the configuration information and the processing logic framework of the risk type elements;
- the configuration information is parsed to obtain the risk type elements in the configuration information and the processing logic framework of the risk type elements, where the risk type elements refer to elements such as time range, quantity and purchase amount, etc.
- the processing logic framework can be a complete processing step for processing the risk elements, and the processing logic framework can also be filled to complete the processing The framework of the steps.
- Step S32 based on the risk element and the processing logic framework, obtain each target metadata
- each target metadata is generated, and the target metadata is a verification process.
- the target metadata is a process of verifying the time range, or the quantity The verification process. It should be noted that, for the insurance type to be verified, there are generally multiple target metadata.
- Step S33 Acquire the combination order of the target metadata based on the configuration information, and combine the target metadata according to the combination order to obtain a target verification process.
- the configuration information in addition to the insurance element and the processing logic framework of the insurance element, it also includes the combination order of each target metadata.
- a target metadata is arranged before b target metadata, and b is sorted in c.
- the combination order of the target metadata is acquired based on the configuration information, and the target metadata is combined according to the combination order to obtain the target verification process.
- acquiring the combination order of the target metadata based on the configuration information, combining the target metadata according to the combination order, and obtaining a target verification process includes:
- Step S331 Obtain the step attribute of each target metadata based on the configuration information
- the step attribute of each target metadata is obtained based on the configuration information, and the step attribute of each target metadata may be determined according to the preset sequence identifier of the step, specifically, the risk element carries There is a preset sequence identifier. For example, if the risk category element carries sequence identifier 1, the step attribute of the target metadata corresponding to the risk category element is ranked at the top of the process. It should be noted that the sequence identifier can be composed of target metadata carry.
- Step S332 Acquire the combination order of the target metadata based on the step attributes, and combine the target metadata according to the combination order to obtain a target verification process.
- the target metadata is combined according to the combination order to obtain a target verification process.
- Step S40 based on the created target verification process and the information of the insurance type to be verified, the insurance type to be verified is repeatedly insured and verified, and the verification result is output.
- the insurance type to be verified is repeatedly insured and verified based on the created target verification process and the information of the risk to be verified, and a verification result is output, wherein the verification result Including the results of passing and failing the verification.
- This application obtains the information of the insurance type to be verified carried in the verification instruction and the type of insurance type to which the insurance type to be checked is carried when a repeated insurance verification instruction is detected; it is determined whether the corresponding insurance type category is pre-stored Target verification process; if there is no target verification process corresponding to the insurance category, the target verification process is created based on preset configuration information; based on the created target verification process and the to-be-verified The information of the insurance type performs repeated insurance verification on the insurance type to be verified, and outputs the verification result.
- the present application provides another embodiment of a method for limiting repeated insurance coverage.
- the step of obtaining each target metadata based on the insurance element and the processing logic framework includes:
- Step S321 obtaining an execution script corresponding to the processing logic framework
- the processing logic framework is an incomplete processing step for processing the risk element, that is, the processing logic framework is a framework that needs to be filled to obtain a complete processing step, and therefore, the processing logic framework can be filled in The execution script is pre-stored.
- Step S322 embedding the risk element into the processing logic framework based on the execution script to generate various processing rules for processing the risk element;
- the processing logic framework After obtaining the execution script, embed the insurance element into the processing logic framework to generate various processing rules for processing the insurance element, for example, if the configuration information in insurance type M includes the time range and the number of insurance elements, The time range and quantity are embedded in the processing logic framework to generate the time range and quantity execution rules such as performing a first comparison on the time scope and a second comparison on the quantity, etc.
- Step S323 Set each processing rule to each target metadata.
- each processing rule is set to each target metadata.
- each target metadata by obtaining an execution script corresponding to the processing logic framework; embedding the risk element into the processing logic framework based on the execution script to generate various processing rules for processing the risk element ; Set each processing rule to each target metadata.
- flexible generation of each target metadata is realized to reduce resource waste caused by customization.
- the present application provides another embodiment of a method for limiting repeated insurance coverage.
- the information based on the generated target verification process is used for repeated insurance coverage verification of the information to be verified and output
- the steps to verify the results include:
- Step S41 based on the generated target verification process, first extract the type of insurance code to be verified from the information of the type of insurance to be verified to obtain the limited number of insurance policies corresponding to the type of insurance code;
- the repeated insurance verification is specifically implemented.
- the insurance type code to be verified is first extracted from the information of the insurance type to be verified, the insurance type code may be multiple, and the insurance type codes are multiple, There may be one or more types of insurance types. After the codes are obtained, the limited number of insurance policies corresponding to the insurance type codes can be obtained, wherein each insurance type code can include multiple insurance policies, and the number of each insurance type code is limited.
- Step S42 judging whether the quantity of the policy to be verified is less than or equal to the restricted quantity
- the restricted quantity may be 1.
- Step S43 If the number of insurance policies to be checked is less than or equal to the limited quantity, then obtain time range information corresponding to each insurance policy to be checked from the information of the insurance type to be checked;
- the time range information corresponding to each insurance policy to be verified is obtained from the information of the insurance types to be verified, that is, after ensuring that the quantity meets the requirements Verification of the policy time range.
- Step S44 Determine whether the time range information corresponding to each policy to be checked is consistent, and if the time range information corresponding to each policy to be checked is consistent, determine that the insurance type to be checked is not repeatedly insured.
- the step of repeating the insurance verification on the information of the insurance type to be verified based on the generated target verification process and outputting the verification result includes:
- Step S50 if it is detected that the verification result is that the verification fails, generating text and voice prompt information that the verification fails;
- step S60 the text prompt information is sent to the preset inspector via email.
- the text prompt information is sent to the preset inspector by email. To generate mail records for easy follow-up inquiry.
- the double insurance is effectively avoided, and the efficiency of the insurance enterprise is improved.
- FIG. 3 is a schematic diagram of a device structure of a hardware operating environment involved in a solution of an embodiment of the present application.
- the repeated insurance restriction device may be a PC, or may be a smartphone, tablet computer, e-book reader, MP3 (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio layer 3 player, MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio layer 4) Terminal devices such as players and portable computers.
- MP3 Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio layer 3 player
- MP4 Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio layer 4
- Terminal devices such as players and portable computers.
- the repeated insurance restriction device may include: a processor 1001, such as a CPU, a memory 1005, and a communication bus 1002.
- the communication bus 1002 is used to implement connection communication between the processor 1001 and the memory 1005.
- the memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as disk storage.
- the memory 1005 may optionally be a storage device independent of the foregoing processor 1001.
- the repeated insurance restriction device may further include a target user interface, a network interface, a camera, and RF (Radio Frequency (radio frequency) circuits, sensors, audio circuits, WiFi modules, etc.
- the target user interface may include a display (Display), an input unit such as a keyboard (Keyboard), and the optional target user interface may also include a standard wired interface and a wireless interface.
- the network interface may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
- the structure of the repeated insurance restriction device shown in FIG. 3 does not constitute a limitation on the repeated insurance restriction device, and may include more or less components than the illustration, or a combination of certain components, or different Parts arrangement.
- the memory 1005 which is a computer storage medium, may include a readable instruction for operating a network communication module and repeating insurance restriction.
- the operating system is a program that manages and controls the repetitive insurance to limit equipment hardware and software resources, and supports the repetitive insurance to limit the operation of readable instructions and other software and/or programs.
- the network communication module is used to implement communication between various components inside the memory 1005, and to communicate with other hardware and software in the repeated insurance restriction device.
- the processor 1001 is configured to execute the repetitive insurance restriction readable instructions stored in the memory 1005 to implement the steps of the repetitive insurance restriction method described in any one of the above.
- the present application also provides a repeated insurance restriction device, the repeated insurance restriction device includes:
- the detection module 10 is configured to obtain information of the insurance type to be checked carried in the verification instruction and the type of insurance type to which the insurance type to be checked is carried when a repeated insurance verification instruction is detected;
- the judgment module 20 is used to judge whether the target verification process corresponding to the insurance type belongs to the pre-stored;
- the generating module 30 is configured to create the target verification process based on preset configuration information if there is no target verification process corresponding to the insurance category to which it belongs.
- the verification module 40 is configured to repeatedly insure and verify the insurance type to be verified based on the created target verification process and the information of the insurance type to be verified, and output the verification result.
- the present application provides a readable storage medium that stores one or more computer-readable instructions, and the one or more computer-readable instructions may also be executed by one or more processors to It is used to implement the steps of the repeated insurance restriction method described in any one of the above.
- the readable storage medium may be a non-volatile readable storage medium.
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
一种重复投保限制方法、装置、设备及可读存储介质,涉及大数据处理技术,所述方法包括:在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别(S10);判断是否预存有所述所属险种类别对应的目标校验流程(S20);若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程(S30);基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果(S40)。所述方法解决了现有技术中定制化开发保险产品的校验流程无法适应保险业务快速发展的需要,降低了投保校验效率的技术问题。
Description
本申请要求于2018年11月27日提交中国专利局、申请号为201811424207.6、发明名称为“重复投保限制方法、装置、设备及可读存储介质”的中国专利申请的优先权,其全部内容通过引用结合在申请中。
技术领域
本申请涉及保险技术领域,尤其涉及一种重复投保限制方法、装置、设备及可读存储介质。
背景技术
目前,重复投保现象严重,进而导致一件事件出现多重的理赔投诉,损失了保险企业的效益,另外,因重复投保对应多个理赔各机构管控方式是存有差异的,因而理赔投诉过程中沟通成本增加,进而降低了理赔效率,因而,保险企业需要对重复投保进行管控,目前,在对重复投保进行管控过程中,由于不同保险产品入件或者配置流程仍存在个性化差异,因而需要通过定制化开发保险产品的校验流程来实现快速配置,然而,定制化开发无法适应保险业务快速发展的需要,降低了用户体验。
发明内容
本申请的主要目的在于提供一种重复投保限制方法、装置、设备及可读存储介质,旨在解决现有技术中定制化开发保险产品的校验流程无法适应保险业务快速发展的需要,降低了投保校验效率的技术问题。
为实现上述目的,本申请提供一种重复投保限制方法,所述重复投保限制方法包括:
在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;
判断是否预存有所述所属险种类别对应的目标校验流程;
若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;
基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。
可选地,所述判断是否预存有所述所属险种类别对应的目标校验流程步骤之后,包括:
若预存有所述所属险种类别对应的目标校验流程,则调用所述预存的目标校验流程,对所述待校验险种进行校验;
其中,对所述待校验险种的校验包括对待校验险种的投保时间范围以及投保保单数量的校验。
可选地,所述基于预设配置信息生成所述目标校验流程的步骤包括:
解析所述配置信息,以获取所述配置信息中的险种元素,以及所述险种元素的处理逻辑框架;
基于所述险种元素以及所述处理逻辑框架,得到各个目标元数据;
基于所述配置信息获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
可选地,所述基于所述配置信息获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程的步骤包括:
基于所述配置信息获取所述各个目标元数据的步骤属性;
基于所述步骤属性获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
可选地,所述基于所述险种元素以及所述处理逻辑框架,得到各个目标元数据的步骤包括:
获取所述处理逻辑框架对应的执行脚本;
基于所述执行脚本将所述险种元素嵌入至所述处理逻辑框架中,以生成对所述险种元素进行处理的各个处理规则;
将所述各个处理规则设置为所述各个目标元数据。
可选地,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果的步骤包括:
基于所述生成的目标校验流程,先从所述待校验险种的信息中提取待校验的险种编码,以得到所述险种编码对应的投保保单的限制数量;
判断所述待校验保单数量是否小于等于所述限制数量;
若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息;
判断所述各待校验保单对应的时间范围信息是否一致,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保。
可选地,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果步骤之后,包括:
若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息;
将所述文本提示信息通过邮件发送给预设检验人员。
本申请还提供一种重复投保限制装置,所述重复投保限制装置包括:
检测模块,用于在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;
判断模块,用于判断是否预存有所述所属险种类别对应的目标校验流程;
生成模块,用于若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;
检验模块,用于基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。
此外,为实现上述目的,本申请还提供一种可读存储介质,所述可读存储介质存储有一个或者一个以上程序,所述一个或者一个以上程序可被一个或者一个以上的处理器执行以用于:
在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;
判断是否预存有所述所属险种类别对应的目标校验流程;
若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;
基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。
本申请通过在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;判断是否预存有所述所属险种类别对应的目标校验流程;若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。在本申请中,在进行重复投保检验时,若未预存有所述所属险种类别对应的目标校验流程,则不再需要定制化开发目标校验流程,而是只需要基于信贷产品的配置信息即可自动生成对应的目标校验流程,并基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,得到校验结果即可,因而提升了校验效率,解决了定制化开发保险产品的校验流程无法适应保险业务快速发展的需要,降低了投保校验效率的技术问题。
发明内容
本申请的主要目的在于提供一种重复投保限制方法、装置、设备及可读存储介质,旨在解决现有技术中重复投保多,降低了投保校验效率的技术问题。
附图说明
图1为本申请重复投保限制方法第一实施例的流程示意图;
图2为本申请重复投保限制方法第二实施例中基于预设配置信息生成所述目标校验流程步骤的细化流程示意图;
图3是本申请实施例方法涉及的硬件运行环境的设备结构示意图;
图4为本申请重复投保限制装置的模块示意图。
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
具体实施方式
应当理解,此处所描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
本申请提供一种重复投保限制方法,在本申请重复投保限制方法的第一实施例中,参照图1,所述重复投保限制方法包括:
步骤S10,在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;
步骤S20,判断是否预存有所述所属险种类别对应的目标校验流程;
步骤S30,若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;
步骤S40,基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。
具体步骤如下:
步骤S10,在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;
重复投保限制方法应用于重复投保限制系统,在该重复投保限制系统中,只要检测到重复投保校验指令时,即获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别,重复投保校验指令触发方式包括:在检测到基于用户的购买操作所触发的购买指令时,则同步触发重复投保校验指令。
在本实施例中,校验指令中携带有待校验险种的信息以及待校验险种的所属险种类别,待校验险种的信息包括待校验险种的名称、编码以及购买待校验险种的用户的信息如用户的身份证号、系统注册号等,待校验险种的所属险种类别主要指的是购买的保单是意外险、延期险或者是重疾险等类型或者是类别,另外,意外险还包括航空意外险,作业意外险等险种,延期险还包括航延险、以及运输延迟险等险种。
步骤S20,判断是否预存有所述所属险种类别对应的目标校验流程;
在得到待校验险种的信息以及待校验险种的所属险种类别后,需要判断重复投保限制系统中是否具有险种类别对应的目标校验流程,校验流程指的是校验步骤以及校验步骤的先后顺序,如是先进行待校验险种中各个投保保单的时间范围的校验,还是先进行待校验险种中投保保单数量的校验,或者是只进行待校验险种各个投保保单的时间范围的校验等,在本实施例中,判断是否预存有所述所属险种类别对应的目标校验流程方式包括:
方式一:根据险种类别的名称与校验流程的名称进行判断,例如,若险种类别的名称与校验流程的名称相同,则确定预存有所述所属险种类别对应的目标校验流程,反之,若险种类别的名称与校验流程的名称不相同,则确定未预存有所述所属险种类别对应的目标校验流程。
方式二:根据险种类别的标识与校验流程的标识进行判断,例如,若险种类别的名称与校验流程的名称相同都为A,则确定预存有所述所属险种类别对应的目标校验流程。反之,若险种类别的标识与校验流程的标识不相同,则确定未预存有所述所属险种类别对应的目标校验流程。
需要说明的是,上述方式一与方式二的实现依赖于在该重复投保限制系统中预存的,险种类别名称与校验流程名称的第一预设关联关系,或者是险种类别标识与校验流程标识的第二预设关联关系。
所述判断是否预存有所述所属险种类别对应的目标校验流程步骤之后,包括:
步骤S21,若预存有所述所属险种类别对应的目标校验流程,则调用所述预存的目标校验流程,对所述待校验险种进行校验;
若重复投保限制系统中预存有所述所属险种类别对应的目标校验流程,则直接通过接口或者是对应脚本调用预存的目标校验流程,对所述待校验险种进行校验。
其中,对所述待校验险种的校验包括对待校验险种的投保时间范围以及投保保单数量的校验。
对所述待校验险种的校验包括对待校验险种的投保时间范围以及投保保单数量的校验,对待校验险种的投保时间范围以及投保保单数量的校验包括对待校验险种中涉及的各个保单的投保时间范围以及各个投保保单数量的校验。例如,待校验险种涉及2个险种,其中一个险种涉及5个保单,另外一个险种涉及10个保单,对待校验险种的投保时间范围以及投保保单数量的校验包括对其中一个险种5个保单涉及的投保时间范围以及对该5个保单的保单数量的校验,以及另一个险种10个保单涉及的投保时间范围以及对该10个保单的保单数量的校验。
步骤S30,若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;
若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程,在生成目标校验流程前,对应的配置信息是已经预置好的。例如,尽管未生预存有意外险的目标校验流程,但是在重复投保限制中预置有生成意外险的目标校验流程的配置信息。
具体地,参照图2,所述基于预设配置信息生成所述目标校验流程的步骤包括:
步骤S31,解析所述配置信息,以获取所述配置信息中的险种元素,以及所述险种元素的处理逻辑框架;
在得到配置信息后,解析该配置信息,得到配置信息中的险种元素,以及险种元素的处理逻辑框架,其中,险种元素指的是时间范围、数量以及购买金额等元素,险种元素的处理逻辑框架指的是对险种元素的比对,判断,校验等处理框架,其中,该处理逻辑框架可以是完整的对险种元素进行处理的处理步骤,该处理逻辑框架也可以是需要填充才能得到完整处理步骤的构架。
步骤S32,基于所述险种元素以及所述处理逻辑框架,得到各个目标元数据;
在得到所述险种元素以及所述处理逻辑框架后,生成各个目标元数据,目标元数据即是一个校验流程,例如,该目标元数据是对时间范围进行校验的流程,或者是对数量进行校验的流程。需要说明的是,对于待校验险种来说,该各个目标元数据一般为多个。
步骤S33,基于所述配置信息获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
在配置信息中,除了险种元素,以及所述险种元素的处理逻辑框架外,还包括各个目标元数据的组合顺序,例如在配置信息中a目标元数据排列在b目标元数据之前,b排序在c目标元数据之前,基于所述配置信息获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
具体地,基于所述配置信息获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程步骤包括:
步骤S331,基于所述配置信息获取所述各个目标元数据的步骤属性;
在本实施例中,基于所述配置信息获取所述各个目标元数据的步骤属性,各个目标元数据的步骤属性可以是根据该步骤的预设顺序标识确定的,具体地,该险种元素中携带有预设顺序标识,例如,险种元素中携带有顺序标识1,则对该险种元素对应的目标元数据的步骤属性是排列在流程的首位,需要说明的是,该顺序标识可以由目标元数据携带。
步骤S332,基于所述步骤属性获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
在得到各个目标元数据的组合顺序后,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
步骤S40,基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。
在得到目标检验流程后,基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果,其中,该校验结果包括校验通过与校验未通过的结果。
本申请通过在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;判断是否预存有所述所属险种类别对应的目标校验流程;若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。在本申请中,在进行重复投保检验时,若未预存有所述所属险种类别对应的目标校验流程,则不再需要定制化开发目标校验流程,而是只需要基于信贷产品的配置信息即可自动生成对应的目标校验流程,并基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,得到校验结果即可,因而提升了校验效率,解决了定制化开发保险产品的校验流程无法适应保险业务快速发展的需要,降低了投保校验效率的技术问题。
进一步地,本申请提供重复投保限制方法的另一实施例,在该实施例中,所述基于所述险种元素以及所述处理逻辑框架,得到各个目标元数据的步骤包括:
步骤S321,获取所述处理逻辑框架对应的执行脚本;
在本实施例中,该处理逻辑框架是不完整的对险种元素进行处理的处理步骤,即该处理逻辑框架是需要填充才能得到完整处理步骤的构架,因而,获取可以对处理逻辑框架进行填充的执行脚本,该执行脚本是预存的。
步骤S322,基于所述执行脚本将所述险种元素嵌入至所述处理逻辑框架中,以生成对所述险种元素进行处理的各个处理规则;
在得到执行脚本后,将所述险种元素嵌入至所述处理逻辑框架中,以生成对所述险种元素进行处理的各个处理规则,例如,若险种M中配置信息包括时间范围,数量险种元素,将所述时间范围,数量嵌入至所述处理逻辑框架中,以生成对时间范围,数量的执行规则如对时间范围进行第一比对、对数量进行第二比对等。
步骤S323,将所述各个处理规则设置为所述各个目标元数据。
在本实施例中,在的代各个处理规则后,将各个处理规则设置为所述各个目标元数据。
在本实施例中,通过获取所述处理逻辑框架对应的执行脚本;基于所述执行脚本将所述险种元素嵌入至所述处理逻辑框架中,以生成对所述险种元素进行处理的各个处理规则;将所述各个处理规则设置为所述各个目标元数据。在本实施例中,实现灵活生成各个目标元数据,减少定制化造成的资源浪费。
进一步地,本申请提供重复投保限制方法的另一实施例,在该实施例中,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果的步骤包括:
步骤S41,基于所述生成的目标校验流程,先从所述待校验险种的信息中提取待校验的险种编码,以得到所述险种编码对应的投保保单的限制数量;
在本实施例中,具体实现重复投保校验,具体地,先从所述待校验险种的信息中提取待校验的险种编码,该险种编码可以为多个,险种编码为多个时,险种类别可以为一个也可以为多个,在得到编码后,获取得到所述险种编码对应的投保保单的限制数量,其中,每一个险种编码可以包括多个投保保单,每一个险种编码的数量是限制的。
步骤S42,判断所述待校验保单数量是否小于等于所述限制数量;
判断所述待校验保单数量是否小于等于所述限制数量,该限制数量可以为1。
步骤S43,若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息;
若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息,即是在确保数量符合要求后,再进行各个保单时间范围的校验。
步骤S44,判断所述各待校验保单对应的时间范围信息是否一致,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保。
判断所述各待校验保单对应的时间范围信息是否一致,其中,一致指的是时间范围相同,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保,若所述各待校验保单对应的时间范围信息不一致,则确定所述待校验险种重复投保,校验未通过。
进一步地,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果步骤之后,包括:
步骤S50,若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息;
在本实施例中,若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息,同时生成文本以及声音提示信息的目的在于确保校验未通过的提示等级。
步骤S60,将所述文本提示信息通过邮件发送给预设检验人员。
在生成文本以及声音提示信息后,将所述文本提示信息通过邮件发送给预设检验人员。以生成邮件记录,便于后续查询。
在本实施例中,通过基于所述生成的目标校验流程,先从所述待校验险种的信息中提取待校验的险种编码,以得到所述险种编码对应的投保保单的限制数量;判断所述待校验保单数量是否小于等于所述限制数量;若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息;判断所述各待校验保单对应的时间范围信息是否一致,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保。在本实施例中,实现有效避免重复投保,提升了保险企业效益。
参照图3,图3是本申请实施例方案涉及的硬件运行环境的设备结构示意图。
本申请实施例重复投保限制设备可以是PC,也可以是智能手机、平板电脑、电子书阅读器、MP3(Moving
Picture Experts Group Audio Layer III,动态影像专家压缩标准音频层面3)播放器、MP4(Moving Picture
Experts Group Audio Layer IV,动态影像专家压缩标准音频层面4)播放器、便携计算机等终端设备。
如图3所示,该重复投保限制设备可以包括:处理器1001,例如CPU,存储器1005,通信总线1002。其中,通信总线1002用于实现处理器1001和存储器1005之间的连接通信。存储器1005可以是高速RAM存储器,也可以是稳定的存储器(non-volatile
memory),例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储设备。
可选地,该重复投保限制设备还可以包括目标用户接口、网络接口、摄像头、RF(Radio
Frequency,射频)电路,传感器、音频电路、WiFi模块等等。目标用户接口可以包括显示屏(Display)、输入单元比如键盘(Keyboard),可选目标用户接口还可以包括标准的有线接口、无线接口。网络接口可选的可以包括标准的有线接口、无线接口(如WI-FI接口)。
本领域技术人员可以理解,图3中示出的重复投保限制设备结构并不构成对重复投保限制设备的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
如图3所示,作为一种计算机存储介质的存储器1005中可以包括操作网络通信模块以及重复投保限制可读指令。操作系统是管理和控制重复投保限制设备硬件和软件资源的程序,支持重复投保限制可读指令以及其它软件和/或程序的运行。网络通信模块用于实现存储器1005内部各组件之间的通信,以及与重复投保限制设备中其它硬件和软件之间通信。
在图3所示的重复投保限制设备中,处理器1001用于执行存储器1005中存储的重复投保限制可读指令,实现上述任一项所述的重复投保限制方法的步骤。
本申请重复投保限制设备具体实施方式与上述重复投保限制方法各实施例基本相同,在此不再赘述。
本申请还提供一种重复投保限制装置,所述重复投保限制装置包括:
检测模块10,用于在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;
判断模块20,用于判断是否预存有所述所属险种类别对应的目标校验流程;
生成模块30,用于若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;
检验模块40,用于基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。
本申请重复投保限制装置具体实施方式与上述重复投保限制方法各实施例基本相同,在此不再赘述。
本申请提供了一种可读存储介质,所述可读存储介质存储有一个或者一个以上计算机可读指令,所述一个或者一个以上计算机可读指令还可被一个或者一个以上的处理器执行以用于实现上述任一项所述的重复投保限制方法的步骤。该可读存储介质可以为非易失性可读存储介质。
本申请可读存储介质具体实施方式与上述重复投保限制方法各实施例基本相同,在此不再赘述。
以上仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换,或直接或间接运用在其他相关的技术领域,均同理包括在本申请的专利处理范围内。
Claims (20)
- 一种重复投保限制方法,其特征在于,所述重复投保限制方法包括:在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;判断是否预存有所述所属险种类别对应的目标校验流程;若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。
- 如权利要求1所述的重复投保限制方法,其特征在于,所述判断是否预存有所述所属险种类别对应的目标校验流程步骤之后,包括:若预存有所述所属险种类别对应的目标校验流程,则调用所述预存的目标校验流程,对所述待校验险种进行校验;其中,对所述待校验险种的校验包括对待校验险种的投保时间范围以及投保保单数量的校验。
- 如权利要求2所述的重复投保限制方法,其特征在于,所述基于预设配置信息生成所述目标校验流程的步骤包括:解析所述配置信息,以获取所述配置信息中的险种元素,以及所述险种元素的处理逻辑框架;基于所述险种元素以及所述处理逻辑框架,得到各个目标元数据;基于所述配置信息获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
- 如权利要求2所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果的步骤包括:基于所述生成的目标校验流程,先从所述待校验险种的信息中提取待校验的险种编码,以得到所述险种编码对应的投保待校验险种的限制数量;判断所述待校验保单数量是否小于等于所述限制数量;若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息;判断所述各待校验保单对应的时间范围信息是否一致,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保。
- 如权利要求2所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果步骤之后,包括:若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息;将所述文本提示信息通过邮件发送给预设检验人员。
- 如权利要求1所述的重复投保限制方法,其特征在于,所述基于预设配置信息生成所述目标校验流程的步骤包括:解析所述配置信息,以获取所述配置信息中的险种元素,以及所述险种元素的处理逻辑框架;基于所述险种元素以及所述处理逻辑框架,得到各个目标元数据;基于所述配置信息获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
- 如权利要求6所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果的步骤包括:基于所述生成的目标校验流程,先从所述待校验险种的信息中提取待校验的险种编码,以得到所述险种编码对应的投保待校验险种的限制数量;判断所述待校验保单数量是否小于等于所述限制数量;若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息;判断所述各待校验保单对应的时间范围信息是否一致,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保。
- 如权利要求6所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果步骤之后,包括:若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息;将所述文本提示信息通过邮件发送给预设检验人员。
- 如权利要求6所述的重复投保限制方法,其特征在于,所述基于所述配置信息获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程的步骤包括:基于所述配置信息获取所述各个目标元数据的步骤属性;基于所述步骤属性获取所述各个目标元数据的组合顺序,按照所述组合顺序对所述各个目标元数据进行组合,得到目标校验流程。
- 如权利要求9所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果的步骤包括:基于所述生成的目标校验流程,先从所述待校验险种的信息中提取待校验的险种编码,以得到所述险种编码对应的投保待校验险种的限制数量;判断所述待校验保单数量是否小于等于所述限制数量;若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息;判断所述各待校验保单对应的时间范围信息是否一致,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保。
- 如权利要求9所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果步骤之后,包括:若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息;将所述文本提示信息通过邮件发送给预设检验人员。
- 如权利要求6所述的重复投保限制方法,其特征在于,所述基于所述险种元素以及所述处理逻辑框架,得到各个目标元数据的步骤包括:获取所述处理逻辑框架对应的执行脚本;基于所述执行脚本将所述险种元素嵌入至所述处理逻辑框架中,以生成对所述险种元素进行处理的各个处理规则;将所述各个处理规则设置为所述各个目标元数据。
- 如权利要求12所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果的步骤包括:基于所述生成的目标校验流程,先从所述待校验险种的信息中提取待校验的险种编码,以得到所述险种编码对应的投保待校验险种的限制数量;判断所述待校验保单数量是否小于等于所述限制数量;若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息;判断所述各待校验保单对应的时间范围信息是否一致,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保。
- 如权利要求13所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果步骤之后,包括:若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息;将所述文本提示信息通过邮件发送给预设检验人员。
- 如权利要求1所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果的步骤包括:基于所述生成的目标校验流程,先从所述待校验险种的信息中提取待校验的险种编码,以得到所述险种编码对应的投保待校验险种的限制数量;判断所述待校验保单数量是否小于等于所述限制数量;若所述待校验保单数量小于等于所述限制数量,则从所述待校验险种的信息中获取各待校验保单对应的时间范围信息;判断所述各待校验保单对应的时间范围信息是否一致,若所述各待校验保单对应的时间范围信息一致,则确定所述待校验险种未重复投保。
- 如权利要求15所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果步骤之后,包括:若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息;将所述文本提示信息通过邮件发送给预设检验人员。
- 如权利要求1所述的重复投保限制方法,其特征在于,所述基于所述生成的目标校验流程对所述待校验险种的信息进行重复投保校验,并输出校验结果步骤之后,包括:若检测到所述校验结果为校验未通过时,生成校验未通过的文本以及声音提示信息;将所述文本提示信息通过邮件发送给预设检验人员。
- 一种重复投保限制装置,其特征在于,所述重复投保限制装置包括:检测模块,用于在检测到重复投保校验指令时,获取所述校验指令中所携带的待校验险种的信息以及待校验险种的所属险种类别;判断模块,用于判断是否预存有所述所属险种类别对应的目标校验流程;生成模块,用于若未预存有所述所属险种类别对应的目标校验流程,则基于预设配置信息创建所述目标校验流程;检验模块,用于基于所述创建的目标校验流程与所述待校验险种的信息对所述待校验险种进行重复投保校验,并输出校验结果。
- 一种重复投保限制设备,其特征在于,所述重复投保限制设备包括:存储器、处理器,通信总线以及存储在所述存储器上的重复投保限制可读指令,所述通信总线用于实现处理器与存储器间的通信连接;所述处理器用于执行所述重复投保限制可读指令,以实现如权利要求1所述的重复投保限制方法的步骤。
- 一种可读存储介质,其特征在于,所述可读存储介质上存储有重复投保限制可读指令,所述重复投保限制可读指令被处理器执行时实现如权利要求1所述的重复投保限制方法的步骤。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811424207.6 | 2018-11-27 | ||
| CN201811424207.6A CN109712000A (zh) | 2018-11-27 | 2018-11-27 | 重复投保限制方法、装置、设备及可读存储介质 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2020107591A1 true WO2020107591A1 (zh) | 2020-06-04 |
Family
ID=66255122
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2018/123189 Ceased WO2020107591A1 (zh) | 2018-11-27 | 2018-12-24 | 重复投保限制方法、装置、设备及可读存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109712000A (zh) |
| WO (1) | WO2020107591A1 (zh) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11559790B2 (en) | 2012-02-20 | 2023-01-24 | Dow Global Technologies Llc | Reconstituted dehydrogenation catalyst showing slowed activity loss when compared with fresh catalyst |
| WO2024059600A1 (en) | 2022-09-14 | 2024-03-21 | Dow Global Technologies Llc | Methods for dehydrogenating hydrocarbons utilizing regenerators |
| WO2024059553A1 (en) | 2022-09-14 | 2024-03-21 | Dow Global Technologies Llc | Methods for dehydrogenating hydrocarbons |
| WO2024059552A1 (en) | 2022-09-14 | 2024-03-21 | Dow Global Technologies Llc | Methods for dehydrogenating hydrocarbons utilizing combustion units |
| WO2024059551A1 (en) | 2022-09-14 | 2024-03-21 | Dow Global Technologies Llc | Methods for dehydrogenating hydrocarbons utilizing countercurrent flow regenerators |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111124394A (zh) * | 2019-11-26 | 2020-05-08 | 泰康保险集团股份有限公司 | 基于元数据的表单配置方法及装置、设备和介质 |
| CN117520467A (zh) * | 2020-09-21 | 2024-02-06 | 浙江网商银行股份有限公司 | 地块处理方法及装置、倒排索引更新方法及装置 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103886503A (zh) * | 2012-12-19 | 2014-06-25 | 中保保险经纪人股份有限公司 | 旅平险快速投保的装置及其方法 |
| US20150205922A1 (en) * | 2012-04-19 | 2015-07-23 | Korea Health And Welfare Information Service | Integrated management method and integrated management system for public health information, and recording medium therefor |
| CN106934480A (zh) * | 2015-12-29 | 2017-07-07 | 平安科技(深圳)有限公司 | 投保等级分析方法、服务器及终端 |
| CN108520469A (zh) * | 2018-06-19 | 2018-09-11 | 南京新贝金服科技有限公司 | 一种基于电商平台的用户重购行为分析方法 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107038575A (zh) * | 2016-08-26 | 2017-08-11 | 平安科技(深圳)有限公司 | 保险费用支付方法和装置 |
| CN108510396B (zh) * | 2017-06-23 | 2020-12-29 | 平安科技(深圳)有限公司 | 投保校验的方法、装置、计算机设备及存储介质 |
| CN108428184A (zh) * | 2017-12-01 | 2018-08-21 | 中国平安财产保险股份有限公司 | 一种保险投保时的资料处理方法、存储介质和服务器 |
| CN108460688A (zh) * | 2018-01-08 | 2018-08-28 | 平安科技(深圳)有限公司 | 核保校验的方法、装置、存储介质及终端 |
-
2018
- 2018-11-27 CN CN201811424207.6A patent/CN109712000A/zh active Pending
- 2018-12-24 WO PCT/CN2018/123189 patent/WO2020107591A1/zh not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150205922A1 (en) * | 2012-04-19 | 2015-07-23 | Korea Health And Welfare Information Service | Integrated management method and integrated management system for public health information, and recording medium therefor |
| CN103886503A (zh) * | 2012-12-19 | 2014-06-25 | 中保保险经纪人股份有限公司 | 旅平险快速投保的装置及其方法 |
| CN106934480A (zh) * | 2015-12-29 | 2017-07-07 | 平安科技(深圳)有限公司 | 投保等级分析方法、服务器及终端 |
| CN108520469A (zh) * | 2018-06-19 | 2018-09-11 | 南京新贝金服科技有限公司 | 一种基于电商平台的用户重购行为分析方法 |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11559790B2 (en) | 2012-02-20 | 2023-01-24 | Dow Global Technologies Llc | Reconstituted dehydrogenation catalyst showing slowed activity loss when compared with fresh catalyst |
| US11951455B2 (en) | 2012-02-20 | 2024-04-09 | Dow Global Technologies Llc | Reconstituted dehydrogenation catalyst showing slowed activity loss when compared with fresh catalyst |
| WO2024059600A1 (en) | 2022-09-14 | 2024-03-21 | Dow Global Technologies Llc | Methods for dehydrogenating hydrocarbons utilizing regenerators |
| WO2024059553A1 (en) | 2022-09-14 | 2024-03-21 | Dow Global Technologies Llc | Methods for dehydrogenating hydrocarbons |
| WO2024059552A1 (en) | 2022-09-14 | 2024-03-21 | Dow Global Technologies Llc | Methods for dehydrogenating hydrocarbons utilizing combustion units |
| WO2024059551A1 (en) | 2022-09-14 | 2024-03-21 | Dow Global Technologies Llc | Methods for dehydrogenating hydrocarbons utilizing countercurrent flow regenerators |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109712000A (zh) | 2019-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020107591A1 (zh) | 重复投保限制方法、装置、设备及可读存储介质 | |
| WO2020087981A1 (zh) | 风控审核模型生成方法、装置、设备及可读存储介质 | |
| WO2020147385A1 (zh) | 数据录入方法、装置、终端及计算机可读存储介质 | |
| WO2020119115A1 (zh) | 数据审核方法、装置、设备及存储介质 | |
| WO2020119369A1 (zh) | 智能it运维故障定位方法、装置、设备及可读存储介质 | |
| WO2020253135A1 (zh) | 自动化分析方法、用户设备、存储介质及装置 | |
| WO2020015067A1 (zh) | 数据采集方法、装置、设备及存储介质 | |
| WO2021003956A1 (zh) | 产品信息的管理方法、装置、设备及存储介质 | |
| WO2020253034A1 (zh) | 客户端埋点测试方法、装置、设备及存储介质 | |
| WO2020015064A1 (zh) | 系统故障处理方法、装置、设备及存储介质 | |
| WO2019037196A1 (zh) | 任务分配方法、装置及计算机可读存储介质 | |
| WO2021027143A1 (zh) | 信息推送方法、装置、设备及计算机可读存储介质 | |
| WO2020107761A1 (zh) | 广告文案处理方法、装置、设备及计算机可读存储介质 | |
| WO2020006852A1 (zh) | 差旅费自助核销处理方法、装置、设备和计算机存储介质 | |
| WO2020224246A1 (zh) | 基于区块链的数据管理方法、装置、设备和存储介质 | |
| WO2020015060A1 (zh) | 用电量异常评估方法、装置、设备和计算机存储介质 | |
| WO2020103275A1 (zh) | 扣款控制方法、装置、设备及可读存储介质 | |
| WO2020098075A1 (zh) | 金融数据处理方法、装置、设备和存储介质 | |
| WO2019174090A1 (zh) | 截屏文件分享的控制方法、装置、设备和计算机存储介质 | |
| WO2020062658A1 (zh) | 合同生成方法、装置、设备及存储介质 | |
| WO2020119069A1 (zh) | 基于自编码神经网络的文本生成方法、装置、终端及介质 | |
| WO2020233057A1 (zh) | 文件打包方法、装置、设备及存储介质 | |
| WO2020119117A1 (zh) | 分布式计算方法、装置、系统、设备及可读存储介质 | |
| WO2021027134A1 (zh) | 数据存储方法、装置、设备和计算机存储介质 | |
| WO2019024485A1 (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: 18941830 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 18941830 Country of ref document: EP Kind code of ref document: A1 |