KR101082850B1 - Active Sync-based Mobile Device for data Synchronizing and Method at the same - Google Patents

Abstract

A mobile terminal for data synchronization with a server according to the present invention comprises: a protocol manager in charge of communication with the data synchronization server; Receives LUID and data for changed data by application program and converts data into hash value, compares hash value corresponding to the LUID from change log table, and if the two hash values are different, synchronize command and LUID and A synchronization message comprising a hash value is transmitted to the data synchronization server through the protocol manager. When a synchronization message is received from the data synchronization server, a synchronization command and LUID and data are analyzed from the synchronization message, and the data is hashed. A synchronization manager for converting the LUID and the hash value into the change log table after the conversion to the value, and reflecting the synchronization command and the LUID and data to the application program; A data store manager that reads an LUID and a hash value from the change log table and provides the LUID and a hash value to the synchronization manager, or receives the LUID and a hash value and registers the LUID and a hash value in the change log table; A datastore providing the change log table and a data storage area of the application program; Characterized in having a.

Description

Mobile terminal for data synchronization and method thereof {Active Sync-based Mobile Device for data Synchronizing and Method at the same}

The present invention relates to a synchronization technology for a mobile terminal, and more particularly, by using the SyncML data synchronization method, which is a standard synchronization method proposed by the Open Mobile Alliance (OMA), the data synchronization method provided by each terminal company is used as it is. The present invention relates to a mobile terminal and a method for enabling mutual synchronization with each other.

Recently, due to the development of mobile computing technology and hardware technology, mobile terminals are spreading very rapidly. In order for a user of the mobile terminal to use desired information regardless of time or place, data synchronization is required to synchronize the data of the central integrated server and the data of the mobile terminal.

SyncML is proposed to develop an open standard interface for data synchronization and device management that can be used for different platforms, communication protocols, data types, and application services of each manufacturer's terminal. The SyncML also becomes an de facto standard for data synchronization by adopting open standards and following a number of implementations.

The SyncML is designed for remote synchronization between a mobile terminal and a server, but may also be used for local synchronization and synchronization between devices connected to a wired network. While synchronization is performed between the client and server based on the SyncML, the object to be synchronized exchanges packages logically.

In addition, each package is separated and exchanged into multiple messages due to the limited resources of the mobile terminal and the low bandwidth in wireless communication. All packages sent and received between client and server for one complete data synchronization are called sessions. A session contains multiple packages, and one package contains multiple messages.

SyncML data synchronization standard consists of XML-based SyncML Data Representation protocol, SyncML Synchronization protocol, and SyncML Transport Bindings protocol. The SyncML data representation protocol defines the logical structure and form of SyncML messages exchanged for data synchronization in XML format. That is, each field defines what information it contains and what promises that information has. The SyncML synchronization protocol defines a method of exchanging messages for synchronization commands and other status information such as addition, deletion, and update of data generated by a data representation protocol specification made between a SyncML client and a server. Finally, the SyncML transport binding protocol is a protocol such as HTTP, WSP, OBEX, etc. that SyncML uses to transmit synchronization messages. The SyncML specification does not define a new protocol for the SyncML transport binding protocol. Define only rules.

The HotSync protocol is a data synchronization method that works with Palm OS-based devices. It uses a code module called Conduit to synchronize data between Palm OS devices and desktop computers. The Palm OS-based HotSync protocol does not disclose the technical specifications for the lower bearer. Therefore, Palm OS-based application software is being developed and supplied by companies with HotSync solutions. Companies such as XcelleNet, Mobile Automation, Pumatech, AdantGo and others provide solutions for HotSync.

HotSync client includes HotSync Manager, Conduit Module, Notifier DLL Module, Handheld App. Module, Desktop App. It consists of 6 components such as module and Sync Manager API. The Hotsync protocol supports two data synchronization modes, Slow-sync and Fast-sync, similar to the Two-way of SyncML protocol. Since Fast Sync is faster than Slow Sync, Fast Sync is given priority over Slow Sync.

