CN115470241A - Aggregated data updating method and device based on mapping dictionary table - Google Patents

Aggregated data updating method and device based on mapping dictionary table Download PDF

Info

Publication number
CN115470241A
CN115470241A CN202211143940.7A CN202211143940A CN115470241A CN 115470241 A CN115470241 A CN 115470241A CN 202211143940 A CN202211143940 A CN 202211143940A CN 115470241 A CN115470241 A CN 115470241A
Authority
CN
China
Prior art keywords
data
aggregation
aggregation result
dictionary table
detail
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211143940.7A
Other languages
Chinese (zh)
Inventor
叶大江
黄主斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Clinbrain Information Technology Co Ltd
Original Assignee
Shanghai Clinbrain Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Clinbrain Information Technology Co Ltd filed Critical Shanghai Clinbrain Information Technology Co Ltd
Priority to CN202211143940.7A priority Critical patent/CN115470241A/en
Publication of CN115470241A publication Critical patent/CN115470241A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2453Query optimisation
    • G06F16/24534Query rewriting; Transformation
    • G06F16/24539Query rewriting; Transformation using cached or materialised query results
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2455Query execution
    • G06F16/24553Query execution of query operations
    • G06F16/24554Unary operations; Data partitioning operations
    • G06F16/24556Aggregation; Duplicate elimination
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2458Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2477Temporal data queries

Abstract

When all detail data are grouped and aggregated, a first mapping dictionary table is generated according to the mapping relation between the detail data and the aggregation result, and a second mapping dictionary table is generated according to the mapping relation between the grouping result and the aggregation result. And then, if the detail data is updated, the newly added detail data or the historical detail data is modified, finding out a related group of which the aggregation result is changed due to the updated data by inquiring the first mapping dictionary table and the second mapping dictionary table, and re-aggregating the grouped data corresponding to the group to obtain a new aggregation result. Therefore, by applying the updating method provided by the application, grouping and aggregation of all data can be avoided, and data omission is further avoided because the first mapping dictionary table and the second mapping dictionary table comprising all data are inquired during updating.

Description

