WO2020108051A1

WO2020108051A1 - Insurance transaction processing method and device

Info

Publication number: WO2020108051A1
Application number: PCT/CN2019/107675
Authority: WO
Inventors: 吴鹃; 王琪; 袁自诚
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2018-11-27
Filing date: 2019-09-25
Publication date: 2020-06-04
Also published as: TW202032483A; CN110009507A; TWI725527B

Abstract

Provided are an insurance transaction processing method and device, the method comprises: according to the insurance type of a target insurance transaction, determining a policy generation strategy corresponding to the insurance type (S101), the policy generation strategy comprising a policy dimension adopted when the insurance type generates a policy; according to the policy generation strategy, checking whether a policy of the insurance type exists under the policy dimension (S102); under the condition that the policy does not exist, generating the policy of the insurance type under the policy dimension (S103), and generating a management rule of the policy according to the transaction information of the target insurance transaction; under the condition that the policy exists, updating the management rule of the policy according to the transaction information of the target insurance transaction (S104), so as to manage the target insurance transaction through the policy.

Description

Insurance transaction processing method and device

Technical field

The embodiments of the present specification relate to the field of Internet application technologies, and in particular, to an insurance transaction processing method and device.

Background technique

The continuous advancement of high and new technology has promoted financial innovation while promoting economic development. Internet finance is becoming more and more perfect, and users can realize online purchases and sales of commodities, financing investments, loans, etc. that could only be done offline. Correspondingly, insurance companies have also developed more insurance for Internet scenarios, such as order insurance for sellers, freight insurance for buyers, insurance for investors, etc., to help users avoid uncertainties in online transactions The new risks brought by sex protect the interests of users during online transactions.

The management of Internet insurance in the prior art generally still uses the traditional insurance management method, such as creating one insurance policy for each insurance transaction, and each insurance policy has an independent process of insurance, payment, and claims. However, Internet insurance generally has the characteristics of fragmentation, low premium, and high transaction frequency. It is different from traditional insurance. Taking order insurance as an example, if an e-commerce trading platform generates hundreds of millions of sales transactions every year, it may generate hundreds of millions of orders As a result, hundreds of millions of insurance policies are generated by insurance transactions. This surge in the number of policies and fragmentation will consume more manpower and physical management, and the management efficiency is relatively low.

Summary of the invention

In response to the above technical problems, the embodiments of the present specification provide an insurance transaction processing method and device. The technical solution is as follows:

An insurance transaction processing method, the method includes:

Determine the policy generation strategy corresponding to the insurance type according to the insurance type of the target insurance transaction, the policy generation strategy includes: the policy dimension adopted when the insurance type generates the policy;

According to the policy generation strategy, check whether the policy of the insurance type already exists under the policy dimension;

In the absence of a policy, the policy of the insurance type is generated under the policy dimension, and the management rules of the policy are generated according to the transaction information of the target insurance transaction;

In the case of an existing policy, update the management rules of the policy according to the transaction information of the target insurance transaction to manage the target insurance transaction through the policy;

Among them, the management rules are used to manage each insurance transaction corresponding to the policy.

An insurance transaction processing device, including:

The strategy determination module is used to determine the policy generation strategy corresponding to the insurance type according to the insurance type of the target insurance transaction. The policy generation strategy includes: the policy dimension adopted when the insurance type generates the policy;

A policy inspection module, configured to check whether a policy of the insurance type already exists in the policy dimension according to the policy generation strategy;

The policy generation module is used to generate a policy of the insurance type in the policy dimension in the absence of a policy, and generate the management rules of the policy according to the transaction information of the target insurance transaction;

The rule update module is used to update the management rules of the policy according to the transaction information of the target insurance transaction under the condition that the policy already exists, so as to manage the target insurance transaction through the policy;

