JP4128946B2 - Data synchronization method for mobile phone having UIM and mobile phone using this synchronization method - Google Patents

Description

  The present invention relates to a mobile phone that can be used by inserting a UIM (User Identity Module), a method for performing data synchronization with a plurality of mobile phones not equipped with UIM, and a mobile phone using this synchronization method. .

In the present invention, a user who owns a plurality of mobile phone units and inserts a UIM only into a phone that is actually used transfers data to use the data of the phone in use on another phone that is not in use. This copying is called data synchronization.
In recent years, mobile phone companies have been using mobile phones with removable IC cards that store contractor information, so-called UIMs (User Identity Modules), in order to facilitate device settings / changes when replacing mobile phones. Yes. The UIM stores contractor information (for example, a local telephone number). By inserting this UIM into a newly purchased telephone, the new telephone can be used as its own telephone without any setting operation.
That is, when a user replaces a new phone with a new one, the user can immediately use the UIM as a phone having his / her own phone number simply by taking out the UIM from the old phone and inserting it into the new phone. As a result, some users have different types of telephones in the kitchen, select one telephone suitable for the mood and work of the day, and insert the UIM taken out from the telephone used so far. The usage form of starting use has come to be assumed.

By the way, every day, in a mobile phone, communication records with a communication partner, mail contents, and the like are accumulated as data each time a call is repeated. Since this kind of data is not stored in the above-mentioned UIM but is stored in a memory (for example, flash memory) inside the telephone, even if the UIM is replaced, these data do not move. This makes it impossible to refer to the communication records so far, which is very inconvenient for the subsequent communication, and causes practical problems. Therefore, this type of data (hereinafter referred to as a telephone book) is called a data synchronization operation. To move to a new phone.
Conventionally, data synchronization between telephones is performed between parent and child telephones. For example, there is an example in which a phone book held by the parent device is shared with the child device. Data synchronization in such a case is such that data held by each other can be exchanged or referred to between a master device that is a master and a slave device that is determined in advance. (For example, see Patent Document 1)
In this case, a main parent phone determined from the manufacturing stage and a device having a fixed parent-child relationship such as a slave child phone are established. By the way, in the case of owning a plurality of mobile phones, a parent-child relationship is not established between each other's phones, and if the other person's UIM is plugged in, it can become another person's phone, so that relationship becomes unspecified, The technique described in Patent Document 1 cannot be used.
JP 2002-101184 A

  As described above, there is no fixed or clear master-slave / parent-child relationship between a mobile phone in use and an unused mobile phone, like a master phone that is a master and a slave phone that is a slave. There has been a problem that conventional data synchronization technology cannot be applied.

  An object of the present invention is to solve the above-described problems, provide a method for enabling data synchronization between a plurality of unspecified mobile phones, and provide a mobile phone using this method.

The data synchronization method for a mobile phone having a UIM according to the present invention includes a first mobile phone unit that can be used as a mobile phone with a UIM (User Identity Module) storing at least the phone number data of the own device, and a UIM A method of data synchronization with a second mobile phone unit that has not been performed,
A telephone number registration procedure for storing the telephone number data stored in the UIM in a table database provided in advance in each of the first mobile phone unit and the second mobile phone unit;
Using the data communication means provided in each of the first mobile phone unit and the second form phone unit, the second mobile phone using the telephone number data as a key from the first mobile phone unit A search procedure to search for the presence of a unit,
A data synchronization procedure in which the first mobile phone unit becomes a main for data synchronization communication, and data synchronization is performed by using the second mobile phone unit detected by the search procedure as a slave for data synchronization. Is included.

  Since the data synchronization method of the present invention and the mobile phone using the data synchronization operation can omit complicated settings, the convenience of the user is increased, and privacy information such as a telephone directory is leaked due to a user operation error. It has the advantage that it can be prevented.

Embodiment 1 FIG.
An outline of data synchronization using the cellular phone of the present invention is shown in FIG. For convenience of explanation, a phone that can be used as a telephone with a UIM attached is called a telephone, and a telephone that is not attached and cannot be used as a telephone is called a telephone unit to be distinguished.
In FIG. 1, a mobile phone unit 101 that does not have a UIM (User Identity Module, also referred to as a contractor information storage device) 104 becomes a mobile phone 105 having a UIM 104 when the UIM 104 is attached. The mobile phone unit 102 and the mobile phone unit 103 are mobile phone units to which a UIM can be attached, but the UIM is not attached. Any mobile phone unit can be used by attaching the UIM 104.
In order to facilitate understanding of the description, the description will be made in the same master / slave relationship as before. The mobile phone 105 is the main mobile phone in performing data synchronization, and the mobile phone unit 102 or the mobile phone unit 103 without the UIM is used. Becomes a subordinate mobile phone unit.

A hardware configuration of the mobile phone 105 of the present invention is shown in FIG. The mobile phone 105 is capable of data synchronization operation and is equipped with a UIM 104. A wireless communication unit (hereinafter referred to as RF) 106, a slot 111 for inserting the UIM 104, determination of the insertion state of the UIM 104, and a telephone to be described later Necessary for arithmetic processing, a CPU 107 that performs processing such as registration of numbers, a ROM (flash ROM or the like) 108 that stores predetermined programs, daily communication records (including mail data), a database 200 described later, and the like A random access memory (RAM) 109 and communication means 110 for data synchronization are provided.
A radio communication unit (RF) 106 is a radio wave transmission / reception functional part for telephone communication of a cellular phone with a base station (not shown) via a radio communication route 12, and a communication means 110 transmits data via a data transmission route 11. Data transmission (communication) means for synchronization can be provided. The transmission route 11 may be wireless or wired, and representative examples of communication means include wired USB (Universal Serial Bus) and wireless Bluetooth. Of course, there are a power supply device, a display device, a voice input / output device, a keyboard, etc., which are not shown in the figure.

  FIG. 3 shows a table database 200 for registering telephone numbers read from the UIM 104 that is installed. The table database 200 is stored in the ROM 108 of FIG. The left side of the table database 200 is a telephone number registration unit having one telephone number, and the right side is a password registration unit having one password. However, registration of the password is arbitrary, and when the password is registered, data concealment by encryption or the like can be performed in data synchronization. FIG. 4 shows an example of the table database 200 when there is no password.

First, as a pre-process, a telephone number registration procedure is performed according to the flow of FIG. 5 for all mobile phone units that the user plans to use as his / her telephone.
FIG. 5 is a flowchart illustrating a procedure for pre-processing for registering information recorded in the UIM 104 in the table database 200, that is, a telephone number registration procedure. Although not described in the following description, it is assumed that the power of the related mobile phone unit is turned on.
Registration of UIM information in the table database 200 is started by first pressing a function key (not shown) and pressing a telephone number registration button. First, in S102, it is determined whether or not the UIM is inserted into the mobile phone 105. If the UIM 104 is inserted in the mobile phone 105 (yes in the figure), the telephone number is extracted from the UIM 104 in S103, and this telephone number is registered in the table database 200 in S104.
Next, a password is set after S105. If it is necessary to set a password in S105 (yes), the user is requested to input a password through the password input screen in S106, and the password input in S107 is registered in the password registration unit of the table database 200. If password setting is unnecessary (No in S105), no password is registered in the password registration unit of the table database 201 in S108. Through the above processing, registration in the table database 200 is completed in S109. Such processing is executed as a block by telephone number registration means (not shown).
The above processing is performed for each mobile phone unit 101, 102, 103.

Next, the data synchronization procedure will be described with reference to FIGS.
The data synchronization operation is performed in a state where common communication means can be used in both the mobile phone with the UIM attached and the mobile phone unit with no UIM attached. After pressing a function key of a keyboard (not shown) in a mobile phone equipped with a UIM, by selecting data synchronization and pressing a start button, this mobile phone starts as a main mobile phone and becomes a main mobile communication device. The process described in FIG. 6 is executed.
In addition, the mobile phone unit not equipped with the UIM becomes a slave in the communication means, and executes a process described later in FIG.

  First, a case of becoming a main mobile phone will be described with reference to FIG. In S112, the telephone number stored in the UIM 104 is compared with the telephone number registered in the table database 200 already described with reference to FIGS. This is to determine whether the UIM 104 being inserted is a UIM 104 that is always used, a temporary UIM, or a third-party UIM, and data synchronization occurs due to an unexpected erroneous operation. This is to prevent this and data leakage to a malicious third party. Therefore, the telephone number stored in the UIM 104 is compared with the telephone number registered in the table database 200, and if it matches, the process proceeds to S113 to continue the process, and this does not match. In this case, the process proceeds to S160 to end the process.

  In S113, it is confirmed whether or not a password is set. The password here refers to the password registered in the table database already described with reference to FIG. 3 or FIG. 4. If the password is set, the data confidentiality by encryption or the like is enabled in S114. To do. This completes the initial process in data synchronization.

In S115, a subordinate mobile phone unit is searched. The communication means 110 used for the search here is, as already described, USB or Bluetooth (technology for performing communication between indoor devices using Bluetooth, radio waves of 2.45 GHz band). In S116, the secondary mobile phone unit that has not been set for data synchronization is searched, but the search is performed using the telephone number and password registered in the table database 200 of the main mobile phone 105 as keywords. . Processing including this search is called a search procedure.
Therefore, when a subordinate mobile phone unit (for example, the mobile phone unit 102) is found, the subordinate mobile phone unit is requested in S117 for a telephone number and a password, and in S118, the subordinate mobile phone unit is obtained. The mobile phone number and password notified from the mobile phone number and the mobile phone number and password registered in the table database are compared. If they match, the subordinate mobile phone unit is set as the data synchronization target mobile phone unit in S119. If it does not match at S118, the mobile phone unit 102 is registered as a mobile phone unit that is not subject to data synchronization at S120. This processing procedure is called a non-target unit storage procedure. The reason why such registration is performed in S120 is to prevent the subordinate mobile phone unit search from entering an infinite loop.

If there is no data synchronization target / non-target in the secondary mobile phone unit that is the target of data synchronization in S116, it is assumed that the search for the secondary mobile phone unit has ended, and the process proceeds to S121 for actual data synchronization processing. In S121, it is confirmed whether or not the data synchronization target set in S119 exists. If there is a data synchronization target, it is checked in step S121A whether the target telephone has completed preparations for data synchronization. If OK, data synchronization processing is started in S122. However, even if it is attempted to start data synchronization in S122, if the data synchronization operation of the subordinate mobile phone unit is incomplete, S122 is not started and a predetermined time is set in a standby state (S121B). It will be in a standby state (for example, 5 minutes).
If it does not exist in S121, it is not necessary to perform data synchronization, and the process ends in S123.
The above processing procedure is called a data synchronization procedure.

Next, the subordinate mobile phone unit will be described with reference to FIG. The mobile phone unit not equipped with the UIM starts the processing of FIG. 7 in response to the secondary mobile phone unit search from the main mobile phone shown in S115 of FIG. 6, and the telephone number from the main mobile phone in S124 Wait for password notification request.
The notification request here is a request from S117 in the main mobile phone processing. In S124, a notification request is waited using a branch, but other means may be used as long as the notification request can be waited without using a branch. Further, the telephone number and password mentioned here indicate the telephone number and password registered in the table database of the subordinate mobile phone unit. When there is a request for notification of the telephone number and password from the main mobile phone, the telephone number and password registered in the table database are notified to the main mobile phone in S125.

  After notifying the telephone number and password in S125, the main mobile phone notifies the user whether or not the data synchronization target has been set. This corresponds to S118, S119, and S120 in the main mobile phone process. When the process of S119 is performed on the main mobile phone, the processes of S126 to S127 are performed, and the data is also set as the data synchronization target on the subordinate mobile phone. When the process of S120 is performed on the main mobile phone, the process proceeds from S126 to S130, and the process ends.

  After setting the data synchronization target in S127, the process waits for execution of data synchronization processing in S128. This corresponds to S121 and S122 in the main mobile phone processing. When the data synchronization process is performed in S122, the slave mobile phone performs the data synchronization process in S129. If the data synchronization process is not performed in S128, the process proceeds to S130, and the process ends.

  As described above, in the mobile phone according to the present embodiment, the main mobile phone for performing control in data synchronization according to the insertion state of UIM 104, and the subordinate mobile phone for performing data synchronization in accordance therewith Can be set automatically, and the phone number in the UIM 104 and the password entered by the user are saved in the mobile phone in advance, so that complicated settings such as setting of the target mobile phone in data parallel can be omitted. Since it has the feature of being possible, it has the advantage that the convenience of the user is increased and the leakage of privacy information such as a telephone directory in the case of a user operation mistake can be prevented.

Embodiment 2. FIG.
The description of S114 in FIG. 6 only describes that confidentiality is enabled, but this is different from, for example, a password that has been input and stored before that in the telephone number registration procedure. At this time, the input of new telephone number data is rejected. As a result, for example, an attempt is made to copy a communication record stored in the mobile phone unit 101 obtained by a malicious third party by unauthorized means to the mobile phone unit owned by the user by a data synchronization operation. Data synchronization operation cannot be executed even if the password is known. In addition, when rewriting the stored password with a new password, it is necessary to input the old password. In addition, when the stored password is forcibly deleted, the communication record and the telephone directory are also deleted.

  The mobile phone synchronization method of the present invention can be used not only for mobile phones but also for fixed phones and personal computers.

It is a schematic diagram for demonstrating the data synchronization between the mobile telephones of this invention. It is a block diagram of a mobile phone unit. It is a figure of a table database. It is a figure of a table database. It is a flowchart explaining a telephone number registration procedure. It is a figure which shows the flow of synchronization implementation by the side of a main telephone. It is a figure which shows the flow of synchronous implementation by the subordinate telephone side.

Explanation of symbols

11 data transmission route, 12 wireless communication route,
101, 102, 103 mobile phone units,
104 UIM, 105 Mobile phone with UIM,
108 ROM, 110 communication means, 200 table database,
S101-S109 telephone number registration procedure,
S112 to S115 search procedure,
S116, S121 to S123 Data synchronization procedure.

Claims (5)

Data between a first mobile phone unit that is equipped with at least a UIM (User Identity Module) that stores phone number data of the own device and that can be used as a mobile phone, and a second mobile phone unit that is not equipped with a UIM A synchronization method,
A telephone number registration procedure for storing the telephone number data stored in the UIM in a table database provided in advance in each of the first mobile phone unit and the second mobile phone unit;
Using the data communication means provided in each of the first mobile phone unit and the second form phone unit, the second mobile phone using the telephone number data as a key from the first mobile phone unit A search procedure to search for the presence of a unit,
A data synchronization procedure in which the first mobile phone unit becomes a main for data synchronization communication, and data synchronization is performed by using the second mobile phone unit detected by the search procedure as a slave for data synchronization. A data synchronization method for a mobile phone having a UIM, comprising:   2. The telephone number registration procedure includes a procedure of inputting a password, and a procedure of rejecting input of the telephone number data when the input password is different from a stored password. Data synchronization method.   In the search procedure, when the telephone number data of the second mobile phone unit that has been detected and detected does not match the stored phone number data, the detected second mobile phone unit is not subject to data synchronization. The data synchronization method according to claim 1, further comprising a non-target unit storing procedure for storing.   A mobile phone configured to execute the data synchronization method according to claim 1. Phone number registration means for storing the phone number data of the own device stored in the installed UIM in a built-in table database;
Search means for searching for presence / absence of a mobile phone unit to be subjected to data synchronization using the telephone number data of the own device as a key,
A mobile phone having a UIM, comprising data synchronization means for performing data synchronization using the mobile phone unit as a slave for data synchronization when the target mobile phone unit is detected.

Images