CN101923571B - Method and device for managing terminal data logging - Google Patents

Method and device for managing terminal data logging Download PDF

Info

Publication number
CN101923571B
CN101923571B CN2010102399709A CN201010239970A CN101923571B CN 101923571 B CN101923571 B CN 101923571B CN 2010102399709 A CN2010102399709 A CN 2010102399709A CN 201010239970 A CN201010239970 A CN 201010239970A CN 101923571 B CN101923571 B CN 101923571B
Authority
CN
China
Prior art keywords
uuid
luid
changelog
data recording
data
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
Application number
CN2010102399709A
Other languages
Chinese (zh)
Other versions
CN101923571A (en
Inventor
付丽琴
蒲竞春
袁磊
刘大志
练煜
何建桥
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN2010102399709A priority Critical patent/CN101923571B/en
Publication of CN101923571A publication Critical patent/CN101923571A/en
Priority to PCT/CN2010/080666 priority patent/WO2012013008A1/en
Application granted granted Critical
Publication of CN101923571B publication Critical patent/CN101923571B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention discloses a method and a device for managing terminal data logging. The method comprises the following steps of: distributing an LUID (Local Unique Identifier) for each data logging of a terminal; distributing a UUID (Universally Unique Identifier) for the storage position of each data logging of the terminal; respectively establishing the mapping relationship between the LUID and the UUID for each data logging of the terminal; respectively concealing the corresponding UUID at each storage position in a change log file; changing values of change log items in the change log file by using the established mapping relationship of the LUID and the UUID when the data logging is non-synchronously operated; and executing synchrotrons operation of the data logging by using the established mapping relationship of the LUID and the UUID and the values of the change log items of the change log file when the data logging is synchronously operated. The invention manages the change log items in the change log file by using the mapping relationship between the LUID and the UUID, thereby greatly reducing the length of the change log file and the operation complexity of the change log, and simplifying the operation and the maintenance of the whole change log file.

Description

The method of managing terminal data logging and device
Technical field
The present invention relates to personal information management PIM (data the are synchronous) business of terminal in the communication field, particularly the method for managing terminal data logging and device.
Background technology
The management of the terminal such as mobile phone, PDA personal information, calendar information and e-mail messages etc. becomes more and more important, and has become an important component part of end message management.How to back up data to safely and effectively in the webserver, when changing terminal or terminal data and changing, can easily Backup Data be returned to terminal and become the synchronous main body of data, the SyncML agreement can realize that the data of the servers such as terminal and network are synchronous, and final so that data on terminal and the server are consistent.
Fig. 1 shown and carried out the synchronous business of data between display client and the server, namely carried out the bi-directional synchronization of data recording item by client such as mobile phone terminal and server.
SyncML agreement master data wheel synchronization type comprises two-way synchronously fast and two-way synchronously slow.Two-wayly synchronously all the data recording items (such as cards folder and schedule) on mobile phone terminal and the server are carried out synchronously slowly; Two-way soon synchronous will carrying out synchronously from last synchronous all renewals afterwards on terminal and the server.
Two-way is that a kind of increment is synchronous soon synchronously, and all modifications of its database between the last time is subsynchronous to this synchronously with terminal and server is synchronous.
Changelog, amendment record is then in order to record terminal/server database all modifications information between the last time is subsynchronous to this synchronously.
Traditional Changelog comprises each modification information that is updated entity, such as the unique identifier (database is the unique distribution of entity) of entity, done operation type etc.Being the changelog file is comprised of amendment record item one by one, and each amendment record item represents the information that an entity is modified.
Fig. 2 has shown the amendment record item structure of traditional changelog, its amendment record item can be fixed length or elongated, because what need record is the modification information of data recording, then common unique identifier LUID and other guide (such as action type, modification type etc.) by data recording forms.
There is following problem in the changelog scheme at present:
1. if to the every operation of database once, the changelog file increases an amendment record item, and then the changelog file will increase without limitation.
2. even under solution increases without limitation problem, the changelog file is also more and larger along with the quantity that is updated entity, and the changelog file need to ceaselessly repeatedly refresh and revises to add or revise " being modified the amendment record item of entity " and delete " the amendment record item of synchronous successful entity " according to database update, synchronous and synchronous result.This operation to the changelog file is normally carried out the traversal formula according to the data ID in the amendment record item and is searched, and relates to interpolation or searches algorithm.So that the management complicated of changelog file.
Summary of the invention
The purpose of this invention is to provide a kind of method that reduces the managing terminal data logging of amendment record management complexity.
Another object of the present invention provides a kind of device that reduces the managing terminal data logging of amendment record management complexity.
According to first aspect present invention, the method for managing terminal data logging may further comprise the steps:
Local unique identifier LUID of each bar data record distribution for terminal;
For distributing a Globally Unique Identifier UUID in the memory location of each bar data record of terminal;
The mapping relations of LUID and UUID set up in each the bar data record that is respectively terminal;
Each deposit position in amendment record changelog file is hidden respectively corresponding UUID;
During the data recording asynchronous operation, the LUID that use is set up and the mapping relations of UUID are revised the value of the amendment record item in the changelog file;
During data recording synchronous operation, the value of the amendment record item of the LUID that use is set up and the mapping relations of UUID and described changelog file is searched and is treated synchronous data recording.
Wherein, during the data recording asynchronous operation, utilize the mapping relations of UUID and LUID to find UUID by the data recording of LUID sign, then revise the value of the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds.
Wherein, during to the synchronous operation of data record, read the effective value of amendment record item in the changelog file and hiding UUID thereof, then utilize the mapping relations of UUID and LUID to obtain the data recording that LUID identifies, and then resulting data recording is carried out synchronous operation.
Wherein, the sequence number of amendment record item deposit position is corresponding to the byte sequence number of changelog file in the described changelog file, the pass of described byte sequence number and described UUID is: BN=(UUID-1) * BL+1, and wherein BN is the byte sequence number, BL is amendment record item byte length.Amendment record item byte length of the present invention is fixed, it for example is 1 byte, in the case, the sequence number of amendment record item deposit position equals the byte sequence number of changelog file in the changelog file, the sequence number that is the N deposit position of amendment record item is the N byte sequence number of changelog file, and BN=UUID.
Wherein, described data recording asynchronous operation comprises: add or the Update Table record, and the synchronous successful subsequent treatment of data recording.
Described data recording synchronously successful subsequent treatment comprises: for finishing synchronous data recording, utilize the mapping relations of UUID and LUID to find UUID by the data recording of LUID sign, it is invalid then the value of the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds to be revised as.
According to second aspect present invention, the device of managing terminal data logging comprises:
The LUID distribution module is used to each bar data record of terminal to distribute a local unique identifier LUID;
The UUID distribution module is used to the memory location of each bar data record of terminal to distribute a Globally Unique Identifier UUID;
LUID and UUID mapping relations are set up module, set up the mapping relations of LUID and UUID for each the bar data record that is respectively terminal; And
The Changelog module is used for:
1) each deposit position in amendment record changelog file is hidden respectively corresponding UUID;
2) during the data recording asynchronous operation, the LUID that use is set up and the mapping relations of UUID are revised the value of the amendment record item in the changelog file; And
3) during data recording synchronous operation, the value of the amendment record item of the LUID that use is set up and the mapping relations of UUID and described changelog file is searched and is treated synchronous data recording.
Wherein, during the data recording asynchronous operation, described Changelog module at first utilizes the mapping relations of UUID and LUID to find UUID by the data recording of LUID sign, then revises the value of the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds.
Wherein, during to the synchronous operation of data record, described Changelog module at first reads the effective value of amendment record item in the changelog file and hiding UUID thereof, then utilize the mapping relations of UUID and LUID to obtain the data recording that LUID identifies, and then resulting data recording is carried out synchronous operation.
Need to prove, the present invention relates to but be not limited to the SyncML protocol synchronization; In addition, it is synchronous that the present invention is applicable to all increments.
Also need to prove, the present invention is applicable to the terminals such as mobile phone or PDA, is applicable to too server, and therefore terminal of the present invention includes but not limited to: server client, network node, mobile phone or PDA etc.
Compared with prior art, useful technique effect of the present invention is: because the present invention utilizes the mapping relations of IUID and UUID to manage amendment record item in the changelog file, therefore the length that can greatly reduce the changelog file, that is to say, changelog file of the present invention is with being modified increasing and increasing of physical quantities, and along with being modified increasing of physical quantities, its storage space advantage is more obvious.
Description of drawings
Fig. 1 is the schematic diagram that carries out the data synchronous service between display client and the server;
Fig. 2 is the schematic diagram of the amendment record item structure of traditional changelog;
Fig. 3 is the schematic diagram of the device of managing terminal data logging of the present invention;
Fig. 4 is dynamic LUID-UUID mapping graph of the present invention, can search the corresponding LUID of current UUID (memory location) according to this figure, and vice versa;
Fig. 5 a is the amendment record item structural drawing of changelog of the present invention, does not wherein comprise LUID and UUID;
Fig. 5 b is changelog file schematic diagram of the present invention, and UUID is hidden in the changelog file;
When Fig. 6 is a certain data of modification of the present invention record to the process flow diagram of the renewal of changelog file;
Fig. 7 is the process flow diagram that data recording of the present invention reads the changelog file when synchronous;
Fig. 8 is the amendment record item structural drawing of the traditional changelog when data recording is phone directory;
Fig. 9 is the amendment record item structural drawing of changelog of the present invention when data recording is phone directory;
Figure 10 is the empty changelog file schematic diagram after the initialization of the present invention;
Figure 11 is the changelog file schematic diagram behind phone directory of interpolation of the present invention.
Embodiment
Fig. 3 has shown the device of managing terminal data logging of the present invention, and terminal of the present invention can be that client shown in Figure 1 is portable terminal, also can be server shown in Figure 1.
As shown in Figure 3, the device of managing terminal data logging of the present invention comprises: LUID distribution module, UUID distribution module and LUID and UUID mapping relations module.The LUID distribution module is used for distributing a local unique identifier LUID into each bar data record of terminal; The UUID distribution module is used for distributing a Globally Unique Identifier UUID into the memory location of each bar data record of terminal; The mapping relations of LUID and UUID set up in each bar data record that LUID and UUID mapping relations module are used for being respectively terminal; The Changelog module then is used for: 1) each deposit position in amendment record changelog file is hidden respectively corresponding UUID; 2) during the data recording asynchronous operation, the LUID that use is set up and the mapping relations of UUID are revised the value of the amendment record item in the changelog file; 3) during data recording synchronous operation, the value of the amendment record item of the LUID that use is set up and the mapping relations of UUID and changelog file is searched and is treated synchronous data recording.
Fig. 4 has shown LUID of the present invention and the UUID mapping relations figure that is generated by mapping relations module shown in Figure 3, wherein LUID44,85 and 100 is respectively that the LUID distribution module is three local unique identifiers (such as positive integer) that the terminal data record distributes, such as 44 be about * * the local unique identifier of the data recording of phone directory, 85 be about Lee * * the local unique identifier of the data recording of phone directory, 100 be about the king * * the local unique identifier of the data recording of phone directory.With LUID44,85 and 100 corresponding UUID1,2,3 be that the UUID distribution module is the globally unique identifier that the memory location of the data recording that identifies of LUID is distributed.
Fig. 5 a has shown the structure of an amendment record item of changelog file of the present invention, and it does not have the LUID in the amendment record item of traditional changelog file shown in Figure 2.Fig. 5 b has shown that UUID is hidden in the situation in the changelog file, because the changelog file is made of a rule amendment record item of ordered arrangement, therefore (its deposit position sequence number is corresponding to the byte sequence number of changelog for the deposit position of each bar amendment record item in the changelog file, for example, when entry length is 1 byte, then the sequence number of N deposit position is the N byte sequence number of changelog) can reflect uniquely the UUID of corresponding data recording, for example when amendment record item length is 1 byte, the amendment record item of the 3rd deposit position reflection UUID is the modification situation of 3 data recording.
The length of each amendment record item of the present invention is fixed, and is 1 byte such as regular length, or 2 bytes etc., this shows, the deposit position of each amendment record item depends on amendment record item byte length in the changelog file.Therefore the hiding relation of UUID in the changelog file is actually the deposit position determined according to the byte sequence number in the changlog file and the corresponding relation of UUID, is expressed as: the byte sequence number in the changlog file=(UUID-1) * amendment record item byte length+1.
If the regular length of each amendment record item is 1 byte, each amendment record item only takies a byte so, therefore the sequence number of amendment record item deposit position is equivalent to the byte sequence number of changelog file, it is the byte sequence number=(UUID-1) * 1+1=UUID in amendment record item deposit position=changlog file, for example the 3rd byte sequence number of changelog file is equivalent to the sequence number of the 3rd deposit position, is 3 UUID so that the sequence number of the 3rd byte of changelog file has been hidden identifier.
If amendment record item regular length is 2 bytes, each amendment record item takies two bytes so, the sequence number of its first byte=(UUID-1) * 2+1=UUID * 2-1.For example when UUID was 3, its sequence number of depositing the first byte of amendment record item was 5, and the sequence number of depositing the second byte of amendment record item is 6, and to have hidden identifier be 3 UUID so that sequence number is the byte of 5 changelog file.
During the data recording asynchronous operation, the Changelog module utilizes the mapping relations of UUID and LUID to find the UUID of the data recording that is identified by LUID, follows the value of revising the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds.Need to prove, data recording asynchronous operation of the present invention comprises: add or the Update Table record, and the synchronous successful subsequent treatment (below will illustrate) of data recording.
During to the synchronous operation of data record, the Changelog module reads the effective value of amendment record item in the changelog file and hiding UUID thereof, then utilize the mapping relations of UUID and LUID to obtain the data recording that LUID identifies, and then resulting data recording is carried out synchronous operation.
On the other hand, the method for managing terminal data logging of the present invention may further comprise the steps:
Local unique identifier LUID of each bar data record distribution for terminal (such as client or server);
For distributing a Globally Unique Identifier UUID in the memory location of each bar data record of terminal;
The mapping relations of LUID and UUID set up in each the bar data record that is respectively terminal;
Each deposit position in amendment record changelog file is hidden respectively corresponding UUID;
During the data recording asynchronous operation, the LUID that use is set up and the mapping relations of UUID are revised the value of the amendment record item in the changelog file;
During data recording synchronous operation, the value of the amendment record item of the LUID that use is set up and the mapping relations of UUID and changelog file is searched and is treated synchronous data recording.
During the data recording asynchronous operation, utilize the mapping relations of UUID and LUID to find UUID by the data recording of LUID sign, then revise the value of the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds.Be in the situation of 1 byte such as the amendment record item length at the changelog file, when add a LUID=85 about Zhao * * phone directory recording the time, utilize the Globally Unique Identifier UUID=2 that figure can inquire its memory location that hints obliquely at of Fig. 4, the deposit position that obtains thus the changelog file is 2, thereby the value of the current amendment record item of the 2nd deposit position of changelog is revised as 1.
Data recording of the present invention synchronously successful subsequent treatment belongs to the data recording asynchronous operation, it comprises: for finishing synchronous data recording, utilize the mapping relations of UUID and LUID to find UUID by the data recording of LUID sign, it is invalid then the value of the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds to be revised as, be generally 0, to avoid lower subsynchronous synchronously successful data recording.
During to the synchronous operation of data record, read the effective value of amendment record item in the changelog file and hiding UUID thereof, then utilize the mapping relations of UUID and LUID to obtain the data recording that LUID identifies, and then resulting data recording is carried out synchronous operation.
Below in conjunction with Fig. 4 to Figure 11 the characteristics of managing terminal data logging of the present invention are elaborated.
For the data recording item that is stored in terminal (such as, a cards folder in the mobile phone),
The present invention is provided with a LUID (Locally Unique Identifier), local unique identifier, and this LUID is unique in whole terminal, and is ever-increasing.Even add a deleted identical data record, the LUID that distributes for this new interpolation data recording also is not identical with original deleted LUID.
Except LUID, the present invention also is provided with a UUID (Univeral Unique Identifier), and Globally Unique Identifier is identifying the memory location that these data are recorded in storage space of database.Article one, data record corresponding UUID, and the value of UUID is fixed, and is generally 1~MAXNUM, and MAXNUM is the storable dominant record item number of terminal database storage container.UUID is identifying the relative position of this data entry in database, according to UUID, can find corresponding data recording content.
The present invention has set up the mapping relations of LUID-UUID shown in Figure 4, and such as mapping table, but its form is not limited to table.
In the LUID-UUID mapping table, corresponding the LUID and the mapping relations of UUID of same data recording dynamically, the corresponding LUID of data recording that can find this UUID to store by current UUID; Can correspondence find its UUID by LUID, and find its memory location by UUID, take out data.
For example in Fig. 4, if know that the LUID of a data record is 3, the UUID that then can find out this record by mapping table is 100, and namely this record is stored in the 100th memory location of database; If knowing the UUID of data is 1, i.e. record on memory location 1, then can find out its LUID by mapping table is 44.
Usually, the changelog file is comprised of amendment record item one by one, and each amendment record item represents the information that data records (entity) are modified.
Unique distinction of the present invention is:
1) the amendment record item is regular length in the changelog file.
2) modification of each data recording is only unique corresponding to a changelog amendment record item, therefore the changelog file size is fixed, its value is the length of MAXNUM * amendment record item.
3) set up the mapping table of a LUID-UUID, can find LUID by UUID, also can find UUID. by LUID simultaneously
4) changelog file data entry does not adopt LUID, does not directly adopt UUID yet, and its amendment record item only is comprised of " other guide " shown in Fig. 5 a, for example represents effective or invalid value and forms.
Simultaneously, the UUID (information) of data is hidden in the position of changelog file modification entry, shown in Fig. 5 b.
As, when amendment record item length was 1 byte, amendment record item 4 represented the 4th amendment record item in the changelog file, and then corresponding UUID is 4.When these data are operated, then can pass through UUID, or find LUID by UUID, to its operation.
So, not only greatly shorten the length (saved the ID byte number of each amendment record item, will greatly reduce the length of amendment record item, thereby saved the storage space of changelog) of amendment record item; Simultaneously, the UUID Information hiding in changelog file itself, is not only saved storage space, and can effectively position the amendment record item, greatly reduced the operation and maintenance complexity of changelog.
Take the mobile phone terminal cards folder synchronously as example, suppose that mobile phone terminal database max cap. is 500 phone directories.The structure of amendment record item only contains the action type of the sign FLAG of regular length (such as accounting for a byte) as shown in Figure 9 in the Changelog file of the present invention.
Fig. 8 has shown the structure of amendment record item among traditional changelog, and wherein the structure of amendment record item comprises in the Changelog file: the LUID with 13 bytes; Contain the action type that indicates FLAG, refer to the operated type of phone book entries, as adding etc.Its value is: 0 representative is invalid, 1 representative interpolation operation, and 2 represent deletion action, and operation is upgraded in 3 representatives, and 1~3 all represents effectively, accounts for 4 bytes.So the data recording item length of traditional changelog is totally 17 bytes.
The structure of amendment record item structure and amendment record item of the present invention shown in Figure 9 is not difficult to find that the present invention shortens the length of amendment record item greatly among documents traditional changelog shown in Figure 8.
Figure 10 has shown one, and wherein grid illustrates that each amendment record item, its length are a byte by an empty changelog file behind the initialization operation, and its initial value is 0, and it is invalid to represent.
Fig. 6 has shown the flow process of renewal changelog file of the present invention, is used for an example of explanation data recording asynchronous operation.Describe as an example of the phone directory recording that adds a LUID=100 example, suppose LUID-UUID mapping table such as Fig. 4 this moment, then:
1) inquires about its UUID=3 according to LUID;
2) according to UUID, search the position at corresponding amendment record item place: (3-1) * 1 (byte length)+1=3.
Directly find position corresponding among the changelog, i.e. the 3rd deposit position shown in Figure 11.
3) revise at the 3rd deposit position (the 3rd entry place) of changelog file, action type is for increasing, and then its value is 1, and representative increases.
Fig. 7 has shown that terminal executing data of the present invention records the flow process that reads the changelog file when synchronous, and this flow process comprises:
1) traversal reads first first, second amendment record item such as the changelog file of Figure 11.Its value is 0, and it is invalid to represent.
2) read the value of the 3rd entry, its value is 1, effectively.Then:
A) according to its position the 3rd byte, calculate UUID=(3-1)/1-1=3.1 length that represents changelog amendment record item wherein.
B) according to the LUID-UUID mapping table, suppose still to be shown in Figure 1, then LUID=100.
C) when synchronous, the phone directory of LUID=100 can be carried out synchronously.
The synchronous successful subsequent treatment of data recording belongs to the asynchronous operation of data recording, usually start this operation according to synchronous successful response signal, during such as the synchronous success response of data recording of sending when server about LUID=100, client is handled as follows (referring to Fig. 6):
Inquire about its UUID=3 according to LUID;
According to UUID, search the position at corresponding amendment record item place: (3-1) * 1 (byte length)+1=3.Directly find position corresponding among the changelog, i.e. the 3rd deposit position shown in Figure 11.
The 3rd deposit position (the 3rd entry place) at the changelog file is revised, and being revised as its value invalid is 0, in order to avoid repeat synchronously next time.
In sum, the present invention has following technique effect:
The changelog file has constant size, and its size is the length of MAXNUM* amendment record item, and namely without the file size problem that increases without limitation, and maximum file size is also very little.
For example traditional changelog scheme changelog file increases along with the increase that is modified the record number, and its value is the length of X* amendment record item, and wherein X is the current record number that is modified; Changelog length of the present invention is the length of MAXNUM* amendment record item.
Such as, the terminal data storage capacity is 500, be the traditional scheme amendment record item of 17 bytes for length, the changelog file needs 500 * 17=8500 byte, and changelog file of the present invention only needs 500 * 1=500 byte, that is to say, under same storage space condition, when the amendment record number surpassed 30 (500/17=30) bar, this programme had a clear superiority in aspect storage space.
On the other hand, suppose that amendment record has M, synchronization server has individual and corresponding each server of N that one cover changelog is arranged.Then for prior art, in the time need to making amendment to certain the bar entry among the changelog, its complexity is 0 (M*N), and all operations all is file operation.For this programme, because changelog can navigate to certain amendment record very soon, need not the traversal formula and search, then its operation complexity is 0 (N).Therefore this programme is very simple to the operation and maintenance of file.
In sum, because the present invention utilizes the mapping relations of IUID and UUID to manage amendment record item in the changelog file, therefore can greatly reduce the length of changelog file, thereby reduce file storage; In addition, the present invention hides relation by changelog storage positions of files and UUID, it is the corresponding relation of changelog file byte sequence number and UUID, office terminal amendment record or obtain the amendment record of LUID sign by deposit position, thereby greatly reduce the operation complexity of changelog, make whole changelog file operation and safeguard simplification.Particularly, for the system of support with a plurality of server sync, the present invention can greatly reduce complexity.
Specifically, the technique effect that file storage of the present invention is few and management complexity is lower is owing to following technical characterstic of the present invention:
1, the length of each amendment record item reduces greatly;
2, each file only comprises the amendment record item of fixed number;
3, the value of at every turn upgrading the amendment record item such as does not need to search at the operation.
Although above the present invention is had been described in detail, the invention is not restricted to this, those skilled in the art of the present technique can carry out various modifications according to principle of the present invention.Therefore, all modifications of doing according to the principle of the invention all should be understood to fall into protection scope of the present invention.

Claims (11)

1. the method for a managing terminal data logging is characterized in that may further comprise the steps:
Local unique identifier LUID of each bar data record distribution for terminal;
Distribute a Globally Unique Identifier UUID for the memory location of each bar data record of terminal, be used for identifying the memory location that described each bar data are recorded in storage space of database;
The mapping relations of LUID and UUID set up in each the bar data record that is respectively terminal;
Each deposit position in amendment record changelog file is hidden respectively corresponding UUID;
During the data recording asynchronous operation, the LUID that use is set up and the mapping relations of UUID are revised the value of the amendment record item in the changelog file;
During data recording synchronous operation, the value executing data record synchronous operation of the amendment record item of the LUID that use is set up and the mapping relations of UUID and described changelog file.
2. method according to claim 1, it is characterized in that, during the data recording asynchronous operation, at first utilize the mapping relations of UUID and LUID to find UUID by the data recording of LUID sign, then revise the value of the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds.
3. method according to claim 1, it is characterized in that, during to the synchronous operation of data record, at first read the effective value of amendment record item in the changelog file and hiding UUID thereof, then utilize the mapping relations of UUID and LUID to obtain the data recording that LUID identifies, and then resulting data recording is carried out synchronous operation.
4. according to claim 2 or 3 described methods, it is characterized in that, the sequence number of amendment record item deposit position is the byte sequence number of changelog file in the described changelog file, the pass of wherein said byte sequence number and described UUID is: BN=(UUID-1) * BL+1, wherein BN is the byte sequence number, and BL is amendment record item byte length.
5. method according to claim 4 is characterized in that, described amendment record item byte length is fixed value.
6. method according to claim 4 is characterized in that, described data recording asynchronous operation comprises: add or the Update Table record, and the synchronous successful subsequent treatment of data recording.
7. method according to claim 6 is characterized in that, described data recording synchronously successful subsequent treatment comprises:
For finishing synchronous data recording, utilize the mapping relations of UUID and LUID to find UUID by the data recording of LUID sign, it is invalid then the value of the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds to be revised as.
8. the device of a managing terminal data logging is characterized in that comprising:
The LUID distribution module is used to each bar data record of terminal to distribute a local unique identifier LUID;
The UUID distribution module is used to the memory location of each bar data record of terminal to distribute a Globally Unique Identifier UUID, is used for identifying the memory location that described each bar data are recorded in storage space of database;
LUID and UUID mapping relations are set up module, set up the mapping relations of LUID and UUID for each the bar data record that is respectively terminal; And
The Changelog module is used for:
1) each deposit position in amendment record changelog file is hidden respectively corresponding UUID;
2) during the data recording asynchronous operation, the LUID that use is set up and the mapping relations of UUID are revised the value of the amendment record item in the changelog file; And
3) during data recording synchronous operation, the value executing data record synchronous operation of the amendment record item of the LUID that use is set up and the mapping relations of UUID and described changelog file.
9. device according to claim 8, it is characterized in that, during the data recording asynchronous operation, described Changelog module utilizes the mapping relations of UUID and LUID to find the UUID of the data recording that is identified by LUID, follows the value of revising the current amendment record item on the changelog storage positions of files corresponding with the UUID that finds.
10. according to claim 8 or 9 described devices, it is characterized in that, during to the synchronous operation of data record, described Changelog module reads the effective value of amendment record item in the changelog file and hiding UUID thereof, then utilize the mapping relations of UUID and LUID to obtain the data recording that LUID identifies, and then resulting data recording is carried out synchronous operation.
11. device according to claim 8 is characterized in that, described terminal comprises: one of server client, network node, mobile phone or PDA.
CN2010102399709A 2010-07-29 2010-07-29 Method and device for managing terminal data logging Active CN101923571B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2010102399709A CN101923571B (en) 2010-07-29 2010-07-29 Method and device for managing terminal data logging
PCT/CN2010/080666 WO2012013008A1 (en) 2010-07-29 2010-12-31 Method and device for managing terminal data records

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2010102399709A CN101923571B (en) 2010-07-29 2010-07-29 Method and device for managing terminal data logging

