Multi-page data consistency guarantee method and device and electronic equipment

Abstract

The invention provides a multi-page data consistency guarantee method and device and electronic equipment, and the method comprises the steps: constructing a unified jump management system for a credit system; based on the business page characteristics of the credit system, a differential data transmission mechanism is set, and data transmission is carried out; performing instance-level isolation on the cache of the credit system through a composite cache key and read-write logic optimization; carrying out full-scene test and verification on the credit system; the full-scene test comprises a jump logic accuracy test, a data transmission integrity test, a cache isolation validity test, a multi-instance concurrent stability test and an abnormal scene fault tolerance test. By means of the method and device, it is ensured that concurrent operation of multiple service modules is supported, meanwhile, the consistency and integrity of data are effectively maintained, and the problem that in the prior art, data consistency and accuracy are poor is solved.

Description

Technical Field

[0001] This invention relates to the field of credit data management technology, and in particular to a method, apparatus and electronic device for ensuring data consistency across multiple pages. Background Technology

[0002] As credit systems become increasingly complex, a single business module often encompasses hundreds or even thousands of pages. The need for multiple concurrent instances of core detail pages, such as credit details, credit usage details, credit limit details, billing details, customer details, guarantee information details, contract details, partner details, and parameter details, has become a common and urgent technical requirement. In practical applications, users often need to operate multiple business detail pages simultaneously to perform complex tasks such as data comparison, cross-validation, or batch processing. However, existing technologies still face many core challenges in handling such high concurrency and multi-instance scenarios. The navigation management is chaotic: the navigation logic for different pages is implemented independently by each development team, lacking a unified standard. Some pages forcibly close historical instances, making multi-window comparison unsupported; some pages create instances without limit, leading to routing conflicts and memory overflows.

[0003] 1. Non-standard data transmission: When small data pages use route parameters for transmission without compression, the data is easily truncated due to exceeding the URL length limit. The big data page directly passes object references, causing multiple page instances to share the same data, and editing operations to interfere with each other. The inconsistent data formats, with some pages using JSON and others using custom formats, increase the difficulty of data validation.

[0004] 2. Defects in the caching mechanism: The cache key design is simple (such as using only the page name), and multiple instances share the same cache space, leading to data overwriting. The caching and data transfer mechanisms are disconnected, and the cache is not refreshed synchronously after data is updated, resulting in the display of "dirty data". Lacking fault tolerance mechanisms, it is impossible to recover data from the cache when routing parameters are lost or data transmission fails.

[0005] 3. Insufficient test coverage: Traditional testing only verifies single-page functionality and does not simulate concurrent scenarios with multiple instances, leading to problems such as data disorder and page crashes after deployment.

[0006] There is currently no effective solution to the problem of poor data consistency and accuracy in existing related technologies. Summary of the Invention

[0007] This invention provides a method, apparatus, and electronic device for ensuring multi-page data consistency, in order to solve the defects of poor data consistency and accuracy in existing related technologies.

[0008] In a first aspect, the present invention provides a method for ensuring data consistency across multiple pages, comprising: For the credit system, build a unified redirect management system; Based on the characteristics of the business pages of the credit system, a differentiated data transmission mechanism is set up and data is transmitted. By optimizing the composite cache key and read / write logic, instance-level isolation is achieved for the cache of the credit system. The credit system was subjected to full-scenario testing and verification; the full-scenario testing included jump logic accuracy testing, data transmission integrity testing, cache isolation effectiveness testing, multi-instance concurrency stability testing, and fault tolerance testing for abnormal scenarios.

[0009] According to the present invention, a multi-page data consistency assurance method is provided, which, for a credit system, constructs a unified redirection management system, including: Logical modeling of the data transmission details for all pages in the credit system's business is performed, core features are extracted, and a common jump function with dynamic judgment capability is developed based on the core features; Perform in-depth analysis of the routing stack to obtain a list of currently opened page instances, and implement differentiated redirection strategies based on the core features mentioned above; Establish a redirection logic access standard, and uniformly replace the redirection entry point from all business list pages to the details page in the credit system with the public redirection function; Maintain the page feature parameters of the credit system to centrally manage the redirection logic.

[0010] According to the multi-page data consistency guarantee method provided by the present invention, the core features include complex business page identifier, multi-instance support attribute, and data volume threshold.

