Data processing method and device, electronic equipment, storage medium and program product

Abstract

The embodiment of the invention provides a data processing method and device, electronic equipment, a storage medium and a program product, and can be applied to the technical field of data processing. The intermediate layer system comprises a client and a server, the method is applied to the server, and the method comprises the following steps: receiving a first delay protection request sent by the client; the first insurance delay request comprises insurance delay information of the first insurance policy; a second insurance delay request is sent to the underwriting system, the second insurance delay request comprises the insurance delay information, so that the underwriting system responds to the second insurance delay request to check the insurance delay information, generates an insurance delay policy under the condition that the check is passed, and returns an insurance delay success message; and sending an insurance delay success message to the client. According to the method and the device, the automation of the insurance extension process is realized, a third-party mechanism does not need to provide the insurance extension information to an insurance mechanism through a mail and other communication modes offline, and the insurance extension efficiency is improved.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and in particular, to a data processing method, apparatus, electronic device, storage medium, and program product. Background Art

[0002] Extended warranty is a service that extends the product warranty period, aiming to provide consumers with additional protection outside the warranty period and service scope provided by the manufacturer. In the extended warranty process, usually a third-party agency sends the extended warranty information to the insurance agency through communication methods such as emails, and after the insurance agency reviews and approves it, it undertakes the insurance. The extended warranty efficiency of this method is relatively low. Summary of the Invention

[0003] This application provides a data processing method, apparatus, electronic device, storage medium, and program product, which improves the extended warranty efficiency.

[0004] In a first aspect, this application provides a data processing method. The middleware system includes a client and a server. The method is applied to the server, and the method includes:

[0005] Receiving a first extended warranty request sent by the client; the first extended warranty request includes the extended warranty information of a first insurance policy;

[0006] Sending a second extended warranty request to the underwriting system, the second extended warranty request including the extended warranty information, so that the underwriting system reviews the extended warranty information in response to the second extended warranty request and generates an extended warranty policy and returns an extended warranty success message when the review is passed;

[0007] Sending the extended warranty success message to the client.

[0008] In some embodiments, it further includes:

[0009] Receiving a policy viewing request sent by the client; the policy viewing request carries the policy identifier corresponding to a second insurance policy;

[0010] Obtaining the policy information stored corresponding to the policy identifier from the policy database;

[0011] Sending the policy information stored corresponding to the policy identifier to the client, so that the client displays based on the policy information.

[0012] In some embodiments, it further includes:

[0013] Receiving a first insurance policy modification request sent by the client; the first insurance policy modification request carries the policy identifier corresponding to a third insurance policy and the field identifier corresponding to the first information field to be modified in the third insurance policy;

[0014] Obtain the policy information stored corresponding to the policy identifier from the policy database, and obtain the first information field corresponding to the field identifier from the policy information;

[0015] Send a first policy modification response to the client, where the first policy modification response carries the first information field;

[0016] Receive the second information field sent by the client, and the second information field is obtained by modifying the first information field;

[0017] Send a second policy modification request to the underwriting system; the second policy modification request carries the second information field, so that the underwriting system audits the second information field in response to the second policy modification request, and updates the third policy based on the second information field when the audit is passed.

[0018] In a second aspect, the present application provides a data processing method. The middle - layer system includes a client and a server. The method is applied to the underwriting system and includes:

[0019] Receive the second extended warranty request sent by the server; the second extended warranty request includes the extended warranty information of the first policy, and the second extended warranty request is sent by the server when it receives the first extended warranty request sent by the client;

[0020] Generate an extended warranty audit task for auditing the extended warranty information, and send the extended warranty audit task to the account of the auditor;

[0021] Obtain the audit result uploaded by the account, and generate an extended warranty policy when the audit result indicates that the audit is passed;

[0022] Send an extended warranty success message to the server, so that the server sends the extended warranty success message to the client.

[0023] In some embodiments, it further includes:

[0024] Receive the second policy modification request sent by the server; the second policy modification request carries the second information field, and the second information field is obtained by modifying the first information field to be modified in the third policy;

[0025] Generate an information audit task for auditing the second information field, and send the information audit task to the account of the auditor;

[0026] Obtain the audit result uploaded by the account, and update the third policy based on the second information field when the audit result indicates that the audit is passed;

[0027] Send a modification success message to the server, so that the server sends the modification success message to the client.

[0028] In some embodiments, the second insurance policy modification request carries the policy identifier corresponding to the third insurance policy; updating the third insurance policy based on the second information field includes:

[0029] Update the second information field to the policy information of the third insurance policy in the policy database to obtain a new third insurance policy.

[0030] In a third aspect, the present application provides a data processing device. The middleware system includes a client and a server. The device is disposed in the server, and the device includes:

[0031] A receiving module, configured to receive a first extended warranty request sent by the client; the first extended warranty request includes extended warranty information of a first insurance policy;

[0032] A sending module, configured to send a second extended warranty request to an underwriting system, the second extended warranty request includes the extended warranty information, so that the underwriting system audits the extended warranty information in response to the second extended warranty request and generates an extended warranty policy and returns an extended warranty success message when the audit passes;

[0033] The sending module is further configured to send the extended warranty success message to the client.

[0034] In a fourth aspect, the present application provides a data processing device. The middleware system includes a client and a server. The device is disposed in the underwriting system, and the device includes:

[0035] A receiving module, configured to receive a second extended warranty request sent by the server; the second extended warranty request includes extended warranty information of a first insurance policy, and the second extended warranty request is sent by the server when the server receives a first extended warranty request sent by the client;

[0036] A generating module, configured to generate an extended warranty audit task for auditing the extended warranty information, and send the extended warranty audit task to the account of the auditor;

[0037] The generating module is further configured to obtain the audit result uploaded by the account, and generate an extended warranty policy when the audit result indicates that the audit passes;

[0038] A sending module, configured to send an extended warranty success message to the server, so that the server sends the extended warranty success message to the client.

[0039] Fifth aspect, the present application provides an electronic device, including: a processor and a memory communicatively connected to the processor;

[0040] The memory stores computer-executable instructions;

[0041] The processor executes the computer-executable instructions stored in the memory to implement the data processing method according to any one of the first aspect or the data processing method according to any one of the second aspect.

[0042] Sixth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the data processing method according to any one of the first aspect or the data processing method according to any one of the second aspect.

[0043] Seventh aspect, the present application provides a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the data processing method according to any one of the first aspect or the data processing method according to any one of the second aspect.

[0044] The data processing method, device, electronic device, storage medium and program product provided by the present application, by deploying an intermediate layer system including a client and a server, in the extended warranty process, the server is used as an information transmission intermediary to receive and send extended warranty requests, realizing the transfer of extended warranty information between the client and the underwriting system, realizing the automation of the extended warranty process, without the need for a third party to provide the extended warranty information to the insurance institution offline through communication methods such as emails, improving the extended warranty efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The drawings here are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0046] Figure 1 is a schematic diagram of an application scenario provided by the present application;

[0047] Figure 2 is a flowchart of a data processing method provided by the present application;

[0048] Figure 3 is a flowchart of another data processing method provided by the present application;

[0049] Figure 4 is a schematic diagram of an extended warranty process provided by the present application;

[0050] Figure 5 is a schematic diagram of a policy viewing process provided by the present application;

[0051] Figure 6 It is a schematic diagram of an insurance policy modification process provided by this application;

[0052] Figure 7 It is a schematic structural diagram of a data processing device provided by this application;

[0053] Figure 8 It is a schematic structural diagram of another data processing device provided by this application;

[0054] Figure 9 It is a schematic structural diagram of an electronic device provided by this application.

[0055] Through the above-mentioned accompanying drawings, the specific embodiments of this application have been shown, and there will be more detailed descriptions hereinafter. These accompanying drawings and text descriptions are not intended to limit the scope of the concept of this application in any way, but to illustrate the concept of this application to those skilled in the art by referring to specific embodiments. Specific Embodiments

[0056] Here, the exemplary embodiments will be described in detail, and their examples are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different accompanying drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. On the contrary, they are merely examples of devices and methods consistent with some aspects of this application as detailed in the appended claims.

[0057] Extended warranty is a service that extends the product warranty period, aiming to provide consumers with additional protection outside the warranty period and service scope provided by the manufacturer. The extended warranty process is usually handled by a third-party agency on behalf of consumers. In the extended warranty process, usually, the third-party agency sends the extended warranty information to the insurance agency through communication means such as emails, and after the insurance agency reviews and approves it, it undertakes the insurance. The extended warranty efficiency of this method is relatively low.

[0058] Based on this, this application proposes a data processing method, device, electronic device, storage medium, and program product, aiming to solve the above-mentioned technical problems.

[0059] Figure 1 It is a schematic diagram of an application scenario provided by this application. As Figure 1 shown, this application scenario shows a network architecture, which includes: an external network and an insurance agency-related system, and the insurance agency-related system includes a Demilitarized Zone (DMZ) and an internal network. Among them, the intermediate layer system includes a client and a server, the client is deployed in the external network, the server is deployed in the DMZ area, and the underwriting system and the policy database are deployed in the internal network.

[0060] Among them, the client is connected to the server through a network, and the server is also connected to the underwriting system through a network. Both the server and the underwriting system can access the policy database.

[0061] Exemplarily, the middle layer system can be a voucher system, an external cooperation business management platform, or a channel system, and the middle layer system can be deployed in the form of microservices. Among them, the staff of the third-party institution logs in to the middle layer system through the client, enabling the client to communicate with the server and perform data interaction. Among them, the server consists of at least one server and is used for data transfer between the client and the underwriting system. The number of the at least one server can be set according to actual needs, and this application does not limit this. For the sake of representation, Figure 1 only take one example.

[0062] Similarly, a background server is deployed in the underwriting system, and the staff of the insurance institution logs in to the underwriting system through the terminal device, so that the terminal device can communicate with the underwriting system and perform data interaction. Exemplarily, the number of third-party systems can be one or more (for the sake of representation, Figure 1 only take one example), and this application does not limit this.

[0063] Optionally, the data interaction between the server and the underwriting system can ensure the compliance of the extended warranty process through electronic signatures.

[0064] Optionally, the number of middle layer systems can be set according to needs. For example, it can be set as a multi-channel system and dock with the underwriting system respectively.

[0065] The technical solution of this application and how the technical solution of this application solves the above technical problems will be described in detail below with specific embodiments. These specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will be described below in conjunction with the accompanying drawings.

[0066] Figure 2 It is a schematic flowchart of a data processing method provided by this application. As Figure 2 shown, the data processing method provided in this embodiment is applied to the server in the middle layer system, and the data processing method provided in this embodiment includes the following steps:

[0067] Step S101, receiving a first extended warranty request sent by the client; the first extended warranty request includes the extended warranty information of the first policy.

[0068] Among them, the client refers to the client in the middle - layer system. The first extended warranty request is used to request the server to extend the warranty for the first insurance policy. The first insurance policy is any insurance policy with an extended - warranty need. The extended - warranty information includes extended - warranty - related information such as the policy identifier, extended - warranty time, and extended - warranty premium. Among them, the policy identifier is used to uniquely identify the insurance policy to distinguish different insurance policies. For example, the policy identifier can be the policy number. The extended - warranty time includes information such as the start time of the extended warranty, the end time of the extended warranty, and the total duration of the extended warranty. Optionally, the first extended - warranty request also includes other information in addition to the extended - warranty information of the first insurance policy. For example, the client identifier corresponding to the client, which is used to uniquely identify the client to distinguish different clients. For example, the client identifier is the Internet protocol address of the client.

[0069] In practical applications, if a user has an insurance policy that needs to be extended, the user can entrust a third - party agency to extend the warranty for the policy. Taking the first insurance policy as an example, the staff of the third - party agency log in to the middle - layer system on the client, upload the extended - warranty information of the first insurance policy, and trigger the client to send a first extended - warranty request to the server. Exemplarily, the staff of the third - party agency log in to the middle - layer system by entering a username and password on the client. Among them, the username and password can be pre - assigned by the insurance agency to the staff of the third - party agency.

[0070] Step S102: Send a second extended - warranty request to the underwriting system. The second extended - warranty request includes extended - warranty information, so that the underwriting system audits the extended - warranty information in response to the second extended - warranty request and generates an extended - warranty policy and returns an extended - warranty success message when the audit is passed.

[0071] Among them, the second extended - warranty request is used to request the underwriting system to extend the warranty for the first insurance policy. Optionally, the second extended - warranty request also includes other information in addition to the extended - warranty information of the first insurance policy. For example, the server identifier corresponding to the server, which is used to uniquely identify the server to distinguish different servers. For example, the server identifier is the Internet protocol address of the server.

[0072] Among them, the extended - warranty policy can be an independent policy or a non - independent policy. Specifically, the type of the extended - warranty policy can be set in advance in the underwriting system according to actual needs, and this application does not limit this. A non - independent policy refers to a policy that uses the policy identifier of the first insurance policy and the non - independent policy includes the additional terms of the first insurance policy. An independent policy refers to a new policy with a different policy identifier from the first insurance policy.

[0073] Among them, the extended - warranty success message is used to indicate that the extension of the first insurance policy is successful. Returning the extended - warranty success information means sending the extended - warranty success information to the server. In this application, for the operation process of the underwriting system, refer to Figure 3 the embodiments shown, which will not be elaborated here for the time being.

[0074] Step S103: Send an extended warranty success message to the client.

[0075] In this embodiment, after receiving the extended warranty success message, the server sends the extended warranty success message to the client that sent the first extended warranty request to notify the client. Correspondingly, the client displays a prompt message, which is used to prompt the user that the first insurance policy's extended warranty is successful, so that the staff of the third-party institution can view the extended warranty progress in a timely manner. The specific content of the prompt message can be set according to actual needs, and the present application does not limit this.

[0076] Regarding the data processing method provided by the present application, this embodiment explains the extended warranty process from the perspective of the server in the middle-tier system. By deploying a middle-tier system including a client and a server, in the extended warranty process, the server serves as an information transmission intermediary to receive and send extended warranty requests, realizing the transfer of extended warranty information between the client and the underwriting system, and realizing the automation of the extended warranty process. There is no need for the third-party institution to provide the extended warranty information to the insurance institution offline through communication methods such as emails, improving the extended warranty efficiency.

