An insurance document archiving system based on a blockchain platform

Abstract

The application belongs to the technical field of blockchain technology application, and discloses an insurance document storage system based on a blockchain platform. The insurance document photo electronic data information is saved through the blockchain, the pages involved in the overall process from opening the client APP to completing the uploading operation of the user and the corresponding operation data are uploaded to the blockchain system, the authenticity of the static file is ensured, the guarantee range is increased, the security of the system is improved, the behavior of the customer is traced by the operator in the dispute process, and the backtracking ability of the system is improved.

Description

Technical Field

[0001] This invention belongs to the field of blockchain application technology and discloses an insurance policy storage system based on a blockchain platform. Background Technology

[0002] Traditional insurance policy data management methods are currently largely limited to paper document storage. Although with the application of the internet, policy-related applications have gradually moved from offline to client-side apps. For example, CN109903174A – "An Insurance Policy Input System and Method Based on Mobile Terminal Camera" provides an insurance policy input system and method based on mobile terminal camera, which greatly improves input efficiency and the accuracy of policy information parsing. However, for client-side app use, ensuring that every step is documented with images to meet the needs of increasingly online business presents challenges. Traditional methods suffer from high resource storage costs, low storage indexing efficiency, and the vulnerability of the files themselves to tampering. Furthermore, in insurance claims disputes, companies often lack evidence to prove whether user materials have been tampered with, as well as reliable user usage records, whether the user operated the system themselves, and the details of the operation process. These issues lead to incomplete evidence and significant discrepancies in the disputed information, directly impacting the final insurance customer complaint. Summary of the Invention

[0003] To address the aforementioned issues in existing scenarios, this invention provides an insurance policy document storage system based on a blockchain platform. Utilizing the immutability of blockchain, the system stores electronic data of insurance policy photos via the blockchain. Simultaneously, it uploads the entire process from the user opening the client app to completing the upload operation, including all related pages and operational data, to the blockchain system. This ensures the authenticity of static files while expanding the scope of coverage, enhancing system security, and facilitating the tracing of customer behavior through operators during disputes, thereby improving the system's traceability capabilities.

[0004] In a first aspect, an insurance policy document storage system based on a blockchain platform is provided. The storage system includes a client, a network layer, an application layer, a blockchain platform, and a storage layer. The application layer includes a backend application module and a national cryptographic algorithm module. The storage layer includes a first storage module, a second storage module, and a third storage module.

[0005] The client responds to user page operations, including: when the user opens the client's homepage (page information W1), the client takes a screenshot (saves as screenshot P1) and records the access time (saves as T1); when the user opens the insurance application guidance page (page information W2), the client takes a screenshot (saves as screenshot P2) and records the access time (saves as T2); when the user opens the insurance application initiation page (page information W3), fills in registration information, and prepares to enter the policy upload stage, the client takes a screenshot (saves as screenshot P3) and records the access time (saves as T3). The registration information includes: user name U. name ID number U no The policy duration, policy rights parameters, and policy payment cycle are specified. Simultaneously, the client initiates user authentication with the backend application module. This authentication is based on the user's token data saved by the client during registration, which includes the user's unique value U. id Login time, login method, user permissions, allowed login duration, and signature; authenticated users can proceed to the next step, the policy upload page, where the registration information is configured according to U... name U no U id The policy duration, policy rights parameters, and policy payment cycle are recorded in sequence and then combined to form the user registration information U. data ;

[0006] The network layer is used to enable remote interaction and security between the backend application module and the client, and to perform load balancing for the backend application module.

[0007] The backend application module interacts with the client to weaken the image of the original insurance policy photo uploaded by the user on the client page to reduce the image size. The weakened insurance policy photo is denoted as photo Y. IMG Meanwhile, the background application module also weakens the screenshots P1, P2, and P3 recorded by the client to generate Y. p1 Y p2 Y p3 ;