The technical solution provided by the embodiment of this specification no longer adopts the traditional way of creating one insurance policy for one insurance order, but sets different strategies for different types of insurance. The strategy includes the dimension of generating insurance policies, such as the dimension of order insurance It can be a "seller", that is, one seller only generates one policy. The order insurance corresponding to all transactions of the seller is included in the policy, and the order insurance under the policy can be uniformly managed for payment and claims, so as to achieve The purpose of reducing the number of policies is to improve the efficiency of policy management and the user experience of policyholders.

It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the embodiments of the present specification.

In addition, any of the embodiments of the present specification does not need to achieve all the above-mentioned effects.

BRIEF DESCRIPTION

In order to more clearly explain the embodiments of the specification or the technical solutions in the prior art, the following will briefly introduce the drawings required in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only These are some of the embodiments described in the embodiments of this specification, and those of ordinary skill in the art can also obtain other drawings based on these drawings.

FIG. 1 is a schematic flowchart of an insurance transaction processing method according to an embodiment of this specification;

2 is a schematic diagram of the management structure of order insurance transactions and insurance policies according to an embodiment of the present specification;

3 is a schematic structural diagram of an insurance transaction processing device according to an embodiment of this specification;

4 is a schematic structural diagram of a rule update module according to an embodiment of this specification;

5 is a schematic structural diagram of a policy generation module according to an embodiment of this specification;

6 is a schematic structural diagram of a device for configuring an apparatus of an embodiment of this specification.

detailed description

In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail in conjunction with the drawings in the embodiments of the present specification. Obviously, the described implementation Examples are only a part of the embodiments of this specification, but not all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art should fall within the scope of protection.

In view of the problems of the prior art, the embodiments of the present specification provide an insurance transaction processing method. Referring to FIG. 1, the method may include the following steps:

S101. Determine a policy generation strategy corresponding to the insurance type according to the insurance type of the target insurance transaction. The policy generation strategy includes: the policy dimension adopted when the insurance type generates a policy;

When a user purchases insurance, he will first need to conclude a transaction with an insurance institution, and then sign an insurance contract to form a corresponding insurance policy. In the insurance scenario, the same user (insured) can conclude multiple transactions with the same insurance institution.

Taking material insurance as an example, the material insurance is paid by the seller, and the buyer enjoys the insurance of the compensation rights. Once the seller chooses to join the insurance, it will insure every commodity order within the scope of coverage in the store. For example, the seller is the store Several types of commodities are covered by material insurance, and each time an order for related commodities is generated, the seller will enter into a material insurance transaction with the insurance institution.

In the traditional insurance management scheme, one insurance policy is created for each insurance transaction, and each insurance policy has an independent process of insurance, payment, and settlement. However, Internet insurance generally has the characteristics of fragmentation, low premium, and high transaction frequency, which are different from traditional insurance.

Taking the material insurance as an example, the seller may generate dozens or even hundreds of commodity orders every day, and the corresponding will reach hundreds of material insurance transactions with the insurance company. According to the traditional insurance management plan, hundreds of insurance policies will be created , And separately carry out insurance, payment, claims and other processes, resulting in low management efficiency.

In the solution provided by the embodiment of this specification, different policy dimensions are set for different types of insurance. When one insurance transaction is reached, the policy is generated from the corresponding policy dimension according to the insurance type of the insurance transaction, thereby generating 1 based on several insurance transactions Policies to improve the efficiency of policy management.

For example, the policy dimension may be the user dimension. Understandably, users can refer to natural persons, enterprises, institutions, etc. In addition, they can refer to policyholders, insured persons, beneficiaries, etc., which are not limited in this specification. Taking order insurance as an example, the policy dimension of the insurance type can be the seller dimension, that is, each order insurance transaction of the same seller corresponds to the generation of an order insurance policy, so that the seller’s multiple order insurances are managed uniformly according to one policy Transaction payment, claim settlement and other processes.

For another example, the policy dimension may be the time dimension. Taking freight insurance as an example, an e-commerce platform insures freight insurance for buyers shopping on the platform, that is, for every shopping order generated, one freight insurance transaction is reached, and the platform may generate tens of thousands of shopping orders every day. Therefore, one insurance policy can be generated corresponding to the daily freight insurance transactions in the time dimension, so as to uniformly manage the payment and settlement processes of multiple freight insurance transactions for each buyer according to one policy.

As another example, the policy dimension can also be the dimension of the participating project. For example, a mutual insurance project initiated by a platform and an insurance agency can have multiple people participating in multiple days, that is, for each user who participates in the project, a total of 1 Mutual assistance insurance transactions, so in the project dimension, several mutual insurance insurance transactions in a mutual insurance insurance project correspondingly generate a policy, so as to uniformly manage the payment and settlement processes of multiple mutual insurance transactions for each user according to one policy .

S102, according to the policy generation strategy, check whether a policy of the insurance type already exists in the policy dimension;

As mentioned above, several insurance transactions in the same dimension will correspondingly generate 1 policy, so first of all, you need to check whether a policy has been generated in this dimension.

Still taking the order insurance as an example, when a seller generates a purchase order, it corresponds to an order insurance transaction, and determines that the policy generation strategy of the order insurance is that the policy dimension is the seller dimension, you can check whether the seller already exists Order insurance policy.

S103, in the absence of an insurance policy, generate an insurance policy of the insurance type under the insurance policy dimension, and generate a management rule of the insurance policy based on the transaction information of the target insurance transaction;

The management rules are used to manage each insurance transaction corresponding to the policy. In a specific implementation manner of this specification, the policy generation strategy may further include: management of each insurance transaction corresponding to the policy generated by the insurance type Dimension.

In one example, when the policy of the insurance type is generated under the policy dimension, and the management rules of the policy are generated based on the transaction information of the target insurance transaction, the insurance type’s insurance type may be generated first under the policy dimension Policy, and determine the management dimension of the target insurance transaction according to the policy generation strategy. Then, according to the determined management dimension, a management group corresponding to the generated policy is created, the management group includes the target insurance transaction, and the management group rules of the management group are generated according to the transaction information of the target insurance transaction. The policy management rules include the management group rules.

The specific content of the management dimension is not limited in the embodiments of the present specification, and those skilled in the art can flexibly set the policy dimension and management dimension according to actual needs.

Still taking the order insurance as an example, the policy dimension of the order insurance can be set as the user dimension, and the management dimension can be set as the time dimension. Specifically, the daily order insurance transactions can be grouped into the same management group, and the seller’s One insurance policy is generated for each order insurance transaction under each management group.

The policy management rules include the management rules of each management group, and each order insurance transaction in the same management group is managed by the management group rules of the group, such as the time and date of payment. In addition, the management rules may also include other rules for further management of each order insurance transaction, such as managing whether the seller's order insurance policy is expired and renewed.

S104: In the case where an insurance policy already exists, update the management rules of the insurance policy based on the transaction information of the target insurance transaction to manage the target insurance transaction through the insurance policy;

In a specific embodiment of the present specification, when the management rules of the policy are updated according to the transaction information of the target insurance transaction to manage the target insurance transaction through the policy, the policy may first be generated based on the policy Strategy, determine the management dimension of the target insurance transaction, and check whether the policy has a corresponding management group under the determined management dimension.

When there is a management group, add the target insurance transaction to the management group, and update the management group rules of the management group according to the transaction information of the target insurance transaction;

For example, the management group rules can include the payment amount and payment date of each insurance transaction under the management group. When updating the management group rules, you can add the transaction ID and payment amount of the target insurance transaction to the management group rules In order to generate a payment reminder when payment is required, or automatically pay for the insurance transaction, etc.

In the absence of a management group, a management group corresponding to the policy is created under the management dimension, and a management group rule for the management group is generated based on the transaction information of the target insurance transaction.

In another specific embodiment of this specification, the management rules may include one or more of the following sub-rules: payment sub-rules, the payment sub-rules are used to: determine the payment time of the managed insurance transaction And payment amount; Term Sub-rule, the Term Sub-rule is used to: determine whether the managed insurance transaction expires and/or renews; Public Sub-rule, the public sub-rule is used to: publicize Management information of the managed insurance transaction, where the management information includes: payment information, claim information warranty period information, and/or user credit information.

It can be understood that, if the management rule further includes a management group rule, the management group rule may also include one or more of the foregoing sub-rules.

For example, the policy generation strategy of insurance type A does not include the management dimension, that is, each insurance transaction under the policy does not need to be divided into management groups, and the management rules of the policy can include payment sub-rules, tenure sub-rules, and public sub-rules One or more of them.

The policy generation strategy of insurance category B includes a management dimension, that is, each insurance transaction under the policy is divided into several management groups according to the management dimension, and each is managed according to the management group rules of the management group. One or more of the payment sub-rules, tenure sub-rules and publicity sub-rules; or the management rules can directly include one or more of the payment sub-rules, tenure sub-rules and publicity sub-rules; of course, also The management rule may include a public sub-rule, while the management group rule includes a payment sub-rule and a warranty sub-rule; and so on, and this embodiment of the present specification does not limit this.

The following describes the insurance transaction processing method provided in this specification in conjunction with a few more specific examples.

(1) Assuming that the insurance type of the target insurance transaction A is order insurance, in determining the policy generation strategy corresponding to the order insurance, the policy dimension adopted when generating the policy is the seller dimension. In addition, in the policy generation strategy, the management dimension of each insurance transaction corresponding to the generated policy is the date dimension.

In addition, the management group rules include the payment sub-rules. The specific rules are the payment of premiums within N days after the policy is insured. The management rules include the rules of each management group and the sub-rules of the tenure. The specific rules of the sub-rules are the seller’s policy period is 1 year.

As a result, after reaching an order insurance transaction, first check whether the seller has an order insurance policy, if there is no policy, generate an order insurance policy for the seller, and generate a management group for the day (T day), According to the transaction time of this order insurance transaction on the T day and the premium to be paid X ₁ yuan, the payment sub-rule of the management group is generated, specifically the X ₁ yuan premium is paid on the T+N day.

If another order insurance transaction is reached on the same day, the result of checking whether the order insurance policy already exists under the seller dimension will be the existence of the policy, and after checking that there is a corresponding management group, the order insurance transaction will be added to the management group, And according to the transaction time of the order insurance transaction on the T day and the premium to be paid X ₂ yuan, update the payment sub-rule in the management group rules of the management group, and update to pay X ₁ +X ₂ yuan premium on T+N day .

It can be seen that, as shown in FIG. 2, the order insurance transactions reached on the same day can be added to the same management group, and the payment date and amount can be managed according to the total amount of order insurance transactions, and a policy can be generated for the same seller's order insurance transactions In order to carry out unified management of the guarantee period, etc., without affecting the original protection content, improve the management efficiency of order insurance with short guarantee period and large insurance transaction volume.

(2) After the investor has invested in the financing platform, the borrower can borrow the investor’s funds through the platform and repay the principal and a certain interest after the scheduled loan period expires, in order to protect the investor to recover the full amount in advance after the period expires The principal and interest promised can be covered by investment insurance for each investor's loan.

Assuming that the insurance type of target insurance transaction B is investment insurance, in the policy generation strategy corresponding to the order insurance, the policy dimension adopted when generating the policy is the investor dimension. In addition, the management rules include the payment sub-rule and the tenure sub-rule. Specifically, the payment sub-rule is based on each loan insured, stipulates the date of payment, and the corresponding proportion of the amount of premiums to be borrowed. The repayment date of each borrowed loan that is insured stipulates the corresponding insured period, and according to the investor's setting, it stipulates whether to automatically renew the insurance when the fund is borrowed again.

As a result, after 1 loan has occurred and 1 investment insurance transaction has been concluded, first check whether the investor has an investment insurance policy, and if there is no policy, generate an investment insurance policy for the investor and generate the The sub-rules for payment and sub-rules in the policy management rules.

When the loan is returned according to the pre-determined principal and interest, the investment insurance will also terminate the protection, and when the investor’s funds are lent out again, an investment insurance transaction will be reached. After checking whether there is an order under the investor dimension The result of the insurance policy will be the existence of the policy, and the sub-rules for payment and the sub-rules for insurance policy will be updated according to the amount of the loan and the repayment date in the investment insurance transaction concluded this time.

It can be seen that each investment insurance transaction of the same investor can be uniformly managed by the investor's 1 policy. When the borrowing situation changes, it is only necessary to update the policy management according to the transaction amount of the loan amount, repayment date and other transaction information Rules, so as to improve the efficiency of the management of investment insurance with flexible tenure and premium without affecting the original protection content.

Corresponding to the above method embodiment, an embodiment of this specification also provides an insurance transaction processing device. Referring to FIG. 3, the device may include:

The strategy determination module 110 is configured to determine a policy generation strategy corresponding to the insurance type according to the insurance type of the target insurance transaction, and the policy generation strategy includes: the policy dimension adopted when the insurance type generates the policy;

The policy inspection module 120 is configured to check whether a policy of the insurance type already exists in the policy dimension according to the policy generation strategy;

The policy generation module 130 is configured to generate a policy of the insurance type under the policy dimension in the absence of a policy, and generate a management rule of the policy according to the transaction information of the target insurance transaction;

The rule updating module 140 is used to update the management rules of the policy according to the transaction information of the target insurance transaction in the case where the policy already exists, so as to manage the target insurance transaction through the policy;

In a specific embodiment provided in this specification, the policy generation strategy may further include:

The management dimension of each insurance transaction corresponding to the insurance policy generated by the insurance type.

In a specific embodiment provided in this specification, referring to FIG. 4, the policy generation module 130 may include:

The policy generation unit 131 is configured to generate a policy of the insurance type under the policy dimension;

The dimension determining unit 132 is configured to determine the management dimension of the target insurance transaction according to the policy generation strategy;

The management group creation unit 133 is configured to create a management group corresponding to the generated policy according to the determined management dimension, and the management group includes the target insurance transaction;

The rule generation unit 134 is configured to generate the management group rules of the management group according to the transaction information of the target insurance transaction, and the generated management rules of the policy include the management group rules.

In a specific embodiment provided by this specification, referring to FIG. 5, the rule update module 140 includes:

The dimension determining unit 141 is used to determine the management dimension of the target insurance transaction according to the policy generation strategy;

The management group checking unit 142 is used to check whether the corresponding management group exists under the determined management dimension of the policy;

The rule updating unit 143 is used to add the target insurance transaction to the management group when there is a management group, and update the management group rules of the management group according to the transaction information of the target insurance transaction;

The rule generation unit 144 is used to create a management group corresponding to the policy under the management dimension when there is no management group, and generate a management group rule for the management group based on the transaction information of the target insurance transaction ;

Wherein, the management rules of the policy include the management group rules.

In a specific embodiment provided by this specification, the management rule may include:

Payment sub-rules, which are used to: determine the payment time and payment amount of the insurance transaction under management; and/or,

Term sub-rules, which are used to: determine whether the managed insurance transaction expires and/or renews; and/or,

Public announcement sub-rules, the public announcement sub-rules are used to: publicly announce the management information of the managed insurance transactions, the management information includes: payment information, claims information warranty period information, and/or user credit information.

For the implementation process of the functions and functions of each module in the above device, please refer to the implementation process of the corresponding steps in the above method for details, which will not be repeated here.

Embodiments of the present specification also provide a computer device, which includes at least a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the program to implement the foregoing insurance transaction processing method . The method includes at least:

An insurance transaction processing method, the method includes:

In the case where an insurance policy already exists, the management rules of the insurance policy are updated according to the transaction information of the target insurance transaction to manage the target insurance transaction through the insurance policy;

6 shows a schematic diagram of a more specific hardware structure of a computing device provided by an embodiment of this specification. The device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040 realize the communication connection between the devices within the device through the bus 1050.

The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit, central processing unit), a microprocessor, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc. Programs to implement the technical solutions provided by the embodiments of this specification.

The memory 1020 may be implemented in the form of ROM (Read Only Memory, Read Only Memory), RAM (Random Access Memory, Random Access Memory), static storage devices, and dynamic storage devices. The memory 1020 may store an operating system and other application programs. When the technical solutions provided by the embodiments of the present specification are implemented by software or firmware, related program codes are stored in the memory 1020 and called and executed by the processor 1010.

The input/output interface 1030 is used to connect input/output modules to realize information input and output. The input/output/module can be configured as a component in the device (not shown in the figure), or can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, mouse, touch screen, microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, and the like.

The communication interface 1040 is used to connect a communication module (not shown in the figure) to implement communication interaction between the device and other devices. The communication module can realize communication through a wired method (such as USB, network cable, etc.), and can also realize communication through a wireless method (such as mobile network, WIFI, Bluetooth, etc.).

The bus 1050 includes a path for transferring information between various components of the device (eg, processor 1010, memory 1020, input/output interface 1030, and communication interface 1040).

It should be noted that although the above device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device may also include necessary for normal operation Other components. In addition, those skilled in the art may understand that the above-mentioned device may also include only the components necessary to implement the solutions of the embodiments of the present specification, rather than including all the components shown in the figures.

Embodiments of the present specification also provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor implements the aforementioned insurance transaction processing method. The method includes at least:

An insurance transaction processing method, the method includes:

Computer-readable media, including permanent and non-permanent, removable and non-removable media, can store information by any method or technology. The information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. As defined in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

It can be known from the description of the above implementation manners that those skilled in the art can clearly understand that the embodiments of this specification can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solutions of the embodiments of the present specification can be embodied in the form of software products in essence or part of contributions to the existing technology, and the computer software products can be stored in a storage medium such as ROM/RAM, Magnetic disks, optical disks, etc., include several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in the embodiments of this specification or some parts of the embodiments.

The system, device, module or unit explained in the above embodiments may be specifically implemented by a computer chip or entity, or implemented by a product with a certain function. A typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or any combination of these devices.

The embodiments in this specification are described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The device embodiments described above are only schematic, wherein the modules described as separate components may or may not be physically separated, and the functions of the modules may be the same when implementing the embodiment solutions of the present specification Or multiple software and/or hardware. It is also possible to select some or all of the modules according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art can understand and implement without paying creative labor.

The above is only a specific implementation manner of the embodiments of this specification. It should be pointed out that for those of ordinary skill in the art, without departing from the principles of the embodiments of this specification, several improvements and retouches can be made. These Improvements and retouching should also be regarded as the scope of protection of the embodiments of this specification.

Claims

An insurance transaction processing method, the method includes:

Determine the policy generation strategy corresponding to the insurance type according to the insurance type of the target insurance transaction, the policy generation strategy includes: the policy dimension adopted when the insurance type generates the policy;

According to the policy generation strategy, check whether the policy of the insurance type already exists under the policy dimension;

In the absence of a policy, the policy of the insurance type is generated under the policy dimension, and the management rules of the policy are generated according to the transaction information of the target insurance transaction;

In the case where an insurance policy already exists, the management rules of the insurance policy are updated according to the transaction information of the target insurance transaction to manage the target insurance transaction through the insurance policy;

Among them, the management rules are used to manage each insurance transaction corresponding to the policy.
The method of claim 1, the policy generation strategy, further comprising:

The management dimension of each insurance transaction corresponding to the insurance policy generated by the insurance type.
The method according to claim 2, the generating the insurance policy of the insurance type under the insurance policy dimension and generating the management rules of the insurance policy based on the transaction information of the target insurance transaction include:

Generate the insurance policy of the insurance type under the insurance policy dimension;

Determine the management dimension of the target insurance transaction according to the policy generation strategy;

Create a management group corresponding to the generated policy according to the determined management dimension, and the management group includes the target insurance transaction;

The management group rules of the management group are generated according to the transaction information of the target insurance transaction, and the management rules of the generated insurance policy include the management group rules.
According to the method of claim 2, the updating of the management rules of the policy based on the transaction information of the target insurance transaction to manage the target insurance transaction through the policy includes:

Determine the management dimension of the target insurance transaction according to the policy generation strategy;

Check whether the insurance policy has a corresponding management group under the determined management dimension;

When there is a management group, add the target insurance transaction to the management group, and update the management group rules of the management group according to the transaction information of the target insurance transaction;

In the absence of a management group, create a management group corresponding to the policy under the management dimension, and generate a management group rule for the management group based on the transaction information of the target insurance transaction;

Wherein, the management rules of the policy include the management group rules.
The method according to claim 1, the management rules comprising:

Payment sub-rules, the payment sub-rules are used to: determine the payment time and payment amount of the insurance transaction under management; and/or,

Term sub-rules, which are used to: determine whether the managed insurance transaction expires and/or renews; and/or,

Public announcement sub-rules, the public announcement sub-rules are used to: publicly announce the management information of the managed insurance transactions, the management information includes: payment information, claims information warranty period information, and/or user credit information.
An insurance transaction processing device, including:

The strategy determination module is used to determine the policy generation strategy corresponding to the insurance type according to the insurance type of the target insurance transaction. The policy generation strategy includes: the policy dimension adopted when the insurance type generates the policy;

A policy inspection module, configured to check whether a policy of the insurance type already exists in the policy dimension according to the policy generation strategy;

The policy generation module is used to generate a policy of the insurance type in the policy dimension in the absence of a policy, and generate the management rules of the policy according to the transaction information of the target insurance transaction;

The rule update module is used to update the management rules of the policy according to the transaction information of the target insurance transaction under the condition that the policy already exists, so as to manage the target insurance transaction through the policy;

Among them, the management rules are used to manage each insurance transaction corresponding to the policy.
The apparatus of claim 6, the policy generation strategy, further comprising:

The management dimension of each insurance transaction corresponding to the insurance policy generated by the insurance type.
The apparatus according to claim 7, the policy generation module comprising:

A policy generation unit, configured to generate a policy of the insurance type under the policy dimension;

A dimension determining unit, used to determine the management dimension of the target insurance transaction according to the policy generation strategy;

The management group creation unit is used to create a management group corresponding to the generated policy according to the determined management dimension, and the management group includes the target insurance transaction;

The rule generation unit is configured to generate the management group rules of the management group according to the transaction information of the target insurance transaction, and the generated management rules of the policy include the management group rules.
The apparatus according to claim 7, the rule update module comprising:

A dimension determining unit, used to determine the management dimension of the target insurance transaction according to the policy generation strategy;

The management group checking unit is used to check whether the corresponding management group exists under the determined management dimension of the insurance policy;

A rule updating unit, used to add the target insurance transaction to the management group when there is a management group, and update the management group rules of the management group according to the transaction information of the target insurance transaction;

The rule generation unit is used to create a management group corresponding to the policy under the management dimension in the absence of a management group, and generate management group rules of the management group based on the transaction information of the target insurance transaction;

Wherein, the management rules of the policy include the management group rules.
The apparatus according to claim 6, the management rule includes:

Payment sub-rules, which are used to: determine the payment time and payment amount of the insurance transaction under management; and/or,

Term sub-rules, which are used to: determine whether the managed insurance transaction expires and/or renews; and/or,

Public announcement sub-rules, the public announcement sub-rules are used to: publicly announce the management information of the managed insurance transactions, the management information includes: payment information, claims information warranty period information, and/or user credit information.
A computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the program as described in any one of claims 1 to 5 when executing the program method.