JP2004363652A - Memory backup system for mobile phone - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology for backing up data such as telephone directory data stored in an internal memory of a mobile phone. <P>SOLUTION: A memory backup apparatus 10 includes: an interface 15 for connection to the mobile phone 20, memories 12, 13, and a control section 11, receives information related to an access procedure to an internal memory 22 of the mobile phone 20 from the mobile phone 20, stores the information to the memory 13, and receives data in the internal memory 22 of the mobile phone into the memory 12 by using the received information related to the access procedure to the internal memory 22 of the mobile phone 20. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention generally relates to a technology for backing up data, and more particularly, to a technology for backing up data such as telephone directory data stored in an internal memory of a mobile phone.
[0002]
[Prior art]
Currently sold mobile phones have a so-called telephone directory (also called a memory dial) function. The telephone directory function generally stores a telephone directory, which is a combination of a name and a telephone number, in an internal memory of a mobile phone. In line with the trend toward higher functionality of mobile phones, the phone book function has also become more sophisticated, and it is possible to store multiple phone numbers, e-mail addresses, etc. in a single name, and to store several hundred entries. Up to these data can be stored.
[0003]
【task to solve】
By the way, if the telephone directory function of the mobile phone is used, all or a part of the data once stored in the mobile phone may be lost in the following cases, and it may be necessary to input the data again.
[0004]
(1) In case of accident such as theft or breakage of mobile phone
(2) When changing a mobile phone to a new model
In order to save the trouble of re-entering data, several methods of backing up the internal memory of the mobile phone have been provided.
[0005]
It is possible to save data on a hard disk or the like of a personal computer using backup software for a personal computer that can save data of a mobile phone. As a backup device dedicated to a mobile phone, a portable data backup device in which a mobile phone connection plug and a storage device are integrated is commercially available.
[0006]
However, various types of mobile phones are provided by various telecommunications carriers, and the access procedure to the internal memory (writing information to the internal memory, reading information from the internal memory, etc.) The communication procedure is the same hereinafter.), And the data format of the telephone directory and the like stored in the internal memory is different. Even within the same company, there are differences between manufacturers and models. For example, even with a mobile phone of the same manufacturer, the successor model may have a different access procedure to the internal memory than the previous model, or may have more input items such as a telephone directory.
[0007]
Therefore, in order to reliably back up the internal data (eg, telephone directory data) of various mobile phones, it is necessary to support the internal memory access procedures and data formats of all models.
[0008]
The backup software for personal computers can handle a variety of models by preparing information on the internal memory access procedures and data formats of all existing models in advance, and can also access the internal memory access procedures and data of new models. Information on the format can also be downloaded via the Internet. However, personal computers are generally expensive and hard to use for those unfamiliar with them. Also, personal computers are inconvenient to carry.
[0009]
Further, in the conventional backup device for exclusive use of a mobile phone, it is difficult to store in advance information on the access procedure and the data format of the internal memory of all models due to the memory capacity. Also, since it is not possible to introduce a read / write procedure and data format for data in the internal memory of a new model, it is not known whether or not the telephone directory data of an old mobile phone can be reliably transferred to a new mobile phone when a mobile phone is replaced.
[0010]
It is also conceivable to store phonebook data and the like in a data backup server via a network by using a program (i-appli (trademark) of NTT DOCOMO, Inc., NTT DOCOMO) operating on a mobile phone. . However, for the protection of personal information, mobile phones are designed so that programs running on the mobile phone cannot access (read and write) the phonebook data stored in the internal memory. Therefore, it is not possible to back up telephone directory data via a network by using a mobile phone alone.
[0011]
Accordingly, it is an object of the present invention to provide a technology capable of easily and easily backing up data in an internal memory including telephone directory data of various models of mobile phones including a new model anytime and anywhere.
[0012]
[Means for Solving the Problems]
An apparatus of the present invention corresponding to the above-mentioned problem includes a data communication means via a mobile phone, and a memory, wherein the data communication means downloads a data acquisition procedure from an internal memory of the mobile phone to the memory, The method is characterized in that data in an internal memory of a mobile phone is obtained by using an obtaining procedure.
[0013]
A data backup device of the present invention corresponding to the above problem includes an interface for connecting to a mobile phone, a memory, and a control device, and receives information on an access procedure to an internal memory of the mobile phone via the mobile phone. And storing the data in the internal memory of the mobile phone in the memory using the received information on the access procedure to the internal memory of the mobile phone.
[0014]
In the backup device of the present invention, only necessary access procedures are stored in the memory, so that the mounted memory capacity can be reduced.
[0015]
In this data backup device, the information on the procedure for accessing the internal memory of the mobile phone may include a procedure for reading data from the internal memory of the mobile phone, and further include a procedure for writing data to the internal memory of the mobile phone. May be included. The data in the internal memory of the mobile phone can be telephone directory data.
[0016]
The data backup device may be housed in a single housing, and the interface may be configured to be exposed from a part of the housing. In addition, all or a part of the memory of the data backup device can be configured to be detachable. This memory may be a flash memory.
[0017]
The server apparatus according to the present invention includes: a first database unit for storing a model name of a mobile phone and an access procedure to an internal memory of the mobile phone in association with each other; a model name transmitted from the mobile phone; Second database means for storing information to be specified in association with the information; and search means for receiving the information for specifying the mobile phone, searching the first and second database means, and specifying the corresponding access procedure. It is characterized by having. A telephone number can be used as information for specifying a mobile phone.
[0018]
A program of the present invention corresponding to the above-described problem causes a computer to realize a data communication function via a mobile phone, download an access procedure to an internal memory of the mobile phone using the data communication function, and execute the access procedure. The data of the internal memory of the mobile phone is acquired by using the mobile phone.
[0019]
According to another program of the present invention corresponding to the above-mentioned problem, a first database means for storing a computer in association with a model name of a mobile phone and an access procedure to an internal memory of the mobile phone, and a model transmitted from the mobile phone Second database means for storing a name and information for identifying the mobile phone in association with each other; and receiving information for identifying the mobile phone, searching the first and second database means for corresponding access procedures. It is characterized by functioning as a search means for specifying.
[0020]
The above program can be recorded on a computer-readable recording medium.
[0021]
BEST MODE FOR CARRYING OUT THE INVENTION
An embodiment of the present invention will be described with reference to the accompanying drawings. For simplification of the drawings and description, illustration and description of elements, functions, structures, programs, and the like that are not so important or obvious in understanding the present invention will be omitted.
[0022]
<Overall system>
FIG. 1 is a block diagram of an entire system according to an embodiment of the present invention. The system includes a telephone directory data backup device 10, a mobile phone 20, and a mobile phone business that performs wireless communication with the mobile phone 20. And a server 40, and an Internet service provider (hereinafter, referred to as an ISP) that connects the base station / exchange station 30 and the server 40 of the mobile phone carrier. The ISP is connected to the base station / switching station 30 of the mobile phone operator via a dedicated line or a packet switching network, and is connected to the server 40 by the so-called Internet. However, the ISP is not an essential component of this system, and it is also possible to directly connect the base station / switching station 30 and the server 40.
[0023]
In this specification, a mobile phone means a mobile phone of various types having a data communication function (PDC, GSM, IMT-2000, etc.), a simple mobile phone (PHS), a mobile phone, a marine phone, a satellite mobile phone. Etc. is a concept that includes all mobile telephones.
[0024]
<Mobile phone and backup device>
FIG. 2 is a functional block diagram of the backup device 10 and the mobile phone 20 of FIG.
The backup device 10 includes a control unit 11 that performs overall control by a CPU, a basic program, and the like (not shown), a backup memory 12 that stores telephone directory data of a mobile phone 20, and an access to a telephone directory memory of the mobile phone 20 described later. An access procedure memory 13 for storing procedures (including data format and program format), an operation unit 14 including buttons and the like for the user to instruct the operation of the backup device 10, and an interface 15 for connecting to the mobile phone 20 It is composed of
[0025]
The backup memory 12 and the access procedure memory 13 may be rewritable memories whose contents are retained for a certain period. Examples include a nonvolatile ROM such as an EEPROM and a flash memory, a nonvolatile RAM such as a ferroelectric memory (FeRAM), and a battery backup SRAM. Further, the backup memory 12 and the access procedure memory 13 can be memory modules that can be removed from the backup device 10, for example, compact flash (trademark) memory. The backup memory 12 and the access procedure memory 13 may be separate memory devices, or may be configured as different storage areas inside a single memory device.
[0026]
The mobile phone 20 includes a control unit 21 that performs overall control by a CPU and a basic program (not shown), a memory 22, a data communication unit 23 that enables data communication between the base station and the exchange 30, (Www: World Wide Web) Communication between a Web browser 24 that decodes page information described in the HTML language and displays a screen on the display device 27, and a base station / switching station 30 It comprises a wireless unit 25 that enables wireless communication, an interface 26 for connecting an external device (also called a downstream device), a display device 27 such as an LCD, and an input / output device 28. The input / output device 28 includes a speaker, a microphone, and a key switch generally used in a mobile phone.
[0027]
<Interfaces 15, 26>
The interface 26 of the mobile phone 20 does not refer to a connection terminal, a plug, or the like specially designed for implementing the present invention, but an interface for connecting an external device (subsequent device) included in a commercially available mobile phone. It is. The interface 15 of the backup device 10 includes a connection terminal configured to be electrically connectable to the interface 26 of the mobile phone 20. Examples of such connection terminals include a master plug for a PDC type mobile phone, the MQ138 series of Hirose Electric Co., Ltd., and the DH01 series of Japan Aviation Electronics Industry Co., Ltd.
[0028]
<Memory 22>
The memory 22 includes an identification information memory 22-1 that stores a telephone number and an individual identification number of a mobile phone, and a telephone directory memory 22-2 that stores telephone directory data. The telephone number is generally written into the identification information memory 22-1 when the mobile phone 20 is sold by the mobile phone operator or its dealer. The individual identification number is a number that is written by the manufacturer of the mobile phone 20 before shipment from the factory and is unique to the mobile phone 20 and does not overlap with other mobile phones. Normally, the user of the mobile phone 20 cannot change the contents of the identification information memory 22-1.
[0029]
The memory 22 is a nonvolatile memory. The identification information memory 22-1 may be supplied as a removable IC memory card (UIM: User Identity Module) separately from the mobile phone 20. Further, the telephone directory memory 22-2 may be supplied as a removable general-purpose IC memory card (miniSD card, memory stick, or the like).
[0030]
The phonebook memory 22-2 stores an authentication password required to access the phonebook data. The structure of the telephone directory data will be described later.
[0031]
<Data communication unit 23>
The data communication unit 23 provides an external device (including the backup device 10) connected to the interface 26 with a data communication function via the mobile phone 20. Data communication via the mobile phone 20 includes a circuit switching system and a packet switching system, which are well known in the art. The circuit switching system is a system that is continuously connected to a specific communication partner like a voice call, and occupies the line all the time even when data is not exchanged. On the other hand, the packet switching system is a system in which several people jointly occupy a line and exchange data as needed.
[0032]
<Web browser 24>
The Web browser 24 is a program for accessing a Web server, which is well known in the art. As a web browser for a mobile phone, a web browser compatible with NTT DOCOMO's i-mode (trademark) is known.
[0033]
<Server 40>
FIG. 3 is a functional block diagram of the server 40 of FIG. The server 40 includes a control unit 41 that controls each unit using a CPU, a basic program, and the like (not shown), a model-specific information database (hereinafter, referred to as a model-specific information DB) 42 that stores model-specific information of a mobile phone, and a mobile phone. A user management database (hereinafter, referred to as a user management DB) 43 for managing information on the telephone 20 and a telephone directory data different for each model of the mobile phone 20 in a format corresponding to the model or in a standard format. It is composed of a telephone directory conversion unit 44 for conversion and a network interface 45 for enabling communication via the Internet. The server 40 can be constructed by a CGI program or the like that operates on a Web server.
[0034]
<Model-specific information DB 42>
FIG. 4 shows the data format of the model-specific information DB 42. The model-specific information DB 42 is configured from a model name list of the mobile phone 20. The list cell of each model name is composed of information (including a data format and a program format) on a data access procedure to the telephone directory memory 22-2 of the mobile phone 20, and information on a data format of the telephone directory.
[0035]
<User management DB 43>
FIG. 5 shows a data format of the user management DB 43. The user management DB 43 includes a list of users. Each user's list cell includes a telephone number, a password, a model name, and telephone directory data. The telephone number is a telephone number given to the mobile phone 20 by a mobile phone operator, for example, 090-1111-2222. The password is an authentication number set by the user to access the telephone directory data of the mobile phone 20, for example, a four-digit number. The model names are, for example, N211i, N504iS, P211iS, and the like sold by NTT DoCoMo. Each user's list cell can also include the individual identification number of the mobile phone 20.
[0036]
The telephone directory data has different data formats depending on the model of the mobile phone 20. FIG. 6 shows one format of telephone directory data. The telephone directory of FIG. 6 has list cells of the number of groups (here, 2), group numbers (1, 2) and group names (company, friend), number of memories (200), and memory numbers (1-200). The list cell of each memory number includes a name, a telephone number, an E-mail address, and a group number.
[0037]
<Phonebook conversion unit 44>
The telephone directory conversion unit 44 has a function of converting the data format of the telephone directory data stored in the user management DB 43. The phonebook conversion unit 44 specifies which model the phonebook data to be converted is based on the model name stored in the user management DB 43, and converts the data format of the phonebook specific to the mobile phone into another model. The data is converted into a data format specific to the mobile phone, or converted into a standard data format, for example, a CVS data format.
[0038]
<Operation>
Next, the operation of the system of the above embodiment will be described with reference to FIG.
[0039]
<Register mobile phone information in server 40>
First, at the start of use of the system or when the model of the mobile phone is changed, the user registers information on the mobile phone 20 in the server or changes registered information.
[0040]
FIG. 7 is a sequence diagram showing a flow of processing for registering information of the mobile phone 20 in the server 40. First, the Web browser 24 of the mobile phone 20 is activated. A URL (Universal Resource Locator) is input to the Web browser 24, and a registration page of the mobile phone information of the server 40 is called. At this time, the model name of the mobile phone 20 is notified to the server 40. Information about the model name is included in an environment variable HTTP_USER_AGENT transmitted from the Web browser 24 to the server 40. Depending on the mobile phone, the environment variable may be transmitted including the individual identification number.
[0041]
Upon receiving the connection request from the Web browser 24, the server 40 sends out a user registration page.
[0042]
The user inputs a user name, a telephone number, and a password on this registration page. On the registration page, the user may confirm whether the model name received by the server 40 is correct. If the server 40 cannot correctly recognize the model name, or if information on the model name cannot be automatically received from the mobile phone 20, a model name list is presented and the user is allowed to select a model name from the list. Is also good. The input information is sent to the server 40. However, the input of the user name can be omitted.
[0043]
The server 40 adds the received information to the list in the user management DB 43 and notifies the mobile phone 20 that the registration has been completed. The registration processing of the mobile phone information by the server 40 can be realized by a CGI program or the like that operates in cooperation with a Web server program (not shown).
[0044]
<Download PIN, model-specific information, etc. from server 40 to backup device 10>
Next, the backup device 10 downloads the access procedure and the password from the server 40. FIG. 8 is a sequence diagram showing the flow of this download.
[0045]
The user connects the backup device 10 to the mobile phone 20. The connection is made by electrically connecting the interfaces 15 and 26.
[0046]
The user instructs the operation unit 14 of the backup device 10 to download the access procedure. The backup device 10 connects to the server 40 via the data communication unit 23 of the mobile phone 20. The connection to the server 40 is made using a well-known dial-up procedure and the TCP / IP protocol when the circuit switching method is used. When the packet switching method is used, the packet switching method is performed using the TCP / IP protocol or another protocol provided by the mobile phone carrier.
[0047]
When the server 40 gives the connection permission to the connection request from the mobile phone 20, the backup device 10 sends the telephone number of the mobile phone 20 acquired from the mobile phone 20 to the server 40. The server 40 that has received the telephone number searches the user management DB 43 and specifies the model name.
[0048]
The server 40 instructs the backup apparatus 10 to access information (hereinafter simply referred to as an access procedure) of the password stored in the user management DB 43 and the model-specific information corresponding to the model name specified from the model-specific information DB 42. ). When an individual identification number is stored in the user management DB 43, the individual identification number can be transmitted at the same time. The backup device 10 stores the received personal identification number and the access procedure in the access procedure memory 13. When another password and access procedure are already stored in the access procedure memory 13, the new password and access procedure are overwritten. When the backup device 10 receives the individual identification number, it can store it in the access procedure memory 13.
[0049]
<Backup of phonebook data>
Next, backup of telephone directory data stored in the telephone directory memory 22-2 of the mobile phone 20 using the backup device 10 will be described. The backup device 10 backs up the phone book data in the phone book memory 22-2 of the mobile phone 20 according to the access procedure stored in the access procedure memory 13.
[0050]
FIG. 9 is a sequence diagram showing the flow of this backup.
[0051]
The backup device 10 is connected to the mobile phone 20. An instruction is issued from the operation unit 14 of the backup device 10 to back up telephone directory data. The backup device 10 requests connection to the mobile phone 20 and performs predetermined initial settings. The mobile phone 20 sets a state in which a command from the backup device 10 can be accepted, and notifies the backup device 10 that the command can be accepted. The backup device 10 requests reading of the telephone directory data. Next, authentication processing using a password is performed between the backup device 10 and the mobile phone 20. If the authentication is successful, the mobile phone 20 sends the phonebook data in the phonebook memory 22-2 to the mobile phone 20. The backup device 10 stores the received telephone directory data in the backup memory 12. When the transmission of the telephone directory data is completed, the mobile phone 20 notifies the backup device 10 to that effect.
[0052]
The procedure for reading the telephone directory data described above differs depending on the model of the mobile phone 20, and all or a part of the backup processing is performed according to the access procedure stored in the access procedure memory 13.
[0053]
<Upload of telephone directory data to server 40>
If necessary, the telephone directory data backed up in the backup device 10 can be uploaded to the server 40. As a result, a double backup can be obtained, or the data format of the telephone directory data can be converted using the telephone directory converter 44 described above.
[0054]
FIG. 10 is a sequence diagram showing a flow of processing for uploading telephone directory data in the backup memory 12 to the server 40.
[0055]
The user connects the backup device 10 to the mobile phone 20 and instructs the operation unit 14 of the backup device 10 to upload telephone directory data. The backup device 10 connects to the server 40 via the data communication unit 23 of the mobile phone 20. The method for connecting to the server 40 is as described above.
[0056]
The backup device 10 transmits a telephone number and makes a connection request to the server 40. The server 40 searches whether or not the received telephone number is registered in the user management DB 43, and if registered, permits the connection. As a condition for permitting the connection, additionally or alternatively, a password and / or an individual identification number stored in the access procedure memory 13 may be used. When the connection is permitted, the fact is notified to the backup device 10. Subsequently, the backup device 10 requests upload of telephone directory data. The backup device 10 having received the permission from the server 40 sends the telephone directory data stored in the backup memory 12 to the server 40. The server 40 stores the received telephone directory data in a corresponding list cell of the user management DB 43. When the transmission of the telephone directory data is completed, the backup device 10 notifies the server 40 of that fact.
[0057]
<Restore (repair) processing>
Next, restoration (restoration) of telephone directory data in the telephone directory memory 22-2 of the mobile phone 20 using the backup device 10 will be described. The backup device 10 restores the telephone directory data in the telephone directory memory 22-2 of the mobile phone 20 according to the access procedure stored in the access procedure memory 13. The restoration process is partially different between the case of performing the same type of mobile phone and the case of performing a different type of mobile phone. Therefore, the following case will be described separately.
[0058]
<For the same model>
FIG. 11 is a sequence diagram showing a flow of restoration to the same model.
[0059]
The backup device 10 is connected to the mobile phone 20. An instruction to restore the telephone directory data is issued from the operation unit 14 of the backup device 10. The backup device 10 requests connection to the mobile phone 20 and performs initial settings. The mobile phone 20 sets a state in which a command from the backup device 10 can be accepted, and notifies the backup device 10 that the command can be accepted. The backup device 10 requests writing of telephone directory data. Next, authentication processing using a password is performed between the backup device 10 and the mobile phone 20. If the authentication is successful, the backup device 10 sends the telephone directory data in the backup memory 12 to the mobile phone 20. The mobile phone 20 stores the received telephone directory data in the telephone directory memory 22-2. When the transmission of the telephone directory data is completed, the backup device 10 notifies the mobile phone 20 of the transmission.
[0060]
The procedure for restoring the telephone directory data described above differs depending on the model of the mobile phone 20, and all or a part of the restoration processing is performed according to the access procedure stored in the access procedure memory 13.
[0061]
<When there is a model change>
<< Download model-specific information >>
When restoring the telephone directory data to another type of mobile phone 20 due to replacement or the like, the access procedure corresponding to the type is downloaded from the server 40. The download of the new access procedure is performed in accordance with the above-described mobile phone information registration processing (FIG. 7), the access procedure and the password download processing (FIG. 8).
[0062]
When the model is changed, the data format of the telephone directory data is also generally changed. Therefore, if the telephone directory data stored in the backup memory 12 is directly restored to the new mobile phone 20, there is a high possibility that a problem will occur. . Therefore, it is desirable to use the above-described telephone directory converter 44 to download (to be described later) the telephone directory data converted into the data format of the new model by the server 40 to the backup device 10 and then perform restoration. The process of restoring the telephone directory data converted to the data format of the new model to the mobile phone 20 of the new model is basically the same as the above-described restoration process to the same model (FIG. 11).
[0063]
<Download phonebook data from server 40>
The telephone directory data uploaded to the server 40 can be downloaded to the backup device 10 as needed. Accordingly, it is possible to cope with a case where the telephone directory data in the backup memory 12 is lost, and to obtain the telephone directory data converted into the data format of the telephone directory data of the new model when changing the model of the mobile phone 20. be able to.
[0064]
FIG. 12 is a sequence diagram illustrating a flow of a process of downloading the telephone directory data uploaded to the server 40 to the backup memory 12.
[0065]
The user connects the backup device 10 to the mobile phone 20 and instructs the operation unit 14 of the backup device 10 to download telephone directory data. The backup device 10 connects to the server 40 via the data communication unit 23 of the mobile phone 20. The method for connecting to the server 40 is as described above.
[0066]
The backup device 10 transmits the telephone number of the mobile phone 20 and makes a connection request to the server 40. The server 40 determines whether the connection is possible using the received telephone number. The determination may additionally or alternatively use a personal identification number and / or an individual identification number stored in the access procedure memory 13. When permitting the connection, the server 40 notifies the backup device 10 to that effect. Subsequently, the backup device 10 requests the server 40 to download the telephone directory data. In response to the request, the server 40 sends out the telephone directory data from the corresponding list cell of the user management DB 43. The backup device 10 stores the received telephone directory data in the backup memory 12. When the transmission of the telephone directory data is completed, the server 40 notifies the backup device 10 to that effect.
[0067]
Next, conversion processing of telephone directory data using the telephone directory converter 44 will be described. The conversion processing of the telephone directory data is automatically performed according to an instruction from the user or at the time of the change registration processing of the model. The telephone directory conversion unit 44 of the server 40 converts the telephone directory data format (hereinafter referred to as an old format) stored in the user management DB 43 in association with the model name into the telephone directory data corresponding to the new model name. To the format. The telephone directory conversion unit 44 searches the model-specific information DB 42 to specify a data format (hereinafter, referred to as a new format) corresponding to the new model name. Subsequently, the telephone directory converter 44 specifies a data item common to the old format and the new format. The telephone directory conversion section 44 creates telephone directory data in a new format, extracts the data of the common data items from the telephone directory data in the old format, and transfers the data to the telephone directory data in the new format. By repeating this process for the number of phonebook entries, old phonebook data can be converted to a new format.
[0068]
The converted telephone directory data can be overwritten on the old-format telephone directory data in the user management DB 43, or can be additionally stored after the old-format telephone directory data.
[0069]
The various functional blocks and processes of the backup device 10 and the server 40 in the above embodiment may be realized and executed by a processor reading and executing the program. The program to be executed may be a combination of a basic program (including an operating system) stored in the backup device 10 and the server 40 in advance and an application program that is assumed to be executed on the basic program. .
[0070]
As described above, the present invention has been described based on the specific embodiments, but the present invention is not limited to the above embodiments.
[0071]
For example, the backup target data in the internal memory of the mobile phone is not limited to the phonebook data. Other data to be backed up can be any other data such as various function setting information, incoming number information (incoming history), outgoing number information (outgoing history), image data (including animation data), and the like. The function setting information is information related to the function of the mobile phone set by the user, and includes, for example, a ringtone (melody), a ringtone volume, a call volume, an answering machine setting, and the like.
[0072]
The interfaces of the mobile phone and the backup device are not limited to those using connection terminals, and may be a non-contact type interface, for example, an infrared transceiver.
[0073]
【effect】
According to the present invention, it is possible to easily back up the internal memory of various types of mobile phones including a new model anytime, anywhere.
[Brief description of the drawings]
FIG. 1 is a block diagram of an entire system according to an embodiment of the present invention.
FIG. 2 is a functional block diagram of the backup device 10 and the mobile phone 20 of FIG.
FIG. 3 is a functional block diagram of a server 40 in FIG. 1;
FIG. 4 is a diagram showing a data format of a model-specific information DB;
FIG. 5 is a diagram showing a data format of a user management DB 43.
FIG. 6 is a view showing an example of a data format of telephone directory data.
FIG. 7 is a sequence diagram showing a flow of processing for registering user information in the server 40.
FIG. 8 is a sequence diagram showing a flow of an access procedure and a download of a personal identification number.
FIG. 9 is a sequence diagram showing a flow of processing for backing up telephone directory data.
FIG. 10 is a sequence diagram showing a flow of processing for uploading telephone directory data.
FIG. 11 is a sequence diagram showing a flow of processing for restoring telephone directory data.
FIG. 12 is a sequence diagram showing a flow of processing for downloading telephone directory data.
[Explanation of symbols]
10. Backup device
11 Control part
12 Backup memory
13 Access procedure memory
14 Operation unit
15 Interface
20 mobile phones
21 Control unit
22 memory
23 Data Communication Department
24 Web browser
25 Radio section
26 Interface
27 Display device
28 I / O devices
40 servers
41 Control unit
42 Model-specific information DB
43 User Management DB
44 Phonebook Conversion Department
45 Network Interface

Claims (14)

A data communication unit via a mobile phone; and a memory, wherein the data communication unit downloads a data acquisition procedure from an internal memory of the mobile phone to the memory, and uses the data acquisition procedure to store data in an internal memory of the mobile phone. A device that acquires data. An interface for connecting to a mobile phone,
Memory and
With a control device,
The information on the access procedure to the internal memory of the mobile phone is received via the mobile phone and stored in the memory, and the received information on the access procedure to the internal memory of the mobile phone is stored in the internal memory of the mobile phone using the received information. A data backup device for receiving data in the memory. 3. The data backup device according to claim 2, wherein the information on the procedure for accessing the internal memory of the mobile phone includes a procedure for reading data from the internal memory of the mobile phone. 4. The data backup device according to claim 3, wherein the information on the procedure for accessing the internal memory of the mobile phone includes a procedure for writing data to the internal memory of the mobile phone. 3. The data backup device according to claim 2, wherein the data in the internal memory of the mobile phone is telephone directory data. The data backup device according to claim 2, wherein the data backup device is housed in a single housing, and the interface is configured to be exposed from a part of the housing. 3. The data backup device according to claim 2, wherein all or a part of the memory is configured to be detachable. The data backup device according to claim 7, wherein the memory is a flash memory. First database means for storing the model name of the mobile phone and the access procedure to the internal memory of the mobile phone in association with each other;
Second database means for storing a model name transmitted from the mobile phone and information for specifying the mobile phone in association with each other;
A server device comprising: a search unit that receives information specifying a mobile phone, searches the first and second database units, and specifies a corresponding access procedure. The server device according to claim 9, wherein the information specifying the mobile phone is a telephone number. A computer realizes a data communication function via a mobile phone, downloads an access procedure to an internal memory of the mobile phone using the data communication function, and obtains data of the internal memory of the mobile phone using the access procedure Program to let you. First database means for storing a computer in association with a model name of a mobile phone and an access procedure to an internal memory of the mobile phone;
Second database means for storing a model name transmitted from the mobile phone and information for specifying the mobile phone in association with each other;
A program for receiving information for specifying a mobile phone, searching the first and second database means, and functioning as search means for specifying a corresponding access procedure. A computer-readable recording medium on which the program according to claim 11 is recorded. A computer-readable recording medium on which the program according to claim 12 is recorded.

Images