CN117742777B - Chip file version management system - Google Patents
Chip file version management system Download PDFInfo
- Publication number
- CN117742777B CN117742777B CN202410191221.5A CN202410191221A CN117742777B CN 117742777 B CN117742777 B CN 117742777B CN 202410191221 A CN202410191221 A CN 202410191221A CN 117742777 B CN117742777 B CN 117742777B
- Authority
- CN
- China
- Prior art keywords
- management tool
- version management
- chip
- version
- file
- 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.)
- Active
Links
- 238000013461 design Methods 0.000 claims description 17
- 238000013507 mapping Methods 0.000 claims description 16
- 230000004927 fusion Effects 0.000 claims description 6
- 230000002457 bidirectional effect Effects 0.000 claims description 5
- 238000011161 development Methods 0.000 abstract description 9
- 238000000034 method Methods 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Abstract
The invention relates to the technical field of chips, in particular to a chip file version management system, which comprises a first version management tool, a second version management tool and a synchronization module connected with the first version management tool and the second version management tool; the first version management tool comprises a first storage bin, and the second version management tool comprises a second storage bin; the first version management tool is used for receiving a chip file F submitted by a user, generating first version information corresponding to the chip file F, and storing the chip file F and the corresponding first version information into a first storage bin; the synchronization module is used for acquiring the chip file F and the corresponding first version information from the first version management tool and synchronizing the chip file F and the corresponding first version information to the second version management tool. The invention can automatically realize the synchronization of the chip files in different version management tools, and improves the efficiency of chip development.
Description
Technical Field
The invention relates to the technical field of chips, in particular to a chip file version management system.
Background
In the chip development process, a chip reference model needs to be developed based on a software language at a software side, and a chip design is constructed based on a hardware language at a hardware side. After the verification of the chip reference model is passed, joint simulation is performed based on the chip reference model and the chip design to verify the chip design. In this process, the related chip files need to be adjusted on the software side and the hardware side, but some chip files need to be kept synchronous on the hardware side and the software side, and the chip files have a plurality of different versions. Therefore, how to automatically realize the synchronization of the chip files at the software side and the hardware side, ensure the normal operation of the chip development process, and improve the chip development efficiency becomes a technical problem to be solved urgently.
Disclosure of Invention
The invention aims to provide a chip file version management system which can automatically realize the synchronization of chip files in different version management tools and improve the efficiency of chip development.
According to a first aspect of the present invention, there is provided a chip file version management system, including a first version management tool, a second version management tool, and a synchronization module connected to the first version management tool and the second version management tool;
The first version management tool comprises a first storage bin, and the second version management tool comprises a second storage bin;
The first version management tool is configured to receive a chip file F submitted by a user, generate first version information (FU, FN, FD) corresponding to the chip file F, and store the chip file F and the corresponding first version information (FU, FN, FD) in the first storage bin, where FU is a user identifier corresponding to the chip file F in the first version management tool, FN is a version number generated by the first version management tool based on the chip file F, FD is a reserved information segment of the first version management tool corresponding to the chip file F, and FD is initially empty;
The synchronization module is used for acquiring a chip file F and corresponding first version information (FU, FN, FD) from the first version management tool and submitting the chip file F and the corresponding first version information (FU, FN, FD) to the second version management tool;
The second version management tool generates corresponding second version information (EU, EN, ED) based on the received chip file F and the corresponding first version information (FU, FN, FD), wherein EU is a user identifier corresponding to the chip file F in the second version management tool, and eu=fu is set; EN is a version number generated by the second version management tool based on the chip file F; ED is a reserved information section of a second version management tool corresponding to the chip file F, ED=FN is set, and a version number mapping relation of the chip file F is established in the second version management tool; storing a chip file F and second version information (EU, EN, ED) into the second storage bin, and sending EN to the synchronization module;
the synchronization module is configured to send EN to the first version management tool, where the first version management tool sets fd=en, and a version number mapping relationship of the chip file F is established in the first version management tool.
Compared with the prior art, the invention has obvious advantages and beneficial effects. By means of the technical scheme, the chip file version management system provided by the invention can achieve quite technical progress and practicality, has wide industrial utilization value, and has at least the following beneficial effects:
According to the invention, the synchronization module is arranged between the first version management tool and the second version management tool, so that the chip files of the first version management tool and the second version management tool are synchronized, and the version number mapping relation of the chip files is respectively established in the first version management tool and the second version management tool based on the reserved information section, thereby automatically realizing the synchronization of the chip files in different version management tools, ensuring the normal operation of the chip development process and improving the chip development efficiency.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a chip file version management system according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to fall within the scope of the invention.
The embodiment of the invention provides a chip file version management system, which is shown in fig. 1 and comprises a first version management tool, a second version management tool and a synchronization module connected with the first version management tool and the second version management tool. The first version management tool includes a first storage bin and the second version management tool includes a second storage bin. As an embodiment, the first version management tool and the second version management tool are any two of perforce, git, svn, cvs version management tools. perforce, git, svn, cvs are all existing version management tools, and are not described here.
The first version management tool is configured to receive a chip file F submitted by a user, generate first version information (FU, FN, FD) corresponding to the chip file F, and store the chip file F and the corresponding first version information (FU, FN, FD) in the first storage bin, where FU is a user identifier corresponding to the chip file F in the first version management tool, and FN is a version number generated by the first version management tool based on the chip file F. FD is a reserved information segment of a first version management tool corresponding to the chip file F, FD is initially empty, the reserved information segment is specifically a description information segment or a label information segment, preferably, the reserved information segment is a label information segment, and the label information segment is more convenient for subsequent search and query.
The synchronization module is used for acquiring a chip file F and corresponding first version information (FU, FN, FD) from the first version management tool and submitting the chip file F and the corresponding first version information (FU, FN, FD) to the second version management tool. As an embodiment, the synchronization module may be implemented based on Jenkins, which is an open-source continuous integration tool that provides friendly operation interfaces.
The second version management tool generates corresponding second version information (EU, EN, ED) based on the received chip file F and the corresponding first version information (FU, FN, FD), wherein EU is a user identifier corresponding to the chip file F in the second version management tool, and eu=fu is set; EN is a version number generated by the second version management tool based on the chip file F; it should be noted that, each time the second version management tool receives a new chip file, a corresponding version number is generated for the chip file. ED is a reserved information section of a second version management tool corresponding to the chip file F, ED=FN is set, and a version number mapping relation of the chip file F is established in the second version management tool. It should be noted that, establishing the mapping relationship between the version number of the chip file F in the first version management tool and the version number of the chip file F in the second version management tool specifically refers to establishing the mapping relationship between the version number of the chip file F in the first version management tool and the version number of the chip file F in the second version management tool. And storing the chip file F and the second version information (EU, EN, ED) into the second storage bin, and sending the EN to the synchronization module.
The synchronization module is configured to send EN to the first version management tool, where the first version management tool sets fd=en, and a version number mapping relationship of the chip file F is established in the first version management tool.
It should be noted that, the version numbers are generated by different version management tools, for example, some version numbers are generated by random numbers, and some version management tools are generated by version number accumulation. The embodiment of the invention utilizes the reserved information segments of the first version management tool and the second version management tool, and stores the version numbers of the opposite sides in the reserved information segments, thereby establishing the version number mapping relation of the chip file F in the first version management tool and the second version management tool.
There are two ways of synchronizing between the first version management tool and the second version management tool, one is a one-way update and one is a two-way update. It should be noted that, the first version management tool and the second version management tool may have two synchronization modes at the same time, or may have only one of them.
As an embodiment, the synchronization manner between the first version management tool and the second version management tool is unidirectional update, the first storage bin is a master bin, the second storage bin is a slave bin, and the system can update the chip file only through the master bin. Specifically, the first version management tool is arranged on a hardware side, the second version management tool is arranged on a software side, the software side is used for developing a chip reference model based on a software language, the hardware side is used for developing a chip design based on a hardware language, the first storage bin and the second storage bin are used for storing a chip design configuration file, the hardware language can be vhdl, verilog, systemVerilog and the like, and the chip design configuration file specifically comprises chip function feature description information, chip composition module description information, bus description information among chip composition modules and register description information. The chip design configuration file can be specifically generated based on python language, perl language, ruby language, yaml, java language and the like, and when the chip design configuration file is used on a software side, the chip design configuration file can be obtained and converted into configuration information of a corresponding software language form on the software side. When the chip design configuration file is used by the hardware side, the chip design configuration file can be obtained and converted into configuration information of a hardware language form corresponding to the hardware side.
As an embodiment, the synchronization mode between the first version management tool and the second version management tool is bidirectional update, the first storage bin is a master bin, the second storage bin is a slave bin, the system updates the chip files through the master bin or the slave bin, it is to be noted that in the bidirectional update mode, the side of the master bin is responsible for generating all original chip files, responsible for most of chip file changes, and the slave bin only makes a small amount of modifications based on the files synchronized by the master bin. Specifically, the first version management tool is arranged at a software side, the second version management tool is arranged at a hardware side, the software side is used for developing a chip reference model based on a software language, the hardware side is used for developing a chip design based on a hardware language, the first storage bin and the second storage bin are used for storing chip reference model code files, the chip reference model code files are used for generating a chip reference model, and the software language can be specifically C++, python, systemC and the like.
In the case that the synchronization manner between the first version management tool and the second version management tool is bidirectional update, as an embodiment, the second version management tool is configured to receive a chip file P submitted by a user, where P and F are different versions of the chip file, generate second version information (PU, PN, PD) corresponding to the chip file P, and store the chip file P and the corresponding second version information (PU, PN, PD) in the second storage bin, where PU is a user identifier corresponding to the chip file P in the second version management tool, PN is a version number generated by the second version management tool based on the chip file P, PD is a reserved information segment of the second version management tool corresponding to the chip file P, and PD is initially null.
The synchronization module is used for acquiring a chip file P and corresponding second version information (PU, PN, PD) from the second version management tool and submitting the chip file P and the corresponding second version information to the first version management tool.
The first version management tool generates corresponding first version information (QU, QN, QD) based on the received chip file P and corresponding second version information (PU, PN, PD), wherein QU is a user identifier corresponding to the chip file P in the first version management tool, and QU=PU is set; the QN is a version number generated by a first version management tool based on a chip design configuration file submitted by a current user; QD is a reserved information segment of a first version management tool corresponding to the chip file P, qd=pn is set, and a version number mapping relation of the chip file P is established in the first version management tool; the chip file P and the first version information (QU, QN, QD) are stored in the first memory bin and QN is sent to the synchronization module.
The synchronization module is configured to send QN to the second version management tool, where the second version management tool sets pd=qn, and a version number mapping relationship of the chip file P is established in the second version management tool. The embodiment of the invention utilizes the reserved information segments of the first version management tool and the second version management tool, and stores the version numbers of the opposite sides in the reserved information segments, thereby establishing the version number mapping relation of the chip files P in the first version management tool and the second version management tool.
And under the condition that the synchronization mode between the first version management tool and the second version management tool is bidirectional updating, if the synchronization module monitors that the first version management tool receives the chip file F submitted by the user and the second version management tool also receives the chip file P submitted by the user, the synchronization module judges whether the chip file F and the chip file P have conflict or not, if so, the synchronization module reports errors, and if not, a file fusion instruction is sent to the first version management tool and the second version management tool. It should be noted that, the existence of the conflict between the chip file F and the chip file P means that the same portion of the chip file is modified by both ends at the same time and submitted to the first version management tool and the second version management tool at the same time. This is not allowed when a conflict occurs, and therefore a time-out is required.
The first version management tool obtains a newly added file part corresponding to the chip file P based on the received file fusion instruction, and updates the chip file F stored in the first storage bin into a union of the chip file F and the newly added file part corresponding to the chip file P.
The second version management tool obtains a newly added file part corresponding to the chip file F based on the received file fusion instruction, and updates the chip file P stored in the second storage bin into a union of the chip file P and the newly added file part corresponding to the chip file F.
According to the embodiment of the invention, the synchronization module is arranged between the first version management tool and the second version management tool, so that the chip files of the first version management tool and the second version management tool are synchronized, the version number mapping relation of the chip files is respectively established in the first version management tool and the second version management tool based on the reserved information segment, the synchronization of the chip files in different version management tools is automatically realized, the normal operation of the chip development process is ensured, and the chip development efficiency is improved.
The present invention is not limited to the above-mentioned embodiments, but is intended to be limited to the following embodiments, and any modifications, equivalents and modifications can be made to the above-mentioned embodiments without departing from the scope of the invention.
Claims (5)
1. A chip file version management system is characterized in that,
The system comprises a first version management tool, a second version management tool and a synchronization module connected with the first version management tool and the second version management tool;
The first version management tool comprises a first storage bin, and the second version management tool comprises a second storage bin;
When the synchronization mode between the first version management tool and the second version management tool is unidirectional update, the first storage bin is a master bin, the second storage bin is a slave bin, the system can update chip files only through the master bin, the first version management tool is arranged on a hardware side, the second version management tool is arranged on a software side, the software side is used for developing a chip reference model based on a software language, the hardware side is used for developing a chip design based on the hardware language, and the first storage bin and the second storage bin are used for storing chip design configuration files;
The first version management tool is configured to receive a chip file F submitted by a user, generate first version information (FU, FN, FD) corresponding to the chip file F, and store the chip file F and the corresponding first version information (FU, FN, FD) in the first storage bin, where FU is a user identifier corresponding to the chip file F in the first version management tool, FN is a version number generated by the first version management tool based on the chip file F, FD is a reserved information segment of the first version management tool corresponding to the chip file F, and FD is initially empty;
The synchronization module is used for acquiring a chip file F and corresponding first version information (FU, FN, FD) from the first version management tool and submitting the chip file F and the corresponding first version information (FU, FN, FD) to the second version management tool;
The second version management tool generates corresponding second version information (EU, EN, ED) based on the received chip file F and the corresponding first version information (FU, FN, FD), wherein EU is a user identifier corresponding to the chip file F in the second version management tool, and eu=fu is set; EN is a version number generated by the second version management tool based on the chip file F; ED is a reserved information section of a second version management tool corresponding to the chip file F, ED=FN is set, and a version number mapping relation of the chip file F is established in the second version management tool; storing a chip file F and second version information (EU, EN, ED) into the second storage bin, and sending EN to the synchronization module;
The synchronization module is used for sending EN to the first version management tool, the first version management tool sets fd=en, and a version number mapping relation of the chip file F is established in the first version management tool;
When the synchronization mode between the first version management tool and the second version management tool is bidirectional updating, the first storage bin is a master bin, the second storage bin is a slave bin, the system updates the chip file through the master bin or the slave bin, the first version management tool is arranged on a software side, the second version management tool is arranged on a hardware side, the software side is used for developing a chip reference model based on a software language, the hardware side is used for developing a chip design based on the hardware language, and the first storage bin and the second storage bin are used for storing the chip reference model code file.
2. The system of claim 1, wherein the system further comprises a controller configured to control the controller,
The reserved information segment is a description information segment or a label information segment.
3. The system of claim 1, wherein the system further comprises a controller configured to control the controller,
The second version management tool is used for receiving chip files P submitted by a user, wherein P and F are chip files of different versions, generating second version information (PU, PN, PD) corresponding to the chip files P, and storing the chip files P and the corresponding second version information (PU, PN, PD) into the second storage bin, wherein PU is a user identifier corresponding to the chip files P in the second version management tool, PN is a version number generated by the second version management tool based on the chip files P, PD is a reserved information section of the second version management tool corresponding to the chip files P, and PD is initially empty;
the synchronization module is used for acquiring a chip file P and corresponding second version information (PU, PN, PD) from the second version management tool and submitting the chip file P and the corresponding second version information to the first version management tool;
The first version management tool generates corresponding first version information (QU, QN, QD) based on the received chip file P and corresponding second version information (PU, PN, PD), wherein QU is a user identifier corresponding to the chip file P in the first version management tool, and QU=PU is set; the QN is a version number generated by a first version management tool based on a chip design configuration file submitted by a current user; QD is a reserved information segment of a first version management tool corresponding to the chip file P, qd=pn is set, and a version number mapping relation of the chip file P is established in the first version management tool; storing a chip file P and first version information (QU, QN, QD) into the first storage bin and sending QN to the synchronization module;
the synchronization module is configured to send QN to the second version management tool, where the second version management tool sets pd=qn, and a version number mapping relationship of the chip file P is established in the second version management tool.
4. The system of claim 3, wherein the system further comprises a controller configured to control the controller,
If the synchronization module monitors that the first version management tool receives a chip file F submitted by a user and the second version management tool also receives a chip file P submitted by the user, the synchronization module judges whether the chip file F and the chip file P have conflict or not, if so, the synchronization module reports errors, otherwise, the synchronization module sends a file fusion instruction to the first version management tool and the second version management tool;
The first version management tool obtains a newly-added file part corresponding to the chip file P based on the received file fusion instruction, and updates the chip file F stored in the first storage bin into a union of the chip file F and the newly-added file part corresponding to the chip file P;
The second version management tool obtains a newly added file part corresponding to the chip file F based on the received file fusion instruction, and updates the chip file P stored in the second storage bin into a union of the chip file P and the newly added file part corresponding to the chip file F.
5. The system of claim 1, wherein the system further comprises a controller configured to control the controller,
The first version management tool and the second version management tool are any two of perforce, git, svn, cvs version management tools.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410191221.5A CN117742777B (en) | 2024-02-21 | Chip file version management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410191221.5A CN117742777B (en) | 2024-02-21 | Chip file version management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117742777A CN117742777A (en) | 2024-03-22 |
| CN117742777B true CN117742777B (en) | 2024-05-03 |
Family
ID=
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101136768A (en) * | 2006-09-01 | 2008-03-05 | 中兴通讯股份有限公司 | Software and hardware version management method and system of communication equipment |
| JP2009110061A (en) * | 2007-10-26 | 2009-05-21 | Nec Corp | Version management system and version management method |
| EP2955627A1 (en) * | 2014-06-13 | 2015-12-16 | BlackBerry Limited | Managing versions of components of a software suite |
| WO2017016210A1 (en) * | 2015-07-27 | 2017-02-02 | 中兴通讯股份有限公司 | Software version management method and apparatus |
| CN110222500A (en) * | 2019-06-14 | 2019-09-10 | 深圳前海微众银行股份有限公司 | Method for edition management, device, equipment and computer readable storage medium |
| CN110287187A (en) * | 2019-06-04 | 2019-09-27 | 华自科技股份有限公司 | Tables of data synchronous updating method, system and storage medium in multiple servers |
| CN113138794A (en) * | 2021-04-28 | 2021-07-20 | 河南中烟工业有限责任公司 | Management method and management system for code version |
| CN113138728A (en) * | 2020-01-20 | 2021-07-20 | 杭州旗捷科技有限公司 | Printer consumable chip upgrading system and method and consumable container |
| CN113380767A (en) * | 2021-05-13 | 2021-09-10 | 苏州裕太微电子有限公司 | Chip version number control structure and method |
| CN113971041A (en) * | 2021-10-28 | 2022-01-25 | 中国银行股份有限公司 | Version synchronization method and device of cross-version control system |
| CN114237688A (en) * | 2021-12-06 | 2022-03-25 | 网易（杭州）网络有限公司 | Branch version merging method, device and system and electronic equipment |
| CN114780137A (en) * | 2022-05-19 | 2022-07-22 | 中国建设银行股份有限公司 | Software version management method and device, storage medium and electronic equipment |
| WO2022205200A1 (en) * | 2021-03-31 | 2022-10-06 | 华为技术有限公司 | Version management method and apparatus |
| CN115237444A (en) * | 2022-07-28 | 2022-10-25 | 深圳壹账通智能科技有限公司 | Concurrent control method, device and equipment based on version number and storage medium |
| CN115794204A (en) * | 2022-11-11 | 2023-03-14 | 苏州浪潮智能科技有限公司 | Firmware management method, system, equipment and storage medium |
| CN116341428A (en) * | 2023-01-16 | 2023-06-27 | 成都登临科技有限公司 | Method for constructing reference model, chip verification method and system |
| CN117453272A (en) * | 2023-11-10 | 2024-01-26 | 东软睿驰汽车技术（沈阳）有限公司 | Automobile software version management system |
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101136768A (en) * | 2006-09-01 | 2008-03-05 | 中兴通讯股份有限公司 | Software and hardware version management method and system of communication equipment |
| JP2009110061A (en) * | 2007-10-26 | 2009-05-21 | Nec Corp | Version management system and version management method |
| EP2955627A1 (en) * | 2014-06-13 | 2015-12-16 | BlackBerry Limited | Managing versions of components of a software suite |
| WO2017016210A1 (en) * | 2015-07-27 | 2017-02-02 | 中兴通讯股份有限公司 | Software version management method and apparatus |
| CN110287187A (en) * | 2019-06-04 | 2019-09-27 | 华自科技股份有限公司 | Tables of data synchronous updating method, system and storage medium in multiple servers |
| CN110222500A (en) * | 2019-06-14 | 2019-09-10 | 深圳前海微众银行股份有限公司 | Method for edition management, device, equipment and computer readable storage medium |
| CN113138728A (en) * | 2020-01-20 | 2021-07-20 | 杭州旗捷科技有限公司 | Printer consumable chip upgrading system and method and consumable container |
| WO2022205200A1 (en) * | 2021-03-31 | 2022-10-06 | 华为技术有限公司 | Version management method and apparatus |
| CN113138794A (en) * | 2021-04-28 | 2021-07-20 | 河南中烟工业有限责任公司 | Management method and management system for code version |
| CN113380767A (en) * | 2021-05-13 | 2021-09-10 | 苏州裕太微电子有限公司 | Chip version number control structure and method |
| CN113971041A (en) * | 2021-10-28 | 2022-01-25 | 中国银行股份有限公司 | Version synchronization method and device of cross-version control system |
| CN114237688A (en) * | 2021-12-06 | 2022-03-25 | 网易（杭州）网络有限公司 | Branch version merging method, device and system and electronic equipment |
| CN114780137A (en) * | 2022-05-19 | 2022-07-22 | 中国建设银行股份有限公司 | Software version management method and device, storage medium and electronic equipment |
| CN115237444A (en) * | 2022-07-28 | 2022-10-25 | 深圳壹账通智能科技有限公司 | Concurrent control method, device and equipment based on version number and storage medium |
| CN115794204A (en) * | 2022-11-11 | 2023-03-14 | 苏州浪潮智能科技有限公司 | Firmware management method, system, equipment and storage medium |
| CN116341428A (en) * | 2023-01-16 | 2023-06-27 | 成都登临科技有限公司 | Method for constructing reference model, chip verification method and system |
| CN117453272A (en) * | 2023-11-10 | 2024-01-26 | 东软睿驰汽车技术（沈阳）有限公司 | Automobile software version management system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102637214B (en) | Method and system for synchronizing general data among database services | |
| EP2932370B1 (en) | System and method for performing a transaction in a massively parallel processing database | |
| CN101188566B (en) | A method and system for data buffering and synchronization under cluster environment | |
| CN101227379B (en) | Method and system for implementation of data synchronization | |
| CN103297456A (en) | Method for accessing sharing resources in distributed system and distributed system | |
| CN105701159A (en) | Data synchronization device and method | |
| CN106354865B (en) | Method, device and system for synchronizing master database and slave database | |
| CN107153660B (en) | Fault detection processing method and system for distributed database system | |
| CN101697136B (en) | Method and device for controlling resource | |
| CN104320495A (en) | Massive data storage method and system of power utilization information collecting system | |
| CN106484321A (en) | A kind of date storage method and data center | |
| CN111026735B (en) | Data transmission method, device, equipment and medium | |
| CN109739640A (en) | A kind of container resource management system based on Shen prestige framework | |
| CN108140035B (en) | Database replication method and device for distributed system | |
| CN112000649B (en) | Method and device for synchronizing incremental data based on map reduce | |
| CN110213359B (en) | Internet of vehicles networking data pushing system and method based on D2D | |
| CN104050297A (en) | Inquiry transaction distribution method and device | |
| CN117742777B (en) | Chip file version management system | |
| CN117742777A (en) | Chip file version management system | |
| CN101526959B (en) | Data storing method and device | |
| CN107609197A (en) | A kind of method of data synchronization, data synchronization unit and mobile terminal | |
| CN102055606B (en) | Business processing method, system and equipment in business support system | |
| CN115604271A (en) | Micro-service-based software and hardware complementary load balancing method | |
| CN112363759B (en) | Register configuration method and device, CPU chip and electronic equipment | |
| CN103368969A (en) | Method and system for transmission management of EML-NML total configuration synchronization |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |