Data synchronization and cache management method and system based on offline priority architecture, storage medium and electronic equipment

Abstract

The invention provides a data synchronization and cache management method and system based on an offline priority architecture, a storage medium and electronic equipment, and the method comprises the steps: intercepting a network request and locally caching target data when the equipment is in an offline state; when the network connection of the equipment is recovered, data synchronization is automatically carried out on the locally cached target data and the server side; based on a version control mechanism, performing conflict detection and solution on a data synchronization process; after data synchronization is completed, periodically checking the validity of locally cached target data based on a cache management mechanism; and based on the update or expiration strategy, according to the validity check result, performing optimization processing on the target data. According to the method, data consistency and integrity are enhanced, data conflicts are automatically detected and solved, data loss or errors are avoided, user experience is improved, data management and storage are more efficient, and better compatibility and cross-platform support are achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of computer data processing, and in particular to a data synchronization and cache management method, system, storage medium and electronic device based on an offline priority architecture. Background Art

[0002] With the popularization of Internet applications and the widespread use of smart devices, data access and operation in offline mode has become an important aspect of improving user experience. Especially when the network is unstable or there is no network connection, how to maintain application availability and ensure data consistency has become an important issue in current Web development.

[0003] Existing offline support technologies usually use a simple "Last-Writer-Wins (LWW)" strategy for data synchronization, but this strategy is prone to data conflicts and inconsistencies, and cannot effectively handle complex cache management issues. In addition, large applications are prone to cache management difficulties when offline, and problems such as expired cache and redundant data often reduce application performance and user experience.

[0004] Therefore, there is an urgent need for a more intelligent and reliable offline-first architecture to solve problems such as data synchronization, cache management, and user experience. Summary of the invention

[0005] One of the purposes of the present invention is to provide a data synchronization and cache management method based on an offline priority architecture, so as to solve the defects of the prior art in the above-mentioned background technology.

[0006] An embodiment of the present invention provides a data synchronization and cache management method based on an offline priority architecture, comprising:

[0007] When the device is offline, intercept network requests and cache target data locally; wherein the target data includes at least: static resources, dynamic data, and user data operations;

[0008] When the device restores the network connection, it automatically synchronizes the locally cached target data with the server.

[0009] Based on the version control mechanism, conflict detection and resolution are performed in the data synchronization process;

[0010] After data synchronization is completed, the validity of the target data in the local cache is regularly checked based on the cache management mechanism;

[0011] Based on the update or expiration strategy, the target data is optimized according to the validity check results.

[0012] Optionally, the version control mechanism includes:

[0013] Detect version conflicts that occur during data synchronization;

[0014] Based on the resolution strategy corresponding to the conflict type of the version conflict, the version conflict is resolved accordingly.

[0015] Optionally, the cache management mechanism includes:

[0016] Based on multiple validity check strategies, the validity of the locally cached target data is checked at preset time intervals.

[0017] Optionally, the update or expiration policy includes:

[0018] When the validity check result reflects that the target data needs to be updated, the target data is updated;

[0019] When the validity check result reflects that the target data needs to be removed, the target data is removed.

[0020] An embodiment of the present invention provides a data synchronization and cache management system based on an offline priority architecture, comprising:

[0021] A cache module, used to intercept network requests and cache target data locally when the device is offline; wherein the target data includes at least: static resources, dynamic data, and user data operations;

[0022] The synchronization module is used to automatically synchronize the locally cached target data with the server when the device restores the network connection;

[0023] The resolution module is used to detect and resolve conflicts in the data synchronization process based on the version control mechanism;

[0024] A checking module is used to periodically check the validity of the target data in the local cache based on the cache management mechanism after data synchronization is completed;

[0025] The optimization module is used to optimize the target data based on the update or expiration strategy and the validity check result.

[0026] Optionally, the version control mechanism includes:

[0027] Detect version conflicts that occur during data synchronization;

