Cache fault tolerance method, device and equipment of claim settlement system and storage medium

By using the user operation tracking mechanism in the claims system to generate a cache database and dynamically adjust the cache management strategy, the problem of inaccurate query results when interface abnormalities in the existing technology is solved, the system's fault tolerance and response speed are improved, and the user's effectiveness is ensured. Query results.

CN119066092APending Publication Date: 2024-12-03CHINA PING AN PROPERTY INSURANCE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411210642.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-30
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The existing claims system cannot effectively provide query results when the interface is abnormal, and the cached data is simple to manage, and the update frequency and retention strategy cannot be dynamically adjusted, resulting in data obsolete or unrelated, affecting the accuracy and timeliness of query results.

Method used

Record user operation behavior through user operation tracking mechanism, generate cache databases, and monitor interface call status in real time. When the interface is normal, preset data is displayed from the cache database; when the interface is abnormal, the target data is retrieved from the cache database and the result is directly returned when the data exists. Dynamically adjust the cache management strategy, give priority to the use of cached data, and ensure the accuracy and timeliness of query results.

Benefits of technology

It significantly improves the system's data query efficiency and response speed under different working conditions, enhances the system's fault tolerance, and ensures that users can still obtain effective query results when interface abnormalities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119066092A_ABST
    Figure CN119066092A_ABST
Patent Text Reader

Abstract

The invention relates to a cache fault tolerance method of a claim settlement system, which comprises the following steps of: recording an operation behavior of a user through a user operation tracking mechanism, and generating a cache database according to the recorded data; the calling state of the claim settlement system interface is monitored in real time, when the interface calling is normal, the preset number of data is preferentially displayed from the cache database, and if the cache data cannot meet the query requirement of a user, the latest query result is obtained and returned through the claim settlement system interface. In the embodiment of the invention, under the condition that interface calling is abnormal, the target data queried by the user can be retrieved from the cache database, and under the condition that the target data is contained in the cache data, the query result is directly returned. By dynamically adjusting the cache management strategy, the data query efficiency and response speed of the system in different working states are remarkably improved, meanwhile, the fault-tolerant capability of the system is enhanced, and it is ensured that a user can still obtain an effective query result when a system interface is abnormal.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data caching and query technology, and in particular to a cache fault-tolerant method, device, equipment and storage medium for a claims system. Background Art

[0002] In modern claims systems, the efficiency and accuracy of data queries are crucial to user experience. Claims systems usually need to process a large number of user query requests, which involve a variety of data operations, such as case status query, claim progress tracking, customer information verification, etc. However, since the claims system relies on the real-time response of the backend server, these operations may be affected by network latency, server load and other uncontrollable factors, resulting in slow system response or even malfunction.

[0003] In order to improve the response speed and stability of the system, many claims systems have introduced data caching mechanisms. Through caching technology, the system can store frequently accessed data locally to reduce dependence on the back-end server. However, the existing caching mechanism usually only works when the claims system interface is normal, and when the interface is abnormal, the system may still not be able to provide users with valid query results. In addition, the management of cached data in the prior art is relatively simple, and usually adopts a fixed cache refresh strategy. It is impossible to dynamically adjust the update frequency and retention strategy of cached data according to the actual operation of the user, which causes the cached data to become obsolete or irrelevant to a certain extent, further affecting the accuracy and timeliness of the query results.

[0004] As users' requirements for system response speed and service stability continue to increase, existing cache management methods can no longer meet actual application needs. Especially when the network environment is unstable and the backend system does not respond in time, how to improve the system's fault tolerance while ensuring data query speed has become a technical problem that needs to be solved urgently. Therefore, a more intelligent and flexible cache management method is needed, which can effectively manage and update cache data in both normal and abnormal system interface conditions, ensuring the accuracy of user queries and the timeliness of system responses. Summary of the invention

[0005] The main purpose of the present invention is to provide a cache fault-tolerant method, device, equipment and storage medium for a claims system, aiming to solve the technical problem that the cache mechanism of the existing claims system cannot effectively provide query results when the interface is abnormal.

[0006] To achieve the above object, the present invention provides a cache fault tolerance method for a claims system, the cache fault tolerance method for the claims system comprising the following steps:

[0007] Record the user's operation behavior records through the user operation tracking mechanism, generate a cache database based on the operation behavior records, and monitor whether the interface call of the claims system is normal;

[0008] When it is detected that the user performs a data query operation and the interface call of the claims system is normal, a first preset amount of data in the cache database is displayed. If the displayed data does not contain the target data queried by the user, the target data is queried through the claims system and the query result is returned;

[0009] When it is detected that the user is performing a data query operation and the interface call of the claims system is abnormal, the target data queried by the user is retrieved from the cache database. If the cache database contains the target data, the query result of the target data is returned.

[0010] Optionally, if the displayed data does not contain the target data queried by the user, querying the target data through the claims system and returning the query result includes:

[0011] If the displayed data does not contain the target data queried by the user, retrieving the target data queried by the user from the cache database;

[0012] If the cache database does not contain the target data, query the target data through the claims system and return the query result;

[0013] If the cache database contains the target data, the query result of the target data is returned.

[0014] Optionally, after retrieving the target data queried by the user from the cache database, the method further includes:

[0015] If the cache database does not contain the target data, the user's query keyword is counted into the cache refresh queue;

[0016] When it is monitored that the interface call of the claims system is normal, the target data corresponding to the query keyword is queried from the claims system and stored in the cache database.

[0017] Optionally, querying the target data corresponding to the query keyword from the claims system and storing it in the cache database includes:

[0018] If there are multiple query keywords in the cache refresh queue, the weight of each query keyword is calculated, and the corresponding target data is sequentially queried according to the weight of each query keyword and stored in the cache database.

[0019] Optionally, generating a cache database according to the operation behavior record includes:

[0020] The cache database is constructed. When the operation behavior record is a list browsing record, the cache database includes a browsing cache data set, and a second preset number of data in the user's browsing list is stored in the browsing cache data set.

