Insurance business automatic real-time processing design method based on event architecture and medium

Abstract

The invention relates to an insurance service automatic real-time processing design method based on an event architecture and a medium. The method comprises the following steps: constructing an insurance service entity, and defining insurance service events and event priorities; the controller is used for designing event-related objects based on the insurance service entities, the insurance service events and the event priorities so as to record changes of the insurance service entities and create the insurance service events through the event-related objects; and based on the event related object, designing an insurance service event, and executing one or more automatic processing flows of event application, event restoration, event reapplication and event cancellation through the control of a controller, so that the insurance service event is processed according to an event priority sequence, and the design process is completed. Compared with the prior art, the method has the advantages that the accuracy and the real-time performance of the insurance service are improved, and the like.

Description

Technical Field

[0001] The present invention relates to the technical field of insurance business, and in particular to a design method and medium for automatic real-time processing of insurance business based on event architecture. Background Art

[0002] Insurance companies provide a variety of security services, many of which are handled in a sequence that often affects the accuracy of calculations of premiums, benefits, and claims payable by customers. In order to protect the rights and interests of customers, insurance companies must ensure that these services are handled in a predetermined order. However, due to the long life cycle of insurance policies, the number of historical services handled is large and complex. Currently, most insurance companies conduct a pre-check before handling services, and check the services that need to be rolled back according to the type of services currently being handled and the effective date. If there is a blockage in the current service, it is necessary to manually determine whether to roll back the historical change records, and then handle the current service after rolling back through manual operations or operation and maintenance means. After completing the current service, redo the rolled back changes. This technical solution is difficult to meet the requirements of accuracy and real-time processing of insurance services. Summary of the invention

[0003] The purpose of the present invention is to provide a design method and medium for automatic real-time processing of insurance business based on an event architecture, which can improve the accuracy and real-time performance of fully automatic processing of insurance business.

[0004] The purpose of the present invention can be achieved by the following technical solutions:

[0005] A design method for automatic real-time processing of insurance business based on event architecture includes the following steps:

[0006] Construct insurance business entities, define insurance business events and event priorities;

[0007] Based on the insurance business entity, the insurance business event and the event priority, an event-related object is designed to record changes of the insurance business entity through the event-related object and to create a controller for the insurance business event;

[0008] Based on the event-related objects, the insurance business event is designed to execute one or more automatic processing procedures of event application, event restoration, event reapplication, and event cancellation through the control of the controller, so that the insurance business event is processed in the order of event priority to complete the design process.

[0009] Furthermore, the insurance business entity includes a policy entity, a personal customer entity, and an account entity.

[0010] Furthermore, each creation and update of the insurance business entity is defined as the insurance business event, and the insurance business events include policy creation / update, policy premium application, customer gender / age / occupation change, customer address / email creation / update, account deposit, and account withdrawal.

[0011] Furthermore, the event priority is defined by evaluating the mutual impact of the order in which all insurance business events occur, to ensure that insurance business events with the same effective date execute first the insurance business event with a higher priority, and that insurance business events with different effective dates execute first the insurance business event with an earlier effective date.

[0012] Furthermore, the event-related objects include:

[0013] (1) Event object: used to record information about changes to a type of insurance business entity;

[0014] The attributes of the event object include event type, primary insurance business entity object, secondary insurance business entity object, parent event, restored event, event activity, effective date, effective deadline, priority, processing date / time, processor, and whether restored;

[0015] (2) Event activity object: used to record the status of a type of insurance business entity before and after the change;

[0016] The attributes of the event activity object include the effective date, processing date / time, class of the insurance business entity object, insurance business entity object, whether it has been restored, restoration date, and new and old values ​​before and after the change;

[0017] (3) Event controller object: used to create a controller for each insurance business event to control the execution of the corresponding insurance business event;

[0018] The attributes of the controller object include processing mode, input parameter list, output parameter list, event activity class, primary insurance business entity object, secondary insurance business entity object, event object, event activity object, event being restored / reapplied, parent controller, execution result, and execution result detailed information.