[0028] Based on the resolution strategy corresponding to the conflict type of the version conflict, the version conflict is resolved accordingly.

[0029] Optionally, the cache management mechanism includes:

[0030] Based on multiple validity check strategies, the validity of the locally cached target data is checked at preset time intervals.

[0031] Optionally, the update or expiration policy includes:

[0032] When the validity check result reflects that the target data needs to be updated, the target data is updated;

[0033] When the validity check result reflects that the target data needs to be removed, the target data is removed.

[0034] An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, and a processor executes the computer program to implement any of the above methods.

[0035] An embodiment of the present invention provides an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement any one of the methods described above.

[0036] The present invention has achieved the following beneficial effects:

[0037] Enhanced data consistency and integrity: Through a data synchronization strategy based on version control, data consistency and integrity are ensured after network recovery.

[0038] Automatically detect and resolve data conflicts to avoid data loss or errors and improve user experience: Provide complete offline functionality so that users can seamlessly access and operate data without a network connection; when the network is restored, data is automatically synchronized to ensure that users always see the latest information.

[0039] More efficient data management and storage: The use of advanced local storage technology and efficient data management mechanisms can better handle large amounts of data and complex data structures, and improve the performance and response speed of applications in offline states.

[0040] Better compatibility and cross-platform support: Through standardized technology and extensive testing, we ensure compatibility on various browsers and devices. No matter what device users use, they can get a consistent offline experience.

[0041] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description and the accompanying drawings.

[0042] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0044] Figure 1 A schematic diagram of a data synchronization and cache management method based on an offline priority architecture in an embodiment of the present invention;

[0045] Figure 2 Schematic diagram of a data synchronization and cache management system based on an offline priority architecture in an embodiment of the present invention. DETAILED DESCRIPTION

[0046] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0047] The embodiment of the present invention provides a data synchronization and cache management method based on an offline priority architecture, such as Figure 1 As shown, including:

[0048] S1. When the device is offline, intercept network requests and cache target data locally; wherein the target data includes at least: static resources, dynamic data, and user data operations; wherein static resources generally refer to files that do not change or rarely change after being stored on the server side, and these files can be directly sent to the client for display or use; dynamic data refers to data that changes according to user operations or system status, and these data are generally generated by the server or client program and dynamically sent to the client when needed; user data operations refer to user operation records on related data on the system, etc.;

[0049] S2. When the device restores the network connection, it automatically synchronizes the locally cached target data with the server.

[0050] S3. Based on the version control mechanism, conflict detection and resolution are performed on the data synchronization process;

[0051] S4. After data synchronization is completed, the validity of the target data in the local cache is regularly checked based on the cache management mechanism;

[0052] S5. Based on the update or expiration strategy and the validity check result, the target data is optimized.

[0053] The present invention has achieved the following beneficial effects:

[0054] Enhanced data consistency and integrity: Through a data synchronization strategy based on version control, data consistency and integrity are ensured after network recovery.

[0055] Automatically detect and resolve data conflicts to avoid data loss or errors and improve user experience: Provide complete offline functionality so that users can seamlessly access and operate data without a network connection; when the network is restored, data is automatically synchronized to ensure that users always see the latest information.

[0056] More efficient data management and storage: The use of advanced local storage technology and efficient data management mechanisms can better handle large amounts of data and complex data structures, and improve the performance and response speed of applications in offline states.

[0057] Better compatibility and cross-platform support: Through standardized technology and extensive testing, we ensure compatibility on various browsers and devices. No matter what device users use, they can get a consistent offline experience.

[0058] The version control mechanism includes:

[0059] Detect version conflicts that occur during data synchronization;

[0060] Based on the resolution strategy corresponding to the conflict type of the version conflict, the version conflict is resolved accordingly.

[0061] Version conflicts include: concurrent modification conflicts (multiple users or nodes modify the same data item), deletion and modification conflicts (one node deletes data while another node modifies the data), merge version conflicts (the synchronization status of different nodes is based on different historical versions, resulting in the inability to merge updates correctly), etc.

[0062] Corresponding solutions include: timestamp priority (compare the timestamps submitted by each node, the latest modification is considered to be the valid version), version priority (each synchronization node has its own version number, and the newer version is applied first), merge priority (if the modification is to different parts of the data, merge), etc. Version control mechanism is a system for managing and tracking file changes, which is widely used in software development and other fields that need to manage document modifications. It can help team collaboration, record historical versions, and restore to previous versions when necessary.

[0063] The cache management mechanism includes:

[0064] Based on multiple validity check strategies, the validity of the locally cached target data is checked at preset time intervals.

[0065] Validation strategies include verifying whether the data still meets the requirements of the application or system and whether it needs to be updated.

[0066] Cache management mechanism is a series of strategies and methods for managing cache data storage and access in computer systems. Cache is a high-speed storage layer used to temporarily store data in order to speed up data access and reduce latency.

[0067] The update or expiration policy includes:

[0068] When the validity check result reflects that the target data needs to be updated, the target data is updated;

[0069] When the validity check result reflects that the target data needs to be removed, the target data is removed.

[0070] Update or expiration strategy is a crucial component of cache management. Its main task is to ensure that the data in the cache is updated (to keep it up to date) or removed (to avoid expired data occupying cache space) at the right time. Usually, it is determined whether the data has expired or needs to be updated based on specific validity check criteria (such as the timestamp of the data, access frequency, usage pattern, etc.). Through reasonable update and expiration decisions, it is possible to avoid storing too much expired data in the cache, thereby improving the system's response speed, reducing cache pollution, and optimizing the use of storage space.

[0071] In one embodiment, when data synchronization is performed between the locally cached target data and the server, the synchronization is performed based on a data synchronization mechanism;

[0072] The steps for obtaining the data synchronization mechanism are as follows:

[0073] S21, determining whether to enter the mechanism planning timing based on the interaction track between the user and the device within the most recent preset time;

[0074] In S21, the most recent preset time may be the most recent 20 minutes; the user moves in reality to generate a movement trajectory, the user continues to interact with the device, and the generated interaction information is set on the movement trajectory at the actual position of the user when interacting, and the movement trajectory is finally used as the interaction trajectory; the interaction trajectory reflects the user's actual work and the interaction between the user and the device, so whether to enter the mechanism planning opportunity can be determined based on it; the mechanism planning opportunity is the opportunity when the user can perform data synchronization mechanism planning;

[0075] S22, when it is determined that the user has entered, assist the user in planning a data synchronization mechanism;

[0076] In S22, when it is determined that entry has been made, subsequent operations are performed, which improves the appropriateness of the timing for assisting the user, thereby improving the user experience; secondly, after being determined to be yes, the user is also assisted in planning a data synchronization mechanism, which improves the efficiency of the user in planning the data synchronization mechanism and further improves the user experience.

[0077] In one embodiment, S21, based on the interaction track between the user and the device within the most recent preset time, determining whether to enter the mechanism planning opportunity includes:

[0078] S211, determining a plurality of target trajectory nodes from the interaction trajectory; wherein, when determining, a target trajectory node is determined at a preset interval distance from the starting point of the interaction trajectory;

[0079] In S211, the interval distance may be 10 meters; the target trajectory node is a real location where an interaction occurs between a user and a device;

[0080] S211, determining a plurality of target trajectory node sets from each target trajectory node based on the first set of set constraints;

[0081] S212, when each target trajectory node set meets the second set of set constraints, it is determined that it is time to enter the mechanism planning;

[0082] The first set of constraints includes:

[0083] Condition A1: the same target trajectory node set contains more than N target trajectory nodes; wherein N is the rounded-up value of the product of the total number of target trajectory nodes multiplied by a preset proportional coefficient; in condition A1, the proportional coefficient may be 0.2;

[0084] as well as,