[0021] Optionally, after storing the second preset number of data in the user browsing list in the cache database, the method further includes:

[0022] When the operation behavior record also includes a search operation record, the cache database also includes a search cache data set, and search keywords are filtered out from the browsing cache data set according to user search terms, and the search keywords and corresponding search data are stored in the search cache data set.

[0023] Optionally, after generating a cache database according to the operation behavior record, the method further includes:

[0024] Setting a validity period for each data in the cache database according to the number of views or searches for each data in the cache database, and detecting whether the data in the cache database exceeds the validity period at every preset time interval;

[0025] If so, remove the expired data from the cache database.

[0026] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a cache fault-tolerant device of a claims system, the cache fault-tolerant device of the claims system comprising:

[0027] A cache generation module records the user's operation behavior records through a user operation tracking mechanism, generates a cache database based on the operation behavior records, and monitors whether the interface call of the claims system is normal;

[0028] A normal query module, when monitoring the user to perform a data query operation and the interface call of the claims system is normal, displays a first preset amount of data in the cache database, and if the displayed data does not contain the target data queried by the user, queries the target data through the claims system and returns the query result;

[0029] The abnormal query module retrieves the target data queried by the user from the cache database when it is detected that the user is performing a data query operation and the interface call of the claims system is abnormal. If the cache database contains the target data, the query result of the target data is returned.

[0030] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a cache fault-tolerant device of a claims system, wherein the cache fault-tolerant device of the claims system comprises a memory, a processor, and a cache fault-tolerant program of the claims system stored on the memory and executable on the processor, wherein the cache fault-tolerant program of the claims system, when executed by the processor, implements the steps of the cache fault-tolerant method of the claims system as described above.

[0031] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a computer storage medium, on which a cache fault-tolerant program of a claims system is stored, and when the cache fault-tolerant program of the claims system is executed by a processor, the steps of the cache fault-tolerant method of the claims system as described above are implemented.

[0032] The present invention relates to a cache fault-tolerant method for a claims system, which records the user's operation behavior through a user operation tracking mechanism, and generates a cache database based on the recorded data. The calling status of the claims system interface is monitored in real time. When the interface call is normal, a preset amount of data is displayed from the cache database first. If the cache data cannot meet the user's query requirements, the latest query results will be obtained and returned through the claims system interface. In the case of an abnormal interface call, the target data of the user's query will be retrieved from the cache database, and the query results will be directly returned if the target data is included in the cache data. The present invention significantly improves the data query efficiency and response speed of the system under different working conditions by dynamically adjusting the cache management strategy, while enhancing the fault tolerance of the system, ensuring that users can still obtain valid query results when the system interface is abnormal. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A schematic diagram of the structure of the device hardware operating environment involved in the embodiment of the cache fault-tolerant device of the claims settlement system of the present invention;

[0034] Figure 2 It is a flow chart of the first embodiment of the cache fault tolerance method of the claims system of the present invention;

[0035] Figure 3 This is a functional module diagram of a preferred embodiment of a cache fault-tolerant device of a claims settlement system of the present invention.

[0036] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0037] 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.

[0038] It should be noted that in modern claims systems, the efficiency and accuracy of data queries are crucial to user experience. Claims systems usually need to process a large number of user query requests, which involve a variety of data operations, such as case status query, claim progress tracking, customer information verification, etc. However, since the claims system relies on the real-time response of the backend server, these operations may be affected by network latency, server load and other uncontrollable factors, resulting in slow system response or even malfunction.

[0039] In order to improve the response speed and stability of the system, many claims systems have introduced data caching mechanisms. Through caching technology, the system can store frequently accessed data locally to reduce dependence on the back-end server. However, the existing caching mechanism usually only works when the claims system interface is normal, and when the interface is abnormal, the system may still not be able to provide users with valid query results. In addition, the management of cached data in the prior art is relatively simple, and usually adopts a fixed cache refresh strategy. It is impossible to dynamically adjust the update frequency and retention strategy of cached data according to the actual operation of the user, which causes the cached data to become obsolete or irrelevant to a certain extent, further affecting the accuracy and timeliness of the query results.

[0040] As users' requirements for system response speed and service stability continue to increase, existing cache management methods can no longer meet actual application needs. Especially when the network environment is unstable and the backend system does not respond in time, how to improve the system's fault tolerance while ensuring data query speed has become a technical problem that needs to be solved urgently. Therefore, a more intelligent and flexible cache management method is needed, which can effectively manage and update cache data in both normal and abnormal system interface conditions, ensuring the accuracy of user queries and the timeliness of system responses.

[0041] Based on the above defects, the present invention provides a cache fault-tolerant device for a claims system, referring to Figure 1 , Figure 1 It is a structural diagram of the device hardware operating environment involved in the cache fault-tolerant device embodiment of the claims settlement system of the present invention.

[0042] like Figure 1As shown, the cache fault-tolerant device of the claims system may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0043] Those skilled in the art will understand that Figure 1 The hardware structure of the cache fault-tolerant device of the claims system shown in the figure does not constitute a limitation of the cache fault-tolerant device of the claims system, and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0044] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a cache fault-tolerant program of the claims system. The operating system is a program for managing and controlling the cache fault-tolerant devices and software resources of the claims system, and supports the operation of the network communication module, the user interface module, the cache fault-tolerant program of the claims system, and other programs or software; the network communication module is used to manage and control the network interface 1004; and the user interface module is used to manage and control the user interface 1003.

[0045] exist Figure 1 In the cache fault-tolerant device hardware structure of the claims system shown, the network interface 1004 is mainly used to connect to the backend server and communicate data with the backend server; the user interface 1003 is mainly used to connect to the client and communicate data with the client; the processor 1001 can call the cache fault-tolerant program of the claims system stored in the memory 1005 and perform the following operations:

[0046] Record the user's operation behavior records through the user operation tracking mechanism, generate a cache database based on the operation behavior records, and monitor whether the interface call of the claims system is normal;

