JP2006287853A - Method for managing data stored in mobile communication apparatus, backup server, and service device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a user service using backed-up data by safely managing data stored in a mobile communication apparatus. <P>SOLUTION: A backup server 10 receives data stored in a memory 112 of a mobile communication apparatus 20, stores the received memory data in a storage device 15 and transmits the memory data stored in the storage device 15 to a service device 60 via the Internet 30 in response to a download request transmitted from the service device 60 via the Internet 30. The service device 60 receives the memory data transmitted from the backup server 10 and transfers them to the mobile communication apparatus 20. Furthermore, the backup server 10 discloses the memory data stored in the storage device 15 on the Internet 30. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a method for managing data stored in a mobile communication device, a backup server, and a service device.

  Recent mobile phones have various additional functions, and the built-in memory of the mobile phone stores various data (hereinafter referred to as memory data) such as a phone book, schedule, and image data taken with an attached camera. ing. The built-in memory stores information related to the settings of the functions and operations of the mobile phone, such as the volume and type of the ringtone and the screen density.

Here, if such information is lost due to a failure or loss of the mobile phone, the user suffers a great deal of damage. Thus, for example, Patent Document 1 discloses a technology for backing up memory data of a mobile phone to a server on the Internet.
JP 2004-228659 A

  By the way, handling of personal information has become a problem in recent years, and it is required to ensure sufficient security when handling personal information backed up on a server. On the other hand, in order to respond to diversifying user needs, it is also necessary to effectively return the data backed up on the server to the user service.

  The present invention has been made in view of such a background. The data stored in the mobile communication device can be safely managed, and the user service using the backed-up data can be provided. It is an object of the present invention to provide a data management method, a backup server, and a service device.

  The main invention of the present invention to achieve the above object is to provide a mobile communication device, a backup server that is communicably connected to the mobile communication device via a mobile phone network, a storage device that is connected to the backup server, A method of managing data stored in a mobile communication device, which is performed in a system including a service device connected to the backup server via the Internet so as to be communicable and communicably connected to the mobile communication device The backup server receives data stored in the mobile communication device transmitted from the mobile communication device via the mobile phone network, and the backup server receives the data Storing the data in the storage device, and the backup server interfacing from the service device. Receiving the data transmission request transmitted via the network, and the backup server transmitting the data stored in the storage device to the service device via the Internet; The service device includes the step of receiving the data, and the service device transmits the received data to the portable communication device.

  According to the above invention, even when data stored in the mobile communication device is lost due to a failure or loss of the mobile communication device, the data can be recovered through the service device. For this reason, the data memorize | stored in the portable communication apparatus can be managed safely. The mobile communication device is, for example, a mobile phone.

  The backup server receives the data in an encrypted state from the portable communication device, and stores the data in the storage device in an encrypted state. Therefore, the data stored in the mobile communication device can be safely managed in the storage device.

  The backup server has a function of publishing the data stored in the storage device to the Internet. This makes it possible to provide a user service using the backed up data.

  According to the present invention, data stored in a mobile communication device can be backed up in a safe state, and user service can be provided using the backed up data.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