[0077] Figure 3 It is a flowchart of another data processing method provided by the present application. As Figure 3 shown, the data processing method provided in this embodiment explains the extended warranty process from the perspective of the underwriting system, and the data processing method provided in this embodiment includes the following steps:

[0078] Step S201: Receive a second extended warranty request sent by the server; the second extended warranty request includes the extended warranty information of the first insurance policy, and the second extended warranty request is sent by the server when it receives the first extended warranty request sent by the client.

[0079] Among them, the server refers to the server in the middle-tier system. When the server receives the first extended warranty request sent by the client, it sends a second extended warranty request to the underwriting system. In the present application, the operation process of the server refers to the Figure 2 embodiment shown, which will not be elaborated here.

[0080] Among them, the second extended warranty request is used to request the underwriting system to extend the warranty for the first insurance policy. Optionally, the second extended warranty request also includes other information other than the extended warranty information of the first insurance policy, such as the server identifier corresponding to the server, and the server identifier is used to uniquely identify the server to distinguish different servers. For example, the server identifier is the Internet protocol address of the server. The first insurance policy is any insurance policy with an extended warranty requirement. The extended warranty information includes extended warranty-related information such as a policy identifier, extended warranty time, and extended warranty premium. Among them, the policy identifier is used to uniquely identify the insurance policy to distinguish different insurance policies. For example, the policy identifier can be a policy number. The extended warranty time includes information such as the start time of the extended warranty, the end time of the extended warranty, and the total duration of the extended warranty.

[0081] Step S202: Generate a warranty extension audit task for auditing the warranty extension information, and send the warranty extension audit task to the account of the auditor.

[0082] Since the warranty extension information uploaded by the staff of the third-party agency on the client side may be incorrect, it is necessary to audit the warranty extension information. In this embodiment, the underwriting system generates a warranty extension audit task and sends the warranty extension audit task to the account of the auditor, so that the auditor can log in to the account in the underwriting system, view and process the warranty extension audit task, and upload the audit result.

[0083] Among them, the task information of the warranty extension audit task carries the warranty extension information of the first insurance policy, so that the auditor can view and audit whether the warranty extension information is incorrect.

[0084] Among them, the audit result is used to indicate whether the audit is passed or not. If the audit is passed, it means that the warranty extension information of the first insurance policy is correct; if the audit is not passed, it means that the warranty extension information of the first insurance policy is incorrect and needs to be modified.

[0085] Step S203: Obtain the audit result uploaded by the account, and generate a warranty extension policy when the audit result indicates that the audit is passed.

[0086] When the audit is passed, the underwriting system directly generates a warranty extension policy. Optionally, the implementation method of generating the warranty extension policy can refer to the related technical means and will not be elaborated here.

[0087] When the audit is not passed, the underwriting system can return an audit failure message to the server. The audit failure message is used to indicate that the audit of the warranty extension information of the first insurance policy fails. Correspondingly, the server sends the audit failure information to the client, so that the client can prompt the user. Thus, the staff of the third-party agency can modify the warranty extension information through the client and upload it again, thereby triggering the client to send a new first warranty extension request to the server, and the first warranty extension request carries the modified warranty extension information.

[0088] Among them, the warranty extension policy can be an independent policy or a non-independent policy. Specifically, the type of the warranty extension policy can be set in advance in the underwriting system according to actual needs, and this application does not limit this. A non-independent policy refers to a policy that uses the policy identification of the first insurance policy, and the non-independent policy includes the additional clauses of the first insurance policy. An independent policy refers to a new policy with a different policy identification from the first insurance policy.

[0089] In this embodiment, the policy database is used to store the policy information corresponding to the policy. Among them, the policy information is the basis of the insurance contract and is used to confirm the contractual relationship between the applicant and the insurance institution. For example, the policy information includes the insurance contract code, applicant information, insured information, insurance product information, etc. The underwriting system can upload the extended warranty policy to the policy database to achieve the storage of the policy. By storing the policy information in an independent database, the security of the data can be guaranteed.

[0090] Step S204, send an extended warranty success message to the server so that the server sends an extended warranty success message to the client.

[0091] Among them, the extended warranty success message is used to indicate that the first policy has been successfully extended. In this embodiment, after receiving the extended warranty success message, the server sends the extended warranty success message to the client that sent the first extended warranty request to notify the client. Correspondingly, the client displays a prompt message, which is used to prompt the user that the first policy has been successfully extended, so that the staff of the third-party institution can view the extended warranty progress in a timely manner. Among them, the specific content of the prompt message can be set according to actual needs, and this application does not make any limitations on this.