[0047] When it is detected that the user performs a data query operation and the interface call of the claims system is normal, a first preset amount of data in the cache database is displayed. If the displayed data does not contain the target data queried by the user, the target data is queried through the claims system and the query result is returned;

[0048] When it is detected that the user is performing a data query operation and the interface call of the claims system is abnormal, the target data queried by the user is retrieved from the cache database. If the cache database contains the target data, the query result of the target data is returned.

[0049] Furthermore, if the displayed data does not contain the target data queried by the user, querying the target data through the claims system and returning the query result includes:

[0050] If the displayed data does not contain the target data queried by the user, retrieving the target data queried by the user from the cache database;

[0051] If the cache database does not contain the target data, query the target data through the claims system and return the query result;

[0052] If the cache database contains the target data, the query result of the target data is returned.

[0053] Further, after retrieving the target data queried by the user from the cache database, the method further includes:

[0054] If the cache database does not contain the target data, the user's query keyword is counted into the cache refresh queue;

[0055] When it is monitored that the interface call of the claims system is normal, the target data corresponding to the query keyword is queried from the claims system and stored in the cache database.

[0056] Further, querying the target data corresponding to the query keyword from the claims system and storing it in the cache database includes:

[0057] If there are multiple query keywords in the cache refresh queue, the weight of each query keyword is calculated, and the corresponding target data is sequentially queried according to the weight of each query keyword and stored in the cache database.

[0058] Furthermore, generating a cache database according to the operation behavior record includes:

[0059] The cache database is constructed. When the operation behavior record is a list browsing record, the cache database includes a browsing cache data set, and a second preset number of data in the user's browsing list is stored in the browsing cache data set.

[0060] Further, after storing the second preset number of data in the user browsing list in the cache database, the method further includes:

[0061] When the operation behavior record also includes a search operation record, the cache database also includes a search cache data set, and search keywords are filtered out from the browsing cache data set according to user search terms, and the search keywords and corresponding search data are stored in the search cache data set.

[0062] Furthermore, after generating a cache database according to the operation behavior record, it also includes:

[0063] Setting a validity period for each data in the cache database according to the number of views or searches for each data in the cache database, and detecting whether the data in the cache database exceeds the validity period at every preset time interval;

[0064] If so, remove the expired data from the cache database.

[0065] The specific implementation of the cache fault-tolerant device of the claims system of the present invention is basically the same as the various embodiments of the cache fault-tolerant method of the claims system described below, and will not be repeated here.

[0066] The present invention also provides a cache fault tolerance method for a claims system based on the cache fault tolerance device of the claims system.

[0067] Reference Figure 2 , Figure 2 It is a flow chart of the first embodiment of the cache fault tolerance method of the claims settlement system of the present invention.

[0068] The embodiment of the present invention provides an embodiment of a cache fault-tolerant method for a claims system. It should be noted that although a logical order is shown in the flow chart, in some cases, the steps shown or described may be executed in an order different from that shown here.

[0069] In various embodiments of the cache fault tolerance method of the claims system, the execution subject is the cache fault tolerance device of the claims system.

[0070] The cache fault tolerance method of the claims system is applied to a cache fault tolerance device of the claims system, and the cache fault tolerance method of the claims system includes:

[0071] Step S10, recording the user's operation behavior records through the user operation tracking mechanism, generating a cache database according to the operation behavior records, and monitoring whether the interface call of the claims system is normal;

[0072] In modern claims systems, the efficiency and accuracy of data queries are crucial to user experience. Claims systems usually need to process a large number of user query requests, which involve a variety of data operations, such as case status query, claim progress tracking, customer information verification, etc. However, since the claims system relies on the real-time response of the backend server, these operations may be affected by network latency, server load and other uncontrollable factors, resulting in slow system response or even malfunction.

[0073] In order to improve the response speed and stability of the system, many claims systems have introduced data caching mechanisms. Through caching technology, the system can store frequently accessed data locally to reduce dependence on the back-end server. However, the existing caching mechanism usually only works when the claims system interface is normal, and when the interface is abnormal, the system may still not be able to provide users with valid query results. In addition, the management of cached data in the prior art is relatively simple, and usually adopts a fixed cache refresh strategy. It is impossible to dynamically adjust the update frequency and retention strategy of cached data according to the actual operation of the user, which causes the cached data to become obsolete or irrelevant to a certain extent, further affecting the accuracy and timeliness of the query results.

[0074] As users' requirements for system response speed and service stability continue to increase, existing cache management methods can no longer meet actual application needs. Especially when the network environment is unstable and the backend system does not respond in time, how to improve the system's fault tolerance while ensuring data query speed has become a technical problem that needs to be solved urgently. Therefore, a more intelligent and flexible cache management method is needed, which can effectively manage and update cache data in both normal and abnormal system interface conditions, ensuring the accuracy of user queries and the timeliness of system responses.

[0075] In this embodiment, various operation behaviors of users in the process of using the claims system are tracked and recorded in real time, such as users browsing certain pages, searching for specific information, clicking certain buttons, etc. These behavior data may include the number of clicks, dwell time, search keywords entered by users, etc. Through these operation behavior records, it is possible to gain an in-depth understanding of the user's usage habits and preferences, and use these data to further optimize performance.

[0076] A cache database is a set of data copies stored locally to speed up data queries. By analyzing user behavior, it is possible to predict the content that users may visit again and store it in the cache database in advance. This method can significantly improve the system's response speed and reduce dependence on remote servers.

[0077] Continuously monitor the interface status of the claims system to determine whether it is working properly. This includes detecting whether the interface can respond to requests in a timely manner and whether data transmission is normal. If the interface call is normal, the user request will be processed according to the predetermined process; if the interface call is abnormal, it will switch to an alternative operation mode, such as using cached data first to respond to user requests.

[0078] A specific implementation method may be: the user operation tracking mechanism continuously records the user's operation behavior in the claims system, such as browsing cases, submitting inquiries, etc. Based on these behavior records, a cache database is regularly analyzed and generated to pre-cache data that the user may access again, such as the status of the most recently queried case, frequently used pages, etc. This method can quickly provide a response when the user accesses again.

[0079] When processing user query requests, first check the call status of the claims system interface. If the interface is normal, some data is quickly returned from the cache database, and the latest data is obtained from the claims system and the results are returned. If the interface is abnormal, the target data of the user query is directly retrieved from the cache database and returned, ensuring that the user can obtain the query results in time, even if the interface is temporarily unavailable.

[0080] Example description:

[0081] Suppose a user queries the status information of the same case number multiple times. The operation tracking mechanism records these behaviors and stores the data related to the case number in the cache database. When the user queries the case again, the interface status is monitored first. If the interface is normal, some data is quickly returned from the cache and the latest data update is obtained. If the interface is abnormal, the relevant data is directly retrieved and returned from the cache database to ensure the timeliness of the query results.

[0082] The above steps ensure that services can be provided efficiently and stably in different situations, improving the user experience and the overall reliability of the system.

[0083] Step S20, when it is detected that the user performs a data query operation and the interface call of the claims system is normal, a first preset amount of data in the cache database is displayed. If the displayed data does not contain the target data queried by the user, the target data is queried through the claims system and the query result is returned;

[0084] In this embodiment, the explanation of relevant technical features is as follows:

[0085] Data query operation: When using the claims system, the user initiates a data query operation, such as querying the status of a case, claims progress, or customer information.

[0086] Normal interface calls: The monitoring mechanism confirms that the interface calls of the claims system are normal, that is, the system can communicate normally with the backend server or database, and data transmission and query requests can proceed smoothly.

[0087] Display preset data in the cache database: After determining that the interface is normal, the system will first extract and display a certain amount of pre-cached data, namely a first preset amount, from the cache database. These data are usually the data that the user is most likely to need, has recently accessed, or has frequently accessed.

[0088] Query target data: If the data displayed in the cache fails to meet the user's query requirements, that is, the cache data does not contain the target data queried by the user, the system will call the backend database or server of the claims system in real time, query the latest target data, and return the query results to the user.

[0089] A specific implementation method may be: the user enters the case number or other query conditions in the query interface and submits a query request. Check the interface call status of the claims system to confirm whether the communication between the interface and the background server is normal. If the interface is normal, the first preset amount of data is preferentially extracted from the cache database for display. These data usually include the case information last accessed by the user, data related to the query conditions, or other high-frequency access data. If the target data of the user's query is not found in the cache database, a real-time query is performed through the background server of the claims system to obtain the latest data and return the query results.

[0090] Example description:

[0091] Users can query the current processing status of a case through the claims system.

[0092] Query operation: The user enters the case number "12345" and submits the query request.

[0093] Interface status monitoring: Detect the calling status of the claims system interface to confirm that it can communicate normally and obtain data.

[0094] Display cache data: Display the data of the last five cases that have been accessed recently and stored in the cache database.

[0095] Query target data: It is found that the cached data does not contain information about the case number "12345". The latest status of the case is queried through the backend server of the claims system and the result is returned to the user.

[0096] Through the above steps, it is ensured that when the interface is normal, the user's query request can be quickly responded to through cached data, and real-time data can be obtained when necessary to ensure the accuracy and timeliness of the query results.

[0097] Step S30, when it is detected that the user is performing a data query operation and the interface call of the claims system is abnormal, the target data queried by the user is retrieved from the cache database, and if the cache database contains the target data, the query result of the target data is returned.

[0098] In this embodiment, when a user initiates a query operation in the claims system, if an abnormality is detected in the interface call with the backend server, the system cannot obtain real-time data through normal communication channels.

[0099] In the case of an interface call exception, the target data queried by the user is retrieved through the local cache database. The cache database usually pre-stores relevant data that the user may access so that services can continue to be provided when the interface is abnormal.

[0100] If the target data of the user's query is found in the cache database, the cached data is directly used as the query result and returned to the user. This ensures that the user can still obtain the query results when the interface is inaccessible, minimizing the impact of service interruption on user experience.

[0101] Specific implementations may be:

[0102] Data query trigger and interface anomalies: When the user enters the query conditions (such as case number) in the query interface and submits the request, it is found that the interface of the claims system cannot communicate normally.

[0103] Cache database retrieval: In the case of interface abnormalities, the target data of the user's query is immediately retrieved from the local cache database. The cache database contains the commonly used or frequently accessed data previously stored by the system. These data are regularly updated when the interface is normal for subsequent queries.

[0104] Return cached data: If the cache database contains the target data of the user's query, such as the processing status of the case number, these cached data are directly used as query results and returned to the user. This method ensures that users can still obtain relevant query information in the event of interface abnormalities.

[0105] Example description:

[0106] The user inquires about the current processing status of a case, but the interface call of the claims system is abnormal.

[0107] Query operation and interface abnormality: The user enters the case number "12345" and submits a query request. However, the system detects that the interface of the claims system cannot communicate with the backend server normally, and the data request cannot be completed.

[0108] Cache database retrieval: After detecting an interface anomaly, immediately retrieve the relevant data of case number "12345" from the cache database. This data may be pre-stored when the interface is normal, including the last processing status of the case and other relevant information.

[0109] Return cached data: Since the cache database contains the data of case number "12345", the query result is immediately returned to the user from the cache. This ensures that even in the case of interface abnormalities, the user can obtain the case processing information in a timely manner.

[0110] Through the above steps, even when problems occur in the system interface, users can still obtain valuable query results, thereby improving system reliability and user experience.

[0111] The present invention relates to a cache fault-tolerant method for a claims system, which records the user's operation behavior through a user operation tracking mechanism, and generates a cache database based on the recorded data. The calling status of the claims system interface is monitored in real time. When the interface call is normal, a preset amount of data is displayed from the cache database first. If the cache data cannot meet the user's query requirements, the latest query results will be obtained and returned through the claims system interface. In the case of an abnormal interface call, the target data of the user's query will be retrieved from the cache database, and the query results will be directly returned if the target data is included in the cache data. The present invention significantly improves the data query efficiency and response speed of the system under different working conditions by dynamically adjusting the cache management strategy, while enhancing the fault tolerance of the system, ensuring that users can still obtain valid query results when the system interface is abnormal.

[0112] Furthermore, a second embodiment of the cache fault tolerance method of the claims system of the present invention is proposed. In the above step S20, if the displayed data does not contain the target data queried by the user, querying the target data through the claims system and returning the query result includes:

[0113] Step a1, if the displayed data does not contain the target data queried by the user, retrieving the target data queried by the user from the cache database;

[0114] Step a2: if the cache database does not contain the target data, query the target data through the claims system and return the query result;

[0115] Step a3: If the cache database contains the target data, return the query result of the target data.

[0116] In this embodiment, if the initially displayed data does not contain the target data queried by the user, the first step is to retrieve the target data queried by the user from the cache database. The cache database usually stores the data that the user may have queried before, so as to speed up the query response speed.

[0117] If the cache database does not contain the target data that the user is querying, the further processing step is to query the latest target data through the backend database or server of the claims system. This ensures that the user can obtain the latest and accurate query results.

[0118] If the cache database contains the target data queried by the user, the data is directly extracted from the cache and returned to the user. This step can significantly reduce the query time and improve the system response speed, especially when the claims system interface is normal.

[0119] Specific implementations may be:

[0120] When a user initiates a data query operation, if the initially displayed data does not contain the target data of the user's query, it will be processed according to the following steps:

[0121] Cache database retrieval: After a user initiates a query operation, the target data is first retrieved from the cache database. The cache database usually stores data such as case status and claim information that the user may query, and is used to quickly respond to the user's query request.

[0122] Cache data processing: If the target data of the user's query is found in the cache database, the cache data is immediately used as the query result and returned to the user. This method can significantly shorten the query time, especially when the user repeatedly queries the same target data.

[0123] Real-time data query: If the target data queried by the user cannot be found in the cache database, a real-time query is required through the background database or server of the claims system. The latest target data is obtained through real-time query and the results are returned to the user. This step ensures the accuracy and real-time nature of the data.

[0124] Example description:

[0125] The user queries the current processing status of a case, but the target case information is not included in the data initially displayed.

[0126] Cache database search: After the user enters the case number "67890" and submits a query request, the data related to the case number "67890" is first retrieved from the cache database.

[0127] Cache data processing: The cache database contains information about case number "67890", which includes the case processing status and other relevant details. Therefore, the cache data is directly returned to the user as the query result. The user does not need to wait for the real-time query process and can quickly obtain case information.

[0128] Real-time data query: If the relevant data of case number "67890" cannot be found in the cache database, a real-time query is performed through the background database of the claims system. The latest case processing status is obtained and the query results are returned to the user to ensure that the user obtains the latest and accurate case information.

[0129] Through the above steps, this embodiment can flexibly process user query requests in different situations, not only utilizing cached data to speed up response, but also obtaining the latest data through real-time query when necessary, thereby ensuring user experience and accuracy of query results.

[0130] Furthermore, a third embodiment of the cache fault tolerance method of the claims system of the present invention is proposed. In the above step S30, after retrieving the target data queried by the user from the cache database, the method further includes:

[0131] Step b1: if the cache database does not contain the target data, the user's query keyword is counted into the cache refresh queue;

[0132] Step b2, when it is monitored that the interface call of the claims system is normal, the target data corresponding to the query keyword is queried from the claims system and stored in the cache database.

[0133] In this embodiment, if the target data queried by the user is not found in the cache database, the system records the query keywords used by the user (such as case number, customer ID, etc.) and adds them to the cache refresh queue. The cache refresh queue is a list of data waiting to be updated, which is used to refresh the data in the cache database at the appropriate time.

[0134] Continuously monitor the interface status of the claims system to determine when the interface call returns to normal. Only when the interface is normal can the system perform real-time data query and cache refresh operations.

[0135] Once the interface call of the claims system is detected to be back to normal, the query keywords in the cache refresh queue will be automatically processed and a data query request will be sent to the claims system. The queried target data will be stored in the cache database so that data can be provided faster in subsequent queries.

[0136] Specific implementations may be:

[0137] When a user queries for data, the target data is first retrieved from the cache database. If the target data is not found in the cache, the subsequent steps are as follows:

[0138] Add query keywords to the cache refresh queue: When the target data queried by the user is not included in the cache database, the query keyword (such as case number) entered by the user is recorded and added to the cache refresh queue. This queue is used to update the cache database after the claims system interface returns to normal.

[0139] Monitor the status of the claims system interface: Continuously monitor the status of the claims system interface until the interface call returns to normal. During this period, the keywords in the cache refresh queue will temporarily wait for processing.

[0140] Query target data and update cache: When the interface status returns to normal, the query keywords in the cache refresh queue are processed in turn to query the corresponding target data. The queried data will be stored in the cache database to improve the response speed of subsequent queries and data availability.

[0141] Example description:

[0142] The user queries the status information of a case, but the cache database does not contain the data of the case, and the interface call of the claims system is abnormal.

[0143] Query keywords are added to the cache refresh queue: The user enters the case number "12345" and initiates a query operation. If no data with the case number "12345" is found in the cache database, "12345" is recorded as the query keyword and added to the cache refresh queue, waiting for subsequent refresh.

[0144] Monitor the status of the claims system interface: Continuously monitor the status of the claims system interface until the interface call returns to normal. During this period, the keywords in the cache refresh queue will temporarily wait for processing.

[0145] Query target data and update cache: Once the claims system interface returns to normal, the keyword "12345" is immediately extracted from the cache refresh queue, and the latest status information of the case is queried through the claims system backend server. The acquired data is stored in the cache database to ensure that the results can be returned more quickly the next time the query is made.

[0146] Through the above steps, this embodiment can ensure that subsequent cache data update operations can be performed in a timely manner even in the case of interface abnormalities, thereby optimizing the query experience and improving the response speed.

[0147] Furthermore, a fourth embodiment of the cache fault tolerance method of the claims system of the present invention is proposed. In the above step b2, the target data corresponding to the query keyword is queried from the claims system and stored in the cache database, including:

[0148] Step c1: if there are multiple query keywords in the cache refresh queue, calculate the weight of each query keyword, query the corresponding target data in turn according to the weight of each query keyword and store them in the cache database.

[0149] In this embodiment, when there are multiple query keywords in the cache refresh queue, these keywords may be caused by user query requests accumulated during the system interface abnormality or other reasons. These keywords need to be effectively processed to optimize the efficiency of cache update.

[0150] The weight of each query keyword is calculated based on multiple factors, such as the query frequency of the keyword, the user's urgent need for related data, historical query records, etc. Keywords with higher weights mean that the corresponding data is more important or urgent in the user's query.

[0151] After calculating the weight of each query keyword, these keywords are processed in descending order. The keyword with the highest weight is processed first, and the corresponding target data is queried through the claims system, and the queried data is stored in the cache database. This method ensures that the most critical data can be updated to the cache database first, improving the system's response speed and user experience.

[0152] Specific implementations may be:

[0153] When the system interface returns to normal and multiple query keywords have accumulated in the cache refresh queue, the system will process these keywords. The specific steps are as follows:

[0154] Calculate the weight of the query keyword: Each query keyword is assigned a weight based on its importance and urgency. The calculation of the weight can take into account factors such as the query frequency of the keyword, the urgency of the user's demand for data, and the number of historical queries.

[0155] Sort by weight and process in sequence: Based on the calculated weights, query keywords are processed in order from high to low. The keyword with the highest weight is processed first, and the corresponding target data is queried through the claims system.

[0156] Update the cache database: Store the target data retrieved through the claims system in the cache database to ensure that these high-priority data can be quickly responded to when the user queries again. Process all query keywords in sequence until all data in the cache refresh queue is updated.

[0157] Example description:

[0158] During the interface abnormality, case numbers queried by multiple users are accumulated in the cache refresh queue. These case numbers need to be queried and the cache updated in sequence after the interface returns to normal.

[0159] Calculate the weight of the query keyword: Assume that there are three case numbers accumulated in the cache refresh queue: "A12345", "B67890" and "C54321". First, calculate the weight of each case number. For example, "B67890" has the highest weight because it is queried many times and involves a high amount of claims; "A12345" has the second highest weight because it is queried less frequently; "C54321" has the lowest weight.

[0160] Sort by weight and process in sequence: Process the three case numbers in order from high to low weight. First process "B67890" with the highest weight, and query the latest status information of the case through the claims system.

[0161] Update the cache database: Store the queried data of "B67890" in the cache database to ensure that the data can be quickly responded to the next time the user queries it. Then process "A12345" and finally process "C54321" until all the data in the cache refresh queue is updated.

[0162] Through the above steps, this embodiment can give priority to processing the most important query requests, ensuring that the most critical data is always stored preferentially in the cache database, thereby improving the response speed of user queries and the overall efficiency of the system.

[0163] Furthermore, a fifth embodiment of the cache fault tolerance method of the claims system of the present invention is proposed. In the above step S10, a cache database is generated according to the operation behavior record, including:

[0164] Step d1, constructing the cache database. When the operation behavior record is a list browsing record, the cache database includes a browsing cache data set, and a second preset number of data in the user's browsing list is stored in the browsing cache data set.

[0165] In this embodiment, a cache database is generated based on the user's operation behavior records, especially the operations related to list browsing. The database is used to improve the response speed of subsequent queries and reduce the dependence on remote servers.

[0166] When a user browses a data list in the claims system (such as a case list, a customer list, etc.), these operation behaviors will be recorded and used as a basis for generating a cache database.

[0167] A dedicated browsing cache dataset is set up in the cache database to store key data related to user browsing operations. This dataset contains the core part of the list data displayed to the user to ensure that the data can be accessed quickly.

[0168] A specific number or range of data in the data list for displaying to the user, i.e., a second preset number of data, is stored in the browsing cache data set. These cached data items can be flexibly adjusted according to the actual usage habits of the user and the system performance requirements, so that when the user visits again, the data can be quickly extracted from the cache without having to be obtained from the remote server every time.

[0169] Specific implementations may be:

[0170] When a user browses a list of data in the claims system, the operational behavior records will be captured and used to generate or update a cache database, especially a browsing cache data set used to speed up subsequent access.

[0171] Build a cache database: When a user browses a list, the relevant operation behavior records are analyzed and used to generate a cache database. The establishment of a cache database helps to improve the response speed of subsequent visits.

[0172] Identify and record list browsing operations: Capture and record the specific behavior of users when browsing data lists. These records include the pages visited by users and the data items viewed, which are used as the basis for creating cached data.

[0173] Store list data displayed to users in cache: Store a specific number or range of data in the list of data displayed to users in the browsing cache data set. These cached data items may include case numbers, case status, applicant information, etc. The next time you visit, the data can be directly retrieved and displayed from the cache, thereby improving response speed and reducing dependence on the server.

[0174] Example description:

[0175] In the claims system, users browse the case list, a cache database is generated based on the operation behavior, and a specific range of content in the data list displayed to the user is cached.

[0176] Establishment of cache database: The user opens the case list in the claims system and browses a certain amount of data, including case number, case status, applicant information, etc.

[0177] Records of list browsing operations: Users' browsing behavior is recorded, including specific cases viewed and pages visited. These records are used to generate cache data to speed up subsequent access.

[0178] Storage of cached data: Store a specific amount or range of data in the case list (such as information on the first 20 cases or the part most frequently visited by users) in the browsing cache data set. In this way, the next time you visit the case list, the data can be directly extracted and displayed from the cache, reducing dependence on remote servers and significantly improving response speed.

[0179] Through the above steps, this embodiment can effectively cache the data list content that users frequently access, ensuring a faster and smoother experience when accessing again, while maintaining flexibility to adapt to different system requirements and user habits.

[0180] Furthermore, a sixth embodiment of the cache fault tolerance method of the claims system of the present invention is proposed, which includes, after the above step d1, the following steps:

[0181] Step e1, when the operation behavior record also includes a search operation record, the cache database also includes a search cache data set, and the search keywords are filtered out from the browsing cache data set according to the user search terms, and the search keywords and corresponding search data are stored in the search cache data set.

[0182] In this embodiment, if search operation records are identified in the user's operation behavior records, the system will further optimize the structure and content of the cache database based on these records.

[0183] A dedicated search cache data set is set up in the cache database to store data related to user search operations. This data set will contain keywords in user search behavior and their corresponding data.

[0184] From the browsing cache data set, based on the user's search terms, filter out keywords related to the user's search operation. These keywords can help quickly locate data that the user may query again.

[0185] The filtered search keywords and their corresponding search result data are stored in the search cache data set. In this way, when the user uses the same or similar search terms again, the system can quickly extract results from the search cache data set, improving the response speed.

[0186] Specific implementations may be:

[0187] When a user browses list data and performs a search operation, the operation behavior record will be further analyzed and processed to optimize the storage of search-related data in the cache database.

[0188] Identification of search operation records: After the user browses the data and completes the cache of the list data, the system will also check whether the user has performed a search operation. If a search operation record is identified, further cache optimization steps will be initiated.

[0189] Create a search cache dataset: In addition to the stored browsing data, a search cache dataset will be created in the cache database. This dataset is specifically used to store keywords and corresponding data in user search behavior.

[0190] Filter search keywords: Based on the search terms entered by the user, filter out keywords related to the search operation from the browsing cache data set. These keywords may be frequently searched by users and have a high probability of being searched again.

[0191] Storing search keywords and corresponding data: The filtered search keywords and their corresponding data are stored in the search cache data set. In this way, when the user uses the same or similar search terms next time, the data can be directly extracted from the search cache data set, which significantly improves the query speed.

[0192] Example description:

[0193] After browsing the case list in the claims system, the user performs a search operation, and the system generates and optimizes the cache database based on the operation behavior.

[0194] Identify search operation records: After browsing the case list, the user enters the case number or applicant name to search. The system recognizes the search operation and prepares to further optimize the cache database.

[0195] Create a search cache data set: In the cache database, the system creates a search cache data set that specifically stores keywords and related data in user search behaviors.

[0196] Filter and store search keywords: According to the search terms entered by the user, filter out relevant search keywords from the stored browsing cache data set. For example, if the user searches for "case number 12345", the system filters out the case number and its related data and stores them in the search cache data set.

[0197] Optimize query speed: The next time the user searches for "case number 12345" or similar keywords, the system can directly extract and return data from the search cache data set without having to query from the remote server again, significantly improving query response speed.

[0198] Through the above steps, the cache database in this embodiment can not only speed up the user's browsing operation, but also optimize the response speed of the search operation, further improving the user experience and system efficiency.

[0199] Furthermore, a seventh embodiment of the cache fault tolerance method of the claims system of the present invention is proposed. In the above step S10, after the cache database is generated according to the operation behavior record, the method further includes:

[0200] Step f1, setting a validity period for each data in the cache database according to the number of views or searches of each data in the cache database, and detecting whether the data in the cache database exceeds the validity period at every preset time interval;

[0201] Step f2: If yes, remove the expired data from the cache database.

[0202] In this embodiment, a validity period is set for each data item according to the number of views or searches of each data item in the cache database. The length of the validity period depends on the frequency of use of the data: data with high access frequency can have a longer validity period, while data with low access frequency may have a shorter validity period.

[0203] At preset intervals, the data in the cache database is checked to determine which data has exceeded the set validity period. This detection mechanism ensures that the data in the cache database is always fresh and useful, and prevents outdated or no longer needed data from occupying cache space.

[0204] For data that has been detected to have expired, it is removed from the cache database. This operation frees up cache space and ensures that the content of the cache database is always up to date and relevant to user needs.

[0205] Specific implementations may be:

[0206] After the user's operation behavior records are generated into a cache database, the data in the database is further managed to ensure its efficient operation.

[0207] Set the validity period of data: After the cache database is generated, the system will set a validity period for each data item based on the number of views or searches for each data item. For example, case data that is frequently viewed or searched may be set to a longer validity period, while data that is less frequently accessed may be set to a shorter validity period.

[0208] Regularly check the validity period of data: The system checks the data in the cache database at a preset time period (such as daily, weekly or monthly) to determine which data has exceeded the set validity period. The detection process can be automated to ensure that no human intervention is required.

[0209] Removing expired data: For data that has exceeded its validity period, the system removes it from the cache database. The purpose of this is to free up cache space and prevent outdated data from occupying resources, thereby ensuring that the data in the cache database is always efficient and useful.

[0210] Example description:

[0211] In the claims system, the cache database is generated and managed based on user operation behavior, and the system sets and regularly checks the validity period of the data.

[0212] Set validity period: Users frequently query the status of case number "ABC123", and a longer validity period is set for the data in the cache database. For case number "XYZ789" that users rarely query, a shorter validity period is set for the data.

[0213] Regular testing: Every week, the system automatically tests the data in the cache database to check which data has exceeded the set validity period. For example, the system finds that case number "XYZ789" has exceeded its validity period, while case number "ABC123" is still within the validity period.

[0214] Removing expired data: The system removes the data of case number "XYZ789" from the cache database to free up cache space. However, the data of case number "ABC123" is still valid and remains in the cache database to ensure that users can still quickly access it in subsequent queries.