[0019] Furthermore, the processing modes of the controller object include event application, event restoration, event reapplication and event cancellation, wherein the event application refers to the change processing of the insurance business entity, the event restoration refers to restoring the insurance business entity change that has occurred to the state before the change, the event reapplication refers to re-changing the event after restoration, and the event cancellation refers to rolling back the event.

[0020] Furthermore, the automatic processing flow includes the following steps:

[0021] 1) The processing mode of the controller is set to event application;

[0022] 2) Confirm the status, check whether the insurance business entity is allowed to be changed according to the pre-collected business rules, if yes, execute the next step, if no, stop processing, output the execution result and detailed information of the execution result;

[0023] 3) Confirm the input and check whether the input parameter list meets the change conditions. If so, execute the next step. If not, stop processing and output the execution result and detailed information of the execution result;

[0024] 4) Confirm the event, search for all insurance business events that have been processed by the main insurance business entity and have an effective date greater than the insurance business event currently being processed, as well as all insurance business events that have an effective date on the same day as the current insurance business event and have a lower priority than the current insurance business event, and merge them into a candidate restoration event list, wherein the candidate restoration event list consists of insurance business events that cannot be automatically restored and insurance business events that can be automatically restored. For insurance business events that cannot be automatically restored, stop processing and prompt that they cannot be automatically restored, and the event needs to be canceled before the current insurance business event;

[0025] 5) Determine whether there is an insurance business event that needs to be restored and can be automatically restored. If so, perform event restoration processing; if not, do not perform event restoration processing;

[0026] 6) Execute the event application, and complete the change processing through the insurance business entity behavior according to the insurance business entity change content in the input parameter list;

[0027] 7) Perform event reapplication processing on all the insurance business events that have been restored in step 5) to complete the automatic processing process.

[0028] Furthermore, the event restoration process in step 5) includes:

[0029] The candidate restoration event list is restored one by one in descending order of occurrence time, and the event restoration mode of the controller is adopted. The event object and the event being restored are input. The controller obtains the old value of the event activity object before the change through the event being restored to restore the state of the insurance business entity object before the change, thereby completing the event restoration processing, wherein the event object is the current application event, and the event being restored is a candidate restoration event.

[0030] Furthermore, the event reapplication processing step in step 7) includes:

[0031] The candidate restoration event list is processed for event reapplication one by one in ascending order of occurrence time, and the event reapplication processing mode of the controller is adopted. The event object and the event being restored are input. The controller obtains the new value of the event activity object after the change through the event being reapplied to re-update the insurance business entity object state, and completes the event reapplication processing process, wherein the event object is the current application event, and the event being restored is the candidate restoration event.

[0032] The present invention also provides a computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device, wherein the one or more programs include instructions for executing the method for designing automatic real-time processing of insurance business based on event architecture as described above.

[0033] Compared with the prior art, the present invention has the following beneficial effects:

[0034] (1) The present invention classifies insurance business events into different priorities, designs event-related objects to record entity changes and create controllers, and then designs automatic processing procedures for event application, event restoration, and event reapplication to ensure that events controlled by the controller are processed according to the set priority. This not only provides a set of standardized event automatic processing procedures for insurance business event processing, but also ensures that all insurance business events occur in a predefined order, thereby improving the accuracy and real-time performance of insurance business processing.

[0035] (2) The present invention creates a controller for each event, so that the execution of each event is controlled by a separate controller, and the controller attributes contain multiple processing modes, which can ensure that the controller processes according to the set processing flow, further improving the accuracy and real-time performance of insurance business processing.

[0036] (3) The present invention adopts an automatic processing flow of event application, event restoration and event reapplication, which clearly records the operation traces and specific content of changes such as changes, rollbacks and re-changes, and also meets the audit requirements of the financial industry.

[0037] (4) The present invention can simply add event types and controllers, maintain the priority of related events and the list of events that can be automatically rolled back, etc., so it has good scalability and simple implementation, and effectively reduces operation and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a schematic diagram of the method flow of the present invention;

[0039] Figure 2 The present invention is an implementation application flow chart. DETAILED DESCRIPTION

