Data updating display method and system

Abstract

The invention provides a data updating display method and system. The method comprises the following steps: splitting pre-acquired data into a plurality of independent resource packages; setting an auxiliary identifier for each independent resource packet based on the data updating time of each independent resource packet; registering the independent resource packets as a plurality of signal lamp positions based on the auxiliary identifiers; obtaining a task virtual lamp, an application virtual lamp and a non-aggregation lamp based on a preset service requirement and the plurality of signal lamp positions; polling the task virtual lamp and the non-aggregated lamp, and integrating data of each independent resource packet into a to-be-updated data packet, so as to update the to-be-updated data packet; and polling the application virtual lamp to display the to-be-updated data packet. The problem that in the prior art, due to the fact that task coupling is high, updating can be carried out after all data are ready, and data updating reliability is poor is solved. According to the method, dynamic updating of task-decoupled data is realized to display the data, and the reliability of data updating and displaying is improved.

Description

Technical Field

[0001] This invention relates to the field of data integration and updating technology, and in particular to a data updating and display method and system. Background Technology

[0002] In the field of asynchronous data updates and displays across multiple systems, especially in scenarios involving updates to TA (Transfer Agent System) data, the clearing times of each TA system vary and are uncertain due to the influence of channel files. This necessitates triggering ETL tasks multiple times to update and display the data. Therefore, ensuring the reliability of data updates and displays, such as data integrity and timeliness, has become a major challenge in the field.

[0003] Currently, existing technologies use a batch processing method based on ETL event triggering mechanism to update data. That is, an ETL task is triggered once the database import of a TA is completed, or a scheduled task is set up based on expert experience to wait for all data to arrive before running the batch. However, although existing technologies can meet business requirements, the high task coupling of traditional methods leads to repeated execution of ETL tasks, making it difficult to guarantee data integrity. Furthermore, the need to wait for all data to be ready before updating and displaying results in poor real-time data updates, which in turn leads to poor reliability of data updates and displays. Summary of the Invention

[0004] To address the aforementioned issues, this invention proposes a data update and display method and system that enables dynamic data updates to display data with task decoupling, thereby improving the reliability of data update and display.

[0005] To achieve the above objectives, embodiments of the present invention provide a data update and display method, comprising: splitting pre-acquired data into several independent resource packages; setting auxiliary identifiers for each independent resource package based on the data update time of each independent resource package; registering each independent resource package as several semaphore positions based on the auxiliary identifiers; obtaining task virtual lights, application virtual lights, and non-aggregated lights based on preset business requirements and several semaphore positions; polling the task virtual lights and non-aggregated lights and integrating the data of each independent resource package into a data package to be updated, so as to update the data package to be updated; and polling the application virtual lights to display the data package to be updated.

[0006] This invention proposes a data update and display method. The method splits pre-acquired data into independent resource packages, allowing each package to be updated independently. An auxiliary identifier is set to register several semaphore positions. Then, the virtual semaphore aggregation logic is dynamically adjusted according to preset business requirements, and a hierarchical triggering mechanism is constructed. Finally, task virtual semaphores and non-aggregated semaphores are polled to generate data packets to be updated, and these data packets are updated. Application virtual semaphores are polled to display the data packets to be updated. Thus, this invention uses semaphore-driven methods instead of tightly coupled events, eliminating the dependence of task triggering on the entire dataset, achieving decoupled dynamic data updates for data display, and improving the reliability of data update and display.

[0007] Furthermore, the pre-acquired data is split into several independent resource packages, including: obtaining several data types based on the pre-acquired data; setting a unique identifier for each data type; integrating data types with the same unique identifier into the same resource package to obtain several initial resource packages; and setting timestamps for several resource packages to obtain several independent resource packages.

[0008] In the above scheme, data is divided into types and assigned unique identifiers, so that data with the same identifier are aggregated into independent resource packages. Then, a timestamp is set for each resource package to mark the update time. By the independence of resource packages and timestamp monitoring, the strong coupling of traditional full data bundled processing is broken. When the timestamp of some resource package data is updated, subsequent processes can be triggered independently without waiting for all data to arrive. Thus, by removing the dependence of task triggering on full data, the dynamic data update of task decoupling is achieved to display data, thereby improving the reliability of data update display.

[0009] Furthermore, based on the data update time of each independent resource package, auxiliary identifiers are set for each independent resource package, including: obtaining the data update time of each independent resource package based on the timestamp of each independent resource package; if the data update time changes, registering the corresponding independent resource package to the preset resource registry; and setting a first auxiliary identifier, a second auxiliary identifier, or a third auxiliary identifier for each independent resource package based on the preset resource registry.

[0010] In the above scheme, the timestamp of the independent resource package is monitored to obtain the update time change and three types of auxiliary identifiers are dynamically set. The three types of auxiliary identifiers are used as differentiated identifiers to control the update permissions of the independent resource package, decouple the strong binding between task triggering and data physical state, and allow the data to be updated independently at a single point according to the auxiliary identifier. This achieves task decoupling and dynamic data update to display the data, and improves the reliability of data update display.

[0011] Furthermore, each independent resource package is registered as a number of semaphore positions based on auxiliary identifiers, including: if the data update time changes, the independent resource package is set to a ready state and the auxiliary identifier of each independent resource package is identified; if the auxiliary identifier of the independent resource package is a first auxiliary identifier, registration is not performed and the auxiliary identifier is waited for to be updated; if the auxiliary identifier of the independent resource package is a second auxiliary identifier, several semaphore positions are obtained through registration; if the auxiliary identifier of the independent resource package is a third auxiliary identifier, the data update time is waited for to meet the preset update requirements, and several semaphore positions are obtained through registration.

[0012] In the above scheme, differentiated auxiliary identifiers are used to control the registration of traffic light positions. The first auxiliary identifier isolates abnormal data to avoid triggering invalid updates. The second auxiliary identifier allows independent participation in downstream processes, eliminating the dependency on waiting for full data. The third auxiliary identifier controls the registration of traffic light positions only after the update requirements are met to ensure the integrity of critical data. Thus, traffic light-driven operation replaces strong event coupling, eliminates the dependency of task triggering on full data, realizes dynamic data updates for data display through task decoupling, and improves the reliability of data update display.

[0013] Furthermore, based on preset business requirements and several signal light positions, task virtual lights, application virtual lights, and non-aggregated lights are obtained, including: obtaining a first aggregation condition and a second aggregation condition based on preset business requirements; selecting several signal light positions that meet the first aggregation condition and aggregating them to obtain task virtual lights; selecting several signal light positions that meet the second aggregation condition and aggregating them to obtain application virtual lights; selecting several signal light positions that do not meet the first aggregation condition and the second aggregation condition to obtain non-aggregated lights, wherein the task virtual lights and application virtual lights are independent of each other, and several signal light positions can simultaneously meet the first aggregation condition and / or the second aggregation condition.

[0014] In the above solution, the preset business requirements are broken down into two aggregation conditions. The first aggregation condition aggregates signal light positions to build task virtual lights, which independently control task triggering. The second aggregation condition aggregates signal light positions to build application virtual lights, which independently control data updates. Non-aggregated lights are built for unaggregated signal light positions, and non-aggregated lights monitor uncovered data. Three parallel channels are built to decouple task triggering from full data, realizing dynamic data updates for data display by decoupling tasks, thereby improving the reliability of data update display.

[0015] Furthermore, polling the task virtual lights and non-aggregated lights and integrating the data from each independent resource package into a data packet to be updated, includes: polling the timestamps of the task virtual lights and non-aggregated lights based on a preset time interval to obtain the task virtual light value and non-aggregated light value; if the task virtual light value meets the preset update requirements but the non-aggregated light value does not meet the preset update requirements, then skipping the non-aggregated lights and integrating the data from the independent resource package corresponding to the task virtual light into a data packet to be updated, thus updating the data packet to be updated; if both the task virtual light value and non-aggregated light value meet the preset update requirements, then integrating the data from the independent resource package corresponding to the task virtual light and the independent resource package corresponding to the non-aggregated light into a data packet to be updated, thus updating the data packet to be updated.

[0016] In the above scheme, the timestamps of the task virtual lights and non-aggregated lights are polled periodically. The polled task virtual light values ​​and non-aggregated light values ​​are combined with preset update requirements to integrate the data of independent resource packages into a data package to be updated. The data package to be updated is then updated. The task virtual lights ensure timely updates of core data, while the non-aggregated lights serve as an asynchronous supplementary channel. State-driven batch updates replace full-volume bundled processing, achieving dynamic data updates for task decoupling to display data and improving the reliability of data update display.

[0017] Furthermore, if both the task virtual light value and the non-aggregated light value meet the preset update requirements, then the data of the independent resource package corresponding to the task virtual light and the data of the independent resource package corresponding to the non-aggregated light are integrated into a data packet to be updated, and the data packet to be updated is updated. This includes: if both the task virtual light value and the non-aggregated light value meet the preset update requirements, then a task triggering instruction is generated according to a preset data integrity threshold; based on the task triggering instruction, the independent resource package corresponding to the task virtual light and the independent resource package corresponding to the non-aggregated light are extracted and the integration task is executed, and the data packet to be updated is output, so as to update the data packet to be updated.

[0018] In the above scheme, when both the virtual light value and the non-aggregated light value of the task meet the preset update requirements, a task triggering instruction is generated based on the preset data integrity threshold. The independent resource package data corresponding to the virtual light and the non-aggregated light of the task is integrated as the data package to be updated. The data package to be updated is updated. The amount of aggregated data of the virtual light is used as the judgment criterion to decouple the task triggering and the physical state of the data, so as to realize the dynamic data update of the task decoupling to display the data and improve the reliability of the data update display.

[0019] Furthermore, polling the application virtual lights to display the data packets to be updated includes: polling the application virtual lights to obtain the application virtual light values; if the application virtual light values ​​meet the preset update requirements, updating the timestamp to obtain the updated timestamp; and polling based on the updated timestamp to display the data packets to be updated.

[0020] In the above scheme, the application virtual lights are polled to obtain the application virtual light values, and the timestamps are updated in combination with preset update requirements. After the timestamps are updated, they are displayed in the data packets to be updated. The independent polling mechanism of the application virtual lights decouples data updates from data processing, realizes dynamic data updates for data display with task decoupling, and improves the reliability of data update display.

[0021] Furthermore, based on the updated timestamp, the data packet to be updated is displayed, including: if the applied virtual light value meets the preset display requirements under the updated timestamp, the data packet to be updated is displayed; if the applied virtual light value does not meet the preset display requirements under the updated timestamp, a task trigger instruction is generated to integrate the independent resource package corresponding to the task virtual light and / or the independent resource package corresponding to the non-aggregated light, until the applied virtual light value meets the preset display requirements, and then the data packet to be updated is displayed.

[0022] In the above scheme, the virtual light status is used to determine whether data should be displayed. If the virtual light status meets the preset display requirements, the data packet to be updated is displayed directly. If the virtual light status does not meet the preset display requirements, the data is integrated and displayed in an asynchronous manner. The virtual light status is used as the basis for update decision, decoupling the task trigger from the full data, realizing dynamic data update to display the data, and improving the reliability of data update display.

[0023] This invention also provides a data update and display system, including: a resource package acquisition module, an auxiliary identifier setting module, a light position registration module, a light position aggregation module, a data update module, and a data display module; the resource package acquisition module is used to split the pre-acquired data into several independent resource packages; the auxiliary identifier setting module is used to set auxiliary identifiers for each independent resource package based on the data update time of each independent resource package; the light position registration module is used to register each independent resource package as several signal light positions based on the auxiliary identifiers; the light position aggregation module is used to obtain task virtual lights, application virtual lights, and non-aggregated lights based on preset business requirements and several signal light positions; the data update module is used to poll the task virtual lights and non-aggregated lights and integrate the data of each independent resource package into a data package to be updated, so as to update the data package to be updated; the data display module is used to poll the application virtual lights and display the data package to be updated.

[0024] This invention proposes a data update and display system. A resource package acquisition module splits the pre-acquired data into independent resource packages, allowing each package to be updated independently. An auxiliary identifier setting module sets auxiliary identifiers to register several signal lights through a light position registration module. A light position aggregation module dynamically adjusts the virtual light position aggregation logic and constructs a hierarchical triggering mechanism based on preset business requirements. Finally, an update data package acquisition module polls task virtual lights and non-aggregated lights to generate update data packages and updates them. A data update module polls application virtual lights to display the update data packages. Thus, this invention uses signal light-driven mechanisms instead of tightly coupled events, eliminating the dependence of task triggering on the entire dataset, achieving decoupled dynamic data updates for data display, and improving the reliability of data update and display. Attached Figure Description

[0025] Figure 1 This is a flowchart illustrating the steps of a data update and display method according to a certain embodiment of the present invention.

[0026] Figure 2 A schematic diagram of the lamp position registration process for a data update and display method provided in a certain embodiment of the present invention;

[0027] Figure 3 A schematic diagram illustrating a lamp position registration example of a data update and display method provided in a certain embodiment of the present invention;

[0028] Figure 4 This is a schematic diagram of the module structure of a data update and display system provided in a certain embodiment of the present invention. Detailed Implementation

[0029] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0030] TA (Transfer Agent System) is a business system widely used in the fund and financial industry. It is a system that can be used to handle data management such as fund share registration, clearing, settlement and account management. Usually, due to the influence of channel documents, the clearing time of each TA system is different. For example, ETF funds are generally cleared at 6:00 on day T, ordinary funds are generally cleared at 10:00 on day T, and LOF funds are generally cleared at 16:00 on day T. Therefore, it is impossible to import all TA data at once, which requires triggering ETL tasks multiple times to update the data or waiting for all TA data to be cleared before updating the data. Therefore, the existing technology has the problem of poor data update reliability.

[0031] To address the aforementioned issues, this invention proposes a data update and display method. Taking a Data Acquisition and Translation (TA) system as an example, the technical solution of this application is explained. For scenarios involving asynchronous updates of multiple TA data, the update time of each TA data is defined as a semaphore to store the data update time. Then, multiple semaphore positions are virtualized into logical semaphore positions. The value of this virtual "semaphore" can be the minimum value of the aggregated actual semaphore positions according to business needs. Finally, the synchronization of ETL task data is controlled through the virtual logical semaphore positions, completing the data update. It is worth noting that in this invention, the preset update requirement is expressed as: whether to update to the latest date T. This will not be elaborated further below. The specific implementation process of a data update and display method and system is as follows:

[0032] Example 1

[0033] See Figure 1 , Figure 1 This is a flowchart illustrating the steps of a data update and display method according to a certain embodiment of the present invention. Figure 1 As shown in the figure, this embodiment of the invention proposes a data update and display method, including steps 101 to 106, each step of which is as follows:

[0034] Step 101: Divide the data to be acquired into several independent resource packages;

[0035] Step 102: Based on the data update time of each independent resource package, set auxiliary identifiers for each independent resource package;

[0036] Step 103: Register each independent resource package as a number of traffic light positions based on the auxiliary identifier;

[0037] Step 104: Based on preset business requirements and several signal light positions, obtain task virtual lights, application virtual lights and non-aggregated lights;

[0038] Step 105: Poll the task virtual lights and non-aggregated lights and integrate the data of each independent resource package into a data package to be updated, so as to update the data package to be updated;

[0039] Step 106: Poll the application's virtual lights to display the data packets to be updated.

[0040] One possible implementation involves treating each TA system as a resource set and acquiring data from each resource set. This data includes transaction data, position data, and account data. Several independent resource packages are constructed based on different data types. After the upstream TA data is imported, the data update time of each independent resource package is determined. If the data update time changes, the resource package is registered in the resource registry. The format of the resource registry can be found in Table 1. Taking the TA1 system as an example, the specific implementation is as follows:

[0041] Table 1 Resource Registry

