JP2009239704A - Data management system and server apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To protect the internal data of a mobile telephone effectively so that it cannot be utilized by a third party. <P>SOLUTION: A data management system 1 for mobile telephone includes a mobile telephone 10 and a slave unit 20 which can only perform short-range radio communications with the mobile telephone 10. The mobile telephone 10 includes first short-range radio communication sections 14 and 16 for short-range radio communication with the slave unit 20, a storing section 13 for storing data, a first determination section 15 for determining whether the distance to the slave unit 20 is larger than a predetermined value, and a first control section 15 for erasing the data of the storing section 13 when it is determined that the distance to the slave unit 20 is larger than the predetermined value. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a data management system for managing data recorded in a mobile phone and a server device applied to the data management system.

  Conventionally, a technique for automatically erasing data recorded in a mobile phone when the mobile phone is lost has been proposed. For example, in Patent Document 1, the owner of a stolen mobile terminal device makes a theft notification from another mobile terminal device to an information center that manages the mobile terminal device. A technique for issuing a system lock request to a target portable terminal device from an information center is disclosed. According to this technique, all the internal data of the stolen portable terminal device is deleted.

Patent Document 2 discloses a technology in which various erasure conditions are set in advance in a mobile terminal device, and the mobile terminal device erases data by its own control when any of the conditions is satisfied. . In this technology, data erasure control is performed not by external control such as a network but by the mobile terminal device itself. Thereby, it is said that the risk of information leaking to a third party can be further reduced when control from the network is impossible and until the loss is noticed. In addition, the data to be erased can be restored to another computer device by uploading it to a server on the network, for example, thereby preventing information leakage from the mobile terminal device without sacrificing user convenience. It is supposed to be possible.
JP-A-8-251660 JP 2007-097023 A

  However, with the conventional technology, since the owner of the mobile phone notices the loss and the internal data of the mobile phone may be abused before making a request to the maintenance service center, it is sufficient as a countermeasure against leakage of important data. It was not a thing. In addition, when a person who tries to find the data inside the lost mobile phone with malicious intent is taken off with the mobile phone turned off, the data is read in an out-of-service area where radio waves do not reach There is also a problem that the internal data cannot be erased because the data erase command from the center side to the mobile phone does not arrive.

  In addition, data is erased when the set time is exceeded in a mechanism that controls data erasure on the mobile phone itself, rather than from the outside such as a network, so data is erased even in daily usage situations. There will be more cases. Also, when data is erased, it is backed up to the center side, but if the internal data of the mobile phone is frequently erased, when the user wants to use it, the download from the center is not completed immediately and the user wants to use it Sometimes inconvenience that it cannot be used. In addition, there is a problem that it is impossible to refer to data outside the service area.

  The present invention has been made in view of such circumstances, and provides a data management system and a server device that can effectively prevent internal data of a mobile phone from being used by a third party. With the goal.

  (1) In order to achieve the above object, the present invention takes the following measures. That is, the data management system of the present invention is a data management system for a mobile phone comprising a mobile phone and a handset capable of short-range wireless communication only between the mobile phone and the mobile phone. Determines whether the distance between the first short-range wireless communication unit that performs short-range wireless communication with the slave unit, a storage unit that stores data, and the slave unit is greater than a predetermined value. A first determination unit; and a first control unit that erases data in the storage unit when the distance from the slave unit is larger than a predetermined value as a result of the determination. It is a feature.

  As described above, when the distance between the mobile phone and the handset becomes larger than a predetermined value, the data in the storage unit is deleted, so that it takes time until the deletion is executed as in the prior art. It is possible to effectively prevent information leakage. Further, since no instruction from the center is required, information leakage can be prevented even when the mobile phone is out of the communication range.

  (2) In the data management system of the present invention, the mobile phone further includes a timer that counts the passage of time, and a first warning sound generation unit that generates a warning sound. As a result of the determination, the counting is started when the distance to the slave unit becomes larger than a predetermined value, and the first warning sound generating unit determines that the distance to the slave unit is previously determined as a result of the determination. A warning sound is generated when the value exceeds a predetermined value, and the first control unit determines whether the count value of the timer has reached a predetermined value, and as a result of the determination, When the count value of the timer reaches a predetermined value, the data in the storage unit is erased.

  In this way, since the warning sound is generated when the distance to the slave unit becomes larger than a predetermined value, it is possible to notify the user that there is no mobile phone nearby. In addition, when the count value of the timer reaches a predetermined value, the data in the storage unit is erased. Therefore, when a certain time elapses after the distance from the slave unit becomes larger than the predetermined value, the data Is erased, information leakage can be prevented. On the other hand, when the distance from the slave unit becomes smaller than a predetermined value, the data erasing operation can be temporarily stopped. As a result, it is possible to avoid the risk of information leakage and to avoid frequent deletion of data in daily usage situations.

  (3) In the data management system of the present invention, the mobile phone includes a main power source and an auxiliary power source, and when the power supply from the main power source is cut off or the main power source is removed, Each of the above components functions by receiving power supply from an auxiliary power source.

  In this way, when the power supply from the main power supply is cut off or the main power supply is removed, the power supply from the auxiliary power supply causes each component to function, so the person who tried to steal the mobile phone However, even when the mobile phone is turned off or the battery is removed, information leakage can be prevented.

  (4) In the data management system of the present invention, the first control unit transmits the data stored in the storage unit to a server device before erasing the data in the storage unit. It is said.

  As described above, since the data stored in the storage unit is transmitted to the server device before the data in the storage unit is erased, the server device can back up the data. Thereby, the user can use again the data erased from the mobile phone.

  (5) Further, in the data management system of the present invention, when the first control unit receives data that instructs forced erasure from the slave unit, the first control unit erases the data stored in the storage unit. It is a feature.

  As described above, when the data requesting the forced erasure is received from the slave unit, the data stored in the storage unit is erased. Therefore, when the user notices the loss of the cellular phone, the data inside the cellular phone is immediately Can be erased. As a result, information leakage can be prevented. For example, when a person who has forged a handset steals a mobile phone, the real handset notifies the user that a mobile phone emits a warning sound, thereby recognizing that there is no mobile phone nearby. Can forcibly erase the internal data from the handset.

  (6) In the data management system of the present invention, the slave unit is a value in which the distance between the mobile phone and a second short-range wireless communication unit that performs short-range wireless communication with the mobile phone is predetermined. A second determination unit that determines whether or not the volume has increased, and a second warning sound generation unit that generates a warning sound, wherein the second warning sound generation unit determines that the mobile phone And a warning sound is generated when the distance between and becomes larger than a predetermined value.

  As described above, since the warning sound is generated when the distance from the mobile phone becomes larger than a predetermined value, it is possible to notify the user that the mobile phone is not nearby.

  (7) Further, in the data management system of the present invention, the slave unit transmits an operation unit that receives a user operation and data that instructs the mobile phone to be forcibly erased when the operation unit is operated. And a second control unit for performing the above.

  As described above, since the data for ordering forced erasure is transmitted from the slave unit to the mobile phone, the mobile phone can erase the data stored in the storage unit. Thereby, when the user notices the loss of the mobile phone, the data in the mobile phone can be immediately erased. As a result, information leakage can be prevented. For example, when a person who has forged a handset steals a mobile phone, the real handset notifies the user that a mobile phone emits a warning sound, thereby recognizing that there is no mobile phone nearby. Can forcibly erase the internal data from the handset.

  (8) Moreover, the server apparatus of this invention is characterized by storing the data received from the mobile telephone in the data management system of Claim 4 as backup data.

  Thus, since the data received from the mobile phone in the data management system according to claim 4 is stored as backup data, the mobile phone can back up the data before erasing the data in the storage unit. It becomes. Thereby, the user can use again the data erased from the mobile phone.

  According to the present invention, when the distance between the mobile phone and the handset becomes larger than a predetermined value, the data in the storage unit is erased. This eliminates the need for information leakage. Further, since no instruction from the center is required, information leakage can be prevented even when the mobile phone is out of the communication range.

  FIG. 1 is a diagram showing a schematic configuration of a data management system according to the present embodiment. The data management system 1 includes a mobile phone 10 and a handset 20. The mobile phone 10 can be connected to the mobile phone network 25 by a mobile phone antenna 11 via a base station device (not shown). In addition, the mobile phone 10 includes a mobile phone communication module 12, and performs processing necessary for wireless communication such as modulation and demodulation, A / D conversion, and D / A conversion by the mobile phone communication module. The internal data memory 13 stores data that can be used by the mobile phone 10. For example, the user's personal information, E-mail address, URL, image data, and the like. The short-range wireless module 14 performs short-range wireless communication with the handset 20 via the short-range wireless input / output unit 16. For this near field communication, for example, Bluetooth (registered trademark) can be applied.

  The control unit 15 controls the overall functions of the mobile phone 10. In particular, the mobile phone communication module 12, internal data memory 13, and short-range wireless module 14 are controlled. The control unit 15 has a timer function, and counts the passage of time when a predetermined condition is satisfied. Further, the mobile phone 10 receives power supply from the power supply unit 17. The power supply unit 17 includes an auxiliary power source 18 that cannot be removed and a removable power source battery 19.

  The handset 20 includes a short-range wireless input / output unit 21 and a short-range wireless module 22 that perform short-range wireless communication with the mobile phone 10. The control unit 23 controls the functions of the entire slave unit 20. Moreover, the control part 23 is provided with the timer which is not shown in figure, and can count progress of time. In addition, the slave unit may be provided with a maintenance button (not shown). When the user operates the maintenance button, the data management system can be set to a maintenance mode to be described later.

  The cellular phone 10 can communicate with the server device (maintenance service center side server) 30 via the cellular phone network 25. The server device 30 includes an information backup unit 32 that stores received data under the control of the control unit 31.

  Next, the operation of the data management system according to this embodiment configured as described above will be described. The operation of the data management system according to the present embodiment can be considered by dividing it into the following four patterns.

(Pattern A: When lost)
The mobile phone and the handset always perform some short-range communication. The user wears the handset separately from the mobile phone, and even if the mobile phone is left behind, the user wears the handset and acts. If the user and the handset are separated from the mobile phone by a certain distance or more, short-distance communication cannot be performed, so that the handset and the mobile phone both sound a warning sound or the like. If the user notices a warning sound or the like and returns to the mobile phone within a certain time, short-range communication resumes, and both the slave unit and the mobile phone stop sounding the warning sound and return to the normal mode.

  If the owner is not aware of the warning sound or the like and is away from the mobile phone for a certain period of time, the internal data of the mobile phone is erased by the internal control of the mobile phone. In addition, before erasing data, there is a case where data is not transferred to the center side server device according to a preset security level.

(Pattern B: Theft)
Even when a person who wants to steal a mobile phone turns off the power of the mobile phone or removes the battery and carries it away, the same processing as pattern A can be performed by the auxiliary power.

(Pattern C: When stolen by a counterfeit handset)
If a counterfeit handset with the same ID as the handset is used and the mobile phone is stolen, the mobile phone remains in a normal state and does not proceed with alarm sound generation or data erasure under the control of the counterfeit handset and the mobile phone. However, it becomes possible for a user who has noticed theft by a warning sound of a real handset to issue a forced data erasure command from the handset to the mobile phone by short-range communication.

(Pattern D: When maintenance mode is set)
In order to prevent warnings and data erasure from being performed when the power of the slave unit or the cellular phone is turned off or during a normal occasion such as charging, the maintenance mode can be switched. Switching to the maintenance mode can be performed only by operating the slave unit and the mobile phone as a set so that the mobile phone cannot be switched to the maintenance mode when the mobile phone is stolen.

  2 to 8 are flowcharts showing the operation of the data management system according to the present embodiment. In the data management system according to the present embodiment, when both devices are separated by a short distance communication function between the child device and the mobile phone, i.e., when the distance is less than a communicable threshold of weak power for short distance communication, both devices When a specific condition is met, the internal data of the mobile phone is automatically deleted. This is intended for when a mobile phone is lost or stolen, but when either power is turned off, a warning sound is generated and data is automatically deleted, which is inconvenient because the frequency is often outside this purpose. It may become.

  Therefore, in the flowchart shown in FIG. 2, it is possible to switch to the “maintenance mode” in order not to generate an unintended warning sound related to the remaining amount of power and automatic data deletion. When the mobile phone is stolen, it is not possible to prevent theft if it is switched to the maintenance mode only by operating the mobile phone. Therefore, it is important to enter the maintenance mode only by operating both terminals as a set.

  First, with reference to FIG. 2, the daily operation of the mobile phone and the operation in the maintenance mode will be described. In FIG. 2, the mobile phone normally has a timer value set to 0 and is in a state where no warning sound is generated (step S1). Further, short-distance wireless communication is performed with the slave unit (step S2). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m. On the other hand, the slave unit is normally in a state where no warning sound is generated (step S3) and performs short-distance wireless communication with the mobile phone (step S4). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m.

  Next, it is determined whether or not the user manually switches the slave unit and the mobile phone to the maintenance mode at the same time (step S5), and when the user manually switches the slave unit and the mobile phone to the maintenance mode at the same time, The handset and the mobile phone are set to the maintenance mode (step S6). In step S5, if the handset and the mobile phone cannot be switched to the maintenance mode at the same time, the handset performs short-range wireless communication with the mobile phone (step S7). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m. Next, it is determined whether or not the power remaining amount of the slave unit has become 10% or less of the full charge (step S8). Transition to.

  On the other hand, in step S8, when the remaining power of the slave unit becomes 10% or less of the full charge, a warning sound is generated and a display to pay attention to the power is displayed (step S9). Next, it is determined whether or not the power remaining amount of the child device has become 5% or less of the full charge (step S10). By charging (step S11), the process proceeds to step S3. On the other hand, in step S10, when the remaining power of the slave unit becomes 5% or less of the full charge, a slave unit power source caution signal is generated to the mobile phone by short-range communication (step S12). When the mobile phone receives a handset power supply attention signal from the handset by short-range communication (step S13), the mobile phone transitions to a flow A shown in FIG.

  If the handset and the mobile phone are not switched to the maintenance mode at the same time in step S5, the mobile phone determines whether the power button is turned off or the power battery is removed (step S14). When the power button is turned off or the power battery is removed, the auxiliary power is activated (step S15), and the process proceeds to the flow B shown in FIG. In step S14, if the power button is not turned OFF and the power battery is not removed, it is determined whether the remaining power is 10% or less of the full charge (step S16), and the remaining power is full. If it is not less than 10% of the charge, the process proceeds to step S1.

  On the other hand, in step S16, when the remaining amount of power becomes 10% or less of the full charge, a warning sound is generated and a display to pay attention to the power is displayed (step S17). Next, it is determined whether or not the remaining power level is 5% or less of the full charge (step S18). If the remaining power level is not 5% or less of the full charge, the user performs charging ( Step S19) and the process proceeds to Step S1. On the other hand, in step S18, when the remaining amount of power becomes 5% or less of the full charge, a portable power source caution signal is generated to the slave unit by short-range communication (step S20). When the slave unit receives the form power supply attention signal from the mobile phone by the short-range communication (step S21), the slave unit transitions to a flow A shown in FIG. In the flowchart shown in FIG. 2, the short-distance communication such as Bluetooth (registered trademark) between the slave unit and the mobile phone is confirmed by the identification ID for judging each other, or the mobile phone is operated by the center side server. The flow for identifying and confirming is omitted.

  Next, with reference to FIG. 3, the flow A among the daily operation and the maintenance mode operation of the mobile phone will be described. This flow A shows an operation in the case where the remaining power of the slave unit or the mobile phone becomes small without the user entering the maintenance mode. In FIG. 3, when a warning sound is generated on the mobile phone or a power warning is displayed (step S22), the mobile phone checks the security level (step S23).

  Here, the security level is the highest at the A level and is set to the confidential level. Further, it is assumed that the B level is a standard level and the C level has no security measures. In general use set to the B level, a warning sound is generated in the slave unit and the cellular phone, or after a power warning is displayed, the maintenance mode is switched to after the warning sound is stopped. In the confidential use set to the A level, the internal data is automatically deleted for the warning sound or the like unless the user manually switches to the maintenance mode. This completes the security.

  In step S23 of FIG. 3, when the security level is B level, the warning sound is stopped (step S24), and the mode is automatically switched to the maintenance mode (step S25). Further, when a warning sound is generated in the slave unit or a power warning is displayed (step S26), the security level is confirmed in the slave unit (step S27). If the security level is B level in step S27, the warning sound is stopped (step S24) and the mode is automatically switched to the maintenance mode (step S25).

  On the other hand, if the security level is A level in step S23 and step S27, the timer of the control unit starts counting and continues counting (step S28). Next, it is determined whether or not the handset and the mobile phone are simultaneously switched to the maintenance mode (step S29). If the handset and the mobile phone are simultaneously switched to the maintenance mode, the warning sound is stopped (step S30). ) And the maintenance mode is switched by the user's manual operation (step S31). In step S29, if the slave unit and the mobile phone cannot be switched to the maintenance mode at the same time, it is determined whether the timer count value is within a certain value (step S32), and the timer count value is within the certain value. If there is, the process proceeds to step S28. On the other hand, if the count value of the timer is not within a certain value in step S32, the internal data is erased (step S33). In the flowchart shown in FIG. 3, the identification ID for judging each other is confirmed by short-range communication such as Bluetooth (registered trademark) between the slave unit and the cellular phone, or the cellular phone is operated by the center side server. The flow for identifying and confirming is omitted.

  FIG. 4 is a flowchart showing the operation when the mobile phone is lost. In FIG. 4, the mobile phone is normally in a state where the timer value is set to 0 and no warning sound is generated (step S40). Further, short-distance wireless communication is performed with the slave unit (step S41). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m. On the other hand, the slave unit is normally in a state where no warning sound is generated (step S42) and performs short-distance wireless communication with the mobile phone (step S43). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m.

  Next, it is determined whether or not the handset and the mobile phone are separated from each other by a certain distance (step S44). In other words, it is determined whether or not the communication threshold value of weak power for short-distance communication has been reached. If the handset and the mobile phone are not separated from each other by a certain distance, the mobile phone shifts to step S40, and the handset goes to step S42. On the other hand, if it is determined in step S44 that the handset and the mobile phone are separated from each other by a certain distance, it is determined whether or not the maintenance mode is set (step S45). In the maintenance mode, the process proceeds to step S40 in the case of a mobile phone, and the process proceeds to step S42 in the case of a slave unit. On the other hand, if the maintenance mode is not set in step S45, the slave unit continues to sound a warning sound (step S46). In the mobile phone, the timer of the control unit starts counting and continues counting (step S47). The warning sound continues to sound even on the mobile phone (step S48).

  Next, it is determined whether the power button has been turned off or the power battery has been removed (step S49). If the power button has been turned off or the power battery has been removed, the auxiliary power source is activated. (Step S50), the process proceeds to the flow B shown in FIG. On the other hand, if the power button is not turned off and the power battery is not removed in step S49, it is determined whether the count value of the timer is within a certain value (for example, 30 seconds) (step S51). ). If the count value of the timer is within a certain value, it is determined whether or not the child device and the mobile phone are within a certain distance (step S52), and the child device and the portable phone are at a certain distance (for example, 2 m ), The warning sound is stopped in the slave unit (step S53), and the process proceeds to step S42. In the mobile phone, the timer of the control unit is reset (step S54), the warning sound is stopped (step S55), and the process proceeds to step S40.

  On the other hand, if the timer count value is not within a certain value in step S51, that is, if the timer count value exceeds the certain value, the security level is confirmed (step S56), and the security level is B level. If there is, the internal data is transmitted (transferred) to the server device on the center side (step S57). When the transmission is completed, the internal data is deleted (step S58). If the security level is A level in step S56, the internal data is deleted (step S58). In the flowchart shown in FIG. 4, confirmation is made with an identification ID for judging each other in short-distance communication such as Bluetooth (registered trademark) between the slave unit and the mobile phone, or the mobile phone at the center side server. The flow for identifying and confirming is omitted.

  FIG. 5 is a flowchart showing the operation when the mobile phone is stolen or when the mobile phone is at risk of being stolen. In FIG. 5, the mobile phone is normally in a state where the timer value is set to 0 and no warning sound is generated (step S60). Further, short-distance wireless communication is performed with the slave unit (step S61). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m. On the other hand, the slave unit is normally in a state where no warning sound is generated (step S62) and performs short-distance wireless communication with the mobile phone (step S63). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m.

  In the mobile phone, it is determined whether the power button is turned off or the power battery is removed (step S64). If the power button is not turned off and the power battery is not removed, the process proceeds to step S1 shown in FIG. On the other hand, if the power button is turned off or the power battery is removed in step S64, the auxiliary power supply is activated (step S65), and the process proceeds to flow B.

  In the flow B, first, the screen display of the mobile phone disappears (step S66). However, in step S66, other functions are held by the auxiliary power source. Next, it is determined whether or not the maintenance mode is set (step S67). If the maintenance mode is set, the process proceeds to step S60. On the other hand, if the maintenance mode is not set, it is determined whether or not the count value of the timer is 0 (step S68). If the count value of the timer is 0, the process proceeds to step S70. If the count value of the timer is 0, as a special case, the warning sound is changed to vibration (step S69), and the process proceeds to step S70. Next, the timer of the control unit starts counting and continues counting (step S70).

  Next, it is determined whether or not the handset and the mobile phone are separated from each other by a certain distance (step S71). When the handset and the mobile phone are separated from each other by a certain distance or more, the handset continues to sound a warning sound. (Step S72), a warning sound continues to sound even on the mobile phone (Step S73). When the warning sound is changed to vibration in step S69, vibration is performed in step S73. And it changes to step S74. If it is determined in step S71 that the handset and the mobile phone are not separated by a certain distance or more, the process proceeds to step S74.

  Next, it is determined whether or not the slave unit and the mobile phone are simultaneously switched to the maintenance mode (step S75). If the slave unit and the mobile phone are simultaneously switched to the maintenance mode, the warning sound is stopped. (Step S75), the mode is switched to the maintenance mode by the user's manual operation (Step S76). On the other hand, if the slave unit and the mobile phone cannot be switched to the maintenance mode at the same time in step S74, it is determined whether or not the count value of the timer is within a certain value (for example, 30 seconds) (step S77). When the count value of the timer is within a certain value, the process proceeds to step S70.

  On the other hand, if the timer count value is not within a certain value in step S77, that is, if the timer count value exceeds the certain value, the security level is confirmed (step S78), and the security level is B level. If there is, the internal data is transmitted (transferred) to the server device on the center side (step S79). When the transmission is completed, the internal data is deleted (step S80). In step S78, if the security level is A level, the internal data is deleted (step S80). In the flowchart shown in FIG. 5, confirmation by identification ID for judging each other in short-distance communication such as Bluetooth (registered trademark) between the slave unit and the mobile phone, or the mobile phone at the center side server The flow for identifying and confirming is omitted.

  FIG. 6 is a flowchart showing the operation of releasing the maintenance mode. While the slave unit and the mobile phone are set to the maintenance mode (step S81), the mobile phone determines whether or not the maintenance mode timer has passed 1 minute (step S82). If the maintenance mode timer has not passed 1 minute, the process proceeds to step S81. If the maintenance mode timer has passed 1 minute, it is determined whether the power button has been turned off or the power battery has been removed (step S83). If the power button is turned off or the power battery is removed, the timer is reset (step S84), and the process proceeds to step S81. On the other hand, if the power button is not turned off and the power battery is not removed in step S83, it is determined whether the remaining power level is 10% or less of the full charge (step S85), and the remaining power level is determined. Is 10% or less of the full charge, the timer is reset (step S86), and the process proceeds to step S81. On the other hand, if the remaining amount of power is not less than 10% of full charge in step S85, the maintenance mode is canceled and the normal mode is entered (step S87).

  Further, the slave unit determines whether or not the maintenance mode timer has passed 1 minute (step S88). If the maintenance mode timer has not passed 1 minute, the process proceeds to step S81. If the maintenance mode timer has passed 1 minute, it is determined whether the remaining power level is 10% or less of the full charge (step S89). If the remaining power level is 10% or less of the full charge, The timer is reset (step S90), and the process proceeds to step S81. On the other hand, if the remaining power is not less than 10% of full charge in step S89, the maintenance mode is canceled and the normal mode is entered (step S87).

  FIG. 7 is a flowchart showing the switching operation to the maintenance mode by the user's manual operation. When the user operates the maintenance button of the slave unit (step S100), the mobile phone is notified of maintenance preparation by short-range communication (step S101). In the slave unit, the timer starts counting (step S102). In the mobile phone, when maintenance preparation is received from the handset by short-range communication (step S103), the timer starts counting (step S104). The mobile phone determines whether or not the mobile phone is being prepared for maintenance (step S105). If the mobile phone is being prepared for maintenance, the mobile phone notifies the slave (step S109). Further, the process shifts to the maintenance mode (step S106). In step S105, when maintenance preparation is not in progress, the process proceeds to step S107. Next, the mobile phone determines whether or not the timer count value is equal to or less than a certain time (eg, 3 seconds) (step S107). If the timer count value is equal to or less than the certain time, the process proceeds to step S105. To do. On the other hand, if the count value of the timer is not less than the predetermined time, it is timed out and the normal mode is maintained (step S108).

  In the slave unit, it is determined whether a notification indicating that maintenance is being prepared by short-range communication is received from the mobile phone (step S110). If a notification indicating that maintenance is being prepared is received, the maintenance mode is entered. Transition is made (step S111). On the other hand, when not receiving notification that maintenance preparation is in progress, the process proceeds to step S112. Next, the slave unit determines whether or not the count value of the timer is equal to or less than a certain time (for example, 3 seconds) (step S112). If the count value of the timer is equal to or less than the certain time, the process proceeds to step S109. To do. On the other hand, if the count value of the timer is not less than the predetermined time, it is timed out and the normal mode is maintained (step S113).

  FIG. 8 is a flowchart showing an operation when transmitting data for instructing forced erasure from the slave unit to the mobile phone. Here, it is assumed that a third party is trying to steal a mobile phone using a forged handset. That is, in short-distance communication such as Bluetooth (registered trademark) performed between the slave unit and the mobile phone, security measures for ID confirmation and the like are set, but it cannot be said that there is no vulnerability and the same. There is a possibility that a person who forged the ID handset will bring the forged handset and steal the mobile phone. In this case, the stolen mobile phone may leak internal data in a normal state. In this embodiment, in such a case, the security level of the mobile phone is ensured by transmitting a command for forcibly erasing data from the slave unit to the mobile phone.

  In FIG. 8, in the mobile phone, the timer value is normally set to 0 and no warning sound is generated (step S120). Further, short-distance wireless communication is performed with the slave unit (step S121). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m. On the other hand, the slave unit is normally in a state where no warning sound is generated (step S122), and performs short-range wireless communication with the mobile phone (step S123). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m. Further, even in the counterfeit handset, there is normally no warning sound (step S124), and short-distance wireless communication with the mobile phone is performed (step S125). At this time, short-range communication is performed in a “short-distance mode” that can handle distances up to 2 m.

  Next, it is determined whether or not the handset and the mobile phone are separated from each other by a certain distance (step S126). If the handset and the mobile phone are not separated from each other by a certain distance, the normal state is maintained. (Step S127). On the other hand, when the handset and the mobile phone are separated by a certain distance or more, the handset keeps sounding a warning sound (step S128). On the other hand, it is determined whether or not the mobile phone and the counterfeit handset are separated from each other by a certain distance (step S129). If the mobile phone and the counterfeit handset are separated from each other by a certain distance, the flowchart shown in FIG. 4 or FIG. (Step S130). On the other hand, when the mobile phone and the counterfeit handset are not separated from each other by a certain distance, no warning sound is generated (step S131). That is, the normal state remains. Therefore, the internal data of the mobile phone is not erased as it is.

  However, in step S128, since the warning sound is continuously sounding in the authentic slave unit, the user can notice that the mobile phone is lost. When the user operates the forced data erasure button on the handset (step S132), data for instructing the mobile phone to perform forced erasure is transmitted in the long distance mode (for example, transmission up to a distance of 10 m) in short distance communication. (Step S133).

  In the mobile phone, when a forced data erasure command is received from a genuine handset (step S134), the long distance mode in the short distance communication is received by the same receiver as the short distance communication mode or another receiver ( In step S135, the security level is confirmed (step S136). If the security level is the B level, nothing is handled and the normal state is maintained (step S137), and if the security level is the A level, the internal data is deleted (step S138).

  As described above, according to the present embodiment, when the distance between the mobile phone and the handset becomes larger than a predetermined value, the data in the storage unit is erased. It is possible to prevent information leakage effectively without taking time to execute. Further, since no instruction from the center is required, information leakage can be prevented even when the mobile phone is out of the communication range.

  That is, in the conventional method, since it takes time to take the erasure measure, there is a risk that the confidential data inside the mobile phone after loss / theft may leak information before the measure is completed. Disappear. In the prior art, since control on the center side is required, there is a risk of information leakage when the mobile phone is out of service or in a power-off state. However, according to the present invention, this possibility is eliminated. Further, in the related art, when the mobile phone itself controls, there is a risk that data is frequently deleted even at a normal opportunity other than at the time of loss or theft. However, according to the present invention, this possibility is eliminated. Further, in the prior art, when the control is performed by the short-distance communication between the mobile phone and the slave unit, the alarm level remains, and there is a possibility that information is leaked by shaking the alarm. However, according to the present invention, this possibility is eliminated. Further, in the prior art, when control is performed by short-range communication between a mobile phone and a slave unit, information may be leaked due to theft using a counterfeit slave unit. However, according to the present invention, this possibility is eliminated. In addition, when using a mobile phone as a corporation, particularly when confidential data or customer information that is difficult to leak information is stored inside the mobile phone for business purposes, the present invention provides a complete measure against information leakage. It is extremely effective.

It is a figure which shows schematic structure of the data management system which concerns on this embodiment. It is a flowchart which shows operation | movement of the data management system which concerns on this embodiment. It is a flowchart which shows operation | movement of the data management system which concerns on this embodiment. It is a flowchart which shows operation | movement of the data management system which concerns on this embodiment. It is a flowchart which shows operation | movement of the data management system which concerns on this embodiment. It is a flowchart which shows operation | movement of the data management system which concerns on this embodiment. It is a flowchart which shows operation | movement of the data management system which concerns on this embodiment. It is a flowchart which shows operation | movement of the data management system which concerns on this embodiment.

Explanation of symbols

1 data management system 10 mobile phone 11 mobile phone antenna 12 mobile phone communication module 13 internal data memory 14 short-range wireless module 15 control unit 16 short-range wireless input / output unit 17 power supply unit 18 auxiliary power source 19 power supply battery 20 slave unit 21 near Distance wireless input / output unit 22 Short-range wireless module 23 Control unit 25 Mobile phone network 30 Server device (maintenance service center server)
31 Control unit 32 Information backup unit

Claims (8)

A mobile phone data management system comprising a mobile phone and a handset capable of short-range wireless communication only between the mobile phone,
The mobile phone is
A first short-range wireless communication unit that performs short-range wireless communication with the slave unit;
A storage unit for storing data;
A first determination unit that determines whether or not a distance from the slave unit is greater than a predetermined value;
As a result of the determination, a data management system comprising: a first control unit that erases data in the storage unit when the distance to the slave unit is greater than a predetermined value. The mobile phone is
A timer that counts the passage of time;
A first warning sound generating unit for generating a warning sound;
As a result of the determination, the timer starts counting when the distance to the slave unit becomes larger than a predetermined value,
The first warning sound generation unit generates a warning sound when the distance from the slave unit is larger than a predetermined value as a result of the determination,
The first control unit determines whether the count value of the timer has reached a predetermined value, and, as a result of the determination, when the count value of the timer has reached a predetermined value, 2. The data management system according to claim 1, wherein the data in the storage unit is erased. The mobile phone is
With main power supply and auxiliary power supply
The power supply from the main power supply is cut off, or when the main power supply is removed, the power supply is supplied from the auxiliary power supply so that each of the components functions. Item 3. A data management system according to item 2.   The said 1st control part transmits the data memorize | stored in the said memory | storage part to a server apparatus, before erasing the data of the said memory | storage part, The claim 1 characterized by the above-mentioned. The data management system described.   The said 1st control part erase | eliminates the data memorize | stored in the said memory | storage part, when the data which command forced deletion from the said subunit | mobile_unit are received. The data management system described in 1. The slave is
A second near field communication unit that performs near field communication with the mobile phone;
A second determination unit that determines whether or not a distance from the mobile phone is greater than a predetermined value;
A second warning sound generator for generating a warning sound,
The second warning sound generation unit generates a warning sound when the distance from the mobile phone becomes larger than a predetermined value as a result of the determination. A data management system according to any of the above. The slave is
An operation unit for receiving user operations;
The data management system according to claim 6, further comprising: a second control unit that transmits data for instructing forced erasure to the mobile phone when the operation unit is operated.   5. A server apparatus for storing data received from a mobile phone in the data management system according to claim 4, as backup data.

Images