[0040] The present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. This embodiment is implemented based on the technical solution of the present invention, and provides a detailed implementation method and specific operation process, but the protection scope of the present invention is not limited to the following embodiments.

[0041] This embodiment provides a design method for automatic real-time processing of insurance business based on event architecture. The method divides business events into different priorities, and provides a set of standardized automatic event processing processes through event application, restoration and re-application, so as to ensure that all insurance business occurs in a predefined order. This order is based on the effective date and priority of the event. If two events have different effective dates, the earlier event must always be executed before the later event; at the same effective date, the pre-defined event priority in the system will ensure that the event with the higher priority is executed first, which maximizes the insurance company's requirements for the accuracy and real-time nature of business processing. Figure 1 As shown, this method can be implemented as follows:

[0042] 1. Identify the insurance business entity

[0043] First, identify the entities that appear in the insurance business, common ones include policy entities, individual customer entities, account entities, etc.

[0044] 2. Define insurance business events

[0045] Every creation and update of an insurance business entity can be defined as a business event. Insurance business events usually include policy creation / update, policy premium application, customer gender / age / occupation change, customer address / email creation / update, account deposit, account withdrawal and other events.

[0046] 3. Define incident priorities

[0047] Evaluate the mutual impact of the order of occurrence of all business events, and uniformly define priorities to ensure that events with the same effective date are executed first with higher priority events. Prepare an event priority list, which can include event type, event name, and priority level. Special case processing: The processing result of this event is not affected by any other event, and the event priority is recorded as 99999; this event cannot be automatically rolled back by the system under any circumstances, and the event priority is recorded as 0.

[0048] 4. Event-related object design

[0049] 4.1 Event objects, which can be persisted, are used to record the main information of a class of entity changes

[0050] The attributes include event type, primary business entity object, secondary business entity object, parent event, restored event, event activity, effective date, effective deadline, priority, processing date / time, processor, and whether it has been restored.

[0051] 4.2 Event activity objects, which can be persisted and used to record detailed information about the state before and after the entity changes

[0052] The attributes include the effective date, processing date / time, class of the business entity object, business entity object, whether it has been restored, restoration date, and the old and new values ​​before and after the change.

[0053] 4.3 The controller object of the event is a non-persistent object used to control the execution of this event. An event controller is created for each event.

[0054] The properties include processing mode (apply, restore, reapply, cancel), input parameter list, output parameter list, event activity class, primary business entity object, secondary business entity object, event object, event activity object, event being restored / reapplied, parent controller, execution result (normal, error), execution result details, etc.

[0055] Controller behaviors include event application, restoration, and reapplication. Event application refers to the processing of entity changes. Event restoration refers to restoring entity changes that have occurred to the state before the change. Event reapplication refers to making changes again after event restoration.

[0056] 5. Ensure that business events are processed in order of priority

[0057] The main reasons for requiring recovery after an entity change are: incorrect information during change processing, changes were processed when they should not have been processed, and the insured changed his mind and requested recovery of the status before the change.

[0058] Scenarios for applying after restore: When applying an event, if another low-priority event has occurred on the same day as the effective date of the current event, you need to restore the low-priority event first, apply the current event, and then reapply the low-priority event. When applying an event, if there is an event that has occurred (with a different effective date) and its effective date is greater than the effective date of the current event, and the event result is affected by the current event, you need to restore and then apply.

[0059] The order in which events occur will affect the outcome of the events. Business personnel need to identify this in advance and record it in the automatic restoration event list. Those that have no impact can be recorded in the automatic restoration exception event list for the event, so that the controller can automatically filter the events that have occurred that can be automatically restored, and prompt for manual processing when the controller automatically determines that the event that has occurred is not in the above two lists.

[0060] The overall processing flow is shown in Figure 2 , each step is described as follows:

[0061] 5.1 The process of automatically executing the restoration and then applying the event application through the controller is as follows:

[0062] Step 1): Set the controller processing mode to "Application"

[0063] Step 2): Confirm the status. Verify the policy status and other information for the business entity according to the pre-collected business rules to see if the change is allowed. If not, stop processing and display the "execution result" and "execution result details".