[0011] According to a multi-page data consistency guarantee method provided by the present invention, the redirection strategy is as follows: For a single-instance page, the credit system automatically redirects the page after triggering a close command for a page instance of the same type. For pages that support multiple instances, the credit system directly creates new page instances while retaining historical page instances.

[0012] According to a multi-page data consistency assurance method provided by the present invention, based on the business page characteristics of the credit system, a differentiated data transmission mechanism is set up and data transmission is performed, including: For pages with data volume less than a preset threshold, data is transmitted using route parameter serialization. For pages with data volume reaching a preset threshold, data is transmitted via an independent data channel.

[0013] According to a multi-page data consistency assurance method provided by the present invention, instance-level isolation of the cache of the credit system is achieved through composite cache keys and read / write logic optimization, including: Design a rule for generating a composite cache key; the composite cache key consists of a unique page identifier, a data instance ID, a transmission method identifier, and a timestamp. Establish a cache write priority mechanism; Optimize cache reading and fault tolerance logic.

[0014] According to the multi-page data consistency guarantee method provided by the present invention, the establishment of a cache write priority mechanism includes: The page whose routing parameters are passed is synchronously written to the cache as a backup after the data is parsed; Pages transmitted via independent channels are immediately written to the cache as the primary storage after data is received, and the cache validity period is dynamically configured according to the page type.

[0015] According to the multi-page data consistency guarantee method provided by the present invention, the optimization of cache reading and fault tolerance logic includes: When the details page is initialized, data is first obtained through the corresponding transmission method. If the data acquisition fails, the cache reading process is triggered. The cache partition is located according to the composite cache key. If the cached data exists and has not expired, it is loaded; otherwise, the pre-set data recovery mechanism is executed.

[0016] Secondly, the present invention also provides a multi-page data consistency assurance device, comprising: The module is used to build a unified redirect management system for the credit system; The data transmission module is used to set up a differentiated data transmission mechanism based on the characteristics of the business pages of the credit system, and to transmit data. An isolation module is used to perform instance-level isolation of the cache of the credit system through composite cache keys and read / write logic optimization; The testing module is used to perform full-scenario testing and verification of the credit system; the full-scenario testing includes jump logic accuracy testing, data transmission integrity testing, cache isolation effectiveness testing, multi-instance concurrency stability testing, and abnormal scenario fault tolerance testing.

[0017] Thirdly, the present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the multi-page data consistency guarantee method as described in the first aspect above.

[0018] Fourthly, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the multi-page data consistency guarantee method as described in the first aspect above.

[0019] Fifthly, the present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the multi-page data consistency guarantee method as described in the first aspect above.

[0020] Compared with the prior art, the present invention has the following beneficial effects: This invention provides a multi-page data consistency assurance method that employs advanced computer software multi-page application data management technology. By constructing a novel standardized jump management framework, a differentiated data transmission mechanism, a refined cache isolation strategy, and a comprehensive scenario testing and verification process, it ensures effective maintenance of data consistency and integrity while supporting the concurrent operation of multiple business modules. Addressing common issues in traditional systems such as routing conflicts, data overwriting, and state disorder, this method successfully resolves potential risks in multi-page operations by dynamically adapting to page characteristics and optimizing the collaborative working mechanism of data transmission and caching. It demonstrates exceptional adaptability and stability, particularly in large-scale credit systems containing more than 1000 pages. This method not only improves the processing capacity and response speed of credit systems but also significantly enhances the user experience, ensuring system stability and data security under high-concurrency business operations. Its application effects are particularly prominent in the banking and credit field, providing precise data synchronization and state management for each page in complex business processes. This greatly improves the intelligent management level of credit business systems, laying a solid technical foundation for the realization of future large-scale digital financial services and solving the problems of poor data consistency and accuracy in existing related technologies. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0022] Figure 1 This invention provides a method for ensuring data consistency across multiple pages. Figure 2 This is a structural block diagram of the multi-page data consistency guarantee device provided by the present invention; Figure 3 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0024] This invention provides a method for ensuring data consistency across multiple pages. Figure 1 This invention provides a method for ensuring data consistency across multiple pages, such as... Figure 1 As shown, the method includes the following steps: Step S101: For the credit system, construct a unified redirection management system; Step S102: Based on the characteristics of the business pages of the credit system, set up a differentiated data transmission mechanism and transmit the data. Step S103: Instance-level isolation of the credit system's cache is achieved through composite cache keys and read / write logic optimization. Step S104: Conduct full-scenario testing and verification of the credit system; the full-scenario testing includes testing the accuracy of redirection logic, the integrity of data transmission, the effectiveness of cache isolation, the stability of multi-instance concurrency, and the fault tolerance of abnormal scenarios.