[0092] For the data processing method provided in this application, this embodiment explains the extended warranty process from the perspective of the underwriting system. By deploying an intermediate layer system including a client and a server, in the extended warranty process, the server is used as an information transmission intermediary to receive and send extended warranty requests, realizing the transfer of extended warranty information between the client and the underwriting system, and realizing the automation of the extended warranty process. There is no need for a third-party institution to provide extended warranty information to the insurance institution offline through communication methods such as emails, improving the extended warranty efficiency.

[0093] In Figure 2 and Figure 3 In the extended warranty process shown, the third-party personnel upload the extended warranty information on the client, and the server sends the extended warranty information to the underwriting system in the form of a request. This method can guarantee the security of the information compared with communication methods such as emails, reducing the possibility of information leakage.

[0094] Figure 4 It is a schematic diagram of an extended warranty process provided by this application. As Figure 4 shown, in the extended warranty process, the staff of the third-party institution log in to the intermediate layer system on the client, trigger the client to send the extended warranty information to the server, for example, in the form of a first extended warranty request, so that the server sends the extended warranty information to the underwriting system, for example, in the form of a second extended warranty request. Correspondingly, the underwriting personnel review the extended warranty information. If the review is passed, the underwriting system generates an extended warranty policy and uploads the extended warranty policy to the policy database. In addition, the underwriting system also sends an extended warranty success message to the server, so that the server sends an extended warranty success message to the client.

[0095] Based on the above embodiments, the staff of the third-party institution can also view the policy information in the client. Correspondingly, the data processing method provided by this application further includes:

[0096] The server receives a policy viewing request sent by the client, and the policy viewing request carries the policy identifier corresponding to the second policy; the server obtains the policy information stored corresponding to the policy identifier from the policy database; the server sends the policy information stored corresponding to the policy identifier to the client, so that the client can display based on the policy information.

[0097] Among them, the policy viewing request is used to request the server to view the policy information of the second policy. The second policy can be any policy with a policy viewing requirement. Optionally, the second policy can be an unextended warranty policy or an extended warranty policy, and this application does not make any limitations on this.

[0098] If the staff of the third-party institution has a viewing requirement for the second policy, they can log in to the account on the client and trigger a policy viewing instruction, thereby triggering the client to send a policy viewing request to the server. For example, the staff of the third-party institution can upload the policy identifier of the second policy on the client, so that the client can generate a policy viewing request carrying the policy identifier.

[0099] Optionally, if the user only needs to view a certain information field in the second policy, they can also upload the field identifier of the information field together when uploading the policy identifier. Correspondingly, the policy viewing request also carries the field identifier.

[0100] The policy database stores the policy information corresponding to each policy. Exemplarily, the policy identifier and the policy information corresponding to the same policy are stored corresponding to each other in the policy database for easy query. The server queries the policy information stored corresponding to the policy identifier from the policy database with the policy identifier corresponding to the second policy as the index. The client can display the policy information in the form of a table item for the staff to view.

[0101] If the policy viewing request also carries a field identifier, the server can query the corresponding information field from the obtained policy information with the field identifier as the index, and send the information field to the client, so that the client can display based on the information field.

[0102] The middle-layer system in this application provides a policy viewing function, which is convenient for users to view policies and has high convenience. The middle-layer system in this embodiment does not store policy information, but is stored by the policy database, and this method can ensure the security of policy information.

[0103] Figure 5It is a schematic diagram of an insurance policy viewing process provided by this application. As Figure 5 shown, in the insurance policy viewing process, the staff of a third-party institution trigger the client to send the policy identifier of the second insurance policy to the server, for example, in the form of an insurance policy viewing request. The server obtains the insurance policy information stored corresponding to the policy identifier from the insurance policy database and sends the insurance policy information to the client.

[0104] Based on the above embodiment, the staff of the third-party institution can also modify the insurance policy information in the client. Correspondingly, the data processing method provided by this application further includes:

[0105] If the staff of the third-party institution has a need to modify the first information field in the third insurance policy, they can log in to the account on the client and trigger a policy modification instruction, thereby triggering the client to send a first insurance policy modification request to the server. Among them, the first insurance policy modification request is used to request the server to modify the insurance policy information of the third insurance policy. The third insurance policy can be any insurance policy with a need for policy modification. It should be noted that the third insurance policy can be an insurance policy without extended warranty, or an insurance policy with extended warranty. For example, the staff of the third-party institution can upload the policy identifier corresponding to the third insurance policy and the field identifier corresponding to the first information field to be modified on the client, so as to facilitate the client to generate the first insurance policy modification request. Exemplarily, the first information field can be any modifiable information field in the third insurance policy, such as certain terms, insurance amount, beneficiary information, etc. The field identifier is used to uniquely identify a specific information field in the insurance policy, such as the field name or other identifiers that can uniquely determine the information field.

