CN112231291A - Method and device for multi-branch version management of cloud files - Google Patents
Method and device for multi-branch version management of cloud files Download PDFInfo
- Publication number
- CN112231291A CN112231291A CN201910633377.3A CN201910633377A CN112231291A CN 112231291 A CN112231291 A CN 112231291A CN 201910633377 A CN201910633377 A CN 201910633377A CN 112231291 A CN112231291 A CN 112231291A
- Authority
- CN
- China
- Prior art keywords
- file
- version
- project
- branch
- versions
- 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
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000005516 engineering process Methods 0.000 claims abstract description 10
- 230000008569 process Effects 0.000 claims abstract description 8
- 230000001419 dependent effect Effects 0.000 claims description 6
- 238000000926 separation method Methods 0.000 abstract 1
- 238000013461 design Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 238000010276 construction Methods 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000013459 approach Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
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/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1873—Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A method for multi-branch version management of a cloud file comprises the following steps: storing files at the cloud end, storing and managing logic files under the engineering project by adopting a relational database, and storing physical files under the engineering project by adopting a distributed object storage technology, wherein the hierarchical relationship and the corresponding permission inheritance relationship of each logic file; allocating a unique File ID (File Id) for each File, wherein each File version has a globally unique version ID (replay Id), and performing single File version management; and performing multi-branch version management of the engineering project based on the mode. The method can realize the separation of logic and physical storage, reduce the file redundancy in the process of creating the project version, create and delete the project version in a light weight manner in real time, and support the creation and combination of multi-branch project versions and the backtracking of projects.
Description
Technical Field
The invention relates to the field of building informatization, in particular to a method and a device for cloud file multi-branch version management.
Background
In the building industry, any design construction project can generate a plurality of two-dimensional drawing files and a large number of three-dimensional models which are divided into major floors. Under the cooperation of multiple participants of projects, the number of files related to the projects is large, and file updating and version iteration are very fast. Meanwhile, for a design construction project, at a stage time node, the sub-model files and the sub-model files are mutually associated and can be finally integrated into a complete full-professional three-dimensional model for BIM service. In the construction industry, version control of a single design model file is not very important, but rather, it is important to perform uniform large version control of all files in a project as a whole in terms of the project. In addition, due to uncertainty in the progress of the project, there is a need for convenient switching and rollback between the various branching versions of the project.
At present, all general large network disks comprise some project document type products in the building industry, the authority control only achieves the level of files, only version management of single files is achieved, no project level version control exists, and the backtracking of project versions cannot be carried out, so that the backtracking of a plurality of actual design or construction projects is an obvious pain point. Several tools or software are commonly used:
(1) a hundred-degree network disk, http:// yun.baidu.com/;
(2)Dropbox:https://www.dropbox.com；
(3)Box:https://www.box.com/；
(4) building a cooperation, https:// xz.glodon.com;
the software services (1) to (3) are general network disk services, only support version management of a single file, and have no project concept, and the software service (4) is a model document cooperation service for a construction industry engineering project, but lacks version control of the project.
However, if the version control of the project level to be implemented is only a simple backup of all files of the project at that time, the following problems may exist:
(1) the number of files and the occupied disk space are increased, and each time one version is added, one more file is contained in the project at that time, even if only a small number of files in the project at that time are modified;
(2) generating a new project version is time consuming, since each copy involves all the files of the entire project;
(3) version update information of the same file among different project versions is lost, and source file modification information cannot be tracked.
Disclosure of Invention
Aiming at the problems, the invention provides a method and a device for multi-branch version management of a cloud file, wherein logic and physical storage are separated, file redundancy in the process of creating a project version is reduced, the creation and deletion of the project version can be carried out in a light-weight manner in real time, and the multi-branch project version creation and combination and the project backtracking are supported.
The invention provides a method for managing multi-branch versions of a cloud file, which comprises the following steps:
(1) storing files at the cloud end, storing and managing logic files under the engineering project by adopting a relational database, and storing physical files under the engineering project by adopting a distributed object storage technology, wherein the hierarchical relationship and the corresponding permission inheritance relationship of each logic file;
(2) allocating a unique File ID (File Id) for each File, wherein each File version has a globally unique version ID (replay Id), and performing single File version management;
(3) and (3) carrying out multi-branch version management on the project item based on the file storage mode in the step (1) and the single file version management mode in the step (2).
Further, each logical folder or file node in the relational database corresponds to a record of the relational database, and different logical files may point to the same physical file.
Furthermore, all the branch versions in the multi-branch version form a tree formed by logical nodes, all the versions are mutually dependent in sequence, and only one leaf node on the tree represents the latest version of the current engineering project.
Further, the multi-branch version management includes merging two branch versions, specifically:
the system simultaneously traverses the two trees, and detects nodes of which the two branch versions are added, deleted and modified compared with the basic version in the traversing process, wherein the nodes are logic folder nodes;
if the changes between the two versions are not conflicted, a combined version tree can be generated;
if the changes between the two versions themselves conflict, policy resolution is required.
Further, the multi-branch version management includes tracing back a history version of the same file in a plurality of project versions, specifically:
each project version is assigned with a unique identifier, the File Id of the same File remains unchanged inside the project version, and the first version of the File in each project version is the last version of the File in the project version inherited by the first version of the File.
The invention also provides a device for multi-branch version management of the cloud file, which is characterized by comprising the following components:
the cloud storage file unit is used for storing files at the cloud, storing and managing the logic files under the engineering project by adopting a relational database, the hierarchical relationship and the corresponding permission inheritance relationship of each logic file, and storing the physical files under the engineering project by adopting a distributed object storage technology;
the single File version management unit is used for allocating a unique File ID (File Id) for each File, wherein each File version has a globally unique version ID (replay Id) and performing single File version management;
and the multi-branch version management unit is used for performing multi-branch version management on the engineering project based on the file storage mode of the cloud storage file unit and the single file version management mode of the single file version management unit.
Further, each logical folder or file node in the relational database corresponds to a record of the relational database, and different logical files may point to the same physical file.
Furthermore, all the branch versions in the multi-branch version form a tree formed by logical nodes, all the versions are mutually dependent in sequence, and only one leaf node on the tree represents the latest version of the current engineering project.
Further, the multi-branch version management includes merging two branch versions, specifically:
the system simultaneously traverses the two trees, and detects nodes of which the two branch versions are added, deleted and modified compared with the basic version in the traversing process, wherein the nodes are logic folder nodes;
if the changes between the two versions are not conflicted, a combined version tree can be generated;
if the changes between the two versions themselves conflict, policy resolution is required.
Further, the multi-branch version management includes tracing back a history version of the same file in a plurality of project versions, specifically:
each project version is assigned with a unique identifier, the File Id of the same File remains unchanged inside the project version, and the first version of the File in each project version is the last version of the File in the project version inherited by the first version of the File.
Compared with the file management mode of a multi-branch version in the prior art, the mode provided by the invention has the advantages that in version updating, logic and physical storage are separated, file redundancy in the project version creating process is reduced, only the really modified file is actually stored, the unchanged file is not generated, the actual physical file is not generated, and the storage is not occupied; the method supports creation and combination of multi-branch project versions, can generate any multiple parallel versions for cooperation based on a certain project version, and combines the project versions at a certain time point, and is very suitable for a scene that multiple parties cooperate around a project; aiming at a file managed by a project in a cloud end, carrying out integral version control according to the granularity of the project; the method supports the management of engineering project versions, is light and flexible in version creation, and supports project-level version backtracking and cross-project file-level version backtracking.
Drawings
Fig. 1 is a flowchart illustrating a method for multi-branch version management of a cloud file according to the present application;
FIG. 2 is a schematic diagram of the manner in which the relational database of the present application is stored;
FIG. 3 is a schematic diagram of the data contained in the logical and physical files and their interrelationships of the present application;
FIG. 4 is a schematic diagram of a single file version management approach of the present application;
FIG. 5 is a schematic diagram of a multi-branch version management approach of the present application;
FIG. 6 is a schematic diagram of historical version tracing of the same file according to the present application
Fig. 7 is a schematic block diagram illustrating an apparatus for multi-branch version management of a cloud file according to the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The first embodiment is as follows:
referring to fig. 1, an embodiment of the present invention provides a method for multi-branch version management of a cloud file, including the following steps:
(1) when the file storage is carried out at the cloud, the logical files under the engineering project, the hierarchical relationship and the corresponding permission inheritance relationship of each logical file are stored and managed by adopting a relational database, and the physical files under the engineering project are stored by adopting a high-reliability distributed object storage technology.
Unlike file storage on a local computer, a user generally has the following requirements for a file storage service at the cloud: 1) the method is always available, and massive concurrent access is supported; 2) the storage capacity is infinitely expanded; 3) managing a traditional folder hierarchical structure; 4) and (4) data reliability.
In order to meet the requirements and combine the advantages and the disadvantages of different technologies, the invention adopts a relational database to store and manage the logic files under the engineering project, the hierarchical relationship and the corresponding permission inheritance relationship of the logic files, and the real storage of the physical files adopts a high-reliability distributed object storage technology.
The storage mode of the relational database is shown in fig. 2, each logical folder or file node in fig. 2 corresponds to a record of the database, different logical files can point to the same physical file, and the data contained in the logical folders or file nodes and the relationship between the logical folders and the physical files are shown in fig. 3. It can be seen that the information on the source file mainly describes attribute information irrelevant to the file content, such as file name, uploader, etc.; the file storage object is referred to by the source file in an n:1 relationship, and the information of the object describes the information of the object file in the physical storage system, such as storage ID, file abstract (MD5) and the like.
The reason why the present invention manages the logic file by using the relational database is that: 1) the logic files do not contain file contents, and each logic file contains less data and is highly structured; 2) from the viewpoint of requirements, flexible real-time query is needed for various dimensions and various combinations of the query.
The reason why the object storage technology is adopted to store the physical file (actual file content) in the invention is that: the object storage is suitable for storing massive binary data files, integrates the advantages of NAS and SAN, has the advantages of high-speed direct access of SAN, data sharing of NAS and the like, and provides a storage architecture with high reliability, cross-platform performance and safe data sharing. Currently, mainstream public cloud platforms provide object storage services, such as:
aliyun OSS: the object storage service provided by the Aliskiu uses RESTful API for access, supports flexible expansion of capacity and processing capacity, and provides multiple storage types for selection;
ceph: the Ceph is a distributed storage system, provides object, block and file storage capacity respectively, and is a storage solution of free open source software. The system can be deployed on a common x86 compatible server, has no complete distributed storage system with single point of failure, enables data to be fault-tolerant and seamlessly copied, can expand EB levels (EB, PB, TB, GB). In addition, its object storage service supports the protocols of S3 and Swift. The unique CRUSH algorithm is one of two major innovations of the CRUSH algorithm and has considerable expansibility.
Meanwhile, by adopting the design of segmenting the logic file and the physical file in this way, high-level functions such as file duplicate removal and file second transmission can be conveniently realized.
(2) And allocating a unique File ID (File Id) for each File, wherein each File version has a globally unique version ID (replay Id) and carrying out single File version management.
If the File ID of the File a is F1, the File ID and its own Revision ID are recorded on each version of the File, as shown in fig. 4.
(3) And (3) carrying out multi-branch version management on the project item based on the file storage mode in the step (1) and the single file version management mode in the step (2).
Based on the above file storage manner and single file version management manner, since the logical files are all managed in the relational database, copying all the logical files recorded in the same project in the database is very light, and mapping with physical files after copying is not destroyed. As shown in FIG. 5, two versions of an item, R1' and R1 ", are created simultaneously on top of a base version of an item, R1, and each has a different modification to the files, but it is important that these unmodified files, their corresponding physical files, are the same file, even if they already appear in multiple versions of the item.
With the branch versions as units, as the engineering project progresses, numerous branch versions appear. All the branch versions in the multi-branch version form a tree structure, all the versions are mutually dependent in sequence, and only one leaf node on the tree represents the latest version of the current engineering project. However, in projects where the actual project is collaborative, or where numerous branching versions are generated, some versions may have been obsolete, but changes on some versions need to be merged with the final version. For this reason, in addition to being able to generate multi-branched versions, it is also necessary to be able to merge between the individual branched versions.
As described above, each branch is a tree formed by logical nodes, when two branch versions are merged, the system traverses the two trees at the same time, and during the traversal, nodes where the two branch versions are added, deleted, and modified from the basic version are detected, where the nodes are logical folder nodes. If the change between the two versions has no conflict, the combined version tree can be generated smoothly; if there is a conflict, e.g., the same logical file node is deleted in version 1, but a new file version is created for it in version 2, policy resolution is required. The problem belongs to the field of multi-version concurrency control, and due to the branched version tree, except that the folder logical nodes are related to modification, the logical files or the version files thereof do not support modification, and only addition and deletion are carried out, so that the conflict is relatively simple to solve. When a true conflict occurs, the current system implementation will detect the conflict and inform the user of the conflict information, requiring the user to make a selection (the default selection is the "last change wins" policy). It should be noted that even if the user makes a wrong choice for conflict resolution, the merging can be chosen again, and the branch data is not affected.
In addition, referring to fig. 6, in order to trace back the history version of the same file in multiple project versions, the following design is made:
each project version has a unique identifier, the File Id of the same File remains unchanged within the project version, and the first version of the File in each project version is the last version of the File in the project version inherited by the first version. As can be seen from FIG. 6, for File 1, a tree-like relationship graph across projects between file versions is labeled between different project versions. The first version of File 1 in project version R1' is version 2, which is the last version 2 of File 1 in inherited project version R1. The above mode is an important condition for version backtracking.
Example two:
referring to fig. 7, a second embodiment of the present invention provides an apparatus for multi-branch version management of a cloud file, where the apparatus includes the following units:
the cloud storage file unit is used for storing files at the cloud, storing and managing the logic files under the engineering project by adopting a relational database, the hierarchical relationship and the corresponding permission inheritance relationship of each logic file, and storing the physical files under the engineering project by adopting a distributed object storage technology;
the single File version management unit is used for allocating a unique File ID (File Id) for each File, wherein each File version has a globally unique version ID (replay Id) and performing single File version management;
and the multi-branch version management unit is used for performing multi-branch version management on the engineering project based on the file storage mode of the cloud storage file unit and the single file version management mode of the single file version management unit.
Each logical folder or file node in the relational database corresponds to a record of the relational database, and different logical files can point to the same physical file.
All branch versions in the multi-branch versions form a tree formed by logic nodes, all versions are dependent on each other in sequence, and only one leaf node on the tree represents the latest version of the current engineering project.
The multi-branch version management includes merging two branch versions, specifically:
the system simultaneously traverses the two trees, and detects nodes of which the two branch versions are added, deleted and modified compared with the basic version in the traversing process, wherein the nodes are logic folder nodes;
if the changes between the two versions are not conflicted, a combined version tree can be generated;
if the changes between the two versions themselves conflict, policy resolution is required.
The multi-branch version management comprises the following steps of tracing the historical version of the same file in a plurality of project versions, specifically:
each project version is assigned with a unique identifier, the File Id of the same File remains unchanged inside the project version, and the first version of the File in each project version is the last version of the File in the project version inherited by the first version of the File.
It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing the relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module/unit in the above embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module.
The present invention is not limited to any specific form of combination of hardware and software. In summary, the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for multi-branch version management of a cloud file is characterized by comprising the following steps:
(1) storing files at the cloud end, storing and managing logic files under the engineering project by adopting a relational database, and storing physical files under the engineering project by adopting a distributed object storage technology, wherein the hierarchical relationship and the corresponding permission inheritance relationship of each logic file;
(2) allocating a unique File ID (File Id) for each File, wherein each File version has a globally unique version ID (replay Id), and performing single File version management;
(3) and (3) carrying out multi-branch version management on the project item based on the file storage mode in the step (1) and the single file version management mode in the step (2).
2. The method of claim 1, wherein each logical folder or file node in the relational database corresponds to a record of the relational database, and different logical files can point to the same physical file.
3. The method of claim 1, wherein all of the multi-branch versions form a tree of logical nodes, each of the versions being dependent on another, and wherein only one leaf node on the tree represents a latest version of a current project.
4. The method of claim 3, wherein the multi-branch version management comprises merging two branch versions, specifically:
the system simultaneously traverses the two trees, and detects nodes of which the two branch versions are added, deleted and modified compared with the basic version in the traversing process, wherein the nodes are logic folder nodes;
if the changes between the two versions are not conflicted, a combined version tree can be generated;
if the changes between the two versions themselves conflict, policy resolution is required.
5. The method according to claim 1, wherein the multi-branch version management comprises tracing back historical versions of the same file among multiple project versions, specifically:
each project version is assigned with a unique identifier, the File Id of the same File remains unchanged inside the project version, and the first version of the File in each project version is the last version of the File in the project version inherited by the first version of the File.
6. An apparatus for multi-branch version management of a cloud file, the apparatus comprising:
the cloud storage file unit is used for storing files at the cloud, storing and managing the logic files under the engineering project by adopting a relational database, the hierarchical relationship and the corresponding permission inheritance relationship of each logic file, and storing the physical files under the engineering project by adopting a distributed object storage technology;
the single File version management unit is used for allocating a unique File ID (File Id) for each File, wherein each File version has a globally unique version ID (replay Id) and performing single File version management;
and the multi-branch version management unit is used for performing multi-branch version management on the engineering project based on the file storage mode of the cloud storage file unit and the single file version management mode of the single file version management unit.
7. The apparatus of claim 6, wherein each logical folder or file node in the relational database corresponds to a record of the relational database, and different logical files can point to the same physical file.
8. The apparatus of claim 6, wherein all of the multi-branch versions form a tree of logical nodes, each of the versions being dependent on another, and wherein only one leaf node on the tree represents a latest version of a current project.
9. The apparatus of claim 8, wherein the multi-branch version management comprises merging two branch versions, specifically:
the system simultaneously traverses the two trees, and detects nodes of which the two branch versions are added, deleted and modified compared with the basic version in the traversing process, wherein the nodes are logic folder nodes;
if the changes between the two versions are not conflicted, a combined version tree can be generated;
if the changes between the two versions themselves conflict, policy resolution is required.
10. The apparatus according to claim 6, wherein the multi-branch version management includes tracing back historical versions of a same file among a plurality of project versions, specifically:
each project version is assigned with a unique identifier, the File Id of the same File remains unchanged inside the project version, and the first version of the File in each project version is the last version of the File in the project version inherited by the first version of the File.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910633377.3A CN112231291A (en) | 2019-07-15 | 2019-07-15 | Method and device for multi-branch version management of cloud files |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910633377.3A CN112231291A (en) | 2019-07-15 | 2019-07-15 | Method and device for multi-branch version management of cloud files |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112231291A true CN112231291A (en) | 2021-01-15 |
Family
ID=74111749
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910633377.3A Pending CN112231291A (en) | 2019-07-15 | 2019-07-15 | Method and device for multi-branch version management of cloud files |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112231291A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112765712A (en) * | 2021-01-20 | 2021-05-07 | 广联达科技股份有限公司 | Structured management method and device of BIM data, computer equipment and storage medium |
| CN113392068A (en) * | 2021-06-28 | 2021-09-14 | 上海商汤科技开发有限公司 | Data processing method, device and system |
| CN114281802A (en) * | 2021-12-27 | 2022-04-05 | 中国建设银行股份有限公司 | Data processing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160092525A1 (en) * | 2014-09-26 | 2016-03-31 | Oracle International Corporation | Integrating object-based data integration tool with a version control system in centralized and decentralized environments |
| CN105912691A (en) * | 2016-04-21 | 2016-08-31 | 国电南瑞科技股份有限公司 | Power grid model multi-version multi-tenant management system and method based on distributed storage |
| CN108319645A (en) * | 2017-12-25 | 2018-07-24 | 中国科学院信息工程研究所 | Multi version file view management method and device under a kind of isomery storage environment |
| CN109271194A (en) * | 2018-08-22 | 2019-01-25 | 五八有限公司 | Branch's access method and device based on distributed version control system |
-
2019
- 2019-07-15 CN CN201910633377.3A patent/CN112231291A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160092525A1 (en) * | 2014-09-26 | 2016-03-31 | Oracle International Corporation | Integrating object-based data integration tool with a version control system in centralized and decentralized environments |
| CN105912691A (en) * | 2016-04-21 | 2016-08-31 | 国电南瑞科技股份有限公司 | Power grid model multi-version multi-tenant management system and method based on distributed storage |
| CN108319645A (en) * | 2017-12-25 | 2018-07-24 | 中国科学院信息工程研究所 | Multi version file view management method and device under a kind of isomery storage environment |
| CN109271194A (en) * | 2018-08-22 | 2019-01-25 | 五八有限公司 | Branch's access method and device based on distributed version control system |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112765712A (en) * | 2021-01-20 | 2021-05-07 | 广联达科技股份有限公司 | Structured management method and device of BIM data, computer equipment and storage medium |
| CN113392068A (en) * | 2021-06-28 | 2021-09-14 | 上海商汤科技开发有限公司 | Data processing method, device and system |
| CN114281802A (en) * | 2021-12-27 | 2022-04-05 | 中国建设银行股份有限公司 | Data processing method and device |
| CN114281802B (en) * | 2021-12-27 | 2024-05-28 | 中国建设银行股份有限公司 | Data processing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7212040B2 (en) | Content Management Client Synchronization Service | |
| US10891067B2 (en) | Fast migration of metadata | |
| JP6309103B2 (en) | Snapshot and clone replication | |
| US8108429B2 (en) | System for moving real-time data events across a plurality of devices in a network for simultaneous data protection, replication, and access services | |
| US8429198B1 (en) | Method of creating hierarchical indices for a distributed object system | |
| US8694564B2 (en) | Method and system for providing on-demand services through a virtual file system at a computing device | |
| US11093387B1 (en) | Garbage collection based on transmission object models | |
| JP2006505069A (en) | Apparatus and method for hardware-based file system | |
| CN112231291A (en) | Method and device for multi-branch version management of cloud files | |
| US11711375B2 (en) | Team member transfer tool | |
| CN110895545A (en) | Shared data synchronization method and device | |
| KR102089710B1 (en) | Continous data mangement system and method |
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 |