Portable universal data storage device

[0001] This Patent Application claims the benefit of the filing date of U.S. Provisional Patent Application Ser. No. 60/549,385, filed on Mar. 2, 2004 and entitled “CELLULAR PHONE DATA BACKUP DEVICE,” the entire content of which is hereby expressly incorporated by reference.

[0002] The present invention relates generally to back up storage devices; and more particularly to a portable universal data storage device.

[0003] In the past decade, the industry of portable and home electronics has seen an unprecedented growth. Devices such as cellular phones, digital cameras, digital music players, and Personal Digital Assistants (PDAs) have entered the market and quickly become part of mainstream use.

[0004] In the last decade, for instance, the use of cellular/mobile (hereinafter, “cell”) phones has been steadily rising. As an example, in 1992, there were about 10 million cell phone users worldwide. Yet by year 2000, that number grew to 700 million, representing a Compound Annual Growth Rate (CAGR) of 70 percent. The advent in technology and sheer convenience of having this technology within mobile devices have compelled most cell phone users to rely on their phones for storing contact information, making schedules, and even leaving memos. As a result, cell phones today not only facilitate communication, but also act as a storage for a great deal of valuable data formats.

[0005] With millions of portable electronic devices, such as cell phones, lost or damaged yearly, it is not difficult to see that an effective method of backing up this valuable data is needed.

[0006] Today, most cell phones in the market attempt to address the issue of potential data loss by offering computer to cell phone communication options. These options enable cell phone users to edit and backup valuable cell phone data on their Personal Computers (PCs) or laptop computers. Although this method can be effective in securing cell phone data, it does not present a total solution. First, the described option requires both, the possession of a computer, and a relatively high level of computer savvy. Second, it requires a purchase of an expensive, higher-end cell phone model. Third, this method calls for separately purchased cables and software necessary for the communication process, and both the hardware and software will only work with specific brand or model. Finally, if one is switching carriers, or upgrading to a new brand or model, it will still require a manual transfer of data from one system into another.

[0007] Another cell phone data backup method that has recently emerged is a SIM (Subscriber Identity Module) card copy device. A SIM card is a card that allows a cell phone to access the global telecommunications network. The SIM card stores the user's unique identification info, as well as other user data such as phone numbers, contact info, and SMS (short message services) messages. The use of SIM card copy device involves taking the SIM card out of the cell phone, inserting it into the device and activating the backup/copy process. Although copying the data stored on the phone's SIM card provides the user with a greater sense of security, this method too, is not without its shortcomings. First, this approach requires a user to carefully dismantle sensitive equipment and to pull out the fragile card without causing damage to it. Second, only data stored on the SIM card is copied, while the phone's memory remains without a backup copy. Finally, since only cell phones within the Global System for Mobile Communications (GSM) system use the SIM cards, this is not a universal solution.

[0008] In one embodiment, the present invention is an universal data storage device (USD) interfaces with an array of portable and home electronics, including cell phones, digital cameras, portable mp3-players, computers, and other personal electronic devices.

[0016] According to one embodiment of the present invention, a cell phone backup device has been designed to be a simple and effective solution for securing cell phone data. The device is simple enough to be used by novice users, and yet sophisticated enough to meet the demands of computer experts. The device is a small-sized, battery-powered, inexpensive hardware solution for cell phone data backup and restoration needs.

[0017] In one embodiment, a portable universal data storage device (USD) according to the invention includes two buttons and an indicator LED. This configuration simplifies the process of backing up cell phone data to two main steps of 1) connecting the device to the cell phone, and 2) pressing the backup button. The process of restoring contacts back into the phone is just as simple and is performed by pressing a restore button. The USD reads a serial number of an unique device, prior to downloading. This prevents unintentional overwrites from an unauthorized (unidentified) cell phone. A LED status indicator provides accurate and reliable communication and operation status information. An exemplary LED interpretation chart is depicted in Table 1 below.

[0018] Once an appropriate adapter is selected and the device is connected to a host, such as a PC, a user is able to easily delete and edit stored information, export the information into delimited formats to be used by other computer software programs, and save a copy of data locally on the PC.

[0019] FIGS. 1A and 1B show two exemplary embodiments of the USD. As shown, the USD includes a main unit 1, an interface adapter 2, an interface adapter port 3, a backup button 4, a restore button 5, a status LED 6, a format button 7 and device interface ports 8a and 8b. Device interface port 8a supports a data cable 9 for connecting the interface adapter 2 to an external device, such as a cell phone, a PC, etc. Device interface port 8b is an optional port on the main unit 1 that supports communication with a host.

[0020] In one embodiment, device interface port 8a is used for communication with both an external device, such as a cell phone and a host, such as a PC.

[0021] Although the exemplary embodiments of the present invention are described with reference to data communication between the invention and cell phones, it is understood that the invention is not limited to data communication to/from a cell phone. Other devices such as, digital cameras, portable mp3-players, computers, and other personal electronic devices are well within the scope of the present invention.

[0022] The main unit 1 plugs into a communication port (for example, serial, Bus, IRDA, Bluetooth, etc.) of a personal electronic device, such as a cell phone, and backs up the phonebook and other personal data by copying the information onto USD's storage component. USD's storage options may include an internal memory unit or an external memory chip (for example, Compact Flash, Secure Digital, Secure Media etc.) which can be inserted to a proper slot and serve to backup the information from the cell phone.

[0023] Typically, each cell phone has a built in one or more of a serial, bus, IRDA, Bluetooth, or other data communication port and supporting protocols. In order for the invention to backup or restore the data from the cell phone, a proper communication protocol needs to be established between the cell phone and the USD via one of the cell phone's communication ports. This connection is made through the serial, bus, IRDA, Bluetooth or some other port, depending on the cell phone model.

[0024] Once the USD is connected to a supported phone, it supports the necessary protocols and commands to establish a communication link to carry out the necessary data exchange. In one embodiment, when the backup or restore button is pressed, the device flashes for example, a yellow light indicating an active status. Upon the completion of the backup or restore operation, a green light appears. If any errors occur during this process, a flashing red light appears.

[0025] Additionally, for the more sophisticated users, the USD incorporates an easy interface to one of the PC's communication ports, which allows the contents of the USD to be easily transferred, manipulated and backed-up in the PC.

[0026] In one embodiment, the main unit 1 includes a plastic casing, essential circuitry, a battery, and one or more memory chips. It also includes buttons and LED/LCD indicators. Pressing and holding a Backup button activates the backup process of the USD. Pressing and holding a Restore button activates the restore process of the USD. In one embodiment, pressing and holding a Format Button clears all the data stored in USD's own memory or an external media card. The LED/LCD indicator is the device's primary means of communicating with the user. The color and pattern variations of the LED indicator serve as an informative messaging system, providing a real-time update on the device's status. Table 1 below includes some examples of different states of the indicators and their respective meanings.

[0027] The interface adapter 2 plugs into the main unit 1. The interface adapter gives the USD its greatest flexibility. Based on the type of cell phone used or a desired operation, an appropriate adapter needs to be selected. Whether connecting to a specific phone via cables or infrared, attaching to a computer, or even making USD act as a SIM card reader, a suitable interface adapter needs to be connected to the main unit.

[0028] In one embodiment, a firmware protocol for each of the supported interface protocols is stored in the memory of the USD. When a respective interface is detected by a universal adapter interface, the appropriate firmware protocol is loaded to the main unit's communication logic and the communication between the cell phone and the USD is initiated.

[0029] In one embodiment, the communication protocol information for a variety of commonly used communication protocols is stored in the memory of the main unit. Alternatively, or additionally, the communication protocol information may be stored in the memory of the universal interface adapter.

[0030] In one embodiment, a number of interface adapters are supported by the USD including the following interface adapters. A Serial Interface Adapter is used to connect to the cell phone models equipped with a serial port connector. Due to serial port variations throughout cell phone brands, a corresponding adapter needs to be selected for establishing serial communication with the phone.

