Data updating method and device, equipment, storage medium and product
By introducing the concept of target rounds and a table partitioning management strategy, the update frequency is dynamically adjusted, solving the problems of chaotic data coverage and inflexible updates in knowledge base data updates, and achieving efficient and automated data updates.
Patent Information
- Application Number
- CN202511028704.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-24
- Publication Date
- 2025-11-18
AI Technical Summary
Existing technologies for updating knowledge base data suffer from problems such as chaotic data coverage, difficulty in tracking historical versions, and inflexible updates, resulting in low update efficiency.
By introducing the concept of target rounds, the update frequency is dynamically adjusted based on the data volume of the master data table and the target data table, seed tables and result tables are generated, and summary tables are merged to ensure data consistency and integrity. A table-splitting and management strategy is adopted to achieve automated updates.
It achieves automated and efficient data updates, avoids data duplication and delays, and ensures the traceability of data versions and the accuracy of updates.
Smart Images
Figure CN120973799A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present disclosure relates to the technical field of computer, and particularly relates to a data updating method and device, equipment, storage medium and product. BACKGROUND
[0002] Knowledge base data needs to be updated periodically to maintain accuracy and timeliness. The automatic method in the related art usually collects data through API, covers and stores after cleaning and integration, and realizes periodic updating. However, this scheme has the following deficiencies in periodic updating management and version control: first, the data coverage is chaotic, and the historical version is difficult to track; second, it depends on fixed period or manual triggering of updating, and cannot be adjusted adaptively according to the data state, which easily causes data repeated processing or updating delay, and reduces the overall efficiency. SUMMARY
[0003] The present disclosure provides a data updating method, device, equipment, storage medium and product to improve updating efficiency.
[0004] The technical solution of the present disclosure is implemented as follows:
[0005] The present disclosure provides a data updating method, which comprises: in the process of performing second batch updating on a master data table, determining a target round to which the second batch belongs according to the data amount of the master data table and the data amount of a target data table corresponding to a first batch; the target data table is used for recording the target round and the data updated in each batch of the target round; the master data table is used for recording the data updated in the target round; generating a seed table according to a summary table corresponding to the master data table and the target round; the summary table is used for storing the data updated in the target round, and the seed table is used for storing the data identifier of the data to be updated; obtaining the data to be updated based on the data identifier of the data to be updated, and generating a result table; the result table is used for storing the data to be updated obtained in the second batch; updating the summary table corresponding to the target round according to the result table; determining the target data table of the second batch based on the target data table of the first batch and the updated summary table; the target data table of the second batch is used for performing third batch updating on the master data table; the first batch is executed before the second batch, and the third batch is executed after the second batch.
[0006] In some possible implementation manners, the target round to which the second batch updating on the master data table belongs is determined according to the data amount of the master data table and the data amount of the target data table corresponding to the first batch, which comprises: comparing the data amount of the master data table and the data amount of the target data table corresponding to the first batch; in the case that the data amount of the master data table and the data amount of the target data table are inconsistent, determining that the target round is the current round; in the case that the data amount of the master data table and the data amount of the target data table are consistent, triggering updating of the next round.
[0007] In some possible implementation manners, the seed table is generated according to the master data table and the summary table corresponding to the target round, including: determining target data identifiers that are not covered by the summary table corresponding to the target round in the master data table by comparing data identifiers of data in the master data table and data identifiers of data in the summary table; obtaining the target data identifiers, generating the seed table, and recording the target round corresponding to the seed table.
[0008] In some possible implementation manners, the summary table corresponding to the target round is updated according to the result table, including: merging the result table and the summary table corresponding to the first batch; wherein the data amount of the summary tables corresponding to different batches is different in the same round; and screening the merged data to retain data updated in the target round, to obtain the updated summary table.
[0009] In some possible implementation manners, the target data table of the second batch is determined based on the target data table of the first batch and the updated summary table, including: merging the updated summary table and the target data table corresponding to the first batch; querying duplicate data identifiers in the merged data; and retaining data updated in the latest round for the data corresponding to the duplicate data identifiers, to obtain the updated target data table.
[0010] In some possible implementation manners, the data updating method further includes: in response to an instruction of adding new data in the target data table, obtaining a data identifier of the data to be added; and storing the data identifier of the data to be added to the master data table.
[0011] The present disclosure provides a data updating apparatus, including: a round confirmation module configured to determine a target round to which a second batch belongs according to a data amount of a master data table and a data amount of a target data table corresponding to a first batch in a process of updating the master data table by the second batch; the target data table is configured to record the target round and data updated in each batch of the target round; the master data table is configured to record the data updated in the target round; a data processing module configured to generate a seed table according to the master data table and a summary table corresponding to the target round; the summary table is configured to store the data updated in the target round, and the seed table is configured to store data identifiers of data to be updated; a data acquisition module configured to obtain the data to be updated based on the data identifiers of the data to be updated, and generate a result table; the result table is configured to store the data to be updated obtained in the second batch; a data updating module configured to update the summary table corresponding to the target round according to the result table; a periodic updating module configured to determine a target data table of a second batch based on a target data table of a first batch and an updated summary table; the target data table of the second batch is configured to update the master data table by a third batch; the first batch is executed before the second batch, and the third batch is executed after the second batch.
[0012] In some possible implementation manners, the round confirmation module is configured to compare the data amount of the master data table and the data amount of the target data table corresponding to the first batch; in the case that the data amount of the master data table and the data amount of the target data table are inconsistent, the target round is determined as the current round; in the case that the data amount of the master data table and the data amount of the target data table are consistent, the update of the next round is triggered.
[0013] In some possible implementation manners, the data processing module is configured to determine the target data identifier in the master data table which is not covered by the target round corresponding summary table by comparing the data identifier of the data in the master data table and the data identifier of the data in the summary table; acquire the target data identifier, generate a seed table, and record the target round corresponding to the seed table.
[0014] In some possible implementation manners, the data update module is configured to merge the result table and the summary table corresponding to the first batch; wherein the data amount of the summary tables corresponding to different batches in the same round is different; and perform screening on the merged data, retain the data updated in the target round, and obtain the updated summary table.
[0015] In some possible implementation manners, the periodical update module is configured to merge the updated summary table and the target data table corresponding to the first batch; in the merged data, query the repeated data identifier; for the data corresponding to the repeated data identifier, retain the data updated in the latest round, and obtain the updated target data table.
[0016] In some possible implementation manners, the data update apparatus further includes an added data module configured to, in response to an instruction of adding data in the target data table, acquire the data identifier of the data to be added; and store the data identifier of the data to be added to the master data table.
[0017] The present disclosure provides an electronic device, comprising: a memory configured to store executable instructions; and a processor configured to execute the executable instructions stored in the memory to implement the method provided by the present disclosure.
[0018] The present disclosure provides a computer storage medium storing executable instructions, which are configured to be executed by a processor to implement the method provided by the present disclosure.
[0019] The present disclosure provides a computer program product comprising a computer program or instructions, which are configured to be executed by a processor to implement the method provided by the present disclosure.
[0020] The present disclosure has the following beneficial effects:
[0021] In the present disclosure, by determining the target round to which the second batch belongs, the target data table after the second batch is updated is obtained to trigger the update of the third batch, which can realize the update rhythm of completion triggering, replace the update mode of manually determining whether the update is completed in the case of fixed time interval, and improve the update efficiency.
[0022] Further, in the data update method, in addition to the main data table, the target data table, the seed table, the result table and the summary table are introduced; the table records are implemented and managed, so that the data update process is more clear, and the operability is improved.
[0023] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS
[0024] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0025] Figure 1 The first embodiment flowchart of the data update method provided by the embodiment of the present disclosure is shown in the following figure:
[0026] Figure 2 The second embodiment flowchart of the data update method provided by the embodiment of the present disclosure is shown in the following figure:
[0027] Figure 3 The structure diagram of the data update device in the embodiment of the present disclosure is shown in the following figure:
[0028] Figure 4 The hardware entity diagram of an electronic device provided by the embodiment of the present disclosure is shown in the following figure. DETAILED DESCRIPTION
[0029] The exemplary embodiments will be described in detail herein with reference to the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present disclosure. Instead, they are merely examples of apparatuses consistent with some aspects of the present disclosure as detailed in the appended claims.
[0030] In order to illustrate the technical solutions described in the present disclosure, the following will be described by specific embodiments.
[0031] Data in knowledge databases typically requires continuous periodic updates to maintain accuracy and timeliness. This dynamic update mechanism is a core requirement for ensuring data real-time performance and accuracy, especially crucial in high-frequency update scenarios such as finance, news, and social networks. However, faced with ever-increasing data volumes, traditional manual update methods are inefficient and prone to errors. Currently, the main processes of dynamic update methods for knowledge databases in related technologies include: data collection, data cleaning, data integration and storage, and automatic updates. This method obtains the latest data through API interfaces and periodically triggers update programs to overwrite old data to achieve automated updates. However, this approach has significant shortcomings in periodic update management and data version control: (1) Lack of round management: The lack of a clear update round division mechanism leads to chaotic overlay of new and old data, making it difficult to track historical versions; (2) The fixed-cycle update mechanism lacks flexibility: Update tasks cannot automatically trigger the next round of updates based on data status, requiring manual intervention or fixed time intervals, which may result in some data being processed repeatedly during the update process, or some data failing to be updated in time due to excessively long update intervals; The combination of these limitations reduces update efficiency.
[0032] To address the aforementioned issues, this disclosure provides a data update method, apparatus, device, storage medium, and product to improve update efficiency.
[0033] Figure 1 A flowchart illustrating a first embodiment of the data update method provided in this disclosure is shown below. Figure 1 As shown, the method may include:
[0034] Step S101: During the second batch update of the master data table, the target round to which the second batch belongs is determined based on the data volume of the master data table and the data volume of the target data table corresponding to the first batch.
[0035] In some embodiments, a knowledge base may include multiple master data tables, each targeting a specific domain. For example, a knowledge base may include a singer master data table, a stock master data table, and a user master data table, etc.
[0036] In some embodiments, the master data table is used to store all data for the relevant domain. Taking the singer domain as an example, the content stored in the singer master data table includes: singer ID, singer name, gender, birthday, number of fans, number of albums, number of songs, number of music videos, awards, etc.
[0037] In some embodiments, a round refers to a basic unit of performing a complete round of updating full-amount data in the master data table. In the case where the data amount of the full-amount data is large, one round can be split into multiple batches for execution, each batch updating a part of the full-amount data, and the complete update of the full-amount data is realized by continuously executing multiple batches.
[0038] In some embodiments, the target data table is used to store the latest data in the full-amount data and the round corresponding to the latest data. It can be understood that, in the case where the current round is not updated, for the data that has been updated in the current round, this part of data is the latest data; for this part of data, the target data table is associated with the data updated in the current round and the round identifier of the current round. For the data that has not been updated in the current round, the data updated in the last round is the latest data; for this part of data, the target data table is associated with the data updated in the last round and the round identifier of the last round.
[0039] In an example, taking the singer target data table as an example, the singer target data table includes singer A related information, singer B related information, and singer C related information. The singer target data table is updated to the 5th round, in the 5th round, the singer A related information and the singer B related information have been updated, and the singer C related information has not been updated. At this time, the singer target data table stores: [singer A related information; round = 5], [singer B related information; round = 5], and [singer C related information; round = 4].
[0040] In some embodiments, by comparing the data amount of the master data table and the data amount of the target data table of the first batch, it can be determined whether the update of the second batch belongs to the same round as the first batch or belongs to different rounds. That is, in the case where the data amount of the master data table and the data amount of the target data table are the same, it indicates that the update of the current round is completed, the first batch is the last batch of the belonging round, and the second batch belongs to the next round; in the case where the data amount of the master data table and the data amount of the target data table are different, it indicates that the update of the current round is not completed, and the first batch is not the last batch of the belonging round. The second batch is the batch adjacent to the first batch.
[0041] In the embodiments of the present disclosure, according to the actual data change situation (i.e., the data change situation of the master data table and the target data table), the update frequency is dynamically adjusted, and it is automatically determined whether to start the next round of update, which can improve the update efficiency.
[0042] In step S102, a seed table is generated according to the summary table corresponding to the master data table and the target round. The seed table is used to store the data identifier of the data to be updated.
[0043] In some embodiments, the summary table is used to store the data that has been updated in the target round and the round identifier of the target round.
[0044] In an example, taking the singer field as an example, the full amount of data stored in the singer master data table includes singer A related information, singer B related information, and singer C related information. The target round (the target round is the fifth round) only updates the singer A related information and the singer B related information; at this time, the singer summary table stores: [singer A related information; round = 5], [singer B related information; round = 5].
[0045] In step S103, based on the data identifier of the data to be updated, the data to be updated is obtained, and a result table is generated. The result table is used to store the data to be updated obtained in the second batch.
[0046] In some embodiments, the data identifier can be used to index the data associated with the data identifier. For example, taking the singer field as an example, the gender, birthday, number of fans, number of albums, number of songs, number of MVs, and award records of the singer can be indexed according to the singer ID or singer name.
[0047] It can be understood that based on the data identifier of the data to be updated, the data to be updated is obtained from a third-party platform (such as a webpage, an application, etc.), and a result table is generated. The result table writes the data obtained in the second batch. Each batch corresponds to a result table.
[0048] In some embodiments, the data can be obtained in any of the following ways: obtained by a data collection tool from a third-party platform (webpage and application); downloaded or subscribed from an authorized data sharing platform data market or open data portal; obtained by calling a standardized application programming interface (API) provided by a third-party platform or an internal system; directly extracted from an associated internal or external database (such as MySQL, PostgreSQL, MongoDB, Oracle, etc.) through SQL query, ETL tool (such as Kettle, Airbyte, dbt) or database connector. The way of obtaining data is not limited to the above examples, and other ways of obtaining data can also be selected according to actual conditions, and the embodiments of the present disclosure are not limited in this regard.
[0049] In step S104, the summary table corresponding to the target round is updated according to the result table.
[0050] In some embodiments, the data to be updated obtained in the second batch in the result table is stored in the summary table to obtain an updated summary table,
[0051] At step S105, the target data table of the second batch (i.e., the target data table after the second batch update) is determined based on the target data table of the first batch and the updated summary table. The target data table of the second batch is used to perform the third batch update on the master data table. The first batch is the adjacent batch before the second batch, and the third batch is the adjacent batch after the second batch.
[0052] It can be understood that the updated summary table is merged with the target data table after the first batch update, and a deduplication process is performed to obtain the target data table after the second batch update. The target data table after the second batch update stores the cycle identifier of the target cycle and all data updated by the target cycle up to the second batch. For example, if the target cycle is the 5th cycle, the cycle identifier of the target cycle can be "cycle time = 5".
[0053] In some embodiments, after obtaining the target data table after the second batch update, the next batch (i.e., the third batch) update can be triggered, i.e., the data updating apparatus determines the cycle to which the third batch belongs based on the target data table of the second batch and the master data table.
[0054] In the embodiments of the present disclosure, the strategy of cycle accumulation is introduced to dynamically determine the cycle to which the new batch belongs, which can avoid cycle overlap or interruption, each update is assigned a unique cycle identifier, which can ensure that the version of the data is traceable, and periodic update is avoided, manual intervention is reduced, and update efficiency is improved.
[0055] In some embodiments, after obtaining the target data table after the second batch update, the updated data in the target data table can be synchronized to the master data table.
[0056] In some possible implementations, the step S101 can include: comparing the data amount of the master data table and the data amount of the target data table corresponding to the first batch; in the case that the data amount of the master data table and the data amount of the target data table are inconsistent, determining that the target cycle is the current cycle; in the case that the data amount of the master data table and the data amount of the target data table are consistent, triggering the update of the next cycle.
[0057] In some embodiments, the data amount is the number of entries of data identifiers stored in the data table. Each data identifier corresponds to an independent update unit (such as a singer, a stock, or a commodity, etc.).
[0058] In some embodiments, when the next batch (i.e., the second batch) of updates is performed, the round to which the next batch of updates belongs is determined. For example, if the data amount of the master data table is not the same as the data amount of the target data table after the previous batch (i.e., the first batch) of updates, it indicates that after the previous batch of updates, the full amount of data has not been updated, and the current round has not been completed. Therefore, the next batch belongs to the same round as the previous batch. If the data amount of the master data table is the same as the data amount of the target data table after the previous batch of updates, it indicates that the round to which the previous batch belongs has been updated, and the next batch belongs to the first batch of the next round.
[0059] In an example, Y = data amount of the master data table - data amount corresponding to max cycle_time in the target data table. Wherein, max cycle_time represents the maximum round, and the data amount corresponding to max cycle_time in the target data table is the data amount corresponding to the maximum round recorded in the target data table. If Y ≠ 0, it indicates that the current round has not been completed, and the data acquisition and update of the current round is continued. The target round = max cycle_time. If Y = 0, it indicates that the current round has been completed, and the data acquisition and update of the next round is entered. At this time, the target round = max cycle_time + 1.
[0060] In the embodiments of the present disclosure, at the beginning of each batch update, the target round is determined by comparing the data amounts of the master data table and the target data table. This can avoid relying on manual triggering of the next round of updates, and achieve automation of data updates.
[0061] In some possible implementations, the step S102 can include: determining target data identifiers that are not covered by the summary table corresponding to the target round, by comparing data identifiers of data in the master data table and data identifiers of data in the summary table; obtaining the target data identifiers, generating a seed table, and recording the target round corresponding to the seed table.
[0062] It can be understood that by comparing the data identifiers in the master data table and the data identifiers in the summary table, it can be determined which data identifiers in the target round have not been updated. The data identifiers that exist in the master data table but do not exist in the summary table are the data identifiers of data that have not been updated in the target round (i.e., target data identifiers). Based on the target data identifiers, a seed table is generated, and the seed table stores the round identifier of the target round in addition to the target data identifiers.
[0063] In some embodiments, in the case that the update of the current round is not completed (i.e. the update of the next batch belongs to the current round), the cycle_time of the seed table = max cycle_time. At this time, the data in the seed table is identified as the data that has not been covered in the current round summary table (i.e. the data identifier that does not exist in the summary table but exists in the master data table).
[0064] In some other embodiments, in the case that the update of the current round is completed and the update of the next batch (i.e. the second batch) belongs to a new round, the cycle_time of the seed table = max cycle_time + 1. At this time, the seed table stores the data identifier of the full amount of data.
[0065] In the embodiments of the present disclosure, the seed table is generated based on the target data identifier, and the target data identifier in the seed table corresponds to the data to be updated. The data to be updated can be obtained according to the seed table, which can ensure that there is no omission in the updating process and ensure the integrity of the updated data.
[0066] In some possible implementation manners, the step S104 can include: merging the result table and the summary table corresponding to the first batch; wherein the data amount of the summary tables corresponding to different batches in the same round is different; and performing screening on the merged data to retain the data updated in the target round, to obtain the updated summary table.
[0067] It can be understood that the result table stores the data obtained in the updating process of the second batch. The data in the result table and the data in the summary table after the first batch update are merged. Then, the merged data is screened, that is, for the data with the same data identifier, only the data updated last time (i.e. the data updated in the target round) is retained. After screening, the summary table after the second batch update is obtained.
[0068] In some embodiments, for the same round, as the batch increases, the data amount of the summary table also gradually increases. For example, in the case that the first batch and the second batch belong to the same round, the data amount of the summary table after the second batch update is greater than the data amount of the summary table after the first batch update. It should be noted that there is only one summary table for one round, and the summary table after the second batch update is updated on the basis of the summary table after the first batch update, that is, the data updated in the second batch is written into the latest partition of the summary table after the first batch update.
[0069] In the embodiments of the present disclosure, the data updated in the partition of the summary table can retain the update trace of the historical batch, which is convenient for tracing the update of each batch of data.
[0070] In some possible implementation manners, the step S105 can include: merging the updated summary table and the target data table corresponding to the first batch; querying repeated data identifiers in the merged data; and retaining the data corresponding to the repeated data identifiers in the data updated in the latest round to obtain the target data table after the second batch update.
[0071] It can be understood that the target data table after the second batch update is obtained based on the target data table after the first batch update and the summary table after the second batch update. The data in the summary table after the second batch update is merged with the data in the target data table after the first batch update. The data identifiers of some data after the merging are the same, and the data with the same data identifier is retained in the data updated in the latest round.
[0072] In some embodiments, the summary table after the second batch update is merged with the target data table after the first batch update, and deduplication is performed according to the data identifier and the round; that is, only the data of each object in the latest round is retained and stored in the latest partition of the target data table, to obtain the target data table after the second batch update.
[0073] It should be noted that the target data table can store both the data updated in the last round and the data updated in the current round; for example, the target data table includes data A, data B, data C and data D, wherein the data A and the data B are updated in the current round, and the data C and the data D are not updated; then, the data A and the data B in the target data table are the data updated in the current round, and the data C and the data D are the data updated in the last round.
[0074] In the embodiments of the present disclosure, the summary table after the second batch update and the target data table after the first batch update are merged and screened to obtain the target data table after the second batch update. Only the updated data is processed, rather than full coverage, so as to reduce the computing resources.
[0075] In some possible implementation manners, after obtaining the target data table after the second batch update, a third batch update is triggered.
[0076] It can be understood that, after obtaining the target data table after the second batch update, the target round to which the third batch belongs is determined by comparing the data amount of the master data table and the data amount of the target data table after the second batch update, and then the third batch update is performed. The third batch update method is the same as the second batch, and the embodiments of the present disclosure do not repeat the description.
[0077] In some embodiments, Figure 2A second embodiment of the data updating method provided by the embodiments of the present disclosure is shown in the flowchart below. Figure 2
[0078] In step S201, the target round of the second batch is calculated.
[0079] Y = the data amount of the master data table - the data amount corresponding to max cycle_time in the target data table. If Y ≠ 0, the target round = max cycle_time; if Y = 0, the target round = max cycle_time + 1.
[0080] In step S202, the seed table = the master data table - the summary table.
[0081] The target data identifier in the master data table that is not covered by the summary table corresponding to the target round is determined by comparing the data identifier in the master data table and the data identifier in the summary table; the target data identifier is obtained, the seed table is generated, and the target round corresponding to the seed table is recorded.
[0082] In an example, the full amount of data stored in the master data table includes a data identifier. For example, the data identifier of the full amount of data of the singer master data table can include the singer ID and the singer name; the data identifier of the full amount of data of the user master data table can include the user ID, the user registration place, and the latest login time; and the data identifier of the full amount of data of the stock master data table can include the stock code, the industry to which the stock belongs, and the listing date.
[0083] In step S203, the data to be updated is obtained according to the target data identifier in the seed table; and the result table is generated according to the data to be updated, in which the round identifier of the target round and the data to be updated are associated and saved.
[0084] In step S204, the result table after the second batch of updates is completed and the summary table after the first batch of updates are merged, the maximum round is retained for the repeated data identifier, and the summary table after the second batch of updates is obtained.
[0085] In step S205, the summary table after the second batch of updates is completed and the target data table after the first batch of updates are merged, the maximum round is retained for the repeated data identifier, and the target data table after the second batch of updates is obtained.
[0086] In some possible implementations, the above data updating method can further include: in response to an instruction to add new data in the target data table, obtaining the data identifier of the data to be added; and storing the data identifier of the data to be added to the master data table.
[0087] It can be understood that in addition to updating data, there will be new data, when the data needs to be added, the data identifier of the data to be added can be obtained from the third-party platform, and the data identifier of the data to be added is written into the master data table.
[0088] In some embodiments, when new data is detected, a new data instruction is generated; the new data instruction is sent to the data updating device; wherein the new data instruction is used to indicate that data is added in the target data table.
[0089] In some embodiments, the data updating device can include a monitoring module and a data adding module, the monitoring module is used to detect whether new data is generated in the third-party platform, when new data is detected, a new data instruction is generated; and the new data instruction is sent to the data adding module; the new data module is used to respond to the new data instruction, to obtain the data identifier of the data to be added from the third-party platform, and to store the data identifier of the data to be added to the master data table.
[0090] In some embodiments, the data identifier of the data to be added is stored in the master data table, and the amount of data in the master data table is increased; after the first batch of updates is completed, the target round to which the second batch belongs is determined according to the master data table after the data identifier is increased and the target data table corresponding to the first batch.
[0091] In some embodiments, the data in the target data table needs to be updated periodically and continuously to maintain the accuracy and up-to-date status of the data. The data updating method described in the embodiments of the present disclosure realizes round accumulation by calculating the target round after the periodic update of the data in each round is completed, to automatically perform the next round of update, thereby realizing uninterrupted update and expansion of the data in the target data table.
[0092] In an example, the "singer master data table" is updated, the data is obtained through the API interface, and the update time of each batch is one day for example; the data amount of the master data table is 100000; the target round corresponding to the target data table on the nth day is "cycle_time=3", and the data amount is 50000; the round corresponding to the summary table is "cycle_time=3", and the data amount is 50000; the data collection amount is set to 10000 pieces / day.
[0093] On the n+1 day, the data updating method is as follows:
[0094] Step 1: Calculate cycle_time (i.e. target round).
[0095] Wherein, Y = the data amount of the main data table - the data amount corresponding to max_cycle_time in the target data table; Y = 100000 - 50000 = 50000 ≠ 0, cycle_time = max_cycle_time = 3. Then continue the 3rd round of update.
[0096] Second step: generate seed table.
[0097] Wherein, seed table = main data table - summary table, 100000 - 50000 (cycle_time = 3) = 50000; the seed table contains 50000 singer IDs, cycle_time = 3.
[0098] Third step: data collection and result table generation.
[0099] Wherein, collect 10000 singer IDs corresponding singer details, the result table contains 10000 singer details, cycle_time = 3. The singer details can include: gender, birthday, number of fans, number of albums, number of songs, number of MVs, award records, etc.
[0100] Fourth step: summary table update
[0101] Wherein, summary table (n+1 day) = result table + summary table (n day), 10000 (cycle_time = 3) + 50000 (cycle_time = 3) = 60000 (cycle_time = 3), keep the latest round. The summary table contains 60000 singer details, cycle_time = 3.
[0102] Fifth step: target data table update.
[0103] Wherein, target data table (n+1 day) = summary table + target data table (n day), 60000 (cycle_time = 3) + 50000 (cycle_time = 3) = 110000 (cycle_time = 3); De-duplication, keep the latest round of each object. The de-duplicated target data table contains 60000 singer details, cycle_time = 3.
[0104] Sixth step: trigger the n+2 day update.
[0105] On the n+2 day, the data update method is as follows:
[0106] Seventh step: calculate cycle_time.
[0107] Wherein, Y = the data volume of the master data table - the data volume corresponding to max_cycle_time in the target data table. Y = 100000 - 60000 ≠ 0, cycle_time = max_cycle_time = 3.
[0108] Eighth step: generating a seed table.
[0109] Wherein, the seed table = the master data table - the summary table, 100000 - 60000 (cycle_time = 3) = 40000; the seed table contains 40000 singer IDs, cycle_time = 3.
[0110] Ninth step: data collection and result table generation.
[0111] Wherein, 10000 singer details of singer IDs are collected, the result table contains 10000 singer details, cycle_time = 3.
[0112] Tenth step: summary table update.
[0113] Wherein, the summary table (the n+2th day) = the result table + the summary table (the n+1th day), 10000 (cycle_time = 3) + 60000 (cycle_time = 3) = 70000 (cycle_time = 3); the summary table contains 70000 singer details, cycle_time = 3.
[0114] Eleventh step: target data table update.
[0115] Wherein, the target data table (the n+2th day) = the summary table + the target data table (the n+1th day), 70000 (cycle_time = 6) + 60000 (cycle_time = 3) = 130000 (cycle_time = 3); deduplication, keeping the latest round of each object. The target data table after deduplication contains a total of 70000 singer details.
[0116] Twelfth step: triggering the n+3th day update.
[0117] In another example, the master data table of "singer" is updated, data is obtained through an API interface, and the update duration of each batch is one day. On the n th day, 1000 singer IDs are newly added in the latest master data table, and the data volume changes from 100000 to 101000. The round of the target data table corresponds to "cycle_time = 5", and the data volume is 100000. The round of the summary table corresponds to "cycle_time = 5", and the data volume is 100000. The data collection volume is set to 10000 per day.
[0118] On the nth+1 day, the data updating method is as follows:
[0119] First step: Calculate cycle_time (i.e. target round).
[0120] Wherein, Y = the data amount of the master data table - the data amount corresponding to max_cycle_time in the target data table; Y = 101000 - 100000 = 1000 ≠ 0, cycle_time = max_cycle_time = 5. Then continue the 5th round of updating.
[0121] Second step: Generate seed table.
[0122] Wherein, seed table = master data table - summary table, 101000 - 100000 (cycle_time = 5) = 1000; the seed table contains 1000 singer IDs, cycle_time = 5.
[0123] Third step: Data collection and result table generation.
[0124] Wherein, collect 1000 singer IDs corresponding singer details, the result table contains 1000 singer details, cycle_time = 5.
[0125] Fourth step: Summary table updating
[0126] Wherein, summary table (nth+1 day) = result table + summary table (nth day), 1000 (cycle_time = 5) + 100000 (cycle_time = 5) = 101000 (cycle_time = 5), keep the latest round. The summary table contains 101000 singer details, cycle_time = 5.
[0127] Fifth step: Target data table updating.
[0128] Wherein, target data table (nth+1 day) = summary table + target data table (nth day), 101000 (cycle_time = 5) + 100000 (cycle_time = 5) = 201000 (cycle_time = 5); de-duplication, keep the latest round of each object. The de-duplicated target data table contains 101000 singer details, cycle_time = 5.
[0129] Sixth step: Trigger the nth+2 day updating.
[0130] On the nth+2 day, the data updating method is as follows:
[0131] Seventh step: Calculate cycle_time.
[0132] Wherein, Y = the data amount of the master data table - the data amount corresponding to max_cycle_time in the target data table. Y = 101000 - 101000 = 0, cycle_time = max_cycle_time + 1 = 5 + 1 = 6. The 6th round full update is started.
[0133] Step 8: Seed table is generated.
[0134] Wherein, Seed table = master data table - summary table, 101000 - 0 (cycle_time = 6) = 101000; the seed table contains 101000 singer IDs, cycle_time = 6.
[0135] Step 9: Data collection and result table generation.
[0136] Wherein, 10000 singer details of singer IDs are collected, the result table contains 10000 singer details, cycle_time = 6.
[0137] Step 10: Summary table update.
[0138] Wherein, Summary table (n+2th day) = result table + summary table (n+1th day), 10000 (cycle_time = 6) + 101000 (cycle_time = 5) = 111000 (cycle_time = 5, 6), the latest round is kept. The summary table contains 10000 singer details, cycle_time = 6.
[0139] Step 11: Target data table update.
[0140] Wherein, Target data table (n+2th day) = summary table + target data table (n+1th day), 10000 (cycle_time = 6) + 101000 (cycle_time = 5) = 111000 (cycle_time = 5, 6); deduplication, the latest round of each object is kept. The deduplicated target data table contains a total of 101000 singer details, of which 10000 singer details have cycle_time = 6 and 91000 singer details have cycle_time = 5.
[0141] Step 12: Trigger the n+3th day update.
[0142] In the embodiments of the present disclosure, by determining the target round to which the second batch belongs, the target data table updated after the second batch is obtained, so as to trigger the update of the third batch, the update rhythm of completing and triggering can be realized, the update mode of manually determining whether the update is completed in the case of fixed time interval is replaced, and the update efficiency is improved.
[0143] Furthermore, in the data update method, in addition to the master data table, a target data table, a seed table, a result table, and a summary table are introduced; this allows for precise identification and management of data in each round of updates, ensuring data consistency and integrity. Implementing separate table recording and management makes the data update process clearer and improves operability.
[0144] The following describes an exemplary structure of the data update device 30 provided in the embodiments of this disclosure as a software module. Figure 3 This is a schematic diagram of a data updating device according to an embodiment of the present disclosure. See also: [link to related documentation] Figure 3 As shown, the software modules in the data update device 30 of the application stored in the memory may include: a round confirmation module 31, used to determine the target round to which the second batch belongs based on the data volume of the main data table and the data volume of the target data table corresponding to the first batch during the second batch update of the main data table; the target data table is used to record the target round and the data updated in each batch of the target round; the main data table is used to record the data updated in the target round; and a data processing module 32, used to generate a seed table based on the main data table and the summary table corresponding to the target round; the summary table is used to store the data updated in the target round. The data includes a seed table for storing data identifiers of the data to be updated; a data acquisition module 33 for acquiring the data to be updated based on the data identifiers and generating a result table; the result table for storing the data to be updated acquired in the second batch; a data update module 34 for updating the summary table corresponding to the target round based on the result table; and a periodic update module 35 for determining the target data table for the second batch based on the target data table of the first batch and the updated summary table; the target data table of the second batch is used to update the main data table for the third batch; the first batch is executed before the second batch, and the third batch is executed after the second batch.
[0145] In some possible implementations, the round confirmation module 31 is used to compare the data volume of the master data table with the data volume of the target data table corresponding to the first batch; if the data volume of the master data table and the data volume of the target data table are inconsistent, the target round is determined as the current round; if the data volume of the master data table and the data volume of the target data table are consistent, the update of the next round is triggered.
[0146] In some possible implementations, the data processing module 32 is used to determine the target data identifier in the main data table that is not covered by the summary table corresponding to the target round by comparing the data identifier of the data in the main data table with the data identifier of the data in the summary table; obtain the target data identifier, generate a seed table, and record the target round corresponding to the seed table.
[0147] In some possible implementation, the data updating module 34 is configured to merge the result table and the summary table corresponding to the first batch; wherein, in the same round, the data amount of the summary tables corresponding to different batches is different; and the merged data is filtered to retain the data updated in the target round, to obtain the updated summary table.
[0148] In some possible implementation, the periodical updating module 35 is configured to merge the updated summary table and the target data table corresponding to the first batch; in the merged data, the repeated data identifiers are queried; and for the data corresponding to the repeated data identifiers, the data updated in the latest round is retained, to obtain the updated target data table.
[0149] In some possible implementation, the data updating apparatus 30 further includes an added data module configured to, in response to an instruction of adding data in the target data table, acquire the data identifier of the data to be added; and store the data identifier of the data to be added to the master data table.
[0150] The above apparatus embodiment is similar to the description of the above method embodiment, and has similar beneficial effects to the method embodiment. In some embodiments, the apparatus provided by the embodiments of the present disclosure has functions or includes modules that can be used to execute the methods described in the above method embodiments. For technical details of the apparatus embodiments of the present disclosure that are not disclosed, please refer to the description of the method embodiments of the present disclosure.
[0151] It should be noted that, in the embodiments of the present disclosure, if the above method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present disclosure can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the embodiments of the present disclosure. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM), a magnetic disk or an optical disk, and various program codes that can be stored in the medium. Thus, the embodiments of the present disclosure are not limited to any specific hardware, software or firmware, or any combination of hardware, software and firmware.
[0152] Figure 4 A hardware entity schematic diagram of an electronic device provided by the embodiments of the present disclosure is provided. For example, the electronic device 400 can be a mobile phone, a computer, a digital broadcast terminal, a message transmission device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
[0153] Referring to Figure 4 The electronic device 400 can include one or more of the following components: a processing component 401, a memory 402, a power component 403, a multimedia component 404, an audio component 405, an input / output (I / O) interface 406, a sensor component 407, and a communication component 408.
[0154] The processing component 401 generally controls the overall operation of the electronic device 400 such as the operation associated with at least one of display, telephony, data communication, camera operation, and recording operation. The processing component 401 can include one or more processors 409 to execute instructions to complete all or a part of steps of the above methods. In addition, the processing component 401 can include one or more modules to facilitate interaction between the processing component 401 and other components. For example, the processing component 401 can include a multimedia module to facilitate the interaction between the multimedia component 404 and the processing component 401.
[0155] The memory 402 is configured to store various types of data to support the operations of the electronic device 400. Examples of these data include at least one of instructions for at least one application or method operating on the electronic device 400, contact data, phonebook data, messages, pictures, and videos. The memory 402 can be implemented by any type of volatile or nonvolatile memory, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
[0156] The power component 403 supplies power to the various components of the electronic device 400. The power component 403 can include at least one of a power management system, one or more power supplies, and other components associated with generating, managing and distributing power for the electronic device 400.
[0157] The multimedia component 404 includes a screen providing an output interface between the electronic device 400 and a user. In some embodiments, the screen includes a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide and gesture on the touch panel. The touch sensor can not only sense a boundary of a touching or sliding action, but also detect duration and pressure related to the touching or sliding action. In some embodiments, the multimedia component 404 includes a front camera and / or a rear camera. When the electronic device 400 is in an operation mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.
[0158] The audio component 405 is configured to output and / or input audio signals. For example, the audio component 405 includes a microphone (MIC) to receive an external audio signal when the electronic device 400 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 402 or transmitted via the communication component 408. In some embodiments, the audio component 405 further includes a speaker to output audio signals.
[0159] The I / O interface 406 provides an interface between the processing component 401 and peripheral interface modules, which can be a keypad, a click wheel, and buttons, etc. The buttons can include, but are not limited to, a home button, a volume button, a start button, and a lock button.
[0160] The sensor component 407 includes one or more sensors for providing status assessments for various aspects of the electronic device 400. For example, the sensor component 407 can detect an open / closed position of the electronic device 400, relative positioning of components, such as a display and a keypad of the electronic device 400, a change in position of the electronic device 400 or a component of the electronic device 400, presence or absence of user contact with the electronic device 400, orientation or acceleration / deceleration / g-force and temperature changes of the electronic device 400. The sensor component 407 can include an accelerometer to detect a change in position, orientation, and the like. The sensor component 407 can also include a proximity sensor configured to detect presence of nearby objects without any physical contact. The sensor component 407 can further include a light sensor, such as a complementary metal oxide semiconductor (CMOS) or charge coupled device (CCD) image sensor, for use in imaging applications. In some embodiments, the sensor component 407 can further include at least one of an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, and a temperature sensor, among others.
[0161] The communication component 408 is configured to facilitate wired or wireless communication between the electronic device 400 and other devices. The electronic device 400 can access a wireless network based on a communication standard, such as Wi-Fi, 4G, 5G, or a combination thereof. In an example embodiment, the communication component 408 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an example embodiment, the communication component 408 can further include a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) techniques, infrared data association (IrDA) techniques, UWB techniques, Bluetooth (BT) techniques, and other techniques.
[0162] In example embodiments, the electronic device 400 can be implemented with one or more application specific integrated circuits (ASICs), DSPs, DSPDs, programmable logic devices (PLDs), FPGAs, controllers, micro-controllers, microprocessors, or other electronic elements.
[0163] In an example embodiment, a non-transitory computer-readable storage medium is also provided, for example, the memory 402 including executable instructions or a computer program, which can be executed by the processor 409 of the electronic device 400 to complete the above method.
[0164] The electronic device provided by the embodiments of the present disclosure includes a memory and a processor, the memory stores a computer program executable on the processor, and the processor implements part or all of the steps of the above method when executing the program.
[0165] The computer-readable storage medium provided by the embodiments of the present disclosure stores a computer program, and the computer program is executed by a processor to implement part or all of the steps of the above method. The computer-readable storage medium can be transitory or non-transitory.
[0166] The computer program provided by the embodiments of the present disclosure includes computer-readable code, and when the computer-readable code is run in a computer device, a processor in the computer device executes part or all of the steps of the above method.
[0167] The computer program product provided by the embodiments of the present disclosure includes a non-transitory computer-readable storage medium storing a computer program, and when the computer program is read and executed by a computer, part or all of the steps of the above method are implemented. The computer program product can be implemented by hardware, software or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium, and in other embodiments, the computer program product is specifically embodied as a software product, for example, a software development kit (SDK) or the like.
[0168] It should be noted that the above description of the various embodiments tends to emphasize the differences between the various embodiments, and the same or similar parts can be referred to each other. The above description of the device, storage medium, computer program and computer program product embodiments is similar to the description of the above method embodiments, and has similar beneficial effects as the method embodiments. For technical details not disclosed in the device, storage medium, computer program and computer program product embodiments of the present disclosure, please refer to the description of the method embodiments of the present disclosure.
[0169] It should be understood that every feature, structure, or characteristic described in relation to one embodiment is applicable to at least one other embodiment, in combination or in isolation, unless the context clearly dictates otherwise. Furthermore, the foregoing description is by way of example only, and other embodiments are also possible. It is, therefore, intended that the disclosure be taken in its broadest sense. The discussion of a feature in relation to an embodiment does not mean that it is a requirement for that embodiment, although it can be. The various embodiments of the disclosure can omit certain features provided in the description, design structure, or characteristic of one or more embodiments. In addition, the same description can be applied to different embodiments according to their functions or roles. It should be understood that the sequence of the steps / processes described above does not mean the order of execution, and the execution order of the steps / processes should be determined according to their functions and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the disclosure. The sequence number of the above embodiments of the disclosure is only for description, and does not represent the advantages or disadvantages of the embodiments.
[0170] It should be noted that the terms "comprising", "including", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or device that comprises a list of elements does not include only those elements, but can also include other elements not expressly listed or inherent to such process, method, article, or device. Without more limitations, the element defined by the phrase "comprising a" does not exclude the presence of additional identical elements in the process, method, article, or device that includes the element.
[0171] In several embodiments provided by the disclosure, it should be understood that the disclosed devices and methods can be implemented in other ways. The above-described device embodiments are only illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the various components shown or discussed can be through some interface, indirect coupling or communication connection between devices or units, which can be electrical, mechanical or other forms.
[0172] The units described above as separate components can or can not be physically separated, and the components shown as units can or can not be physical units; they can be located in one place or distributed on multiple network units; some or all of the units can be selected based on actual needs to achieve the purpose of the embodiment.
[0173] In addition, each functional unit in each embodiment of the disclosure can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be realized in the form of hardware or hardware plus software functional unit.
[0174] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware, the foregoing program can be stored in a computer readable storage medium, and the program executes the steps of the above-mentioned method embodiments when executed; and the foregoing storage medium includes a mobile storage device, a ROM, a magnetic disc or an optical disc and various storage medium capable of storing program codes.
[0175] Alternatively, the integrated units of the present disclosure can be stored in a computer readable storage medium if they are realized in the form of software function modules and sold or used as independent products. Based on such understanding, the technical solutions of the present disclosure can be embodied in the form of a software product, and the computer software product is stored in a storage medium, includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the various embodiments of the present disclosure. The foregoing storage medium includes a mobile storage device, a ROM, a magnetic disc or an optical disc and various storage medium capable of storing program codes.
[0176] Other embodiments of the present disclosure will be apparent to those skilled in the art upon consideration of the specification and practice of the present disclosure. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure following the general principles thereof and including the general principles thereof disclosed in the present disclosure and the art-recognized equivalents thereof. The specification and examples are to be regarded as illustrative only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0177] It should be understood that the present disclosure is not limited to the precise structures described and illustrated above and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the claims that follow.
Claims
1. A data update method, characterized in that, include: During the second batch update of the master data table, the target round to which the second batch belongs is determined based on the data volume of the master data table and the data volume of the target data table corresponding to the first batch. The target data table is used to record the target round and the data updated in each batch of the target round; The master data table is used to record the data updated in the target round; A seed table is generated based on the master data table and the summary table corresponding to the target round; The summary table is used to store the updated data in the target round, and the seed table is used to store the data identifiers of the data to be updated. Based on the data identifier of the data to be updated, obtain the data to be updated and generate a result table; The result table is used to store the data to be updated obtained in the second batch; Update the summary table corresponding to the target round based on the results table; Based on the target data table of the first batch and the updated summary table, the target data table of the second batch is determined; The target data table of the second batch is used to update the master data table in the third batch; the first batch is executed before the second batch, and the third batch is executed after the second batch.
2. The data update method according to claim 1, characterized in that, The step of determining the target round to which the second batch of updates to the master data table belongs, based on the data volume of the master data table and the data volume of the target data table corresponding to the first batch, includes: Compare the data volume of the master data table with the data volume of the target data table corresponding to the first batch; If the amount of data in the master data table and the amount of data in the target data table are inconsistent, the target round is determined to be the current round. If the amount of data in the master data table is the same as the amount of data in the target data table, the next round of updates will be triggered.
3. The data update method according to claim 1, characterized in that, The step of generating a seed table based on the master data table and the summary table corresponding to the target round includes: By comparing the data identifiers of the data in the master data table and the data identifiers of the data in the summary table, the target data identifiers in the master data table that are not covered by the summary table corresponding to the target round are determined. Obtain the target data identifier, generate the seed table, and record the target round corresponding to the seed table.
4. The data update method according to claim 1, characterized in that, The step of updating the summary table corresponding to the target round based on the result table includes: Merge the result table and the summary table corresponding to the first batch; wherein, within the same round, the amount of data in the summary tables corresponding to different batches is different; The merged data is filtered, and the data updated in the target round is retained to obtain the updated summary table.
5. The data update method according to claim 1, characterized in that, The step of determining the target data table for the second batch based on the target data table of the first batch and the updated summary table includes: Merge the updated summary table and the target data table corresponding to the first batch; In the merged data, identify duplicate data. For duplicate data identifiers, the data corresponding to the latest updated data is retained to obtain the updated target data table.
6. The data update method according to any one of claims 1 to 5, characterized in that, The data update method further includes: In response to an instruction to add data to the target data table, obtain the data identifier of the data to be added; The data identifier of the data to be added is stored in the master data table.
7. A data update device, characterized in that, include: The round confirmation module is used to determine the target round to which the second batch belongs during the process of updating the master data table in the second batch, based on the data volume of the master data table and the data volume of the target data table corresponding to the first batch. The target data table is used to record the target round and the data updated in each batch of the target round; the master data table is used to record the data updated in the target round. The data processing module is used to generate a seed table based on the master data table and the summary table corresponding to the target round; The summary table is used to store the updated data in the target round, and the seed table is used to store the data identifiers of the data to be updated. The data acquisition module is used to acquire the data to be updated based on the data identifier of the data to be updated, and generate a result table; The result table is used to store the acquired data to be updated; The data update module is used to update the summary table corresponding to the target round based on the result table; The periodic update module is used to determine the target data table for the second batch based on the target data table of the first batch and the updated summary table. The target data table of the second batch is used to update the master data table in the third batch; the first batch is executed before the second batch, and the third batch is executed after the second batch.
8. An electronic device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method according to any one of claims 1 to 6.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 6.
10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 6.