CN119066092A

CN119066092A - Cache fault tolerance method, device, equipment and storage medium for claims system

Info

Publication number: CN119066092A
Application number: CN202411210642.4A
Authority: CN
Inventors: 庄志辉
Original assignee: Ping An Property and Casualty Insurance Company of China Ltd
Current assignee: Ping An Property and Casualty Insurance Company of China Ltd
Priority date: 2024-08-30
Filing date: 2024-08-30
Publication date: 2024-12-03

Abstract

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 preferentially displayed from the cache database. 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 effective query results when the system interface is abnormal.

Description

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

Technical Field

The present invention relates to the field of data caching and query technologies, and in particular, to a cache fault tolerance method, device, equipment and storage medium for an claim settlement system.

Background

In modern claims systems, the efficiency and accuracy of data queries is critical to the user experience. Claim settlement systems are typically required to handle a large number of user query requests involving a variety of data operations such as case status queries, claim settlement progress tracking, customer information verification, and the like. However, since the claim system relies on real-time responses from the backend servers, these operations may be affected by network delays, server loads, and other uncontrollable factors, resulting in slow or even non-functioning system responses.

In order to improve the response speed and stability of the system, many claim settlement systems introduce a data caching mechanism. Through caching techniques, the system can store frequently accessed data locally to reduce reliance on backend servers. However, existing caching mechanisms generally only work when the claim system interfaces are normal, and when the interfaces are abnormal, the system may still not provide effective query results to the user. In addition, in the prior art, the management of the cache data is simpler, a fixed cache refreshing strategy is generally adopted, and the updating frequency and the reservation strategy of the cache data cannot be dynamically adjusted according to the actual operation of a user, so that the problem that the cache data is old or irrelevant to a certain extent is caused, and the accuracy and timeliness of a query result are further influenced.

With the continuous improvement of the requirements of users on the response speed and the service stability of the system, the existing cache management method cannot meet the actual application requirements. Particularly, under the conditions of unstable network environment and untimely response of a back-end system, how to improve the fault tolerance of the system while ensuring the data query speed becomes a technical problem to be solved urgently. Therefore, a more intelligent and flexible cache management method is needed, which can effectively manage and update cache data under the condition that the system interface is normal and abnormal, and ensure the accuracy of user inquiry and the timeliness of system response.

Disclosure of Invention

The invention mainly aims to provide a cache fault-tolerant method, device, equipment and storage medium of an claim settlement system, and aims to solve the technical problem that a cache mechanism of the existing claim settlement system cannot effectively provide a query result when an interface is abnormal.

In order to achieve the above object, the present invention provides a buffer fault tolerance method of an claim settlement system, the buffer fault tolerance method of the claim settlement system includes the following steps:

recording operation behavior records of a user through a user operation tracking mechanism, generating a cache database according to the operation behavior records, and monitoring whether interface call of the claim settlement system is normal or not;

When the fact that the user performs data query operation and the interface call of the claim settlement system is normal is monitored, displaying first preset quantity of data in the cache database, and querying the target data through the claim settlement system and returning a query result if the displayed data does not contain target data queried by the user;

and when the condition that the user performs data query operation and the interface call of the claim system is abnormal is monitored, retrieving target data queried by the user from the cache database, and if the cache database contains the target data, returning a query result of the target data.

Optionally, if the displayed data does not include the target data queried by the user, querying the target data through the claim settlement system and returning a query result, 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, inquiring the target data through the claim settlement system and returning an inquiry result;

and if the cache database contains the target data, returning a query result of the target data.

Optionally, after retrieving the target data of the user query from the cache database, the method further comprises:

if the target data is not contained in the cache database, counting query keywords of a user into a cache refreshing queue;

and after the interface call of the claim settlement system is monitored to be normal, inquiring target data corresponding to the inquiring keywords from the claim settlement system and storing the target data into the cache database.

Optionally, querying target data corresponding to the query keyword from the claim settlement system and storing the target data in the cache database, including:

If a plurality of query keywords exist in the cache refreshing queue, calculating the weight of each query keyword, sequentially querying corresponding target data according to the weight of each query keyword, and storing the target data in the cache database.

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

And constructing the cache database, and when the operation behavior record is a list browsing record, storing a second preset number of data in a user browsing list into the browsing cache data set by the cache database comprising the browsing cache data set.

Optionally, after storing the second preset amount of data in the user browsing list in the cache database, the method further includes:

when the operation behavior record further comprises a search operation record, the cache database further comprises a search cache data set, search keywords are screened from the browse cache data set according to user search words, and the search keywords and corresponding search data are stored in the search cache data set.

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

Setting a valid period for each data according to the browsing times or searching times of each data in the cache database, and detecting whether the data in the cache database exceeds the valid period or not in each interval preset time period;