[0031] A serial interface PC adapter is used to connect to the computer with a ready serial port. Because the computer serial port is an accepted standard, a single serial interface pc adapter is able to work with most computers (e.g., a PC) with an available serial port. An universal serial bus (USB) adapter is used to connect to either a computer or a cell phone equipped with a USB port. Because USB port is an accepted standard, a single USB adapter can be used to communicate with most computers or cell phones that have an available USB port.

[0032] Additionally, an IrDA/Infrared adapter is utilized to connect to either a computer or a cell phone equipped with an IrDA port. An IrDA adapter can be used to communicate with any computer or cell phone with an activated IrDA port, as long as the USD remains within the infrared field. A RF/Bluetooth adapter is used to communicate with any computer or a cell phone that is Bluetooth compatible. A SIM card adapter allows the USD to function as a SIM card reader. The SIM card is the card that allows cell phones to access the global telecommunications network. It stores the user's own number, along with all the saved phone numbers. The SIM card reader function is a solution for those phone brands, for which serial interface adapter cannot be found, or which are not outfitted with USB, IrDA or Bluetooth ports.

[0033] In one embodiment, the USD includes a smart check system that reads the serial number of the personal electronic device (e.g., a cell phone) and does not allow overwriting of the data by transfer of data from a different phone. The smart check process reads the identification data of the cell phone and compares it to the identification data of the backup dataset currently on the USD. If identification data matches or if the dataset on the USD is blank, backup operation begins.

[0034] Upon clicking of the appropriate button (that is, backup or restore button), an appropriate protocol is loaded, USD performs a smart check function and begins to make the necessary data exchange for the requested operation. If any errors should occur during this process, a flashing red light appears.

[0035] FIG. 1C is an exemplary block diagram of an USD that includes a SIM card. The interface adapter 2 plugs into the main unit 1. The interface adapter in this embodiment is tailored for operation of the SIM/media card 10. The card, whether it is a SIM or a flash card, is inserted into the interface adapter card housing 8c and performs the desired operations. The USD is also capable of reading other data sources, such as, SD cards, memory sticks, Flash cards, and the like.

[0036] FIG. 2 is an exemplary block diagram of a system configuration including a cell phone 20, cell phone adapter port 21, an universal interface port adapter 22, a USD main unit 23, an interface adapter port 24, a PC 25, a PC adapter port 26 (e.g., USB, or Serial), device interface ports 27a and 27b, and relevant adapter cables 29a or 29b. Cell phone 20 connects to USD main unit 23 via cable 29b, which connects device interface port 27a and cell phone adapter port 21, through the interface port adapter 22 that is plugged into the adapter port 24 of the USD main unit 23. Because each cell phone may have a different design and technology for its respective communication port 21, the universal port adapter 22 and cable 29b bridge an interface between the USD and the cell phone 20 from various manufacturers. Cable 29a is used for connecting to a host via the interface port adapter 22.

[0037] Although the universal port adapter 22 is the primary means of USD's communication, the main unit 23 may be equipped with an USB and/or UART port 27b for adapter-free alternate means of communicating with a host. This feature also provides the USD with the capability of functioning as a standard data link cable between the PC and the cell phone extending a host of options that consumers may use, for example, Dial-up access or GPRS access. In this embodiment, the universal port adapter 22 is removable from the USD 23.

[0038] A user can backup data from the cell phone 20 into the USD 23 by pressing a Backup button 28b or restore the data from USD into the cell phone by pressing a Restore button 28c. The user can format data in USD by pressing a Format button 28d. The indicator 28a indicates the status of the USD by emitting different color lights. A PC 25 connects to USD's computer interface port 27a or 27b through the data link cable 29 or 29a. When connected to a host, a host interface mode is available with UART(RS232), IrDA, Bluetooth and USB adapters. Host interface mode is a feature which allows a host to access USD's content and manipulate it. The host mode feature enables the user to backup the data stored in the USD into the PC and make necessary firmware updates to the USD to support other cell phone models. In one embodiment, firmware for the interface port adapter 22 is downloaded from the PC 25 to program the interface port adapter for different protocols supported by different cell phones.

[0039] FIG. 3A is an exemplary hardware block diagram an USD main unit 300 and an universal port adapter 308. The universal port adapter 308 includes adapter interface circuitry 311, interface control slave circuitry 309, and a memory unit 310 that stores the adapter identification and protocol information. The adapter interface circuitry 311 controls the physical connection elements between and external device and the adapter, performing tasks such as voltage conversions. Interface control slave circuitry 309 manages communication between the main unit 300 and an universal port adapter 308. Some of the interface control circuitry's 309 primary functions are adapter power management, adapter interface communication, and adapter operations control. The adapter interface circuitry 311 establishes the necessary communication link with the communication port of the cell phone.

[0040] In one embodiment, the universal interface adapter 308 includes an identification code to identify itself to the main unit. In this case, the universal interface adapter 308 depends on the main unit to have the necessary protocol information. In one embodiment, the universal interface adapter includes the necessary protocol information which is loaded into the main unit processor's 303 communication logic when the communication link is established.

[0041] The main unit 300 includes a processor 303. The processor provides various aspects of system control, such as user interface (I/O), reading and writing to memory, communicating with all adapter peripherals, and battery management. The processor also transfers data from and into memory 304.

[0042] The interface control host circuitry 306 is the main unit's counterpart of the interface control slave circuitry 309 within the universal port adapter 308. The interface control host circuitry 306 manages communication between the main unit 300 and an universal port adapter 308. The interface control host circuitry also controls communications with a host through host interface port 307b.

[0043] Also, included in the main unit 300 is an user interface circuitry 305 for managing user interface components. It supports interpretation of user interface features such as a backup, restore, format buttons and the display (indicators LCD/LED).

[0044] A battery 301 provides power for the power supply circuitry 302 which manages USD's power distribution. Depending on the cell phone model, the USD includes the capability to make use of a cell phone's power supply, thus extending the lifespan of USD's battery.

[0045] FIG. 3b is an exemplary hardware block diagram of an universal interface adapter 308. In one embodiment, for devices with complex and/or unknown protocols, the universal interface adapter includes the basic protocol information which is used by the processor when the communication link is established. This also serves as a connection translator between the interface control slave circuit 353 and adapter interface circuit 351.

[0046] In this embodiment the interface adapter 308 houses the necessary translator circuitry 352 for establishing a communication with an external device. This configuration is used for interfacing with USB-based and Card Reader type of devices. Memory 354 stores protocol information and identification information of the interface adapter.

[0047] FIG. 4 shows an exemplary flowchart of an USD's operations when connected to an universal port adapter and a cell phone, according to one embodiment of the present invention. After an universal port adapter plugs into the USD and connects with a cell phone via a communication port (block 402), a backup or restore function is selected by pressing a respective button, as shown in block 404. At this point, an USD attempts to establish an interface with the connected device, as shown in block 406. If the communication link is established (in block 408), the process proceeds to block 410 to determine if the user requested operation was backup or restore.

[0048] If restore operation was selected, the USD begins the restore operation in block 412. Upon completion, the USD indicates the status of the entire operation in block 420.

[0049] If backup operation was selected, the USD reads the serial number of the user device in block 414 and checks if the serial number of device matches with serial number of the backup set in the USD in block 416. After a successful serial number match, the USD performs backup operation in block 418. Upon completion, the USD indicates the status of the entire operation in block 420 and logs status detail in block 422. During backup operation, the USD indicates the status by flashing an indicator, as shown in block 413. If a match between the serial id of the cell phone and the serial id of the last backup transaction is not found, the USD skips the backup operation, indicates the status (block 420), and logs connection details in block 420.

[0050] FIGS. 5A and 5B are exemplary process flows for establishing a communication protocol with an external device. The connected interface adapter may be a serial (UART) interface type adapter, infrared (IrDA) interface type adapter, USB interface type adapter, CardReader interface type adapter, or other interface type adapters. In block 502, the USD determines the type of interface adapter that is currently plugged into the main unit.

[0051] If the adapter interface type is UART (block 504), the USD detects the baud rate in block 506. In one embodiment, this is done by running a baud rate sequence check file for each known baud rate, starting with the highest supported baud rate and moving down to the lowest supported baud rate to determine the highest baud rate. When the baud rate is detected in block 508, the USD proceeds to detect a PC (host) connection in block 534 of FIG. 5B.

[0052] If the adapter interface type is IrDA (block 510), the USD attempts to establish an IrDA (infrared) connection using RFC-IrDA protocol specifications. When a viable IrDA link is established (blocks 512 and 514), the USD proceeds to detect a PC connection in block 534 of FIG. 5B.

[0053] If the adapter interface type is USB (block 516), an USB connection is attempted using RFC-USB protocol specification. When a viable USB link is established (blocks 518 and 520), the USD proceeds to detect a PC connection in block 534 of FIG. 5B.

[0054] Once the connection is established, the USD utilizes a host/pc connection check file to determine if the connection is in fact a host/pc connection in block 534. If a host/pc connection is verified in block 536, the USD changes its mode to a slave mode. If the connection is not a host/pc connection, the protocol last used by the USD is loaded in block 540. Before testing the protocol, a check is made to determine if the last used protocol is loaded successfully in block 542. In block 544, a new protocol is loaded from the adapter if the last used protocol is not loaded successfully. The protocol test of block 548 also functions to identify the connected external device.

[0055] If the protocol test for the currently loaded protocol fails, the next protocol is loaded in block 544. This process repeats until an appropriate protocol is detected (block 550) or all protocols have been tested (block 546). When an appropriate protocol is found in block 550, device identification data is retrieved in block 552, active protocol information is saved in block 554, and a back up or restore operation is performed in block 556. If any errors occur throughout the entire process, an appropriated error is triggered and a relevant indicator flashes in block 558.

[0056] In another example, where the adapter interface type is a card reader (block 522 of FIG. 5A), an appropriate protocol is loaded in block 524 and the card is checked in block 525. If the card is valid and recognizable (block 526), program execution is resumed. If any errors occur throughout the entire process, an appropriated error is triggered and a relevant indicator light flashes in block 558.

[0057] If the type of interface adapter used is not recognized by the USD (block 528), the USD launches a custom device detection logic in block 530 based on the instruction set provided by the interface adapter's memory. If the external device is one of the custom devices for which a supported protocol is found (block 532), program execution is resumed. If any errors occur throughout the entire process, an appropriated error is triggered and a relevant indicator light flashes in block 558.

[0058] The following exemplary quasi-code depicts establishment of a communication protocol.

[0059]

	Load protocol saved in memory from the main unit
	If protocol loaded successfully
	[TEST COMMUNICATION]
	Test communication using loaded protocol
	If device detected
	Read identification data from device
	Save active protocol in memory
	[RETURN TO PROGRAM EXECUTION]
	If device is NOT detected
	Check if all protocols have been tested
	If all protocols have been tested
	[INDICATE ERROR]
	If NOT all protocols have been
	tested
	Load another protocol
	GO TO [TEST COMMUNICATION]
	If protocol DID NOT load successfully
	Load another protocol
	GO TO [TEST COMMUNICATION]

[0060] The following exemplary quasi-code explains a backup operation.

[0061]

	[Detect Communication Port]
	[Establish Communication Port/Interface]
	If Interface established
	Begin backup operation
	[SMART CHECK OPERATION] Retrieve and compare
	phone's serial number with one stored on the unit
	If serial number matches
	Begin sequential transfer of contacts
	from phone to units memory
	Check completion status
	If status is successful
	Upload status info as SMS
	Text to device
	Copy adapter id into unit's
	memory
	Copy phone's serial number to
	unit's memory
	[INDICATE SUCCESS]
	If status IS NOT successful
	Upload status info as SMS
	Text to device
	[INDICATE ERROR]
	If serial number DOES NOT match
	Check if memory is clear
	If memory is clear
	Begin sequential transfer of
	contacts from phone to units
	memory
	Check completion status
	If status is successful
	Copy phone's serial
	number to unit's
	memory
	Upload status info
	as SMS Text to
	device
	[INDICATE SUCCESS]
	If status is not
	successful
	Upload status info
	as SMS Text to
	device [INDICATE
	ERROR]
	If memory IS NOT clear
	Upload status info as SMS
	Text to device
	[INDICATE ERROR]
	If Interface is NOT established
	[INDICATE ERROR]

[0062] The following exemplary quasi-code explains a restore operation.

[0063]

	[Detect Communication Port]
	[Establish Communication Port/Interface]
	If Interface established
	Begin Restore Operation
	Check if unit memory is clear
	If memory is clear
	Upload status info as SMS Text to
	device
	[INDICATE ERROR]
	If memory is NOT clear
	Begin sequential transfer of contacts
	from unit to phone memory
	Check completion status
	If status is successful
	Copy phones serial number to
	unit's memory
	Upload status info as SMS
	Text to device
	[INDICATE SUCCESS]
	If status IS NOT successful
	Upload status info as SMS
	Text to device
	[INDICATE ERROR]
	If Interface is NOT established
	[INDICATE ERROR]

[0064] In one embodiment, in addition to the back up and restore operations, a PC link operation can also be requested by pressing an existing button, for example, the backup button, when connected to a computer. Alternatively, the PC link operation is established by simply plugging the USD into the PC. Once the PC link operation is selected, an appropriate communication protocol with the PC is established. The user can then edit and format the data on the PC. A software residing on the PC enables the user to interface a PC with the USD. This software allows the user to create data and save it in the USD. It also allows the back up data that was transferred from the USD onto the PC be edited and modified and then reloaded to the USD. From the USD the modified data may then be downloaded to the cell phone. Using the software, a user can add, edit, and delete entries stored in the USD. In one embodiment, the software includes an “Export” feature, that allows saving all contacts in a delimited format, so that the users can import these contacts into their favorite program. Other uses of the PC/host connection include synchronization, firmware updates, and the like.

[0065] In one embodiment, a Format button is also provided on the USD. Pressing this button clears the memory in the USD. The LED indicator begins to flash indicating that the USD is formatting its memory. When the memory is cleared, the LED status indicator will flash indicating that the memory is cleared.

[0066] Table 1 illustrates different patterns and colors for the LED indicator and their interpretations, according to one embodiment of the present invention.

[0067]

TABLE 1
Interpreting LED Indicator
Color &	Operation Mode
Pattern	Backup	Restore	PC Link	Interpretation	Solution
Normal Indications:
Green 1*	●	●		Operation Successful
Green 2*	●	●		Operation successful (new phone)
Green 3*				Format operation successful
Progress Indications:
Amber Flashing	●	●	●	Unit performing operation.
Error Indications:
Red Lit	●	●	●	Internal error
Red 1*	●	●		Phone Connector is unplugged.	Check phone connector.
				IrDA link is not established.	Check adapter connection.
				IrDA link breaks during operation	Make sure IrDA port on
					the phone is activated.
					Make sure infrared
					communication field is
					not interrupted during
					operation.
				Phone not recognized	Check if phone model is
					supported by adapter.
				Bad data	Turn phone OFF then back
					ON. Restart operation.
			●	PC Link breaks during operation	Check data link cable.
				Software communication failure	Check PC. Check host
					software.
Red 2*	●			Memory taken up by a different	Either format the USD or
				phone.	restore contacts on the
					phone
				Unit memory full. Not all data	Delete few contacts from
				backed up.	phone and try backup
					again.
		●		Phone memory full. Not all data	Delete a few contacts
				restored.	from the USD with PC
					Software and try again.
				Unit memory empty	Back data up before
					restore.
Red 3*	●	●	●	Low Battery	Replace Battery
*Number of blinks per second.

[0068] It will be recognized by those skilled in the art that various modifications may be made to the illustrated and other embodiments of the invention described above, without departing from the broad inventive scope thereof. It will be understood therefore that the invention is not limited to the particular embodiments or arrangements disclosed, but is rather intended to cover any changes, adaptations or modifications which are within the scope and spirit of the invention as defined by the appended claims.