Patent Grant
9053330
The present application relates to security for mobile communication devices, and more particularly to a method and devices for providing secure data backup from a mobile communication device to an external computing device.
Mobile communication devices often allow data such as communication data (e.g., email messages, contacts, and calendar entries) to be backed up to a computer connected to the mobile communication device, for example, via a serial data port. Where the mobile communication device is a corporate or other enterprise device which connects to an enterprise network, the mobile communication device may contain confidential information, proprietary information, or information which is otherwise sensitive to the enterprise or corporation. While existing backup solutions allow a user to protect the backup data, for example by encrypting the data, these solutions are user-implemented controls which do not provide the enterprise with control over how data is backed up or restored.
Thus, there exists a need a backup and restore solution that allows enterprises to control the backup and restoration of data and information from enterprise mobile communication devices.
It will be noted that throughout the drawings similar features are identified by the same reference numerals.
Reference is first made to
The communication system 100 also comprises a wireless network gateway 110 with connects the mobile communication devices 201 to the Internet 112, and through the Internet 112 to a wireless connector system such as an enterprise server 120. The wireless network gateway 110 provides translation and routing services between the enterprise server 120 and the WAN 102, which facilitates communication between the mobile communication devices 201 and other devices (not shown) connected, directly or indirectly, to the wireless network 101. Accordingly, communications sent via the mobile communication devices 201 are transported via the wireless network 101 to the wireless network gateway 110. The wireless gateway 110 forwards the communications to the enterprise server 120 via the Internet. Communications sent from the enterprise server 120 are received by the wireless network gateway 110 and transported via the wireless network 101 to the mobile communication devices 201.
The wireless WAN 102 may be implemented as a packet-based cellular network that includes a number of transceiver base stations 108 (one of which is shown in
The WLAN 104 comprises a wireless network which, in some embodiments, conforms to IEEE 802.11x standards (sometimes referred to as Wi-Fi®) such as, for example, the IEEE 802.11a, 802.11b and/or 802.11g standard. Other communication protocols may be used for the WLAN 104 in other embodiments. The WLAN 104 includes one or more wireless RF Access Points (AP) 114 (one of which is shown in
For the embodiment illustrated in
The enterprise server 120 may be implemented as one or more server modules, and is typically located behind a firewall 114. The enterprise server 120 provides the mobile communication devices 201 with access to an organization's internal network referred to as an enterprise network 124 and provides administrative control and management capabilities over users and mobile communication devices 201 which may connect to the enterprise network 124. The enterprise server 120 is dedicated to managing communications to and from a set of managed mobile communication devices 201 (the enterprise mobile communication devices 201) such that the mobile communication devices 201 are each enabled to exchange electronic messages and other information with the enterprise network 124.
The enterprise server 120 allows the enterprise mobile communication devices 201 to access resources of the enterprise network 124, such as an email server 132 (for example, a Microsoft Exchange™, IBM Lotus Domino™, or Novell GroupWise™ email server) for connecting to an enterprise email system, an Internet/Web server 134 for connecting to the Internet/World Wide Web, and one or more application servers 136 for implementing enterprise applications or for accessing other servers such as an instant messaging (IM) server for connecting to an Instant messaging system. The enterprise server 120 is configured to direct or redirect email messages, Personal Information Management (PIM), instant messaging (IM) and other corporate data received from the wireless network 101 and internally within the enterprise network 124 to be addressed to the mobile communication devices 201.
The enterprise server 120 also provides secure transmission of email, PIM, IM and other corporate or enterprise data transmitted from the enterprise server 120 to enterprise mobile communication devices 201. In some embodiments, communications between the enterprise server 120 and the mobile communication devices 201 are encrypted. In some embodiments, communications are encrypted using a symmetric encryption key implemented using Advanced Encryption Standard (AES) or Triple Data Encryption Standard (Triple DES) encryption. Private encryption keys are generated in a secure, two-way authenticated environment and are used for both encryption and decryption of data. The private encryption key is stored only in the user's mailbox on the email server 132 and on the mobile communication device 201, and can typically be regenerated by the user on mobile communication devices 201. Data sent to the mobile communication devices 201 is encrypted by the enterprise server 120 using the private encryption key retrieved from the user's mailbox. The encrypted data, when received on the mobile communication devices 201, is decrypted using the private encryption key stored in memory. Similarly, data sent to the enterprise server 120 from the mobile communication devices 201 is encrypted using the private encryption key stored in the memory of the mobile communication device 201. The encrypted data, when received on the enterprise server 120, is decrypted using the private encryption key retrieved from the user's mailbox.
In some embodiments, the enterprise server 120 comprises a mobile data delivery module (not shown) which provides connectivity between the wireless WAN 102 and the WLAN 104 and the other connections 106 and mobile communication devices 201 and/or networks connected directly or indirectly to the enterprise server 120. Alternatively, the mobile data delivery module (not shown) may be implemented by a separate server or server application which is connected to the enterprise server 120. In some embodiments, the mobile data delivery module (not shown) provides TCP/IP (transmission control protocol/Internet protocol) and HTTP (hypertext transfer protocol)-based connectivity providing an Internet based service connection. The mobile data delivery module provides access for the mobile communication devices 102 to the Internet 112 and World Wide Web (WWW) and possibly other external communication networks.
The wireless network gateway 110 is adapted to route data packets received from the mobile communication device 201 over the wireless network 101 to destination email and/or Instant messaging server 132, Internet/Web servers 134, and one or more application servers 134 through the mobile data delivery module, and to route data packets received from the servers 132, 134, 136 through the mobile data delivery module over the wireless network 101 to a destination mobile communication device 201. The wireless network gateway 110 forms a connection or bridge between the servers 132, 134, 136 and wireless networks associated with wireless e-mail communication and/or Internet access.
The enterprise network 124 may comprise a private local area network, wide area network, or combinations thereof. Typically, the enterprise network 124 is an intranet of a corporation or other organization. The enterprise server 120 may also provide access to other public or private communication networks such as the Internet 112. A plurality of enterprise computer terminals 117 (one of which is shown in
Using a physical interface or short-range wireless communication interface 106, the user can connected to his or her enterprise computer terminal 117 via the mobile communication device 201. The physical interface comprises one or more of an Ethernet port, Universal Serial Bus (USB) port, Firewire™ (also known as an IEEE 1394 interface) port, or other serial data port on the mobile communication device 201, which when connected via a computer terminal 117 such as a desktop or laptop computer, allows the exchange of information between the enterprise server 120 and the mobile communication devices 201. The short-range wireless communication interface comprises one or more of an infrared (IR) or short-range radio frequency (RF) communication such as Bluetooth® or other wireless personal area network (PAN) interface which allows the mobile communication device 201 to exchange information with the computer terminal 117, and the enterprise server 120 via the computer terminal 117.
It will be appreciated that the above-described communication system is provided for the purpose of illustration only, and that the above-described communication system comprises one possible communication network configuration of a multitude of possible configurations for use with the mobile communication devices 201. Suitable variations of the communication system will be understood to a person of skill in the art and are intended to fall within the scope of the present application.
Reference is next made to
The mobile communication device 201 includes a wireless communication subsystem 211 for exchanging radio frequency signals with the wireless network 101. The communication subsystem 211 includes a receiver 214, a transmitter 216, and associated components, such as one or more antenna elements 218 and 220, local oscillators (LOs) 222, and a processing module such as a digital signal processor (DSP) 224. The antenna elements 218 and 220 may be embedded or internal to the mobile communication device 201. As will be apparent to those skilled in the field of communication, the particular design of the communication subsystem 221 depends on the wireless network 101 in which mobile communication device 201 is intended to operate.
The mobile communication device 201 may communicate with any one of a plurality of fixed transceiver base stations 108 of the wireless network 101 within its geographic coverage area. The mobile communication device 201 may send and receive communication signals over the wireless network 101 after the required network registration or activation procedures have been completed. Signals received by the antenna 218 through the wireless network 101 are input to the receiver 214, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, etc., as well as analog-to-digital (A/D) conversion. A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in the DSP 224. In a similar manner, signals to be transmitted are processed, including modulation and encoding, for example, by the DSP 224. These DSP-processed signals are input to the transmitter 216 for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification, and transmission to the wireless network 101 via the antenna 220. The DSP 224 not only processes communication signals, but also provides for receiver and transmitter control. For example, the gains applied to communication signals in the receiver 214 and the transmitter 216 may be adaptively controlled through automatic gain control algorithms implemented in the DSP 224.
The mobile communication device 201 includes a microprocessor 240 which controls the overall operation of the mobile communication device 201. The microprocessor 240 interacts with communication subsystem 211 which performs communication functions. The microprocessor 240 also interacts with additional device subsystems such as a display 242, flash memory 244, random access memory (RAM) 246, read only memory (ROM) 248, auxiliary input/output (I/O) subsystems 250, a data port 252 such as serial data port (for example, a Universal Serial Bus (USB) data port), a keyboard or keypad 254, a speaker 256, microphone 258, a clickable thumbwheel (trackwheel) or trackball 260, a short-range communication subsystem 262, and other device subsystems generally designated as 264.
Some of the subsystems shown in
Operating system 254 software used by the microprocessor 240 is preferably stored in a persistent store such as the flash memory 244, which may alternatively be the ROM 248 or similar storage element. Those skilled in the art will appreciate that the operating system 254, specific device applications 258, or parts thereof, may be temporarily loaded into a volatile store such as the RAM 246.
In some embodiments, the mobile communication device 201 also includes a removable memory card 230 (typical comprising flash memory) and a memory card interface 232. Network access to the WAN 102, and possibly the WLAN 104, is typically associated with a subscriber or user of the mobile communication device 201 via the memory card 230, which may be a Subscriber Identity Module (SIM) card for use in a GSM network or other type of memory card for use in the relevant wireless network type. The memory card 130 is inserted in or connected to the memory card interface 232 of the mobile communication device 201 in order to operate in conjunction with the wireless network 101.
The mobile communication device 201 stores data 220 in an erasable persistent memory, which in one example embodiment is the flash memory 244. In various embodiments, the data 220 includes service data 222 comprising information required by the mobile communication device 201 to establish and maintain communication with the wireless communication network 200 (wireless network service data) and the wireless gateway 210 (gateway service data). The data 220 may also include other data 224, user application data 226 such as email messages, address book and contact information, calendar and schedule information, notepad documents, image files, and other commonly stored user information stored on the mobile communication device 201 by its user. The data 220 may also include data required for the communication layers managed by the enterprise server 120 and servers 132, 134, 136. The data 220 may includes critical data that the user of mobile communication device 201 or the user's associated enterprise does not want to be accessed by an unauthorized party. Some of the data 220 may be stored on the memory card 230. The data 220 stored in the persistent memory (e.g. flash memory 244) of the mobile communication device 201 may be organized, at least partially, into a number of databases each containing data items of the same data type or associated with the same application. For example, email messages, contact records, and task items may be stored in individual databases within the device memory.
The serial data port 252 may be used in a PDA-type communication device for synchronization with a user's computer terminal 117. The serial data port 252 is a Universal Serial Bus (USB) port in some embodiments. The serial data port 252 enables a user to set preferences through an external device or software application and extends the capabilities of the mobile communication device 201 by providing for information or software downloads to the mobile communication device 201 other than through the wireless network 101. The alternate download path may, for example, be used to load an encryption key onto the mobile communication device 201 through a direct, reliable and trusted connection to thereby provide secure device communication.
The mobile communication device 201 also includes a battery 238 as a power source, which is typically one or more rechargeable batteries that may be charged, for example, through charging circuitry coupled to a battery interface such as the serial data port 252. The battery 238 provides electrical power to at least some of the electrical circuitry in the mobile communication device 201, and the battery interface 236 provides a mechanical and electrical connection for the battery 238. The battery interface 236 is coupled to a regulator (not shown) which provides power V+ to the circuitry of the mobile communication device 201.
The short-range communication subsystem 262 is an additional optional component which provides for communication between the mobile communication device 201 and different systems or devices, which need not necessarily be similar devices. For example, the subsystem 262 may include an infrared device and associated circuits and components, or a wireless bus protocol compliant communication mechanism such as a Bluetooth® communication module to provide for communication with similarly-enabled systems and devices (Bluetooth® is a registered trademark of Bluetooth SIG, Inc.).
The microprocessor 240, in addition to its operating system functions, enables execution of software applications on the mobile communication device 201. A predetermined set of applications that control basic device operations, including data and possibly voice communication applications will normally be installed on the mobile communication device 201 during or after manufacture. Additional applications may also be loaded onto the mobile communication device 201 through the wireless network 101, the auxiliary I/O subsystem 250, the serial port 252, the short-range communication subsystem 262, or other suitable subsystem 264, and installed by a user in the RAM 246 or a non-volatile store such as the ROM 248 for execution by the microprocessor 240. Such flexibility in application installation increases the functionality of the mobile communication device 201 and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using the mobile communication device 201.
The mobile communication device 201 may include a personal information manager (PIM) application having the ability to organize and manage data items relating to a user such as, but not limited to, instant messaging, email, calendar events, voice mails, appointments, and task items. One or more memory stores are available on the mobile communication device 201 and the memory card 230 to facilitate storage of PIM data items and other information. The PIM application has the ability to send and receive data items via the wireless network 101. In some example embodiments, PIM data items are seamlessly combined, synchronized, and updated via the wireless network 101, with the user's corresponding data items stored and/or associated with the user's computer terminal 117, thereby creating a mirrored host computer on the mobile communication device 201 with respect to these data items. This is advantageous where the host computer system is the user's office computer system.
In a data communication mode, a received data signal representing information such as a text message, an email message, or Web page download will be processed by the communication subsystem 211 and input to the microprocessor 240. The microprocessor 240 will further process the signal for output to the display 242 or alternatively to the auxiliary I/O device 250. A user of the mobile communication device 201 may also compose data items, such as email messages, for example, using the keypad 254 and/or the clickable thumbwheel or trackball 260 in conjunction with the display 242 and possibly the auxiliary I/O device 250. The keypad 254 maybe either a complete alphanumeric keypad or telephone-type keypad. These composed items may be transmitted through the communication subsystem 211 over the wireless network 101.
In a voice communication mode, the overall operation of the mobile communication device 201 is similar, except that the received signals would be output to the speaker 256 and signals for transmission would be generated by a transducer such as the microphone 258. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on the mobile communication device 201. Although voice or audio signal output is typically accomplished primarily through the speaker 256, the display 242 may also be used to provide an indication of the identity of a calling party, duration of a voice call, or other voice call related information.
The enterprise server 120 is configured to enforce IT (information technology) policies on the mobile communication devices 201. IT policies are rules which govern the functionality of the mobile communication devices 201. The enterprise server 120 may periodically transmit IT policy messages to enforce, modify, or terminate IT policies on the connected computing devices. The enterprise server 120 transmits the IT policy messages through the wireless network 101 to its managed mobile communication devices 201 or via the physical interface (e.g., serial data port 252 such as a USB port) or short-range wireless communication interface (e.g., Bluetooth® connection) 106 when connected to the user's enterprise computer terminal 117. The IT policy messages may be security policies (such as data protection security policies), information and/or security settings regarding these policies, and/or commands to be executed by the mobile communication devices 201. The IT policies can be set by an IT administrator of the enterprise network 124 by sending an appropriate IT policy message to the mobile communication devices 201 managed by the enterprise server 120. The periodic transmission of IT policy messages from the enterprise server 120 to the managed mobile communication devices 201 assists in ensuring, among other things, that each of the mobile communication devices 201 is kept up to date with the latest IT policy. The content and frequency of IT policy messages may be set by the IT administrator. In at least some embodiments, the enterprise server 120 generates a private and public key pair for each mobile communication device 201 to authenticate the IT policy messages. The IT policy private key is stored in the enterprise server 120. The IT policy public key is stored on the mobile communication device 201. The enterprise server 120 digitally signs all IT policy messages using the IT policy public key which uses the IT policy public key to authenticate the digital signature in received IT policy messages.
In one embodiment, elements of the backup and restore processes described below are implemented via an IT policy message which is pushed out to the mobile communication devices 201. Using IT policy messages the mobile communication devices 201 can be instructed to enforce, modify, or terminate aspects of the backup and restore processes. In particular, IT policy messages can be used to instruct the mobile communication device 201 to encrypt data using an encryption key (which may be included in the IT policy message) prior to sending data to a backup application on an external computing device. Similarly, IT policy messages can be used to instruct the mobile communication device 201 to decrypt backup data received from a restore application on an external computing device using a decryption key. Using IT policy messages in this manner allows secure backup and restore functionality to be added to mobile communication devices 201 already managed by the enterprise server 120, and in new mobile communication devices 201 which are added to the list of devices managed by the enterprise server 120 (including new users, device replacements or upgrades, or device switches). In some embodiments, the IT administrator has the option of setting the IT policy globally for all mobile communication devices 201 managed by the enterprise server 120, or for groups or classes of mobile communication devices 201 managed by the enterprise server 120, or for one or more individual communication devices managed by the enterprise server 120.
Referring now to
In some embodiments, the encryption key 272 is stored in protected memory 270 of the mobile communication device 201, for example, in flash memory 244. The protected memory 270 is protected from user access, device wipes (for example, device wipes initiated by the user, or resulting from device replacements or switches, or from triggered data security protections) which erase data stored on the mobile communication device 201, or both. Access to the protected memory 270, and in particular the encryption key and decryption keys, is also restricted to authorized applications, and typically authorized applications are restricted to authorized uses. Storage of the encryption key 272 in protected memory 270 prevents the user of the mobile communication device 201 from accessing the encryption key 272 and tampering with the encryption key 272 in an attempt to modify or delete the key, or otherwise prevent or alter the encryption of data during the backup process 300. Methods of implementing memory protection are known in the art and will not be described.
Generally, the encryption key 272 (and decryption key) may only be added, updated, or removed via an IT policy message sent via the enterprise server 120. In this way, encryption and decryption key control authority is restricted to the enterprise server 120 and the IT administrator. Typically, the encryption key 272 is only accessible by the mobile communication device 201 when the access request is received from an authorized program application such as the backup application. Even in such cases, access is typically limited to authorized purposes such as encrypting data items to be sent to an external computing device in response to a request for the items during a backup operation. Likewise, the decryption key is typically only accessible by the mobile communication device 201 when the access request is received from an authorized program application such as the restore application, and typically only for authorized purposes such as decrypting encrypted data items received from an external computing device during a restore operation. Alternatively, other forms of protecting the encryption and decryption keys may be used. The IT policy messages 276 and/or rules contained within the IT policy messages may be stored in the memory (e.g., flash memory 244) of the mobile communication device 201. In addition, in some embodiments IT policy messages 276 and/or rules contained within the policy messages may be stored in the protected memory 270 of the mobile communication device 201.
In some embodiments, the encryption key 272 is a symmetric key used both as an encryption key for encrypting data during a backup operation, and as a decryption key for decrypting backup data during a restore operation. The encryption key 272 is an AES (Advanced Encryption Standard) key in some embodiments, and a Triple Data Encryption Standard (Triple DES) key in other embodiments. Other types of suitable symmetric keys will be appreciated by persons skilled in the art. Methods for establishing symmetric encryption keys 272 on the enterprise server 120 and mobile communication device 201 are known in the art and will not be described in detail. Generally, the encryption key 272 may be generated by the enterprise server 120 which maintains a copy of the encryption key 272, and transmits a copy of the encryption key 272 to the mobile communication device 201. In some embodiments, the encryption key 272 may be transmitted in an IT policy message sent by the enterprise server 120 to the mobile communication device 201.
In other embodiments, the encryption key 272 is an asymmetric key which is part of a public-private key pair. In asymmetric key implementations, the encryption key 272 is a public key stored locally on the mobile communication device 201 and on the enterprise server 120. Unlike the symmetric encryption key 272 described above, a separate, private decryption key 274 is required to decrypt backup data on restore operations. Both the public encryption key 272 and private decryption key 274 are stored locally on the mobile communication device 201 in persistent memory, for example, in the flash memory 244, and on the enterprise server 120. In some embodiments, the public encryption key 272 and private decryption key 274 are stored in protected memory 270 of the mobile communication device 201, as described above. Methods for establishing asymmetric private-public key pairs between the enterprise server 120 and mobile communication device 201 for encryption and decryption are known in the art and will not be described in detail. Generally, the public encryption key 272 and private decryption key 274 may be generated by the enterprise server 120 which maintains a copy of the encryption key 272 and private decryption key 274, and transmits the encryption key 272 and decryption key 274 to the mobile communication device 201. In some embodiments, the public encryption key 272 and private decryption key 274 may be transmitted in an IT policy message sent by the enterprise server 120 to the mobile communication device 201.
In the first step 302, the mobile communication device 201 is connected to the computing device. The mobile communication device 201 may be connected to the computing device via a data port of the computing device and the serial data port 252 of the mobile communication device 201, or via a short-range wireless communication interface (for example, such as Bluetooth®) between the computing device and the mobile communication device 201. The computing device is provided with a backup program or utility, typically as part of a combined backup and restore program. The backup and restore program is configured for backing up data from the mobile communication device 201 in the form of a backup file, and for restoring data contained in local backup files to the mobile communication device 201. In some embodiments, the backup and restore program or utility application is provided as part of a desktop management software suite for managing data and connections between the external computing device and the mobile communication device 201.
In some embodiments, the backup file is an IPD file or a backup file compatible with the IPD file format. The IPD file format is known in the art and is described in the Blackberry Developer Journal, Volume 3, Issue No. 1, January 2006, published by Research in Motion Limited (http://na.blackberry.com/eng/developers/resources/journals/jan 2006/BlackBerryDeveloperJournal-0301.pdf), which is incorporated herein by reference. In some embodiments, the backup file is organized into a number of databases each containing data items of the same data type. For example, email messages, contact records, and task items may be stored in individual databases within the backup file.
In some embodiments, after launching the backup and restore program, the user of the mobile communication device 201 may be given an option of selecting the data items (or databases) to be backed up, for example using a selection window or menu presented in a graphical user interface (GUI) provided by the backup and restore program.
Next, in step 304 a request to backup one or more data entries or data items stored on the mobile communication device 201 is received. The request is typically made by user input received via the GUI of the backup and restore program running on the external computing device. Alternatively, the request may be received from the mobile communication device 201.
In some embodiments, the data on the mobile communication device 201 may be organized into a number of databases each containing data items of the same data type. In some embodiments, the GUI of the backup and restore program may present the data stored in mobile communication device 201 in this manner for easier selection by the user. In these embodiments, the request from the user may be a request to backup one or more databases selected by the user, a request to backup all databases on the mobile communication device, a request to backup up one or more data items in a database selected by the user, or a request to backup all data items on the mobile communication device 201.
The data items available for backup may comprise user application data 226, service data 222, and other data 224. In some embodiments, the user application data 226 may comprise: email messages, instant messages, address book and contact information, contact records, Short Messaging Service (SMS) messages, text messages, PIN messages, calendar and schedule information such as calendar events and appointments/meetings, voicemail messages, notepad documents, and combinations thereof.
It will be appreciated that the particular databases resident on the mobile communication device 201 depends on the particular applications and features provided by the particular mobile communication device 201, and that the content of the various databases depends on the data stored in association with the particular applications and features. In one example embodiment, the device memory, for example the flash memory 244, comprises databases of data items for the following: Address Book; Address Book Options; Alarm Options; Application Permissions; Attachment Data; Attachment Options; Auto Text; Device Messenger; Bluetooth® Options; Browser Bookmarks; Browser Channels; Browser Data Cache; Browser Folders; Browser Messages; Browser Options; Browser Push Options; Browser Uniform Resource Locators (URLs); Calendar; Calendar Options; Categories; Certificate Options; Content Store; Custom Words Collection; Default Service Selector; Device Options; Email Filters; Email Settings; Enterprise Configuration; File Explorer Options; Firewall Options; Folder identifiers (IDs); Folders; Handheld Agent; Handheld Configuration Handheld key store; Input Learning Data; Input Method Switcher Option; Key Store Options; Key Store Manager; Map Locations; MemoPad Options; Memory Cleaner Options; Memos; Message List Options; Messages; Multimedia Messaging Service (MMS) Messages; MMS Options; Options; Passwords; Password Options; PGP Key Store; Phone Call Logs; Phone Hotlist; Phone Options; Personal identification number (PIN) Messages; Policy; Profiles; Profile Options; Purged Messages; Quick Contacts; Random Pool; Recipient Cache; Ribbon Bar Positions; Rights Management Services (RMS) Databases; Saved Email Messages; Searches; Secure Email Decision Maker; Service Book; Setup Wizard Options; Smart Card Options; Short Message Service (SMS) Messages; Suretype® Options; Tasks; Tasks Options; Time Zones; Transport Layer Security (TLS) Options; Trusted Key Store; Voice Activated Dialing Options; Wireless Application Protocol (WAP) Push Messages; and Wireless Transport Layer Security (WTLS) Options.
In some embodiments, a step of determining which data items and/or databases are available for backup is performed, typically by the mobile communication device 201. It will also be appreciated that particular data items and/or databases on the mobile communication device 201 may be not be subject to the backup process. In other words, not all the data on the mobile communication device 201 may be backed up due to controls placed on the data, for example, by IT policies. In this way, the IT administrator may create one or more IT policies which limit the data items and/or databases that may be backed up, and then pushes the IT policies out to enterprise mobile communication devices 201. In some embodiments, the IT administrator has the option of setting the IT policy globally for all mobile communication devices 201 managed by the enterprise server 120, restricting the IT policy to groups or classes of mobile communication devices 201 managed by the enterprise server 120, or restricting the IT policy to one or more individual communication devices managed by the enterprise server 120.
Where backup controls limiting the data items and/or databases which may be backed up are implemented, and the user is given the option of selecting the data items (or databases) to be backed up, the protected data items/databases will not be available for selection. In these embodiments, the step of determining which data items and/or databases are available for backup is performed prior to presenting the selection menu to the user, and prior to the step 304 of receiving the backup request. In other embodiments, the determining step may occur after receiving the backup request in step 304, for example, in embodiments where the user does not have the option of selecting the data for backup.
Next, in step 306 the backup file is generated on the computing device. At this stage, the backup file is empty but contains the basic structure and conforms to the backup file format such as, for example, the IPD file format.
Next, in step 308 the mobile communication device 201 encrypts a data item selected for backup using the encryption key 272 stored in memory 244. Optionally, the mobile communication device 201 may determine if the selected data item or database is subject to encryption, for example, by consulting the relevant IT policies stored in the memory of the mobile communication device 201, for example, in flash memory 244. If the IT policies do not specify that the data item or database is to be encrypted or specify that the data item or database is not to be encrypted, the operations 300 proceed to step 314 where a check is performed to determine if there are more data items to be backed up.
Next, in step 310 the encrypted data item is transferred to the computer device from the mobile communication device 201.
Next, in step 312 the encrypted data item is received on the computing device from the mobile communication device 201 and added to the backup file.
Next, if there are more data items to be backed up (step 314), the backup operations 300 loop back to step 308 where the next data item is encrypted. Operations 300 proceed until all selected items are backed up. If there are no more data items to be backed up (step 314), the backup file is stored in persistent memory of the external computing device and the operations 300 end.
Typically, individual data items are encrypted, transferred to the computing device, and added to the backup file in series until all data items have been backed up. However, in some embodiments the data items of each database may be encrypted on the mobile communication device 201, then transferred to the computing device en masse, and added to the backup file. In yet other embodiments, all data items may be encrypted on the mobile communication device 201, then transferred to the computing device en masse, and added to the backup file. Though not described above, the backup program may organize the encrypted data items within the backup file, for example, into the databases described above.
In the above-described embodiment, the encryption key 272 is associated with a particular enterprise user or enterprise mobile communication device 201. Depending on the particular use case scenario, an enterprise user may have more than one enterprise mobile communication device 201 in which case each device would have the same encryption and decryption keys associated with the same user name/ID in the enterprise network 124, and each device would have the encryption and decryption keys stored in memory on activation of each enterprise mobile communication device 201 on the enterprise server 120, or upon enforcement of the IT policy to implement the secure backup and restore operations described in the present application (if the enterprise device has already been activated). In alternative embodiments, separate keys may be used for each enterprise user or enterprise mobile communication device 201 for each database. The implementation of a per user/database key may increase security in that an attacker would have to break each decryption key in order to access the underlying data stored in each database of the backup file.
It will be appreciated that any application running on the external computing device where the backup file is stored, i.e. the user's enterprise computer terminal 117 or home computer, cannot access the data within the backup file because it is encrypted and the external computing device does not have access to the encryption or decryption keys required to decrypt the data within the backup file. If the user of the enterprise mobile communication device 201 were to attempt to restore the data contained in the backup file from the external computing device to another mobile communication device 201 which was not been activated on the enterprise server 120 (i.e., is not an enterprise device), the restore operation will fail since the non-enterprise mobile communication device does not have the required decryption keys.
Referring now to
In the first step 402, the mobile communication device 201 is connected to the computing device (i.e., the user's enterprise computer terminal or home computer terminal) where the backup file, for example an IPD file or backup file compatible with the IPD file format, is stored.
Next, in step 404, the computing device receives a request to restore the backup file comprising one or more encrypted data items to the mobile communication device 201. The restore request is typically made by the user using the backup and restore program on the external computing device, however the request may be received from the mobile communication device 201. Optionally, the mobile communication device 201 may be configured to perform a check to determine if the backup file contains encrypted data, and if the backup file does not contact encrypted data, the mobile communication device 201 will not accept the databases. This optional step may be performed on database-by-database basis, rather than as a preliminary check of the backup file. The optional check may be implemented via the IT policy which is specified by the enterprise server 120.
Next, in step 408, an encrypted data item is extracted from the backup file on the computing device and transferred to the mobile communication device 201.
Next, in step 410, the encrypted data item is decrypted using the decryption key 274. If there is no decryption key 274 stored in the memory of the mobile communication device 201, or if the decryption key 274 does not match, the decryption operation fails and, typically, the restore operation 400 ends.
Next, in step 412, the decrypted data item is stored in memory, for example flash memory 244, of the mobile communication device 201. The mobile communication device 201 may also organize the stored data items, for example, into the databases described above. This organization step may occur at this time, or after all data items have been restored.
Next, if there are more data items to be restored (step 414), the restore operations 400 loop back to step 408 where the next data item is transferred to the mobile communication device 201. Operations 400 proceed until all items in the backup file have been restored to the mobile communication device 201. If there are no more data items to be restored (step 414), the operations 400 end.
Referring now to
Next, in optional step 503, the data items and/or databases which are available for backup is determined. Typically, this step is performed by the mobile communication device 201 by consulting the relevant IT policies stored in the memory of the mobile communication device 201, for example, in flash memory 244.
In some embodiments, after launching the backup and restore program, the user of the mobile communication device 201 may be given an option of selecting the data items (or databases) to be backed up, for example using a selection window or menu presented in the GUI provided by the backup and restore program.
Next, in step 504 a request is received to backup one or more databases stored on the mobile communication device 201 is received, where each database comprises one or more data items of a particular data type. The request is typically made by user input received via the GUI of the backup and restore program running on the external computing device. Alternatively, the request may be received from the mobile communication device 201.
Next, in step 506 the backup file is generated on the computing device.
Next, in step 507 a database for backup is selected. Next, in optional step 508, the mobile communication device 201 selects the encryption key 272 associated with the selected database. In some embodiments, only some of the databases may be encrypted and therefore only some of the databases may have an associated encryption key 272. Optionally, the mobile communication device 201 may determine if the selected database is subject to encryption, for example, by consulting the relevant IT policies stored in the memory of the mobile communication device 201, for example, in flash memory 244. If the IT policies do not specify that the database is to be encrypted or specify that the data database is not to be encrypted, the operations 500 proceed to step 516 where a check is performed to determine if there are more databases to be backed up.
Next, in step 509 the mobile communication device 201 encrypts the first data item in the database for backup using the selected encryption key 272 for the selected database.
Next, in step 510 the encrypted data item is transferred to the external computing device from the mobile communication device 201.
Next, in step 512 the encrypted data item is received on the computing device from the mobile communication device 201 and added to the backup file.
Next, if there are more data items to be backed up (step 514), the backup operations 500 loop back to step 508 where the next data item is encrypted. The operations 500 proceed until all the data items in all selected database are backed up. If there are no more data items to be backed up (step 514), the operations proceed to step 516 where a check is performed to see if there are more databases to be backed up. If there are more databases to be backed up, the backup operations 500 loop back to step 507 where the next database is selected. If there are no more databases to be backed up (step 514), the backup file is stored in persistent memory of the external computing device and the operations 500 end.
The backup operations described in the present application provide the IT administrator with some flexibility regarding the controls to be placed on device data during a back up operation. The IT administrator may optionally control, via IT policy messages sent from the enterprise server 120, which databases can be backed up, and optionally which databases which are made available to the user for backup are encrypted, and optionally what encryption key (and decryption key) is to be applied to each database. For example, the IT administrator may be concerned about controlling the backup of corporate (enterprise) email and voicemail and so may prevent the backup of this data or allow the backup of this data but encrypt it. However, the IT administrator may not be concerned about controlling the backup of Game databases and so may place lesser or controls on these databases (i.e., allow backup but do not apply encryption).
Referring now to
In the first step 602, the mobile communication device 201 is connected to the computing device (i.e., the user's enterprise computer terminal or home computer terminal) where the backup file, for example an IPD file or backup file compatible with the IPD file format, is stored.
Next, in step 604, the computing device receives a request to restore the backup file comprising one or more databases each comprising one or more encrypted data items to the mobile communication device 201.
Next, in step 607, a database to be restored is selected. Next, in optional step 608, the mobile communication device 201 determines if the selected database contains encrypted data items. If database does not contact encrypted data items, the mobile communication device 201 will not accept the databases and operation proceed to step 616, where it is determined if there are other database to restored (alternatively, the restore operations 600 could end if any database does not contain encrypted data times). If there are no other databases to restore, the operations 600 end. If there are other databases to restore, the operations 600 proceed back to step 607 where the next database is selected. If the database contains encrypted data items, the operation 600 proceed to step 609 where the encrypted data item is extracted from the database and transferred to the mobile communication device 201. Alternatively, in other embodiments the mobile communication device 201 will accept the unencrypted databases, for example, where the backup process 500 does not encrypt all backed up databases.
Next, in step 610, the encrypted data item is decrypted using the decryption key 274. If there is no decryption key 274 stored in the memory of the mobile communication device 201, or if the decryption key 274 does not match, the decryption operation fails and, typically, the restore operation 600 ends.
Next, in step 612, the decrypted data item is stored in memory, for example flash memory 244, of the mobile communication device 201. The mobile communication device 201 may also organize the stored data items, for example, into the databases described above. This organization step may occur at this time, or after all data items have been restored.
Next, if there are more data items to be restored (step 614), the restore operations 600 loop back to step 609 where the next data item is transferred to the mobile communication device 201. If there are no more data items to be restored in the database, the operations 600 proceed to step 616, where it is determined if there are other database to be restored. If there are no other databases to restore, the operations 600 end. If there are other databases to restore, the operations 600 proceed back to step 607 where the next database is selected.
The backup and restore processes described above allow an enterprise to place restrictions on how data which is backed up from an enterprise mobile communication device 201 may be used. Using the backup processes 300, 500 and the restore processes 400, 600, backup data can only be restored to an enterprise mobile communication device 201 that has been activated and authorized by the enterprise server 120. As a result, a user cannot backup data from an enterprise mobile communication device 201 and restore the data to a personal mobile communication device 201 since the personal device will not have the required decryption key. In addition, because the backup data is encrypted, the use of other applications on the external computing device which may otherwise be able to read the backup file and the backup data contained therein is hindered or prevented. Thus, the backup processes 300, 500 and the restore processes 400, 600 assist in reducing or preventing the unauthorized use of data from an enterprise mobile communication device 201 by a “rogue user”.
It will be appreciated that while the backup processes 300, 500 and the restore processes 400, 600 have been described and shown as occurring in a particular order, persons skilled in the art will understand that variations are possible. For example, the step of generating the backup file need not be performed prior to the step of adding the encrypted data item to the backup file. Furthermore, the step of storing the backup file in persistent memory of the external computing device may occur after each encrypted data item is added (i.e., incremental updating of the stored file may occur), and that prior to storing the backup file in persistent memory, the backup file may be temporally stored in volatile memory of the external computing device such as RAM.
Although reference has been made to certain wireless network types and standards for the purpose of illustration, such as the IEEE 802.11x standards, it will be appreciated that the present application is intended to cover all further revisions, supplements, additions and replacements to the referenced network types and standards, whether or not explicitly described above.
The present application describes a system and method for providing secure data backup from a mobile communication device to an external computing device, and for restoring data from the external computing device. Data being backed up is encrypted with a local encryption key stored on the mobile communication device before being transferred to the external computing device where the encrypted data is included in a backup file generated by a backup application running on the external computing device. The local encryption key is securely provided to the mobile communication device by an enterprise server which manages its communications. To restore data, a local decryption key is used (which may be same as the encryption key if a symmetric key protocol is implemented). The decryption key is securely provided o the mobile communication device by the enterprise server. During a restore operation, encrypted data is transferred from the external computing device to the mobile communication device where it is decrypted using the local decryption key. If the mobile communication device does not have a decryption key or if the key does not match, the restore operation fails as the data cannot be decrypted. Thus, data restore operations are limited to a user's enterprise mobile communication devices.
In accordance with a first example embodiment of the present application, there is provided a method of backing up data from a mobile communication device to an external computing device, the mobile communication device being connected to the external computing device for exchanging data with each other, the method comprising: receiving a request to backup one or more data items in a plurality of data items stored on the mobile communication device; encrypting a data item using an encryption key stored in memory of the mobile communication device; transferring the encrypted data item to the external computing device; and storing a backup file comprising the encrypted data item in the memory of the external computing device.
In accordance with another example embodiment of the present application, there is provided a method of restoring backup data to a mobile communication device from an external computing device, the mobile communication device being connected to the external computing device for exchanging data with each other, the method comprising: receiving a request to restore data from a backup file to the mobile communication device, the backup file comprising one or more encrypted data items; transferring an encrypted data item to the mobile communication device from the external computing device; and decrypting the data item using a decryption key stored in the memory of the mobile communication device.
In accordance with a further example embodiment of the present application, there is provided a mobile communication device, comprising: a processor for controlling the operation of the mobile communication device; a data interface coupled to the processor configured for communicating with external computing devices and for exchanging data therewith; a memory coupled to the processor and having data and instructions stored thereon, the memory having stored thereon an encryption key and a plurality of data items of user application data and service data, the data and instructions configuring the processor to: in response to receiving a request to transfer data items received from a backup application on an external computing device received via the data interface, encrypt the data items with the encryption key, and transmit the encrypted data items to the external computing device via the data interface.
In accordance with yet a further example embodiment of the present application, there is provided a computing device, comprising: a processor for controlling the operation of the computing device; a user input device coupled to the processor and configured for receiving user inputs; a data interface coupled to the processor and configured for communicating with a mobile communication device and for exchanging data therewith; a memory coupled to the processor and having data and instructions stored thereon, the data and instructions configuring the processor to: receive a request from a user to backup one or more data items in a plurality of data items stored on the mobile communication device; request the one or more data items from the mobile communication device; receive encrypted data items from the mobile communication device via the data interface in response to the request; and store the encrypted data items in a backup file in the memory.
In accordance with yet a further example embodiment of the present application, there is provided a method for implementing secure data backup from a mobile communication device to an external computing device, the method comprising: receiving a policy message on the mobile communication device, the policy message comprising a rule for the mobile communication device to encrypt at least some of the data items in response to a request to transfer data items received during a backup to an external computing device before transmitting the items to the external computing device; and receiving an encryption key for encrypting data items during the backup of data items on the mobile communication device.
In accordance with yet a further example embodiment of the present application, there is provided a method of backing up data from a mobile communication device to an external computing device, the mobile communication device being connected to the external computing device for exchanging data with each other, the data comprising one or more databases each comprising one or more data items, the method comprising: determining which databases on the mobile communication device are available for backup; receiving a request to backup selected databases stored on the mobile communication device; for each selected database, determining if the selected database is to be encrypted; if the selected database is to be encrypted, encrypting the selected database using an encryption key stored in memory of the mobile communication device, and transferring the encrypted database to the external computing device; if the database is not to be encrypted, transferring the unencrypted database to the external computing device; storing a backup file comprising the selected databases in the memory of the external computing device. In some embodiments, the method further comprises, for each selected database, selecting an encryption key for the database, the encryption key being selected from a plurality of encryption keys stored in memory of the mobile communication device. In some embodiments, request includes an identification of the selected databases for backup.
In accordance with yet a further example embodiment of the present application, there is provided a method of restoring backup data to a mobile communication device from an external computing device, the mobile communication device being connected to the external computing device for exchanging data with each other, the method comprising: receiving a request to restore data from a backup file to the mobile communication device, the backup file comprising one or more databases; for each database, determining if the database is encrypted, and if the database is encrypted, transferring the database to the mobile communication device from the external computing device and decrypting the database using a decryption key stored in memory of the mobile communication device and storing the decrypting database in the memory of the mobile communication device. If the database is not encrypted, in some embodiments the unencrypted database is transferred to the mobile communication device and stored in the memory of the mobile communication device. In other embodiments, if the database is not encrypted, the unencrypted database is not transferred to the mobile communication device. In some embodiments, the method further comprises, for each database, selecting a decryption key for the database, the decryption key being selected from a plurality of decryption keys stored in memory of the mobile communication device, wherein each data item in the database is decrypted using the selected decryption key.
In accordance with further embodiments of the present application, there is provided an apparatus such as a computing device or data processing system, a method for adapting this system, articles of manufacture such as a machine or computer readable medium having program instructions recorded thereon for practising the method of the application, as well as a computer data signal having program instructions recorded therein for practising the method of the application.
In accordance with an example embodiment of the present application, there is provided a method of backing up data from a mobile communication device to an external computing device, the mobile communication device being in communication with the external computing device, the method comprising: receiving from an enterprise server an encryption key for encrypting data items during the backup of data items on the mobile communication device, the encryption key being alterable only via the enterprise server; storing the encryption key in a protected memory of the mobile communication device, the protected memory being protected from access by unauthorized applications; the mobile communication device receiving a request from an authorized application to backup one or more data items stored on the mobile communication device to the external computing device, the external computing device being physically separate from the enterprise server; the mobile communication device encrypting a data item using the encryption key stored in the protected memory of the mobile communication device; and transferring the encrypted data item from the mobile communication device to the external computing device for storage by the external computing device.
In accordance with an example embodiment of the present application, there is provided a method of restoring backup data to a mobile communication device from an external computing device, the mobile communication device being in communication with the external computing device, the method comprising: receiving from an enterprise server a decryption key for decrypting encrypted data items during the restoration of encrypted data items on the mobile communication device, the decryption key being alterable only via the enterprise server; storing the decryption key in a protected memory of the mobile communication device, the protected memory being protected from access by unauthorized applications; receiving a request from an authorized application to restore one or more encrypted data items stored in the external computing device to the mobile communication device, the external computing device being physically separate from the enterprise server; transferring an encrypted data item to the mobile communication device from the external computing device; and decrypting the encrypted data item using the decryption key stored in the protected memory of the mobile communication device.
In accordance with an example embodiment of the present application, there is provided a mobile communication device, comprising: a processor; a data interface coupled to the processor, the data interface configured for communicating with an external computing device; a memory coupled to the processor and having data items and instructions stored thereon, the memory including a protected memory having stored thereon an encryption key received from an enterprise server that is physically separate from the external computing device, the protected memory being protected from access by unauthorized applications, the instructions directing the processor to: in response to receiving a request from an authorized application to backup data items, encrypt the data items with the encryption key, and transfer the encrypted data items to the external computing device via the data interface.
In accordance with an example embodiment of the present application, there is provided a communication system, comprising an enterprise server; an external computing device which is physically separate from the enterprise server; at least one mobile communication device configured for communicating with the enterprise server and the external computing device, the mobile communication device comprising: a processor; and a memory coupled to the processor and having data items and computer executable instructions stored thereon, the memory including a protected memory having stored thereon an encryption key received from the enterprise server, the protected memory being protected from access by unauthorized applications. The instructions when executed, directing the processor to: in response to receiving a request from an authorized application to backup one or more data items stored on the mobile communication device to the external computing device, encrypt the one or more data items with the encryption key, and transfer the encrypted data items to the external computing device.
While the present application is primarily described as a method, a person of ordinary skill in the art will understand that the present application is also directed to a device (such as a mobile communication device, external capturing device, and enterprise server described above), for carrying out the described methods and including components for performing each described method step, be it by way of hardware components, a computer programmed by appropriate software to enable the practice of the disclosed method, by any combination of the two, or in any other manner. Moreover, an article of manufacture for use with the apparatus, such as a pre-recorded storage device or other similar computer readable medium including program instructions recorded thereon, or a computer data signal carrying computer readable program instructions may direct an apparatus to facilitate the practice of the disclosed method. It is understood that such apparatus (i.e., a mobile communication device, external capturing device, and enterprise server described above), articles of manufacture, and computer data signals also come within the scope of the present application. In addition, a communication system comprising an enterprise server and a plurality of mobile communication devices connected via a wireless communication network, in which the mobile enterprise server is configured to implement at least some of the processes herein described (i.e., to send out IT policies), and in which one or more of the mobile communication devices are configured to implement at least some of the processes herein described, also comes within the scope of the present application.
The embodiments of the present application described above are intended to be examples only. Those of skill in the art may effect alterations, modifications and variations to the particular embodiments without departing from the intended scope of the present application. In particular, features from one or more of the above-described embodiments may be selected to create alternate embodiments comprised of a sub-combination of features which may not be explicitly described above. In addition, features from one or more of the above-described embodiments may be selected and combined to create alternate embodiments comprised of a combination of features which may not be explicitly described above. Features suitable for such combinations and sub-combinations would be readily apparent to persons skilled in the art upon review of the present application as a whole. The subject matter described herein and in the recited claims intends to cover and embrace all suitable changes in technology.
The present application is a continuation of U.S. patent application Ser. No. 11/763,476 filed Jun. 15, 2007, which is owned in common herewith.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5495533 | Linehan et al. | Feb 1996 | A |
| 6134660 | Boneh et al. | Oct 2000 | A |
| 6192130 | Otway | Feb 2001 | B1 |
| 6496949 | Kanevsky et al. | Dec 2002 | B1 |
| 6574733 | Langford | Jun 2003 | B1 |
| 6611850 | Shen | Aug 2003 | B1 |
| 6871278 | Sciupac | Mar 2005 | B1 |
| 7139846 | Rossi | Nov 2006 | B1 |
| 7222233 | Rubin | May 2007 | B1 |
| 8041641 | Panchbudhe et al. | Oct 2011 | B1 |
| 20010056425 | Richard | Dec 2001 | A1 |
| 20020016912 | Johnson | Feb 2002 | A1 |
| 20020081995 | Leppinen et al. | Jun 2002 | A1 |
| 20020107877 | Whiting et al. | Aug 2002 | A1 |
| 20020156921 | Dutta et al. | Oct 2002 | A1 |
| 20020161997 | Yamasaki et al. | Oct 2002 | A1 |
| 20040003272 | Bantz et al. | Jan 2004 | A1 |
| 20040049700 | Yoshida | Mar 2004 | A1 |
| 20040187012 | Kohiyama et al. | Sep 2004 | A1 |
| 20040236958 | Teicher et al. | Nov 2004 | A1 |
| 20050191998 | Onyon et al. | Sep 2005 | A1 |
| 20050223216 | Chan et al. | Oct 2005 | A1 |
| 20050228994 | Kasai et al. | Oct 2005 | A1 |
| 20060053177 | Suomela et al. | Mar 2006 | A1 |
| 20060143251 | Peterson et al. | Jun 2006 | A1 |
| 20060206544 | Oks et al. | Sep 2006 | A1 |
| 20060230081 | Craswell et al. | Oct 2006 | A1 |
| 20060236406 | Johnson | Oct 2006 | A1 |
| 20070038857 | Gosnell | Feb 2007 | A1 |
| 20070100913 | Sumner et al. | May 2007 | A1 |
| 20070136541 | Herz et al. | Jun 2007 | A1 |
| 20070174362 | Pham et al. | Jul 2007 | A1 |
| 20070220319 | Desai et al. | Sep 2007 | A1 |
| 20070281664 | Kaneko et al. | Dec 2007 | A1 |
| 20080307020 | Ko et al. | Dec 2008 | A1 |
| 20090228719 | Almgren et al. | Sep 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 10109040 | Dec 2007 | CN |
| 1158410 | Nov 2001 | EP |
| WO9964996 | Dec 1999 | WO |
| WO03037016 | May 2003 | WO |
| WO2006054340 | May 2006 | WO |
| WO2007047302 | Apr 2007 | WO |
| Entry |
|---|
| Office Action for corresponding Canadian Patent Application No. 2,634,576; dated Oct. 11, 2011; 6 pages. |
| Office Action from related Chinese Patent Application No. 200810178503.2 dated Dec. 31, 2010 and English Translation thereof; 17 pages. |
| “Backup Premium: Reliability, Confidence, Serenity”; http://www.backup-premium.com; SoftOptima LLC, at least as early as Apr. 23, 2007. |
| Microsoft TechNet; http://www.microsoft.com; 17 pages; Microsoft Corporation; at least as early as Apr. 23, 2007. |
| Number | Date | Country | |
|---|---|---|---|
| 20130283049 A1 | Oct 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11763476 | Jun 2007 | US |
| Child | 13924070 | US |