[0042]

[0043]

[0044] As shown in Table 1, the TA1 system includes three data types. Therefore, the three TA1 datasets are set as three independent resource packages. Auxiliary identifiers are set according to the data update time of each independent resource package. Based on the auxiliary identifiers, the TA1 system is registered as a semaphore position for TA+ resources, such as TA1_FUNDSHARE and TA1_CONFIRM. The corresponding semaphore positions are registered for other TA systems in the same way. Then, according to the preset business requirements, such as whether the arrival time of TA data is close, the principle of TA data volume, and the timeliness requirements of data, each semaphore position is aggregated into task virtual lights and application virtual lights according to the preset business requirements. The semaphore positions that are not aggregated are recorded as non-aggregated lights. The task aggregated lights and non-aggregated lights are polled periodically to determine whether the corresponding TA semaphore light is on. The data of each independent resource package corresponding to each semaphore position is integrated into the data package to be updated. The data package to be updated is updated. Then, the application virtual lights are polled to display the data package to be updated. Generally speaking, this triggers the front end to update the latest date so that the data to be updated is displayed on the front end.

[0045] This invention proposes a data update and display method. The method splits pre-acquired data into independent resource packages, allowing each package to be updated independently. An auxiliary identifier is set to register several semaphore positions. Then, the virtual semaphore aggregation logic is dynamically adjusted according to preset business requirements, and a hierarchical triggering mechanism is constructed. Finally, task virtual semaphores and non-aggregated semaphores are polled to generate data packets to be updated, and these data packets are updated. Application virtual semaphores are polled to display the data packets to be updated. Thus, this invention uses semaphore-driven methods instead of tightly coupled events, eliminating the dependence of task triggering on the entire dataset, achieving decoupled dynamic data updates for data display, and improving the reliability of data update and display.

[0046] A preferred approach involves splitting the pre-acquired data into several independent resource packages, including: obtaining several data types based on the pre-acquired data; assigning a unique identifier to each data type; integrating data types with the same unique identifier into the same resource package to obtain several initial resource packages; and assigning timestamps to the several resource packages to obtain several independent resource packages.

[0047] One preferred implementation involves treating each TA system as a resource set, acquiring data from each resource set, including various types such as transaction data, position data, and account data, and assigning a unique identifier to each type. For example, TA1_FUNDSHARE serves as the unique identifier for position data in the TA1 system, and this unique identifier also matches the semaphore position marker. Data types with the same unique identifier are integrated into the same resource package as an initial resource package, and a timestamp is set for each initial resource package, thereby constructing several independent resource packages. In this embodiment, the timestamp is used to record the data update time, and the timestamp is continuously recorded and changed according to the data update time.

[0048] In the above scheme, data is divided into types and assigned unique identifiers, so that data with the same identifier are aggregated into independent resource packages. Then, a timestamp is set for each resource package to mark the update time. By the independence of resource packages and timestamp monitoring, the strong coupling of traditional full data bundled processing is broken. When the timestamp of some resource package data is updated, subsequent processes can be triggered independently without waiting for all data to arrive. Thus, by removing the dependence of task triggering on full data, the dynamic data update of task decoupling is achieved to display data, thereby improving the reliability of data update display.

[0049] A preferred embodiment involves setting auxiliary identifiers for each independent resource package based on its data update time, including: obtaining the data update time of each independent resource package based on its timestamp; registering the corresponding independent resource package in a preset resource registry if the data update time changes; and setting a first auxiliary identifier, a second auxiliary identifier, or a third auxiliary identifier for each independent resource package based on the preset resource registry.

[0050] One preferred implementation method is described in [reference]. Figure 2 , Figure 2 This is a schematic diagram of a lamp position registration process for a data update and display method according to a certain embodiment of the present invention; as shown below. Figure 2 As shown, after the upstream TA data import is completed, the data update time of each independent resource package is determined. When the data update time of an independent resource package changes, the independent resource package, its business date, and update time are registered in the resource registry and the registration signal light is awaited. The resource registry is shown in Table 1. If the business date of the independent resource package is less than the system date, it means that the data has timed out and the upstream task has been delayed, which requires an alarm.

[0051] In the above scheme, the timestamp of the independent resource package is monitored to obtain the update time change and three types of auxiliary identifiers are dynamically set. The three types of auxiliary identifiers are used as differentiated identifiers to control the update permissions of the independent resource package, decouple the strong binding between task triggering and data physical state, and allow the data to be updated independently at a single point according to the auxiliary identifier. This achieves task decoupling and dynamic data update to display the data, and improves the reliability of data update display.

[0052] A preferred embodiment involves registering each independent resource package as a number of semaphore positions based on auxiliary identifiers, including: if the data update time changes, setting the independent resource package to a ready state and identifying the auxiliary identifier of each independent resource package; if the auxiliary identifier of the independent resource package is a first auxiliary identifier, then not registering and waiting for the auxiliary identifier to be updated; if the auxiliary identifier of the independent resource package is a second auxiliary identifier, then registering to obtain a number of semaphore positions; if the auxiliary identifier of the independent resource package is a third auxiliary identifier, then waiting for the data update time to meet a preset update requirement, and then registering to obtain a number of semaphore positions.

[0053] One preferred implementation scheme is shown in Table 1. The TA1 system includes three data types; therefore, the three TA1 datasets are set as three independent resource packages. Taking a TA data update on a certain day as an example, auxiliary identifiers are set according to the data update time of each independent resource package. The control logic for the auxiliary identifiers is shown in Table 2, as follows:

[0054] Table 2 Auxiliary Identification Control Logic Table

[0055]

[0056] As shown in Table 2, when the auxiliary identifier is identified as "0", it indicates that the data may be abnormal and needs to wait for the auxiliary identifier to be updated. Registration is not allowed. When the auxiliary identifier is identified as "1", it indicates that the data does not need to wait for other data to arrive and can be registered and opened to downstream users. When the auxiliary identifier is identified as "2", it is necessary to wait for all TA data to arrive before registration. For example, if the auxiliary identifier of the TA1 system is identified as "2", it is necessary to wait for all data of the TA1 system to arrive before registration. Ten minutes later, all data of the TA1 system arrives, and the independent resource package with the auxiliary identifier "2" is allowed to register a semaphore position and register it as a semaphore position of the TA+ resource. The registered semaphore positions are recorded as TA1_FUNDSHARE and TA1_CONFIRM, and the TA1_ALL position is registered simultaneously. TA1_ALL means that all data of the TA for the day has arrived. The corresponding semaphore positions are registered in the same way for other TA systems. The semaphore position indicates that the TA data has reached the latest "business date" T.

[0057] In the above scheme, differentiated auxiliary identifiers are used to control the registration of traffic light positions. The first auxiliary identifier isolates abnormal data to avoid triggering invalid updates. The second auxiliary identifier allows independent participation in downstream processes, eliminating the dependency on waiting for full data. The third auxiliary identifier controls the registration of traffic light positions only after the update requirements are met to ensure the integrity of critical data. Thus, traffic light-driven operation replaces strong event coupling, eliminates the dependency of task triggering on full data, realizes dynamic data updates for data display through task decoupling, and improves the reliability of data update display.

[0058] A preferred embodiment, based on preset business requirements and a number of signal light positions, obtains task virtual lights, application virtual lights, and non-aggregated lights, including: obtaining a first aggregation condition and a second aggregation condition based on preset business requirements; selecting a number of signal light positions that satisfy the first aggregation condition and aggregating them to obtain task virtual lights; selecting a number of signal light positions that satisfy the second aggregation condition and aggregating them to obtain application virtual lights; selecting a number of signal light positions that do not satisfy the first aggregation condition and the second aggregation condition to obtain non-aggregated lights, wherein the task virtual lights and application virtual lights are independent of each other, and the number of signal light positions can simultaneously satisfy the first aggregation condition and / or the second aggregation condition.

[0059] One preferred implementation method is described in [reference]. Figure 3 , Figure 3 This is a schematic diagram illustrating a lamp position registration example of a data update and display method provided in a certain embodiment of the present invention; as shown below. Figure 3As shown, the signal light positions of each TA system obtained from steps 101 to 103 are recorded in the TA light position table. Based on preset business requirements, a first aggregation condition and a second aggregation condition are obtained. In one example, the first aggregation condition is: whether the TA data arrival time is close and the TA data volume principle; the second aggregation condition is: data timeliness requirements. Based on the first aggregation condition, ETL virtual lights (equivalent to task virtual lights) are set. The ETL virtual lights control the ETL task import library to avoid repeated execution of ETL tasks. Based on the second aggregation condition, application virtual lights are set to update the data to the front end to avoid incomplete TA data. Furthermore, the task virtual lights and application virtual lights are independent of each other, thus allowing independent control of ETL task triggering based on the task virtual lights and independent control of data updates based on the application virtual lights. In one example of this embodiment, the TA light position table is shown in Table 3, as detailed below:

[0060] Table 3 TA Lamp Position Table

[0061]

[0062] Table 3 shows 10 TA+ signal light positions, including TA1, TA2, TA3, TA4, and TA5. Based on the first aggregation condition, the TA signal light positions TA1_FUNDSHARE to TA3_CONFIRM are aggregated into an ETL virtual light, denoted as TA_4ETL. The list of virtual light positions is recorded through configuration, for example, TA1_FUNDSHARE, TA1_CONFIRM, TA2_FUNDSHARE, TA2_CONFIRM, TA3_FUNDSHARE, and TA3_CONFIRM. Then, based on the second aggregation condition, the TA signal light positions TA1_FUNDSHARE to TA4_CONFIRM are aggregated into... The virtual lights used for aggregation are denoted as TA_4RPT. The list of virtual light positions is recorded through configuration, such as TA1_FUNDSHARE, TA1_CONFIRM, TA2_FUNDSHARE, TA2_CONFIRM, TA3_FUNDSHARE, TA3_CONFIRM, TA4_FUNDSHARE, and TA4_CONFIRM. It is worth mentioning that TA signal lights can simultaneously meet the first aggregation condition and the second aggregation condition, or only meet either the first aggregation condition or the second aggregation condition. The virtual signal lights do not need to cover all TA signal lights, but only include those required by the business. Only the specific TA light position list recorded needs to be configured.

[0063] In the above solution, the preset business requirements are broken down into two aggregation conditions. The first aggregation condition aggregates signal light positions to build task virtual lights, which independently control task triggering. The second aggregation condition aggregates signal light positions to build application virtual lights, which independently control data updates. Non-aggregated lights are built for unaggregated signal light positions, and non-aggregated lights monitor uncovered data. Three parallel channels are built to decouple task triggering from full data, realizing dynamic data updates for data display by decoupling tasks, thereby improving the reliability of data update display.