[0025] This method first constructs a unified redirection management system for the credit system. Then, it designs a differentiated data transmission mechanism based on the characteristics of the credit system's business pages and transmits data according to this mechanism. Next, it designs a refined cache isolation and collaboration strategy, using composite cache keys and optimized read / write logic to achieve instance-level isolation of the credit system's cache. Finally, it conducts full-scenario testing and verification of the credit system from multiple levels. The above process employs advanced computer software multi-page application data management technology. By constructing a new standardized redirection management framework, a differentiated data transmission mechanism, a refined cache isolation strategy, and a comprehensive scenario testing and verification process, it ensures effective maintenance of data consistency and integrity while supporting the concurrent operation of multiple business modules. Addressing common issues in traditional systems such as routing conflicts, data overwriting, and state disorder, this method successfully resolves potential risks in multi-page operations by dynamically adapting to page characteristics and optimizing the data transmission and cache collaboration mechanism. It demonstrates excellent adaptability and stability, particularly in large-scale credit systems containing more than 1000 pages. This method not only improves the processing capacity and response speed of the credit system but also significantly enhances the user experience, ensuring system stability and data security under high-concurrency business operations. Its application effect is particularly prominent in the field of banking credit. It can provide accurate data synchronization and status management for every page in complex business processes, greatly improve the intelligent management level of credit business systems, lay a solid technical foundation for the realization of large-scale digital financial services in the future, and solve the problems of poor data consistency and accuracy in existing related technologies.

[0026] The following credit system (containing more than 100 pages, of which more than 370 are detail pages) serves as an example to illustrate the implementation process of this method.

[0027] In some embodiments, step S101 involves constructing a unified redirection management system for the credit system, including: logically modeling the data transmission details of redirections for all pages in the credit system's business, extracting core features, and developing a common redirection function with dynamic judgment capabilities based on the core features; performing deep analysis of the routing stack to obtain a list of currently opened page instances, and implementing differentiated redirection strategies in conjunction with the core features; establishing a redirection logic access specification to uniformly replace the redirection entry points from all business list pages in the credit system to the details page with a common redirection function; and maintaining the page feature parameters of the credit system for centralized control of the redirection logic.

[0028] Specifically, core features include complex business page identifiers, multi-instance support attributes, and data volume thresholds. In addition, core page feature parameters also include data update frequency and dependencies between related pages. The common redirect function dynamically adjusts redirect latency and loading priority based on these feature parameters.

[0029] The redirection strategy is as follows: For single-instance pages, the credit system automatically redirects the page after triggering a command to close a page instance of the same type; for pages that support multiple instances, the credit system directly creates a new page instance while retaining historical page instances to ensure the integrity and continuity of data and operational status.

[0030] In this embodiment, logical modeling of the data transmission for jump details across all pages in the credit system is performed. Complex business page identifiers, multi-instance support attributes, and data volume thresholds are extracted as core features. Based on these features, a common jump function with dynamic judgment capabilities is developed. An advanced tab status monitoring module is integrated into the common jump function of the credit system. Through deep analysis of the routing stack, the list of currently opened page instances is accurately obtained. Based on this, and combined with the multi-instance support attribute of the page, a differentiated jump strategy is implemented. A jump logic access standard is established, uniformly replacing the jump entry points from all business list pages to detail pages in the system with the aforementioned common jump function. Page feature parameters are maintained through the router-index.js configuration file, achieving centralized control of the jump logic.

[0031] For example, firstly, the page features of the credit system are modeled and parameters are configured. Features are extracted from all pages in the credit system (e.g., 500 pages), and a configuration table containing the following parameters is established: Page ID: such as "orderDetail" or "goodsDetail"; MultiInstance Support Attribute: A boolean value indicating whether multiple instances are allowed to be opened simultaneously; Data size threshold (DataSizeThreshold): such as 2000 bytes, used to distinguish data transmission methods; Data update frequency (UpdateFreq): high frequency / low frequency, affecting cache validity period; RelatedPages: Such as order details being associated with payment details, used for redirection dependency validation.

[0032] The configuration table is stored in JSON format, supports dynamic updates, and takes effect without restarting the system.

[0033] Extract features from the details page and create a configuration file named pageConfig.json, as shown in the example below: { "orderDetail": { "multiInstance": true, "dataSizeThreshold": 2000, "updateFreq": "high", "relatedPages": ["paymentDetail", "refundDetail"] }, "userSetting": { "multiInstance": false, "dataSizeThreshold": 500, "updateFreq": "low", "relatedPages": [] } } Next, we designed the common jump function. We developed the core function `unifiedJump(pageID, data, callback)` to implement the following functionality: Input parameters: page ID, data to be passed, and callback function. Feature matching: Read page feature parameters from the configuration table based on pageID; Instance Management: Call the getOpenedInstances(pageID) method to retrieve a list of currently open page instances of the same type; If MultiInstance is false, call closeInstances(instanceList) to close all historical instances; If MultiInstance is true, check if the number of instances exceeds the limit (e.g., 10). If it does, prompt the user to close some instances. Redirect execution: Generate the target URL based on the page routing rules, execute the redirect in combination with the data transmission method, and return the redirect result (success / failure reason) through the callback.

[0034] The unifiedJump function is implemented based on the Vue framework. The specific code is as follows: async function unifiedJump(pageID, data, callback) { const config = await fetchPageConfig(pageID); / / Read configuration const instances = getOpenedInstances(pageID); / / Get opened instances / / Handling single-instance pages if (!config.multiInstance&&instances.length>0) { await closeInstances(instances); / / Close historical instances } / / Handling data transfer let url, token; if (JSON.stringify(data).length <config.dataSizeThreshold) { / / Small data: Passing routing parameters const compressed = compressData(data); / / LZ77 compression const encoded = btoa(compressed); / / Base64 encoding url = ` / ${pageID}?data=${encoded}&instanceId=${uuidv4()}`; } else { / / Big Data: DataBus Delivery token = DataBus.post(pageID, data); / / Store in the data queue url = ` / ${pageID}?token=${token}&instanceId=${uuidv4()}`; } / / Execute jump router.push(url).then(() =>callback({ success: true})) .catch(err =>callback({ success: false, error: err})); } Finally, the redirect entry points were standardized: an access specification was established requiring all redirect logic on the credit system details page to call the unifiedJump function; an automated detection tool was developed to scan for locations in the code that directly call routing APIs (such as window.location.href, router.push) and prompt for conversion to a unified redirect; and the historical pages of the credit system were modified in batches, with compatibility verified through canary releases.

[0035] In some embodiments, step S102 involves setting a differentiated data transmission mechanism based on the characteristics of the business pages of the credit system and transmitting the data, including: for pages with data volume less than a preset threshold, transmitting data using a routing parameter serialization method; and for pages with data volume reaching the preset threshold, transmitting data using an independent data channel method.

[0036] In this embodiment, the routing parameter serialization and transmission method is as follows: the list page converts the target data into a JSON string using a data compression algorithm, encodes it using Base64, and then appends it to the Uniform Resource Locator (URL); the details page extracts the parameters through the routing parsing module, decodes and restores the data, and binds the data operation to a unique identifier of the current page instance. The data compression algorithm uses a variant of the LZ77 algorithm to compress the JSON string before encoding, achieving a compression rate of no less than 30%, and the total length of the routing URL is controlled within 2048 bytes.

[0037] For example, firstly, data preprocessing is performed. The list page calls the `compressData(data)` function to compress the data using a variant of the LZ77 algorithm. The compressed data size must be less than 1500 bytes (548 bytes reserved for other URL parameters). The compressed data is converted to a string using `JSON.stringify()` and then Base64 encoded to avoid URL parsing errors caused by special characters. Next, parameters are concatenated to generate a URL in the format ` / pageID?data=encodedStr&instanceId=xxx`, where `instanceId` is the unique identifier (UUID) of the current page instance. Finally, the details page is parsed. The `encodedStr` parameter is extracted from the URL using the `parseRouteParams()` function; the data is then Base64 decoded, decompressed, and restored using `JSON.parse()`; the data is bound to the `instanceId` to ensure that subsequent edit and save operations only apply to the data of the current instance.

