JP4719732B2 - Backup server, mobile device, communication system using these, and backup method - Google Patents

Description

  The present invention relates to a backup server that performs data backup and data update, a mobile device, a communication system using these, and a backup method.

  As one of backup techniques for user data in a client, there is a DataSync standard for synchronizing differential data between a client and a server, which is standardized by OMA (Open Mobile Alliance). In the DataSync standard, the server sends a message that triggers the start of synchronization to the client, and the client that receives the message starts synchronization. Here, the client and the server perform management by describing in the log information when the contents are changed by adding / editing / deleting to the data managed in advance. Then, based on this log information, it is possible to achieve synchronization by sending only data in which a difference has occurred between the client and the server during synchronization execution. This technology can be used for phone books, still images, moving images, bookmarks, ToruCa, schedule data, and the like.

  Patent Document 1 (Japanese Patent Laid-Open No. 2005-311552) is a technique that can perform general data backup. Patent Document 1 describes that the latest information is backed up without making the user aware of the phone book information.

  On the other hand, regarding the update of data held by the user, when the user acquires data from an information provider such as IP (Information Provider) via the network (NW), the user information obtained by the information provider There is already known a push-type update data transmission system that manages data and sends updated data to a user who has previously acquired the data when the data is updated. . This technology is effective for data distributed by content providers, and can be applied to ToruCa as well as still images and moving images. A technique related to data updating as generally described in Patent Document 2 (Japanese Patent Laid-Open No. 2001-75785) is known.

In addition to this, data that can be checked manually by the user from the client, or by setting time information in the data itself, so that the client checks the server for updates using periodic time information. A system to update the system is also considered. The former is already used in i-αppli (registered trademark), ToruCa (registered trademark), and the like, and the latter can be seen by copyright information etc. in which an expiration date is set.
Japanese Patent Laying-Open No. 2005-311552 Japanese Patent Laid-Open No. 2001-75785

  However, the user data backup / restore system by synchronization and the push type data update system, which are the above-mentioned conventional techniques, have the problem that each of them is processed independently and the wireless resources cannot be used efficiently. That is, when the synchronization process is performed, the radio resource is used only for that time, and when the data is updated, the radio resource is used to transmit the update data to the mobile device.

  Therefore, the present invention solves the above-described problems, and a backup server, mobile device, communication system, and backup method that can efficiently use radio resources when performing user data synchronization processing and user data update processing. The purpose is to provide.

In order to solve the above-described problems, a backup server according to the present invention stores, in a backup server that is in communication connection with a mobile device, user data to be synchronized with the mobile device in association with the mobile device. And means associated with acquisition-related information for enabling acquisition of update user data for overwriting and updating the user data from the mobile device that is the source of the user data stored in the storage means An update unit that acquires the updated user data based on the management table to be stored and the acquisition related information stored in the management table, and updates the user data stored in the storage unit with the updated user data A synchronization method for ensuring consistency between the user data stored in the mobile device and the user data stored in the storage means. When the by synchronization means, the synchronization of the user data between the mobile station is performed, related instructing the updating means so as to acquire the related information related to the user data stored in the storage means An information acquisition means, wherein the update means acquires related information together with the updated user data based on an instruction from the related information acquisition means, and the synchronization means performs synchronization processing after the update by the update means. The acquired related information is synchronized with the user data updated with the updated user data .

According to the present invention, update user data that overwrites and updates user data is acquired based on pre-stored acquisition-related information, and the stored user data is updated with the update user data, while moving Synchronization processing is performed so as to ensure consistency between user data stored in the machine and user data stored in advance. The synchronization process is configured to be performed using the updated user data. Thereby, the operation can be reduced for the user, and the radio resources for the synchronization process and the update process can be efficiently used.
Further, when user data synchronization processing is performed with the mobile device, related information related to the update target user data is acquired, and the acquired related information is acquired together with the update user data, and the target of the synchronization processing is acquired. By doing so, it is possible to automatically acquire related information that is considered to be desired by the user and synchronize it as user data, thereby realizing a user-friendly device. For example, when the user data is a store phone number and the related information is a store URL, ToruCa data, etc., the store URL, ToruCa data, etc. may be acquired using the phone number as a key. It is possible to acquire user data that the user may desire without being requested by the user.

  In the backup server of the present invention, it is preferable that the update unit performs the update process after the synchronization unit performs the synchronization process.

  According to the present invention, after performing the synchronization process, it is possible to perform the update process reliably by performing control so that the update process is performed. At least when performing the synchronization process, the update process is performed before that. As a result, the latest updated user data can be acquired. As a result, the operation can be reduced for the user, and the radio resources for the synchronization process can be used efficiently.

  The acquisition related information stored in the backup server of the present invention is preferably acquisition destination information indicating a storage destination of the updated user data.

  Here, the acquisition related information is acquisition destination information indicating a storage destination of the update user data, for example, link destination information such as a URL, and the update user data can be acquired using the link destination information.

  Further, the acquisition related information stored in the backup server of the present invention is key information for uniquely specifying acquisition destination information indicating a storage destination of the updated user data, and the update data acquisition means includes: It is preferable to obtain updated user data by executing a search process using the key information.

  The acquisition related information is key information for uniquely specifying the acquisition destination information indicating the storage destination of the update user data, and the update user data is acquired by executing a search process using the key information. Can do. For example, the acquisition related information is a telephone number, and the update data acquisition means accesses the telephone directory database and performs a search process using the telephone number, thereby obtaining desired update user data (for example, ToruCa data). Can be acquired.

Moreover, it is preferable that the synchronization means of the backup server of the present invention adds the meta information indicating that the update has been made to the updated user data and transmits the updated user data.

  According to the present invention, the updated user data can be transmitted by adding meta information indicating that the updated user data has been updated, and the mobile device can be notified of the updated user data.

  Moreover, it is preferable that the update means of the backup server of the present invention performs user data update processing every predetermined time.

  According to the present invention, by performing the update process of user data every elapse of a predetermined time, the synchronization process can be performed with the latest user data when a request for the synchronization process is received from the mobile device.

  The management table of the backup server according to the present invention stores update availability information indicating whether update is possible, and the updating means executes update processing based on the update availability information stored in the management table. It is preferable.

  According to the present invention, by executing user data update processing based on pre-stored update availability information, user data that is not desired to be updated is not updated, and thus an easy-to-use device is realized. Can do. The update availability setting information may be set for each user data, content type, or the like, or the update availability information may be set for all data.

  Further, the update means of the backup server of the present invention may perform an update process when the update user data corresponds to the update user data and is newer than the user data stored in the storage means. preferable.

  According to this invention, when the updated user data corresponds to the updated user data and is newer than the user data stored in advance, the updated user data can be updated with the old user data by performing the update process. Since there is no device, a user-friendly device can be realized.

  In addition, the backup server of the present invention is configured so that when synchronization processing of user data is performed with the mobile device by the synchronization unit, an instruction to acquire related information related to the user data to be updated is given to the update unit. It is preferable that the information processing device further includes an information determining unit, and the updating unit acquires related information acquired based on an instruction from the related information determining unit together with the updated user data.

  According to this invention, when synchronization processing of user data is performed with a mobile device, the related information related to the user data to be updated is acquired, the acquired related information is acquired together with the updated user data, By making it a target of synchronization processing, it is possible to automatically acquire related information that is considered to be desired by the user, synchronize it as user data, and realize a user-friendly device. For example, when the user data is a store phone number and the related information is a store URL, ToruCa data, etc., the store URL, ToruCa data, etc. may be acquired using the phone number as a key. It is possible to acquire user data that the user may desire without being requested by the user.

  Further, the synchronization means of the backup server of the present invention obtains all user data from the mobile device during the initial synchronization processing in the mobile device, and at least one of the unique information or the user ID of the mobile device. Acquired as identification information, and stores all of the user data in the storage means, stores the acquired identification information in the management table, and from the mobile device during the second and subsequent synchronization processing in the mobile device When it is determined that the transmitted identification information matches the identification information stored in the management table, it is preferable to execute a synchronization process.

  According to the present invention, in the second and subsequent synchronization processing in the mobile device, it is determined that the identification information (either the unique information or the user ID) transmitted from the mobile device matches the identification information stored in advance. In some cases, synchronization processing can be performed. Therefore, when handling user data such as non-redistributable data managed by DRM, etc., it is possible to restrict illegal data copying and appropriately provide services convenient for users such as synchronization processing and backup processing. Can be provided.

  Further, the mobile device of the present invention comprises mobile device side synchronization means for performing synchronization processing by receiving user data from the backup server, and storage means for storing user data received by the mobile device side synchronization means. I have. According to the present invention, synchronization processing can be performed with a backup server.

  Further, the mobile device of the present invention is the information for specifying the number of updated user data or the updated user data based on the meta information added to the user data received by the mobile device side synchronization means. Display means for displaying at least one of the above is further provided.

  According to the present invention, the number of updated user data can be displayed based on meta information added to the received user data, and the user can display the number of updated user data, or which user You can easily know if the data has been updated.

  By the way, the present invention can be described as an invention of a backup server and a mobile device as described above, and can also be described as an invention of a backup system and a backup method as follows. These are substantially the same inventions only in different categories, and exhibit the same actions and effects.

  That is, the backup system of the present invention includes the backup server and the mobile device.

The backup method of the present invention is a storage means for storing user data to be synchronized with a mobile device in association with the mobile device, and a transmission source of the user data stored in the storage means. In the backup method in a backup server, comprising: a management table that associates and stores a mobile device and acquisition related information for enabling acquisition of update user data for overwriting and updating the user data from the outside. An update step of acquiring the updated user data based on the acquisition-related information stored in the storage unit, and updating the user data stored in the storage unit with the updated user data; and storing in the mobile device A synchronization step for ensuring consistency between the stored user data and the user data stored in the storage means; Synchronous step, the synchronization of the user data between the mobile station is performed, and a related information acquisition step that instructs to acquire the relevant information related to the user data stored in the storage means, The synchronization step performs a synchronization process with the mobile device using the user data that has been subjected to the update process in the update step, and the update step updates the related information based on an instruction in the related information acquisition step. Acquired together with user data, and the synchronization step performs synchronization processing of the acquired related information together with user data updated with the updated user data when performing synchronization processing after updating in the updating step.

  The present invention can reduce operations for the user, and can efficiently use radio resources for synchronization processing and update processing.

  The present invention can be readily understood by considering the following detailed description with reference to the accompanying drawings shown for the embodiments. Subsequently, embodiments of the present invention will be described with reference to the accompanying drawings. Where possible, the same parts are denoted by the same reference numerals, and redundant description is omitted.

  FIG. 1 is a system configuration diagram of a communication system according to the present embodiment. As shown in FIG. 1, the communication system includes a backup server 100, a mobile device 200, and an IP server 300. The form of the IP server 300 is not limited as long as it functions as an update service server that can provide updated user data.

  The backup server 100 includes a data transmission / reception unit 101, a data synchronization protocol processing unit 102 (synchronization unit), a data storage unit 103 (storage unit), a user holding information management table 104 (management table), and a data acquisition unit 105 (update unit). , And an additional information additional data collating unit 106.

  This backup server 100 is realized by the hardware shown in FIG. FIG. 2 is a hardware configuration diagram of the backup server 100. As shown in FIG. 2, the backup server 100 shown in FIG. 1 physically includes a CPU 11, a RAM 12 and a ROM 13 that are main storage devices, an input device 14 such as a keyboard and a mouse that are input devices, and an output such as a display. The computer 15 includes a device 15, a communication module 16 that is a data transmission / reception device such as a network card, an auxiliary storage device 17 such as a hard disk, and the like. Each function described in FIG. 1 has an input device 14, an output device 15, and a communication module 16 under the control of the CPU 11 by reading predetermined computer software on hardware such as the CPU 11 and the RAM 12 shown in FIG. 2. This is realized by reading and writing data in the RAM 12 and the auxiliary storage device 17. Hereinafter, each functional block will be described based on the functional blocks shown in FIG.

  The data transmission / reception unit 101 is a part that performs synchronization processing with the mobile device 200, and that receives differential data from user data held in the mobile device 200 and transmits differential data of user data. is there.

  The data synchronization protocol processing unit 102 is a part that performs protocol processing for synchronizing user data. For example, the data synchronization protocol processing unit 102 performs protocol processing based on the datasync standard. The data transmission / reception unit 101 performs transmission / reception of difference data among user data based on processing by the data synchronization protocol processing unit 102, and performs synchronization processing of user data. The synchronization processing here is processing for taking consistency so that the user data stored in the backup server 100 and the mobile device 200 are the same, and there is a difference in the user data The difference data is transmitted to the mobile device 200 or the backup server 100.

  The data storage unit 103 is a part to be backed up by storing user data or updated user data acquired via the data transmission / reception unit 101 and the data synchronization protocol processing unit 102, and a user for specifying the mobile device 200 The ID, mobile device specific information, and user data are stored in association with each other. User data includes phone book data, downloaded content data / coupon data, image / video data, schedule data, bookmark data, and the like. The data synchronization protocol processing unit 103 performs synchronization processing using user data or updated user data stored in the data storage unit 103.

  The user holding information management table 104 is a management table for storing management information for managing acquisition destination information, data update date, and the like of data provided from the IP server among user data. In the management information stored in the user holding information management table 104, the difference data is stored in the data storage unit 103 by the data synchronization protocol processing object 102, and at the same time, the management information on the updated user data is updated. .

  A specific example of the user holding information management table 104 will be described with reference to FIG. FIG. 3 is an explanatory diagram showing management information described in the user holding information management table 104. As shown in FIG. 3, the user holding information management table 104 includes a data ID for uniquely identifying user data, a data acquisition destination URL (Uniform Resource Locator) indicating an access destination holding user data, data Data update date indicating the date when the user was updated, the user ID indicating the user (mobile device 200) who has acquired the user data, the data ID of the user's mobile device 200, and update availability information indicating whether update is possible Are stored in association with each other.

  The user data stored in the data storage unit 103 may be stored in the user holding information management table 104. For example, the telephone directory data may be stored in the data configuration shown in FIG. FIG. 4 is a schematic explanatory diagram of telephone directory data. As shown in FIG. 4, the telephone directory data includes a data ID, a telephone number 1, a telephone number 2, a name, an email address, an address, a URL, a memo, updatable information, and an update date. The telephone number 1 and the telephone number 2 are used, for example, to distinguish between a fixed telephone number and a mobile telephone number. An arbitrary message can be described in the memo column. The update availability information is update availability information indicating whether overwriting is possible. For example, for data that is described as being updateable, the update data from the backup server 100 can be overwritten. In addition, overwriting processing is rejected for data that is described as not being updated. Note that, in both FIG. 3 and FIG. 4, the update availability information is not essential information, and is information used in the modification as described later. In FIG. 4, the update availability information is set for each user data. However, the update availability information is not limited to this, and the update availability information may be set for all data, or phone book data, schedule data It may be set for each content type such as ToruCa data.

  The data acquisition unit 105 is a part that acquires user data from the IP server 300. After the synchronization processing (backup processing) by the data synchronization protocol processing unit 102 is performed, each data stored in the above-described user holding information management table 104 is stored. Among the user data of the user ID, for user data in which the data acquisition destination URL is described, the IP server 300 is accessed based on the data acquisition destination URL, and updated user data that is the latest user data is acquired. Further, the data acquisition unit 105 recognizes that the phone book data is phone book data even when the data acquisition destination URL is not described, and accesses the phone book management DB set in advance. Get the latest phone book data. For example, a store telephone number, the URL of the store's home page, a store-specific address, and the like can be acquired, and the acquired information can be updated as user data.

  The additional information additional data collating unit 106 includes information (for example, data ID, data update date, user ID, etc.) related to the updated user data acquired by the data acquiring unit 105, and management stored in the user holding information management table 104. This is a part for collating information (for example, data ID, data update date, update availability information, etc.). For example, the additional information additional data collating unit 106 matches the data update date of the acquired update user data (corresponding to the data ID) and the data ID stored in the user holding information management table 104. Compare the renewal date. When it is determined that the data update date of the acquired update user data is new, the update user data is output to the data storage unit 103, and the data storage unit 103 stores the user data as user data so that the update process is performed. Made. In accordance with this, the additional information additional data collating unit 106 also performs an update process of the user holding information management table 104.

  Thereafter, the data transmission / reception unit 101 transmits the difference data among the updated user data stored in the data storage unit 103 to the mobile device 200 that is the destination of the synchronization processing in accordance with the synchronization protocol processing by the data synchronization protocol processing unit 102. Send.

  The additional information additional data matching unit 106 may execute the following process without checking the update date. That is, the data acquisition unit 105 transmits the data update date described for each user data to the IP server 300 according to the control by the additional information additional data collating unit 106, and the transmitted data update date is determined by the IP server 300. Only the user data that can be determined to be older than the update date of the user data (update data) held in the IP server 300 may be transmitted. When such processing is adopted, the additional information additional data collating unit 106 can store the user data acquired by the data acquiring unit 105 as it is in the data storage unit 103 without checking the update date. The processing load on the server 100 can be reduced.

  Further, not only the data update date but also the user ID and the mobile device specific information may be transmitted together to further narrow down the partners to be updated. That is, whether or not updating is possible may be determined using a predetermined user ID or mobile device specific information.

  As another method, in the case of telephone directory data, the data acquisition unit 105 transmits an arbitrary telephone number to the IP server 300 in accordance with the control of the additional information additional data matching unit 106, and corresponds to the telephone number. Update user data (for example, data for filling the blank portion shown in FIG. 4, for example, a URL) may be returned and stored in the data storage unit 103. The IP server 300 here holds a telephone directory database, and can use this telephone directory database to acquire an address, URL, and the like.

  In addition, the data acquisition unit 105 may not transmit to the IP server 300 for those for which the update availability information is set to “no”, or may transmit the update availability information together with the telephone number. Whether the update is possible or not may be processed so as not to reply to the telephone number that is determined to be not updated.

  Further, the additional information additional data collating unit 106 determines whether or not the user (mobile device 200), which is the update destination of the updated user data acquired by the data acquiring unit 105, can be updated. That is, the user holding information management table 104 stores the user ID of the user who is the update destination in association with the update availability information, and the additional information additional data collating unit 106 is stored in the user holding information management table 104. Whether update is possible is determined based on the update availability information. If it is determined that the update is possible, the user data stored in the data storage unit 103 is updated.

  Next, the configuration of the mobile device 200 will be described. The mobile device 200 includes a data transmission / reception unit 201, a data synchronization protocol processing unit 202, a data storage unit 203, a browsing / playback unit 204, and a data synchronization UI unit 205. This mobile device 200 is also realized by the hardware configuration shown in FIG.

  The data transmission / reception unit 201 is a part that performs user data synchronization processing with the backup server 100, and transmits user data difference data together with the user ID to the backup server 100 and updates from the backup server 100. This is a part for receiving difference data of user data. The data transmission / reception unit 201 transmits / receives user data by wireless communication.

  The data synchronization protocol processing unit 202 is a part that performs protocol processing for synchronizing user data. The data transmission / reception unit 201 performs data transmission / reception based on the processing by the data synchronization protocol processing unit 202 to perform user data synchronization processing. That is, it is a part that performs user data synchronization processing in cooperation with the data synchronization protocol processing unit 102 of the backup server 100 described above.

  The data storage unit 203 is a part that stores user data in association with a user ID indicating a user. For example, the data storage unit 203 is a part that stores telephone directory data, downloaded content data / coupon data, image / video data, schedule data, bookmark data, and the like associated with a user ID.

  The browsing / playback unit 204 is a part that displays or plays back the user data. For example, a display that displays telephone directory data, downloaded content data / coupon data, image / video data, schedule data, bookmark data, etc., and playback for playing the audio portion of these data Part.

  A data synchronization UI (UserInterface) unit 205 is an operation part that can be operated by a user, and is a part that requests a synchronization process (backup process) to the backup server 100.

  Next, the IP server 300 will be described. The IP server 300 includes a data transmission / reception unit 301 and a data storage unit 302. This IP server 300 is also realized by the hardware configuration shown in FIG.

  The data transmitting / receiving unit 301 is a part that receives a request for updated user data from the backup server 100 and transmits the updated user data stored in the data storage unit 302 in response to the request.

  The data storage unit 302 stores updated user data such as content data, and stores content data updated by the operator of the IP server 300. This content data describes the update date.

  The operation of the communication system configured as described above will be described. FIG. 5 is a sequence diagram showing the operation of the communication system.

  First, by the operation of the user of the mobile device 200, the data transmission / reception unit 201 in the mobile device 200 connects to the backup server 100 (S101), and the user data is transmitted by the data synchronization protocol processing unit 102 and the data synchronization protocol processing unit 202. Is synchronized (S102). That is, a connection request is transmitted from the mobile device 200 together with the user ID, and the user data corresponding to the user ID is backed up or the difference data is interpolated. Then, the data synchronization protocol processing unit 102 performs a synchronization process completion process between the backup server 100 and the mobile device 200 (S103).

  Next, in the backup server 100, the data synchronization protocol processing unit 102 stores the user data for each user ID in the data storage unit 103 (S104), and the user holding information management table 104 is updated (S104). S105). Thereafter, after the update process of the user holding information management table 104, regarding the user data in which the data acquisition destination URL is described among the plurality of user data of the plurality of user IDs stored in the user holding information management table 104, The updated user data is acquired by the data acquisition unit 105 from the IP server 300 that is the acquisition destination (S106). Here, the acquisition process of user data of all users specified by the user IDs stored in the user holding information management table 104 is performed, but only the user data of the user who requested the connection in S101 is acquired. It may be.

  Next, it is judged by the additional information additional data collation part 106 whether it can update by the acquired update user data (S107). For example, if the acquired user data is newer than the data update date associated with the data ID of the user data stored in the user holding information management table 104, it is determined that the user data is to be updated. In addition, for user data for which whether or not update is possible is determined based on the update availability information.

  Here, when the additional information additional data collating unit 106 determines that the user data is updated (S107: YES), the updated user data acquired by the data acquiring unit 105 is stored in the data storage unit 103 as user data. Stored and updated (S108). After that, when a connection request with a user ID is transmitted from the mobile device 200 to the backup server 100 by a process equivalent to S101, the corresponding user data is acquired from the data storage unit 103 using the user ID as a key. Then, the synchronization process of the user data is performed (S110), and after the synchronization process is completed, the completion process is performed (S111).

  As described above, when the user data synchronization process (backup process) is performed, the update user data is acquired. Therefore, the user can easily perform the synchronization process and the update process without performing the synchronization process and the update process one by one. And radio resources can be used efficiently.

  As described above, in FIG. 5, the update process in the backup server 100 is performed after the synchronization process in the mobile device 200, but the present invention is not limited to this, and the synchronization process in the mobile device 200 is performed. The update user data may be acquired from the IP server 300, and then the synchronization process may be performed using the update user data.

  Further, a method for periodically checking and acquiring the presence / absence of updated user data, and a data acquiring method triggered by notification of an update message from the IP server are conceivable. A specific example relating to such acquisition of updated user data will be described. FIG. 6 is a system configuration diagram of a communication system in a modification of the present embodiment. The backup server 100a in this modification includes a data transmission / reception unit 101, a data synchronization protocol processing unit 102, a data storage unit 103, a user holding information management table 104, a data acquisition unit 105 (related information acquisition unit), and an additional information additional data verification unit In addition to 106, the update permission setting unit 107, the data preference determination unit 108 (related information acquisition unit), the message reception unit 109, the meta information addition unit 110, and the backup data matching table 111 are further configured. . Hereinafter, the components will be described focusing on the added portion.

  The update permission setting unit 107 is a part for setting whether or not updating is possible for each user data in the management information stored in the user holding information management table 104. The update permission setting unit 107 can set whether to update user data based on an instruction from the mobile device 200. In the example of FIG. 3, the update availability information is set for each user data, but is not limited to the description for each user data, and may be set as follows.

  For example, based on an instruction from the mobile device 200, the update permission setting unit 107 includes, for each data type (for example, phone book data, ToruCa data) among the management information stored in the user holding information management table 104. Alternatively, whether or not updating is possible can be set for each data record (for example, destination A in the phone book data and store A for ToruCa data in ToruCa data). In this case, the data storage unit 103 needs to be provided with information indicating the data type for each user data.

  In this modification, the backup server 100 determines whether or not the user data can be updated. However, the present invention is not limited to this, and the backup server 100 (data acquisition unit 105) includes the user ID or the mobile device specific information, The data ID and update availability information set for each user data is transmitted to the IP server 300, and the IP server 300 needs to transmit update user data corresponding to the data ID based on the received data ID and update availability information. You may make it judge NO.

  The data preference determination unit 108 determines the user preference based on the management information stored in the user holding information management table 104 and instructs the data acquisition unit 105 to perform data acquisition based on the determination. Part. For example, when a phone number of a store is stored in the user holding information management table 104, the data acquisition unit 105 can be instructed to add ToruCa data of the store. For example, the data acquisition unit 105 acquires the updated user data from the IP server 300 based on the instruction, accesses the server that manages the ToruCa data, and sets the telephone number or the store name. Based on the search process, related data (for example, ToruCa data) is acquired. The data acquisition unit 105 stores the acquired user data (for example, ToruCa data) and its management information (data update date) in the user holding information management table 104 and the data storage unit 103.

  The message receiving unit 109 is a part that receives an update message transmitted from the update message notification unit 302 in the IP server 300 and indicating that the update has been performed. This update message includes a data ID for specifying user data to be updated. When the message reception unit 109 receives the update message from the IP server 300, the message reception unit 109 outputs a message to that effect to the data acquisition unit 105, and the data acquisition unit 105 uses the data ID included in the update message as a trigger. An acquisition process of specified update user data is performed.

  The meta information addition unit 110 is a part that adds meta information indicating that the update user data acquired by the data acquisition unit 105 has been updated. The updated user data to which the meta information is added is stored in the data storage unit 103 as it is. This meta information is, for example, flag information indicating that it has been updated. In the mobile device 200, for example, an icon is displayed for updated user data so as to change the display form of user data based on this flag information. Can be controlled to display.

  The updated user data acquired by the data acquisition unit 105 is added with an updated data update time (or data acquisition time or synchronization time). Then, the meta information addition unit 110 may describe the data update time in addition to the information indicating the update as the meta information. In this case, the mobile device 200 can grasp the number of meta information by counting the number of meta information, and can display the number and the data update time by means such as a pop-up.

  The number of updates is preferably as follows. The updated updated user data may be composed of a single file (or folder), and this single file may include a plurality of data records. For example, a concert schedule of an artist is composed of a plurality of schedules (a plurality of data records), but updated user data may be handled as one file. In this case, since it may not be preferable that the updated user data is counted as one, if there are multiple data records in one file, the number of multiple data records is the number of updated data. It is preferable to be treated. Furthermore, it is preferable that files and folders can be calculated separately. In this embodiment, a folder and a file are handled as user data, and the mobile device 200 acquires a folder (with meta information) from the backup server 200 as updated user data, and then a file (meta) located below the folder. (With information). By counting the meta information of the folders and the meta information of the files, the number of updates can be grasped individually for the folders and files.

  In the present embodiment, meta information is added by the number of changes, or the number of changes is described therein, and the change number is added to the user data, so that the change is made in the mobile device 200. The number of cases can be recognized. Further, when a plurality of data records are changed in one file, the number of changes needs to be received from the IP server 300. Further, when updating is performed for each predetermined data type or folder, the data type or folder may be counted as one.

  The backup data matching table 111 is a part that stores user data transmitted from the mobile device 200 and mobile device specific information for specifying the mobile device 200 in association with each other. Upon receiving a request for synchronization processing from the mobile device 200, the data transmission / reception unit 101 and the data synchronization protocol processing unit 102 transmit difference data among user data stored in the data storage unit 105 and cannot be redistributed (for example, For user data for which DRM (Digital Right Management) is set, difference data is configured to be transmitted only to the mobile device 200 whose mobile device specific information stored in the backup data matching table 111 matches. Yes.

  The data synchronization protocol processing unit 102 is configured to count the number of accesses (synchronization request count) from the mobile device 200 for each mobile device specific information. When the data synchronization protocol processing unit 102 determines that the access from the mobile device 200 having the mobile device specific information is the first time based on the number of accesses and the mobile device specific information, the mobile device as described below. If there is a discrepancy between the access counts held by the 200 and the backup server 100, all other data is exchanged, and if it is determined that synchronization processing cannot be performed from the difference data, synchronization processing based on the SlowSync processing is performed. That is, instead of transmitting / receiving only difference data, a process for acquiring and storing all data from the mobile device 200 is performed. More specifically, in the SlowSync process, in order to synchronize all data between the mobile device 200 and the backup server 100, all data is transmitted from the mobile device 200 to the backup server 100, and then user data that is not in the mobile device 200 is transmitted. The data is confirmed by the backup server 100, and data is transmitted from the backup server 100 to the mobile device 200.

  Further, the access count is also counted and held in the mobile device 200. Then, after the synchronization is completed, a process of matching the number of accesses held in the data motive protocol processing unit 102 in the server with the number of accesses held in the mobile device 200 is performed. Here, the access count on the mobile device 200 side may be matched, the access count on the backup server 100 side may be matched, or the access count may be matched by another method.

  In the next synchronization process, if the numbers of access counts held in the data synchronization protocol processing unit 202 in the mobile device 200 and the data synchronization protocol processing unit 102 in the backup server 100 match, synchronization is performed only by the difference. If it does not match, the backup server 100 determines that synchronization cannot be achieved with only the difference data, and the SlowSync process is executed. After this SlowSync processing, processing for matching the number of accesses is performed.

  In addition, the number of accesses in the mobile device 200 is changed when the model is changed (the number of accesses is shifted), when data is reset in the mobile device 200, collective data reception by infrared rays, via an external memory such as an SD card (registered trademark). Reset when data is received. In such a case, it can be determined that all data has been replaced, and it can be determined that synchronization cannot be achieved only with the difference data from the end of the previous synchronization. In this case as well, the SlowSync process is executed. . After this SlowSync processing, processing for matching the number of accesses is performed.

  Processing of the backup server 100 in the modified example configured as described above will be described. For example, in addition to the method of acquiring data after the above-described synchronization processing using the backup server 100, a method of periodically checking for and acquiring update data, and data triggered by reception of an update message from an IP server The acquisition method will be described.

  Periodic confirmation of the presence or absence of update data means that a data acquisition request is made for all of the acquisition destination URLs of the backed-up data at preset time intervals (for example, during a period of low traffic). . Data acquisition triggered by reception of an update message from the IP server 300a means that an update message is transmitted by the update message notification unit 303 in the IP server 300a when the data in the IP server 300a is updated. The message is received by the message receiving unit 109 in the backup server 100a. After receiving this message, the backup server 100a makes a data acquisition request to the corresponding URL, whereby the latest user data can be acquired.

  FIG. 7 is a flowchart showing processing in a modified example of the backup server 100, and is a flowchart showing processing when user data is periodically acquired.

  First, for the data IDs in which the data acquisition destination URL is described among the data IDs stored in the user holding information management table 104, the data acquisition destination URL is periodically checked for each user ID by the data acquisition unit 105. (S201). Then, the data acquisition unit 105 executes access to the IP server 300 based on the data acquisition destination URL (S202), and updated user data is acquired for each user ID (S203).

  Next, the additional information additional data collating unit 106 reads the update ID information of the data ID corresponding to the acquired update user data from the user holding information management table 104 (S204). Then, the additional information additional data collating unit 106 determines the update availability information of the user data corresponding to the data ID based on the update availability information (S205).

  Here, when it is determined that the update availability information is possible (S205: YES), the update date of the updated user data is associated with the data ID stored in the user holding information management table 104. It is determined whether or not it is newer (S206). If it is determined that the data is new, update processing of user data corresponding to the data ID is performed in accordance with the user holding information management table 104 (S207). The updated user data is stored in the data storage unit 103, and when the process of S109 in FIG. 5 is executed, the latest updated user data is the target of the synchronization process.

  If it is determined in S205 or S206 that the update availability information is negative and the user data to be updated is old, the user data is not updated and the process ends (S208). .

  In this way, updated user data is periodically acquired, stored as user data in the data storage unit 103, and updated to perform synchronization processing with the mobile device 200 using the latest user data. Can do.

  Next, FIG. 8 is a flowchart when the backup server 100 performs an update process of user data by receiving an update message from the IP server 300.

  When the update message transmitted from the update message notifying unit 302 in the IP server 300 is received by the message receiving unit 109 in the backup server 100 (S301), a message to that effect is output to the data acquiring unit 105, and the data acquiring unit 105 Thus, the data is confirmed with respect to the IP server 300 based on the data acquisition destination URL (S302), and the data is acquired. Thereafter, the processing from S203 to S208 in FIG. 7 is executed.

  Thereby, based on the update information notified in the IP server 300, the backup server 100 can acquire the latest update data, and can perform a synchronization process with the mobile device 200 using this update data.

  Next, processing of the backup server 100 that can add meta information for displaying the updated information on the mobile device 200 will be described. FIG. 9 is a flowchart showing the processing of the backup server 100 for adding meta information indicating update.

  First, updated user data is transmitted from the IP server 300 and stored in the data storage unit 103 and the user holding information management table 104 together with management information related to the user data as updated user data. Here, the user data may be periodically acquired by the backup server 100 or may be acquired based on an update message.

  The updated user data is acquired by the data acquisition unit 105 according to the management information stored in the user holding information management table 104 and is updated when stored as user data in the data storage unit 103. Meta information is added by the meta information adding unit 110 (S401).

  Thereafter, when receiving a request for synchronization processing from the mobile device 200, the backup server 100 performs user data synchronization processing (restoration of updated user data) (S402). After the synchronization processing, the backup server 200 deletes the meta information added to the user data stored in the data storage unit 103 (S403).

  On the other hand, in the mobile device 200, the user data to which the meta information is added is stored in the data storage unit 203 (S404). Then, a user data browsing instruction by an application is made by an operation from the user, and a browsing process of user data is performed in the browsing / playback unit 204 (S405). Here, the browsing / playback unit 204 determines whether or not meta information is added to the user data to be browsed (S406). When it is determined that the user data to which the meta information is added is displayed, the user data is displayed by the browsing / reproducing unit 204 together with information indicating that the meta data has been updated (S407). For example, it may be possible to display “new” using an icon. If the meta information is not given, the user data is displayed by the browsing / reproducing unit 204 as it is (S408). In addition, the number of updates can be calculated and displayed by counting the number of meta information.

  Next, the process for the user data in which the DRM is set in the backup server 100 in this modification will be described. FIG. 10 is a flowchart illustrating the operation of the backup server 100 that performs synchronization processing on user data for which DRM is set.

  In the backup server 100, the backup request and the mobile device specific information of the mobile device 200 are received from the mobile device 200 (S501). Then, in the backup server 100, based on the received mobile device specific information, the data synchronization protocol processing unit 102 can determine whether or not synchronization is possible using only difference data (for example, whether access from the mobile device 200 is the first time). Determination is made (S502).

  Here, if the data synchronization protocol processing unit 102 determines that the synchronization with the differential data is possible, the received mobile device specific information is transferred to the backup data verification table 111 and referred to (S503). When the data motive protocol processing unit 102 determines that the mobile device specific information is stored in the backup data collation table 111 (S504: YES), the data synchronization protocol processing unit 102 stores the data in the data storage unit 103. The synchronization processing of the user data being performed, that is, the restoration processing for the mobile device 200 is performed (S505).

  If the data synchronization protocol processing unit 102 determines that the mobile device specific information is not stored in the backup data matching table 111 (S504: NO), the data synchronization protocol processing unit 102 stores it in the data storage unit 103. Among the existing user data, data that cannot be redistributed is not subjected to synchronization processing, that is, restoration processing for the mobile device 200, and synchronization processing is performed for user data that is not redistributable data (S506).

  In S502, if the data synchronization protocol processing unit 102 determines that synchronization using only difference data is not possible (for example, the first access from the mobile device 200), all user data is received from the mobile device 200. Is stored in the data storage unit 103 as backup data (S507).

  As described above, when data that cannot be redistributed is acquired from a predetermined mobile device 200, the synchronization processing (restore processing) is performed only on the predetermined mobile device 200. Therefore, it is possible to perform an appropriate backup process for user data whose copy is restricted by DRM or the like. For example, as data that cannot be redistributed, there is ToruCa, and there is a time limit for use. There are cases in which updated user data updated at this time is stored as user data and redistributed in accordance with a synchronization request from the mobile device 200. According to the present embodiment, even in such a case, the updated user data can be appropriately transmitted as user data to the mobile device 200, and a user-friendly device can be realized.

  In this modification, whether or not synchronization processing is possible is determined based on the mobile device specific information, but whether or not synchronization processing is possible may be determined based on the user ID. By performing processing based on the user ID, it is possible to back up user data to at least the same user even when a model change or the like is performed, thereby realizing an easy-to-use device. On the other hand, by checking both the user ID and the mobile device specific information, it is possible to more appropriately limit illegal copy processing of content data to be copyrighted.

  Next, a modification of the communication system including the backup server 100 will be described. In the above-described embodiment, it is assumed that the backup server 100 is arranged in a network managed by the carrier and there is only one backup server 100, but the present invention is not limited to this. For example, the backup server 100 may be configured to be distributed for each data type, and the location of the backup server 100 is not limited to within the jurisdiction of the carrier operator, but is also arranged in other carrier operators or other service providers. Also good.

  The specific configuration will be described. FIG. 11 is a system configuration diagram of a communication system according to a modification. As shown in FIG. 11, the backup server 100b is provided for user data of data type A (for example, only ToruCa), accepts only user data of data type A from the mobile device 200, and performs backup and restore processing. It can be performed. Similarly, the backup server 100c is provided for user data of data type B (for example, moving image data), accepts only user data of data type B from the mobile device 200, and performs backup and restore processing. be able to. In this way, the processing load on each of the backup servers 100b and 100c can be reduced by the distributed arrangement. Further, the backup server 100d may be arranged in the IP server 300c. By configuring like this backup server 100d, there is an effect that the processing of the user data update query can be simplified.

  Next, functions and effects of the present embodiment and its modifications will be described. In the backup server 100 according to the present embodiment, the data acquisition unit 105 acquires update user data for overwriting and updating user data based on a data acquisition destination URL that is acquisition-related information stored in advance in the user holding information management table 104. To do. Then, the data acquisition unit 105 updates the user data stored in the data storage unit 103 with the updated user data. On the other hand, the data motivation protocol processing unit 102 performs a synchronization process so that the user data stored in the mobile device 200 and the user data stored in the data storage unit 103 are consistent. The synchronization processing is configured to be performed using user data that has already been updated. That is, the update process is performed before the synchronization process is performed, and when the synchronization process is performed, the update process is further performed at least since the previous synchronization process was performed. For example, when the synchronization processing is performed by the data synchronization protocol processing unit 102, the data acquisition unit 105 updates the user data stored in the data storage unit 103 in accordance with the management information stored in the user holding information management table 104. Process. Thereafter, when a new request for synchronization processing is received from the user, the data synchronization protocol processing unit 102 performs synchronization processing using the updated updated user data. When a request for synchronization processing is received, update processing may be performed prior to the synchronization processing, and the synchronization processing may be performed using updated user data. This update process may be performed every predetermined period, or may be performed according to a notification of an update message from the IP server 300.

  As a result, the synchronization process and the update process are not operated independently, the operation of the synchronization process and the update process can be reduced for the user, and the radio resources for the synchronization process and the update process can be efficiently used. Can be used. Also, the backup server acquires update user data and performs update processing, and the IP server 300 improves communication efficiency compared to receiving update requests from a plurality of mobile devices 200 individually. Can do. Further, since the synchronization process and the update process can be performed in the same manner, the communication protocol for that can be made the same, and the processing load on the mobile device 200 can be reduced. Further, it is considered that the update rate of user data is improved as compared with the case where the update is performed individually according to the request from the mobile device 200.

  Here, the acquisition destination of the update user data may be the IP server 300 specified by the data acquisition destination URL, or a predetermined acquisition destination (IP server 300), and key information such as a telephone number is obtained from the acquisition destination. Update user data (for example, ToruCa data) may be acquired by performing a search process based on the above.

  In addition, the backup server 100a according to the modification includes a meta information adding unit 110, adds meta information indicating that the updated user data is acquired by the data acquiring unit 105, and performs synchronization processing including the meta information. By doing so, it is possible to know the number of updated user data by counting the meta information in the mobile device 200 and to notify the user by displaying it.

  Further, in the backup server 100 according to the present embodiment, the user holding information management table 104 stores update availability information indicating whether update is possible for each user data (data ID). Then, the additional information additional data collating unit 106 performs user data update processing based on the update availability information stored in the user holding information management table 104. Thereby, it is possible to make it impossible to update user data that is not desired to be updated, and it is possible to provide an easy-to-use backup system.

  The additional information additional data collating unit 106 compares the user data stored in the data storage unit 103 with the acquired updated user data when updating the updated user data, and updates the updated user data. If the date is new, the data acquisition unit 105 performs an update process. This makes it possible to provide an easy-to-use backup system because update processing is not performed on old user data.

  Further, when the backup server 100a in the modification performs user data synchronization processing with the mobile device 200 using the data synchronization protocol processing unit 102, the data acquisition unit 105 acquires updated user data and data Based on an instruction from the preference determination unit 108, related information related to user data to be updated is acquired. And by making the acquired related information an object of synchronization processing together with the updated user data, it is possible to automatically acquire the related information that seems to be desired by the user and synchronize it as user data, A user-friendly device can be realized. For example, when the user data is a store phone number and the related information is a store URL, ToruCa data, etc., the store URL, ToruCa data, etc. may be acquired using the phone number as a key. It is possible to acquire user data that the user may desire without being requested by the user.

  In addition, the backup server 100a in the modified example has the identification information (either unique information or user ID) transmitted from the mobile device 200 in the second and subsequent synchronization processing with the mobile device 200, the backup data matching table 111. If the data synchronization protocol processing unit 102 determines that the identification information matches the stored identification information, the data synchronization protocol processing unit 102 can execute the synchronization processing. Therefore, when handling user data such as non-redistributable data managed by DRM, etc., it is possible to restrict illegal data copying and appropriately provide services convenient for users such as synchronization processing and backup processing. Can be provided.

  Further, the mobile device 200 in the present embodiment can perform user data synchronization processing with the backup server 100 or 100a. In addition, for user data to which meta information is added from the backup server 100a, the number of updates can be grasped by counting the number of the meta information, and the number can be displayed on the browsing / playback unit 204. it can. In addition, information for specifying the updated user data can be displayed. For example, by displaying “new” as an icon, it is easy to specify the updated user data. Therefore, the user can know the number of updates of user data based on the number of displayed items, and can easily know which user data has been updated.

It is a system configuration figure of the communications system of this embodiment. 2 is a hardware configuration diagram of a backup server 100. FIG. It is explanatory drawing which shows the management information described in the user holding information management table. 5 is a schematic explanatory diagram of telephone directory data of a mobile device 200. FIG. It is a sequence diagram which shows operation | movement of a communication system. It is a system configuration | structure figure of the communication system in a modification. 4 is a flowchart illustrating processing when user data is periodically acquired in the backup server 100. 4 is a flowchart illustrating processing when user data is acquired based on an update message from an IP server 300 in the backup server 100. It is a sequence diagram which shows the process of the backup server 100 which adds the meta information which shows the effect of an update, and the mobile apparatus 200 which processes meta information. It is a flowchart which shows operation | movement of the backup server 100 which performs the synchronous process with respect to the user data in which DRM was set. It is a system configuration | structure figure of the communication system in a modification.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 ... Backup server, 100a ... Backup server, 100b ... Backup server, 100c ... Backup server, 100d ... Backup server, 101 ... Data transmission / reception part, 102 ... Data synchronization protocol processing part, 103 ... Data storage part, 104 ... User holding information Management table 105 ... Data acquisition unit 106 ... Additional information addition data collation unit 106 ... Data acquisition unit 107 ... Update permission setting unit 108 ... Data preference determination unit 109 ... Message reception unit 110 ... Addition of meta information , 111 ... Backup data collation table, 200 ... Mobile device, 201 ... Data transmission / reception part, 202 ... Data synchronization protocol processing part, 203 ... Data storage part, 204 ... Browsing / playback part, 205 ... Data synchronization UI part, 300 ... IP server, 300c ... IP Over bar, 301 ... data receiving section, 302 ... data storage section, 302 ... update message notification unit.

Claims (13)

In the backup server that is connected to the mobile device,
Storage means for storing user data to be synchronized with the mobile device in association with the mobile device;
Management that associates and stores a mobile device that is a transmission source of user data stored in the storage means and acquisition related information that enables acquisition of update user data for overwriting and updating the user data from the outside Table,
An update unit that acquires the updated user data based on the acquisition related information stored in the management table, and updates the user data stored in the storage unit with the updated user data;
Synchronization means for ensuring consistency between user data stored in the mobile device and user data stored in the storage means;
When the synchronization means performs synchronization processing of user data with the mobile device, acquisition of related information instructing the update means to acquire related information related to user data stored in the storage means Means and
The update means acquires related information together with the updated user data based on an instruction from the related information acquisition means,
The synchronization means, when performing synchronization processing after updating by the updating means, performs synchronization processing of acquired related information together with user data updated with the updated user data .   The backup server according to claim 1, wherein the update unit performs update processing after the synchronization unit performs synchronization processing. The acquisition-related information, the backup server according to claim 1 or 2, characterized in that the acquisition destination information indicating a destination of the updated user data. The acquisition related information is key information for uniquely specifying acquisition destination information indicating a storage destination of the updated user data,
The backup server according to claim 1, wherein the update unit acquires update user data by executing a search process using the key information. Said synchronization means, a meta information indicating that updated by adding the update user data, the backup server according to claim 1, any one of 4, characterized in that transmitting the update user data.   The backup server according to any one of claims 1 to 5, wherein the update unit performs a user data update process every predetermined time. The management table stores update availability information indicating whether update is possible,
The backup server according to any one of claims 1 to 6, wherein the update unit executes update processing based on update availability information stored in the management table.   The update means performs update processing when the update user data corresponds to the update user data and is newer than the user data stored in the storage means. 7. The backup server according to any one of items 6. The synchronization means includes
During the initial synchronization processing in the mobile device, all of the user data is acquired from the mobile device, and at least one of the unique information or the user ID of the mobile device is acquired as identification information, and all of the user data is acquired Storing the acquired identification information in the management table while storing the storage means;
In the second and subsequent synchronization processing in the mobile device, the synchronization processing is executed when it is determined that the identification information transmitted from the mobile device matches the identification information stored in the management table. The backup server according to any one of claims 1 to 8 . Mobile device side synchronization means for performing synchronization processing by receiving user data from the backup server according to any one of claims 1 to 9 ,
A mobile device comprising: storage means for storing user data received by the mobile device-side synchronization means. A display for displaying at least one of the number of updated user data and information for specifying the updated user data based on the meta information added to the user data received by the mobile unit synchronization means The mobile device according to claim 10 , further comprising means. The backup server according to any one of claims 1 to 9 ,
A backup system comprising the mobile device according to claim 10 or 11 . A storage unit that stores user data to be synchronized with the mobile unit in association with the mobile unit, and overwrites and updates the mobile unit that is the source of the user data stored in the storage unit and the user data In a backup method in a backup server comprising: a management table that associates and stores acquisition related information for enabling update user data to be acquired from outside,
An update step of acquiring the updated user data based on the acquisition related information stored in the management table, and updating the user data stored in the storage unit with the updated user data;
A synchronization step for ensuring consistency between user data stored in the mobile device and user data stored in the storage means;
By the synchronization step, the synchronization of the user data between the mobile station is performed, and a related information acquisition step that instructs to acquire the relevant information related to the user data stored in the storage means ,
The synchronization step performs a synchronization process with the mobile device using the user data subjected to the update process in the update step,
The update step acquires related information together with the updated user data based on an instruction of the related information acquisition step,
The synchronization method includes performing synchronization processing of acquired related information together with user data updated with the updated user data when performing synchronization processing after the update in the updating step.

Images