[0085] Condition A2: The trajectory scenes involved in each target trajectory node in the same target trajectory node set are the same or have a first scene association relationship between them; in condition A2, the trajectory scene involved is the scene where the target trajectory node is located in the user's real environment, which can be a work scene, etc.; the first scene association relationship can be the same scene type, the scenes belong to different sub-scenes of completing the same work task, etc.;

[0086] The second set of constraints includes:

[0087] Condition B1: All the trajectory scenes involved in the target trajectory nodes in each of the two adjacent target trajectory node sets have a second scene association relationship; in condition B1, the second scene association relationship refers to the scene transition relationship in which the scene transition represents that the user has a work gap and can plan the data synchronization mechanism, for example: the user transfers from a high-intensity work state scene A to a low-intensity work or idle state scene B;

[0088] or,

[0089] Condition B2: The absolute value of the difference in the number of target trajectory nodes in each of the two adjacent target trajectory node sets does not exceed the absolute value threshold; in condition B2, assuming that the target trajectory node set A contains 5 nodes and the set B contains 8 nodes, the absolute value of the difference in the number between them is |5-8|=3; the absolute value threshold can be 5; this condition reflects the relative stability of the user's behavior over a period of time. If the difference in the number of nodes between the two adjacent target trajectory node sets does not exceed the threshold, it means that the user's behavior trajectory fluctuates less in time and the scene switching is relatively stable; this is very important for the planning of the data synchronization mechanism, because if the user's scene switching is too drastic (such as the difference in the number of nodes is too large), it may mean that the activity pattern has changed significantly, which may cause the data synchronization mechanism to fail or become unstable; on the contrary, smaller fluctuations indicate that the user's activities remain stable over a period of time, and the data synchronization mechanism can be planned more easily.

[0090] The embodiment of the present invention introduces an interactive trajectory to determine whether to enter the mechanism planning opportunity, thereby improving the efficiency and accuracy of timing determination; under the constraints of a first set of set constraints, a target trajectory node set that can be used as a timing entry determination is screened from the interactive trajectory, without the need to perform a full analysis of the interactive trajectory, thereby achieving targeted analysis of the interactive trajectory, reducing the analysis resources of the system, and improving the efficiency of timing determination; under the constraints of a second set of set constraints, whether to enter the mechanism planning opportunity is quickly determined according to each target trajectory node set, thereby improving the accuracy of timing entry determination and improving the applicability of the system.

[0091] In one embodiment, S22, assisting a user in planning a data synchronization mechanism includes:

[0092] S2201, generating a visualization model based on a multimodal modeling basis; wherein the multimodal modeling basis at least includes: target data and data synchronization history;

[0093] In S2201, the data synchronization history is the historical record of data synchronization between the local cache and the server; the visualization model is a three-dimensional model for visually displaying the basis of multimodal modeling;

[0094] S2202: when the user requests assistance for viewing the visualization model, multiple analysis intentions are determined based on the viewing history of the user viewing the visualization model;

[0095] In S2202, when the user views the visualization model, the visualization model can be pushed to a device such as a smart terminal used by the user; when the user views the visualization model, a viewing history is generated, which at least includes: the type of content viewed, the location of the content viewed, the viewing time, etc.; when the user views the visualization model, the user will analyze how to plan the data synchronization mechanism, so the user's analysis intention can be determined based on the analysis intention, which represents how the user wants to analyze the visualization model;

[0096] S2203, determining a plurality of first data source region sets from the visualization model; wherein the data of each data source region in the same first data source region set is related to one analysis intention;

[0097] In S2203, a large amount of display data is distributed on the visualization model, and the area where the display data is located is the data source area. The data is related to the analysis intent, which means that the data is required to be used when performing the analysis of the analysis intent, etc.;

[0098] S2204, extracting a plurality of first model slices from the visualization model; wherein the same first model slice includes all data source regions in a first data source region set;

[0099] In S2204, the model slice refers to a local model cut from the visualization model;

[0100] S2205, allowing the user to view each first model slice;

[0101] In S2205, when the user views each first model slice, he will view the first model slice that meets his different analysis intentions in sequence and get assistance;

[0102] S2206. Whenever a first model slice actively overlaps with another first model slice and the degree of overlap exceeds an overlap threshold, or a first model slice passively overlaps with another first model slice, feature extraction is performed on at least two overlapping first model slices to obtain a feature set; wherein active overlap refers to an update of the first data source region set and thus the first model slice as the analysis intent is updated, resulting in an overlap with other first model slices in the visualization model; passive overlap refers to an overlap of the first model slice with other first model slices due to user operation;

[0103] In S2206, the overlap threshold may be 10%; whenever a first model slice actively overlaps with other first model slices and the overlap exceeds the overlap threshold, or a first model slice passively overlaps with other first model slices, it indicates that the user analysis of how to plan the data synchronization mechanism has made further progress, and the user needs to be assisted again, and the features extracted from the feature set include at least: the data source area in the overlapping area, the data source areas of the two model slices, the overlap retention time, the overlap growth time, etc.;

[0104] S2207, generating a data source search rule based on the feature set; wherein the data source search rule is a rule for searching a data source area where data related to each feature in the feature set is located;

[0105] In S2207, for example, in the feature set, if the overlapping area is located in a specific geographic area or data block, the search rule will point to these specific areas; for another example, if the overlap is maintained or grows for a long time, the search rule may involve data within a specific time period, which may need to be synchronized or processed in advance; for another example, if the data in the overlapping area comes from area A, and slices A and B come from different data sources, then it is necessary to design rules based on the information in the feature set to retrieve the data in area A;

[0106] S2208, searching for a plurality of second data source area sets from the visualization model based on the data source search rule;

[0107] S2209, extracting a plurality of second model slices from the visualization model; wherein the same second model slice includes all data source regions in a second data source region set;

[0108] S2210, allowing the user to view each second model slice;

[0109] S2211. When the duration of non-overlapping between the first model slices exceeds a duration threshold, attempt to receive a planned data synchronization mechanism input by a user; if the attempt fails, generate a mechanism planning suggestion based on the data of all data source areas in the first model slice and the second model slice based on the knowledge base of each analysis intention;

[0110] In S2211, the duration threshold may be 10 minutes; when the duration of the first model slices not overlapping each other exceeds the duration threshold, it indicates that the user can basically complete the planning of the data synchronization mechanism, and attempts are made to receive the planned data synchronization mechanism input by the user; the knowledge base has mechanism planning suggestions corresponding to different data under the analysis intent, and the knowledge base may store a large amount of expert experience related to the data synchronization mechanism, etc.;

[0111] S2212, for users to view mechanism planning suggestions;

[0112] S2213. Receive the planned data synchronization mechanism input by the user based on the mechanism planning suggestion.

[0113] In the embodiment of the present invention, the use of multimodal modeling basis can provide users with a comprehensive analysis basis, thereby helping them to formulate more accurate data synchronization strategies; the visualization model presents data as three-dimensional graphics, which can help users understand data and its relationships more intuitively, thereby improving the efficiency and accuracy of the planning process. By displaying the first model slice and the second model slice, users can view data areas under different analysis intentions, helping users to gradually analyze and determine the most suitable data synchronization plan; based on the user's viewing history and analysis intentions, the system can provide personalized assistance in real time, allowing users to make decisions more efficiently; when active or passive overlap occurs between model slices, the system will automatically extract features and generate data source search rules based on overlapping areas, time and other information, making the entire data synchronization planning process more intelligent and able to dynamically respond to user needs and adjust strategies.

[0114] The embodiment of the present invention provides a data synchronization and cache management system based on an offline priority architecture, such as Figure 2 As shown, including:

[0115] The cache module 1 is used to intercept network requests and cache target data locally when the device is offline; wherein the target data includes at least: static resources, dynamic data and user data operations;

[0116] Synchronization module 2, used to automatically synchronize the locally cached target data with the server when the device restores the network connection;

[0117] Solution module 3 is used to detect and resolve conflicts in the data synchronization process based on the version control mechanism;

[0118] Checking module 4, used for periodically checking the validity of the target data in the local cache based on the cache management mechanism after the data synchronization is completed;

[0119] The optimization module 5 is used to optimize the target data based on the update or expiration strategy and the validity check result.

[0120] The version control mechanism includes:

[0121] Detect version conflicts that occur during data synchronization;

[0122] Based on the resolution strategy corresponding to the conflict type of the version conflict, the version conflict is resolved accordingly.

[0123] The cache management mechanism includes: based on multiple validity check strategies, checking the validity of the target data in the local cache at every preset time interval.

[0124] The update or expiration strategy includes: when the validity check result reflects that the target data needs to be updated, updating the target data;

[0125] When the validity check result reflects that the target data needs to be removed, the target data is removed.

[0126] An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored. A processor executes the computer program to implement any of the above methods.

[0127] An embodiment of the present invention provides an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement any one of the methods described above.

[0128] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A data synchronization and cache management method based on an offline priority architecture, characterized in that: include: When the device is offline, intercept network requests and cache target data locally; wherein the target data includes at least: static resources, dynamic data, and user data operations; When the device restores the network connection, it automatically synchronizes the locally cached target data with the server. Based on the version control mechanism, conflict detection and resolution are performed on the data synchronization process; After data synchronization is completed, the validity of the target data in the local cache is regularly checked based on the cache management mechanism; Based on the update or expiration strategy, the target data is optimized according to the validity check results.

2. The data synchronization and cache management method based on offline priority architecture according to claim 1, characterized in that: The version control mechanism includes: Detect version conflicts that occur during data synchronization; Based on the resolution strategy corresponding to the conflict type of the version conflict, the version conflict is resolved accordingly.

3. The data synchronization and cache management method based on offline priority architecture according to claim 1, characterized in that: The cache management mechanism includes: Based on multiple validity check strategies, the validity of the locally cached target data is checked at preset time intervals.

4. The data synchronization and cache management method based on offline priority architecture according to claim 1, characterized in that: The update or expiration policy includes: When the validity check result reflects that the target data needs to be updated, the target data is updated; When the validity check result reflects that the target data needs to be removed, the target data is removed.

5. A data synchronization and cache management system based on an offline priority architecture, characterized in that: include: A cache module, used to intercept network requests and cache target data locally when the device is offline; wherein the target data includes at least: static resources, dynamic data, and user data operations; The synchronization module is used to automatically synchronize the locally cached target data with the server when the device restores the network connection; The resolution module is used to detect and resolve conflicts in the data synchronization process based on the version control mechanism; A checking module is used to periodically check the validity of the target data in the local cache based on the cache management mechanism after data synchronization is completed; The optimization module is used to optimize the target data based on the update or expiration strategy and the validity check result.

6. The data synchronization and cache management system based on offline priority architecture as claimed in claim 5, characterized in that: The version control mechanism includes: Detect version conflicts that occur during data synchronization; Based on the resolution strategy corresponding to the conflict type of the version conflict, the version conflict is resolved accordingly.

7. The data synchronization and cache management system based on offline priority architecture as claimed in claim 5, characterized in that: The cache management mechanism includes: Based on multiple validity check strategies, the validity of the locally cached target data is checked at preset time intervals.

8. The data synchronization and cache management system based on offline priority architecture as claimed in claim 5, characterized in that: The update or expiration policy includes: When the validity check result reflects that the target data needs to be updated, the target data is updated; When the validity check result reflects that the target data needs to be removed, the target data is removed.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the processor executes the computer program to implement the method according to any one of claims 1 to 4.

10. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method according to any one of claims 1 to 4.

Images