[0038] The independent data transmission method is as follows: a dedicated data queue is created for each page through a global state manager. List pages write JSON-formatted data into the queue and generate a unique data token; detail pages retrieve the corresponding data from the queue using the token, while simultaneously triggering a queue cleanup mechanism to prevent memory leaks. The global state manager uses a publish-subscribe pattern, and a maximum length threshold is set for the data queue. When the queue length exceeds the threshold, the oldest created and unreferenced data entries are automatically cleaned up.

[0039] For example, first, design a global state manager: The DataBus module is implemented based on the publish-subscribe pattern, creating a dedicated data queue [pageID] for each page ID; Queue element format: { token: UUID, data: JSON, timestamp: Number, referenceCount: 0}; Data transmission (list page): Call the DataBus.post(pageID, data) method to generate a unique token; Store the JSON formatted data (object references are prohibited) into the corresponding queue, and initialize referenceCount to 1; Data reception (details page): The redirect URL includes a token parameter: / pageID?token=xxx&instanceId=xxx; The details page calls DataBus.get(pageID, token) to retrieve data, and increments referenceCount by 1. After the data is used up (e.g., the page is closed), call DataBus.release(pageID, token) and decrement referenceCount by 1; Memory reclamation: DataBus periodically (e.g., every 30 seconds) scans the queue and cleans up data with referenceCount=0 and a lifespan of more than 5 minutes; When the queue length exceeds a threshold (e.g., 100 entries), the oldest unreferenced data will be automatically deleted.

[0040] The code for receiving and caching data on the details page is as follows (taking the order details page as an example): async mounted() { const { data, token, instanceId} = this.$route.query; let pageData; / / Receive data if (data) { / / Route parameter parsing const decoded = atob(data); pageData = decompressData(decoded); / / Decompress } else if (token) { / / DataBus Retrieval pageData = await DataBus.get('orderDetail', token); } / / Generate composite cache key const cacheKey = generateCacheKey({ pageID: 'orderDetail', dataID: pageData.orderId, mode: data ? 'url' : 'bus', userID: this.$store.state.user.id, timestamp: Date.now() }); / / Write to cache cache.set(cacheKey, { data: pageData, instanceId, version: 1, updateTime: Date.now() }, 300000); / / Valid for 5 minutes (for frequently updated pages) } In some embodiments, step S103, through composite cache keys and read / write logic optimization, performs instance-level isolation of the credit system's cache, including: designing composite cache key generation rules; the composite cache key consists of a unique page identifier, a data instance ID, a transmission method identifier, and a timestamp, and generates a unique string using the SHA-256 hash algorithm, allocating an independent cache partition for each page instance; establishing a cache write priority mechanism; and optimizing cache read and fault tolerance logic. Furthermore, the composite cache key also includes a user session identifier to ensure cache isolation in multi-user scenarios, and the timestamp is accurate to the millisecond level to distinguish different versions of the same data instance.

[0041] In this embodiment, the cache write priority mechanism includes: pages transmitted via routing parameters are synchronously written to the cache as backups after data parsing is completed; pages transmitted via independent channels are immediately written to the cache as primary storage after data reception, and the cache validity period is dynamically configured according to the page type.

[0042] Optimizing cache reading and fault tolerance logic includes: during detail page initialization, data is retrieved first via the corresponding transmission method. If retrieval fails, the cache reading process is triggered. The cache partition is located based on the composite cache key. If the cached data exists and has not expired, it is loaded; otherwise, a pre-defined data recovery mechanism is executed. The data recovery mechanism includes: sending a data retransmission request to the list page, calling the backend API to retrieve data again, and displaying local default data and prompting the user. These three mechanisms are triggered sequentially according to priority.

[0043] For example, a composite cache key design is as follows: The cache key is composed of: PageID + "|" + DataID + "|" + Mode + "|" + UserID + "|" + Timestamp; PageID: A unique identifier for the page; DataID: A unique identifier for a data instance (such as order ID or user ID); Mode: Passing method ("url" or "bus"); UserID: The identifier for the current user session, ensuring isolation between multiple users; Timestamp: Data generation timestamp (milliseconds), used to distinguish different versions of the same data; Key generation: The above string is converted into a 64-bit unique identifier using the SHA-256 hash algorithm to avoid excessively long key names.

[0044] The cache write strategy is as follows: For pages that pass route parameters: Triggering time: After the details page data is successfully parsed; Content to be written: Complete data object + instanceId + data status (unmodified / modified); Validity period: Based on the page's UpdateFreq configuration, set to 5 minutes for high-frequency page updates and 30 minutes for low-frequency updates; For pages delivered via independent channels: Triggering timing: Data is written immediately after successful reception and updated in real time after data modification; Content to be written: Complete data object + modification history + version number; Validity period: set to 2 hours, and supports manual refresh (e.g., when the user clicks the "Refresh Data" button).

[0045] The cache read and fault tolerance mechanism is as follows: Priority reading strategy: When the details page is initialized, data is first retrieved via route parameters or DataBus; if the retrieval is successful, the data version is compared with the cached version; if the cached version is newer, the user is prompted to load the latest data. Failure recovery process: When routing parameters are lost / decoding fails, or the token in DataBus is invalid, a cache read is triggered; getCacheByKey(generatedKey) is called to query the cache. If valid data exists, it is loaded, and the user is prompted "Data restored from cache"; if no valid data exists in the cache, execution proceeds according to priority: 1. Call requestResend(token) to request the list page to resend the data; 2. If step 1 fails, call the backend API fetchData(DataID) to retrieve it again; 3. If step 2 fails, display the local default template data and prompt the user "Data loading failed, please try again".

[0046] Based on the above embodiments, the effectiveness of the solution is ensured through multi-level testing, specifically including: 1. Jump logic test Single instance page test: Open the system configuration page 3 times consecutively to verify whether the first 2 pages close automatically; Multi-instance page test: Open 5 credit application detail pages to verify whether the URL and instanceId are unique and whether the pages are displayed independently; Boundary testing: Simulate the number of multiple instance pages opened exceeding the limit (e.g., 10) and verify whether the prompt mechanism is triggered.

[0047] 2. Data transmission test Small data page: Test the compression rate, encoding correctness, and parsing integrity of different data volumes (500 bytes, 1500 bytes, 2000 bytes); Big Data Page: Test the transmission time of 10KB and 50KB data to verify the memory usage and recycling efficiency of the DataBus queue; Anomaly testing: Simulate scenarios of URL parameter tampering and token expiration to verify whether the data verification mechanism is effective.

[0048] 3. Caching mechanism test Isolation test: Open two different data instances on the same page at the same time to verify whether the cache key is unique and whether the data overwrites each other; Consistency testing: After modifying page data, verify whether the cache is updated synchronously; close the page and reopen it to verify whether the latest cache is loaded. Fault tolerance test: After deleting the route parameters, refresh the page to verify whether the data can be recovered from the cache.

[0049] 4. Concurrency stability test Stress test: Use JMeter to simulate 100 users simultaneously opening 20 corporate credit details pages, performing editing and saving operations for 1 hour; Data consistency verification: Compare database records with the data displayed on each page to ensure there is no disorder or overwriting; Performance monitoring: Record CPU usage, memory usage, and response time during concurrency to ensure that system metrics are within thresholds.

[0050] When conducting multi-instance concurrent stability testing, stress testing tools are used to simulate scenarios where more than 100 similar page instances are opened, edited, and saved simultaneously, continuously monitoring data consistency and system response time.

[0051] For example, in a full-scenario test, 10 testers simultaneously opened 8 corporate credit details pages (approximately 5KB of data), modified different fields, and saved the results. Results verification: Database records are completely consistent with the data displayed on each page, with no data overwriting; data for each instance in the cache is stored independently, and key-value pairs are unique. Anomaly test: After manually deleting a route parameter on a page and refreshing, the system automatically loads data from the cache and displays "Data restored from cache", indicating that the function is normal and usable.

[0052] After three months of actual operation and verification, the application of this method to the credit system completely solved the problem of data disorder in multiple concurrent pages, reduced the user complaint rate by 100%, and reduced the maintenance cost of the credit system by 60%.

[0053] In summary, compared with existing technologies, this method has the following significant advantages: 1. Standardized jump management: Jump logic is centrally managed through common functions and configuration tables, supporting dynamic switching between single and multiple instances to adapt to different business scenarios.

[0054] 2. Highly efficient and secure data transmission: Small data pages solve the URL length limitation problem through compression encoding, improving data integrity by 99%. The big data page avoids object reference sharing through independent channels and a token mechanism, improving data isolation by 100%.

[0055] 3. Accurate and reliable cache isolation: Composite cache keys achieve instance-level isolation, optimized read and write strategies ensure data consistency, and the cache recovery success rate reaches 99.5% in abnormal scenarios.