Aggregated data updating method and device based on mapping dictionary table
Technical Field
The application relates to the technical field of computer data processing, in particular to a method and a device for updating aggregated data based on a mapping dictionary table.
Background
Because the amount of raw data is too large, it is often desirable to quickly present aggregated results to a user, and it is generally necessary to perform calculations in advance and cache the results. But incremental data may be added or modifications to historical data may be made. The new data will be aggregated into the new results, and the modification of the historical data will affect the old aggregated results and the new aggregated results. For example, a piece of data originally belonging to department a is modified to become data of a new department C, and in the data updating process, the piece of data needs to be removed from the aggregation result of the old department a, and the updated data needs to be added to the aggregation result of the department C.
The current existing technology is to perform packet aggregation processing on all data every day or perform packet aggregation processing on data of last three years to realize data update. However, the data volume is too large, which not only results in excessive occupation of server resources, but also results in long update time, and in addition, grouping and aggregating the data of last three years results in missing update of some data, which results in low data update efficiency and instability of data update.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method and an apparatus for updating aggregated data based on a mapping dictionary table, so as to solve the problems that server resources occupy too much and the update duration is long due to grouping and aggregating all data in the prior art.
The aggregated data updating method based on the mapping dictionary table provided by the embodiment of the application comprises the following steps:
grouping the n detailed data by using the aggregation condition to obtain grouped data corresponding to the m groups; wherein n and m are both positive integers greater than 0;
respectively polymerizing each grouped data to obtain m polymerization results;
generating a first mapping dictionary table according to the mapping relation between the n detailed data and the m aggregation results;
generating a second mapping dictionary table according to the mapping relation between the m groups and the m aggregation results;
when data is updated, based on the query of the first mapping dictionary table and the second mapping dictionary table, the aggregation update of the grouped data corresponding to the updated data related group is realized.
In the above technical solution, when grouping and aggregating all the detail data, a first mapping dictionary table is generated according to the mapping relationship between the detail data and the aggregation result, and a second mapping dictionary table is generated according to the mapping relationship between the grouping and the aggregation result. And then, if the detail data is updated, the newly added detail data or the historical detail data is modified, finding out a related group of which the aggregation result is changed due to the updated data by inquiring the first mapping dictionary table and the second mapping dictionary table, and re-aggregating the grouped data corresponding to the group to obtain a new aggregation result. Therefore, by applying the updating method provided by the application, grouping and aggregation of all data can be avoided, resource occupation of a server is reduced, time for updating the data is shortened, and data omission is further avoided as the first mapping dictionary table and the second mapping dictionary table comprising all data are inquired during updating.
In some alternative embodiments, the detailed data includes: the detail identifier ID and preset values of k attributes;
the aggregation condition is i attributes in the k attributes, wherein k and i are positive integers larger than 0, and k is larger than or equal to i and larger than 0;
any two of the m groups have at least one attribute with different values;
each aggregation result corresponds to an aggregation result ID;
the first mapping dictionary table comprises the mapping relation between n detail identification IDs and m aggregation result IDs;
the second mapping dictionary table includes mappings of m packets to m aggregation result IDs.
In the above technical solution, each detail datum has a unique detail identifier ID and preset values of k attributes, an aggregation condition for performing grouping aggregation on all detail data is i attributes of the k attributes, each aggregation result corresponds to an aggregation result ID, the first mapping dictionary table is a mapping relationship between all detail identifier IDs and all aggregation result IDs, and the second mapping dictionary table is a one-to-one mapping relationship between groups and aggregation result IDs. If the value of the attribute of any detail data changes, the corresponding aggregation result ID can be obtained by looking up the first mapping dictionary table according to the detail identifier ID of the detail data, so that the aggregation result corresponding to the aggregation result ID is updated correspondingly. If any detailed data is grouped into another group after being updated, the corresponding aggregation result ID can be obtained by querying the second mapping dictionary table according to the redistributed group, so that the aggregation result corresponding to the aggregation result ID is updated correspondingly.
In some alternative embodiments, the k attributes include: a timestamp and a service time; the timestamp data is the time of updating the detail data at last, and the service time data is the time of creating the detail data;
the method further comprises the following steps:
acquiring detail data to be updated;
judging whether the timestamp data of the detail data to be updated is consistent with the service time data:
if yes, determining the detail data to be updated as newly added detail data;
if not, determining the detail data to be updated as the modification detail data.
In the above technical solution, the k attributes of the detail data at least include two attributes of a timestamp and a service time, where the timestamp data is the time when the detail data is updated last, and the service time data is the time when the detail data is created. When a certain detail data is updated, if the time stamp data of the detail data is inconsistent with the service time data, namely the time displayed by the time stamp of the detail data is behind the time displayed by the service time, the detail data is considered to be modified, and the detail data is determined to be modified; and if the timestamp data of the detail data is consistent with the service time data, the detail data is regarded as newly added data, and the newly added detail data is determined. And dividing the detail data area to be updated into newly-added detail data or modified detail data so as to realize data aggregation updating under two conditions through subsequent different processing flows.
In some optional embodiments, after determining that the detail data to be updated is the modified detail data, the method further includes:
inquiring a first mapping dictionary table according to the detail identifier ID of the modified detail data to obtain a corresponding first aggregation result ID;
regrouping the modified detail data by using an aggregation condition, and judging whether the modified detail data is distributed to a certain packet in m packets:
if the modification detail data are distributed to one of the m groups, inquiring a second mapping dictionary table according to the group redistributed by the modification detail data to obtain a corresponding second aggregation result ID;
and respectively re-aggregating the grouped data corresponding to the first aggregation result ID and the second aggregation result ID, and updating the corresponding aggregation results.
In the above technical solution, when the obtained detail data to be updated is modified detail data, first, a first mapping dictionary table is queried according to a detail identifier ID of the modified detail data to obtain a first aggregation result ID before updating corresponding to the modified detail data. And then, regrouping the modified detailed data, if the modified detailed data is distributed into one of the original m groups, inquiring a second mapping dictionary table according to the group to obtain a second aggregation result ID corresponding to the modified detailed data after updating.
In some optional embodiments, after re-aggregating the packet data corresponding to the first aggregation result ID and the second aggregation result ID, and updating the corresponding aggregation results, the method further includes:
judging whether the first aggregation result ID is different from the second aggregation result ID:
and if the first aggregation result ID is different from the second aggregation result ID, modifying the first aggregation result ID corresponding to the detail identification ID for modifying the detail data in the first mapping dictionary table into the second aggregation result ID.
In the above technical solution, after the aggregation result corresponding to the first aggregation result ID and the second aggregation result ID is updated, the first mapping dictionary table and the second mapping dictionary table also need to be updated synchronously, and the updated first mapping dictionary table and the updated second mapping dictionary table can be used for next data update. In this embodiment, if the first aggregation result ID is the same as the second aggregation result ID, that is, the updated group of the modified detailed data is the same as the group before updating, at this time, both the first mapping dictionary table and the second mapping dictionary table do not need to be modified; if the first aggregation result ID is different from the second aggregation result ID, that is, the modified detail data is allocated to another group of the m groups after being regrouped, at this time, only the first aggregation result ID corresponding to the detail identification ID of the modified detail data in the first mapping dictionary table needs to be modified to the second aggregation result ID.
In some optional embodiments, after determining whether the modification detail data is allocated to a packet of the m packets, the method further comprises:
if the modified detailed data is not distributed to one of the m groups, adding a mapping relation between a first newly added group and a first newly added aggregation result ID in a second mapping dictionary table;
re-aggregating the grouped data corresponding to the first aggregation result ID, and updating the corresponding aggregation result;
aggregating the grouped data corresponding to the first newly added group, and newly adding a corresponding aggregation result;
and modifying the first aggregation result ID corresponding to the detail identification ID for modifying the detail data in the first mapping dictionary table into the first newly-added aggregation result ID.
In the above technical solution, when the modified detail data is re-grouped to a new group other than the m groups, on one hand, the first mapping dictionary table is queried according to the detail identifier ID of the modified detail data to obtain the first aggregation result ID before updating corresponding to the modified detail data. On the other hand, a first newly added packet and a corresponding first newly added aggregation result ID need to be added, the packet data corresponding to the first newly added packet is aggregated, and a corresponding aggregation result is added, so that the updating of the aggregation result is completed.
In this embodiment, the first mapping dictionary table and the second mapping dictionary table need to be updated synchronously, and the updated first mapping dictionary table and second mapping dictionary table may be used for next data update. In this embodiment, the synchronously updating the first mapping dictionary table and the second mapping dictionary table includes: and adding a mapping relation between the first newly added group and the first newly added aggregation result ID in the second mapping dictionary table, and modifying the first aggregation result ID corresponding to the detail identifier ID for modifying the detail data in the first mapping dictionary table into the first newly added aggregation result ID.
In some optional embodiments, after determining that the detail data to be updated is the new detail data, the method further includes:
grouping the newly added detail data by using the aggregation condition, and judging whether the newly added detail data is distributed to a certain group in the m groups:
if the newly added detailed data is distributed to a certain group of the m groups, inquiring a second mapping dictionary table according to the group to which the newly added detailed data is distributed to obtain a corresponding third aggregation result ID;
re-aggregating the grouped data corresponding to the third aggregation result ID, and updating the corresponding aggregation result; and adding the mapping relation between newly added detailed data and the third aggregation result ID in the first mapping dictionary table.
In the above technical solution, when the obtained detail data to be updated is new detail data, the new detail data is first regrouped, and if the new detail data is allocated to one of the original m groups, the second mapping dictionary table is queried according to the group to obtain a third aggregation result ID corresponding to the updated new detail data.
In this embodiment, the first mapping dictionary table and the second mapping dictionary table need to be updated synchronously, and the updated first mapping dictionary table and second mapping dictionary table may be used for next data update. In this embodiment, the synchronously updating the first mapping dictionary table and the second mapping dictionary table includes: and adding the mapping relation between newly added detailed data and the third aggregation result ID in the first mapping dictionary table.
In some optional embodiments, after determining whether the new detail data is allocated to a certain packet of the m packets, the method further includes:
if the newly added detailed data are not distributed to one of the m groups, adding a mapping relation between a second newly added group and a second newly added aggregation result ID in a second mapping dictionary table;
aggregating the grouped data corresponding to the second newly added group, and newly adding a corresponding aggregation result;
and adding the mapping relation between the newly added detailed data and the second newly added aggregation result ID in the first mapping dictionary table.
In the above technical solution, when the newly added detailed data is re-grouped to a new group other than the m groups, a second newly added group and a second newly added aggregation result ID corresponding to the second newly added group need to be added, and the packet data corresponding to the second newly added group is aggregated, and a corresponding aggregation result is added, so that the update of the aggregation result is completed.
In this embodiment, the first mapping dictionary table and the second mapping dictionary table also need to be updated synchronously, and the updated first mapping dictionary table and the updated second mapping dictionary table can be used for next data update. In this embodiment, the synchronously updating the first mapping dictionary table and the second mapping dictionary table includes: and adding the mapping relation between the newly added group and the newly added aggregation result ID in the second mapping dictionary table, and adding the mapping relation between the newly added detailed data and the newly added aggregation result ID in the first mapping dictionary table.
In some optional embodiments, the aggregation condition is implemented based on an encryption algorithm, or string concatenation according to a preset condition, or according to at least one judgment statement.
In the above technical scheme, the polymerization conditions include, but are not limited to, the following three implementation forms:
firstly, splicing i attributes according to a fixed sequence combined character string to form a column;
secondly, splicing i attributes according to a fixed sequence combined character string, then encrypting by adopting an encryption algorithm, and taking the i encrypted attributes as a column;
and thirdly, respectively taking the i attributes as independent columns and combining the i judgment statements to respectively judge whether the detail data meets the i conditions, and distributing the detail data to the group only when the detail data meets the i conditions of the group at the same time, thereby realizing the grouping of the detail data.
An embodiment of the present application provides an aggregated data updating apparatus based on a mapping dictionary table, including:
the grouping module is used for grouping the n detailed data by using the aggregation condition to obtain grouped data corresponding to the m groups; wherein n and m are positive integers greater than 0;
the aggregation module is used for respectively aggregating each grouped data to obtain m aggregation results;
the dictionary table generation module is used for generating a first mapping dictionary table according to the mapping relation between the n detailed data and the m aggregation results; generating a second mapping dictionary table according to the mapping relation between the m groups and the m aggregation results;
and the updating module is used for realizing the aggregation updating of the grouped data corresponding to the updated data related group based on the query of the first mapping dictionary table and the second mapping dictionary table when the data is updated.
Wherein the detail data includes: the detail identifier ID and preset values of k attributes;
the polymerization condition is i attributes in the k attributes, wherein k and i are positive integers larger than 0, and k is larger than or equal to i and larger than 0;
at least one attribute in any two of the m groups has a different value;
each aggregation result corresponds to an aggregation result ID;
the first mapping dictionary table comprises a mapping relation between n detailed identification IDs and m aggregation result IDs;
the second mapping dictionary table includes mapping relationships of m packets and m aggregation result IDs.
The k attributes include: a timestamp and a service time; the timestamp data is the time of updating the detail data at last, and the service time data is the time of creating the detail data.
In some optional embodiments, the update module comprises:
the acquisition module is used for acquiring detailed data to be updated;
a judging module, configured to judge whether the timestamp data of the detail data to be updated and the service time data are consistent: if yes, determining the detail data to be updated as new detail data; if not, determining the detail data to be updated as modified detail data.
In some optional embodiments, the update module further comprises:
a modification processing module to: inquiring the first mapping dictionary table according to the detail identification ID of the modified detail data to obtain a corresponding first aggregation result ID;
regrouping the modified detail data using the aggregation condition, and determining whether the modified detail data is allocated to a packet of the m packets:
if the modification detail data is distributed to one of the m groups, querying the second mapping dictionary table according to the group redistributed by the modification detail data to obtain a corresponding second aggregation result ID;
and respectively re-aggregating the grouped data corresponding to the first aggregation result ID and the second aggregation result ID, and updating the corresponding aggregation results.
In some optional embodiments, the modification processing module is further configured to:
judging whether the first aggregation result ID is different from the second aggregation result ID:
and if the first aggregation result ID is different from the second aggregation result ID, modifying the first aggregation result ID corresponding to the detail identifier ID of the modified detail data in the first mapping dictionary table into the second aggregation result ID.
In some optional embodiments, the modification processing module is further configured to:
if the modified detailed data is not distributed to one of the m groups, adding a mapping relation between a first newly added group and a first newly added aggregation result ID in the second mapping dictionary table;
re-aggregating the grouped data corresponding to the first aggregation result ID, and updating the corresponding aggregation result;
aggregating the grouped data corresponding to the first newly added group, and newly adding a corresponding aggregation result;
and modifying the first aggregation result ID corresponding to the detail identification ID of the modified detail data in the first mapping dictionary table into the first newly-added aggregation result ID.
In some optional embodiments, the update module further comprises:
a newly-added processing module used for:
grouping the newly added detail data by using the aggregation condition, and judging whether the newly added detail data is distributed to a certain group in the m groups:
if the newly added detailed data is distributed to one of the m groups, inquiring the second mapping dictionary table according to the group to which the newly added detailed data is distributed to obtain a corresponding third aggregation result ID;
re-aggregating the grouped data corresponding to the third aggregation result ID, and updating the corresponding aggregation result; and newly adding the mapping relation between the newly added detailed data and the third aggregation result ID in the first mapping dictionary table.
In some optional embodiments, the newly added processing module is further configured to:
if the newly added detail data is not distributed to one of the m groups, adding a mapping relation between a second newly added group and a second newly added aggregation result ID in the second mapping dictionary table;
aggregating the grouped data corresponding to the second newly added group, and newly adding a corresponding aggregation result;
and newly adding the mapping relation between the newly added detailed data and the second newly added aggregation result ID in the first mapping dictionary table.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a flowchart illustrating steps of an aggregated data updating method based on a mapping dictionary table according to an embodiment of the present application;
FIG. 2 is an original representation provided by an embodiment of the present application;
FIG. 3 is a diagram of a first mapping dictionary representation generated according to detail data in an original table according to an embodiment of the present application;
FIG. 4 is a diagram of a second mapping dictionary representation generated according to detail data in an original table according to an embodiment of the present application;
fig. 5 is a table diagram after detailed data is added or modified in an original table according to an embodiment of the present application;
FIG. 6 is a diagram illustrating an updated first mapping dictionary representation provided by an embodiment of the present application;
FIG. 7 is a diagram representing an updated second mapping dictionary according to an embodiment of the present application;
FIG. 8 is a schematic diagram of an implementation of a polymerization condition provided in an embodiment of the present application;
FIG. 9 is a functional block diagram of an aggregated data updating apparatus based on a mapping dictionary table according to an embodiment of the present application;
fig. 10 is a functional block diagram of an update module according to an embodiment of the present application.
Icon: the system comprises a 1-grouping module, a 2-aggregation module, a 3-dictionary table generation module, a 4-updating module, a 41-acquisition module, a 42-judgment module, a 43-modification processing module and a 44-newly-added processing module.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Referring to fig. 1, fig. 1 is a flowchart illustrating steps of an aggregated data updating method based on a mapping dictionary table according to an embodiment of the present application, including:
step 100, grouping the n detailed data by using aggregation conditions to obtain grouped data corresponding to m groups; wherein n and m are positive integers greater than 0;
step 200, respectively polymerizing each grouped data to obtain m polymerization results;
step 300, generating a first mapping dictionary table according to the mapping relation between the n detailed data and the m aggregation results;
step 400, generating a second mapping dictionary table according to the mapping relation between the m groups and the m aggregation results;
and 500, when the data is updated, realizing the aggregation update of the grouped data corresponding to the updated data related group based on the query of the first mapping dictionary table and the second mapping dictionary table.
In the embodiment of the application, when all the detail data are grouped and aggregated, a first mapping dictionary table is generated according to the mapping relation between the detail data and the aggregation result, and a second mapping dictionary table is generated according to the mapping relation between the grouping and the aggregation result. And then, if the detail data is updated, the newly added detail data or the historical detail data is modified, finding out a related group of which the aggregation result is changed due to the updated data by inquiring the first mapping dictionary table and the second mapping dictionary table, and re-aggregating the grouped data corresponding to the group to obtain a new aggregation result. Therefore, by applying the updating method provided by the application, grouping and aggregation of all data can be avoided, resource occupation of a server is reduced, time for updating the data is shortened, and data omission is further avoided as the first mapping dictionary table and the second mapping dictionary table comprising all data are inquired during updating.
In some alternative embodiments, the detailed data includes: and the detail identifier ID and preset values of k attributes. The aggregation condition is i attributes in the k attributes, wherein k and i are positive integers larger than 0, and k is larger than or equal to i and larger than 0; any two of the m packets have at least one attribute with a different value. Each aggregation result corresponds to an aggregation result ID. The first mapping dictionary table includes a mapping relationship of n detailed identification IDs and m aggregation result IDs. The second mapping dictionary table includes mappings of m packets to m aggregation result IDs.
Each group corresponds to an aggregation condition, and each group corresponds to an aggregation result; the m groups in the second mapping dictionary table may include a minimum granularity group obtained by combining all data values included in the i attributes; the method can also comprise a minimum granularity group and a large granularity group obtained by data values contained in j attributes in i attributes, wherein j is a positive integer larger than 0, and i > j >0; other groups set according to the needs of the user may also be included, which are not limited herein.
In this embodiment, each piece of detail data has a unique detail identifier ID and preset values of k attributes, an aggregation condition for performing grouping aggregation on all the piece of detail data is i attributes of the k attributes, each aggregation result corresponds to one aggregation result ID, the first mapping dictionary table is a mapping relationship between all the detail identifier IDs and all the aggregation result IDs, and the second mapping dictionary table is a one-to-one mapping relationship between a group and an aggregation result ID. If the value of the attribute of any detail data changes, the corresponding aggregation result ID can be obtained by looking up the first mapping dictionary table according to the detail identifier ID of the detail data, so that the aggregation result corresponding to the aggregation result ID is updated correspondingly. If any detailed data is grouped into another group after being updated, the corresponding aggregation result ID can be obtained by querying the second mapping dictionary table according to the redistributed group, and therefore the aggregation result corresponding to the aggregation result ID is updated correspondingly; each aggregation result ID and aggregation result are in one-to-one correspondence, and there are as many aggregation results as there are aggregation result IDs.
In a specific embodiment, each detail datum has a unique detail identification ID, and 8 attributes including timestamp, patient ID, hospital number, business time, department, drug, dose and cost, as shown in the original representation of the intent of fig. 2. The first mapping dictionary representation is intended to mean that as shown in fig. 3, each detail ID corresponds to one aggregation result ID, and since there may be multiple detail data in one packet, there are cases where multiple detail IDs correspond to one aggregation result ID, for example, the detail IDs "1234567894" and "1234567895" in the table both correspond to the aggregation result ID "0987654328". The second mapping dictionary is intended to be as shown in fig. 4, the aggregation condition is aggregation of charge data grouped according to 3 attributes of department, medicine and business time, for example, the aggregation result ID corresponding to "medicine AA charge aggregation in 2021 year by department a" in the table is "0987654321", each group and each aggregation result ID are in one-to-one correspondence, and there are as many groups as there are aggregation result IDs.
In some alternative embodiments, the k attributes include: a timestamp and a service time; the timestamp data is the time of updating the detail data at last, and the service time data is the time of creating the detail data;
the method further comprises the following steps:
step 600, acquiring detail data to be updated;
step 700, judging whether the timestamp data of the detail data to be updated is consistent with the service time data:
if yes, determining the detail data to be updated as the newly added detail data;
if not, determining the detail data to be updated as the modification detail data.
In the embodiment of the application, the k attributes of the detail data at least include two attributes of a timestamp and a service time, the timestamp data is the time of updating the detail data at last, and the service time data is the time of creating the detail data. When a certain detail data is updated, if the time stamp data of the detail data is inconsistent with the service time data, namely the time displayed by the time stamp of the detail data is behind the time displayed by the service time, the detail data is considered to be modified, and the detail data is determined to be modified; and if the timestamp data of the detail data is consistent with the service time data, the detail data is regarded as newly added data, and the newly added detail data is determined. And dividing the detail data area to be updated into newly-added detail data or modified detail data so as to realize data aggregation updating under two conditions through subsequent different processing flows.
In the first case, the detail data to be updated is modified detail data, and the subsequent processing flow for the modified detail data includes:
step 810, inquiring a first mapping dictionary table according to the detail identification ID of the modified detail data to obtain a corresponding first aggregation result ID;
step 820, regrouping the modified detail data by using the aggregation condition, and judging whether the modified detail data is distributed to a certain packet in the m packets:
step 831, if the modified detailed data is distributed to one of the m groups, querying a second mapping dictionary table according to the group redistributed by the modified detailed data to obtain a corresponding second aggregation result ID; and respectively re-aggregating the grouped data corresponding to the first aggregation result ID and the second aggregation result ID, and updating the corresponding aggregation results.
In the embodiment of the application, when the obtained detail data to be updated is modification detail data, firstly, a first mapping dictionary table is queried according to a detail identifier ID of the modification detail data to obtain a first aggregation result ID before updating corresponding to the modification detail data. And then, regrouping the modified detailed data, if the modified detailed data is distributed into one of the original m groups, inquiring a second mapping dictionary table according to the group to obtain a second aggregation result ID corresponding to the modified detailed data after updating.
For example, the original table is modified in fig. 5, with one modification: the "department" attribute of the detail data whose detail identification ID is "1234567891" is modified, and the time stamp data is updated at the same time. The first mapping dictionary table, such as fig. 3, is queried according to the detailed identification ID "1234567891" to find the first aggregation result ID "0987654322". The detailed data whose detailed ID is "1234567891" is regrouped and assigned to the group "department B2021 year medicine BB fee aggregation", and the second aggregation result ID "0987654326" is found by referring to the second mapping dictionary table shown in fig. 4 from the group "department B2021 year medicine BB fee aggregation". Then, the packet data corresponding to the first aggregation result ID "0987654322" and the second aggregation result ID "0987654326" are re-aggregated, respectively, and the aggregation result is updated.
In some optional embodiments, after re-aggregating the packet data corresponding to the first aggregation result ID and the second aggregation result ID, and updating the corresponding aggregation results, the method further includes:
judging whether the first aggregation result ID is different from the second aggregation result ID:
and if the first aggregation result ID is different from the second aggregation result ID, modifying the first aggregation result ID corresponding to the detail identification ID of the modified detail data in the first mapping dictionary table into the second aggregation result ID.
In this embodiment of the present application, after the aggregation result corresponding to the first aggregation result ID and the second aggregation result ID is updated, the first mapping dictionary table and the second mapping dictionary table also need to be updated synchronously, and the updated first mapping dictionary table and the updated second mapping dictionary table may be used for next data update. In this embodiment, if the first aggregation result ID is the same as the second aggregation result ID, that is, the updated group of the modified detail data is the same as the group before the update, at this time, both the first mapping dictionary table and the second mapping dictionary table do not need to be modified; if the first aggregation result ID is different from the second aggregation result ID, that is, the modified detail data is allocated to another group of the m groups after being regrouped, at this time, only the first aggregation result ID corresponding to the detail identification ID of the modified detail data in the first mapping dictionary table needs to be modified to the second aggregation result ID.
As shown in fig. 6, since the first aggregation result ID "0987654322" does not coincide with the second aggregation result ID "0987654326", the detail data having the detail identification ID "1234567891" corresponds to the first aggregation result ID "0987654322" before updating, and after grouping and aggregation are performed again, the detail data having the detail identification ID "1234567891" is updated to the second aggregation result ID "0987654326" in the first mapping dictionary table.
In some optional embodiments, after determining whether the modification detail data is allocated to a certain packet of the m packets in step 820, the method further includes:
step 832, if the modified detailed data is not distributed to one of the m groups, adding a mapping relation between the first newly added group and the first newly added aggregation result ID in the second mapping dictionary table; re-aggregating the grouped data corresponding to the first aggregation result ID, and updating the corresponding aggregation result; aggregating the grouped data corresponding to the first newly added group, and newly adding a corresponding aggregation result; and modifying the first aggregation result ID corresponding to the detail identification ID for modifying the detail data in the first mapping dictionary table into the first newly-added aggregation result ID.
In the embodiment of the present application, when the modified detail data is re-grouped to a new group other than m groups, on one hand, the first mapping dictionary table is queried according to the detail identifier ID of the modified detail data to obtain the first aggregation result ID before updating corresponding to the modified detail data. On the other hand, a first newly added group and a corresponding first newly added aggregation result ID are required to be added, the grouped data corresponding to the first newly added group is aggregated, and a corresponding aggregation result is added, so that the updating of the aggregation result is completed.
In this embodiment, the first mapping dictionary table and the second mapping dictionary table need to be updated synchronously, and the updated first mapping dictionary table and second mapping dictionary table may be used for next data update. In this embodiment, the synchronously updating the first mapping dictionary table and the second mapping dictionary table includes: and adding a mapping relation between the first newly added group and the first newly added aggregation result ID in the second mapping dictionary table, and modifying the first aggregation result ID corresponding to the detail identifier ID for modifying the detail data in the first mapping dictionary table into the first newly added aggregation result ID.
For example, the original table is modified in fig. 5, with one modification: the "department" and "medicine" attributes of the detail data whose detail identification ID is "1234567894" are modified, and the time stamp data is updated at the same time. The first mapping dictionary table, such as fig. 3, is queried according to the detailed identification ID "1234567894" to find the first aggregation result ID "0987654328". After the detail data whose detail ID is "1234567894" is regrouped, the same packet as the modified detail data whose detail ID is "1234567894" is not found in the second mapping dictionary table before updating. Therefore, a first newly added group of "department C2022 year medicine AA cost aggregation" and a corresponding first newly added aggregation result ID "0987654329" need to be added, packet data corresponding to the first aggregation result ID "0987654328" is re-aggregated after excluding detailed data whose detailed identifier ID is "1234567894", and an aggregation result is updated, and packet data corresponding to the first newly added aggregation result ID "0987654329" is aggregated, and a corresponding aggregation result is added. And finishing updating the aggregation result.
And meanwhile, updating the first mapping dictionary table and the second mapping dictionary table. As shown in fig. 7, in the second mapping dictionary table, a mapping relationship between a first new group of "department C2022 year drug AA fee aggregation" and a corresponding first new aggregation result ID "0987654329" is added. And in the first mapping dictionary table as shown in fig. 6, the aggregation result ID corresponding to the detail identification ID "1234567894" is modified to the first newly added aggregation result ID "0987654329". And completing synchronous updating of the first mapping dictionary table and the second mapping dictionary table.
In the second case, the detail data to be updated is newly added detail data, and the subsequent processing flow for the newly added detail data includes:
step 910, grouping the newly added detail data by using aggregation conditions, and determining whether the newly added detail data is allocated to a certain one of the m groups:
step 921, if the newly added detail data is allocated to a certain one of the m groups, querying the second mapping dictionary table according to the group to which the newly added detail data is allocated, and obtaining a corresponding third aggregation result ID; re-aggregating the grouped data corresponding to the third aggregation result ID, and updating the corresponding aggregation result; and adding the mapping relation between newly added detailed data and the third aggregation result ID in the first mapping dictionary table.
In the embodiment of the application, when the obtained detail data to be updated is new detail data, the new detail data is firstly grouped by using aggregation conditions, if the new detail data is distributed to one of the original m groups, the second mapping dictionary table is inquired according to the group, and a third aggregation result ID corresponding to the new detail data after grouping is obtained.
The embodiment also needs to update the first mapping dictionary table synchronously, and the updated first mapping dictionary table can be used for next data update. In this embodiment, the synchronously updating the first mapping dictionary table includes: and adding the mapping relation between newly added detailed data and the third aggregation result ID in the first mapping dictionary table.
For example, new detail data with a detail identifier ID of "1234567896" is added in fig. 5, the new detail data is grouped by using the aggregation condition, the new detail data is assigned to a group of "department a 2022 year drug BB fee aggregation", a corresponding third aggregation result ID "0987654324" is queried in the second mapping dictionary table according to the group of "department a 2022 year drug BB fee aggregation", the grouped data corresponding to the third aggregation result ID "0987654324" is aggregated again, and the corresponding aggregation result is updated. And synchronously updating the first mapping dictionary table, as shown in fig. 6, adding the mapping relationship between the detail identifier ID "1234567896" and the third aggregation result ID "0987654324" of the newly added detail data in the first mapping dictionary table.
In some optional embodiments, after determining whether the new detail data is allocated to one of the m packets in step 910, the method further includes:
step 922, if the newly added detail data is not distributed to one of the m groups, adding a mapping relation between a second newly added group and a second newly added aggregation result ID in a second mapping dictionary table; aggregating the grouped data corresponding to the second newly added group, and newly adding a corresponding aggregation result; and adding the mapping relation between the newly added detailed data and the second newly added aggregation result ID in the first mapping dictionary table.
In the embodiment of the application, when the newly added detailed data is grouped and allocated to a new group other than the m groups by using the aggregation condition, a second newly added group and a corresponding second newly added aggregation result ID thereof need to be added, the grouped data corresponding to the second newly added group is aggregated, and a corresponding aggregation result is added. Updating of the aggregated result is completed.
In this embodiment, the first mapping dictionary table and the second mapping dictionary table need to be updated synchronously, and the updated first mapping dictionary table and second mapping dictionary table may be used for next data update. In this embodiment, the synchronously updating the first mapping dictionary table and the second mapping dictionary table includes: and adding the mapping relation between the newly added grouping and the newly added aggregation result ID in the second mapping dictionary table, and adding the mapping relation between the newly added detailed data and the newly added aggregation result ID in the first mapping dictionary table.
In some optional embodiments, the aggregation condition is implemented based on an encryption operation using an encryption algorithm, or string concatenation according to a preset condition, or according to at least one judgment statement.
In the above technical scheme, the polymerization conditions include, but are not limited to, the following three implementation forms:
first, as shown in fig. 3 and 7, i attributes are spliced according to a fixed order combination string to form a column;
secondly, splicing i attributes according to a fixed sequence combined character string, then encrypting by adopting an encryption algorithm, and taking the i encrypted attributes as a column;
thirdly, as shown in fig. 8, i attributes are respectively used as separate columns and are combined with i judgment statements to respectively judge whether the detail data satisfies i conditions, and the detail data is distributed to the group only when the detail data satisfies the i conditions of the group at the same time, thereby realizing the grouping of the detail data.
Referring to fig. 9, fig. 9 is a functional block diagram of an aggregated data updating apparatus based on a mapping dictionary table according to an embodiment of the present disclosure, including a grouping module 1, an aggregation module 2, a dictionary table generating module 3, and an updating module 4. The grouping module 1 is configured to group the n pieces of detailed data by using an aggregation condition to obtain grouped data corresponding to m pieces of groups; wherein n and m are both positive integers greater than 0; the aggregation module 2 is used for respectively aggregating each grouped data to obtain m aggregation results; the dictionary table generating module 3 is configured to generate a first mapping dictionary table according to the mapping relationship between the n detailed data and the m aggregation results; generating a second mapping dictionary table according to the mapping relation between the m groups and the m aggregation results; and the updating module 4 is used for realizing the aggregation updating of the grouped data corresponding to the updated data related group based on the query of the first mapping dictionary table and the second mapping dictionary table when the data is updated.
Wherein the detail data includes: the detail identifier ID and the preset values of k attributes. The aggregation condition is i attributes in the k attributes, wherein k and i are positive integers larger than 0, and k is larger than or equal to i and larger than 0. Any two of the m packets have at least one attribute with a different value. Each aggregation result corresponds to an aggregation result ID. The first mapping dictionary table includes mapping relationships of n detailed identification IDs and m aggregation result IDs. The second mapping dictionary table includes mapping relationships of m packets and m aggregation result IDs. The k attributes include: a timestamp and a service time; the timestamp data is the time of updating the detail data at last, and the service time data is the time of creating the detail data.
Referring to fig. 10, fig. 10 is a functional block diagram of an update module 4 according to an embodiment of the present disclosure, where the update module 4 includes an obtaining module 41 and a determining module 42. The obtaining module 41 is configured to obtain detail data to be updated. A determining module 42, configured to determine whether the timestamp data of the detail data to be updated and the service time data are consistent: if yes, determining the detail data to be updated as new detail data; if not, determining the detail data to be updated as modified detail data.
In some alternative embodiments, the updating module 4 further comprises a modification processing module 43. A modification processing module 43, configured to: inquiring the first mapping dictionary table according to the detail identification ID of the modified detail data to obtain a corresponding first aggregation result ID; regrouping the modified detail data using the aggregation condition, and determining whether the modified detail data is allocated to a packet of the m packets: if the modification detail data is distributed to one of the m groups, querying the second mapping dictionary table according to the group redistributed by the modification detail data to obtain a corresponding second aggregation result ID; and respectively re-aggregating the grouped data corresponding to the first aggregation result ID and the second aggregation result ID, and updating the corresponding aggregation results.
In some optional embodiments, the modification processing module 43 is further configured to: judging whether the first aggregation result ID is different from the second aggregation result ID: and if the first aggregation result ID is different from the second aggregation result ID, modifying the first aggregation result ID corresponding to the detail identification ID of the modified detail data in the first mapping dictionary table into the second aggregation result ID.
In some optional embodiments, the modification processing module 43 is further configured to: if the modified detailed data is not distributed to one of the m groups, adding a mapping relation between a first newly added group and a first newly added aggregation result ID in the second mapping dictionary table; re-aggregating the grouped data corresponding to the first aggregation result ID, and updating the corresponding aggregation result; aggregating the grouped data corresponding to the first newly added group, and newly adding a corresponding aggregation result; and modifying the first aggregation result ID corresponding to the detail identification ID of the modified detail data in the first mapping dictionary table into the first newly-added aggregation result ID.
In some optional embodiments, the update module 4 further includes a new addition processing module 44. A newly-added processing module 44, configured to: grouping the newly added detail data by using the aggregation condition, and judging whether the newly added detail data is distributed to a certain group in the m groups: if the newly added detailed data is distributed to one of the m groups, inquiring the second mapping dictionary table according to the group to which the newly added detailed data is distributed to obtain a corresponding third aggregation result ID; re-aggregating the grouped data corresponding to the third aggregation result ID, and updating the corresponding aggregation result; and newly adding the mapping relation between the newly added detailed data and the third aggregation result ID in the first mapping dictionary table.
In some optional embodiments, the newly added processing module 44 is further configured to: if the newly added detail data is not distributed to one of the m groups, adding a mapping relation between a second newly added group and a second newly added aggregation result ID in the second mapping dictionary table; aggregating the grouped data corresponding to the second newly added group, and newly adding a corresponding aggregation result; and newly adding the mapping relation between the newly added detail data and the second newly added aggregation result ID in the first mapping dictionary table.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, the division of the units into only one type of logical function may be implemented in other ways, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (10)

