KR100901363B1 - Centralized control backup function - Google Patents

Abstract

A method and a mobile device for centrally controlling the backup function are provided so that parties such as backup devices can effectively know how the data content is backed up from the mobile device or how the data content is restored to the mobile device. . The mobile device exposes to the party rules for backing up or restoring data content, and the rules are for the party as well as other parties including the mobile device itself. The rules are included in a list formatted in extensible markup language (XML). If the party is an external party, in response to the party fetching an object exchange protocol (OBEX) capability object, the mobile device provides the OBEX capability object. The OBEX capability object describes the capabilities of the mobile device, and the OBEX capability object is used by the external party to access a list about the rules via the mobile device exposing the rules to the external party. It is to.

Description

Centrally controlled backup functionality

The present invention relates to data backup, and more particularly to data backup from a mobile communication device.

The importance of user data in mobile telephone devices is of great interest to the telecommunications industry. Because more and more wireless phones are used for communication as well as for personal data management. Therefore, in order to prevent such data loss, data backup has become an important problem. Some of such data may be backed up in synchronization with a local personal computer (PC) or may be backed up remotely by a synchronization server located on a network. If the device is lost or broken, or in the case of a hardware (HW) crash, a one-way synchronization is set up from the server (or PC) to the phone to restore data. You can do that. However, data such as documents or photos taken by the phone's built-in camera may not be an element of a typical synchronization procedure, and they may require conventional backup, which is performed manually instead of a regular synchronization method. . Different types of data need to be backed up at different intervals and may also require different storage capacities, thus backing up different types of data to different locations. An effective system is needed.

Recently, PC "suites" have been developed to provide an application package that allows a user to synchronize, edit and back up many phone files to a compatible PC via wireless or cable connection. For example, Nokia from http://www.nokia.com/nokia/0,,54691,00.html. PC See Suite : Description . Since PC chute evolution has shifted application evolution from "individual deployment for each phone" to "unified" operating mode, it is now increasingly important to minimize phone-dependent differences. have. This need for integration includes backup and restore functions. This is because there are various variations regarding the locations, amounts, and types of data to be backed up. In addition, there are many variations on telephony devices with different application and feature sets (eg, different multimedia capabilities, with or without cameras), so that the data content may be located in various locations according to various rules. And need to be copied from several locations.

In addition, it is also important to consider that the capability of the device is stored on a removable medium, such as a multimedia card (MMC). For such MMCs, the same backup rules are required to ensure good user experience. If the separate backup / recovery application of the device is used in place of the corresponding application on the PC side performing the same backup function, it is not acceptable or effective that the backup instructions have a different meaning.

Conventional device-side backups, and also backups made from the PC side, have no coordination with each other, and there are no coordinated rules regarding how to manage content and how to manage content, respectively. Instead, each side has its own "exclude" lists that are used to block unnecessary content from being backed up, which unfortunately led to the current difficult situation where backups are not necessarily consistent with each other.

It is known in the art to use the Object Exchange Protocol to provide synchronization and backup services to a server. Infrared, January 3, 2003 Data Associaton ( IrDA ) Object Exchange See Section 8.3 of Protocol , OBEX, Version 1.3. To date, however, no method has been found to use OBEX to allow consistent backups for multiple backup repositories, each backing up different categories of data.

The present invention allows a device to expose rules about how the device is backed up and restored, and the exposed rules are for use by all parties including the device itself. The rules may be used for a backup application of the devices themselves (eg MMC), as well as local communication media, such as universal serial bus (USB), Bluetooth (BT), wireless local area network (WLAN), or It is also valid for PC-side backups used over infrastructure links (according to the Infrared Data Association (IrDA)). The rules are also valid for backup applications using a synchronization server located within the network.

The apparatus of the present invention includes a structured list in Extensible Markup Language (XML), which has strict rules about how data content of a particular major category is handled. An external party, such as a PC, may gain access to the structured list by fetching a first object that describes the capabilities of the device.

The first object is part of the Object Exchange Protocol (OBEX) standard developed by IrDA, and the first object is called an "OBEX capability object". Various extensions to the OBEX capability object may be defined including an extension connected to a location of a backup description XML object (backup.XML). The backup description XML object then provides a structured list describing how the data is backed up from the device. It should be noted that the backup description XML object is given by a Document Type Definition (DTD). The purpose of a document type definition is to define allowed building blocks of an XML document; It defines the document structure by a list of allowed elements. Within the DTD there is a possibility to make additions for additional content or content types. Thus, the structured list can be accessed via normal file transfer.

Therefore, the method and the mobile device of the present invention enable centrally controlled backup functionality, so that the backup devices effectively manage the manner in which data content is backed up (and restored to the mobile device) from the mobile device. Make sure you know The device is arranged to provide an object exchange protocol (OBEX) capability object from the mobile device to the backup device. The device then publishes a backup description XML object to the backup device in response to a link in the extension of the OBEX capability object.

The present invention centrally controls the backup function so that parties such as backup devices can effectively learn how data content is backed up from a mobile device, or how data content is restored to the mobile device. The mobile device exposes (i.e. shows) various rules for backing up or restoring data content to a party, the rules being for the party as well as any backup that interacts with the mobile device. For other parties with the mobile device itself, including devices. The rules are included in a list formatted in XML. If the party is an external party, the mobile device provides the OBEX capability object in response to the party fetching an OBEX capability object. As described above, the OBEX capability object describes the capabilities of the mobile device and is also for use by the external party to access the rules list via the mobile device exposing the rules to the external party.

1 is a diagram showing subsystems and elements required for centralized backup processing.

2 shows a method according to an embodiment of the invention.

3 is a block diagram of an embodiment of the present invention.

A backup description XML object (backup.xml) containing a list of rules is available via a link by an OBEX capability object retrieved from the mobile device by a PC, MMC, or network server. The syntax for the capability object is based on XML, and XML is chosen because of its flexibility and ease that allows elements to be classified and their attributes to be collected. The capability object is flexible enough to allow individual manufacturers to selectively include objects, services and attributes of their interest. In addition, the capability object allows the addition of a user-defined element for specific application or manufacturer requirements.

A backup description XML object includes categories that are backed up, such as user documents, calendars, contacts, bookmarks, and the like. Categories can be added to the backup description by defining a new version of the DTD describing the backup.xml. The categories contain rules that are followed in the case of each backup. The rules are, for example, tags, such as "include" or "exclude" or "includeatomic".

The tags each point to folders and / or files belonging to the respective rules. Tags are of "file" type or "folder" type, meaning that the tag considers a single file or the entire folder structure, so that a single file or an entire folder is "included" in the backup. Or "exclude" from the backup. The tag "includeatomic" has a specific purpose: it is used when a folder contains linked files, some of which need to be treated as a whole. In the case of a restore (as opposed to a backup), the "includeatomic" tag means that the entire folder must be emptied (e.g., among the emptied files) before the content can be replaced by older versions of the files. Some are not replaced).

The following is an example of the information provided by the backup description XML object used to control the backups.

The above approach of backing up mobile device data has great advantages in that it has a consistent function. The XML object may be programmed in advance or modified by the user. In each case, the user experience can be improved by ensuring reliable backups of the user data by backing up user data in a coordinated manner to a plurality of external backup areas.

Referring to FIG. 1, an understanding of the implementation of this embodiment of the present invention may be helpful, and FIG. 1 shows subsystems and elements of centralized backup 100. User 109 accesses an external device 105, such as a personal computer (PC), and also accesses telephone device 107.

The external device 105 has a subsystem application 110 that includes applications running on the external device 105. The backup application receives static information related to the connection phone 107 that is not available to backup.xml 180 regarding rules or to the OBEX capability object. Subsystem platform 120 implements connectivity and protocol-specific parts. Subsystem data handling layer 130 is an abstraction layer of application data; It communicates with the telephone apparatus 107 via the subsystem platform 120 using a protocol implemented by the subsystem platform 120. File system 140 provides a large memory that is used for file storage. The external backup application 150 includes logic for decoding the backup rules published by the telephone apparatus 107. The external backup application 150 has a human interface that allows the user 109 to control the backup / recovery function, and the external backup application 150 is connected to the file system 140. Use the file store provided by

Hereinafter, referring to the telephone apparatus 107, the entity includes a connectivity subsystem 160 that is essentially similar to the subsystem platform 120 on the outside side. Similarly, a device file system 170 in the telephone device is essentially similar to the file system 140 on the external (eg PC) side. backup.xml 180 is an object that contains rules in XML format. The MMC 190 is a multi media card that provides a removable mass memory and extends the device file system 170. Finally, a device backup application 150 corresponds to the external backup application 150 on the external side, which stores the backup in the MMC 190.

2 shows a flowchart showing a method 200 according to the present invention. First, it is determined 210 that the backup device is outside of the mobile terminal (ie, outside of the mobile device). If not, then the mobile device directly exposes 250 a list of backup rules to a backup device in the mobile terminal. In addition, the single list is exposed to external backup devices. Of course, assuming the different requirements and capabilities of each backup device, the list is a single list, but different backup devices may use different parts of the list.

If the question 210 is answered affirmatively, then the backup device draws an OBEX capability object from the mobile device (220). The mobile device then provides the OBEX capability object. Then, in this embodiment, the backup device activates a link in the extension of the OBEX capability object (240), which causes the mobile device to recall the list of backup and / or recovery rules. Expose to a backup device (250).

3 shows a system 300 corresponding to some of the methods just described. The external backup device 310 transmits a fetch signal 330 to the mobile device 320, in particular the signal to means 340 for providing an object exchange protocol (OBEX) capability object. Is received by. The means 340 responds by providing the OBEX capability object 360 via line 350. The external backup device 310 then activates the link located within the extension 370 of the OBEX capability object 360, and as a result, the extension 370 moves the exposure request signal 380 to the move. Device 320, in particular any backup device, transmits to means 390 exposing a list of backup rules. Then, in response, the means 390 sends an exposure signal 395 to the external backup device to provide uniform centralized backup rules to the backup device 310. .

The above figures and the accompanying descriptive discussions relating to the best mode embodiments are illustrative of the invention and are not intended to allow for the strict handling of the invention. Those skilled in the art will understand that the steps and signals of the application are indicative of a general causal relationship that does not exclude various types of intermediate interactions. Consistent with, it will be understood that various different combinations of hardware and software may be implemented in various configurations and sequences, and need not be described in more detail herein.

Claims (27)

Including rules about how data content of the mobile device should be backed up or restored, the rules being included in a list formatted in extensible markup language; And Providing an exchange protocol capability object to a party that has requested to withdraw the capability object from the mobile device; To access the list containing the rules, the capability object is used by the party and by all other backup devices that interact with the mobile device, including the mobile device itself. The method of claim 1, And the list is shown to the party in response to a link from an extension of the capability object. The method of claim 1, And the party is a backup device. The method of claim 2, The list exposed to the party is essentially the same as the list for the detachable backup device detachable from the mobile device. The method of claim 1, The capability object provided by the mobile device is essentially the same for at least one other party. The method of claim 1, And wherein said party is a removable server from said mobile device, a personal computer, or a synchronization server in a network. The method of claim 5, The capability object provided by the mobile device is essentially the same for all other parties. The method of claim 6, And the medium is a multi media card. The method of claim 6, If the party is a personal computer, the backup occurs via a local communication medium. The method of claim 1, The list includes a plurality of categories of the data content, and also has a document type definition structure accommodate additions for additional categories of the data content. Way. The method of claim 10, And the list provides backup rules that are respectively followed in each of the categories. The method of claim 9, The local communication medium is a universal serial bus (USB), a Bluetooth, a wireless local area network, or an infrastructure link. A computer readable medium, A computer readable medium encoded with a software data structure for carrying out the method of claim 1. Means for exposing rules to a party on how the data content of a mobile device should be backed up or restored, the rules being for the party and other parties including the mobile device itself, and Exposing means, wherein the rules are included in a list formatted in extensible markup language; And If the party is an external party that has requested a capability object to be fetched, means for providing the capability object from the mobile device to the party, the capability object describing the capabilities of the mobile device, And providing means by which the capability object is used by the external party to access the list via the exposing means. The method of claim 14, And said exposing means responds to a link from an extension of said capability object. The method of claim 14, The party is a backup device, and the other party is another backup device. The method of claim 14, And said list exposed to said party is essentially the same for a detachable backup device detachable from said mobile device. The method of claim 14, And the capability object provided by the mobile device is essentially the same for at least one other party. The method of claim 14, And the party is a media, personal computer, or network synchronization server detachable from the mobile device. The method of claim 18, The capability object provided by the mobile device is essentially the same for all other parties. The method of claim 19, And the medium is a multi media card. The method of claim 19, If the party is a personal computer, the backup occurs via a local communication medium. The method of claim 14, Wherein the list comprises a plurality of categories relating to the data content, and also has a document type definition structure accommodate additions for additional categories relating to the data content. Device. The method of claim 23. And the list provides backup rules that are respectively followed in each of the categories. The method of claim 22, And wherein said local communication medium is a universal serial bus (USB), a Bluetooth, a wireless local area network, or an infrastructure link. Mobile devices; And An external device configured to provide a fetch signal and also provide an expose request signal in response to receipt of a capability object, The mobile device is configured to provide the capability object to the external device in response to the retrieved signal, The mobile device is further configured to, in response to the exposure request signal, expose to the external device rules about how the data content of the mobile device should be backed up or restored. The method of claim 26, The rules are included in the list, The list includes a plurality of categories of the data content, and also has a document type definition structure accommodate additions for additional categories of the data content. system.

Images