FIG. 1 illustrates a system (hereinafter referred to as a data management system) that manages processing (hereinafter referred to as backup processing) related to backup of data (hereinafter referred to as memory data) stored in a memory of a mobile phone, which is described as an embodiment of the present invention. 1). In FIG. 1, a backup server 10 is a computer operated by a communication carrier or the like, and is connected to the Internet 30. A storage device 15 for storing memory data is connected to the backup server 10. The mobile phone 20 has a normal call function performed by connecting to the mobile phone network 40 and a function of connecting the mobile phone network 40 to the Internet 30 via the gateway device 50. The service device 60 is a computer installed in a service store such as a mobile phone shop developed by a mobile phone company or a convenience store, and is connected to the Internet 30. The service device 60 may be communicably connected to the backup server 10 via a dedicated line. The service device 60 has a function of communicating with the mobile phone 20 wirelessly or by wire.

  FIG. 2 shows a hardware configuration of the backup server 10. The backup server 10 includes a CPU 111, a memory 112 such as a RAM / ROM, a hard disk 113, an input device 114 such as a keyboard and a mouse as a user interface for inputting data, a cathode ray tube display as a user interface for displaying data, A display device 115 such as a liquid crystal display and a communication interface 116 for connecting to the Internet 30 are included. The storage device 15 connected to the backup server 10 includes the hard disk 113, a hard disk externally attached to the backup server 10, a semiconductor memory, and the like.

  FIG. 3 shows the software configuration of the backup server 10. Each component shown in the figure is realized by the hardware of the backup server 10 or the CPU 111 executing a program stored in the memory 112 or the hard disk 113.

  In the figure, an Internet communication unit 311 makes a function of performing communication with other devices on the Internet 30 and data stored in the storage device 15 accessible from other devices on the Internet 30. It has a function as a Web server. The Internet communication unit 311 can also perform communication using an encrypted communication method such as SSL (Secure Socket Layer) (for example, HTTPS (Hypertext Transfer Protocol Security)). The memory data storage processing unit 312 stores the memory data transmitted from the mobile phone 20 in the storage device 15. The function of the memory data storage processing unit 312 is realized by a DBMS (DataBase Management System) operating in the backup server 10. The memory data transmission start command transmission unit 313 transmits a command request to start transmission of memory data. The memory data erasure command transmission unit 314 transmits a memory data erasure command request possessed by the mobile phone 20.

  FIG. 4 shows a hardware configuration of the mobile phone 20. The cellular phone 20 includes a CPU 411, a memory 412 such as a ROM and a RAM, an input device 413, a display device 414, a sound processing device 415, a microphone 416, a speaker 417, a communication device 418, a communication antenna 419, a short-range communication interface 420, and an IC card. A device 421 and an IC card type memory 422 attached to the mobile phone 20 are included.

  The memory 412 stores programs and data for realizing various functions of the mobile phone 20. The input device 413 is a user interface such as an operation button or an operation dial. The display device 414 is a display device such as a liquid crystal display, and is a user interface on which various types of information presented to the user are displayed. The voice processing device 415 outputs a transmission voice signal input from the microphone 416 to the communication device 418, and outputs a reception voice signal input from the communication device 418 to the speaker 417. The communication device 418 performs wireless communication with the mobile phone network 40 that is performed via the communication antenna 419. The short-range communication interface 420 is a communication interface for connecting to the service device 60 so as to be communicable through wired or wireless communication, and is a communication interface such as Bluetooth, infrared communication (IrDA), or wireless LAN. The IC card device 421 is a device that reads / writes data from / to the IC card type memory 422. The key information storage device 425 stores key information (for example, a password or biometric information) input by the user.

  FIG. 5 shows a software configuration of the mobile phone 20. Each component shown in the figure is realized by executing a program stored in the memory 412 by the hardware of the mobile phone 20 or the CPU 411.

  In the figure, an Internet communication unit 511 performs communication with other devices connected to the Internet 30. Note that the Internet communication unit 511 also performs communication using an encrypted communication method such as SSL (Secure Socket Layer) (for example, HTTPS (Hypertext Transfer Protocol Security)). The memory data transmission unit 512 receives a command request to start data transmission from the backup server 10, and stores data (hereinafter referred to as memory data) stored in the memory 412 in response to the reception of the command request. Send to. The memory data encryption unit 513 encrypts the memory data with the key information stored in the key information storage device 425. The memory data erasure / encryption request receiving unit 514 receives an erasure / encryption execution request (to be described later) from the service device 60, and erases or encrypts the memory data. The service device communication unit 515 performs processing related to communication performed with the service device 60. The memory data download unit 516 stores the memory data received from the service device 60 in the storage device 15. The memory data decoding unit 517 performs a process related to decoding of the memory data received from the service device. The near field communication unit 518 performs processing related to communication with the service device 60 performed by the near field communication interface 420.

  FIG. 6 shows the hardware configuration of the service device 60. The service device 60 includes a CPU 611, a memory 612 such as a RAM / ROM, a hard disk 613, an input device 614 such as a keyboard and a mouse as a user interface for inputting data, a cathode ray tube display as a user interface for displaying data, It includes a display device 615 such as a liquid crystal display, a communication interface 616 for connecting to the Internet 30, a short-range communication interface 617, and the like. The short-range communication interface 617 is a communication interface for connecting to the mobile phone 20 so as to be communicable through wired or wireless communication, and is a communication interface such as Bluetooth, infrared communication (IrDA), or wireless LAN.

  FIG. 7 shows the software configuration of the service device 60. Each unit shown in the figure is realized by the hardware of the service device 60 or the CPU 611 executing a program stored in the memory 612 or the hard disk 613.

  In the figure, an Internet communication unit 711 performs communication with other devices on the Internet 30. The Internet communication unit 311 also performs communication using an encrypted communication method such as SSL (Secure Socket Layer) (for example, HTTPS (Hypertext Transfer Protocol Security)). The backup server communication unit 712 performs processing related to communication performed with the backup server 10. The memory data receiving unit 713 receives memory data transmitted from the backup server 10. The erasure encryption request transmission unit 714 transmits an erasure encryption request to be described later to the backup server 10. The memory data decryption unit 716 performs processing related to decryption of memory data transmitted from the backup server 10. The short-range communication unit 717 performs processing related to communication with the mobile phone 20 performed by the short-range communication interface 617.

  FIG. 8 shows the configuration of memory data management information (hereinafter referred to as memory data management information 800) stored in the memory 412 of the mobile phone 20. In the figure, the data content 811 is set with information indicating the type of memory data. The memory data management information 800 manages five types of memory data (IC card information, telephone book 1, telephone book 2, image data, music data).

  In the change date 812, the update date of the memory data is set. The transmission date and time 813 is set with the date and time when the memory data was transmitted to the backup server 10 (that is, backed up). In the data attribute 815, the data attribute of the memory data is set. Here, the data attribute is information indicating a management form of the memory data. In the mobile phone 20, the memory data is classified and managed in a plurality of groups for each data attribute. FIG. 8 illustrates three data attributes of “terminal information”, “secret information”, and “public information”. Among these, “terminal information” is a data attribute whose memory data is set to information stored in, for example, the IC card type memory 422. The “secret information” is a data attribute set to information that needs to be managed secretly in the backup server 10 as in the case where the memory data is personal information. “Public information” is a data attribute set in memory data disclosed on the Internet 30. In FIG. 8, the data attribute 815 of the memory data whose data content 811 is “image data” and “music data” is set to “public information”. A mechanism for releasing the memory data set in “public information” on the Internet 30 will be described later. Note that data attributes other than the data attributes exemplified above can be further defined.

  The contents of the public setting 816 of the memory data management information 800 are set when “public information” is set in the data attribute 815. In the public setting 816, information on access restriction applied to the memory data when the memory data is disclosed on the Internet 30 is set. For example, in FIG. 8, “password: XXXXXX” is set in the memory data disclosure setting 816 of “image data”. However, when another device on the Internet 30 accesses the memory data by this setting, Access restrictions requiring password entry are applied.

  Also, in the public setting 816, an option (hereinafter referred to as URL fixing option) for fixing the URL when the memory data is disclosed on the Internet 30 (hereinafter referred to as a save URL) so as not to be changed by each backup process is designated. can do. In addition, an option for securing a storage area that can be read and written from other devices connected to the Internet 30 associated with the saved URL (hereinafter referred to as a storage area addition option) can be set. The storage area secured by setting the storage area addition option can be used as an access log storage area for specific data stored in the URL of the save URL 814, for example. In addition, by using the storage area, the manufacturing number of the mobile phone 20 is set as public information, and when a failure occurs in the mobile phone 20, the manufacturer of the mobile phone 20 searches the Internet 30 for the manufacturing number. Thus, it becomes possible to access the storage area and to write information relating to the defect into the storage area. Also, it is possible to write an electronic mail describing defect information of the mobile phone 20 in the storage area by operating the mail server operating on the Internet 30 and the backup server 10 in cooperation.

  The storage URL 814 of the memory data management information 800 is set with a URL on the Internet 30 to which the memory data is published, which is issued by the backup server 10 when the memory data is “public information”. In FIG. 8, the URL “http: //XXX/X.jpg” is set in the “image data” storage URL 814. On the other hand, since the memory data of “music data” has not been transmitted to the backup server 10 (the transmission date and time is “untransmitted”), nothing is set in the storage URL 814 yet.

  By the way, the data attribute 815 and the public setting 816 may be managed by including them in the memory data management information 800 as described above. You may make it manage independently of information.

  FIG. 9A shows a configuration of data (hereinafter referred to as backup data 900) transmitted from the mobile phone 20 to the backup server 10 during the backup process. 9B shows the configuration of the data header 931 shown in FIG. 9A, FIG. 9C shows the configuration of the data body 932 shown in FIG. 9A, and FIG. 9D shows the configuration of the data information 9321 shown in FIG. 9C.

  The backup data 900 includes a data header 931 and a data body 932 (FIG. 9A). Among these, the data header 931 includes a user ID 9311 (for example, the telephone number of the mobile phone 20) that is a unique identifier assigned to each mobile phone 20, a data attribute 9312, and the date and time when the mobile phone 20 transmitted backup data. Transmission date and time 9313, server ID 9314 which is an identifier of the backup server 10 (for example, IP address of the backup server 10), key information 9315 such as a password and digital certificate necessary for the mobile phone 20 to access the backup server 10, data Information such as the data size 9316 of the body 932 is set (FIG. 9B). Note that the backup data 900 is created for each data attribute in principle.

  The data body 932 includes at least one combination of data information 9321 and encrypted / unencrypted data 9322 (FIG. 9C). The data information 9321 includes a data attribute 93211 in which a data attribute is set, a data ID 93212 in which a data ID that is information for identifying individual encrypted / unencrypted data is set, and encrypted / unencrypted data 9322. The data size 93213 in which the data size is set, the backup date and time 93214 in which the date and time when the encrypted / unencrypted data 9322 is stored in the storage device 15, the contents of the public setting 816 in the memory data management information 800, etc. are set Information 93215 specific to the data attribute to be processed is included.

  The encrypted / unencrypted data 9322 is set with memory data in an encrypted or non-encrypted state. When “terminal information” and “secret information” are set in the data attribute 9312, the memory data set in the encrypted / unencrypted data 933 is encrypted by the key information 9315. This encryption is performed in the mobile phone 20.

  FIG. 10 shows a configuration of memory data (hereinafter referred to as saved data 1000) stored in the storage device 15 by the backup server 10.

  In the user ID 1011 shown in the figure, the contents of the user ID 9311 set in the backup data 1000 are set. In the data area 1012, the contents of the data 931 and the data body 932 of the backup data 900 are set. The entity of the data area 1012 is a disk area partitioned for each data attribute, such as a folder in the file system, for example. If the data area 1012 is a folder, the stored data 1000 may be stored and managed in a different folder for each data attribute.

  In the data ID 1013, the data ID set in the data ID 93212 of the data information 9321 is set. Note that, even if the memory data stored in the data area is encrypted by this data ID, each data can be uniquely specified. In the reception date and time 1014, the date and time when the backup server 10 received the backup data 900 from the mobile phone 20 is set.

FIG. 11 shows a message flow of memory data backup processing between the mobile phone 20 and the backup server 10. First, the backup server 10 starts backup processing in accordance with preset time and conditions (S1151), and the backup server 10 issues a request to start transmission of backup data 900 (hereinafter referred to as backup start request) to the mobile phone. 20 (S1152).
As described above, the backup process is not started by a request from the mobile phone 20 but is started by the backup server 10 in response to an instruction from the backup server 10. Therefore, backup processing can be performed on the convenience of the backup server 10 (for example, the date and time when the load on the backup server 10 is low), thereby enabling efficient operation of the backup server 10.

  When receiving the backup start request transmitted from the backup server 10 (S1153), the mobile phone 20 authenticates the received backup start request. If there is no problem with the authentication, the cellular phone 20 transmits a reception response to the backup start request to the backup server 10 (S1154). When the backup server 10 receives the reception response transmitted from the mobile phone 20, the backup server 10 waits for reception of the backup data 900 transmitted from the mobile phone 20 (S1155).

  Next, the cellular phone 20 starts transmitting the backup data 900 to the backup server 10 (S1156 to S1168). Here, in the data management system 1 of the present embodiment, the backup data 900 is transmitted for each data attribute, and when the backup server 10 receives the backup data 900 for each data attribute, the backup data 900 is stored in the storage device 15. The data 1000 is stored (S1157, S1161, S1166). Further, every time the backup server 10 has received the backup data 900 for a certain data attribute, the backup server 10 transmits a reception response to the mobile phone 20 (S1158, S1162, S1167). In the message flow shown in the figure, the backup data 900 is transmitted to the backup server 10 in the order of “terminal information”, “secret information”, and “public information” (S1156, S1160, S1165). Not limited.

  When the backup data 900 having the data attribute “public information” is transmitted, the backup server 10 attaches the content of the storage URL 915 of the backup data 900 to the reception response of the backup data 900. When the mobile phone 20 receives the reception response of the backup data of the public information (S1168), the content of the storage URL attached thereto is set in the storage URL 814 of the memory data management information 800 (S1164).

  Conventionally, in order to publish image data or the like on the Internet, a predetermined operation is performed on the mobile phone, and the image data stored in the memory of the mobile phone is transferred to the web server one by one, and Although it is necessary to set the URL of the image data, the data management system 1 of the present embodiment uses data stored in the storage device 15 as image data to be disclosed and the URL is also a backup server. 10 is automatically assigned. Therefore, the user can easily publish data stored in the memory of the mobile phone such as image data to the Internet without being forced to perform troublesome operations.

  Next, when the backup server 10 has received all the backup data 900 transmitted from the mobile phone 20, it transmits a backup end response to the mobile phone 20 (S1169).

  By the way, the backup data 900 can be transmitted by transmitting only the backup data 900 for memory data having a specific data attribute. For example, memory data with frequently updated data attributes (for example, memory data with a data attribute of “terminal information”) and memory data with relatively low data frequency (for example, with a data attribute of “secret information”) In the case where there is memory data), the conditions for starting the backup process are individually set for each data attribute, and the memory data of each data attribute is individually backed up according to the condition set for each. It can also be done.

  In FIG. 11, transmission of the backup data 900 from the mobile phone 20 is started when the backup start request is transmitted from the backup server 10 to the mobile phone 20. The telephone 20 may be notified of the transmission date and time of the backup data 900, and the transmission of the backup data 900 may be started when the mobile telephone 20 reaches the notified transmission date and time. In this case, the notification of the transmission date and time may be performed in response to an inquiry from the mobile phone 20 to the backup server 10, or the backup server 10 to the mobile phone 20 regardless of whether there is an inquiry from the mobile phone 20. May be notified.

  FIG. 12 is a flowchart for explaining processing of the mobile phone 20 in the backup processing shown in FIG. When receiving the backup start request transmitted from the backup server 10 (S1211), the cellular phone 20 authenticates the received backup start request (S1212). This authentication is performed using authentication information (for example, a digital certificate, the IP address of the backup server 10) attached to the backup start request by the mobile phone 20. By performing this authentication, it is possible to prevent an illegal act of impersonating the backup server 10 and stealing the memory data of the mobile phone 20. When the authentication fails (S1212: authentication failure), the mobile phone 20 transmits an error message to the backup server 10 (S1213). When the authentication is successful (S1212: authentication success), the mobile phone 20 transmits a backup start request reception response to the backup server 10 (S1214).

  Next, the cellular phone 20 selects memory data to be backed up (S1215). This selection is performed with reference to the memory data management information 800, and the mobile phone 20 stores the memory data in which the transmission date / time in the memory data management information 800 is not set (that is, the memory data that has never been backed up in the past). ), Memory data whose change date and time 812 is later than the transmission date and time 813 (that is, memory data whose contents have been changed after being transmitted to the backup server 10 last time) is selected as memory data to be backed up.

  In S1211, the backup start request received by the mobile phone 20 from the backup server 10 may be set with an option (hereinafter, referred to as a full backup option) for backing up all memory data without performing the above selection. it can.

  In S1216, the cellular phone 20 refers to the memory data management information 800 and checks the data attribute of the memory data selected as the backup target (S1216). If the data attribute is “terminal information”, the process advances to step S1217. If the data attribute is “secret information”, the process advances to step S1218. If the data attribute is “public information”, the process advances to step S1219. In S1217, the contents of the data information 9321 set in the backup data 900 and the data obtained by encrypting the memory data set in the encrypted / unencrypted data 9322 are generated. In S1218, the contents of the data information 9321 set in the backup data 900 and data obtained by encrypting the memory data set in the encrypted / unencrypted data 9322 are generated. In S1219, data information 9321 set in the backup data 900 is generated. Note that the cellular phone 20 sets the memory data in the encrypted / unencrypted data 9322 of the backup data 900 while keeping the unencrypted state. Further, the cellular phone 20 checks whether or not the content is set in the public setting 816 of the memory data management information 800 (S1220). If the content is set (S1220: present), the content is determined as the characteristic of the data information 1032. Is set in the information 93215 (S1221). If there is no public setting (S1220: none), the process proceeds to S1222.

  In S1222, the mobile phone 20 determines, for each data attribute, whether or not the creation of the data information 9321 and the encrypted / unencrypted data 9322 has been completed for all the memory data to be backed up (S1222). When the creation of the data information 9321 and the encrypted / unencrypted data 9322 is completed for all the memory data having a certain data attribute, transmission of the memory data having the data attribute to the backup server 10 is started (S1223). .

  In S1224, the mobile phone 20 determines whether there is a reception response from the backup server 10 for the memory data for each data attribute transmitted in S1223 (S1224). When receiving a reception response for a certain data attribute (S1223: reception), the cellular phone 20 checks whether the data attribute is “public information” (S1225). Here, when the data attribute is “public information” (S1225: YES), the mobile phone 20 acquires the storage URL of “public information” attached to the reception response, and corresponds to the memory corresponding to the memory data management information 800. The data storage URL 814 is set (S1226). If a timeout has occurred in S1224 (S1224: timeout), the process ends.

  In S1227, the mobile phone 20 determines whether or not all memory data to be backed up has been transmitted. If all the memory data to be backed up has been transmitted (S1227: YES), the process proceeds to S1228. If there is untransmitted memory data (S1227: NO), the process proceeds to S1215.

  In S <b> 1228, the mobile phone 20 determines whether or not there is a backup end response from the backup server 10, and if the end response is received (S <b> 1228: YES), the transmission of the backup data 900 is ended.

  FIG. 13 is a flowchart for explaining processing of the backup server 10 in the backup processing shown in FIG. The backup server 10 transmits a backup start request to the mobile phone 20 according to a preset time and conditions (S1311), and waits for a reception response from the mobile phone 20 (S1312). When the reception response waiting state times out (S1312: timeout), the backup process ends (S1313).

  When the reception response is received (S1312: reception), the backup server 10 next enters a state of waiting for the backup data 900 transmitted from the mobile phone 20 (S1314). When the reception waiting state times out (S1314: timeout), the backup process ends (S1313). Note that the timeout time in S1314 may be set longer than the timeout time in S1314 in consideration of the preparation time of the backup data 900 on the mobile phone 20 side.

  When the backup data 900 is received (S1314: reception), the backup server 10 authenticates the received backup data 900 (S1315). This authentication is performed using authentication information attached to the backup data 900 (for example, a password, a digital certificate, a mobile phone number or a mobile phone manufacturing number). When the above authentication is successful (S1315: Authentication successful), the backup server 10 stores the backup data 900 as the saved data 1000 in the storage device 15. In S1316, the data attribute of the backup data 900 is determined. This determination is made using, for example, the data attribute 9312 of the data header 931 of the backup data 900 and the data attribute 93211 of the data information 9321.

  In S1316, if the data attribute is “terminal information” (S1316: terminal information), the process proceeds to S1317. If the data attribute is “secret information” (S1316: secret information), the process proceeds to S1318. If the data attribute is “public information” (S1316: public information), the process proceeds to S1319.

  In S 1317, the encrypted / unencrypted data 9322 included in the backup data 900 is stored as the stored storage data 1000 in the storage area for storing the “terminal information” memory data in the storage device 15. In this case, the memory data is stored in the storage device 15 in an encrypted state. In S 1318, the encrypted / unencrypted data 9322 included in the backup data 900 is stored as the stored storage data 1000 in the storage area for storing the “secret information” memory data in the storage device 15. In this case, the memory data is stored in the storage device 15 in an encrypted state. In S 1319, the encrypted / unencrypted data 9322 included in the backup data 900 is stored as saved data 1000 in a storage area for storing “public information” memory data in the storage device 15. In this case, the memory data is stored in the storage device 15 without being encrypted. In subsequent S1320, the backup server 10 checks whether the content is set in the unique information 93215 of the data information 9321 of the backup data 900 (S1320). When the contents are set (S1320: Yes), the backup server 10 accesses the contents corresponding to the contents of the unique information 93215 when the stored data 1000 corresponding to the backup data 900 is disclosed on the Internet 30. The contents of the unique information 93215 (that is, the contents of the public setting) are reflected so that the restriction or the like is performed (S1321). In S1320, if there is no information regarding the public setting (S1320: none), the process proceeds to S1322. In S1322, the backup server 10 sets the URL (save URL) corresponding to the storage area of the saved data 1000 stored in the storage device 15 in the response message transmitted to the mobile phone 20 in S1324 described later (S1322). ).

  In S1323, the backup server 10 determines whether or not all encrypted / unencrypted data 1033 has been received for each data attribute (S1323). This determination is made, for example, by comparing the data size of the received encrypted / unencrypted data 1033 with the contents of the data size 9316 of the data header 931.

  When all the encrypted / unencrypted data 1033 for a certain data attribute is received in S1323 (S1323: YES), the backup server 10 responds that the backup has been completed for the data attribute (hereinafter referred to as a response message). ) Is transmitted to the mobile phone 20 (S1324). In S1323, when it is not received (S1323: NO), the process proceeds to S1314.