[0215] Through the above steps, the cache database can dynamically adjust and optimize its content in this embodiment, ensuring that the system provides the latest and most relevant data to users while maintaining efficient operation. This mechanism not only improves the utilization rate of data, but also improves the overall performance of the system.

[0216] The present invention also provides a cache fault-tolerant device for a claims settlement system.

[0217] Reference Figure 3 , Figure 3 This is a functional module diagram of the first embodiment of the cache fault tolerance device of the claims system of the present invention. The cache fault tolerance device of the claims system includes:

[0218] A cache generation module records the user's operation behavior records through a user operation tracking mechanism, generates a cache database based on the operation behavior records, and monitors whether the interface call of the claims system is normal;

[0219] A normal query module, when monitoring the user to perform a data query operation and the interface call of the claims system is normal, displays a first preset amount of data in the cache database, and if the displayed data does not contain the target data queried by the user, queries the target data through the claims system and returns the query result;

[0220] The abnormal query module retrieves the target data queried by the user from the cache database when it is detected that the user is performing a data query operation and the interface call of the claims system is abnormal. If the cache database contains the target data, the query result of the target data is returned.

[0221] In addition, an embodiment of the present invention further provides a computer storage medium.

[0222] The storage medium stores a cache fault-tolerant program of the claims system, and when the cache fault-tolerant program of the claims system is executed by the processor, the steps of the cache fault-tolerant method of the claims system as described above are implemented.

[0223] The specific implementation of the storage medium of the present invention is basically the same as the various embodiments of the cache fault tolerance method of the above-mentioned claims system, and will not be repeated here.

[0224] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the enlightenment of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims. All equivalent structures or equivalent process changes made using the contents of the specification and drawings of the present invention, or directly or indirectly used in other related technical fields, are protected by the present invention.

[0225] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to the multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0226] In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part. If the function is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, RandomAccess Memory), a disk or an optical disk.

[0227] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0228] The above are only various implementations of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A cache fault tolerance method for a claims system, characterized in that: The following steps are involved: Record the user's operation behavior records through the user operation tracking mechanism, generate a cache database based on the operation behavior records, and monitor whether the interface call of the claims system is normal; When it is detected that the user performs a data query operation and the interface call of the claims system is normal, a first preset amount of data in the cache database is displayed. If the displayed data does not contain the target data queried by the user, the target data is queried through the claims system and the query result is returned; When it is detected that the user is performing a data query operation and the interface call of the claims system is abnormal, the target data queried by the user is retrieved from the cache database. If the cache database contains the target data, the query result of the target data is returned.

2. The cache fault tolerance method of the claims system according to claim 1, characterized in that: If the displayed data does not contain the target data queried by the user, the target data is queried through the claims system and the query results are returned, including: If the displayed data does not contain the target data queried by the user, retrieving the target data queried by the user from the cache database; If the cache database does not contain the target data, query the target data through the claims system and return the query result; If the cache database contains the target data, the query result of the target data is returned.

3. The cache fault tolerance method of the claims system according to claim 1, characterized in that: After retrieving the target data of the user query from the cache database, the method further includes: If the cache database does not contain the target data, the user's query keyword is counted into the cache refresh queue; When it is monitored that the interface call of the claims system is normal, the target data corresponding to the query keyword is queried from the claims system and stored in the cache database.

4. The cache fault tolerance method of the claims system according to claim 3, characterized in that: Querying the target data corresponding to the query keyword from the claims system and storing it in the cache database includes: If there are multiple query keywords in the cache refresh queue, the weight of each query keyword is calculated, and the corresponding target data is sequentially queried according to the weight of each query keyword and stored in the cache database.

5. The cache fault tolerance method of the claims system according to claim 1, characterized in that: Generating a cache database according to the operation behavior record includes: The cache database is constructed. When the operation behavior record is a list browsing record, the cache database includes a browsing cache data set, and a second preset number of data in the user's browsing list is stored in the browsing cache data set.

6. The cache fault tolerance method of the claims system according to claim 5, characterized in that: After storing the second preset number of data in the user's browsing list in the cache database, the method further includes: When the operation behavior record also includes a search operation record, the cache database also includes a search cache data set, and search keywords are filtered out from the browsing cache data set according to user search terms, and the search keywords and corresponding search data are stored in the search cache data set.

7. The cache fault tolerance method of the claims system as claimed in claim 1, characterized in that: After the cache database is generated according to the operation behavior record, the method further includes: Setting a validity period for each data in the cache database according to the number of views or searches for each data in the cache database, and detecting whether the data in the cache database exceeds the validity period at every preset time interval; If so, remove the expired data from the cache database.

8. A cache fault-tolerant device for a claims system, characterized in that: The cache fault-tolerant device of the claims system comprises: A cache generation module records the user's operation behavior records through a user operation tracking mechanism, generates a cache database based on the operation behavior records, and monitors whether the interface call of the claims system is normal; A normal query module, when monitoring the user to perform a data query operation and the interface call of the claims system is normal, displays a first preset amount of data in the cache database, and if the displayed data does not contain the target data queried by the user, queries the target data through the claims system and returns the query result; The abnormal query module, when monitoring the user to perform data query operations and the interface call of the claims system is abnormal, retrieves the target data queried by the user from the cache database, and returns the query result of the target data if the cache database contains the target data.

9. A cache fault-tolerant device for a claims system, characterized in that: The cache fault-tolerant device of the claims system includes a memory, a processor, and a cache fault-tolerant program of the claims system stored in the memory and executable on the processor. When the cache fault-tolerant program of the claims system is executed by the processor, the steps of the cache fault-tolerant method of the claims system as described in any one of claims 1 to 7 are implemented.

10. A computer storage medium, characterized in that: The storage medium stores a cache fault-tolerant program of the claims system, and when the cache fault-tolerant program of the claims system is executed by the processor, the steps of the cache fault-tolerant method of the claims system as described in any one of claims 1 to 7 are implemented.