if yes, removing the data exceeding the validity period from the cache database.

Further, in order to achieve the above object, the present invention further provides a buffer fault-tolerant device of a claim settlement system, where the buffer fault-tolerant device of the claim settlement system includes:

The cache generation module records the operation behavior record of a user through a user operation tracking mechanism, generates a cache database according to the operation behavior record, and monitors whether the interface call of the claim settlement system is normal or not;

The normal query module is used for displaying a first preset amount of data in the cache database when the fact that the user performs data query operation and the interface call of the claim settlement system is normal is monitored, and querying the target data through the claim settlement system and returning a query result if the displayed data does not contain target data queried by the user;

And the abnormal query module is used for retrieving target data queried by the user from the cache database when the condition that the user performs data query operation and the interface of the claim settlement system calls abnormality is monitored, and returning a query result of the target data if the target data is contained in the cache database.

Further, to achieve the above object, the present invention further provides a cache fault-tolerant device of an claim system, where the cache fault-tolerant device of the claim system includes a memory, a processor, and a cache fault-tolerant program of the claim system stored on the memory and capable of running on the processor, where the cache fault-tolerant program of the claim system is executed by the processor to implement the steps of the cache fault-tolerant method of the claim system as described above.

Further, to achieve the above object, the present invention further provides a computer storage medium, where a cache fault-tolerant program of the claim settlement system is stored, where the cache fault-tolerant program of the claim settlement system, when executed by a processor, implements the steps of the cache fault-tolerant method of the claim settlement system as described above.

The invention relates to a cache fault-tolerant method of a claim settlement system, which records the operation behavior of a user through a user operation tracking mechanism and generates a cache database according to the recorded data. And monitoring the calling state of the interface of the claim settlement system in real time, when the interface is normally called, preferentially displaying the preset quantity of data from the cache database, and if the cache data cannot meet the query requirement of the user, acquiring and returning the latest query result through the interface of the claim settlement system. Under the condition of abnormal interface call, target data queried by a user can be retrieved from a cache database, and under the condition that the target data is contained in the cache data, a query result is directly returned. The invention obviously improves the data query efficiency and response speed of the system under different working states by dynamically adjusting the cache management strategy, enhances the fault tolerance of the system, and ensures that a user can still obtain an effective query result when the system interface is abnormal.

Drawings

FIG. 1 is a schematic diagram of a device hardware operating environment according to an embodiment of a cache fault tolerance device of the claim system of the present invention;

FIG. 2 is a flowchart illustrating a first embodiment of a cache fault tolerance method of the claim system of the present invention;

FIG. 3 is a schematic diagram of functional modules of a buffer fault tolerance device of the claim system according to a preferred embodiment of the present invention.

The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

It should be noted that in modern claim settlement systems, the efficiency and accuracy of data queries is critical to the user experience. Claim settlement systems are typically required to handle a large number of user query requests involving a variety of data operations such as case status queries, claim settlement progress tracking, customer information verification, and the like. However, since the claim system relies on real-time responses from the backend servers, these operations may be affected by network delays, server loads, and other uncontrollable factors, resulting in slow or even non-functioning system responses.

In view of the above drawbacks, the present invention provides a cache fault-tolerant device of an claim system, and referring to fig. 1, fig. 1 is a schematic structural diagram of a device hardware operating environment related to an embodiment of the cache fault-tolerant device of the claim system.

As shown in FIG. 1, the cache fault tolerance of the claim 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. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., 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 optionally be a storage device separate from the processor 1001 described above.

Those skilled in the art will appreciate that the hardware architecture of the cache fault tolerance device of the claim system shown in fig. 1 does not constitute a limitation on the cache fault tolerance device of the claim system, and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

As shown in fig. 1, a memory 1005, which is a storage medium, may include an operating system, a network communication module, a user interface module, and a cache fault tolerance program of the claim system. The operating system is a program for managing and controlling the cache fault-tolerant device and software resources of the claim settlement system, and supports the operation of a network communication module, a user interface module, the cache fault-tolerant program of the claim settlement system and other programs or software, wherein the network communication module is used for managing and controlling the network interface 1004, and the user interface module is used for managing and controlling the user interface 1003.

In the hardware structure of the cache fault-tolerant device of the claim system shown in fig. 1, the network interface 1004 is mainly used for connecting a background server and performing data communication with the background server, the user interface 1003 is mainly used for connecting a client and performing data communication with the client, and the processor 1001 may call the cache fault-tolerant program of the claim system stored in the memory 1005 and perform the following operations:

Further, if the displayed data does not include the target data queried by the user, querying the target data through the claim settlement system and returning a query result, including:

Further, after retrieving the target data of the user query from the cache database, the method further comprises:

Further, querying target data corresponding to the query keyword from the claim settlement system and storing the target data in the cache database, including:

Further, generating a cache database according to the operation behavior record, including:

Further, after storing the second preset amount of data in the user browsing list in the cache database, the method further includes:

Further, after generating the cache database according to the operation behavior record, the method further comprises:

The specific implementation manner of the buffer fault-tolerant device of the claim system is basically the same as each embodiment of the buffer fault-tolerant method of the claim system described below, and is not repeated here.

The invention also provides a cache fault-tolerant method of the claim settlement system based on the cache fault-tolerant device of the claim settlement system.

Referring to fig. 2, fig. 2 is a flowchart illustrating a first embodiment of a buffer fault tolerance method of the claim system according to the present invention.

Embodiments of the present invention provide embodiments of a cache fault tolerance method for claim settlement systems, it being noted that although a logical sequence is illustrated in the flow chart, in some cases the steps illustrated or described may be performed in a different order than that illustrated herein.

In various embodiments of the cache fault tolerance method of the claim system, the execution body is a cache fault tolerance device of the claim system.

The cache fault-tolerant method of the claim settlement system is applied to the cache fault-tolerant device of the claim settlement system, and comprises the following steps:

Step S10, recording operation behavior records of a user through a user operation tracking mechanism, generating a cache database according to the operation behavior records, and monitoring whether interface call of the claim settlement system is normal or not;

In this embodiment, various operation behaviors of the user during the use of the claim system are tracked and recorded in real time, such as the user browsing certain pages, searching for specific information, clicking certain buttons, and the like. These behavior data may include the number of clicks of the user, dwell time, search keywords entered, etc. Through these operational behavior records, the user's usage habits and preferences can be understood in depth and used to further optimize performance.

A cache database is a set of copies of data stored locally for the purpose of accelerating data queries. By analyzing the operation behavior of the user, it is possible to predict contents that the user may access again and store them in the cache database in advance. The method can obviously improve the response speed of the system and reduce the dependence on a remote server.

And continuously monitoring the interface state of the claim settlement system, and judging whether the claim settlement system works normally or not. This includes detecting whether the interface is able to respond to the request in time, whether the data transfer is normal, etc. If the interface call is normal, the user request is processed according to a preset flow, and if the interface call is abnormal, the operation mode is switched to a standby operation mode, for example, the buffer data is preferentially used for responding to the user request.

A specific embodiment may be that the user operation tracking mechanism continuously records the user's operation behavior in the claim settlement system, such as browsing cases, submitting queries, etc. Based on these behavior records, a cache database is generated by periodic analysis, and data that may be accessed again by the user, such as the recently queried case state, common pages, etc., are cached in advance. This way, the response can be provided quickly when the user accesses again.

When processing a user query request, the call state of the claim system interface is checked first. If the interface is normal, part of data is returned from the cache database quickly, and the latest data is acquired from the claim settlement system and the result is returned. If the interface is abnormal, the target data queried by the user is directly retrieved from the cache database and returned, so that the user can obtain the query result in time even if the interface is temporarily unavailable.

Example description:

Assume that a user queries status information of the same case number multiple times. The operation tracking mechanism records these actions and stores the data associated with the case number in a cache database. When the user queries the case again, the interface state is monitored first. If the interface is normal, part of data is returned from the cache quickly, and the latest data update is acquired. If the interface is abnormal, the relevant data is directly retrieved from the cache database and returned, so that timeliness of the query result is ensured.

Through the steps, the service can be provided efficiently and stably under different conditions, and the use experience of a user and the overall reliability of the system are improved.

Step S20, when the fact that the user performs data query operation and the interface call of the claim settlement system is normal is monitored, displaying first preset quantity of data in the cache database, and if the displayed data does not contain target data queried by the user, querying the target data through the claim settlement system and returning a query result;

in the present embodiment, the explanation of the related technical features is as follows:

And data query operation, namely, when a user uses the claim settlement system, initiating a data query operation, such as querying the state of a certain case, the claim settlement progress or the client information and the like.

And the interface call is normal, namely the monitoring mechanism confirms that the interface call of the claim settlement system is normal, namely the system can normally communicate with a background server or a database, and the data transmission and the query request can be smoothly carried out.

And displaying the preset data in the cache database, namely, after the interface is determined to be normal, firstly extracting and displaying a certain amount of preset data, namely, a first preset amount of preset cache data, from the cache database by the system, wherein the data are usually the most likely data which are required by a user and are accessed recently or at high frequency.

And inquiring target data, namely if the data displayed in the cache cannot meet the inquiry requirement of the user, namely the cache data does not contain target data inquired by the user, the system can call a background database or a server of the claim settlement system in real time, inquire the latest target data and return the inquiry result to the user.

The specific implementation mode is that a user inputs a case number or other query conditions in a query interface to submit a query request. And checking the interface calling state of the claim settlement system, and confirming whether the communication between the interface and the background server is normal. And under the condition that the interface is normal, preferentially extracting the first preset quantity of data from the cache database for display. Such data typically includes case information last accessed by the user, data related to query conditions, or other high frequency access data. If the target data of the user query is not found in the cache database, the background server of the claim settlement system is used for carrying out real-time query, obtaining the latest data and returning the query result.

Example description:

And the user inquires the current processing state of a certain case through the claim settlement system.

Query operation the user enters the case number "12345" and submits a query request.

And monitoring interface state, namely detecting the calling state of the interface of the claim settlement system, confirming that normal communication can be realized and acquiring data.

And displaying the cache data, namely displaying the data of the last accessed first 5 cases stored in the cache database.

And querying target data, namely finding that the cache data does not contain information of the case number '12345', querying the latest state of the case through a background server of the claim settlement system, and returning the result to the user.

Through the steps, under the condition that the interface is normal, the query request of the user can be responded quickly through the cache data, and the real-time data can be acquired when necessary, so that the accuracy and timeliness of the query result are ensured.

And step S30, when the condition that the user performs data query operation and the interface call of the claim settlement system is abnormal is monitored, searching target data queried by the user from the cache database, and if the cache database contains the target data, returning a query result of the target data.

In this embodiment, when a user initiates a query operation in the claim settlement system, if an interface call abnormality with the background server is detected, that is, the system cannot acquire real-time data through a normal communication channel.

And under the condition of abnormal interface call, searching target data queried by the user through the local cache database. The cache database typically pre-stores relevant data that the user may access in order to continue providing service in the event of an interface abnormality.

If the target data of the user query is found in the cache database, the cache data is directly used as a query result to be returned to the user. Therefore, under the condition that the interface cannot be accessed, the user can still obtain the query result, and the influence of service interruption on the user experience is reduced as much as possible.

Specific embodiments may be:

when the user inputs the query condition (such as a case number) in the query interface and submits the request, the interface of the claim settlement system can not normally communicate.

And (3) searching the cache database, namely immediately searching target data queried by a user from the local cache database under the condition of abnormal interfaces. The cache database contains the data stored before the system, which is accessed frequently or at high frequency, and is updated periodically when the interface is normal for subsequent querying.

And returning the cache data, namely if the cache database contains target data queried by the user, such as the processing state of the case number, directly using the cache data as a query result and returning the query result to the user. This way it is ensured that the user is able to still obtain relevant query information in case of an interface abnormality.

Example description:

The user inquires the current processing state of a certain case, and the interface of the claim settlement system calls an exception.

Query operations and interfaces are abnormal-the user enters the case number "12345" and submits a query request. However, the system detects that the interface of the claim settlement system cannot normally communicate with the background server, and the data request cannot be completed.

And (4) searching the cache database, namely immediately searching relevant data of the case number '12345' from the cache database after the interface abnormality is detected. The data may be pre-stored when the interface is normal, including the last processing state of the case and other relevant information.

And returning the cached data, namely immediately returning the query result from the cache to the user due to the fact that the data of the case number '12345' is contained in the cache database. This ensures that even in the event of interface abnormality, the user can acquire the processing information of the case in time.

Through the steps, even when a problem occurs in the system interface, a user can still obtain a valuable query result, so that the reliability and the user experience of the system are improved.

Further, a second embodiment of the cache fault tolerance method of the claim system of the present invention is provided, in the step S20, if the displayed data does not include the target data queried by the user, querying the target data through the claim system and returning a query result, including:

step a1, if the displayed data does not contain target data queried by a user, retrieving the target data queried by the user from the cache database;

step a2, if the cache database does not contain the target data, inquiring the target data through the claim settlement system and returning an inquiry result;

and a3, if the cache database contains the target data, returning a query result of the target data.

In this embodiment, if the initially displayed data does not include 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 typically stores data that a user may have previously queried in order to speed up the query response.

If the cache database also does not contain the target data queried by the user, the further processing step is to query the latest target data through a background database or server of the claim settlement system. This ensures that the user can obtain the latest and accurate query results.

If the cache database contains target data queried by the user, the data is directly extracted from the cache and returned to the user. The step can obviously reduce the inquiry time and improve the response speed of the system, especially under the condition that the interface of the claim system is normal.

Specific embodiments may be:

When a user initiates a data query operation, if the initially displayed data does not contain target data queried by the user, the data is processed according to the following steps:

And (3) searching the cache database, namely after a user initiates a query operation, firstly searching target data from the cache database. The cache database generally stores data such as case states, claim information and the like which are possibly queried by a user, and is used for quickly responding to the query request of the user.

And (3) processing the cache data, namely if target data queried by the user are found in the cache database, immediately using the cache data as a query result and returning the query result to the user. This way, the query time can be significantly shortened, especially in the case where the user repeatedly queries the same target data.

And (3) real-time data query, namely if target data queried by the user cannot be found in the cache database, real-time query is needed through a background database or a server of the claim settlement system. And acquiring the latest target data through real-time query, and returning the result to the user. This step ensures the accuracy and real-time of the data.

Example description:

The user inquires the current processing state of a certain case, but the initially displayed data does not contain the target case information.

The cache database is retrieved, and after the user enters the case number "67880" and submits the query request, the data associated with the case number "67880" is first retrieved from the cache database.

And (3) processing cache data, namely retrieving information containing a case number of 67880 in a cache database, wherein the information comprises processing states and other relevant details of the case. Therefore, the cached data is directly returned to the user as the query result. The user can quickly obtain the case information without waiting for a real-time query process.

Real-time data query, namely if the related data of the file number '67880' cannot be found in the cache database, real-time query is carried out through a background database of the claim settlement system. The latest case processing state is acquired, and the query result is returned to the user, so that the user is ensured to obtain the latest and accurate case information.

Through the steps, the query request of the user can be flexibly processed under different conditions, the response speed is increased by using the cached data, the latest data can be obtained through real-time query when necessary, and the user experience and the accuracy of the query result are ensured.

Further, a third embodiment of the cache fault tolerance method of the claim system of the present invention is provided, wherein in the step S30, after retrieving the target data queried by the user from the cache database, the method further includes:

Step b1, if the target data is not contained in the cache database, counting query keywords of a user into a cache refreshing queue;

and b2, inquiring target data corresponding to the inquiring keywords from the claim system and storing the target data into the cache database after monitoring that the interface call of the claim system is normal.

In this embodiment, if the target data of the user query is not found in the cache database, the system records the query key words (e.g., file number, client ID, etc.) used by the user and adds them to the cache refresh queue. The cache refresh queue is a data list waiting to be updated for refreshing data in the cache database at an appropriate timing.

The interface state of the claim system is continuously monitored, and when the interface call is recovered to be normal is judged. Only if the interface is normal, the system can perform real-time data query and cache refreshing operation.

And once the interface call of the claim settlement system is monitored to be normal, automatically triggering the processing of the query keywords in the cache refreshing queue, and sending a data query request to the claim settlement system. The queried target data will be stored in the cache database so that the data can be provided faster upon subsequent queries.

Specific embodiments may be:

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

And the query keywords are added into the cache refreshing queue, namely, when the target data queried by the user is not contained in the cache database, the query keywords (such as a case number) input by the user are recorded, and the keywords are added into the cache refreshing queue. The queue is used for updating the cache database after the interface of the claim system returns to normal.

And monitoring the state of the interface of the claim settlement system, namely continuously monitoring the state of the interface of the claim settlement system until the interface call is recovered to be normal. During this time, the keywords in the cache flush queue will temporarily wait for processing.

And (3) inquiring the target data and updating the cache, namely, after the interface state is recovered to be normal, sequentially processing the inquiry keywords in the cache refreshing queue and inquiring the corresponding target data. The queried data is stored in a cache database to improve the response speed of subsequent queries and the availability of the data.

Example description:

The user inquires the state information of a certain case, but the data of the case is not contained in the cache database, and meanwhile, the interface of the claim settlement system calls abnormity.

The query keyword is added to the cache refresh queue, and a user inputs a case number of 12345 and initiates a query operation. After the data of the case number '12345' is not found in the cache database, the '12345' is used as a query keyword record and added into a cache refreshing queue to wait for the subsequent refreshing.

And (3) inquiring target data and updating a cache, namely immediately extracting a keyword '12345' from a cache refreshing queue once the interface of the claim settlement system is recovered to be normal, and inquiring the latest state information of the case through a background server of the claim settlement system. The acquired data is stored in a cache database, so that the result can be returned more quickly when the next inquiry is performed.

Through the steps, even under the condition of abnormal interfaces, the embodiment can ensure that the subsequent cache data updating operation can be performed in time, optimize the query experience and improve the response speed.

Further, a fourth embodiment of a cache fault tolerance method of the claim system of the present invention is provided, in the step b2, the querying, from the claim system, the target data corresponding to the query keyword and storing the target data in the cache database, including:

Step c1, if a plurality of query keywords exist in the cache refreshing queue, calculating the weight of each query keyword, sequentially querying corresponding target data according to the weight of each query keyword, and storing the target data in the cache database.

In this embodiment, when there are multiple query keywords in the cache flush queue, these keywords may be due to user query requests accumulated during system interface anomalies or other reasons. Efficient processing of these keywords is required to optimize the efficiency of cache updates.

The weight of each query keyword is calculated according to a plurality of factors, such as the query frequency of the keyword, the emergency demand level of the user on the related data, the historical query record and the like. The higher weighted keywords indicate that their corresponding data is more important or urgent in the user query.

After the weight of each query keyword is calculated, the keywords are sequentially processed in the order of the weights from high to low. Firstly, processing the keyword with highest weight, inquiring corresponding target data through the claim settlement system, and storing the inquired data into a cache database. The method ensures that the most critical data can be updated to the cache database preferentially, and improves the response speed and user experience of the system.

Specific embodiments may be:

when the system interface is recovered to be normal and a plurality of query keywords are accumulated in the cache refreshing queue, the system processes the keywords, and the specific steps are as follows:

The weights of the query keywords are calculated, and each query keyword is given a weight according to the importance and the emergency degree. The weight calculation can consider factors such as the query frequency of the keywords, the urgency of the user on the data, the historical query times and the like.

And sequencing and sequentially processing according to the weights, namely sequentially processing the query keywords from high to low according to the calculated weights. Firstly, processing the keyword with highest weight, and inquiring the corresponding target data through the claim settlement system.

Updating the cache database, namely storing target data queried by the claim settlement system into the cache database to ensure that the data with high priority can quickly respond when the user queries again. And sequentially processing all query keywords until the data in the cache refreshing queue is updated completely.

Example description:

During abnormal interface period, the case numbers queried by multiple users are accumulated in the cache refreshing queue, and the case numbers need to be queried and updated in sequence after the interface is recovered to be normal.

The weights of the query keywords are calculated assuming that three case numbers, "A12345", "B67880", and "C54321" are accumulated in the cache flush queue. First, a weight is calculated for each case number, for example, "B6789" is highest in weight due to being queried multiple times and involving high amount claims, "A12345" is less frequently queried and "C54321" is lowest in weight.

And sequencing and sequentially processing the three case numbers according to the order of the weights from high to low. The highest weighted "B6789" is processed first and the latest state information of the case is queried through the claim settlement system.

Updating the cache database, namely storing the queried data of B67880 into the cache database, so as to ensure that the data can quickly respond when the user queries next time. Next, process "A12345" and finally process "C54321" until all data in the cache flush queue is updated.

Through the steps, the most important query request can be processed preferentially, and the most critical data is ensured to be stored preferentially in the cache database all the time, so that the response speed of the user query and the overall efficiency of the system are improved.

Further, a fifth embodiment of a cache fault tolerance method of the claim system of the present invention is provided, in the step S10, the generating a cache database according to the operation behavior record includes:

And d1, constructing the cache database, and when the operation behavior record is a list browsing record, storing a second preset number of data in a user browsing list into the browsing cache data set by the cache database comprising the browsing cache data set.

In this embodiment, a cache database is generated based on the user's operational records, particularly those related to list browsing. The database is used for improving the response speed of subsequent queries and reducing the dependence on a remote server.

When a user browses a list of data (e.g., a list of cases, a list of clients, etc.) in the claims system, these actions will be recorded and used as a basis for generating a cache database.

A special browsing cache data set is set in the cache database, and key data related to browsing operation of a user is stored. This dataset contains a core of list data for display to the user to ensure quick access to the data.

A specific amount or range, i.e. a second preset amount, of data in the data list for display to the user 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 accesses again, the data is quickly extracted from the cache without having to be acquired from the remote server each time.

Specific embodiments may be:

When a user browses a list of data in the claims system, the operational behavior record will be captured and used to generate or update a cached database, particularly a browse cached data set for accelerating subsequent accesses.

And constructing a cache database, namely analyzing related operation behavior records and generating the cache database when a user performs list browsing operation. The establishment of the cache database is helpful to improve the response speed of subsequent access.

And identifying and recording list browsing operation, namely capturing and recording specific behaviors of a user when browsing the data list. These records include pages accessed by the user and viewed data items that serve as the basis for creating cached data.

Storing list data for display to the user in a cache storing a particular amount or range of data in a list of data for display to the user in a browsing cache data set. These cached data items may include case numbers, case states, applicant information, and so forth. At the next access, the data can be directly extracted from the cache and displayed, thereby improving the response speed and reducing the dependence on the server.

Example description:

In the claim settlement system, a user browses the case list, generates a cache database based on the operation behavior, and caches a specific range of contents of the data list for display to the user.

And establishing a cache database, namely opening a case list in the claim settlement system by a user and browsing a certain amount of data, wherein the data comprises case numbers, case states, applicant information and the like.

And recording list browsing operation, namely recording browsing behaviors of the user, including specific viewed cases and accessed pages. These records are used to generate cached data to speed up subsequent accesses.

The storage of the cached data is to store a specific amount or range of data in the list of cases (e.g., the information of the first 20 cases or the most commonly accessed portion of the user) into the browsing cache data set. Therefore, when the case list is accessed next time, the data can be directly extracted from the cache and displayed, the dependence on a remote server is reduced, and the response speed is remarkably improved.

Through the steps, the embodiment can effectively cache the content of the data list frequently accessed by the user, ensure that a faster and smoother experience can be provided when the user accesses the data list again, and simultaneously maintain flexibility so as to adapt to different system requirements and user habits.

Further, a sixth embodiment of the cache fault tolerance method of the claim system of the present invention is provided, where after step d1, the method further includes:

And e1, when the operation behavior record further comprises a search operation record, the cache database further comprises a search cache data set, search keywords are screened out from the browse cache data set according to user search words, and the search keywords and corresponding search data are stored in the search cache data set.

In this embodiment, in the operation behavior records of the user, if it is recognized that there are search operation records, the system further optimizes the structure and content of the cache database according to the records.

A special search cache data set is established in the cache database for storing data associated with the user search operation. This data set will contain keywords in the user's search behavior and their corresponding data.

And screening keywords related to the user search operation from the browsing cache data set based on the search words of the user. These keywords can help quickly locate data that the user may be querying again.

And storing the screened search keywords and the corresponding search result data into a search cache data set. Thus, when the user uses the same or similar search words again, the system can quickly extract the results from the search cache data set, and the response speed is improved.

Specific embodiments may be:

In the case of a user browsing through list data and conducting a search operation, the operational behavior records will be further analyzed and processed to optimize search-related data storage in the cache database.

And (3) identifying the search operation record, namely after the user browses the data and finishes caching the list data, checking whether the user performs the search operation or not by the system. If a search operation record is identified, a further cache optimization step is initiated.

A search cache data set is created in which a search cache data set is created in addition to stored browsing data. This dataset is dedicated to storing keywords and corresponding data in the user's search behavior.

Screening search keywords, namely screening keywords related to search operation from the browsing cache data set according to the search words input by the user. These keywords may be frequently searched content by the user, with a high likelihood of re-querying.

Storing the search keywords and the corresponding data, namely storing the screened search keywords and the corresponding data thereof into a search cache data set. Thus, when the user uses the same or similar search words next time, the data can be directly extracted from the search cache data set, and the query speed is remarkably improved.

Example description:

After browsing the case list in the claim settlement system, the user performs one-time searching operation, and the system generates and optimizes a cache database according to the operation behavior.

And identifying a search operation record, namely inputting a case number or the name of the applicant for searching after the user browses the case list. The system recognizes the search operation and prepares to further optimize the cached database.

And creating a search cache data set, namely creating a search cache data set in a cache database by the system, and specially storing keywords and related data in the search behavior of the user.

Screening and storing search keywords, namely screening relevant search keywords from the stored browsing cache data set according to the search words input by the user. For example, the user has searched for "case number 12345", and the system screens out the case number and its associated data and stores it in the search cache dataset.

And optimizing the query speed, namely, when the user searches for the 'case number 12345' or similar keywords again, the system can directly extract and return data from the search cache data set without re-querying from a remote server, so that the query response speed is remarkably improved.

Through the steps, the cache database not only can accelerate browsing operation of a user, but also can optimize response speed of searching operation, and further improves user experience and system efficiency.

Further, a seventh embodiment of the cache fault tolerance method of the claim system of the present invention is provided, where in step S10, after generating the cache database according to the operation behavior record, the method further includes:

Step f1, setting a valid period for each data according to the browsing times or searching times of each data in the cache database, and detecting whether the data in the cache database exceeds the valid period or not in each interval preset time period;

And f2, if yes, removing the data exceeding the validity period from the cache database.

In this embodiment, an expiration date is set for each data item according to the number of browses or searches for each data item in the cache database. The duration of the validity period depends on the frequency of use of the data, i.e. data with a high access frequency may have a longer validity period, while data with a low access frequency may have a shorter validity period.

And detecting data in the cache database every other preset time period to judge which data have exceeded the set validity period. This detection mechanism ensures that the data in the cache database remains fresh and useful all the time, avoiding that obsolete or no longer needed data occupies the cache space.

For data that is detected to have exceeded the validity period, it is removed from the cache database. This releases the cache space and ensures that the contents of the cache database are always up-to-date and relevant to the user's needs.

Specific embodiments may be:

After the operation behavior record of the user generates the cache database, the data in the database is further managed to ensure the efficient operation of the user.

And setting the validity period of the data, wherein after the generation of the cache database, the system sets a validity period for each data according to the browsing times or searching times of each data item. For example, case data that is browsed or searched frequently may be set to a longer validity period, while data that is less accessed is set to a shorter validity period.

The validity period of the data is periodically checked, that is, the system checks the data in the cache database every other preset time period (such as daily, weekly or monthly) to judge which data has exceeded the set validity period. The detection process may be automated, ensuring that no manual intervention is required.

And removing the expired data, namely removing the data exceeding the validity period from the cache database by the system. The purpose of this is to free up buffer space, avoiding outdated data from occupying resources, thus ensuring that the data in the buffer database is always efficient and useful.

Example description:

in the claim settlement system, a cache database is generated and managed according to the operation behaviors of users, and the system sets and periodically checks the validity period of data.

The validity period is set, namely, a user frequently inquires the state of a file number 'ABC 123', and the data is set to be longer in the validity period in the cache database. For the case number of XYZ789, which is rarely queried by the user, the data sets a shorter validity period.

And (3) periodically detecting, namely automatically detecting data in the cache database by the system every other week, and checking which data have exceeded the set validity period. For example, the system finds that case number "XYZ789" has exceeded its expiration date, while case number "ABC123" is still within the expiration date.

And removing the expired data, namely removing the data of the case number 'XYZ 789' from the cache database by the system, and releasing the cache space. And the data of the case number 'ABC 123' is kept in the cache database because the data is still in the validity period, so that the user can still access quickly during the subsequent inquiry.

Through the steps, the content of the cache database can be dynamically adjusted and optimized, so that the system can provide the latest and most relevant data for users while keeping high-efficiency operation. The mechanism not only improves the utilization rate of data, but also improves the overall performance of the system.

The invention also provides a cache fault-tolerant device of the claim settlement system.

Referring to fig. 3, fig. 3 is a schematic functional block diagram of a first embodiment of a buffer fault tolerance device of the claim system of the present invention. The cache fault-tolerant device of the claim settlement system comprises:

In addition, the embodiment of the invention also provides a computer storage medium.

The storage medium stores a cache fault-tolerant program of the claim system, and the cache fault-tolerant program of the claim system, when executed by the processor, implements the steps of the cache fault-tolerant method of the claim system as described above.

The specific implementation manner of the storage medium of the present invention is basically the same as the embodiments of the buffer fault tolerance method of the claim settlement system, and will not be described herein.

While the embodiments of the present invention have been described above with reference to the drawings, the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many modifications may be made thereto by those of ordinary skill in the art without departing from the spirit of the present invention and the scope of the appended claims, which are to be accorded the full scope of the present invention as defined by the following description and drawings, or by any equivalent structures or equivalent flow changes, or by direct or indirect application to other relevant technical fields.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative, for example, of the flowcharts and block diagrams in the figures that illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In addition, functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part. The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. The storage medium includes various media capable of storing program codes, such as a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, randomAccess Memory), a magnetic disk, or an optical disk.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.

The above description is merely illustrative of various embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about variations or substitutions within the scope of the present application, and the application is intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. The cache fault tolerance method of the claim settlement system is characterized by comprising the following steps:

2. The cache fault tolerance method of claim 1, wherein if the displayed data does not include target data queried by a user, querying the target data and returning a query result by the claim system, comprising:

3. The cache fault tolerance method of claim 1, further comprising, after retrieving target data for a user query from the cache database:

4. The cache fault tolerance method of claim 3, wherein querying target data corresponding to the query keyword from the claim system and storing the target data in the cache database comprises:

5. The cache fault tolerance method of claim 1, wherein generating a cache database from the operational behavior record comprises:

6. The cache fault tolerance method of claim 5, further comprising, after storing a second predetermined amount of data in the user browsing list in the cache database:

7. The cache fault tolerance method of claim 1, further comprising, after generating a cache database from the operational behavior records:

8. A cache fault tolerance apparatus for a claim system, the cache fault tolerance apparatus comprising:

9. A cache fault tolerance device of a claim system, characterized in that the cache fault tolerance device of the claim system comprises a memory, a processor and a cache fault tolerance program of the claim system stored on the memory and executable on the processor, the cache fault tolerance program of the claim system, when executed by the processor, implementing the steps of the cache fault tolerance method of the claim system according to any one of claims 1-7.

10. A computer storage medium, wherein a cache fault tolerant program of a claim system is stored on the storage medium, and the cache fault tolerant program of the claim system, when executed by a processor, implements the steps of the cache fault tolerant method of the claim system as claimed in any one of claims 1-7.