CN104199929B - Method for mutual relation description between metadata - Google Patents
Method for mutual relation description between metadata Download PDFInfo
- Publication number
- CN104199929B CN104199929B CN201410447979.7A CN201410447979A CN104199929B CN 104199929 B CN104199929 B CN 104199929B CN 201410447979 A CN201410447979 A CN 201410447979A CN 104199929 B CN104199929 B CN 104199929B
- Authority
- CN
- China
- Prior art keywords
- metadata
- relation
- definition
- dependence
- description
- 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
- 238000000034 method Methods 0.000 title claims abstract description 17
- 238000009434 installation Methods 0.000 claims abstract description 42
- 238000011161 development Methods 0.000 claims abstract description 14
- 238000009795 derivation Methods 0.000 claims description 11
- 238000004519 manufacturing process Methods 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 6
- 230000002085 persistent effect Effects 0.000 claims description 5
- 238000007689 inspection Methods 0.000 claims description 3
- 238000012795 verification Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
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/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24573—Query processing with adaptation to user needs using data annotations, e.g. user-defined metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for mutual relation description between metadata. The method includes the steps of classification of relations during mutual use of the metadata, detailed description of the relations and how to use the relations. The method aims to improve integrity of an ERP system during installation and patching by describing the mutual relations between the metadata, and increases a description mode of the content of the ERP system. By means of classification, description and use of the relations, all elements in the ERP system can be described with the metadata and the relations between the metadata, and another description mode of the ERP system is increased. Meanwhile, integrity of the whole system during the development stage, the publish stage and the installation stage can be guaranteed, and integrity of the whole ERP system is improved.
Description
Technical field
The present invention relates to ERP system research and development of software field, it is therefore an objective to by the description of mutual relation between metadata, improve
ERP system is installed and integrity during patch installing, increases a kind of describing mode of ERP system content, specifically a kind of unit
The method of mutual relation description between data.
Background technology
As the continuous expansion of scope of the enterprise, ERP system become increasingly complex, the content for constituting ERP system is more and more, leads to
Cross metadata all elements in ERP system can be described, the mutual relation between element is also required to be described, come
The integrity of guarantee system.
Metadata has had various definition, but metadata does not have one to relation each other when mutually using
Plant describable method；After element in ERP system is all with metadata description, how to ensure the integrity of whole system, it is ensured that
When in exploitation, issue operation, metadata used is all consistent, complete.
The content of the invention
It is an object of the invention to provide a kind of method that mutual relation is described between metadata.
The purpose of the present invention realized in the following manner, by ERP system all of element all with metadata describe it is same
When, relation each other will also describe clear, it is ensured that the integrity of system, comprising 1）The classification of relation, 2）The description of relation
With 3）Three parts of use of relation, wherein：
1）In the classified part of relation, comprise the following steps and content：
（1）Define type
（2）Define each type of use scene
Step（1）Definition type, for the classification of descriptive metadata relation each other, comprising dependence, derive from
Relation, expansion relation, inclusion relation, dependence refer to the description of other metadata to be relied on during a metadata use,
Description comprising metadata entity and the concrete description for relying on content；Derived relation refers to that a metadata is derived from another yuan
Data, the data after the content metadata before derivation is derived from after changing also and then change；Expansion relation refers to a metadata pin
Another metadata is extended, it doesn't matter for the metadata when content metadata after extension changes and before extension；Bag
Refer to that a metadata is included by another metadata containing relation, the life cycle of two metadata is the same；
Step（2）The each type of use scene of definition, it is for describing each type of use scene, different types of
Relation, the scene for using are different, the corresponding scene of specific definition, increase to understand in depth to various types of, and guide tool
In body development process, how this uses, and dependence is used in content of the metadata using another metadata, is similar to
Reference between code；Derived relation when a metadata is used by a user, according to user's request different dimensions ways of presentation
It is different, the demand of user is met by derived relation；Expansion relation after one standardized product of user is supplied to, Yong Hugen
Increase some contents according to the service needed of oneself, adjust some flow processs, at this moment by expansion relation solving user's request；One
In definition, a part of content could be defined after needing to define another metadata metadata, the metadata for being included and this yuan
Data are bound, and whole life cycle is all identical, and inclusion relation is used under this scene；
2）In relationship description part, comprise the following steps and content：
（1）Each type of description
（2）The definition of data structure
Step（1）Each type of description, needs each type of definition is realized in code, comprising dependence
Definition, the definition of derived relation, the definition of expansion relation, the definition of inclusion relation.The definition of dependence is first comprising relying on
The unique identifier of data, the version number of dependence, if the detailed relation for relying on can be recognized, need to record certain section of metadata
The dependence of certain node of point and another metadata；Derived relation definition to be recorded derivation metadata unique identifier and
Correspondence version number；Expansion relation definition will describe the unique identifier of source metadata and version number, and source metadata is multiple；
Inclusion relation will describe the unique identifier comprising metadata and version number；
Step（2）The definition of data structure, according to each type realized in code, it is desirable to provide corresponding persistence is deposited
The structure of storage, the persistent storage that different type has same data store organisation, dependence are divided to two pieces, and one piece is between object
Dependence, only record the unique identifier of two metadata and corresponding version number, between the detailed node of another piece of record according to
Bad relation, the unique identifier comprising detailed node and node description information；Derived relation, expansion relation, inclusion relation are only
The unique identifier of record metadata and version number, data are existed in a relation table, are made a distinction by type field；
3）In the use part of relation, comprise the following steps and content：
（1）Use during development system；
（2）Use during fabrication and installation bag；
（3）Use when installation kit is installed；
Step（1）Development system when use, between different metadata produce relation when, be according to type not
With being recorded, according to different metadata types, relation is remembered between objects, or the relation of the detailed node of record, exploitation system
During system, when having used derivation, extension, inclusion relation, to recognize in the metadata and record, during relationship change, more new relation
Description content；When source metadata is deleted, judge whether to be used by other metadata according to relation, dependence is in design
Defined in device during metadata, it is identified according to the use relation between metadata, content metadata will be according to dependence when changing
Relation carries out integrity verification；
Step（2）Fabrication and installation bag when use, installation kit make when, be according to the relation between metadata needs
The data for being put into an installation kit are put into one piece, while the relation between metadata is recorded in installation kit, there is relation
Metadata, is put in an installation kit as far as possible, if one piece can not be put, the relation between installation kit is arranged；
Step（3）Use of installation kit when installing, by the installation of one piece of related metadata when installation kit is performed, use
In the integrity for ensureing whole system, if there is the metadata of relation not in an installation kit, need to be judged according to relation
The metadata being related whether there is, and whether relation is set up, what inspection did not passed through, not allow to install, if system supports fortune
Customize during row, need the relation between metadata is saved in client, when operationally customizing, need to close using these
System.
The excellent effect of the present invention：By the classification of relation, the description of relation, three parts of the use of relation, can be by
In ERP system, all of element is described with the relation between metadata and metadata, increased another ERP system
Describing mode, at the same can ensure that the development phase, launch phase, erection stage whole system integrity, improve whole ERP
The integrity of system.
Description of the drawings
Fig. 1 is that mutual relation describes topological diagram between metadata.
Specific embodiment
It is described in detail below with reference to the method for mutual relation description between metadata of the Figure of description to the present invention.
It is an object of the invention to provide a kind of method that mutual relation is described between metadata, all of by ERP system
While element is all described with metadata, relation each other also describes clear, it is ensured that the integrity of system.
In order to achieve the above object, the present invention includes three parts：The classification of relation, the description of relation, the use of relation.
In the classified part of relation, there is provided following steps and content：
（One）Define type
（Two）Define each type of use scene
Preferably, for step（One）Definition type, for the classification of descriptive metadata relation each other, comprising according to
Bad relation, derived relation, expansion relation, inclusion relation etc..Dependence refers to be relied on other during a metadata use
The description of metadata, the description comprising metadata entity and the concrete description for relying on content；Derived relation refers to a metadata
Another metadata is derived from, the data after the content metadata before derivation is derived from after changing also and then change；Expansion relation is
Refer to first number that a metadata is extended for another metadata, when the content metadata after extension changes and before extension
According to it doesn't matter；Inclusion relation refers to that a metadata is included by another metadata, and the life cycle of two metadata is the same.
Preferably, for step（Two）The each type of use scene of definition, for describing each type of use field
Scape.Different types of relation, the scene for using are different, the corresponding scene of specific definition, increase to various types of deep
Understand, in and guiding concrete development process, how this uses.Dependence is in a metadata is using another metadata
Use during appearance, similar to the reference between code；Derived relation is when a metadata is used by a user, different according to user's request
Dimension ways of presentation is different, and the demand of user is met by derived relation；Expansion relation is being supplied to one standard of user
After product, user increases some contents according to the service needed of oneself, adjusts some flow processs, at this moment by expansion relation solving
User's request；In definition, a part of content could be defined after needing to define another metadata one metadata, be included
Metadata and the bind meta-data, whole life cycle are all identical, and inclusion relation is used under this scene.
In relationship description part, there is provided following steps and content：
（One）Each type of description
（Two）The definition of data structure
Preferably, for step（One）Each type of description, needs each type of definition is realized in code, wrap
Definition containing dependence, the definition of derived relation, the definition of expansion relation, the definition of inclusion relation.The definition of dependence
The unique identifier for relying on metadata, the version number of dependence are included, if the detailed relation for relying on can be recognized, record unit is needed
The dependence of certain node of data and certain node of another metadata；Derived relation definition to be recorded the metadata of derivation
Unique identifier and correspondence version number；Expansion relation definition will describe the unique identifier of source metadata and version number, source
Metadata can be multiple；Inclusion relation will describe the unique identifier comprising metadata and version number.
Preferably, for step（Two）The definition of data structure, according to each type realized in code, it is desirable to provide right
The structure of the persistent storage answered, different type can have same data store organisation.The persistent storage of dependence can
To be divided to two pieces, one piece is dependence between object, only records the unique identifier of two metadata and corresponding version number, another
Dependence between the detailed node of block record, the unique identifier comprising detailed node and node description information；Derived relation,
Expansion relation, inclusion relation can only record unique identifier and the version number of metadata, and data there may be a relation table
In, made a distinction by type field.
In the use part of relation, there is provided following steps and content：
（One）Use during development system
（Two）Use during fabrication and installation bag
（Three）Use when installation kit is installed
Preferably, for step（One）Development system when use, between different metadata produce relation when,
Difference according to type is recorded, and according to different metadata types, relation can be remembered between objects, it is also possible to record bright
The relation of minutiae point.During development system, when having used derivation, extension, inclusion relation, to recognize in the metadata and record, close
System change when, more new relation description content；When source metadata is deleted, to be judged whether by other metadata according to relation
Use.Dependence during metadata, is identified according to the use relation between metadata, in metadata defined in designer
Integrity verification to be carried out according to dependence when holding change.
Preferably, for step（Two）Fabrication and installation bag when use, installation kit make when, be according between metadata
Relation the data for needing to be put into an installation kit are put into one piece, while the pass between metadata is recorded in installation kit
System.There is the metadata of relation, be put in an installation kit as far as possible, if one piece can not be put, the pass between installation kit is set
System.
Preferably, for step（Three）Use of installation kit when installing, by related first number when installation kit is performed
Install according to one piece, for ensureing the integrity of whole system.If there is the metadata of relation not in an installation kit, need
Judge that the metadata being related whether there is according to relation, whether relation can be set up, what inspection did not passed through, do not allow peace
Dress.If system is supported to customize during operation, need the relation between metadata is saved in client, operationally customize
When, need using these relations.
The present invention with function and beneficial effect：By the classification of relation, the description of relation, three portions of the use of relation
Point, all of element in ERP system can be described with the relation between metadata and metadata, increased another
The describing mode of ERP system, at the same can ensure that the development phase, launch phase, erection stage whole system integrity, carry
The integrity of high whole ERP system.
Embodiment
Below by by the detailed description to relation between metadata, above-mentioned target of the invention, feature and advantage are made more
Plus it is clear, understandable.
First in relation classified part：
（One）Various scenes during extracting metadata use, the relation between metadata is divided into：Rely on and close
System, expansion relation, derived relation, inclusion relation；
（Two）Dependence is mainly used in describing the dependence produced between 2 metadata, and the content of such as 1 metadata is used
To another 1 metadata.Expansion relation is used for 1 metadata of description and comes from another 1 metadata profile, and extension can be nothing
The extension of limit layer.Derived relation is used for 1 metadata of description and is derived from another 1 metadata.Inclusion relation is used to describe 1 first number
According in, a certain piece of content has used another 1 metadata completely, and this metadata can not be used by other metadata.
In the description section of relation：
（One）When metadata entity is defined, all of type is all included.For dependence, only can define
Rely on the unique identifier of object, it is also possible to which definition depends on the detailed nodal information of certain metadata.Expansion relation, derivation are closed
System will record the unique identifier of object before extension, while corresponding version number will be recorded, the metadata suggestion after extension, derivation
The increment information of metadata is recorded only, can not recognize really increment can remember full dose.Inclusion relation record correspondence metadata
Unique identifier；
（Two）During data structure definition, according to the detailed description degree of relation, different structure definition are realized.Extension is closed
System, derived relation, inclusion relation can only record the unique identifier for corresponding to metadata.Dependence suggestion carries out detailed note
Record, in addition to the metadata that record is relied on, in addition it is also necessary to record the nodal information which node depends on metadata, for first number
According to being controlled in detail.
In the use part of relation：
（One）During exploitation, if metadata and another metadata generate relation, designer is needed according to generation pass
The type of system records relation information in metadata entity.When relation changes, description information that be in more new metadata.Designer
During middle acquisition metadata, if other metadata being related with the metadata, it is proposed that by the one piece of loading of other metadata,
It is easy to designer quickly open and change；
（Two）During fabrication and installation bag, one piece of data packed can will be needed disposable according to the relation between metadata
Packing, if across deployment unit, the relation between installation kit can be automatically identified according to the relation between metadata；
（Three）When installation kit is performed, one piece of the metadata for needing to be installed according to the relation between metadata, it is ensured that be
The integrity of system.If related metadata is not in an installation kit, to be verified according to relation before metadata is installed,
Be unsatisfactory for condition does not allow installation.While metadata is installed, one piece of relation each other is installed to into client
In, it is custom made with during operation and may uses these relations.
In addition to the technical characteristic described in description, the known technology of those skilled in the art is.
Claims (1)
1. a kind of method that mutual relation is described between metadata, it is characterised in that ERP system all of element is all used into first number
According to while description, relation each other will also describe clear, it is ensured that the integrity of system, comprising 1）The classification of relation, 2）
The description of relation and 3）Three parts of use of relation, wherein：
1）In the classified part of relation, comprise the following steps and content：
（1）Define type
（2）Define each type of use scene
Step（1）Definition type, for the classification of descriptive metadata relation each other, comprising dependence, derived relation,
Expansion relation, inclusion relation, dependence refer to the description of other metadata to be relied on during a metadata use, comprising unit
The description of data entity and the concrete description for relying on content；Derived relation refers to that a metadata is derived from another metadata,
Data after content metadata before derivation is derived from after changing also and then change；Expansion relation refers to a metadata for another
Individual metadata is extended, and it doesn't matter for the metadata when content metadata after extension changes and before extension；Inclusion relation
Refer to that a metadata is included by another metadata, the life cycle of two metadata is the same；
Step（2）The each type of use scene of definition, for describing each type of use scene, different types of pass
System, the scene for using are different, the corresponding scene of specific definition, increase to understand in depth to various types of, and guide concrete
In development process, how this uses, and dependence is used in content of the metadata using another metadata；Derive from and close
It is when tying up to a metadata and being used by a user, different according to user's request different dimensions ways of presentation, by derived relation come
Meet the demand of user；After one standardized product of user is supplied to, user increases expansion relation according to the service needed of oneself
Some contents, adjust some flow processs, at this moment by expansion relation solving user's request；One metadata definition when, one
Point content could be defined after needing to define another metadata, the metadata for being included and the bind meta-data, whole Life Cycle
Phase is all identical, and inclusion relation is used under this scene；
2）In relationship description part, comprise the following steps and content：
（1）Each type of description
（2）The definition of data structure
Step（1）Each type of description, needs each type of definition, determining comprising dependence are realized in code
Justice, the definition of derived relation, the definition of expansion relation, the definition of inclusion relation, the definition of dependence will be comprising the first number of dependence
According to unique identifier, the version number of dependence, if can recognize rely on detailed relation, need record metadata certain node
With the dependence of certain node of another metadata；Derived relation definition to be recorded the unique identifier of metadata of derivation and right
Answer version number；Expansion relation definition will describe the unique identifier of source metadata and version number, and source metadata is multiple；Bag
The unique identifier comprising metadata and version number will be described containing relation；
Step（2）The definition of data structure, according to each type realized in code, it is desirable to provide corresponding persistent storage
Structure, the persistent storage that different type has same data store organisation, dependence are divided to two pieces, one piece be between object according to
Rely, only record the unique identifier of two metadata and corresponding version number, the dependence between another piece of record detail node is closed
System, the unique identifier comprising detailed node and node description information；Derived relation, expansion relation, inclusion relation are only recorded
The unique identifier of metadata and version number, data are present in a relation table, are made a distinction by type field；
3）In the use part of relation, comprise the following steps and content：
（1）Use during development system；
（2）Use during fabrication and installation bag；
（3）Use when installation kit is installed；
Step（1）Development system when use, between different metadata produce relation when, to enter according to the difference of type
Row record, according to different metadata types, relation is remembered between objects, or the relation of the detailed node of record, during development system,
When having used derivation, extension, inclusion relation, to recognize in the metadata and record, during relationship change, more new relation description
Content；When source metadata is deleted, judge whether to be used by other metadata according to relation, dependence is fixed in designer
During adopted metadata, it is identified according to the use relation between metadata, content metadata will enter according to dependence when changing
Row integrity verification；
Step（2）Fabrication and installation bag when use, installation kit make when, needs to be put into according to the relation between metadata
The data of one installation kit are put into one piece, while the relation between metadata is recorded in installation kit, the first number that there is relation
According to being put in an installation kit, if one piece can not be put, the relation between installation kit arranged as far as possible；
Step（3）Use of installation kit when installing, by the installation of one piece of related metadata when installation kit is performed, for protecting
The integrity of card whole system, if there is the metadata of relation not in an installation kit, needs to judge occur according to relation
The metadata of relation whether there is, and whether relation is set up, what inspection did not passed through, not allow to install, if system supports operation
Customization, needs the relation between metadata is saved in client, when operationally customizing, needs using these relations.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410447979.7A CN104199929B (en) | 2014-09-04 | 2014-09-04 | Method for mutual relation description between metadata |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410447979.7A CN104199929B (en) | 2014-09-04 | 2014-09-04 | Method for mutual relation description between metadata |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104199929A CN104199929A (en) | 2014-12-10 |
| CN104199929B true CN104199929B (en) | 2017-04-12 |
Family
ID=52085222
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410447979.7A Active CN104199929B (en) | 2014-09-04 | 2014-09-04 | Method for mutual relation description between metadata |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104199929B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106371832A (en) * | 2016-08-29 | 2017-02-01 | 石化盈科信息技术有限责任公司 | SaaS (Software As A Service) function customization system and method based on metadata driving |
| CN111401671B (en) * | 2019-01-02 | 2023-11-21 | 中国移动通信有限公司研究院 | Derived feature calculation method and device in accurate marketing and readable storage medium |
| CN112132533B (en) * | 2020-08-26 | 2024-03-22 | 浪潮通用软件有限公司 | Method for searching dependence of custom development content |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102023979A (en) * | 2009-09-09 | 2011-04-20 | 中国工商银行股份有限公司 | Meta-data management method and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6466992B2 (en) * | 1994-12-07 | 2002-10-15 | Next Computer, Inc. | Method for providing stand-in objects |
-
2014
- 2014-09-04 CN CN201410447979.7A patent/CN104199929B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102023979A (en) * | 2009-09-09 | 2011-04-20 | 中国工商银行股份有限公司 | Meta-data management method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104199929A (en) | 2014-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3561674B1 (en) | Method and apparatus for verifying block data in a blockchain | |
| CN104123126B (en) | It is a kind of to be used to generate the method and apparatus for merging conflict record list | |
| CN105760184B (en) | A kind of method and apparatus of charging assembly | |
| CN105893008A (en) | Method and device for customizing multi-channel installation package | |
| WO2016026328A1 (en) | Information processing method and device and computer storage medium | |
| CN106598672A (en) | Application configuration method and apparatus | |
| JP2008146601A5 (en) | ||
| CN106897103B (en) | Method for quickly and thermally updating version of mobile terminal network game | |
| CN104199929B (en) | Method for mutual relation description between metadata | |
| CN106293782A (en) | A kind of method for upgrading system and terminal | |
| CN103631590B (en) | The edit methods of automatic test script | |
| CN105488210B (en) | A kind of batch data matching process and device | |
| CN104484460A (en) | Metadata heat degree statistical method of distributed file system | |
| CN105608142A (en) | Storage method and device of Json data | |
| CN109634682A (en) | The configuration file update method and device of application program | |
| CN110442371A (en) | A kind of method, apparatus of release code, medium and computer equipment | |
| CN110134646B (en) | Knowledge platform service data storage and integration method and system | |
| CN106682021A (en) | Database migration method and device | |
| CN104808953A (en) | Device and method for controlling data storage and mobile terminal | |
| CN102880677B (en) | A kind of packing of the file based on Hash and read method | |
| CN110673849B (en) | Method and device for presetting file security contexts in batches | |
| CN109471901A (en) | A kind of method of data synchronization and device | |
| CN104978355B (en) | A kind of operating method and device of CPIO files | |
| CN105975567B (en) | Method and device for processing internal file of application program | |
| CN110069455A (en) | A kind of file mergences method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |