JP2003309669A - User data backup method of portable apparatus, its system, server and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To make it possible for a portable apparatus using user data whose format is different from user data preserved in a server to use the user data preserved in the server, in a backup system wherein the user data like telephone directory data or the like of a portable telephone set are preserved in the server on a network. <P>SOLUTION: A user of the portable telephone set 10 registers the user data like the telephone directory data or the like in a storage server 20. When the user purchased a new portable telephone set whose user data format is different from the telephone set 10, the user requests format conversion. In response to the request, a format conversion server 50 converts the format of the user data registered in the storage server 20 to a format conformable to the format of the new portable telephone set. The user performs down load of the user data after format conversion, to the new portable telephone set. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a user data backup technique for storing user data stored in a mobile device such as a mobile phone in a server on a network, and more particularly to user data stored in the server. The present invention relates to a user data backup technique for a mobile device that can use user data stored in a server even if the mobile device uses user data having different formats.

[0002]

2. Description of the Related Art Recent mobile phones are capable of registering various user data. User data includes telephone directory data, incoming melody data, standby screen image data, electronic mail data, and the like. User data is important to the user. Therefore, various techniques for backing up user data have been conventionally proposed.

For example, in Japanese Utility Model Registration No. 3057080, a mobile phone and a telephone directory data backup device are connected by a communication cable, and the telephone directory data stored in the mobile phone is stored in a data memory of the telephone directory data backup device. The technology to save is described. However, this conventional technique has a problem that the user has to purchase a telephone directory data backup device and a connection cable.

In order to solve such a problem, a backup server is arranged on the network, the phonebook data of the mobile phone is stored in this backup server, and the backup server stores the phonebook in the mobile phone as needed. Techniques for downloading data have been proposed (for example, Japanese Patent Laid-Open Nos. 2001-298522 and 2001-3).
06518).

[0005]

According to this conventional technique, it is not necessary for the user to purchase a telephone directory data backup device or a connection cable, but there are the following problems. That is, there is a problem that the user data registered in the backup server cannot be used in the mobile device that uses the user data in the format different from the user data stored in the backup server. For example, when the user purchases a new mobile phone, if the format of the user data of the newly purchased mobile phone is the same as the format of the user data saved in the backup server, it is saved in the backup server. Download user data,
You can register your new mobile phone. However, if the user data format is different,
The user data stored in the backup server cannot be used, and the user has to manually input the phone book data and the like.

Therefore, an object of the present invention is to make it possible to use user data stored in a server even in a portable device that uses user data having a format different from that of the user data stored in the server.

[0007]

In order to achieve the above object, a user equipment backup system for a portable device according to the present invention has a means for transmitting the user data to a server via a network. , Means for saving user data sent from the mobile device, means for converting the format of the saved user data into a format of a mobile device different from the mobile device, and format for the other mobile device And means for transmitting the converted user data.

Further, in the user data backup system for portable equipment of the present invention, in order to allow the server operator to make a profit, the server charges a fee for format conversion, a fee for saving user data, or a user fee. Means for charging the user of the mobile device for a fee associated with the transmission of data.

Further, in the user data backup system for a portable device of the present invention, the server is configured so that the user data (eg, telephone directory data) registered in the server can be processed (eg, converted into text). It is provided with means for processing the stored user data according to an instruction from the user of the portable device.

[0010]

Since the server has the means for converting the format of the user data, the user data stored in the server can be used even in the portable device using the user data whose format is different from the user data stored in the server. become able to. Further, since the server has means for charging the user of the mobile device with various fees such as a fee associated with the format conversion, the operator of the server can make a profit. Further, since the server is provided with a means for processing the registered data, the user can obtain, for example, the text or the like corresponding to the registered telephone directory data.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, embodiments of the present invention will be described in detail with reference to the drawings.

[0012]

1 is a block diagram of a first embodiment of a user data backup system for a mobile device according to the present invention, which is a mobile phone 10 and a storage server 20.
An authentication server 30, a billing server 40, a format conversion server 50, and a network 100 such as the Internet for connecting them to each other.

The mobile phone 10 has a function of storing telephone directory data including a telephone number and name, incoming melody data, standby screen image data, user data such as electronic mail. Furthermore, the mobile phone 10 has the authentication server 3
A function of making a system use contract with 0, a function of transmitting a user authentication request to the authentication server 30, and a function of transmitting user data stored in the mobile phone 10 to the storage server 20 and storing the user data. It also has a function of downloading user data stored in the storage server 20, and the like.

The storage server 20 is a network 1
00 is a storage device connected to the mobile phone 10
And a function of notifying the authentication server 30 of the position information of the writing area of the user data allocated to the mobile phone 10 when the system use contract is signed between the authentication server 30 and
The function of saving user data sent from the mobile phone 10 and the stored user data
And a function of transmitting the stored user data to the format conversion server 50.

The authentication server 30 has a function of concluding a system use contract with the mobile phone 10 and the storage server 2.
It has a function of transmitting the position information of the writing area assigned to the mobile phone 10 sent from the mobile phone 10 to the mobile phone 10 and a function of performing an authentication process in response to a user authentication request from the mobile phone 10.

The format conversion server 50 has a function of converting the format of user data registered in the storage server 20. The billing server 40 has a function of performing payment processing. Each server 20, 3 described above
0, 40, and 50 are realized by, for example, a computer that operates under program control.

[0017]

[Description of Operation of the Embodiment] Next, the operation of the present embodiment will be described in detail with reference to FIGS.

First, the operation at the time of concluding the system use contract will be described.

When the user of the mobile phone 10 desires to use the user data backup system for a mobile device according to the present invention, he / she accesses the authentication server 30 (FIG. 2, step A1). As a result, the authentication server 30
Send contract screen information to mobile phone 10 (step A
2).

The mobile phone 10 displays the contract screen according to the contract screen information (step A3). When the contract screen is displayed, the user confirms the contract content, inputs contract information using the input field of the contract screen, and sends it to the authentication server 30 (step A4). Here, the contract information includes, for example, the user's name, address, credit member number used for payment, and the like.

When the contract information is sent from the mobile phone 10, the authentication server 30 sends a request to secure a writing area to be allocated to the mobile phone 10 to the storage server 20 (step A5). As a result, the storage server 20 secures the write area to be allocated to the mobile phone 10, and the position information indicating the position is stored in the authentication server 3
The value is returned to 0 (step A6).

The authentication server 30 is the storage server 20.
When the position information is sent from, the contract conclusion processing is performed (step A7). In this contract conclusion processing, the authentication server 30 determines the user ID and password to be given to the user of the mobile phone 10, and performs a process of transmitting a contract conclusion message including this user ID and password to the mobile phone 10 and writing the message. A process of associating the position information of the area with the user ID and saving them is performed. Furthermore,
The authentication server 30 performs a process of transmitting user information (including name, address, user ID, credit member number) of the mobile phone 10 to the billing server 40.

The mobile phone 10 displays the contract conclusion message sent from the authentication server 30 and informs the user of the user ID and password (step A8).

The billing server 40 is the authentication server 30.
Register the user information sent from (Step A
9).

Next, a process for registering the user data of the mobile phone 10 in the storage server 20 will be described.

When registering user data in the storage server 20, the user uses the mobile phone 10 to send a user authentication request including a user ID and a password to the authentication server 30 (FIG. 3, step B1).

The authentication server 30 performs the authentication process, and if the authentication is OK, it is necessary to display the request selection screen data for displaying the request selection screen, and display the request selection screen data in accordance with the operation performed on the request selection screen by the user. The screen data of various screens and the position information of the writing area stored in association with the user ID of the mobile phone 10 in step A7 are transmitted to the mobile phone 10, and an error notification is given in the case of authentication NG (step B2). ).

The mobile phone 10 displays the request selection screen as shown in FIG. 4 according to the request selection screen data sent from the authentication server 30. The request selection screen is a screen for selecting the type of request to be transmitted, and is provided with selection fields for user data registration request, user data read request, and format conversion request, and a decision button. In this case, the user selects the user data registration request and then clicks the OK button. When the enter button is clicked, the mobile phone 10 displays a registration target data selection screen as shown in FIG. The registration target data selection screen is a screen for selecting the type of user data (phone book data, incoming melody data, etc.) to be registered in the storage server 20, and a selection column for each type of user data and the entire user data is selected. A selection field for selecting and a decision button are provided. The user
When the registration target data is selected on the registration target data selection screen and the decision button is clicked, the mobile phone 10 displays the type and size of the selected user data and the mobile phone 1.
A user data registration request including the position information of the write area for 0 is transmitted to the storage server 20 (step B
3).

The storage server 20 sends a transfer permission to the mobile phone 10 if the transmitted data size is less than the use permission size, and otherwise sends an error notification (step B4).

Upon receiving the transfer permission, the mobile phone 10 transmits to the storage server 20 the user data of the type selected on the transfer target data selection screen among the held user data (step B5).

The storage server 20 is a mobile phone 10.
The user data sent from the device is overwritten in the writing area assigned to the mobile phone 10, and a registration completion notification is transmitted to the mobile phone 10 (step B6). The mobile phone 10 displays a registration completion notification to inform the user that registration of user data has been completed (step B
7). In step B6, when the user data is already stored in the writing area assigned to the mobile phone 10, an inquiry message inquiring whether the overwrite is possible is transmitted to the mobile phone 10, and the overwrite OK is returned. Only in the case, it may be overwritten.

After that, the storage server 20 transmits the usage status information indicating the usage status (including, for example, the usage date and the information indicating that the usage pattern is registration of user data) to the authentication server 30 ( Step B8). As a result, the authentication server 30 displays the billing information (the mobile phone 1
A user ID of 0, a date of use, and a usage pattern of user data are transmitted to the billing server 40 (step B).
9).

The billing server 40 stores the sent billing information in association with the user information stored in step A9 (step B10).

Next, the operation of reading the user data stored in the storage server 20 from the mobile phone 10 will be described.

When reading user data from the storage server 20, the user sends a user authentication request including the user ID and password to the authentication server 30 using the mobile phone 10 (FIG. 6, step C1).

The authentication server 30 performs the authentication process, and if the authentication is OK, it is necessary to display the request selection screen data for displaying the request selection screen, and to display it according to the operation performed on the request selection screen by the user. The screen data of various screens and the position information of the writing area stored in association with the user ID of the mobile phone 10 in step A7 are transmitted to the mobile phone 10, and an error notification is given in the case of authentication NG (step C2). ).

The mobile phone 10 displays the request selection screen shown in FIG. 4 in accordance with the request selection screen data sent from the authentication server 30. In this case, the user selects the user data read request and then clicks the OK button. When the enter button is clicked, the mobile phone 10 displays a read target data selection screen as shown in FIG. The read target data selection screen is a screen for selecting the type of user data (phone book data, incoming melody data, etc.) to be read from the storage server 20, and a selection field for each type of user data and the entire user data is selected. A selection field for setting and a decision button are provided. When the user selects the read target data on the read target data selection screen and clicks the OK button, the mobile phone 10 issues a user data read request including the type of the selected user data and the position information of the write area to the storage server 20. (Step C3).

According to the user data read request, the storage server 20 reads the user data (the user data of the type specified by the user data read request) from the writing area and sends it to the mobile phone 10 (step C4). Of the user data currently held, the mobile phone 10 replaces the user data of the type selected on the transmission target data selection screen with the user data sent from the storage server 20 (step C
5).

After that, the storage server 20 sends the usage status information indicating the usage status (including, for example, the usage date and the information indicating that the usage pattern is the reading of user data) to the authentication server 30 (step. C6). As a result, the authentication server 30 displays the billing information (the mobile phone 1
A user ID of 0, a date of use, and a usage pattern of reading user data are transmitted to the billing server 40 (step C).
7).

The billing server 40 stores the sent billing information in association with the user information stored in step A9 (step C8).

Next, the operation when converting the format of the user data will be described. The format conversion of the user data is performed, for example, when the user of the mobile phone 10 purchases a new mobile phone (the model and format of which are different from those of the mobile phone 10).

The user uses the mobile phone 10 or a newly purchased mobile phone (not shown) to authenticate the authentication server 3
A user authentication request including the user ID and password is sent to 0 (FIG. 8, step D1). In the following description, the user uses the mobile phone 10.

The authentication server 30 performs the authentication process, and if the authentication is OK, it is necessary to display the request selection screen data for displaying the request selection screen, and display the request selection screen data according to the operation performed on the request selection screen by the user. The screen data of various screens and the position information of the writing area saved in association with the user ID of the mobile phone 10 in step A7 are transmitted to the mobile phone 10, and an error notification is given in the case of authentication NG (step D2).

The mobile phone 10 displays a request selection screen as shown in FIG. 4 according to the request selection screen data. In this case, the user clicks the OK button after selecting the format conversion request. When the decision button is clicked,
The mobile phone 10 displays a format conversion instruction screen as shown in FIG. In the format conversion instruction screen,
An input field for the model name of the mobile phone 10 used when registering user data in the storage server 20, an input field for the model name of a newly purchased mobile phone, and an enter button are provided. The user inputs the model name in the input field and then clicks the OK button. Accordingly, the mobile phone 10 transmits a format conversion request including the model name (two pieces) and the position information of the writing area to the authentication server 30 (step D3).

The authentication server 30 transmits the format conversion request sent from the mobile phone 10 to the format conversion server 50 (step D4).

The format conversion server 50 transmits to the storage server 20 a data request including position information of the writing area of the mobile phone 10 (step D).
5). As a result, the storage server 20 transmits the user data registered in the write area to the format conversion server 50 (step D6).

The format conversion server 50 identifies the conversion source format and the conversion destination format based on the model name included in the format conversion request, and determines the format of the user data sent from the storage server 20 as the conversion destination format. To (step D
7). After that, the format conversion server 50 transmits the format-converted user data and the position information of the writing area to the storage server 20 (step D8).

The storage server 20 overwrites the user data sent from the format conversion server 50 in the writing area indicated by the position information (step D9).

After that, the format conversion server 50
The usage status information indicating the usage status (for example, including the usage date and the information indicating that the usage pattern is format conversion) is transmitted to the authentication server 30 (step D10).
As a result, the authentication server 30 transmits the billing information (the user ID of the mobile phone 10, the date of use, the format of use to the format conversion) to the billing server 40 (step D1).
1).

The billing server 40 stores the sent billing information in association with the user information stored in step A9 (step D12).

After that, the authentication server 30 determines that the mobile phone 1
Send a conversion complete message to 0 (step D1
3). The mobile phone 10 displays a conversion completion message to notify the user that the format conversion has been completed (step D14). After that, when the user wants to download the user data registered in the storage server 20 to the newly purchased mobile phone, the user will use the newly purchased mobile phone and will be described with reference to the flowchart of FIG. Perform the same operation as the above. As a result, user data such as phone book data is downloaded to the newly purchased mobile phone. Here, since the user data downloaded is in conformity with the data format of the newly purchased mobile phone, it is possible to use the downloaded user data.

The billing server 40 determines the billing amount based on the billing information of the user based on the contract with the user of the mobile phone 10 at a time determined by the contract, such as at the end of the month, and performs credit settlement.

It should be noted that in the above-described embodiment, the user does not operate as shown in FIG.
Although the conversion source format and the conversion destination format are specified using the format conversion instruction screen shown in FIG. 7, only the conversion destination format is specified using the format conversion instruction screen, and the conversion destination format is the format conversion server 50. In the above, the determination may be automatically made based on the user data sent from the storage server 20. As a method of automatically determining, for example, the formats of user data used by various mobile phones are formatted, and the formats are compared with the user data sent from the storage server 20 to determine the format. The method can be adopted. Further, the conversion destination format may be automatically determined, and the specification of the conversion destination format using the format instruction screen may be eliminated. As a method of automatically determining the conversion destination format, for example, the authentication server 30 manages the correspondence relationship between the connection source (gateway server) and the mobile phone company, and the correspondence relationship between the mobile phone company and the format. A method can be adopted in which the mobile phone company is specified based on through which gateway server the conversion request is sent, and further the format is specified by using the correspondence relationship between the mobile phone company and the format.

Further, in the above-mentioned embodiment, the plurality of servers 20, 30, 40, 50 share the functions, but instead of the above-mentioned servers 20, 30, 40, 50, each server 20, You may make it connect one server with all the functions which 30,40,50 has to the network 100, and may perform the process demonstrated in the above-mentioned Example by this server. In addition, the storage server 20
When storing the user data sent from the mobile phone 10, the user data may be compressed and stored. When the user data is compressed and stored, when the user data is transmitted to the mobile phone 10, it is decompressed and then transmitted.

[0055]

[Second Embodiment] Next, a second embodiment of the present invention will be described. In this embodiment, the present invention is applied to a network system in which a mobile network and the Internet are mutually connected via a gateway server.

FIG. 10 is a block diagram of the second embodiment of the present invention. Referring to the figure, the mobile phone 10 is connected to the mobile network 110, and the storage server 20, the authentication server 30, the billing server 40, and the format conversion server 50 are connected to the Internet 120. Mobile network 110 and Internet 12
The protocol used is different from 0, and they are mutually connected via the gateway server 60.

The gateway server 60 has a function of mutually converting the protocol used in the mobile network 110 and the protocol used in the Internet 120, and by this function, the Internet 120
Each of the servers 20, 30, 40, 50 in the mobile phone 10 and the mobile phone 10 in the mobile network 110 can communicate using the respective protocols.

Referring to FIGS. 2, 3, 6, and 8, steps A1, A4, B1, B3, B5, C1, C3, D
1, D3, from the mobile phone 10 to the authentication server 30
Alternatively, communication with the storage server 20 is occurring.
In this case, from the mobile phone 10 to the mobile network 110
Communication is performed with the gateway server 60 via the.
After that, at the gateway server 60, the mobile network 1
The protocol in 10 is converted into the protocol in the Internet 120, and via the Internet 120,
Communication will be performed to the authentication server 30 or the storage server 20.

Similarly, referring to FIGS. 2, 3, 6, and 8, steps A2, A7, B2, B4, B6, C2,
At C4, D2, and D13, communication from the authentication server 30 or the storage server 20 to the mobile phone 10 occurs. In this case, the authentication server 30 or the storage server 20 communicates with the gateway server 60 via the Internet 120. After that, the gateway server 60 converts the protocol in the Internet 120 into the protocol in the mobile network 110, and communication is performed with the mobile phone 10 via the mobile network 110. The operation other than the above is the same as that of the first embodiment.

Although a plurality of servers 20, 30, 40, 50 share the functions in the above-described embodiment, each server 20, 30, 40, 50 is replaced with each server 20, You may make it connect one server with all the functions which 30,40,50 has to the network 100, and may perform the process demonstrated in the above-mentioned Example by this server.

[0061]

[Third Embodiment] Next, a third embodiment of the present invention will be described. The present embodiment is characterized in that a portable personal computer (personal computer) or a mobile information terminal is used instead of the mobile phone.

FIG. 11 is a block diagram of the third embodiment of the present invention. The difference between the present embodiment and the embodiment shown in FIG. 1 is that a personal computer or a mobile information terminal 11 is connected to the network 100 instead of the mobile phone 10. The operation of this embodiment is the same as that of the first embodiment except that the personal computer or the mobile information terminal 11 performs the process performed by the mobile phone 10.

In the above embodiment, the plurality of servers 20, 30, 40, 50 share the functions, but instead of the above-mentioned servers 20, 30, 40, 50, each server 20, You may make it connect one server with all the functions which 30,40,50 has to the network 100, and may perform the process demonstrated in the above-mentioned Example by this server.

[0064]

[Fourth Embodiment] Next, a fourth embodiment of the present invention will be described. The present embodiment is characterized in that the user data registered in the storage server can be processed using the application server.

FIG. 12 is a block diagram of the fourth embodiment of the present invention, which is different from the first embodiment shown in FIG. 1 in that an application server 70 is added.

When processing the user data registered in the storage server 20, the user uses the mobile phone 10 to send a user authentication request including the user ID and password to the authentication server 30 (step E in FIG. 13).
1).

The authentication server 30 performs the authentication process, and if the authentication is OK, it is necessary to display the request selection screen data for displaying the request selection screen, and to display it according to the operation performed on the request selection screen by the user. The screen data of various screens and the position information of the writing area stored in association with the user ID of the mobile phone 10 in step A7 are transmitted to the mobile phone 10, and an error notification is given in the case of authentication NG (step E2). ).

The mobile phone 10 displays a request selection screen as shown in FIG. 14 according to the request selection screen data.
The request selection screen shown in the figure is different from the request selection screen shown in FIG. 4 in that a processing request selection field is added. When the request selection screen shown in FIG. 14 is displayed, the user selects the processing request and then clicks the OK button. Thereby, the mobile phone 10 displays a processing menu screen as shown in FIG. The processing menu screen is provided with a plurality of selection fields for selecting what type of processing the application server 70 should perform, and a determination button. The user selects a processing process to be executed by the application server 70 on the processing menu screen, and then clicks the OK button. Thereby, the mobile phone 10 transmits a processing request including the type of processing selected by the user to the authentication server 30 (step E3).

As a result, the authentication server 30 requests the storage server 20 to reserve a temporary work area for application operation (step E4). The storage server 20 secures the work area and returns the position information to the authentication server 30 (step E5).

After that, the authentication server 30 passes the position information of the writing area allocated to the mobile phone 10 and the position information of the work area obtained in step E5 to the format conversion server 50, and uses the work area. Then, it is instructed to convert the format of the data stored in the writing area into the format of the application server 70. In response to this instruction, the format conversion server 50 performs format conversion (step E6).

After that, the authentication server 30 transmits the processing request and the work area position information sent from the mobile phone 10 to the application server 70 (step E7). As a result, the application server 70 uses the work area to perform the processing requested by the processing request (eg, converting the telephone directory data into text).
Then, when the processing is completed, the fact is notified to the authentication server 30 (step E8).

As a result, the authentication server 30 instructs the format conversion server 50 to restore the format in the work area to the original format. As a result, the format conversion server 50 restores the user data in the work area to the original format (step E).
9).

After that, the authentication server 30 sends the billing information (user ID of the mobile phone 10, date of use, use form of use of application server) to the billing server 40 (step E10). The billing server 40 stores the sent billing information in association with the user information (step E11).

Further, the authentication server 30 transmits a processing completion message including the processing result stored in the work area to the mobile phone 10 (step E12). As a result, the mobile phone 10 displays the processing completion message (step E13).

Finally, the authentication server 30 instructs the storage server 20 to release the work area (step E14). As a result, the storage server 2
0 releases the work area (step E15).

In the above-described embodiment, the plurality of servers 20, 30, 40, 50, 70 share the functions, but the above-mentioned servers 20, 30, 40, 50,
Instead of 70, each server 20, 30, 40, 50, 7
It is also possible to connect one server having all the functions of 0 to the network 100, and to perform the processing described in the above-mentioned embodiment by this server.

[0077]

[Fifth Embodiment] A fifth embodiment of the present invention will now be described. In this embodiment, the network system shown in FIG. 1 is caused to perform almost the same processing as the processing shown in the flow charts of FIGS. 2, 3, 6, and 8 and shown in the flow charts of FIGS. It is realized by performing processing, and is characterized in that a writing area can be added and contents of a plurality of allocated writing areas can be replaced at the request of the user. .

When the user requests the addition of the writing area, the user first uses the mobile phone 10 to authenticate the authentication server 30.
A user authentication request including the user ID and password is sent to (step F1 in FIG. 16).

The authentication server 30 performs the authentication process, and if the authentication is OK, it is necessary to display the request selection screen data for displaying the request selection screen, and to display the request selection screen data according to the operation performed on the request selection screen by the user. The position information of the writing area (one or more) stored in association with the screen data of various screens and the user ID of the mobile phone 10 is transmitted to the mobile phone 10, and in the case of authentication NG, an error notification is issued. Perform (step F2).

The mobile phone 10 displays a request selection screen as shown in FIG. 17 according to the request selection screen data. In the request selection screen of FIG. 17, the addition of a write area addition request selection field and a replacement request selection field are added.
This is different from the request selection screen shown in FIG. In the present embodiment, when steps B3, C3 and D3 are executed, the request selection screen shown in FIG. 17 is displayed instead of the request selection screen shown in FIG. The user selects the writing area addition request on the request selection screen, and then clicks the OK button. Thereby, the mobile phone 10 transmits a region addition request to the authentication server 30 (step F3).

When the area addition request is sent from the mobile phone 10, the authentication server 30 sends a request to secure a write area to be allocated to the mobile phone 10 to the storage server 20 (step F4). As a result, the storage server 20 secures the writing area to be allocated to the mobile phone 10 and returns the position information indicating the position to the authentication server 30 (step F5).

When the position information is returned, the authentication server 30
Is the position information returned (position of the added writing area) in addition to the position information of the writing area (such as the writing area allocated at the time of concluding the contract) that is already stored in association with the user ID of the mobile phone 10. Information) is also saved. Further, the authentication server 30 transmits the position information of the writing area added to the mobile phone 10 (step F
6). Thereby, the mobile phone 10 displays the position information of the added writing area (step F7). After that, the authentication server 30 transmits the billing information (user ID of the mobile phone 10, date of use, addition of writing area for use form) to the billing server 40 (step F8). The billing server 40 stores the billing information.

Next, the operation when the user of the mobile phone 10 exchanges the contents of the plurality of writing areas assigned to himself / herself will be described.

When the user of the mobile phone 10 exchanges the contents of the plurality of writing areas assigned to him / her, first, the user of the mobile phone 10 is authenticated by the authentication server 30 including the user ID and the password. Send the request (FIG. 18, step G1).

The authentication server 30 performs the authentication process, and if the authentication is OK, it is necessary to display the request selection screen data for displaying the request selection screen, and display the request selection screen data according to the operation performed on the request selection screen by the user. The position information of the writing area (one or more) stored in association with the screen data of various screens and the user ID of the mobile phone 10 is transmitted to the mobile phone 10, and in the case of authentication NG, an error notification is issued. Return (step G2).

The mobile phone 10 displays a request selection screen as shown in FIG. 17 according to the request selection screen data. The user selects the replacement request and then clicks the OK button. As a result, the mobile phone 10 is displayed in FIG.
The replacement instruction screen as shown in is displayed. The exchange instruction screen of FIG. 19 is an example of a screen displayed when the user of the mobile phone 10 is assigned with three writing areas. The screen data for displaying the replacement instruction screen is included in the screen data sent from the authentication server 30 in step G2. The authentication server 30 creates screen data for displaying the replacement instruction screen based on the position information of the writing area assigned to the mobile phone 10, which is stored in association with the user ID of the mobile phone 10. The exchange instruction screen is provided with a selection field for selecting two writing areas in which the storage contents are exchanged, and an enter button. When the user selects two writing areas, the user clicks the enter button. Thereby, the mobile phone 10 transmits a replacement request including the position information of the two writing areas selected by the user to the authentication server 30 (step G3).

When the replacement request is sent, the authentication server 30 requests the storage server 20 to temporarily secure a work area (step G4). In accordance with this request, the storage server 20 secures the work area and notifies the authentication server 30 of the position information (step G5).

The authentication server 30 reads user data from one of the two write areas designated by the user (area 1) and writes the user data in the work area (steps G6 and G7). Next, the user data is read from the other write area (area 2) designated by the user and written in area 1 (steps G8 and G9). Then, the user data is read from the work area and written in the area 2 (steps G10 and G11).

When the replacement is completed, the authentication server 30
Instructs the storage server 20 to release the work area, whereby the storage server 20 releases the work area (steps G12 and G13).

After that, the authentication server 30 changes the charging server 4
The billing information (user ID of mobile phone 10, date of use, area of user data used) is sent to 0 (step G14). The billing server 40 stores the billing information (step G15). Then, finally, the authentication server 30 sends an operation result notification to the mobile phone 10 (step G16). The mobile phone 10 displays the operation result notification (step 17).

In the present embodiment, after the writing area is added, the user of the mobile phone 10 transmits the user data registration request in step B3, among the plural writing areas allocated. It is also necessary to send information specifying which writing area the data is written to. Similarly, when the read request and the format conversion request are transmitted in steps C3 and D3, it is necessary to transmit information indicating which write area is to be processed. Further, in the above-described embodiment, the plurality of servers 20, 30, 40, 50 share the functions in the above-described embodiment, but the respective servers 20, 30, 4 described above are assigned.
Instead of 0, 50, each server 20, 30, 40, 50
It is also possible to connect one server having all the functions of the above to the network 100, and to perform the processing described in the above-mentioned embodiment by this server.

[0092]

As described above, in the user data backup system for a portable device of the present invention, the server has means for converting the format of the user data. Therefore, the user data stored in the server has a format different from that of the user data. Even the mobile device using the data can use the user data stored in the server. Therefore, for example, even when the user changes the model of the mobile device and the format of the user data changes, the user data registered in the server can be used.

Further, in the user data backup system for a portable device of the present invention, the server is provided with means for charging the user of the portable device of various fees such as a fee associated with the format conversion. Can benefit.

Furthermore, in the user data backup system for portable equipment of the present invention, the server has means for processing the registered data, so that the user can, for example, write text corresponding to the registered telephone directory data. It will be possible to obtain.

[Brief description of drawings]

FIG. 1 is a block diagram of a first embodiment of the present invention.

FIG. 2 is a flowchart showing a processing example when a contract is concluded.

FIG. 3 is a flowchart showing a processing example when user data is registered.

FIG. 4 is a diagram showing an example of a request selection screen.

FIG. 5 is a diagram showing an example of a registration target data selection screen.

FIG. 6 is a flowchart showing a processing example when reading user data.

FIG. 7 is a diagram showing an example of a read target data selection screen.

FIG. 8 is a flowchart showing a processing example at the time of format conversion.

FIG. 9 is a diagram showing an example of a format conversion instruction screen.

FIG. 10 is a block diagram of a second embodiment of the present invention.

FIG. 11 is a block diagram of a third embodiment of the present invention.

FIG. 12 is a block diagram of a fourth embodiment of the present invention.

FIG. 13 is a flowchart showing a processing example when processing user data.

FIG. 14 is a diagram showing an example of a request selection screen.

FIG. 15 is a diagram showing an example of a processing menu screen.

FIG. 16 is a flowchart illustrating a processing example when adding a region.

FIG. 17 is a diagram showing an example of a request selection screen.

FIG. 18 is a flowchart showing a processing example when the contents of the writing area are replaced.

FIG. 19 is a diagram showing an example of a replacement instruction screen.

[Explanation of symbols]

10 ... Mobile phone 20 ... Storage server 30 ... Authentication server 40 ... Billing server 50 ... Format conversion server 60 ... Gateway server 70 ... Application server 100 ... Network 110 ... Cellular network

─────────────────────────────────────────────────── ─── Continuation of front page (51) Int.Cl. ⁷ Identification code FI theme code (reference) G06F 17/60 506 G06F 17/60 506 H04M 1/275 ZEC H04M 1/275 ZEC F term (reference) 5B019 GA10 KA10 5K036 AA07 BB01 DD01 DD11 DD25 DD32 EE13 JJ02 JJ03 JJ04 JJ05 JJ12 5K101 KK18 LL12 MM07 NN18 NN48 PP03 UU19 UU20

Claims (17)

[Claims] 1. A mobile device transmits user data to a server via a network, the server stores user data sent from the mobile device, and the server stores the stored user data. A portable device including a step of converting a format into a format of a portable device different from the portable device; and a step of causing the server to transmit the user data after the format conversion to the different portable device. User data backup method. 2. The method of backing up user data of a portable device according to claim 1, wherein the server charges a fee associated with format conversion, a fee associated with saving user data, or a fee associated with transmission of user data to a user of the portable device. A method for backing up user data of a mobile device, comprising the step of claiming. 3. The portable device user data backup method according to claim 2, wherein the server includes a step of processing the stored user data according to an instruction from a user of the portable device. Device user data backup method. 4. The user data backup method for a portable device according to claim 3, further comprising the step of the server charging a fee for processing the data to a user of the portable device. Backup method. 5. The user data backup method for mobile device according to any one of claims 1 to 4, wherein the mobile device is a mobile phone. 6. The user data backup method for a mobile device according to claim 5, wherein the user data is telephone directory data. 7. The user data backup method for a mobile device according to claim 3, wherein the mobile device is a mobile phone, the user data is phonebook data, and the user data is processed. , A method for backing up user data of a mobile device, characterized by converting the telephone book data into text. 8. The mobile device comprises means for transmitting user data to a server via a network, the server storing means for storing user data sent from the mobile device, and storing the stored user data. User data of a mobile device, comprising means for converting a format into a format of a mobile device different from the mobile device, and means for transmitting the user data after the format conversion to the another mobile device. Backup system. 9. The user data backup system for a mobile device according to claim 8, wherein the server charges a fee associated with format conversion, a fee associated with saving user data, or a fee associated with transmission of user data. A user data backup system for a mobile device, comprising: 10. The mobile device user data backup system according to claim 9, wherein the server follows an instruction from a user of the mobile device.
A user data backup system for a mobile device, comprising a means for processing the stored user data. 11. The mobile device user data backup system according to claim 10, wherein the server comprises means for charging a user of the mobile device with a fee associated with data processing. User data backup system. 12. The user data backup system for a mobile device according to claim 8, wherein the mobile device is a mobile phone. 13. The user data backup system for a mobile device according to claim 12, wherein the user data is telephone directory data. 14. The user data backup system for a mobile device according to claim 10, wherein the mobile device is a mobile phone, the user data is phonebook data, and processing for the user data is performed. , A user data backup system for mobile devices, characterized by converting the phone book data into text. 15. A user data backup system for a mobile device, comprising: a mobile device connected to a mobile network; a server connected to the Internet; and a gateway server interconnecting the mobile network and the Internet. The mobile device includes means for transmitting user data to the server, the server stores the user data sent from the mobile device, and the format of the stored user data is stored in the mobile device. A means for converting to a format of a mobile device different from the device; and means for transmitting the user data after the format conversion to the different mobile device, wherein the gateway server includes means for performing protocol conversion. Characteristic portable device user data backup system. 16. A server, to which user data is sent from a mobile device via a network, for storing user data sent from the mobile device, and a format of the saved user data, A server comprising: means for converting into a format of a mobile device different from the mobile device; and means for transmitting the user data after the format conversion to the different mobile device. 17. A server computer to which user data is sent from a mobile device via a network, means for storing user data sent from the mobile device, a format of the saved user data, A unit for converting into a format of a mobile device different from the device, and a program for functioning as a unit for transmitting the user data after the format conversion to the other mobile device.