[0064] A preferred embodiment involves polling task virtual lights and non-aggregated lights and integrating the data from each independent resource package into a data packet to be updated, for updating the data packet to be updated. This includes: polling the timestamps of task virtual lights and non-aggregated lights based on a preset time interval to obtain task virtual light values ​​and non-aggregated light values; if the task virtual light value meets a preset update requirement but the non-aggregated light value does not, then skip the non-aggregated lights and integrate the data from the independent resource package corresponding to the task virtual light into a data packet to be updated, for updating the data packet to be updated; if both the task virtual light value and the non-aggregated light value meet the preset update requirement, then integrate the data from the independent resource package corresponding to the task virtual light and the independent resource package corresponding to the non-aggregated light into a data packet to be updated, for updating the data packet to be updated. Furthermore, if both the task virtual light value and the non-aggregated light value meet the preset update requirements, then the data of the independent resource package corresponding to the task virtual light and the data of the independent resource package corresponding to the non-aggregated light are integrated into a data packet to be updated, and the data packet to be updated is updated. This includes: if both the task virtual light value and the non-aggregated light value meet the preset update requirements, then a task triggering instruction is generated according to a preset data integrity threshold; based on the task triggering instruction, the independent resource package corresponding to the task virtual light and the independent resource package corresponding to the non-aggregated light are extracted and the integration task is executed, and the data packet to be updated is output, so as to update the data packet to be updated.

[0065] One preferred implementation involves periodically (equivalent to a preset time interval, which can be set according to actual needs) polling the task virtual light TA_4ETL and the non-aggregated lights TA4_FUNDSHARE, TA4_CONFIRM, TA5_FUNDSHARE, and TA5_CONFIRM to obtain the task virtual light values ​​and the non-aggregated light values. Based on the task virtual light values ​​and the non-aggregated light values, it is determined whether the corresponding TA signal light is lit. If the light is lit, it indicates that the corresponding TA signal light position has been updated to the latest T-day. Specifically, the lit task virtual light TA_4ETL indicates that all signal light positions included in the task virtual light have been updated to the latest T-day. Then, a data integrity threshold is preset according to business needs, for example, set to 0.9, representing 90% of the TA signals. Once all data is available, the data can be updated and displayed. Since different traffic lights contain different amounts of TA data, the TA data represented by the virtual TA_4ETL light typically exceeds a preset integrity threshold. When the data integrity reaches the threshold, a task trigger command is generated, initiating an ETL task to integrate and obtain the data package to be updated. Specifically, the ETL task extracts data from independent resource packages, cleans, processes, and integrates the data, such as standardizing and unifying data formats. The processed data is then integrated into the data package to be updated, and the data is updated using this data package. After updating the data package, the system awaits subsequent data display. Typically, the data is updated on the backend based on the data package to be updated, and subsequently displayed on the frontend through user queries.

[0066] In the above scheme, the timestamps of the task virtual lights and non-aggregated lights are polled periodically. The polled task virtual light values ​​and non-aggregated light values ​​are combined with preset update requirements to integrate the data of independent resource packages, resulting in a data package to be updated. The task virtual lights ensure timely updates of core data, while the non-aggregated lights serve as asynchronous supplementary channels. State-driven batch updates replace full-volume bundling processing, achieving decoupled dynamic data updates for data display and improving the reliability of data update display. In addition, when both the task virtual light values ​​and non-aggregated light values ​​meet the preset update requirements, a task trigger command is generated based on a preset data integrity threshold. This command integrates the independent resource package data corresponding to the task virtual lights and non-aggregated lights to obtain the data package to be updated. The aggregated data volume of the virtual lights is used as a criterion to decouple task triggering from the physical state of the data, achieving decoupled dynamic data updates for data display and improving the reliability of data update display.

[0067] In a preferred embodiment, polling the application virtual lights to display the data packet to be updated includes: polling the application virtual lights to obtain the application virtual light values; if the application virtual light values ​​meet preset update requirements, updating the timestamp to obtain the updated timestamp; and displaying the data packet to be updated based on the updated timestamp. Further, displaying the data packet to be updated based on the updated timestamp includes: if the application virtual light values ​​at the updated timestamp meet preset display requirements, then displaying the data packet to be updated; if the application virtual light values ​​at the updated timestamp do not meet the preset display requirements, then generating a task trigger instruction to integrate the independent resource packets corresponding to the task virtual lights and / or the independent resource packets corresponding to the non-aggregated lights, until the application virtual light values ​​meet the preset display requirements, and then displaying the data packet to be updated.

[0068] In one preferred implementation, after the TA data corresponding to the application virtual light TA_4RPT set according to the second aggregation condition is complete (equivalent to the preset display requirements), the front-end page is updated to the latest date T, and the data to be updated is updated to the front-end for display. Typically, the amount of TA data represented by the set application virtual light TA_4RPT exceeds the preset integrity threshold. Therefore, when the latest date has not been updated, i.e., the timestamp has not been updated, polling the TA_4RPT light value can trigger the update of the latest date on the front-end, thus obtaining the updated timestamp. Based on the updated timestamp, the TA_4RPT light value is periodically polled to determine whether TA_4RPT is lit. If the light is lit, it means that all corresponding TA signal lights have been updated to the latest date T. Then, the front-end page is updated to the latest date T, and the update... The data is displayed after all the lights TA1 to TA4 in Table 3 are in place, triggering the latest date and displaying the front-end data. When the latest date T is updated according to the TA_4RPT light value, the TA data corresponding to that date may not be complete. Therefore, it is necessary to continue polling the non-aggregated lights to complete the TA data. Thus, the process of polling the virtual light TA_4ETL and non-aggregated lights needs to be repeated. At the same time, the light values ​​corresponding to the non-aggregated lights TA4_FUNDSHARE, TA4_CONFIRM, TA5_FUNDSHARE and TA5_CONFIRM are checked. After the light is lit, the ETL task is triggered to add the data of the independent resource package corresponding to this part of the signal light. This process does not update the latest date displayed on the front end, but the completeness of the data is continuously improved.

[0069] In the above scheme, the application virtual lights are polled to obtain their values. The timestamps are then updated based on preset update requirements. The updated timestamps are then displayed in the data packets to be updated. The independent polling mechanism for the application virtual lights decouples data updates from data processing, achieving dynamic data updates for data display with task decoupling, thus improving the reliability of data update display. Furthermore, the virtual light status determines whether data should be displayed. If the application virtual light statuses all meet the preset display requirements, the data packets to be updated are displayed directly. If the application virtual light statuses do not meet the preset display requirements, the data is integrated asynchronously before being displayed. Using the virtual light status as the update decision basis decouples task triggering from the full dataset, achieving dynamic data updates for data display with task decoupling, and improving the reliability of data update display.

[0070] Example 2

[0071] See Figure 4 , Figure 4 This is a schematic diagram of the module structure of a data update and display system provided in a certain embodiment of the present invention. Figure 4 As shown in the figure, this embodiment of the invention also provides a data update and display system, including: a resource package acquisition module 201, an auxiliary identifier setting module 202, a light position registration module 203, a light position aggregation module 204, a data update module 205, and a data display module 206; the resource package acquisition module 201 is used to split the pre-acquired data into several independent resource packages; the auxiliary identifier setting module 202 is used to set auxiliary identifiers for each independent resource package based on the data update time of each independent resource package; the light position registration module 203 is used to register each independent resource package as several signal light positions based on the auxiliary identifiers; the light position aggregation module 204 is used to obtain task virtual lights, application virtual lights, and non-aggregated lights based on preset business requirements and several signal light positions; the data update module 205 is used to poll the task virtual lights and non-aggregated lights and integrate the data of each independent resource package into a data package to be updated, so as to update the data package to be updated; the data display module 206 is used to poll the application virtual lights and display the data package to be updated.

[0072] One possible implementation involves treating each TA system as a resource set. Data is acquired from each resource set, including transaction data, position data, and account data. Several independent resource packages are constructed based on different data types. After the upstream TA data is imported, the data update time of each independent resource package is determined. If the data update time changes, the resource package is registered in the resource registry. The format of the resource registry can be found in Table 1. As shown in Table 1, the TA1 system includes three data types. Therefore, the three TA1 datasets are set as three independent resource packages. An auxiliary identifier is set based on the data update time of each independent package. Based on the auxiliary identifier, the TA1 system is registered as a semaphore position for TA+ resources. For example, the registered semaphore position is denoted as T. A1_FUNDSHARE and TA1_CONFIRM; similarly, register corresponding semaphore positions for other TA systems. Then, based on preset business requirements, such as whether the arrival time of TA data is close, TA data volume principles, and data timeliness requirements, aggregate each semaphore position into task virtual lights and application virtual lights according to preset business requirements. The semaphore positions that are not aggregated are recorded as non-aggregated lights. The task aggregated lights and non-aggregated lights are polled periodically to determine whether the corresponding TA semaphore light is on. The data of each independent resource package corresponding to each semaphore position is integrated into the data package to be updated, and the data package to be updated is updated. Then, the application virtual lights are polled to display the data package to be updated. Generally speaking, this triggers the front end to update the latest date so that the data to be updated is displayed on the front end.

[0073] This invention proposes a data update and display system. A resource package acquisition module splits the pre-acquired data into independent resource packages, allowing each package to be updated independently. An auxiliary identifier setting module sets auxiliary identifiers to register several signal lights through a light position registration module. A light position aggregation module dynamically adjusts the virtual light position aggregation logic and constructs a hierarchical triggering mechanism based on preset business requirements. Finally, an update data package acquisition module polls task virtual lights and non-aggregated lights to generate update data packages and updates them. A data update module polls application virtual lights to display the update data packages. Thus, this invention uses signal light-driven mechanisms instead of tightly coupled events, eliminating the dependence of task triggering on the entire dataset, achieving decoupled dynamic data updates for data display, and improving the reliability of data update and display.

[0074] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

[0075] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. Furthermore, the described specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.

[0076] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

Claims

1. A method for updating and displaying data, characterized in that, include: The data to be acquired is split into several independent resource packages; Based on the data update time of each independent resource package, an auxiliary identifier is set for each independent resource package; Based on the auxiliary identifier, each of the independent resource packages is registered as a number of traffic light positions; Based on preset business requirements and several signal light positions, task virtual lights, application virtual lights, and non-aggregated lights are obtained; The task virtual lights and non-aggregated lights are polled and the data of each of the independent resource packages are integrated into a data package to be updated, so as to update the data package to be updated; The application's virtual lights are polled to display the data packets to be updated.

2. The data update and display method as described in claim 1, characterized in that, The process of splitting the pre-acquired data into several independent resource packages includes: Based on the pre-acquired data, several data types are obtained; Set a unique identifier for each of the data types described; Data types with the same unique identifier are integrated into the same resource package to obtain several initial resource packages; A timestamp is set on several of the aforementioned resource packages to obtain several independent resource packages.

3. The data update and display method as described in claim 2, characterized in that, The step of setting auxiliary identifiers for each independent resource package based on the data update time of each independent resource package includes: Based on the timestamp of each independent resource package, obtain the data update time of each independent resource package; If the data update time changes, the corresponding independent resource package will be registered in the preset resource registry. Based on the preset resource registry, a first auxiliary identifier, a second auxiliary identifier, or a third auxiliary identifier is set for each of the independent resource packages.

4. The data update and display method as described in claim 3, characterized in that, Based on the auxiliary identifier, each of the independent resource packages is registered as a number of traffic light positions, including: If the data update time changes, the independent resource package is set to a ready state and the auxiliary identifier of each independent resource package is identified; If the auxiliary identifier of the independent resource package is the first auxiliary identifier, then registration is not performed and the auxiliary identifier is waited for to be updated; If the auxiliary identifier of the independent resource package is the second auxiliary identifier, then several traffic light positions are obtained through registration; If the auxiliary identifier of the independent resource package is the third auxiliary identifier, then wait for the data update time to meet the preset update requirements, and obtain several signal light positions through registration.

5. The data update and display method as described in claim 4, characterized in that, The process of obtaining task virtual lights, application virtual lights, and non-aggregated lights based on preset business requirements and several signal light positions includes: Based on the preset business requirements, obtain the first aggregation condition and the second aggregation condition; Select several signal light positions that meet the first aggregation condition, and aggregate them to obtain a task virtual light; Select several signal light positions that meet the second aggregation condition, and aggregate them to obtain an application virtual light; Select a number of signal light positions that do not meet the first aggregation condition and the second aggregation condition to obtain non-aggregated lights, wherein the task virtual light and the application virtual light are independent of each other, and the number of signal light positions can simultaneously meet the first aggregation condition and / or the second aggregation condition.

6. The data update and display method as described in claim 5, characterized in that, Polling the task virtual lights and non-aggregated lights and integrating the data of each of the independent resource packages into a data package to be updated, and updating the data package to be updated, includes: Based on a preset time interval, the timestamps of the task virtual lights and the non-aggregated lights are polled to obtain the task virtual light values ​​and non-aggregated light values. If the value of the task virtual light meets the preset update requirement and the value of the non-aggregated light does not meet the preset update requirement, then the non-aggregated light is skipped and the data of the independent resource package corresponding to the task virtual light is integrated into the data package to be updated, so as to update the data package to be updated. If both the task virtual light value and the non-aggregated light value meet the preset update requirements, then the data of the independent resource package corresponding to the task virtual light and the data of the independent resource package corresponding to the non-aggregated light are integrated into a data package to be updated, so as to update the data package to be updated.

7. The data update and display method as described in claim 6, characterized in that, If both the task virtual light value and the non-aggregated light value meet the preset update requirements, then the data of the independent resource package corresponding to the task virtual light and the data of the independent resource package corresponding to the non-aggregated light are integrated into a data package to be updated, and the data package to be updated is updated, including: If both the virtual light value and the non-aggregated light value of the task meet the preset update requirements, then a task triggering instruction is generated according to the preset data integrity threshold. Based on the task triggering instruction, the independent resource package corresponding to the task virtual light and the independent resource package corresponding to the non-aggregated light are extracted and the integration task is executed to output the data package to be updated, so as to update the data package to be updated.

8. The data update and display method as described in claim 7, characterized in that, Polling the application's virtual lights to display the data packets to be updated includes: Poll the application's virtual lights to obtain the application's virtual light values; If the application virtual light value meets the preset update requirements, then the timestamp is updated to obtain the updated timestamp; Based on the updated timestamp, the data packet to be updated is displayed.

9. The data update and display method as described in claim 8, characterized in that, Based on the updated timestamp, the data packet to be updated is displayed, including: If the application virtual light value meets the preset display requirements under the updated timestamp, then the data packet to be updated will be displayed. If the application virtual light value does not meet the preset display requirements under the updated timestamp, the task trigger instruction is generated to integrate the independent resource package corresponding to the task virtual light and / or the independent resource package corresponding to the non-aggregated light until the application virtual light value meets the preset display requirements, and the data package to be updated is then displayed.

10. A data update and display system, characterized in that, include: The system includes a resource package acquisition module, an auxiliary identification setting module, a light position registration module, a light position aggregation module, a data update module, and a data display module. The resource package acquisition module is used to split the pre-acquired data into several independent resource packages; The auxiliary identifier setting module is used to set an auxiliary identifier for each independent resource package based on the data update time of each independent resource package; The light position registration module is used to register each of the independent resource packages as several signal light positions based on the auxiliary identifier; The light position aggregation module is used to obtain task virtual lights, application virtual lights and non-aggregated lights based on preset business requirements and several signal light positions. The data update module is used to poll the task virtual lights and non-aggregated lights and integrate the data of each independent resource package into a data package to be updated, so as to update the data package to be updated; The data display module is used to poll the application virtual lights to display the data packets to be updated.

Images