[0064] Step 3): Confirm the input and check whether the data in the "Parameter List" meets the conditions for this change. If not, stop processing and prompt "Execution Result" and "Execution Result Details".

[0065] Step 4): Confirm the event. First, find the event that has been processed by the main business entity and has an effective date greater than the event currently being processed. Secondly, find all events that are effective on the same date as the current event and have a lower priority than the current event. The events found twice are combined into a candidate restoration event list, and then this list is divided into two parts. The first part consists of events that cannot be automatically restored, and the second part is a list of events that can be automatically restored. If there are any events that cannot be automatically restored, stop processing and prompt the event that cannot be automatically restored, indicating that the user must manually cancel the event before trying the current event.

[0066] Step 5): If there are events that need to be restored and they can be restored automatically, then the event restoration process is performed.

[0067] Step 6): Execute the application event, complete the change processing through entity behavior according to the entity change content in the input parameter list, and retain the event and event activity related information.

[0068] Step 7): Re-apply all events restored in step 5).

[0069] 5.2 The controller automatically performs event restoration, and the processing flow is as follows:

[0070] The candidate restoration event list is restored one by one in descending order of event occurrence time. The controller automatic restoration mode is used to input the event object (current application event) and the event being restored (candidate restoration event). The controller obtains the old value of the event activity object before the change through the event being restored to restore the state of the business entity object before the change. Retain information related to events and event activities, and record restoration events.

[0071] 5.3 The controller automatically executes the event reapplication, and the processing flow is as follows:

[0072] The candidate restoration event list is reapplied one by one in ascending order of event occurrence time. The controller is in automatic reapplication mode. The event object (current application event) and the event being reapplied (candidate restoration event) are input. The controller obtains the changed new value of the event activity object through the event being reapplied to re-update the state of the business entity object. Information related to events and event activities is retained, and restoration events are recorded.

[0073] Examples of practical applications:

[0074] (1) The renewal premium payable record of insurance business is usually generated 60 days before the premium starts. If the insured person changes his / her occupation on the day when the renewal premium payable record is generated, and if this affects the renewal premium amount of this period and subsequent periods, the renewal premium payable needs to be recalculated, and the renewal premium payable generation event should be restored before application.

[0075] (2) During the insurance claims process, if an accident occurs that warrants a premium exemption, the premiums after the accident should be exempted. However, if the premiums to be exempted have been paid and taken effect before the claims are settled, the premiums used should be cancelled and the event rolled back through the event cancellation mode.

[0076] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., which can store program code.

[0077] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. The schemes in the embodiments of the present invention may be implemented in various computer languages, for example, object-oriented programming language Java and literal scripting language JavaScript, etc.

[0078] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0079] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0080] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0081] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0082] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A design method for automatic real-time processing of insurance business based on event architecture, characterized in that: The following steps are involved: Construct insurance business entities, define insurance business events and event priorities; Based on the insurance business entity, the insurance business event and the event priority, an event-related object is designed to record changes of the insurance business entity through the event-related object and to create a controller for the insurance business event; Based on the event-related objects, the insurance business event is designed to execute one or more automatic processing procedures of event application, event restoration, event reapplication, and event cancellation through the control of the controller, so that the insurance business event is processed in the order of event priority to complete the design process.

2. According to claim 1, a method for designing automatic real-time processing of insurance business based on event architecture is characterized in that: The insurance business entities include policy entities, individual customer entities, and account entities.

3. The method for designing automatic real-time insurance business processing based on event architecture according to claim 1, characterized in that: Each creation and update of the insurance business entity is defined as the insurance business event, and the insurance business events include policy creation / update, policy premium application, customer gender / age / occupation change, customer address / email creation / update, account deposit, and account withdrawal.

4. The method for designing automatic real-time insurance business processing based on event architecture according to claim 1, characterized in that: The event priority is defined by evaluating the mutual impact of the order in which all insurance business events occur, to ensure that insurance business events with the same effective date execute first the insurance business event with a higher priority, and insurance business events with different effective dates execute first the insurance business event with an earlier effective date.

