KR100379457B1 - Personal Information Management Method - Google Patents

Abstract

The present invention relates to a personal information management system, and more particularly, to a personal information management method for synchronizing personal data management program (PIMP) data existing in a computer with personal data stored in a mobile phone through a hash value.

To this end, the present invention provides a personal information management method for synchronizing personal data management program (PIMP) data of a computer and personal data stored in a mobile phone through a hash value in a personal information management system. When exchanging data of management program (PIMP) and data of mobile phone, it provides personal information management method to synchronize data between computer and mobile phone by comparing only necessary records.

Description

Personal Information Management Method

The present invention relates to a personal information management system, and more particularly, to a personal information management method for synchronizing personal data management program (PIMP) data existing in a computer with personal data stored in a mobile phone through a hash value.

In general, a personal information management system (PIMS) is a comprehensive system that efficiently manages various types of information generated in the social and personal lives of modern people.

This personal information management system (PIMS) uses a personal information management program (PIMP), which is a software area, to use mobile phone users' personal information such as phone book, address book, schedule management, consultation management, and memory management. Manage.

For personal information management, the mobile phone is connected to the computer with a serial cable.

After that, data synchronization between the computer and the mobile phone should be performed. Data synchronization, also called data exchange, is the process of copying or updating the contents of the database managed by the computer's personal information management program (PIMP) to the mobile phone, or newly created on the mobile phone. Alternatively, the updated data is reflected in a database managed by a personal information management program (PIMP) of a computer.

In particular, the Personal Information Management System (PIMS) manages all the user information required by the list in order to efficiently exchange data and data between mobile phones and computers. This list of information is called a record.

However, in the prior art, when the data of the personal information management program (PIMP) and the data of the mobile phone are exchanged or synchronized in the data by the personal information management system (PIMS), all records are compared even though only some records have been changed. In order for the computer to compare all records, the phone moves all records over a serial cable.

Subsequently, according to the comparison result, the newly created or updated data on the mobile phone is reflected in the database managed by the personal information management program (PIMP) of the computer and also managed by the personal information management program (PIMP) of the computer. You have copied or updated some of the contents of your phone.

As a result, when synchronizing the data of a personal information management program (PIMP) with the data of a mobile phone, since a whole record is the comparison object, a larger amount of data is transmitted and received between the computer and the mobile phone. Also reduces the transmission speed.

In addition, when a single mobile phone is manufactured, a data exchanger is created that checks whether data of the personal data management program (PIMP) or data stored in the mobile phone is changed by referring to the data structure of the mobile phone data. . This will make the exchange unusable for the upcoming phone models. This is because the fields are different from each other, i.e. if a field that does not exist in the personal information manager (PIMP) exists in the mobile phone or a field that does not exist in the mobile phone exists only in the personal information management program (PIMP), the data is not shared. It becomes impossible.

As a result, data exchangers are required in order to exchange data between personal information management programs (PIMP) and mobile phone data for data synchronization between the computer and mobile phone, depending on the upcoming mobile phone model.

An object of the present invention has been made in view of the above, personal information management system so that personal information management program (PIMP) data of a computer and personal data of a mobile phone are synchronized with each other through a hash value in a personal information management system. Provide management methods.

It is still another object of the present invention to provide a personal information management method for synchronizing data between a computer and a mobile phone by using only the necessary records when exchanging data of a personal information management program (PIMP) and data of a mobile phone.

A characteristic of the personal information management method according to the present invention for achieving the above object is the step of constructing each hash table from each data present in the computer and the mobile phone, and each of the configured hash table stored in the previous data exchange Generating a new update hash table in comparison with the hash table, and selectively updating a specific user information list among respective data existing in the computer and the mobile phone by analyzing the generated update hash table.

Preferably, the step of configuring each hash table of the computer and the mobile phone, assigning a record identifier by sequentially increasing the count value for each user information list, and hashing the user information content corresponding to each record identifier by a predetermined byte A hash table of the mobile phone is configured by expressing the value, and record identifiers are provided for each list to user information expressed as a hash value of a predetermined byte with reference to the count value provided from the mobile phone, thereby configuring a hash table of the computer.

The generating of the update hash table may include assigning a new record identifier for each updated user information list according to whether the computer data or the mobile phone data is changed, and specifying the content of user information corresponding to each of the given record identifiers. The update hash table is generated by expressing a hash value of a byte and expressing a change of the computer data or the mobile phone data by a flag of a predetermined bit.

In addition, the updating of the specific user information list may include analyzing a flag indicating a change in the computer data or the mobile phone data by a predetermined bit in the generated update hash table, and selecting a specific user among respective data existing in the computer and the mobile phone. Optionally add, change and delete information lists.

A characteristic of the personal information management system according to the present invention for achieving the above object is that a personal information management program (PIMP) of the computer and a hash table of data present in the mobile phone in order to synchronize the data with the mobile phone to the computer. A data exchange that finds a list of information of the user that needs to be updated compared to the hash table stored in the previous data exchange, and sets a data structure for the mobile phone data and record identifier for each user data list to communicate with the data exchange to the mobile phone. It is configured to include a phone manager that provides the required count value.

1 is a view showing a hash table structure for a personal information management method according to the present invention.

Figure 2 is a block diagram showing a portion of a computer and a mobile phone for explaining the personal information management method according to the present invention.

3 is a flowchart illustrating a data synchronization procedure for managing personal information according to the present invention.

4 is a view for explaining a hash table update procedure for managing personal information according to the present invention.

* Description of the symbols for the main parts of the drawings *

100: computer 110: data exchange

120: personal information management program 130: PIMP database

200: cell phone 210: phone manager

Hereinafter, a preferred embodiment of a personal information management method according to the present invention will be described with reference to the accompanying drawings.

In the present invention, once the mobile phone and the computer are connected by a serial cable in hardware, the data of the personal information management program (PIMP) or the data of the mobile phone are transmitted / received in the form of a hash table through the serial cable. A detailed description of the procedure for transmitting and receiving data between a computer and a mobile phone using a cable is not mentioned, and since the operation of the personal information management program is not directly related to the present invention, the detailed description thereof is not mentioned.)

1 is a view showing a hash table structure for a personal information management method according to the present invention, Figure 2 is a block diagram showing a part of the configuration of a computer and a mobile phone for explaining the personal information management method according to the present invention.

In order to clarify the description of the present invention, FIG. 2 will be described first.

Referring to FIG. 2, in exchanging data of a personal information management program (PIMP) with data of a mobile phone, an update is required by checking whether data of the personal information management program (PIMP) or data stored in the mobile phone 200 is changed. A data exchange 110 for finding data is provided in the computer 100, and the mobile phone 200 is provided with a phone manager 210 for communicating with the data exchange 110 of the computer 100. In particular, these data exchange 110 and the phone manager 210 is in the form of a module (module).

The data exchange 110 configures the data created by the personal information management program (PIMP) 120 into a hash table, and receives the data stored in the mobile phone 200 in the form of a hash table. The structure of these hash tables is shown in FIG. 1A.

Thereafter, the data exchange 110 compares the hash table of the type shown in FIG. 1A stored in the previous data exchange with the hash table configured above and the hash table received from the mobile phone 200. At this time, the data exchange 110 checks whether the data of the two hash tables has changed with respect to the data of the previous hash table.

If it is determined that the data of the two hash tables has been changed with respect to the data of the previous hash table, then the data exchanger 110 transfers the data stored in the personal information management program (PIMP) database 130 of the computer 100. By modifying the data of the hash table to create a new hash table of the type shown in Figure 1b, or instructs the phone manager 210 of the mobile phone 200 to modify the data.

The phone manager 210 receives a data modification command from the data exchange 110 to modify mobile phone data stored in the phone manager 210.

In addition, the mobile phone 200 has information on the data structure of the data stored therein in order to exchange data of the personal information management program (PIMP) and data of the mobile phone.

Here, the data structure for facilitating the management of personal information of the present invention is a record, which is a list of information for each individual, and each field constitutes a field for more detailed items. For example, in the case of managing an address book as shown in Table 1 stored in the mobile phone 200, all data for each individual is one record, and names, phone numbers, addresses, and other memos, which are detailed items of each address book, are fields. . The mobile phone 200 stores the information on the records and fields in this way.

Each field → number name address Phone number … → record →→ One Hong Gil Dong Seoul City 548-9696 2 Chulsoo Kim Daejeon 456-4566 3 Younghee Kim Busan 585-8854

Each record is assigned a unique record identifier for each record, which is set by a record counter. This record counter exists in the mobile phone 200, and sets a record identifier by incrementing the count value each time a new record is generated, and the initial value of the record counter is "1".

Data stored in a personal information management program (PIMP) database 130 of the computer 100 is also divided into records and fields, and a record identifier is also assigned to each record. However, since there is no record counter in the computer 100, a record identifier is assigned to each record by referring to the record count value read from the mobile phone 200 at the time of data exchange.

Based on the data structure described above, the hash table generated in the data exchange 110 and the mobile phone 200 is illustrated in FIG. 1A, and the hash table newly generated based on the hash table shown in FIG. 1A is illustrated in FIG. 1B. Shown in

In the present invention, data exchange between the computer 100 and the mobile phone 200 is made through a hash value. Exactly, data exchange takes place in the form of a hash table shown in FIG. 1A.

A hash table is a collection of buckets containing one or more records, where a bucket is a collection of data belonging to the same class when sorting multiple data according to specific criteria.

By default, the hash table contains a unique record identifier for each record, and the record contents classified by each record identifier. Here, the contents of each record are hash values represented by several bytes (for example, 4 bytes) through a hash function.

Even if different records have the same record value, they have the same hash value. On the other hand, different records have different hash values.

In addition, the hash table of FIG. 1B newly generated based on the hash table shown in FIG. 1A further includes a 6-bit flag. Three of these 6-bit flags represent changes in personal data management program (PIMP) data, and the remaining three bits represent changes in data stored in the phone. The hash table update procedure including the 6-bit flag will be described in more detail with reference to FIG. 4 below.

The following describes the data synchronization, or data exchange, procedure between computer and mobile phone for personal information management, before explaining the hash table update procedure.

3 is a flowchart illustrating a data synchronization procedure for personal information management according to the present invention.

Once data is synchronized between a computer and a cell phone, data exchange can begin on either the computer or the cell phone.

As the data exchange between the computer and the mobile phone can be started from either the computer or the mobile phone, the mobile phone continuously monitors the start signal of the computer for exchanging data while the power is on, and the computer has a serial cable when the data exchange is started. Continuously monitoring the data exchange start signal of the mobile phone input through (S10).

Thereafter, when either of the computer and the mobile phone detects a data exchange start signal, data exchange starts (S20).

Once data exchange between the computer and the mobile phone is started, the data exchanger requests a record count value and data structure of the mobile phone to the phone manager of the mobile phone (S30). However, this is when the computer detects the data exchange start signal of the mobile phone. In contrast, when the mobile phone detects the data exchange start signal of the computer, the start signal becomes a request signal. Pass the structure and count values of the record counter to the transfer data exchange.

The data exchanger receives the data structure of the data stored in the current mobile phone and the count value of the record counter from the phone manager, and stores the record count value and analyzes the received data structure (S40).

The phone manager delivers the data exchange in a distinguishable form, an example of which is shown below.

"104, {NAME, PHONENUMBER, ADDRESS, MEMO}"

Here, '104' indicates that the record identifier of the address book to be created next is '104' as the record count value. The data exchange stores this record count and assigns it as the identifier of the record corresponding to the address book when updating a new hash table. In addition, '{NAME, PHONENUMBER, ADDRESS, MEMO}' represents each field of the record, and each of these fields is called a field token. Each of these field tokens is used not only in the data structure of the data stored in the mobile phone, but also in the data structure of the personal information management program (PIMP) database of the computer. The data exchanger analyzes each field token received from the phone manager.