In S1325, the backup server 10 determines whether or not all backup data 900 transmitted from the mobile phone 20 has been received (S1325). If all the backup data 900 has not been received (S1325: NO), the process proceeds to S1314. If all backup data 900 has been received, the process advances to step S1326.
In S 1326, the backup server 10 transmits a message indicating that reception of the backup data 900 has ended to the mobile phone 20 (hereinafter referred to as an end message).

  FIG. 14 is a flowchart for explaining a process for causing the mobile phone 20 to recover the memory data. Recovery of the memory data to the mobile phone 20 is performed via the service device 60, and a user who has lost the mobile phone 20 or the like can use the newly purchased mobile phone 20 or the mobile phone 20 returned from repair. Then, the memory data is restored using the service device 60.

  The user sets the mobile phone 20 in a state where communication with the service device 60 is possible, and performs a predetermined operation for starting download (transmission) to the service device 60. Accordingly, a memory data download request is transmitted from the service device 60 to the backup server 10 (S1411). The download request to be transmitted is accompanied by a user ID (for example, a telephone number) of the mobile phone 20 and authentication information (for example, a password, a digital certificate, an IP address of the service device 60, biometric authentication information).

  When receiving the download request (S1412), the backup server 10 authenticates the received download request (S1413). When the authentication fails (S1413: authentication failure), the backup server 10 notifies the service device 60 that the authentication has failed (S1414). When the authentication is successful (S1413: authentication success), the backup server 10 searches the storage device 15 for the stored data 1000 for the mobile phone 20 (S1415).

  If the saved data 1000 does not exist (S1415: none), the backup server 10 transmits a message indicating that the saved data cannot be downloaded to the mobile phone 20 (S1416). If the saved data 1000 exists (S1415: present), the backup server 10 transmits (downloads) the memory data stored in the data area 1012 of the corresponding saved data 1000 to the service device 60 (S1417).

  The memory data downloaded here is accompanied by the user ID 1011 of the saved data 1000, other information stored in the data area 1012, the contents of the reception date and time 1014, the contents of the saved URL 1015, the contents of the public setting 1016, and the like. If the data attribute of the memory data to be transmitted to the service device 60 is “terminal information” or “secret information”, the memory data is encrypted and transmitted. If the content is set in the public setting 1016 of the saved data 1000 retrieved in S1415, the backup server 10 sets the key information (for example, password) in which the memory data to be transmitted to the service device 60 is set as the content. Encrypt using. Thereby, the memory data having the data attribute “public information” can be safely downloaded to the service device 60.

  Next, the service device 60 transfers the memory data downloaded from the backup server 10 to the mobile phone 20 (S1418). In order to restore the memory data to the mobile phone 20, it is necessary to decrypt the memory data, but this decryption may be performed by the service device 60 or the mobile phone 20. In decryption, the user inputs key information necessary for decryption (for example, password and biometric authentication information). It is also assumed that the same memory data is duplicated in the downloaded memory data (for example, when there are a plurality of files having the same file name with different time stamps). The reception date and time (contents of the reception date and time 1014 of the stored data 1000) downloaded along with the data are compared to adopt the latest memory data.

  FIG. 15 shows memory data stored in the lost mobile phone 20, erased or encrypted so that the memory data stored in the mobile phone 20 is not misused by others when the mobile phone 20 is lost. It is a flowchart explaining the process at the time of conversion. This process is performed by the user using the service device 60.

  A user who loses the mobile phone 20 first performs a predetermined operation on the service device 60. In response to this operation, a request for erasing or encrypting memory data of the cellular phone 20 that has been lost or the like is transmitted from the service device 60 to the backup server 10 (hereinafter referred to as an erasure encryption request) (S1511). . In the erase encryption request, the user ID (for example, telephone number) of the lost mobile phone 20 input by the user, authentication information (password, digital certificate, IP address of the service device 60, etc.), and erase Also, an option for specifying which processing of encryption is performed is attached.

  When the backup server 10 receives the erasure encryption request from the service device 60 (S1512), the backup server 10 authenticates the authentication information sent along with the request. If this authentication fails (S1513: authentication failure), the backup server 10 notifies the service device 60 that the authentication has failed (S1514). On the other hand, if the authentication is successful (S1513: authentication success), the backup server 10 checks whether the storage data 1000 of the user ID sent along with the erasure encryption request is stored in the storage device 15. . As described above, erasure and encryption are performed after the backup server 10 confirms whether or not the memory data is stored in the storage device 15 in advance. Memory data can be recovered.

  When it is confirmed that the storage data 1000 is stored in the storage device 15 (S1515: present), the backup server 10 erases or encrypts the memory data to the mobile phone 20 that has transmitted the erase encryption request ( A request (hereinafter, referred to as an erasure / encryption execution request) is transmitted to determine which is to be performed depending on the option (S1516). Note that authentication information (for example, authentication information transmitted from the service device 60) is attached to the erasure encryption execution request.

  When the mobile phone 20 receives the erasure encryption execution request transmitted from the service device 60 (S1517), it authenticates the authentication information sent along with the erasure encryption execution request (S1518). When the authentication is successful (S1518: authentication success), the mobile phone 20 erases or encrypts the memory data stored in the memory 412 (S1519). In addition, after erasing or encrypting the memory data, the cellular phone 20 downloads the memory data together with the erasure or encryption in order to prevent a person who has obtained the cellular phone 20 from downloading the memory data again to restore the memory data. It is also possible to execute processing for prohibiting the above.

  By the way, description of the above embodiment is for making an understanding of this invention easy, and does not limit this invention. It goes without saying that the present invention can be changed and improved without departing from the gist thereof, and that the present invention includes equivalents thereof.

  For example, the present invention can be applied to backup of data stored in a memory of a portable communication device such as a PDA (Personal Digital Assistance) having a function of communicating through the Internet.

  Further, for example, for memory data in which the data attribute 815 is set to “public information”, data transfer from one mobile phone 20 to another mobile phone 20 (for example, transfer of image data) is performed in the following procedure. Can be. That is, instead of transmitting the memory data itself, the transfer source mobile phone 20 notifies the transfer destination mobile phone 20 of only the URL set in the save URL 814, and the transfer destination mobile phone 20 notifies the storage device 15. Access stored memory data. With such a mechanism, it is not necessary to transmit memory data from the mobile phone 20 to the backup server 10.

  Further, the communication between the mobile phone 20 and the backup server 10 and the communication between the service device 60 and the backup server 10 are performed using an encrypted communication protocol such as HTTPS (Hypertext Transfer Protocol Security). Data can be managed more safely.

It is a figure which shows schematic structure of the data management system 1 demonstrated as one Embodiment of this invention. It is a figure which shows the hardware constitutions of the backup server 10 demonstrated as one Embodiment of this invention. It is a figure explaining the software configuration of the backup server 10 demonstrated as one Embodiment of this invention. It is a figure which shows the hardware constitutions of the mobile telephone 20 demonstrated as one Embodiment of this invention. It is a figure which shows the software structure of the mobile telephone 20 demonstrated as one Embodiment of this invention. It is a figure which shows the hardware constitutions of the service apparatus 60 demonstrated as one Embodiment of this invention. It is a figure which shows the software structure of the service apparatus 60 demonstrated as one Embodiment of this invention. It is a figure which shows the structure of the memory data management information 800 demonstrated as one Embodiment of this invention. It is a figure which shows the structure of the backup data 900 demonstrated as one Embodiment of this invention. It is a figure which shows the structure of the data header 931 demonstrated as one Embodiment of this invention. It is a figure which shows the structure of the data body 932 demonstrated as one Embodiment of this invention. It is a figure which shows the structure of the data information 9321 demonstrated as one Embodiment of this invention. It is a figure which shows the structure of the preservation | save data 1000 demonstrated as one Embodiment of this invention. It is a message flow of the backup process demonstrated as one Embodiment of this invention. It is a flowchart explaining the process of the mobile telephone 20 in the backup process demonstrated as one Embodiment of this invention. It is a flowchart explaining the process of the backup server 10 in the backup process demonstrated as one Embodiment of this invention. It is a flowchart explaining the process for recovering the memory data demonstrated as one Embodiment of this invention. It is a flowchart explaining the process which erases or encrypts the memory data of the mobile telephone 20 demonstrated as one Embodiment of this invention.

Explanation of symbols

1 Data Management System 10 Backup Server 15 Storage Device 20 Mobile Phone 30 Internet 40 Mobile Phone Network 50 Gateway Device 60 Service Device

Claims (14)

A mobile communication device, a backup server that is communicably connected to the mobile communication device via a mobile phone network, a storage device that is connected to the backup server, and a backup server that is communicably connected via the Internet, A management method of data stored in a mobile communication device, performed in a system including a service device that is communicably connected to the mobile communication device,
The backup server receives data stored in the mobile communication device transmitted from the mobile communication device via the mobile phone network; and
The backup server storing the received data in the storage device;
The backup server receiving the data transmission request transmitted from the service device via the Internet;
The backup server transmitting the data stored in the storage device to the service device via the Internet;
The service device receiving the data;
The service device transmitting the received data to the portable communication device;
A method for managing data stored in a mobile communication device, comprising: A method for managing data stored in a mobile communication device according to claim 1,
The backup server receives the data in an encrypted state from the portable communication device, and stores the data in the storage device in an encrypted state. The backup server stores the data in the storage device. Data management method. A method for managing data stored in a mobile communication device according to claim 2,
The backup server appends information for identifying the data to the data received from the mobile phone and stored in the storage device. A method for managing data stored in a mobile communication device . A method for managing data stored in a mobile communication device according to claim 2,
The data received by the backup server from the mobile communication device and stored in the storage device is classified into a plurality of preset groups, and the data is encrypted for each group,
The said backup server receives the said data for every said attribute. The management method of the data memorize | stored in the portable communication apparatus characterized by the above-mentioned. A method for managing data stored in a mobile communication device according to claim 1,
The method for managing data stored in a mobile communication device, comprising: a step of transmitting a request for starting transmission of the data to the mobile communication device by the backup server. A method for managing data stored in a mobile communication device according to claim 1,
The backup server includes transmitting to the portable communication device information indicating a date and time when the portable communication device transmits the data to the backup server;
The method of managing data stored in a mobile communication device, wherein the transmission of the data from the mobile communication device to the backup server is performed at a date and time indicated by the information in the mobile communication device. A method for managing data stored in a mobile communication device according to claim 1,
The backup server receiving a request from the service device to erase or encrypt data stored in the mobile communication device;
The backup server determining whether the data stored in the portable communication device to be erased or encrypted is stored in the storage device;
When the backup server determines that the data is stored in the storage device, a process of transmitting an execution request for erasing or encrypting the data to the portable communication device;
A method for managing data stored in a mobile communication device, comprising: A method for managing data stored in a mobile communication device according to claim 1,
A method of managing data stored in a portable communication device, comprising: a step of the backup server publishing the data stored in the storage device to the Internet. A method for managing data stored in a mobile communication device according to claim 8,
The backup server includes a step of transmitting to the mobile communication device an address on the Internet assigned when the data stored in the storage device is disclosed to the Internet. Data management method. A method for managing data stored in a mobile communication device according to claim 8,
The backup server receiving from the portable communication device information related to access restrictions set in the data to be disclosed to the Internet;
The backup server performing access control on the data released to the Internet according to the information on the access restriction;
A method for managing data stored in a mobile communication device, comprising: A method for managing data stored in a mobile communication device according to claim 8,
The backup server includes a step of setting a storage area associated with the data stored in the storage device and writable by another device connected to the Internet. Data management method. A method for managing data stored in a mobile communication device according to claim 11,
The backup server operates in cooperation with a mail server operating on the Internet;
The backup server storing the email sent from the mail server in the writable storage area;
A method for managing data stored in a mobile communication device, comprising: A backup server that is communicably connected to the mobile communication device via a mobile phone network, a storage device that is connected to the backup server, and a communication device that is communicably connected to the backup server via the Internet and communicates with the mobile communication device A backup server in a system configured to include a service device that can be connected,
Receiving data stored in the mobile communication device transmitted from the mobile communication device via the mobile phone network;
Storing the received data in the storage device;
Receiving a transmission request for the data transmitted from the service device via the Internet;
A backup server that transmits the data stored in the storage device to the service device via the Internet. A mobile communication device, a backup server that is communicably connected to the mobile communication device via a mobile phone network, a storage device that is connected to the backup server, and a backup server that is communicably connected via the Internet, And a service device that is communicably connected to the mobile communication device, and the backup server is stored in the mobile communication device that is transmitted from the mobile communication device via the mobile phone network. Receiving data, storing the received data in the storage device, receiving a transmission request for the data transmitted from the service device via the Internet, and storing the data stored in the storage device; In the system for transmitting to the service device via the Internet, the service device,
Receives data stored in the storage device transmitted from the backup server via the Internet,
A service device that transmits the received data to the portable communication device.

Images