Insurance claim settlement method, device and equipment based on CA authentication and storage medium

Abstract

The invention relates to the technical field of data security and the field of insurance science and technology, and discloses an insurance claim settlement method based on CA authentication, which comprises the following steps: receiving personal identity information and insurance claim settlement data of a user through a CA authentication terminal, performing identity authentication, generating a digital certificate containing a public key and a private key after auditing by the CA authentication terminal, and storing the digital certificate and the private key in a database; the method comprises the following steps: performing digital signature on insurance claim settlement data by using a private key, generating electronic signature data, performing associated storage on the electronic signature data and the insurance claim settlement data, performing distributed storage by adopting a block chain technology, verifying the electronic signature data by using a public key when an insurance claim settlement application is received, and performing claim settlement processing after verification is passed. According to the method, the digital certificate and the private key are generated through the CA authentication terminal, digital signature is performed on the insurance claim settlement data by using the private key, the authenticity and the security of the signature are ensured, and the signature data and the insurance claim settlement data are stored in a distributed manner in combination with the block chain technology, so that the data cannot be tampered.

Description

Technical Field

[0001] The present invention relates to the fields of data security technology and insurance technology, and in particular to an insurance claims settlement method, device, equipment and storage medium based on CA authentication. Background Art

[0002] With the continuous development of Internet technology, the business processing of the insurance industry has gradually moved towards digitalization and informatization, and the daily operational efficiency of insurance companies has been significantly improved. However, despite the increasing electronicization of business processes, many links in the insurance claims process still rely on traditional paper signatures, which exposes many obvious shortcomings.

[0003] First, inefficiency is one of the main problems with paper signatures. The insurance claim process is cumbersome, especially in large-scale claims such as group insurance and agricultural insurance. Signing a large number of documents requires customers to be present in person or by mail, which consumes a lot of time and manpower, seriously affecting the processing speed of insurance claims. In addition, insurance companies need specialized personnel and equipment to process these paper documents, further increasing operating costs.

[0004] Secondly, the authenticity and anti-counterfeiting ability of signatures are also major defects of traditional paper signatures. Paper signatures are easy to be forged and tampered with, and there is a lack of effective technical means to verify the authenticity of signatures. In the process of insurance claims, problems such as false signatures and irregular signatures often occur, which not only increases the insurance company's claims risk, but also provides opportunities for fraud. Especially in group agricultural insurance business, due to the large number of customers, false signatures and inconsistent signatures are more common, which brings great challenges to supervision.

[0005] Thirdly, the difficulty in storing and managing signed documents is also a key issue. Paper signed documents are easily damaged or lost during the storage process, and the search and retrieval process is cumbersome, which adds an additional burden to the insurance company's document management and compliance review. Due to the long process of document circulation, the documents are easily affected by human or environmental factors, and it is difficult to ensure their integrity and long-term security. In large-scale claims business, the problem of document security management is particularly prominent, which not only increases the management cost of insurance companies, but also affects customers' claims experience.

[0006] In addition, although electronic signature technology has been applied in some fields, the applicability of ordinary electronic signatures in insurance claims business is still limited. Electronic signatures have certain deficiencies in terms of security and legal effectiveness. Especially in insurance claims scenarios that require high security and reliability, ordinary electronic signature technology cannot completely prevent signature forgery and tampering. At the same time, the legal effect of electronic signatures has not been consistently recognized in all jurisdictions, increasing the compliance risks of insurance companies when handling cross-regional claims. These technical and legal deficiencies have led to the fact that electronic signatures have not yet completely replaced traditional paper signatures. Summary of the invention

[0007] The main purpose of the present invention is to provide an insurance claims method, device, equipment and storage medium based on CA authentication, aiming to solve the technical problems of low efficiency, insufficient security and difficulty in ensuring the authenticity of signatures in the insurance claims process of existing signature technologies.

[0008] To achieve the above object, the present invention provides an insurance claim settlement method based on CA authentication, comprising:

[0009] Receive the user's personal identity information and insurance claim information through the CA authentication terminal and perform identity authentication;

[0010] Review the personal identity information and insurance claim information through a CA authentication terminal, and generate a digital certificate containing a public key and a private key based on the personal identity information and insurance claim information;

[0011] Use the private key to digitally sign the insurance claim information to generate electronic signature data;

[0012] The electronic signature data is associated with the insurance claim information and stored in a distributed manner using blockchain technology;

[0013] When an insurance claim application is received, the electronic signature data is verified using the public key in the digital certificate, and the claim is processed after the verification is passed.

[0014] Furthermore, to achieve the above-mentioned purpose, the present invention provides an insurance claim settlement device based on CA authentication, comprising:

[0015] User registration and authentication module, used to receive the user's personal identity information and insurance claim information through the CA authentication terminal, and perform identity authentication;

[0016] A CA authentication module, used to review the personal identity information and insurance claim information through a CA authentication terminal, and generate a digital certificate containing a public key and a private key based on the personal identity information and insurance claim information;

[0017] An electronic signature generation module, used to digitally sign the insurance claim information using the private key to generate electronic signature data;

[0018] A signature data storage and management module is used to associate and store the electronic signature data with insurance claim information, and use blockchain technology for distributed storage;

[0019] The insurance claim processing module is used to verify the electronic signature data using the public key in the digital certificate when receiving an insurance claim application, and to process the claim after the verification is passed.

[0020] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a computer device, which includes a memory, a processor, and an insurance claim settlement program based on CA certification stored in the memory and executable on the processor, wherein the insurance claim settlement program based on CA certification, when executed by the processor, implements the steps of the insurance claim settlement method based on CA certification as described above.

[0021] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a computer-readable storage medium, on which a CA-certified insurance claim procedure is stored. When the CA-certified insurance claim procedure is executed by a processor, the steps of the CA-certified insurance claim method as described above are implemented.

[0022] Beneficial effects: The present invention relates to the fields of data security technology and insurance technology, and discloses an insurance claim method based on CA authentication. The user's personal identity information and insurance claim information are received through a CA authentication terminal, and identity authentication is performed. After review, the CA authentication terminal generates a digital certificate and a private key containing a public key, and uses the private key to digitally sign the insurance claim information to generate electronic signature data. The electronic signature data is associated with the insurance claim information and stored, and distributed storage is performed using blockchain technology. When receiving an insurance claim application, the public key is used to verify the electronic signature data, and the claim is processed after the verification is passed. The present invention generates a digital certificate and a private key through a CA authentication terminal, and uses the private key to digitally sign the insurance claim information to ensure the authenticity and security of the signature, and combines the blockchain technology to distribute the signature data and the insurance claim information to ensure that the data cannot be tampered with. The process of using the public key to verify the signature ensures that the claim information has not been tampered with during the transmission and storage process, further improving the security and reliability of the insurance claim processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0024] Figure 1 A schematic diagram of an application environment of an insurance claim settlement method based on CA authentication in an embodiment of the present invention;

[0025] Figure 2 It is a flowchart of an embodiment of an insurance claim settlement method based on CA authentication of the present invention;

[0026] Figure 3 It is a functional module diagram of a preferred embodiment of the insurance claim settlement device based on CA authentication of the present invention;

[0027] Figure 4 A schematic diagram of the structure of a computer device in one embodiment of the present invention;

[0028] Figure 5 FIG. 4 is another schematic diagram of the structure of a computer device in one embodiment of the present invention. DETAILED DESCRIPTION

[0029] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0030] The insurance claim settlement method based on CA authentication provided by the embodiment of the present invention can be applied in the following aspects: Figure 1 In the application environment, the user terminal communicates with the service terminal through the network. The service terminal can submit user identity information and insurance claim information to the CA authentication terminal through the user terminal for identity authentication. After review, the CA authentication terminal generates a digital certificate and a private key containing a public key, uses the private key to digitally sign the insurance claim information, generates electronic signature data, and stores the electronic signature data in association with the insurance claim information. Blockchain technology is used for distributed storage. When receiving an insurance claim application, the public key is used to verify the electronic signature data, and the claim processing is performed after the verification is passed. The present invention generates a digital certificate and a private key through a CA authentication terminal, uses the private key to digitally sign the insurance claim information, ensures the authenticity and security of the signature, and combines the blockchain technology to distribute the signature data and the insurance claim information to ensure that the data cannot be tampered with. The process of using the public key to verify the signature ensures that the claim information has not been tampered with during the transmission and storage process, further improving the security and reliability of the insurance claim processing. Among them, the user terminal can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers and portable wearable devices. The server can be implemented with an independent server or a server cluster composed of multiple servers. The present invention is described in detail below through specific embodiments.

[0031] See also Figure 2 , Figure 2 This is a flowchart of an embodiment of an insurance claim settlement method based on CA authentication provided by the present invention. It should be noted that although a logical sequence is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0032] like Figure 2 As shown, the insurance claim settlement method based on CA authentication proposed by the present invention includes the following steps:

[0033] S10, receiving the user's personal identity information and insurance claim information through the CA authentication terminal, and performing identity authentication;

[0034] In this embodiment, the user's personal identity information is collected, including name, ID number, contact information (such as mobile phone number), etc. This information is the basis for verifying the user's true identity and plays an important role in the entire insurance claims process. The system receives the personal identity information entered by the user through a preset user interface or APP, and transmits it through an SSL / TLS encrypted channel to ensure that the information will not be stolen or tampered with during transmission. The collected information will be stored in the insurance company's database and transmitted to the CA authentication terminal for subsequent verification.

[0035] Collect the insurance claim-related information submitted by the user, which may include insurance contracts, proof of loss, claim application forms, etc. This information is used together with the user's identity information for subsequent verification and processing of claims. Users can submit claim-related information in the form of uploading electronic files, and the system will conduct preliminary verification of the format and content of these files to ensure the integrity of the information. The uploaded files will be packaged together with the user's identity information, encrypted and sent to the CA authentication terminal.

[0036] In order to ensure the security of user identity information and insurance claims data during transmission, the data must be encrypted and sent to the CA certification terminal using a secure transmission protocol. After the system collects user information and claims data, it uses asymmetric encryption technology (such as RSA or ECC) to encrypt sensitive information, generate ciphertext, and securely transmit it to the CA certification terminal via the SSL / TLS protocol. The encryption key is only held by the CA certification terminal at the receiving end, ensuring that the data will not be intercepted or decrypted by a third party during transmission.

[0037] Send the encrypted user identity information and insurance claim information to the CA certification terminal for identity authentication and information review. Submit the encrypted data to the CA certification terminal through the secure API interface. After receiving the data, the CA certification terminal decrypts and reviews the user identity information and claim information to ensure the authenticity of the user identity and the integrity and legality of the information. For example, when a user submits identity information and claim information through the insurance company's website, the web front end uses HTML5 encryption technology to process the user information, encrypts it and transmits it to the server, and then submits it to the CA certification terminal.

[0038] Example: During the agricultural insurance claim process, a farmer submitted a claim application because his crops were damaged by floods. The farmer uploaded his identity certificate and related loss proof materials through the mobile application provided by the insurance company. After the system encrypted these materials, it submitted them to the CA authentication terminal for identity review and material verification. After the review was passed, the insurance company immediately processed the claim application and finally completed the claim under the premise of ensuring the security and authenticity of the materials, effectively protecting the interests of the farmer.

[0039] Through the above steps, the authenticity and security of user identity information and insurance claim materials are ensured. The use of encryption technology and secure transmission protocols prevents user sensitive information from being stolen or tampered with during transmission, and the participation of CA authentication terminals improves the authority of identity authentication. Ultimately, the safe submission of insurance claim materials is achieved, effectively avoiding information leakage and improper claims.

[0040] S20, reviewing the personal identity information and insurance claim information through a CA authentication terminal, and generating a digital certificate including a public key and a private key based on the personal identity information and insurance claim information;

[0041] In this embodiment, the CA authentication terminal is responsible for reviewing the identity information and insurance claim information submitted by the user, verifying the authenticity of the user's identity and the legality of the submitted information. The audit content includes verifying whether the personal identity information (such as ID number, name, etc.) is consistent with the insurance company's records, and checking whether the submitted insurance claim information meets the requirements. The CA authentication terminal verifies the user's identity information through a preset database or data connection with a third-party certification agency (such as public security, taxation, etc.). The information review is verified through the insurance company's internal system to ensure that the submitted claim information is consistent with the actual situation. Information comparison uses hash algorithms and database indexing technology to ensure efficient and accurate identity authentication and information review.

[0042] After the user's identity information and insurance claim information are reviewed, the CA certification terminal generates the user's public key and private key based on an asymmetric encryption algorithm. The public key will be used for subsequent signature verification, while the private key will be used by the user to sign the claim information. The CA certification terminal uses an asymmetric encryption algorithm (such as RSA or ECC algorithm) to generate a pair of keys - a public key and a private key. The private key is stored in the secure hardware module of the user's device (such as a smart card or a trusted execution environment TEE) to ensure that it will not be tampered with or stolen. The public key is recorded in the database of the CA certification terminal for subsequent signature verification.

[0043] The CA authentication terminal uses the user's public key to generate a digital certificate. The digital certificate contains the user's public key and other identity information as the proof of the user's digital signature. The digital certificate provides the authentication basis for the electronic signature of subsequent insurance claims. The CA authentication terminal generates a digital certificate in accordance with the X.509 standard. The certificate contains the user's public key, identity information, certificate serial number and validity period, and is signed by the CA organization's private key to ensure the legitimacy and credibility of the certificate. The generated digital certificate can be passed to the insurance company through a secure API interface and stored in the insurance company's authentication database for easy reference during claims processing.

[0044] The user's private key and public key must be stored securely, and ensure that the private key will not be leaked during transmission or storage. The public key is used for subsequent signature verification and needs to be securely transmitted to the insurance company and other relevant parties. The private key is stored in the secure hardware module of the user's device, such as a smart card, encrypted USB device, or a secure chip of a mobile device to ensure that the private key cannot be illegally accessed. The public key is transmitted to the insurance company and the CA certification terminal through the SSL / TLS secure channel for subsequent verification operations. For example, the CA certification terminal uses the elliptic curve cryptography (ECC) algorithm to generate a key pair. Compared with the RSA algorithm, ECC can provide the same level of security at a smaller key length. The generated private key is stored in the trusted execution environment (TEE) of the user's device, and the public key is embedded in the digital certificate generated by the CA.

[0045] The CA certification terminal reviews the information submitted by the user and generates public and private keys, ensuring the authenticity and legitimacy of the user's identity and providing a secure foundation for the subsequent electronic signature of insurance claims. The generation and management of digital certificates make the signature legally effective, ensuring the credibility and anti-counterfeiting of the signed data in the claims process. The application of asymmetric encryption technology ensures the security of the private key and avoids security risks in the signing process.

[0046] S30, using the private key to digitally sign the insurance claim information to generate electronic signature data;

[0047] In this embodiment, before digital signing, the content of the insurance claim information needs to be hashed to generate a fixed-length hash value (digest). The hash value can uniquely represent the content of the information. The content of the insurance claim information is hashed using a standard hash algorithm (such as SHA-256 or SHA-3). The hash algorithm maps files of any length to a fixed-length digest, ensuring that each file has a unique digest. If the file content changes, the hash value will change accordingly.

[0048] The generated hash value needs to be encrypted with the user's private key, and the encrypted hash value is the electronic signature. Through this encryption process, anyone can decrypt and verify the validity of the signature with the user's public key to ensure that the data has not been tampered with. The hash value is encrypted using the private key in an asymmetric encryption algorithm (such as RSA or ECC algorithm). The encrypted hash value is encapsulated as electronic signature data, which is anti-counterfeiting and cannot be tampered with. The encryption process is usually completed in a secure environment on the user's device to ensure the security of the private key.

[0049] The encrypted hash value is combined with the user's identity information to generate electronic signature data, which is used in the subsequent signature verification process. The system packages the encrypted hash value with the user's digital certificate (including the user's public key and identity information) to generate electronic signature data. This data will be attached to the insurance claim information and used for subsequent verification. The entire process can be completed through a smart card, a trusted execution environment (TEE) or an encrypted USB device to ensure that the private key is not leaked.

[0050] Example: In a group medical insurance claim scenario, a user submits a hospital diagnosis certificate, expense list, and other information. The system generates a hash value for these information using SHA-256 and digitally signs them using the user's private key. After the electronic signature is generated, the system attaches the signature to the claim information and then submits it to the insurance company. When the insurance company receives the claim application, it verifies the electronic signature using the user's public key to confirm that the information has not been tampered with, and then completes the claim process. This digital signature process ensures the authenticity of each claim document and reduces the risk of false claims.

[0051] By using a private key to digitally sign insurance claim information, the generated electronic signature data can effectively prevent the claim information from being tampered with, ensuring the authenticity and legitimacy of the signature. Hash processing ensures that the signature is only for the content of the information, not the entire document, reducing the computational burden. At the same time, the use of private key encryption allows only those with the public key to verify the signature, ensuring that the signature cannot be forged. The entire process improves the security of the insurance claim process and avoids fraud caused by signature forgery or data tampering.

[0052] S40, storing the electronic signature data in association with the insurance claim information, and using blockchain technology for distributed storage;

[0053] In this embodiment, a unique association must be established between the electronic signature data and the insurance claim information to ensure that it can be verified later whether the signature actually corresponds to the claim information. This association is usually implemented through a unique identifier (such as a hash value or a file ID). The system generates a unique identifier (such as a hash value) for each claim information, and then stores the identifier in association with the generated electronic signature data. The association method can be to directly attach the signature data to the metadata part of the insurance claim file, or to logically bind the signature data to the claim file through the associated field of the database table. Ensure that the correspondence between the signature and the claim file can be verified at any time through the identifier.

[0054] The storage of electronic signature data and insurance claims information requires the use of blockchain technology to ensure the immutability and distributed storage characteristics of the data. The distributed ledger of the blockchain can effectively prevent the risks caused by single-point data storage and ensure that each claim data can be accurately recorded. Each linked insurance claim information and electronic signature data will be packaged as a block in the blockchain. The system broadcasts the packaged blocks to multiple nodes in the blockchain network through a consensus mechanism, which are verified and stored by these nodes. The storage method adopts the chain structure commonly seen in blockchains, and subsequent blocks are linked to the previous blocks through encrypted hashes to ensure that the timestamp and content of each piece of data are securely recorded. Each node holds a complete copy of the ledger to ensure that even if individual nodes fail, other nodes can retain the data intact.

[0055] The distributed storage and consensus mechanism of blockchain technology ensures that data is stored on multiple nodes, and once the record is completed, the data cannot be tampered with. Through this mechanism, the security and integrity of electronic signature data and insurance claims information are guaranteed. The data in each block includes the hash value of the previous block, the hash value of the current block, the timestamp, the electronic signature data, and the unique identifier of the insurance claims information. Through the chain structure of the blockchain, any change will cause the hash value of the subsequent block to become invalid, thereby quickly detecting data tampering. Insurance companies or third parties can verify the integrity of each claim data at any time through the nodes in the blockchain network.

[0056] Example: In agricultural insurance claims, a farmer submitted claims information and completed the electronic signature. The insurance system associated the farmer's electronic signature data with the claims information through a generated unique identifier and packaged it into the blockchain network. Multiple nodes in the network verified and stored the data to ensure that the data cannot be tampered with. A few months later, the insurance company needed to review the farmer's claims record. The system verified the integrity of the claims information and signature data through the blockchain to ensure that the claims documents had not been tampered with at any time after submission, and finally completed the review and settlement process of the claims.

[0057] By associating electronic signature data with insurance claim information and using blockchain technology for distributed storage, the anti-counterfeiting and anti-tampering capabilities of claim information are ensured. The distributed ledger of blockchain allows data to be stored in multiple nodes, ensuring that even if individual nodes fail or are attacked, the data remains safe and effective. In addition, the anti-tampering mechanism provided by the blockchain network ensures that claim information and signature data cannot be tampered with, improving the transparency and security of the claim process.

[0058] S50, when receiving an insurance claim application, the electronic signature data is verified using the public key in the digital certificate, and after the verification is passed, the claim is processed.

[0059] In this embodiment, the insurance company receives the insurance claim application submitted by the user, including the user's claim information and the electronic signature data previously generated by the digital signature. This step provides input for subsequent signature verification and claim processing. The insurance claim system receives the claim application submitted by the user through an online platform, APP or other digital channels. The system stores the received application in the database and triggers the subsequent signature verification process. The claim application data includes the user's insurance claim information and the attached electronic signature.

[0060] Extract the public key for signature verification from the user's digital certificate. This public key is issued by the CA certification terminal and is the only tool used to decrypt the user's private key encrypted signature. The claims system retrieves and verifies the user's digital certificate by calling the API of the CA certification terminal, and extracts the public key associated with the user's identity. The extracted public key will be used to verify whether the electronic signature submitted by the user is valid. The public key extraction process is completed through a secure protocol (such as SSL / TLS) to ensure the security of data transmission.

[0061] The electronic signature submitted by the user is verified using the public key to ensure that the signature data matches the claim information and confirm that the information has not been tampered with. The system calls an asymmetric encryption algorithm (such as RSA or ECC) to decrypt the electronic signature using the public key and obtain the original hash value. Next, the system hashes the insurance claim information submitted by the user to generate a new hash value. The decrypted hash value is compared with the newly generated hash value. If the two are consistent, it proves that the information has not been tampered with and the signature verification is passed. Otherwise, the system will issue a warning indicating that the signature or information may have been tampered with.

[0062] On the premise that the signature verification is passed, the system enters the claim processing process, reviews the user's claim application in accordance with the insurance contract, and completes the claim payment operation. After the verification is passed, the system further reviews the claim information according to the terms of the insurance contract to confirm whether the user meets the claim conditions. After that, the system triggers the automatic or manual claim process. The approved claim application will enter the payment processing stage, and the funds will be transferred to the user's account through a bank or a third-party payment platform. The entire process is automatically recorded by the system for subsequent review and compliance verification.

[0063] Example: In an agricultural insurance claim scenario after a natural disaster, a farmer submitted a claim application through the insurance company's website, along with electronic signature data and claim information. After receiving the application, the insurance company extracted the farmer's digital certificate public key through the API of the CA authentication terminal and used the public key to verify the electronic signature data. After the verification, the system reviewed the claim information and confirmed that the farmer's claim request met the contract terms, then triggered the automatic payment process, and the compensation was directly transferred to the farmer's bank account.

[0064] By using the public key in the user's digital certificate to verify the electronic signature data, the authenticity and integrity of the claim information is ensured. The electronic signature verification process can effectively prevent the claim information from being tampered with or forged, improving the security and credibility of the claim processing. After the signature verification is passed, the system can automatically trigger the claim process, improving processing efficiency and reducing possible errors in manual operations. In addition, the use of digital certificates ensures the uniqueness and legitimacy of the public key, making the entire claim process more transparent and standardized.

[0065] The present invention relates to the fields of data security technology and insurance technology, and discloses an insurance claim method based on CA authentication. The user's personal identity information and insurance claim information are received through a CA authentication terminal, and identity authentication is performed. After review, the CA authentication terminal generates a digital certificate and a private key containing a public key, uses the private key to digitally sign the insurance claim information, generates electronic signature data, and stores the electronic signature data in association with the insurance claim information. Blockchain technology is used for distributed storage. When receiving an insurance claim application, the public key is used to verify the electronic signature data, and the claim is processed after the verification is passed. The present invention generates a digital certificate and a private key through a CA authentication terminal, uses the private key to digitally sign the insurance claim information, ensures the authenticity and security of the signature, and combines the blockchain technology to distribute the signature data and the insurance claim information to ensure that the data cannot be tampered with. The process of using the public key to verify the signature ensures that the claim information has not been tampered with during the transmission and storage process, further improving the security and reliability of the insurance claim processing.

[0066] In one embodiment, the above S10 includes:

[0067] S101, obtaining the user's personal identity information and insurance claim information, and encrypting the personal identity information and insurance claim information to generate encrypted information;

[0068] S102, submitting the encrypted information to a CA authentication terminal through a secure channel;

[0069] S103, receiving the encrypted information through the CA authentication terminal and performing identity authentication, and when the identity authentication is successful, entering the review stage.

[0070] In this embodiment, the system needs to collect the user's personal identity information (such as name, ID number, contact information, etc.) and insurance claim information (such as claim application form, loss certificate, etc.). This information is used for subsequent identity verification and review of claim applications. Users submit personal identity information and claim information through the insurance company's online platform, mobile APP or other digital channels. The system saves the information in a temporary database to ensure the integrity and availability of the data. While collecting information, the system will perform format verification to ensure that the submitted information is complete and correct, such as verifying the format of the telephone number and ID number through regular expressions, or checking the integrity of the claim information through form verification.

[0071] In order to protect the user's privacy and data security, the system encrypts the user's personal identity information and insurance claim information. The encrypted information will be transmitted to the CA certification terminal in ciphertext to ensure data security during transmission. The system uses an asymmetric encryption algorithm (such as RSA or ECC) to encrypt the user's identity information and insurance claim information. The generated encrypted information contains the user's personal data and claim information, ensuring that it will not be stolen or tampered with during transmission. The encryption process is completed by the security module on the server side. The user's data is encrypted with the public key and stored in the database in ciphertext form, waiting for further transmission.

[0072] The system submits the encrypted information to the CA certification terminal through a secure network transmission channel to ensure that the data will not be leaked or tampered with during the transmission process. The establishment of a secure channel is a key link in the secure transmission of data. The system uses the SSL / TLS encryption protocol to establish a secure transmission channel and transmit the encrypted information to the server of the CA certification terminal through HTTPS. The SSL / TLS protocol provides encryption, integrity verification and identity authentication functions to ensure that the information is not illegally eavesdropped or tampered with during the transmission process. In addition, the transmission process can ensure that the CA certification terminal and the insurance company's server are legal and credible through two-way authentication.

[0073] After receiving the encrypted information, the CA authentication terminal first decrypts the information, extracts the user's personal identity information and claim information, and then authenticates the user's identity. The success or failure of the identity authentication determines the start of the next review process. The CA authentication terminal decrypts the received encrypted information with a private key and verifies the user's personal information using a pre-set identity authentication system. The authentication method may include verifying key information such as ID card number and mobile phone number and comparing them with authoritative data sources (such as public security systems or banking systems) to ensure the legitimacy and accuracy of the user's identity. Through database queries and third-party data source interfaces, the CA authentication terminal can quickly verify the user's identity. When the authentication is passed, the system will enter the review stage.

[0074] Example: During a customer's claim for crop loss due to a natural disaster, the customer submitted his identity certificate, insurance contract, and loss certificate through the insurance company's mobile app. The system first encrypts these materials and the customer's identity information, generates ciphertext, and securely sends it to the CA authentication terminal through the SSL / TLS channel. After receiving the encrypted information, the CA authentication terminal uses its private key to decrypt and verify the customer's identity. After the authentication is passed, the customer's claim application enters the insurance company's review stage. The entire process ensures the security and authenticity of customer data and avoids information leakage or forgery.

[0075] This embodiment collects the user's personal identity information and insurance claim information, and uses asymmetric encryption technology to encrypt the data, which can ensure the security of user information during transmission and processing. The encrypted information is submitted to the CA authentication terminal through a secure channel to ensure that the data will not be stolen or tampered with during transmission. The CA authentication terminal decrypts the information and performs identity authentication with its private key, effectively ensuring the authenticity of the user's identity and the integrity of the information, and providing a safe and reliable foundation for the smooth progress of the subsequent insurance claim process.

[0076] In one embodiment, the above S20 includes:

[0077] S201, matching and comparing the personal identity information with a pre-established identity information database to verify the authenticity of the personal identity information;

[0078] S202, verifying the integrity of the insurance claim information based on a preset information list;

[0079] S203, when the personal identity information and insurance claim information are verified, a key pair including a public key and a private key is generated using an asymmetric encryption algorithm;

[0080] S204, combining the personal identity information with the public key to generate a certificate signing request;

[0081] S205: Submit the certificate signing request to a CA authentication terminal, and the CA authentication terminal signs the certificate signing request using the private key to generate a digital certificate.

[0082] In this embodiment, the system extracts key information (such as ID number, name, contact information, etc.) from the personal identity information submitted by the user, and matches and compares it with the identity information database of the CA authentication terminal or the third-party authentication platform to verify whether the identity information provided by the user is true. The CA authentication terminal will use an internal or external identity database (such as data from the public security bureau, bank or third-party authentication platform) to verify the information submitted by the user. Through the interface connection, the user's identity information is compared with the records in the database to ensure that the submitted information is consistent with the authoritative data source. This process can use a hash algorithm to accelerate the matching process and realize real-time connection with external data sources through an API.

[0083] After verifying personal identity information, the CA certification terminal further checks whether the insurance claim information submitted by the user is complete and meets the preset information list requirements. Only complete claim information will enter the subsequent process. The CA certification terminal or the insurance company has pre-set a claim information list, which clearly defines the materials that must be submitted for each claim application. The system automatically compares the file list of the claim information to ensure that the submitted information includes all necessary items, such as the claim application form, loss certificate, insurance contract, etc. If there is any missing, the system will generate a notification to prompt the user to supplement the information. The data structure of each claim document can be standardized in XML or JSON format for automatic verification.

[0084] After personal identity information and insurance claim information are verified, the CA authentication terminal generates a public key and a private key pair through an asymmetric encryption algorithm. The private key is used for user signatures, and the public key is used for subsequent signature verification. The CA authentication terminal calls an encryption algorithm (such as RSA, ECC, etc.) to generate a key pair. The private key is used to digitally sign the user's insurance claim information, and the public key is embedded in the user's digital certificate. In order to ensure the security of the private key, the private key is generally only generated and saved in the user's device, while the public key is stored by the CA authentication terminal and associated with the user's digital certificate.

[0085] Generate a Certificate Signing Request (CSR), which contains the user's personal identity information and the generated public key. The CSR request is used to apply for a digital certificate from a CA authentication terminal. The system creates a CSR based on the user's personal information and the generated public key. The CSR usually contains the user's public key, organizational information (such as the company the user belongs to), username, etc., and the CSR is signed with the user's private key. The CSR is a standardized request sent to a CA authentication terminal to apply for a digital certificate.

[0086] The CA authentication terminal receives the certificate signing request (CSR), signs the CSR with the CA's private key, generates the final digital certificate, and returns the digital certificate to the user. The CA authentication terminal signs the CSR with its CA private key to generate a digital certificate that complies with the X.509 standard. The certificate contains the user's public key, identity information, and information about the issuing authority. After the digital certificate is issued, the CA authentication terminal will store it in its own public key infrastructure (PKI), and users and third parties can query and verify the legitimacy of the certificate through PKI. The final generated digital certificate will be stored in the user's device or server for subsequent signature verification.

[0087] This embodiment ensures the authenticity of the identity information by matching and verifying the user's personal identity information with the identity information database; and ensures that the submitted information meets the requirements by checking the integrity of the claim information. After the verification is passed, the CA authentication terminal generates a public key and a private key to ensure the security and authenticity of the signature data. Finally, a legal and valid digital certificate is generated through the submission of a certificate signing request (CSR) and the signature of the CA authentication terminal, providing a reliable authentication basis for subsequent electronic signatures. This process improves the security, reliability and automation level of the insurance claims process.

[0088] In one embodiment, the above S30 includes:

[0089] S301, using a hash algorithm to perform hash processing on the content of the insurance claim information to generate a hash value;

[0090] S302, encrypting the hash value using the private key to generate an encrypted hash value;

[0091] S303, encapsulating the encrypted hash value into electronic signature data, and associating the electronic signature data with the insurance claim information.

[0092] In this embodiment, before digital signing, the content of the insurance claim information is hashed. The hash algorithm is a one-way encryption algorithm that maps an input of arbitrary length to an output (hash value) of fixed length, and the hash value can uniquely identify the file content. The system uses a standard hash algorithm (such as SHA-256 or SHA-3) to hash the text or file of the insurance claim information. The output of the algorithm is a hash value of fixed length, representing the content of the insurance claim information. Any changes to the claim information will result in a different hash value being generated to ensure the uniqueness of each claim information. This process is completed on the user device or server, and the hash value will not expose the specific content of the claim information.

[0093] The generated hash value needs to be encrypted with the user's private key to form a digital signature. The encrypted hash value can be used to verify whether the claim information has been tampered with, while ensuring the non-repudiation of the data. The system calls an asymmetric encryption algorithm (such as RSA or ECC algorithm) and encrypts the hash value with the user's private key. The encrypted hash value is the electronic signature, which can ensure the integrity and non-forgeability of the data. The private key is stored in the secure hardware module of the user's device (such as the trusted execution environment TEE or smart card), and the signing process is performed in a trusted environment to prevent the leakage of the private key.

[0094] The encrypted hash value is associated with the insurance claim information to form complete electronic signature data. The electronic signature data contains both the encrypted hash value and the public key information used for verification. This data will be bound to the insurance claim information for subsequent signature verification. The system encapsulates the encrypted hash value into an electronic signature data structure, which usually includes the signature algorithm, the encrypted hash value, the signer's identity information and public key, etc. The system associates the electronic signature with the insurance claim information through a unique identifier (such as a file ID or hash value) to ensure the validity and traceability of the signature. This association can be made by attaching signature information to the file metadata or by associating through database records.

[0095] In one specific implementation, SHA-256 can be used to hash the insurance claim data to generate a 256-bit hash value. The SHA-256 algorithm can process large amounts of data with high security. The RSA-2048 algorithm can also be used for encryption. The hash value after private key encryption is 2048 bits long, and the generated electronic signature can resist complex cryptanalysis attacks. The signature data is encapsulated into the PKCS#1 format, which includes not only the encrypted hash value, but also metadata such as the signature timestamp and signature algorithm identifier to improve the transparency and traceability of signature verification. The signature time is obtained through the timestamp server, and the timestamp information of the signature is added during the signature data encapsulation process to ensure that the signature process is completed at the specified time to prevent subsequent tampering or forgery.

[0096] This embodiment uses a hash algorithm to hash the insurance claim information, ensuring the uniqueness and integrity of each claim information. The private key is used to encrypt the hash value to generate electronic signature data, ensuring the authenticity and non-tamperability of the signature data, and preventing the claim information from being forged or tampered with. Finally, the encrypted hash value is associated with the insurance claim information to ensure a one-to-one correspondence between the signature and the information, which is convenient for subsequent verification. The security, integrity and anti-counterfeiting of the insurance claim business are enhanced, and the credibility of the signature data is improved.

[0097] In one embodiment, the above S40 includes:

[0098] S401, associating the electronic signature data with the insurance claim information through a unique identifier;

[0099] S402, encapsulating the associated electronic signature data and insurance claim information into blockchain data in a blockchain transaction format;

[0100] S403, submitting the packaged blockchain data to the blockchain network, and verifying the received blockchain data through the nodes in the blockchain network;

[0101] S404, the verified blockchain data is added to the distributed ledger of the blockchain, and the blockchain data in the distributed ledger is backed up through each node in the blockchain network;

[0102] S405, generate and provide storage proof to prove that the electronic signature data and insurance claim information have been stored on the blockchain.

[0103] In this embodiment, to ensure the unique association between the electronic signature data and the insurance claim information, the system assigns a unique identifier to each insurance claim information and signature data, and associates the two through this identifier. The system generates a unique identifier based on the content of the insurance claim information (such as using SHA-256 to generate a unique hash value for the claim file), which identifies both the claim information and the electronic signature data. The unique identifier will be used as a key field in the blockchain transaction to logically associate the claim information with the electronic signature data and store them in the same block.

[0104] The associated electronic signature data and insurance claim information are packaged in a transaction format that complies with the blockchain platform, which ensures that the data can be effectively transmitted and processed in the blockchain network. Depending on the blockchain platform used (such as Ethereum, Hyperledger, etc.), the system will package the electronic signature data and insurance claim information into a blockchain transaction format (such as JSON or a proprietary blockchain data format). The packaged data includes signature data, a unique identifier for the insurance claim information, a signature timestamp, and other information. The transaction packaging process includes generating a transaction header, setting the destination address of the transaction, and verifying data integrity.

[0105] The encapsulated blockchain data is submitted to the blockchain network, and multiple nodes verify the transaction to ensure the integrity and legitimacy of the data. The system broadcasts the encapsulated blockchain data through the transaction channel of the blockchain network. After receiving the transaction data, multiple nodes will verify the data according to the consensus mechanism of the blockchain (such as PoW, PoS or PBFT). The node will check the validity of the signature data, the correctness of the unique identifier, and confirm that the data has not been tampered with. Through encryption and signature verification, the node ensures the authenticity of the data.

[0106] When a node successfully verifies blockchain data, the data will be added to the blockchain's distributed ledger as a new block, and all nodes will back up this data. The verified blockchain data will be recorded in the blockchain's distributed ledger. Each node maintains a complete copy of the ledger to ensure that the data is permanently recorded. Whenever a new block is added to the blockchain, all nodes will update the ledger synchronously to maintain consistency. Even if a node fails, the backups of other nodes can ensure the integrity and security of the data.

[0107] After the system successfully stores the electronic signature data and insurance claim information in the blockchain, it will generate a storage proof to prove that the data has been successfully recorded and can be verified at any time. The system generates a hash value for each successfully recorded transaction as a storage proof, which can be queried by users or third parties to verify whether the data has been stored on the blockchain. The storage proof can be verified through a blockchain browser or smart contract call. The storage proof is usually generated in the form of a transaction ID, and users can query the ID to obtain the claim data and signature records stored on the blockchain.

[0108] This embodiment ensures the anti-counterfeiting, non-tampering and high transparency of the data by associating the electronic signature data with the insurance claim information and using blockchain technology for distributed storage. The signature data is associated with the claim information through a unique identifier to ensure the accurate correspondence of each piece of data. The distributed storage and verification mechanism of the blockchain network provides a high degree of security and reliability. Even if some nodes fail, the backup of other nodes can ensure the integrity and availability of the data. The generation of storage proof provides users and insurance companies with transparent storage proof, which facilitates auditing and verification and enhances the credibility of the claim process.

[0109] In one embodiment, in the above S50, when receiving an insurance claim application, the electronic signature data is verified using the public key in the digital certificate, including:

[0110] S501, when receiving an insurance claim application, extracting a public key for electronic signature verification from the digital certificate;

[0111] S502, obtaining electronic signature data associated with the insurance claim information;

[0112] S503, decrypting the electronic signature data using the public key to obtain the original hash value;

[0113] S504, recalculating the hash value of the insurance claim information and comparing it with the original hash value obtained by decryption;

[0114] S505: If the comparison results are consistent, the electronic signature is confirmed to be valid and the verification is successful.

[0115] In this embodiment, when receiving an insurance claim application, the system needs to extract the public key used to verify the electronic signature from the user's digital certificate. The public key is generated by the CA authentication terminal and bound to the user's identity information, and is the core of verifying the electronic signature data. The system queries the user's digital certificate from the insurance company database or through the online verification system and extracts the public key therein. The public key is usually stored in X.509 format, and the system will obtain the public key information through the key management field in the digital certificate for subsequent signature verification. The entire extraction process is ensured by the SSL / TLS protocol to ensure security and avoid data leakage.

[0116] The system extracts the associated electronic signature data from the received insurance claim information. The signature data contains the encrypted hash value and other signature information. The system searches and extracts the electronic signature data associated with the claim information through the unique identifier of the claim information (such as the file hash value or file ID). The electronic signature data usually includes information such as the encrypted hash value, the signature timestamp, and the signature algorithm identifier. The system parses this information to ensure that the extracted signature data corresponds to the claim information one by one.

[0117] Use the public key extracted from the digital certificate to decrypt the electronic signature data and obtain the original hash value generated when signing. The decryption process ensures that the hash value is generated by the user's private key encryption, which is unique and unforgeable. The system uses the public key in an asymmetric encryption algorithm (such as RSA or ECC) to decrypt the electronic signature data. The decryption process verifies the legitimacy of the signature data and restores the hash value at the time of signing. If the decryption fails, the system will issue a warning indicating that the signature data may have been tampered with or invalid. The decrypted hash value will be used for subsequent comparison and verification.

[0118] The system performs hash processing on the insurance claim information received, generates a new hash value, and compares the hash value with the original hash value obtained by decryption to determine whether the claim information has been tampered with after signing. The system uses the same hash algorithm as when signing (such as SHA-256 or SHA-3) to recalculate the hash value of the claim information. The generated new hash value is compared with the decrypted hash value. If the two are consistent, it means that the claim information has not been modified after signing; if the two are inconsistent, the system prompts that the signature verification failed, indicating that the claim information may have been tampered with. The comparison result will serve as the basis for whether the signature verification is passed.

[0119] If the recalculated hash value is consistent with the original decrypted hash value, the system confirms that the electronic signature is valid, the signature verification is successful, and the insurance company can continue to process the claim application. After the system confirms the validity of the signature through the comparison result, it records the successful verification log and marks the claim information as verified. After the verification is passed, the system will continue to enter the insurance claim processing process to ensure that the claim application is legal and complies with the insurance terms. If the verification fails, the system will automatically trigger the alarm mechanism, refuse to process the claim application and notify relevant personnel for further investigation.

[0120] This embodiment ensures the integrity and authenticity of insurance claim data by using the public key in the digital certificate to decrypt the electronic signature data and compare the decrypted hash value with the recalculated hash value. This prevents the possibility of data tampering and ensures the security and fairness of the claim process. In addition, the application of asymmetric encryption technology ensures that the signature cannot be forged and improves the reliability of signature verification.

[0121] In one embodiment, in the above S50, after the verification is passed, the claim settlement process is performed, including:

[0122] S506, after verification, determining applicable insurance terms based on the content of the insurance claim application and the insurance claim information;

[0123] S507, analyzing whether the insurance claim application meets the claim conditions based on the insurance terms;

[0124] S508, based on the insurance claim application, determining the required auxiliary materials, prompting the user to submit and receiving the auxiliary materials;

[0125] S509, analyzing the risk level of the claim application based on the insurance claim information and the auxiliary information based on the risk assessment model;

[0126] S510, comprehensively evaluate the insurance terms, claim conditions, insurance claim information and auxiliary information to generate a claim decision result.

[0127] In this embodiment, after the electronic signature verification is passed, the system needs to automatically match the relevant insurance clauses based on the insurance claim application content and claim information submitted by the user to ensure that the clauses in the insurance contract are correctly applied for claim assessment. The system uses text analysis technology (such as natural language processing NLP) to parse the key information in the insurance claim application and claim information, and matches the applicable insurance clauses from the insurance contract database. The matching process automatically matches the user's insurance type, insurance coverage, insurance liability, etc. to ensure that the correct clauses are selected for subsequent claim review.

[0128] The system evaluates the user's insurance claim application based on the applicable insurance terms and conditions to determine whether the application meets the claim conditions. This process ensures that the claim application submitted by the user is within the scope of the law and contract. The system automatically evaluates the legality and validity of the claim application through the rule engine. The rule engine will compare the claim application with the compensation conditions in the insurance terms (such as the scope of loss, the upper limit of the compensation amount, etc.) to determine whether the application meets the claim conditions in the law and insurance contract. The system will also call the historical claim records and the user's policy records for further verification to ensure that the application does not exceed the compensation limit.

[0129] If the claim application requires additional information, the system will prompt the user to submit the required supporting information and receive the information for further review. This supporting information may include additional proof of loss, photos or medical reports. When reviewing insurance claim applications, the system automatically identifies the missing required information and generates a detailed list of supporting information. Users will receive a list of supporting information that needs to be submitted via email, mobile phone notification or platform message. After the user uploads it, the system will verify the integrity and format of the information, and automatically store and associate the information.

[0130] The system uses a risk assessment model to assess the risk level of insurance claims. This assessment is based on insurance claims information, auxiliary information, and historical claims data to help insurance companies identify potential fraud or high-risk claims. The system uses a machine learning model or a rule-based risk assessment engine to analyze the risk factors of claims. The model may include multiple dimensions such as the user's claim history, claim amount, claim frequency, loss type, etc. The system will classify applications based on risk scores, and claims with high risk levels will be further manually reviewed or investigated to reduce the risk of fraud.

[0131] The system generates the final claim decision by comprehensively evaluating the insurance terms, claim application content, claim information submitted by the user and auxiliary information, and determines whether to agree to compensation and the amount of compensation. The system uses a decision engine or expert system to conduct a final review of all relevant data, including applicable insurance terms, claim conditions, submitted information, risk assessment results, etc. Based on the evaluation results, the system automatically generates a claim decision, which can be approval of the claim, partial claim, or rejection of the claim. At the same time, the system generates a claim report and sends it to the user and the relevant internal audit team.

[0132] Example: In the scenario of agricultural insurance claims, a farmer submitted a claim for crop losses due to a natural disaster. The system first verifies the electronic signature of the application, and after confirming its validity, it automatically matches the insurance terms related to the farmer to assess whether his claim application meets the conditions. The system prompts the farmer to submit additional photos of the loss, and after receiving these auxiliary materials, it uses the risk assessment model to assess the risk of the claim application. Finally, the system comprehensively evaluates all relevant data, generates a claim decision, agrees to the claim and pays the compensation, ensuring that the claims process is fast, transparent and compliant.

[0133] This embodiment uses an automated claims processing system to enable insurance companies to efficiently and accurately process claims applications. This reduces possible errors caused by manual intervention and improves the speed and transparency of claims review. By comprehensively evaluating insurance terms, claims conditions, risk factors, and supporting information, the system can provide insurance companies with comprehensive claims decision support, while effectively identifying and reducing potential fraud risks through risk assessment models.

[0134] In one embodiment, a CA-authenticated insurance claim settlement device is provided, and the CA-authenticated insurance claim settlement device corresponds one-to-one to the CA-authenticated insurance claim settlement method in the above embodiment. Figure 3 , Figure 3 This is a functional module diagram of a preferred embodiment of the insurance claim settlement device based on CA authentication of the present invention. User registration and authentication module 10, CA authentication module 20, electronic signature generation module 30, signature data storage and management module 40 and insurance claim settlement processing module 50. The functional modules are described in detail as follows:

[0135] The user registration and authentication module 10 is used to receive the user's personal identity information and insurance claim information through the CA authentication terminal and perform identity authentication;

[0136] CA authentication module 20, used to review the personal identity information and insurance claim information through a CA authentication terminal, and generate a digital certificate containing a public key and a private key according to the personal identity information and insurance claim information;

[0137] An electronic signature generation module 30, for digitally signing the insurance claim information using the private key to generate electronic signature data;

[0138] The signature data storage and management module 40 is used to associate the electronic signature data with the insurance claim information and store it in a distributed manner using blockchain technology;

[0139] The insurance claim processing module 50 is used to verify the electronic signature data using the public key in the digital certificate when receiving an insurance claim application, and to perform claim processing after the verification is passed.

[0140] In one embodiment, the user registration and authentication module 10 is specifically used to:

[0141] Obtaining the user's personal identity information and insurance claim information, and encrypting the personal identity information and insurance claim information to generate encrypted information;

[0142] Submitting the encrypted information to the CA authentication terminal through a secure channel;

[0143] The encrypted information is received through the CA authentication terminal and identity authentication is performed. When the identity authentication is successful, the review stage is entered.

[0144] In one embodiment, the CA authentication module 20 is specifically used to:

[0145] Matching and comparing the personal identity information with a pre-established identity information database to verify the authenticity of the personal identity information;

[0146] Verify the integrity of the insurance claim information based on a preset list of information;

[0147] When the personal identity information and insurance claim information are verified, an asymmetric encryption algorithm is used to generate a key pair including a public key and a private key;

[0148] Combining the personal identity information with the public key to generate a certificate signing request;

[0149] The certificate signing request is submitted to a CA authentication terminal, and the CA authentication terminal signs the certificate signing request using the private key to generate a digital certificate.

[0150] In one embodiment, the electronic signature generation module 30 is specifically used to:

[0151] Use a hash algorithm to hash the contents of insurance claim information and generate a hash value;

[0152] Encrypting the hash value using the private key to generate an encrypted hash value;

[0153] The encrypted hash value is encapsulated into electronic signature data, and the electronic signature data is associated with the insurance claim information.

[0154] In one embodiment, the signature data storage and management module 40 is specifically used to:

[0155] Associating the electronic signature data with the insurance claim data via a unique identifier;

[0156] Encapsulate the associated electronic signature data and insurance claim information into blockchain data in a blockchain transaction format;

[0157] Submit the packaged blockchain data to the blockchain network, and verify the received blockchain data through the nodes in the blockchain network;

[0158] The verified blockchain data is added to the distributed ledger of the blockchain, and the blockchain data in the distributed ledger is backed up by each node in the blockchain network;

[0159] Generate and provide storage proof to prove that electronic signature data and insurance claim information are stored on the blockchain.

[0160] In one embodiment, the insurance claim processing module 50 is specifically used to:

[0161] When receiving an insurance claim application, extracting a public key for electronic signature verification from the digital certificate;

[0162] Obtaining electronic signature data associated with the insurance claim data;

[0163] Decrypting the electronic signature data using the public key to obtain the original hash value;

[0164] Recalculating the hash value of the insurance claim information and comparing it with the original hash value obtained by decryption;

[0165] If the comparison results are consistent, the electronic signature is confirmed to be valid and the verification is successful.

[0166] In one embodiment, the insurance claim processing module 50 is specifically used to:

[0167] After verification, the applicable insurance terms will be determined based on the content of the insurance claim application and the insurance claim information;

[0168] Analyze whether the insurance claim application meets the claim conditions based on the insurance terms;

[0169] Based on the insurance claim application, determine the required auxiliary materials, prompt the applicant to submit and receive the auxiliary materials;

[0170] Analyze the risk level of the claim application based on the insurance claim information and supporting information based on the risk assessment model;

[0171] Comprehensively evaluate insurance terms, claim conditions, insurance claim information and auxiliary information to generate claim decision results.

[0172] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 4As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external user terminal via a network connection. When the computer program is executed by the processor, it implements a function or step on the service side of an insurance claim method based on CA certification.

[0173] In one embodiment, a computer device is provided. The computer device may be a user terminal, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server through a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the user side of a CA-authenticated insurance claim method.

[0174] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

[0175] Receive the user's personal identity information and insurance claim information through the CA authentication terminal and perform identity authentication;

[0176] Review the personal identity information and insurance claim information through a CA authentication terminal, and generate a digital certificate containing a public key and a private key based on the personal identity information and insurance claim information;

[0177] Use the private key to digitally sign the insurance claim information to generate electronic signature data;

[0178] The electronic signature data is associated with the insurance claim information and stored in a distributed manner using blockchain technology;

[0179] When an insurance claim application is received, the electronic signature data is verified using the public key in the digital certificate, and the claim is processed after the verification is passed.

[0180] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0181] Receive the user's personal identity information and insurance claim information through the CA authentication terminal and perform identity authentication;

[0182] Review the personal identity information and insurance claim information through a CA authentication terminal, and generate a digital certificate containing a public key and a private key based on the personal identity information and insurance claim information;

[0183] Use the private key to digitally sign the insurance claim information to generate electronic signature data;

[0184] The electronic signature data is associated with the insurance claim information and stored in a distributed manner using blockchain technology;

[0185] When an insurance claim application is received, the electronic signature data is verified using the public key in the digital certificate, and the claim is processed after the verification is passed.

[0186] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can refer to the relevant descriptions on the server side and the user side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0187] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0188] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0189] It should be noted that if software tools or components other than those of the Company appear in the embodiments of the present application, they are only used for illustration and do not represent actual use. The above-described embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the above-mentioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the above-mentioned embodiments can still be modified, or some of the technical features thereof can be replaced by equivalents; and these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. An insurance claim settlement method based on CA authentication, characterized in that: The following steps are involved: Receive the user's personal identity information and insurance claim information through the CA authentication terminal and perform identity authentication; Review the personal identity information and insurance claim information through a CA authentication terminal, and generate a digital certificate containing a public key and a private key based on the personal identity information and insurance claim information; Use the private key to digitally sign the insurance claim information to generate electronic signature data; The electronic signature data is associated with the insurance claim information and stored in a distributed manner using blockchain technology; When an insurance claim application is received, the electronic signature data is verified using the public key in the digital certificate, and the claim is processed after the verification is passed.

2. The insurance claim settlement method based on CA authentication as claimed in claim 1, characterized in that: The CA authentication terminal receives the user's personal identity information and insurance claim information and performs identity authentication, including: Obtaining the user's personal identity information and insurance claim information, and encrypting the personal identity information and insurance claim information to generate encrypted information; Submitting the encrypted information to the CA authentication terminal through a secure channel; The encrypted information is received through the CA authentication terminal and identity authentication is performed. When the identity authentication is successful, the review stage is entered.

3. The insurance claim settlement method based on CA authentication as claimed in claim 1, characterized in that: The personal identity information and insurance claim information are reviewed by the CA authentication terminal, and a digital certificate and private key containing a public key are generated based on the personal identity information and insurance claim information, including: Matching and comparing the personal identity information with a pre-established identity information database to verify the authenticity of the personal identity information; Verify the integrity of the insurance claim information based on a preset list of information; When the personal identity information and insurance claim information are verified, an asymmetric encryption algorithm is used to generate a key pair including a public key and a private key; Combining the personal identity information with the public key to generate a certificate signing request; The certificate signing request is submitted to a CA authentication terminal, and the CA authentication terminal signs the certificate signing request using the private key to generate a digital certificate.

4. The insurance claim settlement method based on CA authentication as claimed in claim 1, characterized in that: The insurance claim data is digitally signed using the private key to generate electronic signature data, including: Use a hash algorithm to hash the contents of insurance claim information and generate a hash value; Encrypting the hash value using the private key to generate an encrypted hash value; The encrypted hash value is encapsulated into electronic signature data, and the electronic signature data is associated with the insurance claim information.

5. The insurance claim settlement method based on CA authentication as claimed in claim 1, characterized in that: The electronic signature data is stored in association with the insurance claim information, and distributed storage is performed using blockchain technology, including: Associating the electronic signature data with the insurance claim data via a unique identifier; Encapsulate the associated electronic signature data and insurance claim information into blockchain data in a blockchain transaction format; Submit the packaged blockchain data to the blockchain network, and verify the received blockchain data through the nodes in the blockchain network; The verified blockchain data is added to the distributed ledger of the blockchain, and the blockchain data in the distributed ledger is backed up by each node in the blockchain network; Generate and provide storage proof to prove that electronic signature data and insurance claim information are stored on the blockchain.

6. The insurance claim settlement method based on CA authentication as claimed in claim 1, characterized in that: When receiving an insurance claim application, the electronic signature data is verified using the public key in the digital certificate, including: When receiving an insurance claim application, extracting a public key for electronic signature verification from the digital certificate; Obtaining electronic signature data associated with the insurance claim data; Decrypting the electronic signature data using the public key to obtain the original hash value; Recalculating the hash value of the insurance claim information and comparing it with the original hash value obtained by decryption; If the comparison results are consistent, the electronic signature is confirmed to be valid and the verification is successful.

7. The insurance claim settlement method based on CA authentication as claimed in claim 1, characterized in that: After verification, claims processing will be carried out, including: After verification, the applicable insurance terms will be determined based on the content of the insurance claim application and the insurance claim information; Analyze whether the insurance claim application meets the claim conditions based on the insurance terms; Based on the insurance claim application, determine the required auxiliary materials, prompt the applicant to submit and receive the auxiliary materials; Analyze the risk level of the claim application based on the insurance claim information and supporting information based on the risk assessment model; Comprehensively evaluate insurance terms, claim conditions, insurance claim information and auxiliary information to generate claim decision results.

8. An insurance claim settlement device based on CA authentication, characterized in that: The insurance claim settlement device based on CA authentication includes: User registration and authentication module, used to receive the user's personal identity information and insurance claim information through the CA authentication terminal, and perform identity authentication; A CA authentication module, used to review the personal identity information and insurance claim information through a CA authentication terminal, and generate a digital certificate containing a public key and a private key based on the personal identity information and insurance claim information; An electronic signature generation module, used to digitally sign the insurance claim information using the private key to generate electronic signature data; A signature data storage and management module is used to associate and store the electronic signature data with insurance claim information, and use blockchain technology for distributed storage; The insurance claim processing module is used to verify the electronic signature data using the public key in the digital certificate when receiving an insurance claim application, and to process the claim after the verification is passed.

9. A computer device, characterized in that: The computer device includes a memory, a processor, and a CA-certified insurance claim program stored in the memory and executable on the processor. When the CA-certified insurance claim program is executed by the processor, the steps of the CA-certified insurance claim method described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The storage medium stores an insurance claim settlement program based on CA authentication, and when the insurance claim settlement program based on CA authentication is executed by the processor, the steps of the insurance claim settlement method based on CA authentication as described in any one of claims 1 to 7 are implemented.

Images