[0056] 4. Significantly improved system stability: Tests show that the data disorder rate in multi-page concurrent scenarios has been reduced from 30% to 0, the system crash rate has been reduced by 99%, and user operation efficiency has been improved by 40%.

[0057] This method can be widely applied to complex systems containing a large number of detail pages, such as those in finance, enterprise resource planning (ERP), and e-commerce, and has strong practical value and promising prospects for promotion.

[0058] The present invention also provides a multi-page data consistency guarantee device. The multi-page data consistency guarantee device provided by the present invention will be described below. The multi-page data consistency guarantee device described below can be referred to in correspondence with the multi-page data consistency guarantee method described above. Figure 2 This is a structural block diagram of the multi-page data consistency assurance device provided by the present invention, as shown below. Figure 2 As shown, the device includes: Module 201 is used to build a unified redirect management system for the credit system; The data transmission module 202 is used to set up a differentiated data transmission mechanism based on the characteristics of the business pages of the credit system, and to transmit data. Isolation module 203 is used to perform instance-level isolation of the cache of the credit system through composite cache keys and read / write logic optimization; Test module 204 is used to perform full-scenario testing and verification of the credit system. Full-scenario testing includes jump logic accuracy testing, data transmission integrity testing, cache isolation effectiveness testing, multi-instance concurrency stability testing, and fault tolerance testing for abnormal scenarios.

[0059] When this device is in use, firstly, the construction module 201 builds a unified redirection management system for the credit system. Then, the transmission module 202 designs a differentiated data transmission mechanism based on the characteristics of the credit system's business pages and transmits data according to this mechanism. The isolation module 203 then designs a refined cache isolation and collaboration strategy, optimizing the cache through composite cache keys and read / write logic to achieve instance-level isolation of the credit system's cache. Finally, the testing module 204 conducts full-scenario testing and verification of the credit system from multiple levels. The above process employs advanced computer software multi-page application data management technology. By constructing a new standardized redirection management framework, a differentiated data transmission mechanism, a refined cache isolation strategy, and a comprehensive scenario testing and verification process, it ensures effective maintenance of data consistency and integrity while supporting the concurrent operation of multiple business modules. Addressing common issues in traditional systems such as routing conflicts, data overwriting, and state disorder, this device successfully resolves potential risks in multi-page operations by dynamically adapting to page characteristics and optimizing the data transmission and cache collaboration mechanism. It demonstrates excellent adaptability and stability, especially in large-scale credit systems containing more than 1000 pages. This device not only enhances the processing power and response speed of the credit system but also significantly improves the user experience, ensuring system stability and data security under high-concurrency business operations. Its application effect is particularly prominent in the banking and credit field, providing precise data synchronization and status management for every page in complex business processes. This greatly improves the intelligent management level of the credit business system, laying a solid technical foundation for the realization of large-scale digital financial services in the future, and solving the problems of poor data consistency and accuracy in existing related technologies.

[0060] Figure 3 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 3 As shown, the electronic device may include: a processor 301, a communication interface 302, a memory 303, and a communication bus 304. The processor 301, communication interface 302, and memory 303 communicate with each other via the communication bus 304. The processor 301 can invoke logical instructions in the memory 303 to execute a multi-page data consistency guarantee method, which includes: For the credit system, build a unified redirect management system; Based on the characteristics of the business pages of the credit system, a differentiated data transmission mechanism is set up and data is transmitted. By optimizing the composite cache key and read / write logic, instance-level isolation is achieved for the cache of the credit system. The credit system underwent full-scenario testing and verification. Full-scenario testing included testing the accuracy of redirection logic, the integrity of data transmission, the effectiveness of cache isolation, the stability of multi-instance concurrency, and the fault tolerance of abnormal scenarios.

[0061] Furthermore, the logical instructions in the aforementioned memory 303 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0062] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the multi-page data consistency guarantee method provided by the above methods, the method including: For the credit system, build a unified redirect management system; Based on the characteristics of the business pages of the credit system, a differentiated data transmission mechanism is set up and data is transmitted. By optimizing the composite cache key and read / write logic, instance-level isolation is achieved for the cache of the credit system. The credit system underwent full-scenario testing and verification. Full-scenario testing included testing the accuracy of redirection logic, the integrity of data transmission, the effectiveness of cache isolation, the stability of multi-instance concurrency, and the fault tolerance of abnormal scenarios.

[0063] In another aspect, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the multi-page data consistency guarantee method provided by the above methods, the method comprising: For the credit system, build a unified redirect management system; Based on the characteristics of the business pages of the credit system, a differentiated data transmission mechanism is set up and data is transmitted. By optimizing the composite cache key and read / write logic, instance-level isolation is achieved for the cache of the credit system. The credit system underwent full-scenario testing and verification. Full-scenario testing included testing the accuracy of redirection logic, the integrity of data transmission, the effectiveness of cache isolation, the stability of multi-instance concurrency, and the fault tolerance of abnormal scenarios.

[0064] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0065] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0066] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for ensuring data consistency across multiple pages, characterized in that, include: For the credit system, build a unified redirect management system; Based on the characteristics of the business pages of the credit system, a differentiated data transmission mechanism is set up and data is transmitted. By optimizing the composite cache key and read / write logic, instance-level isolation is achieved for the cache of the credit system. The credit system was tested and verified in all scenarios. The full-scenario testing includes jump logic accuracy testing, data transmission integrity testing, cache isolation effectiveness testing, multi-instance concurrency stability testing, and fault tolerance testing for abnormal scenarios.

2. The method for ensuring multi-page data consistency according to claim 1, characterized in that, For the credit system, a unified redirect management system will be built, including: Logical modeling of the data transmission details for all pages in the credit system's business is performed, core features are extracted, and a common jump function with dynamic judgment capability is developed based on the core features; Perform in-depth analysis of the routing stack to obtain a list of currently opened page instances, and implement differentiated redirection strategies based on the core features mentioned above; Establish a redirection logic access standard, and uniformly replace the redirection entry point from all business list pages to the details page in the credit system with the public redirection function; Maintain the page feature parameters of the credit system to centrally manage the redirection logic.

3. The method for ensuring multi-page data consistency according to claim 2, characterized in that, The core features include complex business page identifiers, multi-instance support attributes, and data volume thresholds.

4. The method for ensuring multi-page data consistency according to claim 2, characterized in that, The jump strategy is as follows: For a single-instance page, the credit system automatically redirects the page after triggering a close command for a page instance of the same type. For pages that support multiple instances, the credit system directly creates new page instances while retaining historical page instances.

5. The method for ensuring multi-page data consistency according to claim 1, characterized in that, Based on the characteristics of the business pages of the credit system, a differentiated data transmission mechanism is established and data transmission is performed, including: For pages with data volume less than a preset threshold, data is transmitted using route parameter serialization. For pages with data volume reaching a preset threshold, data is transmitted via an independent data channel.

6. The method for ensuring multi-page data consistency according to claim 1, characterized in that, By optimizing the composite cache key and read / write logic, instance-level isolation is achieved for the cache of the credit system, including: Design a rule for generating a composite cache key; the composite cache key consists of a unique page identifier, a data instance ID, a transmission method identifier, and a timestamp. Establish a cache write priority mechanism; Optimize cache reading and fault tolerance logic.

7. The method for ensuring multi-page data consistency according to claim 6, characterized in that, Establishing a cache write priority mechanism includes: The page whose routing parameters are passed is synchronously written to the cache as a backup after the data is parsed; Pages transmitted via independent channels are immediately written to the cache as the primary storage after data is received, and the cache validity period is dynamically configured according to the page type.

8. The method for ensuring multi-page data consistency according to claim 6, characterized in that, Optimization of cache read and fault tolerance logic includes: When the details page is initialized, data is first obtained through the corresponding transmission method. If the data acquisition fails, the cache reading process is triggered. The cache partition is located according to the composite cache key. If the cached data exists and has not expired, it is loaded; otherwise, the pre-set data recovery mechanism is executed.

9. A multi-page data consistency assurance device, characterized in that, include: The module is used to build a unified redirect management system for the credit system; The data transmission module is used to set up a differentiated data transmission mechanism based on the characteristics of the business pages of the credit system, and to transmit data. An isolation module is used to perform instance-level isolation of the cache of the credit system through composite cache keys and read / write logic optimization; The testing module is used to perform full-scenario testing and verification of the credit system; The full-scenario testing includes jump logic accuracy testing, data transmission integrity testing, cache isolation effectiveness testing, multi-instance concurrency stability testing, and fault tolerance testing for abnormal scenarios.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the multi-page data consistency guarantee method as described in any one of claims 1 to 8.

Images