Thereafter, the data exchange selects the same fields as the data structure received from the personal information management program (PIMP) database to construct a hash table, and simultaneously requests the phone manager to transmit the hash table (S50).

The phone manager requesting the hash table transfer calculates a hash value corresponding to the record contents of each record, and transfers the hash table generated after assigning each record identifier to the data exchanger (S60).

The data exchange then reads the hash table stored in the previous data exchange from a file (S70).

Accordingly, the data exchanger compares the hash table selected from the personal information management program (PIMP) database and the hash table received from the phone manager with the hash table at the time of exchanging data read from the file (S80).

At this time, the data exchanger checks whether the data of the hash tables has been modified with respect to the data of the previous hash table (S90), and if it is determined that the data of the hash table has been changed with respect to the data of the previous hash table, it is shown in FIG. 1B. Compose a new hash table as shown (S100). A more detailed procedure of updating a new hash table is described with reference to FIG. 4 below.

The data exchange then checks the flag of the newly updated hash table (S110), depending on which of the computer or mobile phone has detected the data exchange start signal, to the previous data or mobile phone of the personal data management program (PIMP) database. Only the corresponding record added, changed or deleted from the stored data is modified (S120).

Thereafter, the data exchanger transmits a data exchange termination signal to the mobile phone (S130), and stores the newly updated hash table in a file (S140).

The following is a comparison between the hash table configured by the data exchanger selected from the personal information management program (PIMP) database and the hash table received from the phone manager with the hash table of the previous data exchange read from the file. This section describes the procedure for updating the hash table.

4 is a diagram illustrating a hash table update procedure for managing personal information according to the present invention.

Once the data exchange selects the appropriate fields from the Personal Information Management Program (PIMP) database, it constructs a hash table and receives the hash table from the phone manager. It also reads from the file the hash table of the previous data exchange.

The hash tables are then compared. Next, the hash table update according to the comparison result will be described.

First, if the record identifier is '0' in a hash table constructed from a personal information management program (PIMP) database, this indicates that data not present in the mobile phone is newly added to the computer. Therefore, the first flag bit of the update hash table is set to 1 (CASE1 in Table 2).

If the hash value of a particular record identifier in a hash table constructed from the next Personal Information Manager (PIMP) database is different from the hash value of the same record identifier in the hash table at the time of the previous data exchange, this is a Personal Information Manager (PIMP) data. Indicates that the record corresponding to the specific record identifier has been changed. Therefore, the second flag bit of the update hash table is set to 1 (CASE2 in Table 2).

If a record identifier that exists in the hash table at the next data exchange does not exist in the hash table configured from the Personal Information Manager (PIMP) database, it is not present in the hash table constructed from the Personal Information Manager (PIMP) data. Indicates that the record of identifier has been deleted from the hash table at the previous data exchange. Therefore, the third flag bit of the update hash table is set to 1 (CASE3 in Table 2).

If a particular record identifier in the hash table received from the next phone manager does not exist in the hash table at the previous data exchange, this indicates that data not present in the mobile phone is newly added to the mobile phone. Therefore, the fourth flag bit of the update hash table is set to 1 (CASE4 in Table 2).

If the hash value of a specific record identifier in the hash table received from the next phone manager is different from the hash value of the same record identifier in the hash table at the previous data exchange, this indicates that the record corresponding to the specific record identifier in the mobile phone data has changed. Indicates. Therefore, the fifth flag bit of the update hash table is set to 1 (CASE5 of Table 2).

If the record identifier in the hash table at the next previous data exchange does not exist in the hash table passed from the phone manager, this means that the corresponding record of the record identifier that does not exist in the hash table received from the phone manager is hashed at the previous data exchange. Indicates that it was deleted from the table. Therefore, the sixth flag bit of the update hash table is set to 1 (CASE6 in Table 2).

We have already mentioned that the updated hash table contains a flag of three bits on the front side indicating changes in personal information management program (PIMP) data and a flag of three bits on the back indicating changes in data stored on the mobile phone. By applying different flag bit values differently for each addition, change, and deletion, the data exchange then checks the 6-bit flag of the update hash table, and the personal information management program (PIMP) as shown in Table 2 below. Independently decide whether to modify previous data in the database or data stored in the mobile phone.

CASE flag Material revision One 100000 Since the record was added from PIMP data, add that record to your phone data. 2 010000 Since the record was changed in PIMP data, the record is changed in the mobile phone data. 3 001000 Since the record was deleted from the PIMP data, delete the record from the mobile phone data. 4 000100 Since the record was added from the phone data, add it to the PIMP data 5 000010 Since the record has changed in the phone data, change the record in the PIMP data 6 000001 Since the record was deleted from the phone data, delete the record from the PIMP data. 7 010010 Since the record has changed in both PIMP data and mobile phone data, contact the mobile phone user. 8 001010 Since the record was deleted in both PIMP data and mobile phone data, contact the mobile phone user. 9 010001 Contact the mobile phone user because the record has changed in PIMP data and the record has been deleted from mobile phone data at the same time. 10 001010 Since the record was deleted from the PIMP data and the record was changed from the mobile phone data at the same time, contact the mobile phone user.

However, if the data exchange finds a record whose record identifier is '0' in a hash table constructed from a personal information management program (PIMP) database as shown in CASE1 of Table 2 above, the data exchange reads from the mobile phone at the time of data exchange. Refer to the record count value and assign a new record identifier to the record, and then modify the corresponding data in the database so that this new record identifier is reflected in the database managed by the personal information management program (PIMP) of the computer. .

As described above, the personal information management method according to the present invention has the following effects.

In synchronizing the data of the personal information management program (PIMP) with the data of the mobile phone, only the records needed through the hash value are compared. In the present invention, the data exchange calculates the hash value of the record from the data of the mobile phone and personal information management program (PIMP), and uses the update hash table generated by the hash value calculation to find the record change.

Therefore, in synchronizing the data of the personal information management program (PIMP) with the data of the mobile phone, only the necessary record fields are exchanged, thereby reducing the amount of data transmitted and received between the computer and the mobile phone, and eventually reducing the data transmission speed between the computer and the mobile phone. none.

Information about the data structure of the mobile phone data is pre-stored in the mobile phone, and the data exchange refers to this to synchronize only the necessary fields from the data of the personal information management program (PIMP). There is no need to create a new data exchanger.

Claims (8)

Constructing a hash table from each data present in the computer and the mobile phone, Generating a new update hash table by comparing each of the configured hash tables with the hash tables stored at the time of exchanging data; And analyzing the generated update hash table to selectively update a specific user information list among respective data existing in the computer and the mobile phone. The method of claim 1, wherein configuring each hash table of the computer and the mobile phone comprises: The hash table of the mobile phone is configured by assigning a record identifier while sequentially increasing a count value for each user information list and expressing user information corresponding to each record identifier as a hash value of a predetermined byte. And a record identifier is provided for each list to the user information expressed as a hash value of a predetermined byte with reference to the count value provided from the mobile phone, thereby configuring a hash table of the computer. The method of claim 1, wherein generating the update hash table comprises: A new record identifier is given for each updated user information list according to whether the computer data or the mobile phone data is changed. Expressing user information content corresponding to each of the given record identifiers as a hash value of a predetermined byte, And the update hash table is generated by indicating a change of the computer data or the mobile phone data with a flag of a predetermined bit. The method of claim 1, wherein updating the specific user information list comprises: Selectively adding, changing, and deleting a specific user information list among data existing in the computer and the mobile phone by analyzing a flag indicating a change in the computer data or the mobile phone data in a predetermined bit in the generated update hash table. Personal information management method. In order to synchronize the data with the mobile phone to the computer, the computer's personal information management program (PIMP) and the hash table of the data existing in the mobile phone are compared with the hash table stored at the time of exchanging the data, and the user's information list which needs updating is obtained. With data exchanger to find; And a phone manager for providing the cell phone with a count value for setting a data structure for cell phone data and a record identifier for each user data list to communicate with the data exchange. delete delete delete