Publications (2)

Publication Number Publication Date
CN101923571A CN101923571A (en) 2010-12-22
CN101923571B true CN101923571B (en) 2013-05-01

Family

ID=43338504

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2010102399709A Active CN101923571B (en) 2010-07-29 2010-07-29 Method and device for managing terminal data logging

Country Status (2)

Country Link
CN (1) CN101923571B (en)
WO (1) WO2012013008A1 (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101923571B (en) * 2010-07-29 2013-05-01 中兴通讯股份有限公司 Method and device for managing terminal data logging
CN102291453B (en) * 2011-08-09 2017-04-26 中兴通讯股份有限公司 Data synchronization method and device
CN102375890A (en) * 2011-11-02 2012-03-14 杭州合众信息工程有限公司 Data synchronization method for source terminal table of database without major key
CN103136200B (en) * 2011-11-22 2018-02-02 中兴通讯股份有限公司 Data fresh information acquisition methods, device and method of data synchronization, device
CN103237075B (en) * 2013-04-24 2016-07-06 广州市动景计算机科技有限公司 A kind of method of data synchronization, Apparatus and system
CN103970843B (en) * 2014-04-28 2017-09-19 东华大学 Conversation combining method based on UUID in a kind of Web log integrities
CN105242988B (en) * 2015-10-10 2018-02-02 国家电网公司 The data back up method of distributed file system and distributed file system
CN108595392B (en) * 2018-05-04 2022-02-01 卢成伟 Global unique identifier GUID generation method and device
CN109324809B (en) * 2018-10-09 2022-04-22 郑州云海信息技术有限公司 Data processing method and device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1585944A (en) * 2001-11-12 2005-02-23 诺基亚有限公司 Arrangement of data synchronization in a telecommunications system
CN1794724A (en) * 2005-10-27 2006-06-28 华为技术有限公司 Method of realizing data synchronization on SyncML layer
CN101370032A (en) * 2008-09-09 2009-02-18 中兴通讯股份有限公司 Modification log maintenance method and apparatus for data synchronization

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100551109C (en) * 2007-07-25 2009-10-14 中兴通讯股份有限公司 The method of data synchronization of multi-module mobile terminal
US7747784B2 (en) * 2008-03-04 2010-06-29 Apple Inc. Data synchronization protocol
CN101923571B (en) * 2010-07-29 2013-05-01 中兴通讯股份有限公司 Method and device for managing terminal data logging

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1585944A (en) * 2001-11-12 2005-02-23 诺基亚有限公司 Arrangement of data synchronization in a telecommunications system
CN1794724A (en) * 2005-10-27 2006-06-28 华为技术有限公司 Method of realizing data synchronization on SyncML layer
CN101370032A (en) * 2008-09-09 2009-02-18 中兴通讯股份有限公司 Modification log maintenance method and apparatus for data synchronization

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
《基于SyncML协议的数据同步技术的研究》;周英军;《哈尔滨工业大学工学硕士学位论文》;20061215;第三章 SyncML数据同步理论分析 *
周英军.《基于SyncML协议的数据同步技术的研究》.《哈尔滨工业大学工学硕士学位论文》.2006,第三章 SyncML数据同步理论分析.

Also Published As

Publication number Publication date
CN101923571A (en) 2010-12-22
WO2012013008A1 (en) 2012-02-02

Similar Documents

Publication Publication Date Title
CN101923571B (en) Method and device for managing terminal data logging
CN103020315B (en) A kind of mass small documents storage means based on master-salve distributed file system
CN102542071B (en) Distributed data processing system and method
EP4202694A1 (en) Node memory-based data processing method and apparatus, device, and medium
CN101751473A (en) The searching of a kind of amendment record item, renewal and method for synchronous and data sync equipment
CN100592291C (en) Web page dynamic updating method, system and apparatus
CN102662992B (en) Method and device for storing and accessing massive small files
CN105138571B (en) Distributed file system and method for storing massive small files
CN103023982B (en) Low-latency metadata access method of cloud storage client
CN102882985A (en) File sharing method based on cloud storage
CN105183394A (en) Data storage processing method and device
CN101867607A (en) Distributed data access method, device and system
CN102024005B (en) Issuance system and method of information item set directories
WO2007067797A2 (en) Method and system for maintaining current data for wireless devices
CN103853714A (en) Data processing method and device
JP2001522074A (en) Communication system and method
CN103327052A (en) Data storage method and system and data visiting method and system
CN100458790C (en) Method and system for access data base
CN100378663C (en) Method, system and module for dynamic downloading of applied programe to user identification
CN111177143B (en) Key value data storage method and device, storage medium and electronic equipment
CN104348859A (en) File synchronizing method, device, server, terminal and system
CN107766355B (en) Hierarchical data management method, hierarchical data management system and instant messaging system
CN105812469A (en) Address book synchronization method and device
CN110334145A (en) The method and apparatus of data processing
CN111400334A (en) Data processing method, data processing device, storage medium and electronic 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
C14 Grant of patent or utility model
GR01 Patent grant