Data synchronization solutions currently offered by major handset manufacturers exist, but lack the compatibility between each handset and its application services. Therefore, in order to guarantee the interoperability of the synchronization method provided by each mobile terminal company, in February 2000, various mobile terminal companies proposed the SyncML method by the Open Mobile Alliance (OMA), which attempted to openly standardize.

However, since handset makers are increasing their market share through technical competition, they do not provide a technical disclosure of each synchronization method. Therefore, although SyncML tries to standardize the synchronization solution, it is difficult for all mobile terminals equipped with each synchronization method to replace the SyncML method with synchronization standardization.

The present invention provides a mobile terminal capable of synchronizing with each other while using various data synchronization methods provided by a mobile terminal company by using a SyncML data synchronization method, which is a standard synchronization method proposed by the Open Mobile Alliance (OMA). Its purpose is to provide a method.

A mobile terminal according to the present invention for achieving the above object, the protocol manager in charge of communication with the data synchronization server; Receives LUID and data for changed data by application program and converts data into hash value, compares hash value corresponding to the LUID from change log table, and if the two hash values are different, synchronize command and LUID and A synchronization message comprising a hash value is transmitted to the data synchronization server through the protocol manager. When a synchronization message is received from the data synchronization server, a synchronization command and LUID and data are analyzed from the synchronization message, and the data is hashed. A synchronization manager for converting the LUID and the hash value into the change log table after the conversion to the value, and reflecting the synchronization command and the LUID and data to the application program; A data store manager that reads an LUID and a hash value from the change log table and provides the LUID and a hash value to the synchronization manager, or receives the LUID and a hash value and registers the LUID and a hash value in the change log table; A datastore providing the change log table and a data storage area of the application program; Characterized in having a.

According to the present invention, ActiveSync data synchronization objects mounted in WinCE or Window Mobile based mobile terminals lack mutual compatibility with mobile terminals equipped with different synchronization methods. However, the embedded data synchronization agent developed in the present invention can ensure mutual compatibility between different synchronization schemes.

In addition, since the present invention was developed based on the OMA DS SyncML protocol specification proposed by OMA, it complies with international standards, and contributes to the future adoption of OMA DS SyncML protocol as a global standard technology in data synchronization.

In addition, although the data synchronization gateway system of Patent Registration No. 100844361 (2008.07.01) is similar to the present invention, the system increases the amount of data to be processed simultaneously by the synchronization request received from several terminals. Bottlenecks can occur. In addition, in order to convert data received from each terminal or synchronization server in the gateway, a process of decrypting the encrypted data is required. If a security attack occurs during this process, sensitive personal data may be exposed to the outside world. The agent of the present invention has been developed in an embedded manner to compensate for these shortcomings, and is mounted in each user's mobile terminal, and extracts and converts data in the terminal, thereby alleviating security vulnerabilities and bottlenecks.

1 is a block diagram of a SyncML based data synchronization gateway system according to the present invention;
2 is a SyncML client and a Sync. Processing flow between protocol managers.
3 is a process flow diagram of a data synchronization gateway system in accordance with the present invention.
4 illustrates a mechanism of operation of a SyncML based data synchronization gateway in accordance with the present invention.
5 shows a graph of total synchronization time and time spent in a conversion gateway in accordance with the present invention.

The present invention enables synchronization between each other while using various data synchronization methods provided by a mobile terminal company by using SyncML data synchronization method, which is a standard synchronization method proposed by the Open Mobile Alliance (OMA).

1 illustrates a configuration of an embedded data synchronization agent device according to a preferred embodiment of the present invention.

The embedded data synchronization agent device has a data conversion method and is mounted in a mobile terminal. The embedded data synchronization agent device converts an ActiveSync type message into an OMA DS SyncML based message or converts an OMA DS SyncML based message into an ActiveSync type message. The embedded data synchronization agent device includes a protocol manager 100, a synchronization manager 102, a data store manager 104, and a data store 106.

The protocol manager 100 includes a communication module 108, a session module 110, and an authentication module 112.

The communication module 108 is responsible for exchanging synchronization messages between a data synchronization agent and a data synchronization server, not shown.

The session module 110 maintains a session with the server until the data synchronization is completely terminated, interprets the header portion of the synchronization message and verifies the suitability of the message. In this case, when the data synchronization starts, the mobile terminal and the data synchronization server exchange synchronization messages, and all packages exchanged between the mobile terminal and the data synchronization server for one time data synchronization are called sessions.

The authentication module 112 checks whether the synchronization request is from an authorized data synchronization server before performing data synchronization. The authentication module 112 takes the data synchronization server authentication information stored in the authentication table 134 of the datastore 106 and compares it with the authentication information transmitted by the data synchronization server at the time of synchronization. As the authentication method of the authentication module 112, the BASIC and MD5 hash algorithms used in the OMA DS may be adopted.

The synchronization manager 102 performs actual data synchronization, and includes a synchronization engine 114, a data extraction module 116, a synchronization type determiner 118, and a terminal information extractor 120.

The synchronization engine 114 interprets the synchronization message received from the data synchronization server, extracts the synchronization command and the synchronization data, and reflects the data to the datastore 106 through the datastore manager 104. The message structure interpreted by the synchronization engine 114 is shown in FIG.

The synchronization message is composed of a unique ID of the mobile terminal material, a synchronization command indicating an LUID, an ADD, a DELETE, a REPLACE, and actual synchronization data such as a contact and a schedule.

And when there is a mobile terminal side change or when sending a response message to the data synchronization server side synchronization request, the synchronization engine 114 generates a synchronization message. The synchronization message is currently widely used, and is generated in an XML format that is also used in OMA DS.

The data extraction module 116 uses a change log table for extracting changes. In the change log table, a status flag of each data, a change time, and the like are recorded. Based on the change log table, only data changed since the last synchronization is extracted and transmitted to the synchronization engine 114.

The synchronization type determination unit 118 uses an anchor table to determine whether to transmit the entire data (Slow Sync) or only the changed data (Fast Sync). The previous synchronization time is stored in the anchor table. If the anchor information of the data synchronization agent and the data synchronization server is different, the entire data is transmitted. If the data is identical, only the changed data is transmitted.

The terminal information extracting unit 120 extracts a terminal setting value for informing the data synchronization server of a synchronization type that can be accommodated by the mobile terminal, a memory capacity of the terminal, and the like. The terminal setting value is stored as an XML document.

The datastore adapter 104 includes a POOM (Pocket Outlook Object Model) manager 122 and a DB manager 124.

The POOM manager 122 extracts, stores and modifies data used in an application program. The POOM is a set of classes representing PIMS (Personal Information Management System) information of a Windows Mobile or Windows CE based terminal application. The POOM manager 122 extracts, stores, deletes, and modifies data using the POOM library in three steps.

1) Create an OutlookSession object to start a POOM session

2) Using the ItemID object to extract the LUID, which is the unique ID of the data used by the application

3-1) When adding data, call Add () method with data as parameter and return newly allocated LUID

3-2) Calling Remove () method with LUID as parameter when deleting data

3-3) Calling the Update () method with LUID and data as parameters when modifying data

The DB manager 124 extracts, stores, and modifies change logs, anchors, setting values, and authentication values. The DB manager 124 extracts a hash value stored in the change log by using a query statement by referring to the LUID of the data extracted by the POOM manager 122. The change log uses CEDB provided by Windows Mobile and has a LUID and a hash value paired with data used by an application. The CEDB is a database used in the Windows Mobile terminal. The DB manager 124 extracts, stores, deletes, and modifies a hash value using a CEDB query as follows.

1) Create a SqlCeConnection object to connect to the database

2) Execute the SELECT query statement using the ExecuteReader () method to select the same record as the LUID of the data extracted by the POOM manager 122.

3) Execute INSERT, DELETE, UPDATE query statement using ExecuteNonQuery () method

3 shows a detailed structural diagram of the data extraction module 116. The data extraction module 116 compares a pair of data received from the POOM manager 122 and the DB manager 124 and transfers the change state (synchronization command), LUID, and data to the synchronization engine 114. For example, if data ABC with LUID 3 is added in the application, the data extraction module 116 delivers the message < ADD, LUID # 3, ABC > to the synchronization engine. In addition, when the synchronization target data and the synchronization command is received from the data synchronization server, the synchronization command such as add (ADD) / delete (DELETE) / modify (REPLACE), LUID, and data is transmitted to the POOM manager 122. In addition, the hash value of the data is calculated and delivered to the DB manager 124 together with the LUID.

4 shows a flowchart of an embedded data synchronization agent in accordance with the present invention. The operation of the embedded data synchronization agent according to the present invention will be described with reference to FIG. 4.

The POOM manager 122 extracts the changed data from the application program and combines the data with the LUID, which is a unique ID of the data, and provides the data to the data extraction module 116. The DB manager 124 extracts the hash value stored in the change log by referring to the LUID of the data extracted by the POOM manager 122, and combines the LUID and the hash value to provide the data to the data extraction module 116.

The data extraction module 116 converts the data into a hash value for the LUID and the data transmitted by the POOM manager 122. Thereafter, the data extraction module 116 compares the LUID and the hash value with the LUID and the hash value from the DB manager 124. If the two values are different, the data extraction module 116 combines the synchronization command with the LUID and the hash value. ) The message generation module 136 combines the synchronization command, LUID, and hash value to generate a synchronization message and transmits the synchronization message to the data synchronization server.

When the synchronization message from the data synchronization server is received, the message analysis module 138 analyzes the synchronization message as a synchronization command, LUID, and data, and then provides the synchronization message to the data extraction module 116.

The data extraction module 116 converts the data analyzed from the synchronization message into a hash value and then provides the data to the DB manager 124. The DB manager 124 changes the hash value and the LIUD included in the synchronization message. Save to the log.

Thereafter, the data extraction module 116 provides the POOM manager 122 with the synchronization command, LUID, and data included in the synchronization message. The POOM manager 122 performs a synchronization operation such as storing / deleting / modifying data according to the synchronization command, LUID, and data.

100: protocol manager
102: synchronization manager
104: datastore manager
106: datastore

Claims (4)

In a system in which a mobile terminal and a data synchronization server are networked for data synchronization, the mobile terminal includes:
A protocol manager in charge of communicating with the data synchronization server;
A datastore providing a change log table, an anchor table, a terminal setting value and a data storage area of an application program;
A data store manager including a POOM manager for extracting, storing, and modifying data used by the application, and a DB manager for extracting, storing, and modifying the change log, anchor information, and terminal setting values;
Receives LUID and data from POOM Manager, converts data into hash value, compares LUID and hash value with LUID and hash value from DB manager, and if two hash values are different, synchronize command, LUID and hash value. Combining the data extraction module to combine the synchronization command, LUID and hash value in the data extraction module to generate a synchronization message to send to the protocol manager, or the synchronization message received from the protocol manager, the synchronization command, LUID and The synchronization engine analyzes the data and provides the data extraction module to the data extraction module and the anchor information of the data synchronization server and the anchor information of the mobile terminal to determine whether to transmit the entire data or only the changed data. And the data synchronization server in association with the DB manager. And a synchronization manager including a terminal information extraction unit for extracting terminal information values for transmission to the mobile terminal. The method of claim 1,
The data store further comprises an authentication table,
The DB manager extracts, stores and modifies the authentication value in the authentication table.
The protocol manager further comprises an authentication module for authenticating the data synchronization server in cooperation with the DB manager. In a method of synchronizing data between a mobile terminal and a data synchronization server in a networked system,
The mobile terminal,
Receives LUID and data for changed data by application program and converts data into hash value, compares hash value corresponding to the LUID from change log table, and if the two hash values are different, synchronize command and LUID and Transmitting a synchronization message comprising a hash value to the data synchronization server;
When a synchronization message is received from the data synchronization server, the synchronization command and LUID and data are analyzed from the synchronization message, the data is converted into a hash value, and the LUID and hash value are output to be reflected in the change log table.
Reflecting the synchronization command and LUID and data to the application program;
Comparing anchor information of the data synchronization server with anchor information of the mobile terminal to determine whether to transmit entire data or only changed data;
Data synchronization method of a mobile terminal, comprising a. The method of claim 3,
And performing the authentication on the data synchronization server.

Images