CN112559495A - System for supporting multi-system label mapping to realize unified label management - Google Patents
System for supporting multi-system label mapping to realize unified label management Download PDFInfo
- Publication number
- CN112559495A CN112559495A CN202011543925.2A CN202011543925A CN112559495A CN 112559495 A CN112559495 A CN 112559495A CN 202011543925 A CN202011543925 A CN 202011543925A CN 112559495 A CN112559495 A CN 112559495A
- Authority
- CN
- China
- Prior art keywords
- label
- mapping
- data
- version
- module
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a system for realizing unified label management by supporting multi-system label mapping, which comprises the following steps: each department tag synchronization module, a tag mapping relationship establishing module, a tag mapping version management module, a tag mapping version state module, a tag mapping version copying module and a tag mapping import and export module. The system can support the data of different business departments of the data in different historical stages or continuously maintain the original business classification system, and the data uniformity is ensured in the company unified analysis dimension by a label mapping mode. The uniqueness and the particularity of historical data and business department data are kept, the uniformity of company data analysis is ensured, and the company data is reasonably analyzed and utilized. The method can help enterprises convert the business data of each department into company-level business data in a label mapping mode, supports all business data to be summarized and analyzed according to uniform dimensionality, and can solve the problem of unification of business labels in companies.
Description
Technical Field
The invention relates to the technical field of big data, in particular to a system for realizing unified label management by supporting multi-system label mapping.
Background
In the big data era, enterprises extract valuable information from large batch of data through the analysis of internal business data and internet public opinion data, help the enterprises to quickly grasp market changes, grasp business opportunities, improve enterprise profits and increase profits.
However, the development of big data in the enterprise is not achieved all at once, but a process of gradual accumulation is developed, the big data is developed with the development of business of the enterprise, and in the process of enterprise development, different departments accumulate and analyze the big data differently.
In the process of development of companies, business data is increased in an incremental manner. However, as the demands of different business departments of the same company are different, the business label systems required to be used in different periods are also different, and the best operation mode is to fully update all historical business data of the company according to the latest business label system. But this causes new problems: the new business report generated after the historical data is reprocessed has a difference in statistical analysis with the old business report generated before.
For enterprises, a company-level big data platform is built on a unified business analysis dimension and system. A set of label mapping system with company-level dimensionality is needed among analysis systems of different business departments of an enterprise, so that the analysis dimensionality at the company level is unified, and the uniqueness of data analysis of each business department can be considered; the new data can be analyzed in real time, and the historical data can be analyzed again through the label mapping relation to find a new service value point.
In view of the above, the following problems still exist:
1. the data sources are diversified, different data sources have different data access modes, and the data service attributes are different, so that the data are difficult to process in one mode, and the data processing process is complicated;
2. the department business is diversified, different department business data have different label systems, and the business is difficult to be analyzed and processed in a unified way;
3. the data updating frequency is different, some data are real-time data, some data are asynchronous data, some data are newly added, some data are used for correcting historical data, and different data updating frequencies and updating ranges can cause the data to have a plurality of versions, so that the difficulty is increased in data processing;
4. the service scenes of all departments are different, and the requirements are different, so that the update frequency of the sub-label systems of all the departments is different from that of the label systems of the company level.
Disclosure of Invention
The invention aims to solve the problems that in the enterprise development process, diversified entry labels of data channels are not uniform, data are dispersed in different departments and data are difficult to acquire, and the like, which troubles the digital transformation of a company, and provides a system for supporting multi-system label mapping to realize uniform label management.
The embodiment of the invention provides a system for realizing unified tag management by supporting multi-system tag mapping, which comprises the following steps:
each department tag synchronization module is used for synchronizing the service tag systems of each department to a company-level tag platform and managing the synchronized data according to different versions;
the system comprises a label mapping relation establishing module, a label mapping relation determining module and a label mapping relation judging module, wherein the label mapping relation establishing module is used for establishing a many-to-one mapping relation between labels of all departments and company-level labels;
the system comprises a label mapping version management module, a service label management module and a service label mapping version management module, wherein the label mapping version management module is used for supporting different service label systems to carry out version creation and modification in different time periods according to different data sources or different data generation times in the data processing process;
the label mapping version state module is used for setting the closing, activating and releasing states of the label mapping version for the label mapping version created and/or modified by the label mapping version management module;
the label mapping version copying module is used for copying the existing label mapping version;
and the label mapping import and export module is used for importing and exporting all label systems and mapping relations.
In one embodiment, further comprising: and the non-mapping data management module is used for marking the data without the mapping relation label.
In one embodiment, further comprising: and the data consumption processing module is used for supporting the analysis and processing of data according to different mapping versions according to sources and time periods.
In one embodiment, the establish label mapping relationship module is further configured to determine that all child nodes under the department label parent node are also mapped to the company label node when the department label parent node is mapped to the company label node.
In one embodiment, the department tag synchronization module includes:
the API gateway synchronization unit is used for synchronizing the data of each department service label system into the company-level label platform through the API interface;
the database synchronization unit is used for synchronously copying the service label system data stored in the database of each department to a company-level label platform;
and the HTTP synchronization unit is used for downloading and synchronously storing the service label system data uploaded to the cloud space by each department into the company-level label platform through the HTTP.
In one embodiment, the tag mapping version status module includes:
the label mapping version closing unit is used for setting the label mapping version to be in a closing state after the label mapping version is successfully established;
the label mapping version activating unit is used for activating the label mapping version in the closed state according to the first instruction, and the mapping relation takes effect;
and the tag mapping version release unit is used for releasing the tag mapping version in the activated state according to the second instruction, so that the current data is consumed and processed in real time.
Compared with the prior art, the system for realizing the unified label management by supporting the multi-system label mapping can support the data of different business departments of the data in different historical stages or continuously maintain the original business classification system, and the data uniformity is ensured in the unified analysis dimension of a company by the label mapping mode. The uniqueness and the particularity of historical data and business department data are kept, and the uniformity of company data analysis is ensured, so that the company data can be analyzed and utilized most reasonably.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:
FIG. 1 is a block diagram of a system supporting multi-system label mapping to implement unified label management provided in the present invention;
FIG. 2 is a flow chart of supporting multi-system label mapping to implement unified label management provided in the present invention;
FIG. 3 is a flow diagram of a department tag synchronization module provided in the present invention;
FIG. 4a is a flow chart of an API gateway synchronization unit provided in the present invention;
FIG. 4b is a flow chart of a database synchronization unit provided in the present invention;
fig. 4c is a flow chart of an HTTP protocol synchronization unit provided in the present invention;
FIG. 5 is a logic diagram of a department tag synchronization process provided in the present invention;
FIG. 6 is a schematic diagram of a tag mapping logical relationship provided in the present invention;
FIG. 7 is a schematic diagram of a tag mapping relationship provided in the present invention;
FIG. 8 is a schematic diagram of company-level tag mapping management provided in the present invention;
FIG. 9 is a schematic diagram of the import and export of a tag map version provided in the present invention;
FIG. 10 is a schematic diagram of the data portion consumption processing logic provided in the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In the development process of enterprises, along with the increase of business, various enterprise data can be brought along with the business. The granularity and scope of the analysis of such enterprise data is different in different stages of development. For an enterprise, both historical data precipitated during development and current business data are data wealth of the enterprise. The analysis and application of the data are indispensable contents of enterprises. However, data in different historical stages and data in different business departments cannot be completely re-divided and analyzed according to the latest company business system, so that the result of analyzing the same business data by using the latest label system is inconsistent with the past business report.
Referring to fig. 1, an embodiment of the present invention provides a system for supporting multi-system label mapping to implement unified label management, including:
each department tag synchronization module is used for synchronizing the service tag systems of each department to a company-level tag platform and managing the synchronized data according to different versions;
the system comprises a label mapping relation establishing module, a label mapping relation determining module and a label mapping relation judging module, wherein the label mapping relation establishing module is used for establishing a many-to-one mapping relation between labels of all departments and company-level labels;
the system comprises a label mapping version management module, a service label management module and a service label mapping version management module, wherein the label mapping version management module is used for supporting different service label systems to carry out version creation and modification in different time periods according to different data sources or different data generation times in the data processing process;
the label mapping version state module is used for setting the closing, activating and releasing states of the label mapping version for the label mapping version created and/or modified by the label mapping version management module;
the label mapping version copying module is used for copying the existing label mapping version;
and the label mapping import and export module is used for importing and exporting all label systems and mapping relations.
As shown in fig. 2, the data of various sources or business departments in the enterprise are collected and integrated, and then the mapping relationship version is read from the tag mapping relationship library according to the source and time range, and the integrated data is processed, so that the finally obtained business data is the business data of the company platform level. The part of data not only contains historical data labels of all service data, but also can support summary statistics according to company-level service labels, and can also perform service analysis according to the current latest service logic under the condition of not influencing the historical result of the previous service statistics. The greatest benefit is that the digitization transformation inside the enterprise is accelerated and promoted through the compatibility of technology and business.
The above modules are described in detail below:
1) the department tag synchronization module, as shown in fig. 3, synchronizes the original data of each business department (e.g., data of department 1, data of department 2, and data of … department N) into the company-level platform database, including the business data and the business tag, and also supports real-time update of the data after the data synchronization. The module can be used for collecting and managing all the synchronized data and providing a data base for later analysis and processing.
Referring to fig. 4a-4c, the data synchronization method mainly includes three methods:
the API gateway synchronization unit is used for synchronizing the data of each department service label system into the company-level label platform through the API interface; as shown in fig. 4 a.
The database synchronization unit is used for synchronously copying the service label system data stored in the database of each department to a company-level label platform; as shown in fig. 4 b.
The HTTP synchronization unit is used for downloading and synchronously storing the service label system data uploaded to the cloud space by each department into the company-level label platform through the HTTP; as shown in fig. 4 c.
In addition, referring to fig. 5, when synchronizing a new version of a tag, it is necessary to determine whether a new version of the tag mapping exists; if the new version exists, the new version is immediately synchronized, whether the synchronization is successful or not is checked, and when the synchronization is failed, prompt failure information can be given out and the synchronization is performed again; when the synchronization is successful, a new version may be created, with the status "closed". And when the prompt already exists in the latest version, the synchronization and creation are not needed.
2) The system comprises a label mapping relation establishing module, a label mapping relation determining module and a label mapping relation judging module, wherein the label mapping relation establishing module is used for establishing a many-to-one mapping relation between labels of all departments and company-level labels;
and establishing a label mapping relation between each business department label system and a company grade label system, wherein different business departments have independent label systems. The core function of the module is to support the mapping of the label systems of a plurality of business departments to a company-level label system according to the node mapping relationship, and the mapping relationship is a many-to-one mapping relationship. The labels of the business departments can only correspond to one company-level label system node, but one company-level label system node can correspond to a plurality of different business department label system nodes. For example, a parent node of a department label maps to a node of a company label, then all children nodes under the default department label parent node may also map to the company label node.
a) The plurality of business department tags correspond to a company level tag node;
b) one company level label node corresponds to business department labels of a plurality of different departments;
the mapping logic relationship is shown in fig. 6. The operation mode is as follows: two columns of attributes are added in a business department tag table and are used for storing tag ids and tag names of company-level platform tags. Updating the id and the name of the successfully mapped corresponding company-level platform tag in a business tag report, so that the mapping relation of the business tag is completed; the mapping is schematically shown in fig. 7.
3) The label mapping version management module: and establishing a mapping version management relation on the basis of the label mapping relation. The label mapping relation is a relation updated continuously and iteratively: some of the services need to update the content of the service label due to the change of the service, so that the label mapping relationship is changed; some of the mapping relations are changed due to the change of mapping logic; some of them are due to the change of mapping relation caused by the modification of data. In the business development of a company, there are various reasons for the change of the label mapping relationship.
However, such changes are caused by a lot of changes, and the contents of the changes are many (the label node multi-mapping relationship is also complicated), so that the mapping relationships need to be managed. By introducing the version management method, the changes can be managed in order, and the versions are distinguished according to the content causing the changes.
The label relation mapping version not only can facilitate the effective management of various data from a manager, but also can enhance the flexibility of the data from a user. The method provides the possibility of using a plurality of different mapping relations to process the business data in one environment.
Referring to fig. 8, a schematic diagram of company-level label mapping management is shown. The operation mode is as follows:
such as adding the attribute of the version, version id and version name to the tag database table. Matching all the service labels and the company-level labels with the version attributes, adding the version attributes for all the label relations, and managing and operating the label mapping relations according to the versions.
4) The tag mapping version status module: and the system is used for setting the closing, activation and release states of the label mapping version for the label mapping version created and/or modified by the label mapping version management module.
And the version management of the label mapping relation can ensure that the mapping relation is more ordered and organized. However, for the use of these relationships, various states are also required to be introduced for the differentiated management, otherwise all the version relationships can be used, which may cause confusion of data.
Therefore, the tag mapping version status module includes:
the label mapping version closing unit is used for setting the label mapping version to be in a closing state after the label mapping version is successfully established;
the label mapping version activating unit is used for activating the label mapping version in the closed state according to the first instruction, and the mapping relation takes effect;
a tag mapping version release unit, configured to release the tag mapping version in the activated state according to the second instruction, so as to implement real-time consumption processing on the current data
When the version is in a closed state, the version is invalid and can not be edited and modified;
when the version is in an activated state, the version is in an available state and can be edited and modified, but the version cannot be applied to a designed service environment and cannot be called by a service system;
when the version is in the release state, the version is in a state that can be called by the business system, and the business system can use the mapping relation. And different mapping versions of the publication can be used depending on the dimensions of time, data source, etc.
The operation mode is as follows:
for example, a version of an attribute may be added to a tag database table: version status. The version status has the values: closing, activating and releasing. And updating the state value of the version according to different operation types.
5) And the label mapping version copying module supports copying and modifying of the label mapping version. In order to facilitate creation and management of the tag mapping version, a copy function of the mapping version is necessary. The existing mapping version is copied, and then the adjustment is modified on the basis, so that the aim of creating a new mapping version is fulfilled.
The operation mode is as follows:
the version is copied by regenerating a new copy of all contents (including tag contents and mapping relations) of the copied tag version in the database and storing the new copy in the database, but the version name is different from the version id. For example, the original version is the V1.0 version, and the version created after copying may be the V1.1 version.
6) And the label mapping import and export module supports the import and export of the label mapping version. Referring to fig. 9, the mapping relationship is imported and exported to increase the channel for modifying the mapping relationship offline. And exporting the mapping relation, and after the mapping relation is modified online (outside the system), uploading the mapping relation by the system to achieve the purpose of modifying and adjusting the mapping relation.
The operation mode is as follows:
the export function: for example, all the tag contents and corresponding mapping relationships under the corresponding versions can be exported through a page export button function;
the import function: for example, the exported version content of the tag can be locally adjusted and modified, and the content of the tag-mapped version is imported through an import button of the page according to the same format. And judging whether the new version or the old version is covered according to the version id.
Further, the system further comprises: the mapping-free data management module is used for marking the data of which the mapping-free labels are identified; and the data consumption processing module is used for supporting the analysis and processing of data according to different mapping versions according to sources and time periods.
Wherein:
7) and the mapping-free data management module is used for managing the data without mapping relation in the mapping version. In the process of establishing the label mapping, labels without mapping relations need to be identified, otherwise, the situation of label mapping relation omission occurs. For the data without mapping relation, a mark is made in the system, so that the mapping relation maintenance personnel can conveniently identify and process the data.
The operation mode is as follows:
through database query, all the label contents without matching mapping relation can be queried. The label information without mapping relation is marked on the page, so that the user can pay attention to processing the data.
8) A data consumption processing module: and data consumption processing, which supports analyzing and processing data according to different mapping versions according to sources and time periods. In the process of data consumption, sometimes data re-consumption processing is required due to business requirements or partial mapping relation changes. If the data is re-consumed in full amount, time is consumed and resources are occupied. The system can support batch consumption of data according to different sources, time periods and the like through the mapping relation version. The service purpose can be achieved in the shortest time and the fastest and best way.
The operation mode is as follows:
referring to fig. 10, the data to be processed is queried according to the source and the time period; and inquiring the mapping relation of the corresponding service label according to the mapping version. Partial processing and updating can be carried out on a small amount of local data by combining the data to be processed with the corresponding service mapping labels, so that large-batch data processing is avoided, and computing resources are saved.
The system for realizing the unified label management by supporting the multi-system label mapping can support the data of different business departments of the data in different historical stages or continuously maintain the original business classification system, and ensures the data uniformity in the unified analysis dimension of a company by a label mapping mode. The uniqueness and the particularity of historical data and business department data are kept, and the uniformity of company data analysis is ensured, so that the company data can be analyzed and utilized most reasonably. The invention solves the problem of managing a large number of complicated labels of enterprises, and realizes the clear and systematic management of label information of the enterprises through the label information synchronization, the visual label mapping, the label version management and the non-mapping data management of the invention. The invention has the advantages of easy use and indirection, and can solve the complex label management scene in an enterprise.
Finally, it should be noted that the above embodiments are only used for illustrating the technical solutions of the present invention and are not limited. Although the present invention has been described in detail with reference to the embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (6)
1. A system for supporting multi-system label mapping to realize uniform label management is characterized by comprising:
each department tag synchronization module is used for synchronizing the service tag systems of each department to a company-level tag platform and managing the synchronized data according to different versions;
the system comprises a label mapping relation establishing module, a label mapping relation determining module and a label mapping relation judging module, wherein the label mapping relation establishing module is used for establishing a many-to-one mapping relation between labels of all departments and company-level labels;
the system comprises a label mapping version management module, a service label management module and a service label mapping version management module, wherein the label mapping version management module is used for supporting different service label systems to carry out version creation and modification in different time periods according to different data sources or different data generation times in the data processing process;
the label mapping version state module is used for setting the closing, activating and releasing states of the label mapping version for the label mapping version created and/or modified by the label mapping version management module;
the label mapping version copying module is used for copying the existing label mapping version;
and the label mapping import and export module is used for importing and exporting all label systems and mapping relations.
2. The system for supporting multi-system label mapping to realize unified label management according to claim 1, further comprising: and the non-mapping data management module is used for marking the data without the mapping relation label.
3. The system for supporting multi-system label mapping to realize unified label management according to claim 1, further comprising: and the data consumption processing module is used for supporting the analysis and processing of data according to different mapping versions according to sources and time periods.
4. The system for supporting multi-system label mapping to realize unified label management as claimed in claim 1, wherein the label mapping relationship establishing module is further configured to determine that all child nodes under a department label parent node are also mapped to a company label node when the department label parent node is mapped to the company label node.
5. The system of claim 1, wherein the department tag synchronization module comprises:
the API gateway synchronization unit is used for synchronizing the data of each department service label system into the company-level label platform through the API interface;
the database synchronization unit is used for synchronously copying the service label system data stored in the database of each department to a company-level label platform;
and the HTTP synchronization unit is used for downloading and synchronously storing the service label system data uploaded to the cloud space by each department into the company-level label platform through the HTTP.
6. The system of claim 1, wherein the tag mapping version status module comprises:
the label mapping version closing unit is used for setting the label mapping version to be in a closing state after the label mapping version is successfully established;
the label mapping version activating unit is used for activating the label mapping version in the closed state according to the first instruction, and the mapping relation takes effect;
and the tag mapping version release unit is used for releasing the tag mapping version in the activated state according to the second instruction, so that the current data is consumed and processed in real time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011543925.2A CN112559495A (en) | 2020-12-23 | 2020-12-23 | System for supporting multi-system label mapping to realize unified label management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011543925.2A CN112559495A (en) | 2020-12-23 | 2020-12-23 | System for supporting multi-system label mapping to realize unified label management |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112559495A true CN112559495A (en) | 2021-03-26 |
Family
ID=75031938
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011543925.2A Pending CN112559495A (en) | 2020-12-23 | 2020-12-23 | System for supporting multi-system label mapping to realize unified label management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112559495A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113343072A (en) * | 2021-05-07 | 2021-09-03 | 深圳市酷开网络科技股份有限公司 | Label query method, device, equipment and storage medium |
| CN115481108A (en) * | 2022-09-19 | 2022-12-16 | 北京三维天地科技股份有限公司 | Management method and system for same data among different departments |
-
2020
- 2020-12-23 CN CN202011543925.2A patent/CN112559495A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113343072A (en) * | 2021-05-07 | 2021-09-03 | 深圳市酷开网络科技股份有限公司 | Label query method, device, equipment and storage medium |
| CN115481108A (en) * | 2022-09-19 | 2022-12-16 | 北京三维天地科技股份有限公司 | Management method and system for same data among different departments |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111061817B (en) | Adaptive business construction system, method and computer readable medium | |
| US6574655B1 (en) | Associative management of multimedia assets and associated resources using multi-domain agent-based communication between heterogeneous peers | |
| CN103049271B (en) | The method and apparatus of the description document of automatic generation api interface | |
| US8196100B2 (en) | Content management system for computer software with dynamic traceability between code and design documents | |
| US10621211B2 (en) | Language tag management on international data storage | |
| US7072985B1 (en) | Method and apparatus for two phase structured message to tagged message translation | |
| CN112685433B (en) | Metadata updating method and device, electronic equipment and computer-readable storage medium | |
| TW200842627A (en) | Techniques to cross-synchronize data | |
| CN115934855B (en) | Full-link field-level blood margin analysis method, system, equipment and storage medium | |
| CN112559495A (en) | System for supporting multi-system label mapping to realize unified label management | |
| CN111143382A (en) | Data processing method, system and computer readable storage medium | |
| Ju et al. | An embedded Web server architecture for XML-based network management | |
| CN113886485A (en) | Data processing method, device, electronic equipment, system and storage medium | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| CN115293124A (en) | Automatic generation method and device for software engineering document | |
| CN111143310B (en) | Log recording method and device and readable storage medium | |
| US7058939B2 (en) | Automatic link maintenance to ensure referential integrity constraints | |
| CN113076343B (en) | Data query method, device, equipment and storage medium | |
| TW201448544A (en) | Message exchange via generic TLV generator and parser | |
| US7730105B2 (en) | Time sharing managing apparatus, document creating apparatus, document reading apparatus, time sharing managing method, document creating method, and document reading method | |
| CN109977516B (en) | Automatic modeling logic node processing method | |
| CN109144489B (en) | State data processing method based on Yang language model | |
| CN113742321A (en) | Data updating method and device | |
| CN111222015A (en) | Method for generating document by heterogeneous XML mapping | |
| CN110889013A (en) | Data association method, device, server and storage medium based on XML |
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 |