Multi-account point management method and device, equipment and storage medium

Abstract

The invention relates to a multi-account point management method and device, equipment and a storage medium. According to the main technical scheme, the method comprises the steps of obtaining an insurance policy event and a behavior event of a client, and judging whether the client establishes an insurance point account; if not, establishing a plurality of insurance point accounts for the customer; according to the insurance policy event, the behavior event and a preset point rule, point management is carried out on the multiple insurance point accounts, and whether corresponding rights and interests exchange operation is triggered or not is judged; and if the corresponding right and interest exchange operation is triggered, synchronizing the corresponding right and interest exchange data to the third-party server so as to indicate the client to carry out right and interest exchange operation on the third-party server. According to the method, the multiple insurance point accounts are established through the insurance management system, the points of all the accounts are managed, then the third-party server is synchronized so that corresponding exchange rights and interests can be provided for clients, and the effects of conveniently adjusting insurance services, reducing the docking cost and improving the management efficiency are achieved.

Description

Technical Field

[0001] The present application relates to the technical field of insurance business, and in particular to a multi-account points management method, device, equipment and storage medium. Background Art

[0002] At present, due to the characteristics of insurance products and the diversity of sales models, the interaction between insurance companies and insurance customers is poor and the stickiness is low. Of course, compared with Internet products, the attribute of insurance itself is low-frequency interaction. In general, in addition to contract issuance, other scenarios for reaching customers are mostly negative scenarios, such as cancellation, claims, preservation, etc., and in the aforementioned situations, customers are generally in a bad mood and are prone to resistance. Therefore, it is not very helpful for the interaction between insurance companies and insurance customers. In addition, the diversity of sales models, such as the intervention of intermediary platforms, has also weakened customers' concept of insurance companies, making the insurance companies' reach rate even lower.

[0003] In the traditional implementation method, in order to break the inherent model of insurance, create more positive scenarios, attract customers, and increase the chances of insurance companies reaching customers. Most insurance companies choose to provide a variety of service rights to add value to insurance products, such as health service rights, self-operated shopping mall consumption rights, and community admission rights, so as to achieve the effect of allowing customers to interact with insurance companies many times. Generally, insurance companies will formulate strategies such as policy value-added or behavioral incentives to motivate users. The policy value-added here means that when the accumulated premiums payable for the policy purchased by the customer or a single policy reaches a certain amount, the policy will be increased in value, and the value-added includes obtaining third-party points; and behavioral incentives mean that users log in to the insurance company platform and participate in company activities within a limited time to obtain some third-party points, and the aforementioned points are generally only solved by creating an account to interact with third-party servers.

[0004] However, the above method realizes the exchange of rights and interests through the interaction between customers and third-party servers, so that customers can directly bypass the insurance company and exchange rights and interests on the third-party server. In addition, the insurance company has no management rights over the third-party points. If it wants to change the points and the rules for obtaining rights and interests in the future, it needs to operate through the third-party server, which makes the rights and interests tightly bound to the third-party server, which is not conducive to the docking of the insurance company's business. Summary of the invention

[0005] Based on this, the present application provides a multi-account points management method, device, equipment and storage medium, which establishes multiple insurance points accounts through the insurance management system, and manages the points of each account separately, and then synchronizes with a third-party server to provide customers with corresponding redemption rights, thereby facilitating adjustments to insurance business, reducing docking costs and improving management efficiency.

[0006] In a first aspect, a multi-account points management method is provided, the method comprising:

[0007] Obtain the customer's insurance policy events and behavior events, and determine whether the customer has established an insurance points account;

[0008] If not established, multiple insurance points accounts will be established for the customer;

[0009] Manage points for multiple insurance points accounts and determine whether to trigger corresponding rights redemption operations based on policy events, behavioral events and preset points rules;

[0010] If the corresponding rights exchange operation is triggered, the corresponding rights exchange data will be synchronized to the third-party server to instruct the customer to perform the rights exchange operation on the third-party server.

[0011] According to an achievable method in the embodiment of the present application, after the step of obtaining the customer's policy events and behavior events, the method further includes:

[0012] Determine whether to trigger the account points recharge operation based on policy events and behavioral events;

[0013] If not, the current state of the insurance management system is maintained;

[0014] If so, an operation is performed to determine whether the customer has established an insurance points account.

[0015] According to an achievable method in the embodiment of the present application, points management is performed on multiple insurance points accounts according to policy events, behavior events and preset points rules, and it is determined whether to trigger corresponding rights exchange operations, including:

[0016] Perform point recharge operations on multiple insurance point accounts according to policy events, behavioral events, and preset point rules to obtain points for multiple accounts;

[0017] Determine whether to trigger the corresponding rights exchange operation based on multiple account points and preset rights exchange rules.

[0018] According to an achievable method in the embodiment of the present application, points recharge operations are performed for multiple insurance points accounts according to policy events, behavior events and preset points rules, and multiple account points are obtained, including:

[0019] Calculate the first premium and the second premium according to the policy event, wherein the first premium is the sum of the premiums payable for multiple policies in the policy event; the second premium is the paid premium for the current policy in the policy event;

[0020] Points are recharged for multiple insurance points accounts according to the first premium, the second premium, behavioral events and preset points rules to obtain points for multiple accounts.

[0021] According to an achievable method in an embodiment of the present application, the multiple insurance points accounts include business-related accounts and equity docking accounts, and the preset points rules include:

[0022] Recharge the business-related account according to the first insurance premium to obtain business-related account points;

[0023] Recharge the rights and interests docking account based on the second premium and behavioral events, and obtain rights and interests docking account points.

[0024] According to an achievable manner in the embodiment of the present application, the method further includes:

[0025] If the corresponding rights exchange operation is not triggered, determine whether to synchronize the points of multiple accounts to the third-party server according to the preset points synchronization rules;

[0026] If not, the current state of the insurance management system is maintained;

[0027] If yes, the operation of synchronizing the points of multiple accounts to the third-party server is performed.

[0028] According to an achievable manner in the embodiment of the present application, the method further includes:

[0029] When the corresponding relationship between the policy event and / or behavior event and the account points changes, the operation of adjusting the preset points rules is triggered;

[0030] When the correspondence between the third-party server and the account points changes, the operation of adjusting the preset rights exchange rules is triggered.

[0031] In a second aspect, a multi-account points management device is provided, the device comprising:

[0032] An acquisition unit, used to acquire the customer's policy events and behavior events, and to determine whether the customer has established an insurance points account;

[0033] A creation unit, used to create multiple insurance points accounts for the customer if they have not been established;

[0034] The points management unit is used to manage the points of multiple insurance points accounts according to policy events, behavioral events and preset points rules, and to determine whether to trigger corresponding rights and interests redemption operations;

[0035] The synchronous exchange unit is used to synchronize the corresponding equity exchange data to a third-party server if the corresponding equity exchange operation is triggered, so as to instruct the customer to perform the equity exchange operation on the third-party server.

[0036] In a third aspect, a computer device is provided, comprising:

[0037] at least one processor; and

[0038] a memory communicatively connected to at least one processor; wherein,

[0039] The memory stores computer instructions that can be executed by at least one processor, and the computer instructions are executed by at least one processor to enable the at least one processor to execute the method involved in the first aspect above.

[0040] In a fourth aspect, a computer-readable storage medium is provided, on which computer instructions are stored, characterized in that the computer instructions are used to enable a computer to execute the method involved in the above-mentioned first aspect.

[0041] According to the technical content provided in the embodiments of the present application, by obtaining the customer's policy events and behavior events, and judging whether the customer has established an insurance points account; if not, multiple insurance points accounts are established for the customer; points management is performed on multiple insurance points accounts according to policy events, behavior events and preset points rules, and it is judged whether the corresponding rights exchange operation is triggered; if the corresponding rights exchange operation is triggered, the corresponding rights exchange data is synchronized to a third-party server to instruct the customer to perform the rights exchange operation on the third-party server. The above operation establishes multiple insurance points accounts through the insurance management system, and manages the points of each account separately, and then synchronizes with the third-party server to provide customers with corresponding exchange rights, so as to facilitate the adjustment of insurance business, reduce docking costs and improve management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A system architecture diagram of a multi-account points management method in one embodiment;

[0043] Figure 2 A schematic diagram of a flow chart of a multi-account points management method in one embodiment;

[0044] Figure 3 A schematic diagram of a preferred flow chart of a multi-account points management method in one embodiment;

[0045] Figure 4 It is a structural block diagram of a multi-account points management device in one embodiment;

[0046] Figure 5 FIG. 4 is a schematic structural diagram of a computer device in one embodiment. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0048] For ease of understanding, the system to which this application is applicable is first described. This application provides a multi-account points management method that can be applied to Figure 1 In the system architecture shown. The system architecture includes: terminal 101-insurance management system 103-third-party server 105. Specifically, the insurance management system 103 obtains the customer's policy events and behavior events from the terminal 101, and determines whether the customer has established an insurance points account; if not, multiple insurance points accounts are established for the customer; points management is performed on multiple insurance points accounts according to policy events, behavior events and preset points rules, and it is determined whether the corresponding rights and interests exchange operation is triggered; if the corresponding rights and interests exchange operation is triggered, the corresponding rights and interests exchange data is synchronized to the third-party server 105 to instruct the customer to perform the rights and interests exchange operation on the third-party server 105. Among them, the terminal 101 can be but not limited to various personal computers, laptops, smart phones and tablet computers; the insurance management system 103 can be implemented with an independent server or a server cluster composed of multiple servers; the third-party server can be a docking rights and interests server or server cluster for managing rights and interests exchange.

[0049] In one embodiment, Figure 2 As shown, a multi-account points management method is provided, and the method is applied to Figure 1 Take the insurance management system in the example as an example, including the following steps:

[0050] Step S201: Obtain the customer's insurance policy events and behavior events, and determine whether the customer has established an insurance points account.

[0051] Among them, policy events include but are not limited to the policy effective time, policy fees, policyholder information, policy details and policyholder change information; behavioral events include but are not limited to behavior type, behavior occurrence time and business channel; and regardless of whether it is a policy event or a behavioral event, both include positive events and negative events, and the two types of events have different impacts on the insurance points account.

[0052] Here, the insurance management system obtains the customer's policy events and behavior events, and determines whether the customer has currently established an insurance points account. If the customer has not established an insurance points account, step S203 is executed; if the customer has established an insurance points account, step S205 is executed.

[0053] Step S203: Establish multiple insurance points accounts for the customer.

[0054] Here, if the customer has not established an insurance points account, multiple insurance points accounts are recommended to the customer; wherein the multiple insurance points accounts include but are not limited to business-related accounts and rights and interests docking accounts, etc.

[0055] Step S205: manage points for multiple insurance point accounts according to policy events, behavioral events and preset point rules, and determine whether to trigger corresponding rights and interests redemption operations.

[0056] Among them, the preset points rules are how to manage points for different insurance points accounts according to policy events and behavioral events, and there is no restriction here for the time being. Rights exchange includes but is not limited to serious illness green channel service rights, online consultation service rights, retirement community admission rights, and third-party welfare mall exchange rights. It should be noted that community admission rights are also a kind of health service, and customers can exercise the right to live in a retirement community; the third-party welfare mall exchange rights are the rights that customers can redeem to purchase goods in the commodity mall provided by the supplier cooperating with the insurance company.

[0057] Here, after establishing multiple insurance points accounts, the relevant information in policy events and behavioral events can be converted into account points, and rights can be redeemed based on the account points. That is, multiple insurance points accounts can be managed separately according to policy events, behavioral events and preset points rules, and after each insurance points account obtains the corresponding account points, it can be determined whether to trigger the corresponding rights redemption operation.

[0058] Step S207: If the corresponding rights exchange operation is triggered, the corresponding rights exchange data is synchronized to the third-party server to instruct the customer to perform the rights exchange operation on the third-party server.

[0059] Among them, the third-party server can be a docking equity server used to manage equity exchange.

[0060] Here, if the corresponding rights exchange operation is triggered, the corresponding rights exchange data can be synchronized to a third-party server, namely, the docking rights server, so that the customer can perform the rights exchange operation on the docking rights server to further protect the customer's rights.

[0061] It can be seen that the embodiment of the present application obtains the customer's policy events and behavior events, and determines whether the customer has established an insurance points account; if not, multiple insurance points accounts are established for the customer; points management is performed on multiple insurance points accounts according to policy events, behavior events and preset points rules, and it is determined whether the corresponding rights exchange operation is triggered; if the corresponding rights exchange operation is triggered, the corresponding rights exchange data is synchronized to the third-party server to instruct the customer to perform the rights exchange operation on the third-party server. The above operation establishes multiple insurance points accounts through the insurance management system, and manages the points of each account separately, and then synchronizes with the third-party server to provide customers with corresponding exchange rights, so as to facilitate the adjustment of insurance business, reduce docking costs and improve management efficiency.

[0062] In one embodiment, after the step of obtaining the customer's policy events and behavioral events, the method also includes: determining whether to trigger an account points recharge operation based on the policy events and behavioral events; if not, maintaining the current state of the insurance management system; if so, executing an operation to determine whether the customer has established an insurance points account.

[0063] Specifically, after the insurance management system obtains the customer's policy events and behavior events, it can determine whether to trigger the account points recharge operation based on the policy events and behavior events. If the account points recharge operation is not triggered, the current state of the insurance management system can be maintained; if the account points recharge operation is triggered, the operation of determining whether the customer has established an insurance points account can be performed. Here, since the insurance company also has certain requirements for recharging the insurance points account, it is not possible to recharge the corresponding insurance points account as long as the policy events and behavior events are obtained, but it is also necessary to determine and adjust according to the specific actual situation, and no specific restrictions are made here.

[0064] After the above operation has completed the steps of obtaining the customer's policy events and behavioral events, it is also necessary to determine whether to trigger the account points recharge operation based on the policy events and behavioral events. Only after determining that the account points recharge operation has been triggered can the operation of determining whether to establish an insurance points account be performed to achieve the effect of improving the management efficiency of account points.

[0065] In one embodiment, points management is performed on multiple insurance points accounts according to policy events, behavioral events, and preset points rules, and it is determined whether a rights redemption operation is triggered, including: points recharge operations are performed on multiple insurance points accounts according to policy events, behavioral events, and preset points rules to obtain multiple account points; and it is determined whether a corresponding rights redemption operation is triggered according to multiple account points and preset rights redemption rules.

[0066] Among them, the preset rights exchange rules refer to the specific threshold requirements that must be met to achieve rights exchange, and there are no restrictions for the time being.

[0067] Here, the first premium and the second premium can be calculated according to the policy event. The first premium is the sum of the premiums payable for multiple policies in the policy event; the second premium is the paid premium for the current policy in the policy event. After obtaining the first premium and the second premium, points recharge operations can be performed for multiple insurance points accounts according to the first premium, the second premium, the behavior event, and the preset points rules, and then multiple account points can be obtained, so as to determine whether to trigger the corresponding rights exchange operation according to the multiple account points and the preset rights exchange rules.

[0068] In one achievable manner, the preset points rules include: recharging the business-related account according to the first premium to obtain business-related account points; recharging the rights and interests docking account according to the second premium and behavioral events to obtain rights and interests docking account points.

[0069] Here, since the insurance points account includes a business-related account and a rights-connected account, and the business-related account includes a retirement community account, and the rights-connected account includes an exchange mall account, that is, the retirement community account can be recharged only through the first premium to obtain the retirement community account points, that is, the retirement community account points do not receive the customer's behavior events; the exchange mall account is recharged according to the second premium and the behavior event to obtain the exchange mall account points, that is, the exchange mall account can be recharged through the second premium or through the behavior event, that is, the exchange mall account receives both the policy event and the behavior event.

[0070] In another achievable manner, the preset rights exchange rules include: triggering a corresponding rights exchange operation when the points of the business-related account reach a first threshold and / or the points of the rights docking account reach a second threshold.

[0071] The first threshold and the second threshold can be limited according to specific needs and are not limited here.

[0072] Here, after the balance in the retirement community account reaches the first threshold, the corresponding rights exchange operation is triggered and the rights exchange data is synchronized to the docking rights server, that is, the customer can obtain the right to live in the retirement community; after the balance in the redemption mall account reaches the second threshold, the corresponding rights exchange operation is triggered and the rights exchange data is synchronized to the docking rights server, which can be a third-party mall, so that the customer can go to the third-party mall to perform product redemption operations.

[0073] The above operations coordinate policy events and behavioral events, establish multiple insurance points accounts, manage the account points of multiple insurance points accounts, and customize the account attributes themselves, that is, the retirement community account only receives policy events and does not receive behavioral events; and the redemption mall account receives both policy events and behavioral events, thereby realizing different rights and interests redemption for different account types, which not only provides convenience to customers, but also improves the overall management of insurance points accounts.

[0074] In one embodiment, the method also includes: if the corresponding rights redemption operation is not triggered, determining whether to synchronize multiple account points to a third-party server according to a preset points synchronization rule; if not, maintaining the current state of the insurance management system; if so, executing the operation of synchronizing multiple account points to a third-party server.

[0075] Among them, the preset integral synchronization rules refer to the specific threshold requirements that must be met to achieve integral synchronization, and there are no restrictions for the time being.

[0076] Here, points management is performed on multiple insurance points accounts according to policy events, behavioral events and preset points rules, and it is determined whether to trigger corresponding rights and interests redemption operations. If the rights and interests redemption operation is not triggered, it is possible to determine whether to synchronize the points of multiple accounts to a third-party server according to the preset points synchronization rules. If the points of multiple accounts do not meet the set threshold requirements, the current state of the insurance management system is maintained; if any of the points of multiple accounts meets the set threshold requirements, the operation of synchronizing the points of the account to the third-party server can be executed.

[0077] If the above operation does not trigger the corresponding rights redemption operation, the preset points synchronization rules will be used to determine whether to synchronize the points of multiple accounts to the third-party server, and the synchronization will be determined based on the judgment result, thereby achieving the effect of improving the management efficiency of account points.

[0078] In one embodiment, the method also includes: when the correspondence between policy events and / or behavioral events and account points changes, triggering the operation of adjusting the preset points rules; when the correspondence between the third-party server and the account points changes, triggering the operation of adjusting the preset rights and interests redemption rules.

[0079] Here, since the account points are managed by the insurance company, when the configuration between the policy events and / or behavior events and the account points changes, it is sufficient to adjust the preset points rules and / or preset rights exchange rules. Specifically, when the corresponding relationship between the policy events and / or behavior events and the account points changes, the operation of adjusting the preset points rules is triggered, that is, only by changing the preset points rules, the support for the business when the corresponding relationship between the policy events and / or behavior events and the account points changes can be achieved; when the corresponding relationship between the third-party server and the account points changes, the operation of adjusting the preset rights exchange rules is triggered, that is, only by changing the preset rights exchange, the support for the business when the corresponding relationship between the third-party server and the account points changes can be achieved, and when the insurance company wants to change the supplier of the third-party mall, it can also directly change it by changing the preset rights rules accordingly.

[0080] The above operations can trigger the adjustment of preset benefit redemption rules and preset points rules when the correspondence between policy events and / or behavioral events and account points changes, or when the correspondence between third-party servers and account points changes, thereby reducing the cost of multiple IT development and docking and improving the flexibility of docking with third-party servers.

[0081] In order to facilitate further understanding, an example is given here to illustrate the above embodiment as a whole.

[0082] Assume that the customer's policy event is that the first premium of the policy purchased for insurance type A / B is X million yuan, and the second premium is Y million yuan, and the first premium and the second premium have reached the requirements for triggering the account points recharge operation, and two accounts, the retirement community and the redemption mall, have been established.

[0083] In one feasible method, X million points can be recharged for the retirement community account based on the first premium, and at the same time, it is checked whether the balance of points in the retirement community account reaches a first threshold, assuming it is 1.2 million points. If the balance of points in the retirement community account reaches 1.2 million points, the rights exchange operation is triggered and the rights exchange data is synchronized to the docking rights server, that is, the customer can obtain the right to live in the retirement community; if the balance of points in the retirement community account does not reach 1.2 million points, the rights exchange operation is not triggered, and it is determined whether to synchronize the retirement community account to the docking rights server according to the preset points synchronization rules; if not, the current state of the insurance management system is maintained; if so, the operation of synchronizing the points in the retirement community account to the docking rights server is executed.

[0084] Here, Y ten thousand points can also be recharged for the redemption mall account based on the second premium. At the same time, the behavioral event is assumed to be an event of reminding the customer to log in to the application and register to participate in the points redemption activity through a mobile terminal. The insurance management system can recharge a fixed threshold points for the redemption mall account based on the customer's login and registration operations, assuming 10 points, and add Y ten thousand points and 10 points to obtain the total points of the redemption mall account. The total points balance of the redemption mall account is updated in real time, and at the same time, it is checked whether the total points of the redemption mall account reaches the second threshold. If the total points of the redemption mall account reaches the second threshold, the rights and interests redemption operation is triggered and the rights and interests redemption data is synchronized to the docking rights and interests server, that is, the third-party mall, so that the customer can go to the third-party mall to perform rights and interests redemption operations; if the total points balance of the redemption mall account does not reach the second threshold, the rights and interests redemption operation is not triggered, and it is determined whether to synchronize the redemption mall account to the docking rights and interests server according to the preset points synchronization rules; if not, the current state of the insurance management system is maintained; if so, the operation of synchronizing the total points of the redemption mall account to the docking rights and interests server is executed.

[0085] In combination with the implementation method in the above embodiment, Figure 3 An example of a preferred method flow provided in the embodiment of the present application is described. Figure 3 As shown, the method may include the following steps:

[0086] Step S301, obtain the customer's insurance policy events and behavior events, and determine whether to trigger the account points recharge operation based on the insurance policy events and behavior events; if so, execute step S302; if not, execute step S310.

[0087] Step S302, determine whether the customer has established an insurance points account; if not, execute step S303; if established, execute step S304.

[0088] Step S303, establishing multiple insurance points accounts for the customer.

[0089] Step S304, calculating a first premium and a second premium according to the policy event, wherein the first premium is the sum of the premiums payable for multiple policies in the policy event; and the second premium is the paid premium for the current policy in the policy event.

[0090] Step S305, performing point recharge operations for multiple insurance point accounts according to the first premium, the second premium, the behavior event and the preset point rules, and obtaining multiple account points.

[0091] Step S306, judging whether a corresponding equity exchange operation is triggered according to the multiple account points and the preset equity exchange rules; if the corresponding equity exchange operation is triggered, executing step S307; if the corresponding equity exchange operation is not triggered, executing step S308;

[0092] In step S307, the rights exchange data is synchronized to a third-party server to instruct the client to perform rights exchange operations on the third-party server.

[0093] In step S308, it is determined whether to synchronize the points of multiple accounts to a third-party server according to the preset points synchronization rules; if so, step S309 is executed; if not, step S310 is executed.

[0094] Step S309, synchronizing the points of multiple accounts to a third-party server.

[0095] Step S310, maintaining the current state of the insurance management system.

[0096] It should be understood that although Figure 2-Figure 3 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in the application, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2-Figure 3 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0097] Figure 4 A schematic diagram of a multi-account points management device provided in an embodiment of the present application, which can be arranged at Figure 1 The insurance management system in the system architecture shown is used to perform the following operations: Figure 2-Figure 3 The method flow shown in Figure 4 As shown, the device may include: an acquisition unit 401, an establishment unit 403, a points management unit 405, and a synchronous redemption unit 407. The main functions of each component module are as follows:

[0098] The acquisition unit 401 is used to acquire the customer's insurance policy events and behavior events, and determine whether the customer has established an insurance points account;

[0099] An establishing unit 403 is used to establish multiple insurance points accounts for the customer if they have not been established;

[0100] The points management unit 405 is used to manage the points of multiple insurance points accounts according to the policy events, behavior events and preset points rules, and to determine whether to trigger the corresponding rights and interests redemption operation;

[0101] The synchronous exchange unit 407 is used to synchronize the equity exchange data to the third-party server if the corresponding equity exchange operation is triggered, so as to instruct the client to perform the equity exchange operation on the third-party server.

[0102] In one embodiment, the device is further used to:

[0103] Determine whether to trigger the account points recharge operation based on policy events and behavioral events;

[0104] If not, the current state of the insurance management system is maintained;

[0105] If so, an operation is performed to determine whether the customer has established an insurance points account.

[0106] In one embodiment, the device is further used to:

[0107] Based on policy events, behavioral events and preset points rules, multiple insurance points accounts are recharged to obtain points for multiple accounts;

[0108] Determine whether to trigger the corresponding rights exchange operation based on multiple account points and preset rights exchange rules.

[0109] In one embodiment, the device is further used for:

[0110] Calculate the first premium and the second premium according to the policy event, wherein the first premium is the sum of the premiums payable for multiple policies in the policy event; the second premium is the paid premium for the current policy in the policy event;

[0111] Points are recharged for multiple insurance points accounts according to the first premium, the second premium, behavioral events and preset points rules to obtain points for multiple accounts.

[0112] In one embodiment, the device is further used to:

[0113] Recharge the business-related account according to the first insurance premium to obtain business-related account points;

[0114] Recharge the rights and interests docking account based on the second premium and behavioral events, and obtain rights and interests docking account points.

[0115] In one embodiment, the device is further used for:

[0116] If the corresponding rights exchange operation is not triggered, determine whether to synchronize the points of multiple accounts to the third-party server according to the preset points synchronization rules;

[0117] If not, the current state of the insurance management system is maintained;

[0118] If yes, the operation of synchronizing the points of multiple accounts to the third-party server is performed.

[0119] In one embodiment, the device is further used for:

[0120] When the corresponding relationship between the policy event and / or behavior event and the account points changes, the operation of adjusting the preset points rules is triggered;

[0121] When the correspondence between the third-party server and the account points changes, the operation of adjusting the preset rights exchange rules is triggered.

[0122] The same or similar parts between the above embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0123] It should be noted that the embodiments of the present application may involve the use of user data. In actual applications, user-specific personal data can be used in the scheme described in this article within the scope permitted by applicable laws and regulations, provided that the applicable laws and regulations of the country are met (for example, the user's explicit consent, effective notification to the user, and the user's explicit authorization, etc.).

[0124] According to an embodiment of the present application, the present application also provides a computer device and a computer-readable storage medium.

[0125] like Figure 5 , is a block diagram of a computer device according to an embodiment of the present application. The computer device is intended to represent various forms of digital computers or mobile devices. The digital computer may include a desktop computer, a portable computer, a workbench, a personal digital assistant, a server, a mainframe computer, and other suitable computers. The mobile device may include a tablet computer, a smart phone, a wearable device, etc.

[0126] like Figure 5 As shown, the device 500 includes a computing unit 501, a ROM 502, a RAM 503, a bus 504, and an input / output (I / O) interface 505, and the computing unit 501, ROM 502 and RAM 503 are connected to each other through the bus 504. The input / output (I / O) interface 505 is also connected to the bus 504.

[0127] The computing unit 501 can perform various processes in the method embodiment of the present application according to the computer instructions stored in the read-only memory (ROM) 502 or the computer instructions loaded from the storage unit 508 to the random access memory (RAM) 503. The computing unit 501 can be various general and / or special processing components with processing and computing capabilities. The computing unit 501 may include, but is not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. In some embodiments, the method provided in the embodiment of the present application can be implemented as a computer software program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 508.

[0128] RAM 503 may also store various programs and data required for the operation of device 500. Part or all of the computer program may be loaded and / or installed on device 500 via ROM 502 and / or communication unit 509.

[0129] The input unit 506, output unit 507, storage unit 508 and communication unit 509 in the device 500 can be connected to the I / O interface 505. The input unit 506 can be, for example, a keyboard, a mouse, a touch screen, a microphone, etc. The output unit 507 can be, for example, a display, a speaker, an indicator light, etc. The device 500 can exchange information, data, etc. with other devices through the communication unit 509.

[0130] It should be noted that the device may also include other components necessary for normal operation, or may only include components necessary for implementing the solution of the present application, rather than all the components shown in the figure.

[0131] Various implementations of the systems and techniques described herein can be realized in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof.

[0132] The computer instructions for implementing the method of the present application can be written in any combination of one or more programming languages. These computer instructions can be provided to the computing unit 501, so that when the computer instructions are executed by the computing unit 501 such as a processor, the steps involved in the method embodiment of the present application are executed.

[0133] The computer-readable storage medium provided in the present application may be a tangible medium that may contain or store computer instructions for executing the steps involved in the method embodiments of the present application. The computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, and other forms of storage media.

[0134] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A multi-account points management method, characterized in that: The method comprises: Obtain the customer's insurance policy events and behavior events, and determine whether the customer has established an insurance points account; If not established, multiple insurance points accounts will be established for the customer; According to the policy events, behavior events and preset points rules, the multiple insurance points accounts are managed and it is determined whether the corresponding rights and interests redemption operation is triggered; If the corresponding rights exchange operation is triggered, the corresponding rights exchange data will be synchronized to the third-party server to instruct the customer to perform the rights exchange operation on the third-party server.

2. The method according to claim 1, characterized in that After the step of obtaining the customer's policy events and behavior events, the method further includes: Determine whether to trigger the account points recharge operation based on the policy event and behavior event; If not, the current state of the insurance management system is maintained; If so, an operation is performed to determine whether the customer has established an insurance points account.

3. The method according to claim 1, characterized in that The step of managing points for the multiple insurance points accounts and determining whether to trigger corresponding rights exchange operations according to the policy events, behavior events and preset points rules includes: According to the policy events, behavior events and preset points rules, points recharge operations are performed on the multiple insurance points accounts to obtain multiple account points; Whether to trigger a corresponding rights exchange operation is determined based on the multiple account points and preset rights exchange rules.

4. The method according to claim 3, characterized in that The points recharge operation is performed for the multiple insurance points accounts according to the policy events, behavior events and preset points rules to obtain multiple account points, including: Calculate a first premium and a second premium according to the policy event, wherein the first premium is the sum of the premiums payable for multiple policies in the policy event; and the second premium is the paid premium for the current policy in the policy event; Points recharge operations are performed on the multiple insurance points accounts according to the first premium, the second premium, behavioral events and preset points rules to obtain multiple account points.

5. The method according to claim 4, characterized in that The multiple insurance points accounts include business-related accounts and equity docking accounts, and the preset points rules include: Recharging the business-related account according to the first insurance premium to obtain business-related account points; The rights and interests docking account is recharged according to the second premium and the behavior event to obtain rights and interests docking account points.

6. The method according to claim 1, characterized in that The method further comprises: If the corresponding rights exchange operation is not triggered, determining whether to synchronize the points of the multiple accounts to the third-party server according to the preset points synchronization rules; If not, the current state of the insurance management system is maintained; If so, the operation of synchronizing the points of the multiple accounts to the third-party server is performed.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: When the corresponding relationship between the policy event and / or behavior event and the account points changes, triggering the operation of adjusting the preset points rule; When the correspondence between the third-party server and the account points changes, an operation of adjusting the preset rights exchange rules is triggered.

8. A multi-account points management device, characterized in that: The device comprises: An acquisition unit, used to acquire the customer's policy events and behavior events, and to determine whether the customer has established an insurance points account; A creation unit, used to create multiple insurance points accounts for the customer if they have not been established; A points management unit, used to manage points for the multiple insurance points accounts according to the policy events, behavior events and preset points rules, and to determine whether to trigger corresponding rights and interests redemption operations; The synchronous exchange unit is used to synchronize the corresponding equity exchange data to a third-party server if the corresponding equity exchange operation is triggered, so as to instruct the customer to perform the equity exchange operation on the third-party server.

9. A computer device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores computer instructions that can be executed by the at least one processor, and the computer instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having computer instructions stored thereon, characterized in that: The computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 7.

Images