CA2447821C - Synchronization of database data - Google Patents
Synchronization of database data Download PDFInfo
- Publication number
- CA2447821C CA2447821C CA2447821A CA2447821A CA2447821C CA 2447821 C CA2447821 C CA 2447821C CA 2447821 A CA2447821 A CA 2447821A CA 2447821 A CA2447821 A CA 2447821A CA 2447821 C CA2447821 C CA 2447821C
- Authority
- CA
- Canada
- Prior art keywords
- synchronization
- update identifier
- update
- stored
- databases
- 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.)
- Expired - Lifetime
Links
- 238000000034 method Methods 0.000 claims abstract description 18
- 238000004590 computer program Methods 0.000 claims description 9
- 230000004044 response Effects 0.000 claims description 6
- 230000032258 transport Effects 0.000 description 42
- 230000001360 synchronised effect Effects 0.000 description 24
- 230000005540 biological transmission Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 238000012986 modification Methods 0.000 description 9
- 230000004048 modification Effects 0.000 description 9
- 238000012545 processing Methods 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 238000013480 data collection Methods 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- RQNWIZPPADIBDY-UHFFFAOYSA-N arsenic atom Chemical compound [As] RQNWIZPPADIBDY-UHFFFAOYSA-N 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 229920000136 polysorbate Polymers 0.000 description 2
- 241001137251 Corvidae Species 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 229910052729 chemical element Inorganic materials 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 235000015108 pies Nutrition 0.000 description 1
- 230000007781 signaling event Effects 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99938—Concurrency, e.g. lock management in shared database
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
Abstract
A method of arranging synchronization of databases, the method comprising the steps of establishing a transport layer connection for synchronization between a first and a second device which synchronize databases. During initialization of synchronization a first update identifier, which is stored at least in the first device and describes the latest synchronization event the devices have performed in the databases, and a second update identifier, which is defined by the first device and describes the present synchronization, are transmitted from the first device to the second device. The second update identifier is stored in the first and the second device. The contents of the first update identifiers stored in the devices are updated in the first and the second device if synchronization has been performed and after this said transport layer connection has been ended substantially properly.
Description
SYNCHRONIZATION OF DATABASE DATA
BACKGROUND OF THE INVENTION
[0001] The invention relates to synchronization of database data in a telecommunications system, particularly to maintenance of data on synchro-nization events. Data synchronization is a function where at least two data col-lections are made similar to each other so that the data units of the data col-lections substantially correspond to each other after synchronization.
BACKGROUND OF THE INVENTION
[0001] The invention relates to synchronization of database data in a telecommunications system, particularly to maintenance of data on synchro-nization events. Data synchronization is a function where at least two data col-lections are made similar to each other so that the data units of the data col-lections substantially correspond to each other after synchronization.
[0002] Data of portable terminals, such as portable computers, PDA
devices (Personal Digital Assistant), mobile stations or pagers, can be syn-chronized with network applications, applications of desktop computers or with other databases of the telecommunications system. In particular, data of cal-endar and e-mail applications are typically synchronized. EP 1 024 441 dis-closes a method of synchronizing databases. The method comprises maintain-ing data on the time the database has transmitted records to another database (transmission time), the time the database has received records from another database (reception time) and the time each record in the database has been modified (modification time). A record is transmitted from the first database to the second database only if the record modification time is later than the transmission time and the modification time is earlier than the reception time.
devices (Personal Digital Assistant), mobile stations or pagers, can be syn-chronized with network applications, applications of desktop computers or with other databases of the telecommunications system. In particular, data of cal-endar and e-mail applications are typically synchronized. EP 1 024 441 dis-closes a method of synchronizing databases. The method comprises maintain-ing data on the time the database has transmitted records to another database (transmission time), the time the database has received records from another database (reception time) and the time each record in the database has been modified (modification time). A record is transmitted from the first database to the second database only if the record modification time is later than the transmission time and the modification time is earlier than the reception time.
[0003] Synchronization has been based on the use of different manufacturer-specific protocols which are incompatible. This restricts the use of terminal or data types and often causes troubles to the user. In mobile communication, in particular, it is important that data can be retrieved and up-dated regardless of the terminal and application used.
[0004] To improve synchronization of application data, a language known as Synchronized Markup Language SyncML, which is based on the XML (Extensible Markup Language), has been developed. Using a SyncML
synchronization protocol, which employs messages in the SyncML format, data of any application can be synchronized between networked terminals of any kind. The SyncML synchronization protocol functions both in wireless and in fixed networks and supports several transmission protocols.
synchronization protocol, which employs messages in the SyncML format, data of any application can be synchronized between networked terminals of any kind. The SyncML synchronization protocol functions both in wireless and in fixed networks and supports several transmission protocols.
[0005] Figure 1 shows an example of synchronization where a mo-bile station MS functions as the SyncML client terminal and a network server S
functions as the SyncML server. The SyncML synchronization service com-prises first initializing a synchronization session during which e.g. the database to be synchronized is selected. The SyncML client terminal MS comprises a sync client agent which implements the SyncML protocol and sends a SyncML
message (Client Modifications), which includes at least the data which are to be synchronized in the mobile station MS and have changed since the last synchronization. The SyncML server S comprises a sync server agent, which controls synchronization, and a synchronization block (Sync Engine). The server usually waits for an initiative for synchronization from the SyncML
client (MS). The server S synchronizes the data, i.e. analyses the changes made to the database and client terminal data, and harmonizes it (makes necessary modifications, replacements and deletions). After this, the SyncML server S
sends the server modifications back to the SyncMl client (MS). The example described above is simple; yet it illustrates the roles of the devices according to the SyncML standard. The SyncML client terminal (MS) is typically a mobile station (MS), a PC (Personal Computer), a laptop, or a PDA device. The SyncML server S is typically a network server or a PC.
functions as the SyncML server. The SyncML synchronization service com-prises first initializing a synchronization session during which e.g. the database to be synchronized is selected. The SyncML client terminal MS comprises a sync client agent which implements the SyncML protocol and sends a SyncML
message (Client Modifications), which includes at least the data which are to be synchronized in the mobile station MS and have changed since the last synchronization. The SyncML server S comprises a sync server agent, which controls synchronization, and a synchronization block (Sync Engine). The server usually waits for an initiative for synchronization from the SyncML
client (MS). The server S synchronizes the data, i.e. analyses the changes made to the database and client terminal data, and harmonizes it (makes necessary modifications, replacements and deletions). After this, the SyncML server S
sends the server modifications back to the SyncMl client (MS). The example described above is simple; yet it illustrates the roles of the devices according to the SyncML standard. The SyncML client terminal (MS) is typically a mobile station (MS), a PC (Personal Computer), a laptop, or a PDA device. The SyncML server S is typically a network server or a PC.
(0006] The system according to the SyncML standard employs `synchronization anchors' associated with databases. These are strings which describe a synchronization event in terms of the date and time, for example.
The synchronization anchors used are called the `Last' anchor and the 'Next' anchor, of which the Last anchor represents the last event when the database was synchronized in respect of the transmitting device and the Next anchor represents the present synchronization event in respect of the transmitting de-vice. The devices transmit their anchors to each other during initialization of a synchronization session so that the Next anchor can be stored after a suc-cessful synchronization session. During the next synchronization the device can compare the Next anchor stored with the Last anchor received, and if they match, the device notes that no errors have occurred since the last synchroni-zation. If the anchors do not match, it is necessary to perform slow synchroni-zation, for example, where all data units in the databases have to be com-pared with one another. In practice, in slow synchronization the client terminal transmits all data from the database to be synchronized to the SyncML server, which analyses field by field the data it has received and the data of another database to be synchronized, or alternatively replaces all the data of the other database to be synchronized with the data it has received. In standard SyncML Sync Protocol, version 1.0, December 2000, which defines the SyncML synchronization protocol, it is stated that the synchronization anchors must not be updated until the synchronization session has finished.
The synchronization anchors used are called the `Last' anchor and the 'Next' anchor, of which the Last anchor represents the last event when the database was synchronized in respect of the transmitting device and the Next anchor represents the present synchronization event in respect of the transmitting de-vice. The devices transmit their anchors to each other during initialization of a synchronization session so that the Next anchor can be stored after a suc-cessful synchronization session. During the next synchronization the device can compare the Next anchor stored with the Last anchor received, and if they match, the device notes that no errors have occurred since the last synchroni-zation. If the anchors do not match, it is necessary to perform slow synchroni-zation, for example, where all data units in the databases have to be com-pared with one another. In practice, in slow synchronization the client terminal transmits all data from the database to be synchronized to the SyncML server, which analyses field by field the data it has received and the data of another database to be synchronized, or alternatively replaces all the data of the other database to be synchronized with the data it has received. In standard SyncML Sync Protocol, version 1.0, December 2000, which defines the SyncML synchronization protocol, it is stated that the synchronization anchors must not be updated until the synchronization session has finished.
[0007] Figure 2 illustrates use of synchronization anchors. In this example the SyncML client (MS) and the SyncML server (S) synchronize twice (synchronization sessions 1 and 2). The anchor (9.9.2001, 09:09:09 AM) of the preceding synchronization session (which precedes synchronization ses-sion 1) related to the same databases is stored in the synchronization server S. This anchor was the contents of the Next anchor of the preceding synchro-nization session and was stored as the Last anchor for the first synchroniza-tion session 1. The client MS initiates synchronization session 1 on 10 October 2001 at 10:10:10 AM. This time will be the Next anchor for synchronization session 1. The MS transmits the Last anchor stored in it and the Next anchor to the server S. During synchronization session 1 it is unnecessary to initiate slow synchronization because the Last synchronization anchors match, i.e. the Last anchor (9.9.2001, 09:09:09 AM) in the memory of the S corresponds to the Last anchor received. After the server S has transmitted an acknowledge-ment (OK), data can be synchronized. The acknowledgement is preferably an initialization message, which also comprises the Last and the Next anchor.
After synchronization session 1 has finished, the S replaces the preceding Last anchor (9.9.2001, 09:09:09 AM) with the contents of the Next anchor (10.10.2001, 10:10:10 AM) in its memory. A transport failure occurs in the ex-ample, i.e. the MS does not update the Last anchor to its memory. The trans-port failure can be an error in the transmission connection, for example. The S
can also disconnect the connection immediately after it has received a syn-chronization message, but the SyncML client can still remain waiting for an acknowledgement from the server. In that case disconnection is a transport failure from the SyncML client's point of view. During initialization of the sec-ond synchronization session the MS transmits a non-updated Last anchor (9.9.2001, 09:09:09 AM) and a Next anchor (11.11.2001, 11:11:11 AM) to the server S. The S notes that the Last anchors do not match, and thus it requests refresh, typically slow synchronization.
After synchronization session 1 has finished, the S replaces the preceding Last anchor (9.9.2001, 09:09:09 AM) with the contents of the Next anchor (10.10.2001, 10:10:10 AM) in its memory. A transport failure occurs in the ex-ample, i.e. the MS does not update the Last anchor to its memory. The trans-port failure can be an error in the transmission connection, for example. The S
can also disconnect the connection immediately after it has received a syn-chronization message, but the SyncML client can still remain waiting for an acknowledgement from the server. In that case disconnection is a transport failure from the SyncML client's point of view. During initialization of the sec-ond synchronization session the MS transmits a non-updated Last anchor (9.9.2001, 09:09:09 AM) and a Next anchor (11.11.2001, 11:11:11 AM) to the server S. The S notes that the Last anchors do not match, and thus it requests refresh, typically slow synchronization.
[0008] The problem related to the SyncML standard is that the up-date moment of the update identifiers which describe synchronization (syn-chronization anchor in the SyncML, e.g. a time stamp) has not been defined accurately. Depending on the manufacturer's application, some devices may update the identifier as soon as synchronization messages have been sent, whereas others perform this after the connection used for the synchronization session has been disconnected. As described in the example of Figure 2, some devices do not necessarily update the identifier in an error situation, as a result of which slow synchronizations are performed needlessly. Slow synchronizations are particularly undesirable for the user because they take a lot of time and typically cause additional data transmission costs. The user may also think that synchronization failed because slow synchronization takes so much time.
BRIEF DESCRIPTION OF THE INVENTION
BRIEF DESCRIPTION OF THE INVENTION
[0009] An object of the invention is to avoid the problem described above and provide as uniform function as possible in the devices that participate in synchronization. The object of the invention is achieved with a method, a synchronization system, a synchronization device, a telecommunications device and computer program products.
[0010] The invention is based on updating in a first device and in a second device the contents of first update identifiers, which describe the preceding synchronization and are stored in the devices, with the contents of a second update identifier, which describes the present synchronization, if synchronization has been performed and after this the transport layer connection established for synchronization has been ended substantially properly. The transport layer generally refers to a layer which provides the synchronization application layer with a reliable logical data transmission connection (not necessarily a protocol of the transport layer according to the OSI model, such as TCP). The transport layer connection has been ended properly when the handshaking related to ending of a connection has been performed according to the steps defined in the transport layer standard, after which the devices do not wait for any transport layer messages from each other. The updated contents of the update identifier are used in the next synchronization event.
[0011] The term 'database' is to be understood broadly as referring to a data collection of any data source or data storage that can be updated by one or more applications. The update identifier is any identifier that is associated with a synchronization event of databases, typically a sequence number or a time stamp. The fist update identifier always represents the synchronization event that precedes the present synchronization event. Update can be performed by replacing an earlier value with a new value or by using a sequential solution, i.e. by adding a new value to the earlier values, after which the newest value is always logically the first update identifier in the next synchronization event.
5 [0012] The arrangement of the invention has the advantage that the devices which support the invention always update the update identifiers substantially simultaneously, which allows to minimize unnecessary slow synchronizations and avoid the disadvantages related to them. Using the timing according to the invention, it can be ensured in a reliable manner that the devices participating in synchronization always either update the update identifiers or not.
[0013] According to a preferred embodiment of the invention, synchronization is based on the synchronization protocol according to the SyncML standard, and thus the first update identifier is the Last anchor of synchronization and the second update identifier is the Next anchor.
[0013A] In one aspect of the present invention there is provided a method of arranging synchronization of databases, the method comprising the steps of:
establishing a transport layer connection for synchronization between a first and a second device which synchronize databases;
transmitting a first update identifier, which is stored at least in the first device and describes the latest synchronization event the first and the second device have performed in the databases, during initialization of synchronization from the first device to the second device, and a second update identifier, which is defined by the first device and describes the present synchronization;
storing said second update identifier in the first device and in the second device; and updating the contents of the first update identifiers stored in the devices with the contents of said second update identifier in the first device and in the second device if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013B] In yet another aspect of the present invention there is provided a synchronization system for synchronizing databases comprising a 5a first device and a second device which perform synchronization and are arranged to:
establish a transport layer connection between the first device and the second device for performing synchronization;
transmit a first update identifier, which is stored at least in the first device and describes the latest synchronization event the first and the second device have performed in the databases, from the first device to the second device during initialization of synchronization and a second update identifier, which is defined by the first device and describes the present synchronization;
store said second update identifier; and update the contents of the first update identifiers stored in the devices with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013C] In yet another aspect of the present invention there is provided a telecommunications device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
means for transmitting a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization, the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013D] In yet another aspect of the present invention there is provided a synchronization device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
5b means for receiving a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the first update identifier with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013E] In yet another aspect of the present invention there is provided a computer program product loadable into the memory of a telecommunications device and comprising code embodied thereon which is executable in the telecommunications device to cause the telecommunications device to:
establish a transport layer connection to at least one other device for synchronizing databases;
transmit a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization, the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
store said second update identifier; and update the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013F] In yet another aspect of the present invention, there is provided a computer program product loadable into the memory of a computer functioning as a synchronization device and comprising code embodied thereon which is executable in the synchronization device to cause the synchronization device to:
5c establish a transport layer connection to at least one other device for synchronizing databases;
receive a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
store the second update identifier; and update the contents of the first update identifier stored in said synchronization device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013G] In yet another aspect of the present invention there is provided a telecommunications device configured to:
establish a transport layer connection to at least one other device for synchronizing databases;
transmit a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization; the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
store said second update identifier; and update the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013H] In yet another aspect of the present invention there is provided a synchronization device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
5d means for receiving a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the first update identifier with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The invention will be described in greater detail by means of preferred embodiments with reference to the accompanying drawings, in which Figure 1 illustrates synchronization according to the SyncML
synchronization protocol;
Figure 2 illustrates use of synchronization anchors;
Figure 3 illustrates a wireless network and a local area network;
Figure 4 illustrates a method according to a preferred embodiment of the invention;
Figure 5 illustrates a method according to another preferred embodiment of the invention; and Figure 6 is a signalling chart illustrating signalling events according to preferred embodiments of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0015] In the following, the preferred embodiment of the invention will be described in a system supporting the SyncML standard without limiting the invention thereto.
[0016] Figure 3 illustrates a networked system where data of databases DB and terminals TE can be synchronized. In respect of synchronization the terminal TE functions as a client device. Figure 3 shows two examples pies. In the first one there are terminals TE, databases DB and synchroniza-tion servers S connected to a local area network LAN. The terminal TE con-nected to the network LAN comprises a functionality for communicating with the devices of the network LAN, e.g. a network card and software which con-trols data transmission. The local area network LAN can be a local area net-work of any type and the TE can also communicate with the server S via the Internet, typically using a firewall FW. In the second example a terminal TE, a synchronization server S and databases DB are connected to a mobile net-work MNW. The terminal TE connected to the network MNW comprises a mo-bile station functionality for communicating wirelessly with the network MNW.
The mobile network MNW can be any prior art wireless network, such as a network which supports the GSM service, a network which supports the GPRS
service (General Packet Radio Service), a third-generation mobile communica-tion network, such as a UMTS network (Universal Mobile Telecommunications System), a wireless local area network WLAN or a private network. It should be noted that the server S can also function as a database DB, even though in Figure 3 the servers S and the databases DB are shown separately for the sake of clarity.
[0017] The terminals TE (in wired networks LAN and in wireless networks MNW) and the servers comprise memory MEM; SMEM, a user inter-face UI; SUI, 1/O means I/O; SI/O for arranging data transmission and a cen-tral processing unit CPU; SCPU which comprises one or more processors.
The memory MEM; SMEM includes a non-volatile portion of the central proc-essing unit CPU; SCPU for storing controlling applications and a random ac-cess memory portion for data processing. The memory MEM of the TE (which in this example is the database to be synchronized) and the memory of the databases DB store application data which are to be synchronized. A client agent SA operating according to the invention is preferably implemented by running a computer program code stored in the memory MEM in the CPU. The synchronization server S also provides a synchronization agent SA and a syn-chronization block SE according to the invention preferably by running a com-puter program code stored in the memory SMEM in the SCPU. The computer program code executable in the central processing unit CPU and SCPU
makes the terminal TE and the synchronization server S implement the inven-tive means. Embodiments of these means are illustrated in Figures 4 and 5.
The computer programs can be obtained via the network and/or stored in memory means, such as a floppy disk, CD ROM or other external memory means from which they can be loaded into the memory MEM, SMEM. Inte-grated circuits can also be used.
[0018] Figure 4 illustrates a synchronization method according to an embodiment of the invention where the terminal TE initiates synchronization with the server S. When there is need 401 to synchronize data of the data-bases (e.g. MEM, DB), a transport layer connection is established 402 be-tween the server S and the TE. The TE retrieves 403 the Last anchor updated after the preceding synchronization session from its memory MEM and defines 403 a Next anchor, e.g. checks the date and time. The Last and Next anchors are typically sequence numbers or time stamps. The anchors are database-specific, i.e. they indicate when the data of the database concerned have been updated. The TE also defines a Next anchor for synchronization and stores it temporarily in the random access memory section of the memory MEM. The TE transmits 404 a client initialization message to the server S. The Alert ele-ments of the message (for each database to be synchronized) comprise a Last anchor and a Next anchor. The client initialization message also informs the synchronization server S of the databases the data of which are to be syn-chronized and what type of synchronization is to be used. The client initializa-tion message typically also includes authentication information and information on the services and device features supported by the terminal TE.
[0019] The server S receives the client initialization message, stores the Next anchor temporarily in the random access memory section of the memory SMEM and retrieves 405 the stored Last anchor from its memory SMEM (which is the contents of the Next anchor of the last/preceding syn-chronization session stored preferably in the field labelled Last anchor). The S
checks 406 the Last anchor received and the Last anchor retrieved from its memory. After 407 the check 406 the server S sends a server initialization message containing the Next anchor (received from the TE) and the Last an-chor (from the memory SMEM of the server S) to the terminal TE, too. The server initialization message includes information on whether the time stamps correspond to each other. The TE checks 408 correspondence of the Last an-chors by comparing the Last anchor received with the Last anchor stored in the memory MEM.
[0020] If both the check 408 carried out by the TE and the check 406 carried out by the S indicate that the Last anchors correspond to each other, synchronization can be initiated 410 in the requested manner, in which case only the data units modified after the Last anchor need to be synchro-nized. After initialization has been finished, the data of at least one database DB defined in initialization of synchronization and data of the terminal TE
can be synchronized. The necessary authentications can be performed (in the case of two-way synchronization) employing SyncML messages illustrated in Figure 1 (Client Modifications, Server Modifications).
The type of synchronization can be e.g.
Two-way sync One-way sync from client only Refresh sync from client only One-way sync from server only Refresh sync from server only Server alerted sync [0021] As regards a more detailed description of the initialization of synchronization session and data synchronization 407, reference is made to the standard SyncML Sync Protocol, version 1.0, December 2000, which de-fines the SyncML synchronization protocol.
[0022] If the Last anchors do not match according to the compari-son 406 and/or 408, an error has occurred and all the data of the databases under synchronization need to be synchronized. After the comparison 406 the S can give information on unsuccessful synchronization or more preferably send an initialization message according to which slow synchronization is started 409. The TE can also request slow sync if the Last anchors do not cor-respond to each other according to the comparison 408.
[0023] Next it is checked 411 whether synchronization has been performed and the transport layer connection ended properly. Synchronization has been performed after all the data needed according to the synchronization type have been transferred between the TE and the S (neither has anything to transmit) and neither of the devices waits for an acknowledgement from the other. In the case of two-way synchronization, for example, synchronization has been performed when the server S acknowledges (Map Acknowledge-ment from Server) to the terminal TE that it has received the modifications made by the TE (Data Update Status Package for Server) and the TE receives the acknowledgement it has been waiting for. The connection has not been ended properly if, for example, the TE or the S receives an error message, an erroneous transport layer message or does not receive the message it is wait-ing for (in which case the TE/S can send an error message).
[0024] The SyncML synchronization protocol can be implemented between the TE and the S on top of the HTTP protocol (Hyper Text Transfer Protocol), the WSP protocol (Wireless Session Protocol) of the WAP standard (Wireless Application Protocol), the OBEX protocol used for cable connec-tions, such as USB (Universal Serial Bus) or RS-232, for short-range radio frequency connections (Bluetooth) or for infrared connections (IrDA), the TCP/IP stack (Transport Control Protocol/Internet Protocol) and on top of the transport layer service which offered by the e-mail protocol (SMTP, Simple Mail Transfer Protocol). Transfer at the lower layer can be performed accord-ing to the underlying network using e.g. short messages SMS or other signal-ing type transmission methods (e.g. USSD; Unstructured Supplementary Ser-vice Data), circuit-switched data calls or packet-switched data transfer ser-vices.
[0025] According to an embodiment, the HTTP protocol is used for providing a transport layer connection. In that case the connection has been ended properly after a 'HTTP request' message of the HTTP protocol, which includes last acknowledgements of the SyncML session, which require no re-sponse, and in response to which an acknowledgement message 'HTTP
status response' received in the device that transmitted the finish message has been transmitted, has been transferred between the devices. For exam-ple, the TE can send a `HTTP request' message which includes the last mes-sage (Data Update Status Package for Server) to which no acknowledgement is required (i.e. synchronization has been performed). The S responds by transmitting a 'HTTP status response' message, after which it can update 412 the contents of the Last anchor. If the TE receives the last correct `HTTP
status response' message (ok in the HTTP header 200) from the server S, it can update 412 the contents of the Last anchor.
[0026] According to an embodiment, the OBEX protocol is used to offer the transport layer connection. In that case the connection has been ended properly when a `disconnect' command in accordance with the OBEX
protocol has been transferred between the devices and a 'response' command related to the 'disconnect' command has been transmitted and received.
[0027] According to another embodiment, the WSP protocol is used to offer the transport layer connection. In that case the connection has been ended properly if a `disconnect request' message has been transferred be-tween the devices and a `disconnect indication' message related to the 'dis-connect request' message has been transmitted and received.
[0028] The contents of the previous Last anchors are updated 412 5 in the server S and the terminal TE (the contents can also be zero or empty if the Last anchor has not been stored earlier) with the contents of the Next an-chor of the present synchronization session if synchronization has been per-formed and the transport layer connection has been ended properly. The memory MEM, SMEM preferably includes one record in which the Last anchor 10 is maintained for the next synchronization. It is also possible that the value of the preceding Last anchor is not deleted but update 412 is performed by add-ing a record with a new value to the memory and by using it in the next syn-chronization. Thus the values stored in step 412 can be used 414 during the next synchronization, that is to say, the initiating party can send the value stored in the memory as the Last anchor and the receiving party can retrieve the stored value from its memory for comparison.
[0029] If synchronization has not been finished and/or the transport layer connection has not been ended properly, the values of the Last anchors stored in the memory are not changed 413 and the Next anchors stored tem-porarily are rejected.
[0030] Figure 5 illustrates synchronization according to another embodiment of the invention. When there is need 501 to synchronize data, a transport layer connection is established 502 between the server S and the TE. The TE retrieves 503 the Last anchor updated after the preceding syn-chronization session from its memory MEM and determines 503 a Next an-chor. The TE sends 504 to the server S an initialization message of synchroni-zation session which comprises the Last and the Next anchor defined. The S
receives the initialization message, stores the Next anchor temporarily and retrieves 505 the stored Last anchor (which is the contents of the Next anchor of preceding synchronization) from its memory SMEM. The S compares 506 the received Last anchor with the Last anchor it has retrieved from its memory.
If they correspond to each other, synchronization 507 can be implemented in the manner requested by the TE and only the data units modified after the Last anchor need to be synchronized. In that case the S can send an initializa-tion message to the TE, which indicates that synchronization can be carried out in the requested manner. Even though the S typically always sends the Last and the Next anchors to the TE, the TE does not compare these anchors with the anchors of its own in this embodiment. After initialization has been finished, data of at least one database DB and terminal TE defined in the syn-chronization initialization can be synchronized.
[0031] If the Last anchors do not correspond to each other accord-ing to the comparison 506, an error has occurred and the data of all the data-bases under synchronization need to be synchronized 508. Step 508 is also performed if the data of the databases of the S and the TE have not been synchronized earlier or if the memory MEM, SMEM has been cleared, in which case the Last anchor indicates the value `empty'. In that case the S can give information on unsuccessful synchronization or preferably send an initialization message according to which slow synchronization is started.
[0032] After synchronization (507 or 508) has been performed, the synchronization session and the transport layer connection are ended 509.
After this, the contents of the stored Last anchors are updated in the server S
511 and in the terminal TE 510 with the contents of the Next anchor of the present synchronization session if synchronization has been performed and the transport layer connection has been ended properly (cf. step 411, 412).
[0033] It should be noted that the functions illustrated in Figures 4 and 5 can be utilized in synchronization between more than two devices, in which case the Next and the Last anchors can be transmitted between all de-vices. The Last anchor is updated with a new value if synchronization has been performed between all the devices and the transport layer connections have been ended properly.
[0034] Unlike in Figures 4 and 5, synchronization can also be started without separate initialization messages. In that case initialization is performed simultaneously with synchronization. After the synchronization ses-sion and the transport layer connection have been ended, the Next anchors of the synchronization session can be updated as the value of the Last anchors in the memory MEM, SMEM, as described above. In that case the number of messages to be sent during synchronization can be reduced.
[0035] Figure 6 illustrates a signaling chart according to an em-bodiment of the invention, which resembles synchronization illustrated in Fig-ure 2. Slow synchronization is not needed in synchronization session I be-cause the Last synchronization anchors match, i.e. the Last anchor (9.9.2001, 09:09:09 AM) in the memory of the S corresponds to the received Last anchor.
5 [0012] The arrangement of the invention has the advantage that the devices which support the invention always update the update identifiers substantially simultaneously, which allows to minimize unnecessary slow synchronizations and avoid the disadvantages related to them. Using the timing according to the invention, it can be ensured in a reliable manner that the devices participating in synchronization always either update the update identifiers or not.
[0013] According to a preferred embodiment of the invention, synchronization is based on the synchronization protocol according to the SyncML standard, and thus the first update identifier is the Last anchor of synchronization and the second update identifier is the Next anchor.
[0013A] In one aspect of the present invention there is provided a method of arranging synchronization of databases, the method comprising the steps of:
establishing a transport layer connection for synchronization between a first and a second device which synchronize databases;
transmitting a first update identifier, which is stored at least in the first device and describes the latest synchronization event the first and the second device have performed in the databases, during initialization of synchronization from the first device to the second device, and a second update identifier, which is defined by the first device and describes the present synchronization;
storing said second update identifier in the first device and in the second device; and updating the contents of the first update identifiers stored in the devices with the contents of said second update identifier in the first device and in the second device if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013B] In yet another aspect of the present invention there is provided a synchronization system for synchronizing databases comprising a 5a first device and a second device which perform synchronization and are arranged to:
establish a transport layer connection between the first device and the second device for performing synchronization;
transmit a first update identifier, which is stored at least in the first device and describes the latest synchronization event the first and the second device have performed in the databases, from the first device to the second device during initialization of synchronization and a second update identifier, which is defined by the first device and describes the present synchronization;
store said second update identifier; and update the contents of the first update identifiers stored in the devices with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013C] In yet another aspect of the present invention there is provided a telecommunications device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
means for transmitting a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization, the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013D] In yet another aspect of the present invention there is provided a synchronization device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
5b means for receiving a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the first update identifier with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013E] In yet another aspect of the present invention there is provided a computer program product loadable into the memory of a telecommunications device and comprising code embodied thereon which is executable in the telecommunications device to cause the telecommunications device to:
establish a transport layer connection to at least one other device for synchronizing databases;
transmit a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization, the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
store said second update identifier; and update the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013F] In yet another aspect of the present invention, there is provided a computer program product loadable into the memory of a computer functioning as a synchronization device and comprising code embodied thereon which is executable in the synchronization device to cause the synchronization device to:
5c establish a transport layer connection to at least one other device for synchronizing databases;
receive a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
store the second update identifier; and update the contents of the first update identifier stored in said synchronization device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013G] In yet another aspect of the present invention there is provided a telecommunications device configured to:
establish a transport layer connection to at least one other device for synchronizing databases;
transmit a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization; the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
store said second update identifier; and update the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
[0013H] In yet another aspect of the present invention there is provided a synchronization device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
5d means for receiving a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the first update identifier with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The invention will be described in greater detail by means of preferred embodiments with reference to the accompanying drawings, in which Figure 1 illustrates synchronization according to the SyncML
synchronization protocol;
Figure 2 illustrates use of synchronization anchors;
Figure 3 illustrates a wireless network and a local area network;
Figure 4 illustrates a method according to a preferred embodiment of the invention;
Figure 5 illustrates a method according to another preferred embodiment of the invention; and Figure 6 is a signalling chart illustrating signalling events according to preferred embodiments of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0015] In the following, the preferred embodiment of the invention will be described in a system supporting the SyncML standard without limiting the invention thereto.
[0016] Figure 3 illustrates a networked system where data of databases DB and terminals TE can be synchronized. In respect of synchronization the terminal TE functions as a client device. Figure 3 shows two examples pies. In the first one there are terminals TE, databases DB and synchroniza-tion servers S connected to a local area network LAN. The terminal TE con-nected to the network LAN comprises a functionality for communicating with the devices of the network LAN, e.g. a network card and software which con-trols data transmission. The local area network LAN can be a local area net-work of any type and the TE can also communicate with the server S via the Internet, typically using a firewall FW. In the second example a terminal TE, a synchronization server S and databases DB are connected to a mobile net-work MNW. The terminal TE connected to the network MNW comprises a mo-bile station functionality for communicating wirelessly with the network MNW.
The mobile network MNW can be any prior art wireless network, such as a network which supports the GSM service, a network which supports the GPRS
service (General Packet Radio Service), a third-generation mobile communica-tion network, such as a UMTS network (Universal Mobile Telecommunications System), a wireless local area network WLAN or a private network. It should be noted that the server S can also function as a database DB, even though in Figure 3 the servers S and the databases DB are shown separately for the sake of clarity.
[0017] The terminals TE (in wired networks LAN and in wireless networks MNW) and the servers comprise memory MEM; SMEM, a user inter-face UI; SUI, 1/O means I/O; SI/O for arranging data transmission and a cen-tral processing unit CPU; SCPU which comprises one or more processors.
The memory MEM; SMEM includes a non-volatile portion of the central proc-essing unit CPU; SCPU for storing controlling applications and a random ac-cess memory portion for data processing. The memory MEM of the TE (which in this example is the database to be synchronized) and the memory of the databases DB store application data which are to be synchronized. A client agent SA operating according to the invention is preferably implemented by running a computer program code stored in the memory MEM in the CPU. The synchronization server S also provides a synchronization agent SA and a syn-chronization block SE according to the invention preferably by running a com-puter program code stored in the memory SMEM in the SCPU. The computer program code executable in the central processing unit CPU and SCPU
makes the terminal TE and the synchronization server S implement the inven-tive means. Embodiments of these means are illustrated in Figures 4 and 5.
The computer programs can be obtained via the network and/or stored in memory means, such as a floppy disk, CD ROM or other external memory means from which they can be loaded into the memory MEM, SMEM. Inte-grated circuits can also be used.
[0018] Figure 4 illustrates a synchronization method according to an embodiment of the invention where the terminal TE initiates synchronization with the server S. When there is need 401 to synchronize data of the data-bases (e.g. MEM, DB), a transport layer connection is established 402 be-tween the server S and the TE. The TE retrieves 403 the Last anchor updated after the preceding synchronization session from its memory MEM and defines 403 a Next anchor, e.g. checks the date and time. The Last and Next anchors are typically sequence numbers or time stamps. The anchors are database-specific, i.e. they indicate when the data of the database concerned have been updated. The TE also defines a Next anchor for synchronization and stores it temporarily in the random access memory section of the memory MEM. The TE transmits 404 a client initialization message to the server S. The Alert ele-ments of the message (for each database to be synchronized) comprise a Last anchor and a Next anchor. The client initialization message also informs the synchronization server S of the databases the data of which are to be syn-chronized and what type of synchronization is to be used. The client initializa-tion message typically also includes authentication information and information on the services and device features supported by the terminal TE.
[0019] The server S receives the client initialization message, stores the Next anchor temporarily in the random access memory section of the memory SMEM and retrieves 405 the stored Last anchor from its memory SMEM (which is the contents of the Next anchor of the last/preceding syn-chronization session stored preferably in the field labelled Last anchor). The S
checks 406 the Last anchor received and the Last anchor retrieved from its memory. After 407 the check 406 the server S sends a server initialization message containing the Next anchor (received from the TE) and the Last an-chor (from the memory SMEM of the server S) to the terminal TE, too. The server initialization message includes information on whether the time stamps correspond to each other. The TE checks 408 correspondence of the Last an-chors by comparing the Last anchor received with the Last anchor stored in the memory MEM.
[0020] If both the check 408 carried out by the TE and the check 406 carried out by the S indicate that the Last anchors correspond to each other, synchronization can be initiated 410 in the requested manner, in which case only the data units modified after the Last anchor need to be synchro-nized. After initialization has been finished, the data of at least one database DB defined in initialization of synchronization and data of the terminal TE
can be synchronized. The necessary authentications can be performed (in the case of two-way synchronization) employing SyncML messages illustrated in Figure 1 (Client Modifications, Server Modifications).
The type of synchronization can be e.g.
Two-way sync One-way sync from client only Refresh sync from client only One-way sync from server only Refresh sync from server only Server alerted sync [0021] As regards a more detailed description of the initialization of synchronization session and data synchronization 407, reference is made to the standard SyncML Sync Protocol, version 1.0, December 2000, which de-fines the SyncML synchronization protocol.
[0022] If the Last anchors do not match according to the compari-son 406 and/or 408, an error has occurred and all the data of the databases under synchronization need to be synchronized. After the comparison 406 the S can give information on unsuccessful synchronization or more preferably send an initialization message according to which slow synchronization is started 409. The TE can also request slow sync if the Last anchors do not cor-respond to each other according to the comparison 408.
[0023] Next it is checked 411 whether synchronization has been performed and the transport layer connection ended properly. Synchronization has been performed after all the data needed according to the synchronization type have been transferred between the TE and the S (neither has anything to transmit) and neither of the devices waits for an acknowledgement from the other. In the case of two-way synchronization, for example, synchronization has been performed when the server S acknowledges (Map Acknowledge-ment from Server) to the terminal TE that it has received the modifications made by the TE (Data Update Status Package for Server) and the TE receives the acknowledgement it has been waiting for. The connection has not been ended properly if, for example, the TE or the S receives an error message, an erroneous transport layer message or does not receive the message it is wait-ing for (in which case the TE/S can send an error message).
[0024] The SyncML synchronization protocol can be implemented between the TE and the S on top of the HTTP protocol (Hyper Text Transfer Protocol), the WSP protocol (Wireless Session Protocol) of the WAP standard (Wireless Application Protocol), the OBEX protocol used for cable connec-tions, such as USB (Universal Serial Bus) or RS-232, for short-range radio frequency connections (Bluetooth) or for infrared connections (IrDA), the TCP/IP stack (Transport Control Protocol/Internet Protocol) and on top of the transport layer service which offered by the e-mail protocol (SMTP, Simple Mail Transfer Protocol). Transfer at the lower layer can be performed accord-ing to the underlying network using e.g. short messages SMS or other signal-ing type transmission methods (e.g. USSD; Unstructured Supplementary Ser-vice Data), circuit-switched data calls or packet-switched data transfer ser-vices.
[0025] According to an embodiment, the HTTP protocol is used for providing a transport layer connection. In that case the connection has been ended properly after a 'HTTP request' message of the HTTP protocol, which includes last acknowledgements of the SyncML session, which require no re-sponse, and in response to which an acknowledgement message 'HTTP
status response' received in the device that transmitted the finish message has been transmitted, has been transferred between the devices. For exam-ple, the TE can send a `HTTP request' message which includes the last mes-sage (Data Update Status Package for Server) to which no acknowledgement is required (i.e. synchronization has been performed). The S responds by transmitting a 'HTTP status response' message, after which it can update 412 the contents of the Last anchor. If the TE receives the last correct `HTTP
status response' message (ok in the HTTP header 200) from the server S, it can update 412 the contents of the Last anchor.
[0026] According to an embodiment, the OBEX protocol is used to offer the transport layer connection. In that case the connection has been ended properly when a `disconnect' command in accordance with the OBEX
protocol has been transferred between the devices and a 'response' command related to the 'disconnect' command has been transmitted and received.
[0027] According to another embodiment, the WSP protocol is used to offer the transport layer connection. In that case the connection has been ended properly if a `disconnect request' message has been transferred be-tween the devices and a `disconnect indication' message related to the 'dis-connect request' message has been transmitted and received.
[0028] The contents of the previous Last anchors are updated 412 5 in the server S and the terminal TE (the contents can also be zero or empty if the Last anchor has not been stored earlier) with the contents of the Next an-chor of the present synchronization session if synchronization has been per-formed and the transport layer connection has been ended properly. The memory MEM, SMEM preferably includes one record in which the Last anchor 10 is maintained for the next synchronization. It is also possible that the value of the preceding Last anchor is not deleted but update 412 is performed by add-ing a record with a new value to the memory and by using it in the next syn-chronization. Thus the values stored in step 412 can be used 414 during the next synchronization, that is to say, the initiating party can send the value stored in the memory as the Last anchor and the receiving party can retrieve the stored value from its memory for comparison.
[0029] If synchronization has not been finished and/or the transport layer connection has not been ended properly, the values of the Last anchors stored in the memory are not changed 413 and the Next anchors stored tem-porarily are rejected.
[0030] Figure 5 illustrates synchronization according to another embodiment of the invention. When there is need 501 to synchronize data, a transport layer connection is established 502 between the server S and the TE. The TE retrieves 503 the Last anchor updated after the preceding syn-chronization session from its memory MEM and determines 503 a Next an-chor. The TE sends 504 to the server S an initialization message of synchroni-zation session which comprises the Last and the Next anchor defined. The S
receives the initialization message, stores the Next anchor temporarily and retrieves 505 the stored Last anchor (which is the contents of the Next anchor of preceding synchronization) from its memory SMEM. The S compares 506 the received Last anchor with the Last anchor it has retrieved from its memory.
If they correspond to each other, synchronization 507 can be implemented in the manner requested by the TE and only the data units modified after the Last anchor need to be synchronized. In that case the S can send an initializa-tion message to the TE, which indicates that synchronization can be carried out in the requested manner. Even though the S typically always sends the Last and the Next anchors to the TE, the TE does not compare these anchors with the anchors of its own in this embodiment. After initialization has been finished, data of at least one database DB and terminal TE defined in the syn-chronization initialization can be synchronized.
[0031] If the Last anchors do not correspond to each other accord-ing to the comparison 506, an error has occurred and the data of all the data-bases under synchronization need to be synchronized 508. Step 508 is also performed if the data of the databases of the S and the TE have not been synchronized earlier or if the memory MEM, SMEM has been cleared, in which case the Last anchor indicates the value `empty'. In that case the S can give information on unsuccessful synchronization or preferably send an initialization message according to which slow synchronization is started.
[0032] After synchronization (507 or 508) has been performed, the synchronization session and the transport layer connection are ended 509.
After this, the contents of the stored Last anchors are updated in the server S
511 and in the terminal TE 510 with the contents of the Next anchor of the present synchronization session if synchronization has been performed and the transport layer connection has been ended properly (cf. step 411, 412).
[0033] It should be noted that the functions illustrated in Figures 4 and 5 can be utilized in synchronization between more than two devices, in which case the Next and the Last anchors can be transmitted between all de-vices. The Last anchor is updated with a new value if synchronization has been performed between all the devices and the transport layer connections have been ended properly.
[0034] Unlike in Figures 4 and 5, synchronization can also be started without separate initialization messages. In that case initialization is performed simultaneously with synchronization. After the synchronization ses-sion and the transport layer connection have been ended, the Next anchors of the synchronization session can be updated as the value of the Last anchors in the memory MEM, SMEM, as described above. In that case the number of messages to be sent during synchronization can be reduced.
[0035] Figure 6 illustrates a signaling chart according to an em-bodiment of the invention, which resembles synchronization illustrated in Fig-ure 2. Slow synchronization is not needed in synchronization session I be-cause the Last synchronization anchors match, i.e. the Last anchor (9.9.2001, 09:09:09 AM) in the memory of the S corresponds to the received Last anchor.
12 After the server S has sent an acknowledgement (OK), data can be synchro-nized. The acknowledgement is preferably an initialization message which also includes a Last anchor and a Next anchor. After the synchronization session 1 has been finished, a transport failure occurs in the example due to an error in data transmission or due to non-uniform function of the devices (TE waits for an acknowledgement from the server S). According to the invention, neither the terminal TE nor the server S has updated a new value for the Last anchor in its memory. In synchronization session 2 the TE sends 9.10.2001, 09:09:09 AM as the value of the Last anchor. The Last anchor stored in the memory of the server S and the Last anchor received from the terminal TE correspond to each other, and thus synchronization session 2 can be performed without slow synchronization. This allows to avoid slow synchronization due to a transport failure according to the prior art shown in Figure 2.
[0036] It will be obvious to a person skilled in the art that as the technology advances, the inventive concept can be implemented in a number of ways. The invention and its embodiments are thus not limited to the exam-ples described above but may vary within the scope of the claims.
[0036] It will be obvious to a person skilled in the art that as the technology advances, the inventive concept can be implemented in a number of ways. The invention and its embodiments are thus not limited to the exam-ples described above but may vary within the scope of the claims.
Claims (15)
1. A method of arranging synchronization of databases, the method comprising the steps of:
establishing a transport layer connection for synchronization between a first and a second device which synchronize databases;
transmitting a first update identifier, which is stored at least in the first device and describes the latest synchronization event the first and the second device have performed in the databases, during initialization of synchronization from the first device to the second device, and a second update identifier, which is defined by the first device and describes the present synchronization;
storing said second update identifier in the first device and in the second device; and updating the contents of the first update identifiers stored in the devices with the contents of said second update identifier in the first device and in the second device if synchronization has been performed and after this said transport layer connection has been ended properly.
establishing a transport layer connection for synchronization between a first and a second device which synchronize databases;
transmitting a first update identifier, which is stored at least in the first device and describes the latest synchronization event the first and the second device have performed in the databases, during initialization of synchronization from the first device to the second device, and a second update identifier, which is defined by the first device and describes the present synchronization;
storing said second update identifier in the first device and in the second device; and updating the contents of the first update identifiers stored in the devices with the contents of said second update identifier in the first device and in the second device if synchronization has been performed and after this said transport layer connection has been ended properly.
2. A method according to claim 1, which further comprises the steps of:
comparing the first update identifier received in the second device with the first update identifier stored in the second device;
performing synchronization in the requested manner if the first received update identifier corresponds to the first stored update identifier; and synchronizing all data units of the databases if the first received update identifier does not correspond to the first stored update identifier.
comparing the first update identifier received in the second device with the first update identifier stored in the second device;
performing synchronization in the requested manner if the first received update identifier corresponds to the first stored update identifier; and synchronizing all data units of the databases if the first received update identifier does not correspond to the first stored update identifier.
3. A method according to claim 2, which further comprises the steps of:
transmitting the first stored update identifier from the second device to the first device; and comparing also the first received update identifier with the first stored update identifier in the first device.
transmitting the first stored update identifier from the second device to the first device; and comparing also the first received update identifier with the first stored update identifier in the first device.
4. A method according to claim 1, wherein the update identifiers indicate the date and time.
5. A method according to claim 1, wherein synchronization is based on a synchronization protocol according to the SyncML standard, the first update identifier being the Last anchor of synchronization and the second update identifier the Next anchor.
6. A method according to claim 1, wherein said transport layer connection is a logical connection in accordance with the HTTP protocol, and said transport layer connection has been ended properly if a 'HTTP request' message has been transferred between the first device and the second device after synchronization and a 'HTTP status response' message related to the 'HTTP request' message has been transmitted and received.
7. A synchronization system for synchronizing databases comprising a first device and a second device which perform synchronization and are arranged to:
establish a transport layer connection between the first device and the second device for performing synchronization;
transmit a first update identifier, which is stored at least in the first device and describes the latest synchronization event the first and the second device have performed in the databases, from the first device to the second device during initialization of synchronization and a second update identifier, which is defined by the first device and describes the present synchronization;
store said second update identifier; and update the contents of the first update identifiers stored in the devices with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
establish a transport layer connection between the first device and the second device for performing synchronization;
transmit a first update identifier, which is stored at least in the first device and describes the latest synchronization event the first and the second device have performed in the databases, from the first device to the second device during initialization of synchronization and a second update identifier, which is defined by the first device and describes the present synchronization;
store said second update identifier; and update the contents of the first update identifiers stored in the devices with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
8. A synchronization system according to claim 7, wherein the second device is arranged to compare the first update identifier received with the first update identifier stored in the second device, the first and the second device are arranged to perform synchronization in the requested manner if the first received update identifier corresponds to the first stored update identifier, or the first device and the second device are arranged to synchronize all data units of the databases if the first received update identifier does not correspond to the first stored update identifier.
9. A telecommunications device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
means for transmitting a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization, the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
means for establishing a transport layer connection to at least one other device for synchronizing databases;
means for transmitting a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization, the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
10. A synchronization device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
means for receiving a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the first update identifier with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
means for establishing a transport layer connection to at least one other device for synchronizing databases;
means for receiving a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the first update identifier with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
11. A synchronization device according to claim 10, which also comprises:
means for comparing the first update identifier received with the first update identifier stored in said synchronization device;
means for performing synchronization in the manner requested by the other device if the first received update identifier corresponds to the first stored update identifier; and means for synchronizing data units of all databases if the first received update identifier does not correspond to the first stored update identifier.
means for comparing the first update identifier received with the first update identifier stored in said synchronization device;
means for performing synchronization in the manner requested by the other device if the first received update identifier corresponds to the first stored update identifier; and means for synchronizing data units of all databases if the first received update identifier does not correspond to the first stored update identifier.
12. A computer program product loadable into the memory of a telecommunications device and comprising code embodied thereon which is executable in the telecommunications device to cause the telecommunications device to:
establish a transport layer connection to at least one other device for synchronizing databases;
transmit a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization, the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
store said second update identifier; and update the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
establish a transport layer connection to at least one other device for synchronizing databases;
transmit a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization, the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
store said second update identifier; and update the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
13. A computer program product loadable into the memory of a computer functioning as a synchronization device and comprising code embodied thereon which is executable in the synchronization device to cause the synchronization device to:
establish a transport layer connection to at least one other device for synchronizing databases;
receive a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
store the second update identifier; and update the contents of the first update identifier stored in said synchronization device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
establish a transport layer connection to at least one other device for synchronizing databases;
receive a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
store the second update identifier; and update the contents of the first update identifier stored in said synchronization device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
14. A telecommunications device configured to:
establish a transport layer connection to at least one other device for synchronizing databases;
transmit a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization; the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
store said second update identifier; and update the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
establish a transport layer connection to at least one other device for synchronizing databases;
transmit a first update identifier and a second update identifier defined by said telecommunications device to the other device during initialization of synchronization; the first update identifier being stored at least in said telecommunications device and describing the latest synchronization event said telecommunications device and the other device have performed in the databases, and said second update identifier describing the present synchronization;
store said second update identifier; and update the contents of the first update identifier stored in said telecommunications device with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
15. A synchronization device comprising:
means for establishing a transport layer connection to at least one other device for synchronizing databases;
means for receiving a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the first update identifier with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
means for establishing a transport layer connection to at least one other device for synchronizing databases;
means for receiving a first update identifier and a second update identifier from the other device during initialization of synchronization, the first update identifier describing the latest synchronization event said synchronization device and the other device have performed in the databases, and the second update identifier describing the present synchronization;
means for storing said second update identifier; and means for updating the first update identifier with the contents of said second update identifier if synchronization has been performed and after this said transport layer connection has been ended properly.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US09/842,568 | 2001-04-25 | ||
| US09/842,568 US6839564B2 (en) | 2001-04-25 | 2001-04-25 | Synchronization of database data |
| PCT/FI2002/000339 WO2002086758A1 (en) | 2001-04-25 | 2002-04-24 | Synchronization of database data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2447821A1 CA2447821A1 (en) | 2002-10-31 |
| CA2447821C true CA2447821C (en) | 2010-11-23 |
Family
ID=25287663
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2447821A Expired - Lifetime CA2447821C (en) | 2001-04-25 | 2002-04-24 | Synchronization of database data |
Country Status (10)
| Country | Link |
|---|---|
| US (2) | US6839564B2 (en) |
| EP (1) | EP1390874B1 (en) |
| JP (2) | JP2004534994A (en) |
| KR (1) | KR100937163B1 (en) |
| CN (1) | CN100371929C (en) |
| BR (1) | BRPI0209171B1 (en) |
| CA (1) | CA2447821C (en) |
| EE (1) | EE200300518A (en) |
| WO (1) | WO2002086758A1 (en) |
| ZA (1) | ZA200308298B (en) |
Families Citing this family (153)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7039656B1 (en) * | 1999-10-20 | 2006-05-02 | Yodlee.Com, Inc. | Method and apparatus for synchronizing data records between a remote device and a data server over a data-packet-network |
| US20020184234A1 (en) * | 2001-06-01 | 2002-12-05 | Lundberg Steven W. | Internet-based patent and trademark applicaton management system |
| WO2002087188A1 (en) * | 2001-04-19 | 2002-10-31 | Nokia Corporation | Method and system for privacy preferences management using a synchronisation protocol |
| US20030028577A1 (en) * | 2001-04-30 | 2003-02-06 | Chia-Chu Dorland | HTTP distributed XML-based automated event polling for network and E-service management |
| US7653631B1 (en) * | 2001-05-10 | 2010-01-26 | Foundationip, Llc | Method for synchronizing information in multiple case management systems |
| FI114417B (en) | 2001-06-15 | 2004-10-15 | Nokia Corp | Select data for synchronization |
| US7320011B2 (en) | 2001-06-15 | 2008-01-15 | Nokia Corporation | Selecting data for synchronization and for software configuration |
| US20040093342A1 (en) * | 2001-06-27 | 2004-05-13 | Ronald Arbo | Universal data mapping system |
| US8107937B2 (en) * | 2001-07-31 | 2012-01-31 | Nokia Corporation | System and method for automatic provisioning detection and notification |
| US7149813B2 (en) * | 2001-08-14 | 2006-12-12 | Microsoft Corporation | Method and system for synchronizing mobile devices |
| US7203505B1 (en) * | 2001-08-30 | 2007-04-10 | Nokia Corporation | Message transfer from a source device via a mobile terminal device to a third device |
| US20030045311A1 (en) * | 2001-08-30 | 2003-03-06 | Tapani Larikka | Message transfer from a source device via a mobile terminal device to a third device and data synchronization between terminal devices |
| FR2829330B1 (en) * | 2001-08-31 | 2003-11-28 | Canon Kk | METHOD FOR REQUESTING RECEIPT OF THE RESULT OF EXECUTION OF A REMOTE FUNCTION ON A PREDETERMINED DATE |
| US7570668B2 (en) * | 2001-10-03 | 2009-08-04 | Nokia Corporation | Data synchronization |
| KR100421624B1 (en) * | 2001-11-02 | 2004-03-11 | (주) 한정문 | Platform Independent Software Automatic Searching/Distribution/Install Apparatus and The method of Searching and Distribution for that apparatus |
| US20030093435A1 (en) * | 2001-11-05 | 2003-05-15 | Bandekar Vijay R. | Method and system for application level data object synchronization between two or more processes |
| US20030087089A1 (en) * | 2001-11-08 | 2003-05-08 | Rodriguez Peter A. | Roll of adhesive labels for cutting tape |
| AU2003209194A1 (en) | 2002-01-08 | 2003-07-24 | Seven Networks, Inc. | Secure transport for mobile communication network |
| US6721871B2 (en) | 2002-04-02 | 2004-04-13 | Nokia Corporation | Method and apparatus for synchronizing data stores with respect to changes in folders |
| US7076567B1 (en) * | 2002-04-25 | 2006-07-11 | Oracle International Corporation | Simplified application object data synchronization for optimized data storage |
| US7606881B2 (en) * | 2002-04-25 | 2009-10-20 | Oracle International Corporation | System and method for synchronization of version annotated objects |
| US20040039755A1 (en) * | 2002-06-05 | 2004-02-26 | Matthew Kunze | Metadata relationships |
| EP1518381B1 (en) * | 2002-06-28 | 2007-10-24 | Nokia Corporation | Method and device for retrieving data store access information |
| US7787489B2 (en) * | 2002-10-07 | 2010-08-31 | Oracle International Corporation | Mobile data distribution |
| FI114245B (en) * | 2002-11-13 | 2004-09-15 | Nokia Corp | Organizing a synchronization session |
| US7171421B2 (en) * | 2002-11-26 | 2007-01-30 | General Electric Company | System for automating operating parameter list process |
| WO2004051509A1 (en) * | 2002-12-04 | 2004-06-17 | Nokia Corporation | Selecting data for synchronization and for software configuration |
| US20040127242A1 (en) * | 2002-12-31 | 2004-07-01 | Dashevsky Jane Y. | Apparatus and associated methods for the synchronization of shared content |
| US7917468B2 (en) | 2005-08-01 | 2011-03-29 | Seven Networks, Inc. | Linking of personal information management data |
| US7853563B2 (en) | 2005-08-01 | 2010-12-14 | Seven Networks, Inc. | Universal data aggregation |
| US8468126B2 (en) | 2005-08-01 | 2013-06-18 | Seven Networks, Inc. | Publishing data in an information community |
| US7613797B2 (en) * | 2003-03-19 | 2009-11-03 | Unisys Corporation | Remote discovery and system architecture |
| JP2004318828A (en) * | 2003-03-31 | 2004-11-11 | Seiko Epson Corp | Data backup system, data backup method, wearable computer, mail transmission system, image information transmission system and data backup program |
| US7216133B2 (en) * | 2003-07-29 | 2007-05-08 | Microsoft Corporation | Synchronizing logical views independent of physical storage representations |
| KR100585748B1 (en) * | 2003-11-27 | 2006-06-07 | 엘지전자 주식회사 | Synchronization method and system for telephone number |
| GB2409545A (en) * | 2003-12-24 | 2005-06-29 | Nokia Corp | File synchronisation |
| US7437484B2 (en) * | 2003-12-29 | 2008-10-14 | International Business Machines Corporation | Method for optimizing synchronization |
| US20050197747A1 (en) * | 2004-03-04 | 2005-09-08 | Jason Rappaport | In-vehicle computer system |
| JP2005309968A (en) * | 2004-04-23 | 2005-11-04 | Kyosan Electric Mfg Co Ltd | Newest information display system and train operation display system using it |
| US20060047837A1 (en) * | 2004-06-14 | 2006-03-02 | Jukka-Pekka Rissanen | Arrangement for informing application capabilities by an object exchange protocol |
| JP2006018895A (en) * | 2004-06-30 | 2006-01-19 | Sony Corp | Content transfer system, content storage system, content storage device, and content storage method |
| US7533074B2 (en) * | 2004-07-23 | 2009-05-12 | Sap Ag | Modifiable knowledge base in a mobile device |
| JP4091095B2 (en) * | 2004-08-06 | 2008-05-28 | シャープ株式会社 | Transmitter, receiver, communication system, communication method, communication program |
| JP4529612B2 (en) * | 2004-09-21 | 2010-08-25 | 株式会社セガ | Method for reducing communication charges when using application programs on mobile devices |
| US8775650B2 (en) * | 2004-10-29 | 2014-07-08 | Core Wireless Licensing S.A.R.L. | Memory association to folder information |
| KR100902341B1 (en) * | 2005-01-28 | 2009-06-12 | 샤프 가부시키가이샤 | Communication device, communication system, communication method, computer-readable recording media having communication program recorded therein, and communication circuit |
| US8291273B2 (en) * | 2005-01-28 | 2012-10-16 | Sharp Kabushiki Kaisha | Communication device, non-transitory computer-readable medium storing a communication program |
| US8051182B2 (en) * | 2005-01-28 | 2011-11-01 | Sharp Kabushiki Kaisha | Communication device, communication system, communication method, communication program, and communication circuit |
| US7787391B2 (en) * | 2005-01-28 | 2010-08-31 | Sharp Kabushiki Kaisha | Communication device, communication system, communication method, communication program, and communication circuit |
| US7752633B1 (en) | 2005-03-14 | 2010-07-06 | Seven Networks, Inc. | Cross-platform event engine |
| US20060212489A1 (en) * | 2005-03-15 | 2006-09-21 | Eggers Michael R | Technique for effectively synchronizing data through an information service |
| EP1708095A1 (en) * | 2005-03-31 | 2006-10-04 | Ubs Ag | Computer network system for constructing, synchronizing and/or managing a second database from/with a first database, and methods therefore |
| US8438633B1 (en) | 2005-04-21 | 2013-05-07 | Seven Networks, Inc. | Flexible real-time inbox access |
| WO2006136660A1 (en) | 2005-06-21 | 2006-12-28 | Seven Networks International Oy | Maintaining an ip connection in a mobile network |
| US8001076B2 (en) * | 2005-07-12 | 2011-08-16 | International Business Machines Corporation | Ranging scalable time stamp data synchronization |
| US20070014307A1 (en) * | 2005-07-14 | 2007-01-18 | Yahoo! Inc. | Content router forwarding |
| US20070016636A1 (en) * | 2005-07-14 | 2007-01-18 | Yahoo! Inc. | Methods and systems for data transfer and notification mechanisms |
| US7623515B2 (en) * | 2005-07-14 | 2009-11-24 | Yahoo! Inc. | Content router notification |
| US7631045B2 (en) * | 2005-07-14 | 2009-12-08 | Yahoo! Inc. | Content router asynchronous exchange |
| US20070038703A1 (en) * | 2005-07-14 | 2007-02-15 | Yahoo! Inc. | Content router gateway |
| US7849199B2 (en) * | 2005-07-14 | 2010-12-07 | Yahoo ! Inc. | Content router |
| US7890508B2 (en) * | 2005-08-19 | 2011-02-15 | Microsoft Corporation | Database fragment cloning and management |
| US8015319B2 (en) * | 2005-10-27 | 2011-09-06 | Huawei Technologies Co., Ltd. | Method, system, client and server for implementing data sync |
| US20090262661A1 (en) * | 2005-11-10 | 2009-10-22 | Sharp Kabushiki Kaisha | Data transmission device and method of controlling same, data receiving device and method of controlling same, data transfer system, data transmission device control program, data receiving device control program, and storage medium containing the programs |
| US8024290B2 (en) | 2005-11-14 | 2011-09-20 | Yahoo! Inc. | Data synchronization and device handling |
| US8065680B2 (en) * | 2005-11-15 | 2011-11-22 | Yahoo! Inc. | Data gateway for jobs management based on a persistent job table and a server table |
| CN100452734C (en) * | 2005-11-17 | 2009-01-14 | 中国科学院计算技术研究所 | Global Internet topology knowledge-based P2P application construction method |
| CN100429891C (en) * | 2005-11-17 | 2008-10-29 | 乐金电子(中国)研究开发中心有限公司 | Data synchronization method |
| US7657575B2 (en) * | 2005-12-30 | 2010-02-02 | Sap Ag | Sequencing updates to business objects |
| US9367832B2 (en) * | 2006-01-04 | 2016-06-14 | Yahoo! Inc. | Synchronizing image data among applications and devices |
| KR100725414B1 (en) | 2006-02-07 | 2007-06-07 | 삼성전자주식회사 | Method and apparatus for creating identifier for synchronizing digital content |
| US7769395B2 (en) | 2006-06-20 | 2010-08-03 | Seven Networks, Inc. | Location-based operations and messaging |
| CN100450108C (en) * | 2006-03-23 | 2009-01-07 | 华为技术有限公司 | System, device and method for synchronously processing e-mail using data |
| KR100772879B1 (en) | 2006-04-19 | 2007-11-02 | 삼성전자주식회사 | Apparatus, system and method for executing discovery in network |
| KR100755715B1 (en) * | 2006-04-21 | 2007-09-05 | 삼성전자주식회사 | Method for synchronizing multiple cds devices, cds device, and system comprising the cds device |
| US20070297458A1 (en) * | 2006-06-27 | 2007-12-27 | Microsoft Corporation | Efficient and layered synchronization protocol for database systems |
| EP1883257A1 (en) * | 2006-07-28 | 2008-01-30 | Gemplus | Method for synchronisation between a mobile equipment and a smart card |
| US20080034008A1 (en) * | 2006-08-03 | 2008-02-07 | Yahoo! Inc. | User side database |
| US7860826B2 (en) * | 2006-08-04 | 2010-12-28 | Apple Inc. | Method and system for using global equivalency sets to identify data during peer-to-peer synchronization |
| JP4219950B2 (en) * | 2006-10-16 | 2009-02-04 | シャープ株式会社 | COMMUNICATION DEVICE, COMMUNICATION METHOD, COMMUNICATION CIRCUIT, MOBILE PHONE, PROGRAM, AND COMPUTER-READABLE RECORDING MEDIUM CONTAINING THE PROGRAM |
| US10255607B2 (en) * | 2006-11-15 | 2019-04-09 | Disney Enterprises, Inc. | Collecting consumer information |
| US20080155112A1 (en) * | 2006-12-22 | 2008-06-26 | Nokia Corporation | System and method for updating information feeds |
| US7805403B2 (en) * | 2007-01-07 | 2010-09-28 | Apple Inc. | Synchronization methods and systems |
| US7660831B2 (en) * | 2007-01-07 | 2010-02-09 | Apple Inc. | Synchronization methods and systems |
| US7778971B2 (en) * | 2007-01-07 | 2010-08-17 | Apple Inc. | Synchronization methods and systems |
| US7739410B2 (en) * | 2007-01-07 | 2010-06-15 | Apple Inc. | Synchronization methods and systems |
| US20080163743A1 (en) * | 2007-01-07 | 2008-07-10 | Freedman Gordon J | Synchronization methods and systems |
| US8239504B2 (en) * | 2007-01-07 | 2012-08-07 | Apple Inc. | Synchronization methods and systems |
| US7761414B2 (en) * | 2007-01-07 | 2010-07-20 | Apple Inc. | Asynchronous data synchronization amongst devices |
| JP2008226167A (en) * | 2007-03-15 | 2008-09-25 | Toshiba Corp | Data distribution system and data distribution program |
| US20080270629A1 (en) * | 2007-04-27 | 2008-10-30 | Yahoo! Inc. | Data snychronization and device handling using sequence numbers |
| US8693494B2 (en) | 2007-06-01 | 2014-04-08 | Seven Networks, Inc. | Polling |
| US8805425B2 (en) | 2007-06-01 | 2014-08-12 | Seven Networks, Inc. | Integrated messaging |
| US8209540B2 (en) * | 2007-06-28 | 2012-06-26 | Apple Inc. | Incremental secure backup and restore of user settings and data |
| CN100489787C (en) * | 2007-07-10 | 2009-05-20 | 北京大学 | Dummy machine external storage on-line migration method |
| CN101355726A (en) * | 2007-07-25 | 2009-01-28 | 国际商业机器公司 | Method and system for synchronizing data base based on multimedia information transference |
| CN101374144B (en) * | 2007-08-21 | 2012-04-25 | 华为技术有限公司 | Method, apparatus and system for controlling conversational data synchronization |
| US8073434B2 (en) * | 2007-09-18 | 2011-12-06 | Sap Ag | System and method of object simulation in an intermittently connected mobile application |
| US8364181B2 (en) | 2007-12-10 | 2013-01-29 | Seven Networks, Inc. | Electronic-mail filtering for mobile devices |
| US9002828B2 (en) | 2007-12-13 | 2015-04-07 | Seven Networks, Inc. | Predictive content delivery |
| US8862657B2 (en) | 2008-01-25 | 2014-10-14 | Seven Networks, Inc. | Policy based content service |
| US20090193338A1 (en) | 2008-01-28 | 2009-07-30 | Trevor Fiatal | Reducing network and battery consumption during content delivery and playback |
| US8787947B2 (en) | 2008-06-18 | 2014-07-22 | Seven Networks, Inc. | Application discovery on mobile devices |
| US8078158B2 (en) | 2008-06-26 | 2011-12-13 | Seven Networks, Inc. | Provisioning applications for a mobile device |
| US8135670B2 (en) * | 2008-07-22 | 2012-03-13 | International Business Machines Corporation | Embedded change logging for data synchronization |
| CN101639950B (en) * | 2008-07-29 | 2011-07-13 | 中兴通讯股份有限公司 | Method and device for synchronizing data in lane toll system |
| US8909759B2 (en) | 2008-10-10 | 2014-12-09 | Seven Networks, Inc. | Bandwidth measurement |
| US20100131513A1 (en) | 2008-10-23 | 2010-05-27 | Lundberg Steven W | Patent mapping |
| KR100935831B1 (en) * | 2008-11-17 | 2010-01-08 | 우용태 | A method for a data synchronizing based on a data structure which has multiple event identifier and the Data back up solution uses the method |
| US20100211544A1 (en) * | 2009-02-19 | 2010-08-19 | Jyshyang Chen | System with session synchronization |
| US20100268784A1 (en) * | 2009-04-17 | 2010-10-21 | Marc Henness | Data synchronization system and method |
| CN102271347A (en) * | 2010-06-01 | 2011-12-07 | 宏达国际电子股份有限公司 | Communication apparatus and method thereof |
| EP3651028A1 (en) | 2010-07-26 | 2020-05-13 | Seven Networks, LLC | Mobile network traffic coordination across multiple applications |
| US8838783B2 (en) | 2010-07-26 | 2014-09-16 | Seven Networks, Inc. | Distributed caching for resource and mobile network traffic management |
| US8484314B2 (en) | 2010-11-01 | 2013-07-09 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
| CN103620576B (en) | 2010-11-01 | 2016-11-09 | 七网络公司 | It is applicable to the caching of mobile applications behavior and network condition |
| US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
| US8903954B2 (en) | 2010-11-22 | 2014-12-02 | Seven Networks, Inc. | Optimization of resource polling intervals to satisfy mobile device requests |
| WO2012060995A2 (en) | 2010-11-01 | 2012-05-10 | Michael Luna | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
| CA2798523C (en) | 2010-11-22 | 2015-02-24 | Seven Networks, Inc. | Aligning data transfer to optimize connections established for transmission over a wireless network |
| CN102054035B (en) * | 2010-12-29 | 2013-01-02 | 北京播思软件技术有限公司 | Data range-based method for synchronizing data in database |
| GB2501416B (en) | 2011-01-07 | 2018-03-21 | Seven Networks Llc | System and method for reduction of mobile network traffic used for domain name system (DNS) queries |
| US8316098B2 (en) | 2011-04-19 | 2012-11-20 | Seven Networks Inc. | Social caching for device resource sharing and management |
| EP2702500B1 (en) | 2011-04-27 | 2017-07-19 | Seven Networks, LLC | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
| EP2621144B1 (en) | 2011-04-27 | 2014-06-25 | Seven Networks, Inc. | System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief |
| US9904726B2 (en) | 2011-05-04 | 2018-02-27 | Black Hills IP Holdings, LLC. | Apparatus and method for automated and assisted patent claim mapping and expense planning |
| WO2013015995A1 (en) | 2011-07-27 | 2013-01-31 | Seven Networks, Inc. | Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network |
| US20130086070A1 (en) * | 2011-10-03 | 2013-04-04 | Steven W. Lundberg | Prior art management |
| US20130086106A1 (en) | 2011-10-03 | 2013-04-04 | Black Hills Ip Holdings, Llc | Systems, methods and user interfaces in a patent management system |
| US20130097116A1 (en) * | 2011-10-17 | 2013-04-18 | Research In Motion Limited | Synchronization method and associated apparatus |
| US8934414B2 (en) | 2011-12-06 | 2015-01-13 | Seven Networks, Inc. | Cellular or WiFi mobile traffic optimization based on public or private network destination |
| US8868753B2 (en) | 2011-12-06 | 2014-10-21 | Seven Networks, Inc. | System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation |
| WO2013086455A1 (en) | 2011-12-07 | 2013-06-13 | Seven Networks, Inc. | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
| US9277443B2 (en) | 2011-12-07 | 2016-03-01 | Seven Networks, Llc | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
| WO2013090821A1 (en) | 2011-12-14 | 2013-06-20 | Seven Networks, Inc. | Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization |
| EP2792188B1 (en) | 2011-12-14 | 2019-03-20 | Seven Networks, LLC | Mobile network reporting and usage analytics system and method using aggregation of data in a distributed traffic optimization system |
| US9832095B2 (en) | 2011-12-14 | 2017-11-28 | Seven Networks, Llc | Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic |
| WO2013103988A1 (en) | 2012-01-05 | 2013-07-11 | Seven Networks, Inc. | Detection and management of user interactions with foreground applications on a mobile device in distributed caching |
| WO2013116856A1 (en) | 2012-02-02 | 2013-08-08 | Seven Networks, Inc. | Dynamic categorization of applications for network access in a mobile network |
| WO2013116852A1 (en) | 2012-02-03 | 2013-08-08 | Seven Networks, Inc. | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
| US8812695B2 (en) | 2012-04-09 | 2014-08-19 | Seven Networks, Inc. | Method and system for management of a virtual network connection without heartbeat messages |
| WO2013155208A1 (en) | 2012-04-10 | 2013-10-17 | Seven Networks, Inc. | Intelligent customer service/call center services enhanced using real-time and historical mobile application and traffic-related statistics collected by a distributed caching system in a mobile network |
| KR101333468B1 (en) * | 2012-04-25 | 2013-11-26 | 한국항공우주산업 주식회사 | Method for checking channel id of flight control computer and computer readable recording medium to store the computer program to run the same method |
| WO2014011216A1 (en) | 2012-07-13 | 2014-01-16 | Seven Networks, Inc. | Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications |
| US9161258B2 (en) | 2012-10-24 | 2015-10-13 | Seven Networks, Llc | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
| US9307493B2 (en) | 2012-12-20 | 2016-04-05 | Seven Networks, Llc | Systems and methods for application management of mobile device radio state promotion and demotion |
| US9241314B2 (en) | 2013-01-23 | 2016-01-19 | Seven Networks, Llc | Mobile device with application or context aware fast dormancy |
| US8874761B2 (en) | 2013-01-25 | 2014-10-28 | Seven Networks, Inc. | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
| US9326185B2 (en) | 2013-03-11 | 2016-04-26 | Seven Networks, Llc | Mobile network congestion recognition for optimization of mobile traffic |
| US9065765B2 (en) | 2013-07-22 | 2015-06-23 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
| US10243891B2 (en) * | 2014-08-14 | 2019-03-26 | Oath Inc. | Cross-device integration system and method |
| US10671640B2 (en) | 2017-06-02 | 2020-06-02 | Apple Inc. | Adaptive cross-device event data synchronization |
| KR20230152377A (en) | 2022-04-27 | 2023-11-03 | 한국전자통신연구원 | Data real-time synchronization system and method between multi-datahubs in open data environments |
Family Cites Families (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5274240A (en) * | 1990-01-12 | 1993-12-28 | The Regents Of The University Of California | Capillary array confocal fluorescence scanner and method |
| US5529679A (en) * | 1992-02-28 | 1996-06-25 | Hitachi, Ltd. | DNA detector and DNA detection method |
| US5516409A (en) * | 1991-02-28 | 1996-05-14 | Hitachi, Ltd. | DNA detector and DNA detection method |
| JPH04291556A (en) | 1991-03-20 | 1992-10-15 | Fujitsu Ltd | Communication control system |
| JP2785530B2 (en) * | 1991-09-13 | 1998-08-13 | 株式会社日立製作所 | Electrophoresis device |
| US5307487A (en) | 1991-10-03 | 1994-04-26 | The United States Of America As Represented By The Secretary Of The Navy | Method of database synchronization with consistency determined by entry and exit counters used on both update and retrieval |
| US5608720A (en) * | 1993-03-09 | 1997-03-04 | Hubbell Incorporated | Control system and operations system interface for a network element in an access system |
| US5730850A (en) * | 1993-04-23 | 1998-03-24 | Hitachi, Ltd. | Capillary array electrophoresis system |
| US5710922A (en) | 1993-06-02 | 1998-01-20 | Apple Computer, Inc. | Method for synchronizing and archiving information between computer systems |
| US5439578A (en) * | 1993-06-03 | 1995-08-08 | The Governors Of The University Of Alberta | Multiple capillary biochemical analyzer |
| JP2605673B2 (en) | 1994-06-06 | 1997-04-30 | 日本電気株式会社 | TDMA wireless communication system |
| US6515968B1 (en) * | 1995-03-17 | 2003-02-04 | Worldcom, Inc. | Integrated interface for real time web based viewing of telecommunications network call traffic |
| US5582705A (en) * | 1995-05-19 | 1996-12-10 | Iowa State University Research Foundation, Inc. | Multiplexed capillary electrophoresis system |
| US5943676A (en) * | 1996-11-13 | 1999-08-24 | Puma Technology, Inc. | Synchronization of recurring records in incompatible databases |
| WO1998024018A2 (en) | 1996-11-13 | 1998-06-04 | Puma Technology Inc. | Synchronization of databases |
| US5790727A (en) * | 1997-02-05 | 1998-08-04 | Brookhaven Science Associates Llc | Laser illumination of multiple capillaries that form a waveguide |
| US6173311B1 (en) * | 1997-02-13 | 2001-01-09 | Pointcast, Inc. | Apparatus, method and article of manufacture for servicing client requests on a network |
| CN1160970C (en) * | 1997-05-09 | 2004-08-04 | 美国阿尔卡塔尔资源有限合伙公司 | Communication system with rapid database synchronization |
| US6654785B1 (en) * | 1998-03-02 | 2003-11-25 | Hewlett-Packard Development Company, L.P. | System for providing a synchronized display of information slides on a plurality of computer workstations over a computer network |
| US6490617B1 (en) * | 1998-06-09 | 2002-12-03 | Compaq Information Technologies Group, L.P. | Active self discovery of devices that participate in a network |
| US6516314B1 (en) | 1998-11-17 | 2003-02-04 | Telefonaktiebolaget L M Ericsson (Publ) | Optimization of change log handling |
| US6266525B1 (en) * | 1998-12-17 | 2001-07-24 | Lucent Technologies Inc. | Method for detecting fraudulent use of a communications system |
| CN1262481A (en) | 1999-01-27 | 2000-08-09 | 电话通有限公司 | Method and device for synchronizing multiple data base |
| JP2000222268A (en) | 1999-01-29 | 2000-08-11 | Hitachi Ltd | Method for synchronizing file for plural computers |
| US20050192008A1 (en) * | 1999-03-31 | 2005-09-01 | Nimesh Desai | System and method for selective information exchange |
| WO2000074019A1 (en) * | 1999-06-01 | 2000-12-07 | Siemens Automotive Corporation | Portable driver information device |
| CA2276840A1 (en) * | 1999-07-05 | 2001-01-05 | Telefonaktiebolaget Lm Ericsson | Method and apparatus for synchronizing a database in portable communication devices |
| EP1109106A1 (en) * | 1999-12-14 | 2001-06-20 | Sun Microsystems, Inc. | Reference data base |
| US6643669B1 (en) | 2000-03-14 | 2003-11-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for optimization of synchronization between a client's database and a server database |
| US7035932B1 (en) * | 2000-10-27 | 2006-04-25 | Eric Morgan Dowling | Federated multiprotocol communication |
-
2001
- 2001-04-25 US US09/842,568 patent/US6839564B2/en not_active Expired - Lifetime
-
2002
- 2002-04-24 BR BRPI0209171A patent/BRPI0209171B1/en active IP Right Grant
- 2002-04-24 CA CA2447821A patent/CA2447821C/en not_active Expired - Lifetime
- 2002-04-24 WO PCT/FI2002/000339 patent/WO2002086758A1/en active Application Filing
- 2002-04-24 JP JP2002584207A patent/JP2004534994A/en active Pending
- 2002-04-24 EP EP02716869.9A patent/EP1390874B1/en not_active Expired - Lifetime
- 2002-04-24 EE EEP200300518A patent/EE200300518A/en unknown
- 2002-04-24 KR KR1020037013954A patent/KR100937163B1/en active IP Right Grant
- 2002-04-24 CN CNB028127773A patent/CN100371929C/en not_active Expired - Lifetime
-
2003
- 2003-10-24 ZA ZA2003/08298A patent/ZA200308298B/en unknown
-
2004
- 2004-11-18 US US10/991,697 patent/US7555303B2/en not_active Expired - Lifetime
-
2008
- 2008-11-20 JP JP2008296890A patent/JP2009110530A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| US6839564B2 (en) | 2005-01-04 |
| BR0209171A (en) | 2004-08-03 |
| CA2447821A1 (en) | 2002-10-31 |
| JP2004534994A (en) | 2004-11-18 |
| WO2002086758A1 (en) | 2002-10-31 |
| WO2002086758A8 (en) | 2003-01-16 |
| KR20040005933A (en) | 2004-01-16 |
| EP1390874A1 (en) | 2004-02-25 |
| US20020161769A1 (en) | 2002-10-31 |
| BRPI0209171B1 (en) | 2016-04-26 |
| US20050125459A1 (en) | 2005-06-09 |
| JP2009110530A (en) | 2009-05-21 |
| EP1390874B1 (en) | 2017-04-05 |
| ZA200308298B (en) | 2005-06-29 |
| CN1564990A (en) | 2005-01-12 |
| CN100371929C (en) | 2008-02-27 |
| KR100937163B1 (en) | 2010-01-15 |
| US7555303B2 (en) | 2009-06-30 |
| EE200300518A (en) | 2004-02-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2447821C (en) | Synchronization of database data | |
| US8171171B2 (en) | Data synchronization method and system between devices | |
| KR101011216B1 (en) | Data synchronization | |
| US6978453B2 (en) | System with required enhancements to syncML DM environment to support firmware updates | |
| KR100737996B1 (en) | A synchronization system, a synchronization server, a computer-readable medium storing a computer program loadable to the memory of the synchronization server, a method of starting a session in the synchronization system, and an electronic device in the synchronization system | |
| US5274762A (en) | Method for high speed data transfer | |
| US8190671B2 (en) | Arranging synchronization session | |
| US7570668B2 (en) | Data synchronization | |
| EP1980954A1 (en) | Method, device and system for synchronizing of data providing for the handling of an interrupted synchronization process | |
| WO2006087422A1 (en) | Method, electronic device and server for the obtaining of deployment components to electronic devices | |
| JP4494970B2 (en) | Method, apparatus, and system for synchronizing data in response to an interrupted synchronization process | |
| US20100077024A1 (en) | Method for transmitting data transmitted incompletely between server and client | |
| JP2001216187A (en) | Method and device for making data coincident among devices | |
| EP1257918B1 (en) | Data recovery in a distributed system | |
| WO1996017460A9 (en) | Methods and systems for preventing unnecessary file transfers between a server and a remote node |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry |
Effective date: 20220425 |