[0008] The background application module interacts with the national cryptographic algorithm module, calling the national cryptographic algorithm module to process screenshots P1, P2, P3, and Y. IMG Perform signature processing and generate T respectively. P1 T P2 T P3 T IMG ; Retrieve the unique value U assigned to the user during registration id and W1, T P1 T1, W2, T P2 T2, T P3 W3, T3, TIMG U id U data Collect the user's login device ID, i.e., D. id After concatenating the components sequentially, the national cryptographic algorithm module is called to encrypt the result, K. L ;

[0009] The backend application module interacts with the storage module. The first storage module stores unstructured data, the second storage module stores metadata information and creates an index based on date for easy retrieval, and the third storage module stores user cache information for quick querying of cached data by the backend application module. After user authentication, the backend application module calls the second storage module to store token data. After authentication, the backend application module calls the second storage module to return a unique password record value Q to the blockchain platform. pw With user unique value U id Storage is performed; after the image is uploaded, the backend application module calls the first storage module to compress the image Y. p1 Y p2 Y p3 Y IMG Store the compressed image and assign a unique value Q to the corresponding block. id Stored in the second storage module; after the backend application module initiates a transaction request by uploading an image of the insurance policy, it calls the second storage module to access W1 and T. P1 T1, W2, T P2 T2, T P3 W3, T3, T IMG U id U data Storage is performed; after the insurance policy image is uploaded to the blockchain and the transaction is completed, the backend application module verifies the unique value Q of the block. id With user unique value U id The storage module and the second storage module are used for storage; the authentication module will use U id The randomly generated salt value A is stored in the third storage module; the authentication module combines the user-generated token with U. id Stored in the third storage module;

[0010] The metadata information Y is all the information stored in the storage module;

[0011] The backend application module interacts with the blockchain platform. When the backend application module initiates a blockchain transaction request, it uploads W1, W2, W3, and U. data Did, T1, T2, T3, T P1 T P2 T P3 T IMG K L Uid Information is sent to the blockchain platform; after receiving a blockchain transaction request initiated by the backend application module, the endorsing node in the blockchain platform uses the blockchain platform to allocate U to the current user. id The public key verifies the signature of the current transaction, whether the user has the relevant access permissions to the system, the legality of the transaction, and the transaction format. After the endorsement module of the blockchain platform verifies the transaction, the backend application module initiates the blockchain to execute the transaction. The blockchain platform records the transactions, performs chaincode calculations, generates blocks, and sends the blocks to the sorting nodes for sorting. After the sorting nodes complete the sorting, the management node sends the blocks to other organization nodes for on-chain storage. After execution, the blockchain platform returns information to the backend application module, which includes the block transaction ID, i.e., Q. id The backend application module uses Q through the blockchain transaction query API. id The input parameter is used to query block information, obtain block information details, and return W1, W2, W3, U. data Did, T1, T2, T3, U id T P1 T P2 T P3 T IMG K L U id information.

[0012] Preferably, the blockchain platform is the Hyperledger Fabric platform;

[0013] Preferably, the national cryptographic algorithm module is a national cryptographic algorithm SM3 processing module;

[0014] Preferably, the image weakening operation includes the following steps: The image is processed into a two-dimensional array IMG[height][length] using the IMGIO.read() method, where each array field represents the three elements of an RPG (0-255); by traversing the array and processing each array item, the array segment is converted into a number pix = IMG.getRGB(); red is red = (pix>>16)&0xff, yellow is green = (pix>>16)&0xff, and blue is blue = pix>>0xff; the color is changed to black, and by limiting red>0, green>0, and blue>0, all colored elements are uniformly set to black (0x00ffffff); pixes are concatenated to weaken the image and reduce its size. It should be noted that this image weakening applies to the original insurance policy photo and the screenshots P1, P2, and P3.

[0015] Preferably, the first storage module is the xSky storage platform, that is, the background application module calls the xSky storage platform interface to store Yp1 Y p2 Y p3 Y IMG The process of sharding storage involves splitting each image into smaller image files, distributing them across different physical machines on the xSky storage platform using a hash algorithm, and copying each small file according to the number of copies specified in the configuration file. This ensures data integrity and prevents data loss. The high availability, scalability, and fast read performance of the xSky storage platform are utilized for storage, and historical data can be periodically transferred.

[0016] Preferably, the second storage module is a search engine ES, which can quickly find the corresponding image metadata information through relevant parameters of the metadata information; and through the unique value Q of the block. id The system performs queries and returns results via an API, verifying the accuracy of the blockchain-stored data by obtaining image and metadata information.

[0017] Preferably, the third storage module caches REDIS, improving the backend application module's ability to preprocess business logic and retrieve data quickly.

[0018] Compared with existing policy storage and verification schemes, the present invention is characterized by:

[0019] Regarding the policy generation requirements in the insurance industry, since there's a certain probability that the next interaction with the user after the policy is generated will be many years later (claims, policy return benefits), this long time span carries the risk of changes in the personnel and systems used at the time, leading to missing data. Furthermore, it's difficult for customers to collect evidence proving the details of their actions, potentially resulting in customer complaints. Regulatory agencies also have strict enforcement strategies for such complaints. To reduce disputes and the high costs and reputational damage they can cause to companies, it's necessary to fully retain all user transaction records. This is not only required for policy generation but also for policy payouts, renewals, modifications, and upgrades. The insurance policy document storage system based on the blockchain platform provided by this invention utilizes the immutability of the blockchain. Through the program, not only are the electronic data information of insurance policy photos stored on the blockchain, but also the pages involved in the entire process from the user opening the client APP to completing the upload operation and the corresponding operation data are uploaded to the blockchain system. While ensuring the authenticity of static files, the scope of protection is increased, the security of the system is improved, and it is convenient to trace the customer's behavior through the operator in the process of disputes, thereby improving the traceability of the system.

[0020] As a preferred implementation of this application, the insurance policy storage system addresses the system's security requirements by enhancing encryption methods for user login, such as password keypad generation rules and storing encrypted password content on the blockchain established herein, thereby ensuring the authenticity of user operations.

[0021] As a preferred embodiment of this application, the insurance policy storage system optimizes the system's storage by compressing the original electronic image data according to the specific characteristics of the insurance industry, thereby reducing the network traffic during transmission.

[0022] As a preferred implementation of this application, the insurance policy storage system enables rapid searching of structured data generated during system operation. It also standardizes the metadata processing of images in this document and stores the processed data in the ElasticSearch search engine. Since the data generated by this system is quite large, the processing of big data can utilize the acceleration capabilities of the search engine for rapid querying, locating block information, and improving the efficiency of the verification module. Attached Figure Description

[0023] Figure 1 This is a diagram illustrating the architecture of the insurance policy storage system on the blockchain platform of this invention.

[0024] Figure 2 This is a flowchart illustrating the user insurance application process in a specific embodiment of the present invention.

[0025] Figure 3 This is a flowchart illustrating the blockchain processing in a specific embodiment of the present invention. Detailed Implementation

[0026] To explain the solution concept in more detail, the technical solution of this invention will be described in detail below with relevant example diagrams. Taking the Hyperledger Fabric blockchain platform as an example, the operation of the insurance policy storage system based on the blockchain platform provided by this invention will be described in detail with reference to the accompanying drawings. Figure 1 The diagram shows the architecture of the insurance policy notarization system built on the Hyperledger Fabric blockchain platform according to this invention.

[0027] I. Build a blockchain-based insurance policy management platform and establish a storage platform blockchain network based on the Hyperledger Fabric open-source blockchain technology. Specifically, utilize the Hyperledger Fabric open-source code to deploy various applications and configure relevant parameters. The configuration file is as follows:

[0028] Generate certificate: Run the configuration directory according to crypto-config.yaml;

[0029] Generate the initial block: Create the channel-art directory and generate region.block in that directory;

[0030] Generate blockchain platform configuration information: Generate back.tx in the channel-art directory;

[0031] Generate registration information: Generate Org1BAGPanchors.tx and Org2BAGPanchors.tx in the channel-art directory;

[0032] Configure the docker-compose.yml file;

[0033] Start the Fabric network;

[0034] Develop the relevant Java SDK and expose the interface via HTTP protocol: Download the standard blockchain SDK-Java project and import it into Eclipse;

[0035] Modify the connection address IP in the Config utility class of the project to the IP address of your own Fabric server;

[0036] Develop the relevant Java SDK and expose the interface via HTTP protocol: Download the standard blockchain SDK-Java project and import it into Eclipse; modify the connection address IP in the Config utility class of the project to the IP address of your pre-built Fabric server; configure the FabricSDK: create a new config.yaml configuration file; build an SDK instance via API; query the chaincode and debug the SDK interface; instantiate the chaincode and write smart contracts; publish the chaincode to the compute nodes; test the data interaction with the blockchain via Java calls.

[0037] To set up the Xsky platform: Edit the / etc / hosts file on all hosts and add the relevant IP address and corresponding hostname.

[0038] Setting up ElasticSearch: Configure the elasticsearch.yml file, directly configuring data and logs, and disable configuration updates; open the ElasticSearch login page to test access;

[0039] Setting up REDIS: Modify the configuration file REDIS-serverREDIS-6380.conf;

[0040] Reference Figure 1 The overall system architecture of the insurance policy document storage and management platform is as follows:

[0041] Client-side layer: The client-side APP layer is used for the display and basic logic judgment of key pages such as login initiation, policy initiation page, and image upload page;

[0042] Network layer: Enables remote interaction and security between the backend application module and the client, and performs load balancing for the backend application module;

[0043] Application Layer: National Cryptographic Algorithm Module: This module extracts the relevant processes of the national cryptographic algorithm and microservices them, assembling the algorithm into interfaces for use by the backend application module. The backend application module is responsible for the microservice architecture, developed using Spring Cloud, and decomposes the application into authentication services, page display services, transaction submission services, image compression processing services, information query services, and blockchain transaction services. Storage Layer: This layer stores data and images related to the processes and interfaces with the backend application module, providing query functionality.

[0044] The first storage module is the xSky storage platform, meaning the background application module calls the xSky storage platform interface to store Y. p1 Y p2 Y p3 Y IMG The process of sharding storage involves splitting each image into smaller image files, distributing them across different physical machines on the xSky storage platform using a hash algorithm, and copying each small file according to the number of copies specified in the configuration file. This ensures data integrity and prevents data loss. The high availability, scalability, and fast read performance of the xSky storage platform are utilized for storage, and historical data can be periodically transferred.

[0045] The second storage module is the search engine ES, which can quickly find the corresponding image metadata information through relevant parameters of the metadata information; through the unique value Q of the block. id The system performs queries and returns results via an API, verifying the accuracy of the blockchain-stored data by obtaining image and metadata information.

[0046] The third storage module caches Redis, improving the backend application modules' ability to preprocess business logic and retrieve data quickly.

[0047] Blockchain Platform: This platform interfaces with the backend application module for shared data storage and distribution within the blockchain. It includes: a CA authentication cluster, sorting nodes, management nodes, endorsement nodes, and a submission module. The CA authentication cluster provides key distribution for the interfaced API, as well as encryption / decryption and verification functions for transaction messages. The sorting nodes queue the generated blocks. The management nodes are responsible for the network communication and data flow among all nodes in the blockchain organization. The endorsement nodes execute programs for initiated API transactions and verify program consistency. The submission module stores blockchain data and manages the links.

[0048] II. User Login Process

[0049] When the client app is opened, the login page will be opened by default if the user is not logged in.

[0050] User enters username U userno When the user clicks the password field, the client app will send the username U. userno Upon reaching the authentication module, the authentication module queries the local database to determine the username U. userno Is it correct?

[0051] The authentication module randomly generates a salt value number A and records it in the third storage module REDIS. The authentication can then be verified by pressing the number P on the keyboard. o The new character P is obtained by adding the ASCII number corresponding to the letter and A%128. n Retrieve the corresponding character image (IMG) from the file library. key This refers to the character that the character actually represents. For example, the character 'a' is converted to the character 'g'. This logic is used to sequentially retrieve all characters from the password keyboard, and the resulting character arrangement differs from the actual keyboard layout displayed on the page. In the authentication module, the key is the user's unique value U. id + Encrypt characters and store them in Redis; the client APP obtains the IMG file. key Then, a password keyboard is generated and displayed based on the logic;

[0052] Backend application management sends P o P n A, U id Obtain the unique password record Q from the blockchain platform PW The user enters the password U through the password keyboard generated by the client APP. pwd Users click to log in, and the client app sends a U (user ID). userno With password U pwd The authentication module uses a concatenated U... id +encrypted character, retrieve real user characters, retrieve the current user's real password R pwd The authentication module uses the user's unique value U id +Rpwd The system performs SM3 signature encryption to obtain Ppwd, which is then compared with the user password stored in the second storage module. If they match, authentication is successful. The authentication module generates a token (user-unique value, login time, login method, user permissions, allowed login duration, and signature) and sends it to the client APP. The client APP logs in via the password keyboard instead of the phone's built-in password keyboard, which increases password security and prevents password cracking due to message hijacking.

[0053] III. User insurance application process, such as Figure 2 As shown, the relevant operation steps are as follows:

[0054] 1. When a user enters the client app's homepage, the client app calls the backend application module to determine if it's their first login. If it is, the user is directed to the login page. The user clicks the password field and uploads their username. userno At this point, the background application module interacts with the client app to create a special keyboard using a special method. The logic for generating the special keyboard is as follows:

[0055] (1) By entering the username U userno The authentication module randomly generates a salt value A and saves it in the third storage module REDIS. The new character obtained by adding the ASCII code of the number and letter input from the keyboard to A%128 is retrieved from the file library, along with the corresponding character image (IMG). key This refers to the character that the character actually represents. For example, the character 'a' is converted into the character 'g'. This logic is used to sequentially retrieve all the characters on the keypad, and the resulting keypad arrangement differs from the actual layout displayed on the page.

[0056] (2) The authentication module uses the username U userno Call the user query interface of the backend application module to obtain the user's unique value (002234221), denoted as U. id ;

[0057] (3) The actual field mapped (numbers on the keyboard) + the key value displayed on the password keyboard + A + U id The keys are sorted according to their ASCII values, separated by commas. The authentication module calls the blockchain insertion API to store the data on the blockchain platform, which then returns the unique value Q of the password record. pw Used for record keeping.

[0058] (4) The background application module will obtain the Q pw with U id This parameter is stored in the second storage module, ElasticSearch, for easy querying and retrieval.

[0059] (5) The client APP can obtain the string U of the permutations and combinations of the password by inputting the password via the password keyboard. pwd The data is transmitted to the authentication module. The authentication module retrieves the value of 'A' by calling REDISS, for example, by passing in the parameter '202311011025'. Then, through mapping, it converts the permutations and combinations of the password string and assembles the actual password string 'R'. pwd R pw +U id The SM3 encryption is used to obtain Ppwd, which is the user password stored in the second storage module. The authentication module verifies the correctness of Ppwd by comparing it with the password.

[0060] (6) The authentication module generates token data and returns it to the client APP. The token data includes data using U... id Login time, login method, user permissions including accessible pages and interactive buttons, allowed login duration, and signature;

[0061] (7) The client APP saves token data. The client APP needs to add the token to the HTTP header for each business access request, and use it as a token for the system.

[0062] 2. After successful authentication, the user enters the client APP system; opens the homepage; the authentication module combines the token with the user ID. id Bind it and store it in the third storage module Redis;

[0063] 3. After a user logs into the system, the client APP adds a token to the message header each time it logs in. The authentication module obtains the token from the third-party storage module REDIS and verifies whether the two parties are consistent. If the verification is inconsistent, the verification is canceled and the client APP is returned to the login page.

[0064] 4. When a user browses the client APP and opens the homepage, the page information W1 is recorded. The page information includes the unique value of the page, the unique value of the previous page, the time spent on the previous page, the page notes, and the page name. The opening time is T1, for example, 20231101110000. When the user opens the insurance guidance page, the page information is W2, and the corresponding time is T2. When the user opens the insurance application page, the page information is W3, and the corresponding time is T3. When a page is opened, the screen is automatically captured and saved. The page screenshot images are recorded as P1 (P1.jpg), P2, and P3 respectively.

[0065] 5. On the insurance application page, fill in the required information and enter your user name (U). name ID number U no The policy duration, policy rights parameters, and policy payment cycle information are recorded as user registration information.data Meanwhile, the device ID collected by the client APP is recorded as D. id For example, kskskddff%kddk*;

[0066] 6. Access the image upload page in the client app. Users upload the original document image (IMG) through the client app. The image size of the IMG is reduced by weakening the image:

[0067] 7. Parse images that have been uniformly converted to JPG format by the client APP: Call the IMGIO.read() method on the IMG file to process the image into a two-dimensional array, IMG[height][length], where each array field represents the three elements of RPG (0-255); traverse the array and process each array item, converting the array segment into a number: pix = IMG.getRGB(); red is red = (pix>>16)&0xff, yellow is green = (pix>>16)&0xff, and blue is blue = pix>>0xff; change the color to black by setting red>0, green>0, and blue>0 to black (0x00ffffff); concatenate the pixes to reduce the size of the insurance policy photo, resulting in a compressed insurance policy photo Y. IMG Regarding the image compression technology in this article, since the policy data needs to be displayed in the client APP to consider user experience, the image color format is set to be aesthetically pleasing. In this case, color compression of the image not only does not change the image display data, but also reduces the image size and improves network access. In this example, the original image size was 263KB, and after compression it was 230KB.

[0068] 8. The national cryptographic algorithm module for Y IMG Perform SM3 signature using the national cryptographic algorithm to obtain the electronic signature T. IMG ;

[0069] 9. The background application module compresses P1, P2, and P3 using the method described above to generate Y. p1 Y p2 Y p3 and for Y p1 Y p2 Y p3 Perform SM3 signing and generate T P1 T P2 T P3 ;

[0070] 10. The backend application module connects W1 and T P1 T1, W2, T P2 T2, T P3W3, T3, T IMG U id U data D id After concatenating the components in sequence, SM3 encryption is performed to obtain KL;

[0071] 11. The backend application module will use Y p1 Y p2 Y p3 Y IMG The first storage module's xSky storage platform interface is called to perform fragmented storage on different physical machines of the xSky storage platform, ensuring that data is not lost.

[0072] 12. Backend application module: Initiate blockchain transaction application, upload W1, W2, W3, and U. data Did, T1, T2, T3, U id T P1 T P2 T P3 T IMG K L U id information;

[0073] IV. Blockchain processing flow, such as Figure 3 As shown, the relevant operation steps are as follows:

[0074] After receiving a network application initiated by the system, the endorsement node in the blockchain policy management platform uses the blockchain policy management platform to allocate U to the current user. id The public key is used to verify the signature of the current transaction, whether the user has the relevant access rights to log in to the system, whether the transaction is legal, and the transaction format.

[0075] After the endorsement module of the blockchain policy management platform verifies the transaction, the backend application module initiates the blockchain execution transaction.

[0076] The blockchain-based insurance policy management platform performs chaincode calculations and generates blocks during the accounting process.

[0077] After the blockchain policy management platform is executed, the accounting module sends the blocks to the sorting nodes for sorting.

[0078] After the sorting node of the blockchain policy management platform completes the sorting, the management node sends it to other organizational nodes for on-chain storage;

[0079] After execution, the blockchain policy management platform returns information to the backend application module, including the unique block value (293837833txii), which is Q. id The backend application module uses Q through the blockchain transaction query API. idUse `request = 293837833txii` as the input parameter to query block information, and retrieve block information details, returning W1, W2, W3, and U. data Did, T1, T2, T3, U id T P1 T P2 T P3 T IMG K L U id information;

[0080] The process of creating and uploading records during the user's insurance application includes:

[0081] When a user enters the client APP homepage, the current page screenshot P1 is recorded, along with page information W1 (including the unique value of the page, the unique value of the previous page, the time spent on the previous page, page notes, and page name), and the access time T1 (20231101110000).

[0082] When a user clicks on the policy guidance page in the client app, the current page screenshot P2 is recorded, along with page information W2 and access time T2.

[0083] When a user clicks "Next" in the client app, a screenshot of the policy application page is shown in P3, page information is shown in W3, and access time is shown in T3.

[0084] Users register their information on the client APP, including the policy duration, policy rights parameters, policy payment cycle, ID number, and user name.

[0085] The client app takes you to the image upload page, selects image upload, and the original document image is an IMG file;

[0086] The backend application module uses the image compression module to compress P1, P2, P3, and IMG images uploaded by the client app to generate Y. p1 Y p2 Y p3 Y IMG And call the national cryptographic algorithm module to process Y p1 Y p2 Y p3 Y IMG Perform SM3 signing and generate T P1 T P2 T P3 T IMG ;

[0087] The national cryptographic algorithm module uses W1 and T P1 T1, W2, T P2 T2, T P3 W3, T3, TIMG U id U data D id KL is obtained by performing SM3 encryption;

[0088] The backend application module will include W1, W2, W3, and U. data Did, T1, T2, T3, U id T P1 T P2 T P3 T IMG K L U id The information is sent to the blockchain, and the blockchain returns a unique block value, denoted as Q. id ;

[0089] The backend application module for Y p1 Y p2 Y p3 Y IMG The images are stored by calling the object storage tool of the commercial version of Xsky, the first storage module. Xsky itself has high availability (sharding images into files and storing them in multiple copies), scalability (horizontal scaling of server resources), and fast read performance. It can also periodically transfer historical data according to the configuration information of Ssky. For example, if it is configured to transfer three years, the data from three years ago will be transferred to the disk.

Claims

1. An insurance policy document storage system based on a blockchain platform, characterized in that, The evidence storage system includes a client, a network layer, an application layer, a blockchain platform, and a storage layer. The application layer includes a backend application module and a national cryptographic algorithm module. The storage layer includes a first storage module, a second storage module, and a third storage module. The client responds to user page operations, including: when the user opens the client's homepage (page information W1), the client takes a screenshot (saves as screenshot P1) and records the access time (saves as T1); when the user opens the insurance application guidance page (page information W2), the client takes a screenshot (saves as screenshot P2) and records the access time (saves as T2); when the user opens the insurance application initiation page (page information W3), fills in registration information, and prepares to enter the policy upload stage, the client takes a screenshot (saves as screenshot P3) and records the access time (saves as T3). The registration information includes: user name U. name ID number U no The policy duration, policy rights parameters, and policy payment cycle are specified. Simultaneously, the client initiates user authentication with the backend application module. This authentication is based on the user's token data saved by the client during registration, which includes the user's unique value U. id Login time, login method, user permissions, allowed login duration, and signature; authenticated users can proceed to the next step, the policy upload page, where the registration information is configured according to U... name U no U id The policy duration, policy rights parameters, and policy payment cycle are recorded in sequence and then combined to form the user registration information U. data ; The network layer is used to enable remote interaction and security between the backend application module and the client, and to perform load balancing for the backend application module. The backend application module interacts with the client to weaken the image of the original insurance policy photo uploaded by the user on the client page to reduce the image size. The weakened insurance policy photo is denoted as photo Y. IMG Meanwhile, the background application module also weakens the screenshots P1, P2, and P3 recorded by the client to generate Y. p1 Y p2 Y p3 ; The background application module interacts with the national cryptographic algorithm module, calling the national cryptographic algorithm module to process screenshots P1, P2, P3, and Y. IMG Perform signature processing and generate T respectively. P1 T P2 T P3 T IMG ; Retrieve the unique value U assigned to the user during registration id and W1, T P1 T1, W2, T P2 T2, T P3 W3, T3, T IMG U id U data Collect the user's login device ID, i.e., D. id After concatenating the components sequentially, the national cryptographic algorithm module is called to encrypt the result, K. L ; The backend application module interacts with the storage module. The first storage module stores unstructured data, the second storage module stores metadata information and creates an index based on date for easy retrieval, and the third storage module stores user cache information for quick querying of cached data by the backend application module. After user authentication, the backend application module calls the second storage module to store token data. After authentication, the backend application module calls the second storage module to return a unique password record value Q to the blockchain platform. pw With user unique value U id Storage is performed; after the image is uploaded, the backend application module calls the first storage module to compress the image Y. p1 Y p2 Y p3 Y IMG Store the compressed image and assign a unique value Q to the corresponding block. id Stored in the second storage module; after the backend application module initiates a transaction request by uploading an image of the insurance policy, it calls the second storage module to access W1 and T. P1 T1, W2, T P2 T2, T P3 W3, T3, T IMG U id U data Storage is performed; after the insurance policy image is uploaded to the blockchain and the transaction is completed, the backend application module verifies the unique value Q of the block. id With user unique value U id The storage module and the second storage module are used for storage; the authentication module will use U id The randomly generated salt value A is stored in the third storage module; the authentication module combines the user-generated token with U. id The metadata information Y is all the information stored in the third storage module; The backend application module interacts with the blockchain platform. When the backend application module initiates a blockchain transaction request, it uploads W1, W2, W3, and U. data Did, T1, T2, T3, T P1 T P2 T P3 T IMG K L U id Information is sent to the blockchain platform; after receiving a blockchain transaction request initiated by the backend application module, the endorsing node in the blockchain platform uses the blockchain platform to allocate U to the current user. id The public key verifies the signature of the current transaction, whether the user has the relevant access permissions to the system, the legality of the transaction, and the transaction format. After the endorsement module of the blockchain platform verifies the transaction, the backend application module initiates the blockchain to execute the transaction. The blockchain platform performs chaincode calculation, generates blocks, and sends the blocks to the sorting nodes for sorting. After the sorting nodes complete the sorting, the management node sends the blocks to other organization nodes for on-chain storage. After execution, the blockchain platform returns information to the backend application module, which includes the unique value of the block, Q. id The backend application module uses Q through the blockchain transaction query API. id The input parameter is used to query block information, obtain block information details, and return W1, W2, W3, U. data Did, T1, T2, T3, U id T P1 T P2 T P3 T IMG K L U id information.

2. The insurance policy storage system based on a blockchain platform as described in claim 1, characterized in that, The blockchain platform mentioned is the Hyperledger Fabric blockchain platform.

3. The insurance policy storage system based on a blockchain platform as described in claim 1, characterized in that, The national cryptographic algorithm module is the SM3 national cryptographic algorithm processing module.

4. The insurance policy storage system based on a blockchain platform as described in claim 1, characterized in that, The image weakening operation includes the following steps: The image is processed into a two-dimensional array IMG[height][length] using the IMGIO.read() method, where each array field represents the three elements of an RPG (0-255); the array is traversed, and each array item is processed to convert the array segment into a number pix = IMG.getRGB(); red is red = (pix>>16)&0xff, yellow is green = (pix>>16)&0xff, and blue is blue = pix>>0xff; the color is changed to black, and by limiting red>0, green>0, and blue>0, all colored elements are uniformly set to black (0x00ffffff), and the pix is ​​concatenated.

5. The insurance policy storage system based on a blockchain platform as described in claim 1, characterized in that, The first storage module is the xSky storage platform, meaning the background application module calls the xSky storage platform interface to store Y. p1 Y p2 Y p3 Y IMG The process of sharding storage involves splitting each image into smaller image files, distributing them across different physical machines on the xSky storage platform using a hash algorithm, and copying each small file according to the number of copies in the configuration file, and storing copies on the same servers.

6. The insurance policy storage system based on a blockchain platform as described in claim 1, characterized in that, The second storage module is the search engine ES.

7. The insurance policy storage system based on a blockchain platform as described in claim 1, characterized in that, The third storage module is the REDIS cache module.

Images