[0106] Correspondingly, the server receives the first insurance policy modification request sent by the client; the first insurance policy modification request carries the policy identifier corresponding to the third insurance policy and the field identifier corresponding to the first information field to be modified in the third insurance policy; the server obtains the insurance policy information stored corresponding to the policy identifier from the insurance policy database and obtains the first information field corresponding to the field identifier from the insurance policy information; the server sends a first insurance policy modification response to the client, and the first insurance policy modification response carries the first information field. After receiving the first insurance policy modification response, the client displays the first information field on the interface, so that the staff of the third-party institution can edit the first information field to obtain the second information field and trigger the client to send the second information field to the server. It can be seen that the second information field is obtained by modifying the first information field.

[0107] Correspondingly, the server receives the second information field sent by the client, and the server sends a second insurance policy modification request to the underwriting system. The second insurance policy modification request carries the second information field, and the second insurance policy modification request is used to request the underwriting system to modify the insurance policy information of the third insurance policy.

[0108] Accordingly, the underwriting system receives the second insurance policy modification request, generates an information review task for reviewing the second information field, and issues the information review task to the account of the reviewer; the underwriting system obtains the review result uploaded by the account, and when the review result indicates that the review is passed, updates the third insurance policy based on the second information field; the underwriting system sends a modification success message to the server; the server sends a modification success message to the client.

[0109] Among them, since the second information field uploaded by the staff of the third-party institution on the client may be incorrect, it is necessary to review the second information field. In this embodiment, the underwriting system generates an information review task and issues the information review task to the account of the reviewer, so that the reviewer can log in to the account in the underwriting system, view and process the information review task, and upload the review result.

[0110] Among them, the task information of the information review task carries the second information field, so that the reviewer can view and review whether the second information field is incorrect.

[0111] Among them, the review result is used to indicate whether the review is passed or not. If the review is passed, it means that the second information field is correct; if the review is not passed, it means that the second information field is incorrect and needs to be modified.

[0112] In the case where the review is passed, the underwriting system directly updates the third insurance policy. In some embodiments, the second insurance policy modification request carries the policy identifier corresponding to the third insurance policy; accordingly, updating the third insurance policy based on the second information field includes: updating the second information field to the policy information of the third insurance policy in the policy database to obtain a new third insurance policy.

[0113] In the case where the review is not passed, the underwriting system can return a review failure message to the server, and the review failure message is used to indicate that the review of the second information field fails. Accordingly, the server sends the review failure information to the client, so that the client can prompt the user, so that the staff of the third-party institution can modify the second information field through the client and re-upload it, thereby triggering the client to send a new first insurance policy modification request to the server, and the first insurance policy modification request carries the new second information field.

[0114] Among them, the modification success message is used to indicate that the first information field has been successfully modified to the second information field. In this embodiment, after receiving the modification success message, the server sends the modification success message to the client that sent the first insurance policy modification request to notify the client. Accordingly, the client displays a prompt message, and the prompt message is used to prompt the user, so that the staff of the third-party institution can view the modification progress in time. Among them, the specific content of the prompt message can be set according to actual needs, and this application does not make any limitations on this.

[0115] The intermediate layer system in this application provides a policy modification function, which is convenient for users to modify policies and has high convenience.

[0116] Figure 6 It is a schematic diagram of a policy modification process provided by this application. As Figure 6 shown, in the policy modification process, the staff of the third-party institution trigger the client to send a first policy modification request to the server. The first policy modification request carries the policy identifier corresponding to the third policy and the field identifier corresponding to the information field to be modified (such as the first information field). The server obtains the information field to be modified from the policy database, for example, and returns the information field to the client. The staff of the third-party institution modify the information field on the client to obtain the modified information field (such as the second information field), and trigger the client to send the modified information field to the server. The server sends the modified information field to the underwriting system. The underwriting personnel review the modified information field. If the review is passed, the modified information field is updated to the policy database to obtain a new third policy.

[0117] Figure 7 It is a schematic diagram of the structure of a data processing device provided by this application. As Figure 7 shown, in this embodiment, the data processing device 30 can be set on the server of the intermediate layer system. The data processing device 30 includes:

[0118] A receiving module 301, configured to receive a first extended warranty request sent by the client; the first extended warranty request includes the extended warranty information of the first policy;

[0119] A sending module 302, configured to send a second extended warranty request to the underwriting system. The second extended warranty request includes the extended warranty information, so that the underwriting system reviews the extended warranty information in response to the second extended warranty request and generates an extended warranty policy and returns an extended warranty success message when the review is passed;

[0120] The sending module 302 is further configured to send an extended warranty success message to the client.

[0121] In some embodiments, it further includes:

[0122] The receiving module 301 is further configured to receive a policy viewing request sent by the client; the policy viewing request carries the policy identifier corresponding to the second policy;

[0123] An obtaining module, configured to obtain the policy information stored corresponding to the policy identifier from the policy database;

[0124] The sending module 302 is further configured to send the policy information stored corresponding to the policy identifier to the client, so that the client displays based on the policy information.

[0125] In some embodiments, it further includes:

[0126] A receiving module 301, further configured to receive a first insurance policy modification request sent by a client; the first insurance policy modification request carries a policy identifier corresponding to a third insurance policy and a field identifier corresponding to a first information field to be modified in the third insurance policy;

[0127] An obtaining module, configured to obtain the insurance policy information stored corresponding to the policy identifier from an insurance policy database, and obtain the first information field corresponding to the field identifier from the insurance policy information;

[0128] A sending module 302, further configured to send a first insurance policy modification response to the client, and the first insurance policy modification response carries the first information field;

[0129] The receiving module 301 is further configured to receive a second information field sent by the client, and the second information field is obtained by modifying the first information field;

[0130] The sending module 302 is further configured to send a second insurance policy modification request to an underwriting system; the second insurance policy modification request carries the second information field, so that the underwriting system audits the second information field in response to the second insurance policy modification request, and updates the third insurance policy based on the second information field when the audit is passed.

[0131] The data processing device 30 provided in this embodiment can execute the technical solutions of the corresponding method embodiments, and its implementation principle and technical effects are similar to those of the corresponding method embodiments, and will not be described in detail here.

[0132] Figure 8 It is a schematic structural diagram of another data processing device provided by the present application. As Figure 8 shown, in this embodiment, the data processing device 40 can be set in an underwriting system. The data processing device 40 includes:

[0133] A receiving module 401, configured to receive a second extended warranty request sent by a server; the second extended warranty request includes extended warranty information of a first insurance policy, and the second extended warranty request is sent by the server when receiving a first extended warranty request sent by a client;

[0134] A generating module 402, configured to generate an extended warranty audit task for auditing the extended warranty information, and send the extended warranty audit task to the account of an auditor;

[0135] The generating module 402 is further configured to obtain the audit result uploaded by the account, and generate an extended warranty insurance policy when the audit result indicates that the audit is passed;

[0136] A sending module 403, configured to send an extended warranty success message to the server, so that the server sends an extended warranty success message to the client.

[0137] In some embodiments, it further includes:

[0138] A receiving module 401, further configured to receive a second insurance policy modification request sent by the server; the second insurance policy modification request carries a second information field, and the second information field is obtained by modifying a first information field to be modified in a third insurance policy;

[0139] A generating module 402, further configured to generate an information review task for reviewing the second information field, and send the information review task to the account of the reviewer;

[0140] An obtaining module, configured to obtain the review result uploaded by the account, and update the third insurance policy based on the second information field when the review result indicates that the review is passed;

[0141] A sending module 403, further configured to send a modification success message to the server, so that the server sends a modification success message to the client.

[0142] In some embodiments, the second insurance policy modification request carries an insurance policy identifier corresponding to the third insurance policy; when updating the third insurance policy based on the second information field, the obtaining module is specifically configured to: update the second information field to the insurance policy information of the third insurance policy in the insurance policy database to obtain a new third insurance policy.

[0143] The data processing apparatus 40 provided in this embodiment may execute the technical solutions of the corresponding method embodiments, and its implementation principles and technical effects are similar to those of the corresponding method embodiments, and will not be elaborated here.

[0144] An embodiment of the present application further provides an electronic device. The electronic device may be provided as a server in an intermediate layer system or an underwriting system. For example, the electronic device is provided as a server.

[0145] Figure 9 It is a schematic structural diagram of an electronic device provided by the present application. As Figure 9 shown, the electronic device 50 includes: a processor 501 and a memory 502 communicatively connected to the processor 501.

[0146] The memory 502 stores computer-executable instructions; the processor 501 executes the computer-executable instructions stored in the memory 502 to implement the data processing method provided by the present application.

[0147] Among them, in the embodiments of the present application, the memory 502 and the processor 501 are connected through a bus. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc.

[0148] The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described herein and / or claimed. The various components are interconnected using different buses and can be mounted on a common motherboard or otherwise installed as needed.

[0149] In an exemplary embodiment, a computer-readable storage medium is further provided. Computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the data processing method provided by the present application.

[0150] In an exemplary embodiment, a computer program product is further provided, including a computer program, and when the computer program in the computer program product is executed by a processor, it is used to implement the data processing method provided by the present application.

[0151] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0152] Furthermore, it should be noted that although the steps in the flowchart are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowchart 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 alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

[0153] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0154] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0155] When the integrated unit / module is implemented in the form of hardware, the hardware can be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a controller, a microcontroller, a microprocessor, or other electronic components. Unless otherwise specified, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as a USB flash drive, a Random-Access Memory (RAM), a Static Random-Access Memory (SRAM), a Dynamic Random-Access Memory (DRAM), an Enhanced Dynamic Random-Access Memory (EDRAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), an Erasable Programmable Read-Only Memory (EPROM), a Programmable read-only memory (PROM), a Read-Only Memory (ROM), a High-Bandwidth Memory (HBM), or a Hybrid Memory Cube (HMC), etc., which are various media that can store program code.

[0156] When the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a memory and includes several instructions for causing an electronic device to execute all or part of the steps of the methods of the various embodiments of the present application.

[0157] In the above embodiments, the descriptions of the various embodiments each have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0158] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include the common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the claims.

[0159] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A data processing method, characterized in that, The middle - layer system includes a client and a server. The method is applied to the server and includes: Receiving a first extended warranty request sent by the client; the first extended warranty request includes extended warranty information of a first insurance policy; Sending a second extended warranty request to the underwriting system, the second extended warranty request including the extended warranty information, so that the underwriting system audits the extended warranty information in response to the second extended warranty request and generates an extended warranty policy and returns an extended warranty success message when the audit passes; Sending the extended warranty success message to the client.

2. The method according to claim 1, wherein It also includes: Receiving a policy viewing request sent by the client; The policy viewing request carries a policy identifier corresponding to a second insurance policy; Obtaining policy information stored corresponding to the policy identifier from the policy database; Sending the policy information stored corresponding to the policy identifier to the client, so that the client displays based on the policy information.

3. The method according to claim 1, wherein It also includes: Receiving a first policy modification request sent by the client; the first policy modification request carries a policy identifier corresponding to a third insurance policy and a field identifier corresponding to a first information field to be modified in the third insurance policy; Obtaining policy information stored corresponding to the policy identifier from the policy database, and obtaining the first information field corresponding to the field identifier from the policy information; Sending a first policy modification response to the client, the first policy modification response carrying the first information field; Receiving a second information field sent by the client, and the second information field is obtained by modifying the first information field; Sending a second policy modification request to the underwriting system; The second policy modification request carries the second information field, so that the underwriting system audits the second information field in response to the second policy modification request and updates the third insurance policy based on the second information field when the audit passes.

4. A data processing method, characterized in that, The middle - layer system includes a client and a server. The method is applied to the underwriting system. The method includes: Receiving a second extended warranty request sent by the server; the second extended warranty request includes extended warranty information of a first insurance policy, and the second extended warranty request is sent by the server when it receives a first extended warranty request sent by the client; Generating an extended warranty audit task for auditing the extended warranty information and sending the extended warranty audit task to the account of the auditor; Obtaining the audit result uploaded by the account, and generating an extended warranty policy when the audit result indicates that the audit passes; Sending an extended warranty success message to the server, so that the server sends the extended warranty success message to the client.

5. The method according to claim 4, wherein It also includes: Receiving a second policy modification request sent by the server; The second policy modification request carries a second information field, and the second information field is obtained by modifying a first information field to be modified in a third insurance policy; Generating an information audit task for auditing the second information field and sending the information audit task to the account of the auditor; Obtain the review result uploaded by the account, and update the third insurance policy based on the second information field when the review result indicates that the review is passed; Send a modification success message to the server so that the server sends the modification success message to the client.

6. The method according to claim 5, wherein The second insurance policy modification request carries the policy identifier corresponding to the third insurance policy; the updating the third insurance policy based on the second information field includes: Update the second information field to the policy information of the third insurance policy in the policy database to obtain a new third insurance policy.

7. A data processing device, characterized in that, The middle layer system includes a client and a server, the device is arranged in the server, and the device includes: A receiving module, configured to receive a first extended warranty request sent by the client; the first extended warranty request includes the extended warranty information of the first insurance policy; A sending module, configured to send a second extended warranty request to the underwriting system, the second extended warranty request includes the extended warranty information, so that the underwriting system audits the extended warranty information in response to the second extended warranty request and generates an extended warranty policy and returns an extended warranty success message when the audit is passed; The sending module is further configured to send the extended warranty success message to the client.

8. A data processing device, characterized in that, The middle layer system includes a client and a server, the device is arranged in the underwriting system, and the device includes: A receiving module, configured to receive a second extended warranty request sent by the server; the second extended warranty request includes the extended warranty information of the first insurance policy, and the second extended warranty request is sent by the server when it receives the first extended warranty request sent by the client; A generating module, configured to generate an extended warranty review task for reviewing the extended warranty information and send the extended warranty review task to the account of the reviewer; The generating module is further configured to obtain the review result uploaded by the account, and generate an extended warranty policy when the review result indicates that the review is passed; A sending module, configured to send an extended warranty success message to the server so that the server sends the extended warranty success message to the client.

9. An electronic device, characterized in that, Includes: A processor and a memory communicatively connected to the processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the data processing method according to any one of claims 1 to 3 or the data processing method according to any one of claims 4 to 6.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer execution instructions, and when the computer execution instructions are executed by a processor, they are used to implement the data processing method according to any one of claims 1 to 3 or the data processing method according to any one of claims 4 to 6.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the data processing method according to any one of claims 1 to 3 or the data processing method according to any one of claims 4 to 6.

Images