5. The method for designing automatic real-time insurance business processing based on event architecture according to claim 1, characterized in that: The event-related objects include: (1) Event object: used to record information about changes to a type of insurance business entity; The attributes of the event object include event type, primary insurance business entity object, secondary insurance business entity object, parent event, restored event, event activity, effective date, effective deadline, priority, processing date / time, processor, and whether restored; (2) Event activity object: used to record the status of a type of insurance business entity before and after the change; The attributes of the event activity object include the effective date, processing date / time, class of the insurance business entity object, insurance business entity object, whether it has been restored, restoration date, and new and old values ​​before and after the change; (3) Event controller object: used to create a controller for each insurance business event to control the execution of the corresponding insurance business event; The attributes of the controller object include processing mode, input parameter list, output parameter list, event activity class, primary insurance business entity object, secondary insurance business entity object, event object, event activity object, event being restored / reapplied, parent controller, execution result, and execution result detailed information.

6. The method for designing automatic real-time insurance business processing based on event architecture according to claim 5, characterized in that: The processing modes of the controller object include event application, event restoration, event reapplication and event cancellation, wherein the event application refers to the change processing of the insurance business entity, the event restoration refers to the restoration of the insurance business entity change that has occurred to the state before the change, the event reapplication refers to re-changing the event after restoration, and the event cancellation refers to rolling back the event.

7. The method for designing automatic real-time insurance business processing based on event architecture according to claim 6, characterized in that: The automatic processing flow includes the following steps: 1) The processing mode of the controller is set to event application; 2) Confirm the status, check whether the insurance business entity is allowed to be changed according to the pre-collected business rules, if yes, execute the next step, if no, stop processing, output the execution result and detailed information of the execution result; 3) Confirm the input and check whether the input parameter list meets the change conditions. If so, execute the next step. If not, stop processing and output the execution result and detailed information of the execution result; 4) Confirm the event, search for all insurance business events that have been processed by the main insurance business entity and have an effective date greater than the insurance business event currently being processed, as well as all insurance business events that have an effective date on the same day as the current insurance business event and have a lower priority than the current insurance business event, and merge them into a candidate restoration event list, wherein the candidate restoration event list consists of insurance business events that cannot be automatically restored and insurance business events that can be automatically restored. For insurance business events that cannot be automatically restored, stop processing and prompt that they cannot be automatically restored, and the event needs to be canceled before the current insurance business event; 5) Determine whether there is an insurance business event that needs to be restored and can be automatically restored. If so, perform event restoration processing; if not, do not perform event restoration processing; 6) Execute the event application, and complete the change processing through the insurance business entity behavior according to the insurance business entity change content in the input parameter list; 7) Perform event reapplication processing on all the insurance business events that have been restored in step 5) to complete the automatic processing process.

8. The method for designing automatic real-time insurance business processing based on event architecture according to claim 7, characterized in that: The event restoration process in step 5) includes: The candidate restoration event list is restored one by one in descending order of occurrence time, and the event restoration mode of the controller is adopted. The event object and the event being restored are input. The controller obtains the old value of the event activity object before the change through the event being restored to restore the state of the insurance business entity object before the change, thereby completing the event restoration processing, wherein the event object is the current application event, and the event being restored is a candidate restoration event.

9. The method for designing automatic real-time insurance business processing based on event architecture according to claim 7, characterized in that: The event reapplication processing step in step 7) includes: The candidate restoration event list is processed for event reapplication one by one in ascending order of occurrence time, and the event reapplication processing mode of the controller is adopted. The event object and the event being restored are input. The controller obtains the new value of the event activity object after the change through the event being reapplied to re-update the insurance business entity object state, and completes the event reapplication processing process, wherein the event object is the current application event, and the event being restored is the candidate restoration event.

10. A computer-readable storage medium, characterized in that: It comprises one or more programs for execution by one or more processors of an electronic device, wherein the one or more programs comprise instructions for executing a method for designing automatic real-time processing of insurance business based on an event architecture as described in any one of claims 1-9.

Images