1. A method for updating aggregated data based on a mapping dictionary table is characterized by comprising the following steps:
grouping the n detailed data by using the aggregation condition to obtain grouped data corresponding to the m groups; wherein n and m are positive integers greater than 0;
respectively polymerizing each grouped data to obtain m polymerization results;
generating a first mapping dictionary table according to the mapping relation between the n detailed data and the m aggregation results;
generating a second mapping dictionary table according to the mapping relation between the m groups and the m aggregation results;
and when data is updated, realizing the aggregation update of the grouped data corresponding to the updated data related group based on the query of the first mapping dictionary table and the second mapping dictionary table.
2. The method of claim 1, wherein the detail data comprises: the detail identifier ID and the preset values of k attributes;
the aggregation condition is i attributes in the k attributes, wherein k and i are positive integers larger than 0, and k is larger than or equal to i and larger than 0;
any two groups of the m groups have at least one attribute with different values;
each aggregation result corresponds to an aggregation result ID;
the first mapping dictionary table comprises mapping relations of n detailed identification IDs and m aggregation result IDs;
the second mapping dictionary table includes mappings of m packets to m aggregation result IDs.
3. The method of claim 2, wherein the k attributes comprise: a timestamp and a service time; the timestamp data is the time of updating the detail data at last, and the service time data is the time of creating the detail data;
the method further comprises the following steps:
acquiring detail data to be updated;
judging whether the timestamp data of the detail data to be updated is consistent with the service time data:
if yes, determining the detail data to be updated as new detail data;
if not, determining the detail data to be updated as modified detail data.
4. The method of claim 3, wherein after determining that the detail data to be updated is modified detail data, the method further comprises:
inquiring the first mapping dictionary table according to the detail identification ID of the modified detail data to obtain a corresponding first aggregation result ID;
regrouping the modification detail data by using the aggregation condition, and judging whether the modification detail data is distributed to a certain packet in the m packets:
if the modification detail data is distributed to one of the m groups, querying the second mapping dictionary table according to the group redistributed by the modification detail data to obtain a corresponding second aggregation result ID;
and respectively re-aggregating the grouped data corresponding to the first aggregation result ID and the second aggregation result ID, and updating the corresponding aggregation results.
5. The method as claimed in claim 4, wherein said re-aggregating the packet data corresponding to the first aggregation result ID and the second aggregation result ID, respectively, and after updating the corresponding aggregation results, further comprising:
judging whether the first aggregation result ID is different from the second aggregation result ID:
and if the first aggregation result ID is different from the second aggregation result ID, modifying the first aggregation result ID corresponding to the detail identification ID of the modified detail data in the first mapping dictionary table into the second aggregation result ID.
6. The method of claim 4, wherein after determining whether the modification details data is allocated to a packet of the m packets, the method further comprises:
if the modification detail data are not distributed to one of the m groups, adding a mapping relation between a first newly added group and a first newly added aggregation result ID in the second mapping dictionary table;
re-aggregating the grouped data corresponding to the first aggregation result ID, and updating the corresponding aggregation result;
aggregating the grouped data corresponding to the first newly added group, and newly adding a corresponding aggregation result;
and modifying the first aggregation result ID corresponding to the detail identification ID of the modified detail data in the first mapping dictionary table into the first newly-added aggregation result ID.
7. The method of claim 3, wherein after determining that the detail data to be updated is new detail data, further comprising:
grouping the newly added detail data by using the aggregation condition, and judging whether the newly added detail data is distributed to a certain group in the m groups:
if the newly added detailed data is distributed to one of the m groups, inquiring the second mapping dictionary table according to the distributed group of the newly added detailed data to obtain a corresponding third aggregation result ID;
re-aggregating the grouped data corresponding to the third aggregation result ID, and updating the corresponding aggregation result; and newly adding the mapping relation between the newly added detailed data and the third aggregation result ID in the first mapping dictionary table.
8. The method of claim 7, wherein said determining whether said new detail data is assigned to one of said m packets further comprises:
if the newly added detail data is not distributed to one of the m groups, adding a mapping relation between a second newly added group and a second newly added aggregation result ID in the second mapping dictionary table;
aggregating the grouped data corresponding to the second newly added group, and newly adding a corresponding aggregation result;
and newly adding the mapping relation between the newly added detail data and the second newly added aggregation result ID in the first mapping dictionary table.
9. The method of claim 1, wherein the aggregation condition is implemented based on an encryption operation using an encryption algorithm, or string concatenation according to a preset condition, or according to at least one judgment statement.
10. An aggregated data updating apparatus based on a mapping dictionary table, comprising:
the grouping module is used for grouping the n detailed data by using the aggregation condition to obtain grouped data corresponding to the m groups; wherein n and m are positive integers greater than 0;
the aggregation module is used for respectively aggregating each grouped data to obtain m aggregation results;
a dictionary table generating module, configured to generate a first mapping dictionary table according to the mapping relationship between the n pieces of detail data and the m pieces of aggregation results; generating a second mapping dictionary table according to the mapping relation between the m groups and the m aggregation results;
and the updating module is used for realizing the aggregation updating of the grouped data corresponding to the updated data related group based on the query of the first mapping dictionary table and the second mapping dictionary table when the data is updated.
CN202211143940.7A 2022-09-20 2022-09-20 Aggregated data updating method and device based on mapping dictionary table Pending CN115470241A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211143940.7A CN115470241A (en) 2022-09-20 2022-09-20 Aggregated data updating method and device based on mapping dictionary table

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211143940.7A CN115470241A (en) 2022-09-20 2022-09-20 Aggregated data updating method and device based on mapping dictionary table

Publications (1)

Publication Number Publication Date
CN115470241A true CN115470241A (en) 2022-12-13

Family

ID=84333233

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211143940.7A Pending CN115470241A (en) 2022-09-20 2022-09-20 Aggregated data updating method and device based on mapping dictionary table

Country Status (1)

Country Link
CN (1) CN115470241A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116911269A (en) * 2023-06-05 2023-10-20 杭州观远数据有限公司 Method for modifying and splitting aggregated data into details

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116911269A (en) * 2023-06-05 2023-10-20 杭州观远数据有限公司 Method for modifying and splitting aggregated data into details
CN116911269B (en) * 2023-06-05 2024-02-20 杭州观远数据有限公司 Method for modifying and splitting aggregated data into details

Similar Documents

Publication Publication Date Title
CN109034809B (en) Block chain generation method and device, block chain node and storage medium
CN107622096B (en) Asynchronous multi-party data interaction method based on block chain system and storage medium
CN103559217B (en) A kind of massive multicast data towards isomeric data storehouse warehouse-in implementation method
WO2019144553A1 (en) Data storage method and apparatus, and storage medium
EP3637280B1 (en) Data storage method and device, and storage medium
CN105072160A (en) Serial number generating method and device, and a server
TW201800967A (en) Method and device for processing distributed streaming data
CN111353275B (en) Unique identifier of distributed system and generation method thereof
CN104636286A (en) Data access method and equipment
CN110310198B (en) Enterprise quota information management method, device, equipment and readable storage medium
CN105915369A (en) Configuration information management method and configuration information management device
CN100579133C (en) Method for generating ID symbol
CN110505306A (en) A kind of data ID generation method may specify digit
CN115470241A (en) Aggregated data updating method and device based on mapping dictionary table
CN110738038A (en) Contract text generation method, device, equipment and computer readable storage medium
CN108268344A (en) A kind of data processing method and device
CN108733802B (en) Identification code generation and analysis method and device, storage medium and electronic equipment
CN114185895A (en) Data import and export method and device, electronic equipment and storage medium
WO2020000486A1 (en) Data processing method and device
CN106993022B (en) Identification management method for cluster, identification server and corresponding system
CN111090803A (en) Data processing method and device, electronic equipment and storage medium
CN110807035A (en) Serial number generation method, device, equipment and storage medium
CN103051480B (en) The storage means of a kind of DN and DN storage device
CN104573088A (en) Document serial number generation method and device
CN113704245A (en) Database main key generation method, sub-table positioning method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination