This invention relates generally to the field of data storage systems. More specifically, the invention relates to methods and systems for synchronizing end devices with one or more data stores and/or other end devices.
The use of data stores by individuals and other entities has become more widespread in recent years given increases in data access speeds and decreases in costs of storage capacity. For example, services such as IBackup™, My Docs Online™, StreamLoad™ and Xdrive™ offer inexpensive storage of data through the use of any internet connection. Also, internet service providers such as Comcast™ provide internet accessible data storage to customers who purchase internet access services.
Meanwhile, the number of end devices that may be connected with these systems has increased dramatically due to high user demand for new functionality and lower manufacturing costs. These end devices include cellular phones, personal data assistants, portable music players, computers, television service receivers, and video game consoles such as the Microsoft Xbox™, Xbox 360™ and Sony PlayStation 2™.
Currently, only limited methods exist for synchronizing end devices to data stores. The types of network connectivity employed to synchronize end devices to the data stores is limited, as is the type of data that may be synchronized. For example, a Blackberry™ handheld computer may, in certain circumstances, only be able to communicate over proprietary networks, and then only be able to synchronize e-mail, calendar and contact information. As another example, cellular phones may only be able to synchronize to data held in a data store maintained by the cellular phone service provider, but not to data on an internet accessible data store. Additionally, certain data repositories are only configured to store certain data types, meaning that end devices must complete multiple, separate, and often user initiated synchronizing operations to synchronize multiple data types with multiple repositories.
Many of these methods also require user intervention to initiate synchronization. These methods may require that a user instruct an end device to initiate synchronization rather than conduct routine automatic synchronization whenever network connectivity is present. Likewise, other methods presently known in the art may allow for automatic synchronization of certain data types on certain networks, but require physical docking and/or user initiation of synchronization of remaining data types.
Hence, there is a need for methods that allow for more complete and automatic synchronization of end devices with data stores and/or other end devices.
In one embodiment the invention provides a method for synchronizing an end device. The method may consist of storing data on the end device, where data consists of multimedia data and non-multimedia data. The method may further consist of connecting the end device with a data repository. The method may compare data on the end device with data on the data repository to determine if any of the data is more recent on the end device or the data repository. The method may also provide a portion of the data from the end device to the data repository, or from the data repository to the end device, possibly based on the comparison of the data.
In such an embodiment, the end device may, merely by way of example, be a cellular phone, a personal data assistant, a portable music player, a handheld computer, a notebook computer, a laptop computer, a desktop computer, a video game console, a cable television receiver, and/or a satellite television receiver. In some embodiments, connecting the end device with the data repository may consist of the end device entering a wireless phone network, the end device entering a wireless local area network, the end device entering a wireless wide area network, the end device connecting with a wired phone network, the end device connecting with a wired local area network, the end device connecting with a wired wide are network, the end device connecting to a cable television system, and/or the end device connecting with a satellite television system.
In one aspect, a portion of the data may be data header information. Data header information may, merely by way of example, be an email header, a file name, a file size, a file type, and/or other descriptive information. In another aspect of the invention, multimedia data may include various file types, including, but not limited to, a Joint Photographic Experts Group (“JPG”) file, a Graphic Interchange Format (“GIF”) file, a Motion Picture Expert Group (“MPG”) file, an Audio Video Interleave (“AVI”) file, a Motion Picture Expert Group Audio Layer 3 (“MP3”) file, a Motion Picture Expert Group 4 Audio (“M4A”) file, a Motion Picture Expert Group 4 Audio Protected (“M4P”) file, and/or a Windows Media Audio (“WMA”) file. Non-multimedia data may, merely by way of example, consist of calendar appointments, contacts, text, email, and/or settings.
In another embodiment, the method may further consist of registering with the data repository. Registering with the data repository may possibly consist of purchasing a service plan from a service provider, opening an email account with a service provider, and/or storing data at the data repository. In another embodiment of the invention, the method may further consist of accessing the data repository with a web browser on an end device.
In one particular aspect, the comparison of data on the end device with data on the data repository may occur periodically. In another aspect, the comparison of data on the end device with data on the data repository may occur with or without user intervention.
In some embodiments of the invention, the data repository may be connected with a communication subsystem and further connected with a translation subsystem. The communication subsystem may direct communication with the data repository. The translation subsystem may translate communication with the data repository.
In another embodiment of the invention, a method for automatically synchronizing an end device with multiple data repositories is provided. The method may consist of storing data on an end device. The data may consist of multimedia data and non-multimedia data. The method may also consist of connecting the end device with two data repositories. Furthermore, the method may consist of comparing data on the end device with data on the two repositories to determine if the data is more recent on the end device or on either of the two data repositories. The method may also consist of providing data from the end device to one of the data repositories, or from one or both of the data repositories to the end device, possibly based on the comparison of the data.
In one aspect, connecting the end device with two data repositories may consist of connecting the end device with a first data repository, connecting the first data repository with a second data repository, and connecting the end device with the second data repository through the connection made between the first data repository and the second data repository. In another aspect, connecting the end device with the second data repository through the connection made between the first data repository and the second data repository may consist of a communication between the end device and the first data repository, a communication between the first data repository and the second data repository based on the communication between the end device and the first data repository, and a communication between the first data repository and the end device based on the communication between the first data repository and the second data repository.
In some embodiment of the invention, a method for synchronizing at least two end devices is provided. The method may consist of connecting both a first and a second end device with a data repository. The method may further store data on the first end device. This data may consist of multimedia data and non-multimedia data. The method may provide at least a portion of the data from the first end device to the data repository. This data may be stored on the first data repository. The first data may provide at least a portion of the data from the data repository to the second end device. The method may then store on the second end device at least a portion of the data provided by the data repository.
In one aspect of these embodiments, the method may provide at least a portion of the data from the first end device to the data repository because the data is new to the first end device. In another aspect of these embodiments, the method may provide at least a portion of the data from the data repository to the second end device because the data stored on the data repository is new to the data repository. In another aspect, the method may provide at least a portion of the data from the data repository to the second end device based at least in part upon a comparison of the data stored on the data repository and the data stored on the second end device.
The present invention is described in conjunction with the appended figures:
One embodiment of the invention provides a method for synchronizing an end device. In such an embodiment, the method may consist of storing data on an end device, where the data may consist of multimedia data and non-multimedia data. The method may further consist of connecting the end device with a data repository and comparing data on the end device with data on the data repository to determine if the data is more recent on the end device or on the data repository. The method may possibly compare only a portion of any data on the end device to data on the data repository. Merely by way of example, the method may only compare metadata or characteristics of specific data. The method may then provide data from the end device to the data repository or from the data repository, to the end device based upon the comparison of the data.
In some embodiments, the method may connect the end device with at least two data repositories. The end devices may connect directly or indirectly with any one data repositories. Merely by way of example, an indirect connection with a data repository may be made through multiple networks or possibly through another data repository. Each data repository may store certain types of data. Merely by way of example, some data repositories may store only: multimedia data; non-multimedia data; image files; video files; audio files; contacts; calendar appointments; e-mail; or some subset of the aforementioned data. This may be because the provider of the data repository only offers services related to particular end devices which only concern themselves with certain data types. Numerous other reasons may also require or permit limiting of the types of data stored on a certain repository. The method may compare data on the end device with data on all connected data repositories to determine if the data is more recent on the end device or on any of the data repositories. In one aspect, the method may provide data from the end device to any one of the data repositories or from at least one data repository to the end device based upon the comparison of the data.
In some embodiments, a method for synchronizing multiple end devices with one or more data repositories is provided. The method may connect multiple end devices with one or more data repositories. The method may make an initial comparison of the data stored on the data repositories and the data stored on the end devices. The method may then provide data from any of the data repositories or end devices to any of the end devices or data repositories, based at least in part on the comparison of the data. In some embodiments only a portion of the data not present on either the end devices or the data repositories may be provided. Merely by way of example, communication logs of calls made with a first end device that is a cellular phone may be provided in full to a particular data repository, but only a portion of that data would be provided to a second end device that is a replacement cellular phone should the first end device become lost or malfunction. So in such an example, while the data repository may contain two years of phone call logs, the method might possibly only provide ten days of phone call logs to the second end device that is the replacement cellular phone.
The method may also store data on any one or more of the end devices. The method may then provide at least a portion of the stored data to one or more of the data repositories. In one aspect, the method may provide at least a portion of the stored data to one or more of the data repositories because the stored data on the end device is new to the end device. Data may be recognized as new to the end device because, merely by way of example, it was created by a user of the end device and not provided to the end device by another end device or data repository. By way of another example, data may be recognized as new to the end device because it is or is not flagged within certain metadata. Multiple methods, known in the art, may be used within the scope of the invention to determine that data is new to the end device.
The method may store on one or more of the data repositories at least a portion of the data provided from the end device(s). Differing portions of the data may possibly be stored on different data repositories. The method may provide at least a portion of the stored data to other end devices besides the end device which provided the stored data. As above, the method may provide at least a portion of the stored data to other end devices besides the end device which provided the stored data because the stored data is recognized as being new to one or more data repositories. Data may be recognized as new to any one data repository because it came from an end device that provided the data because it was new on the end device. Multiple methods, known in the art, may be used within the scope of the invention to determine that data is new to any one of the data repositories. Data provided by the data repositories to end devices which did not originally provide the data may then be stored by the method on such end devices.
In some embodiments, a software program stored on a computer may consist of instructions executable by the computer to conduct one or more of the embodiments of the invention. The computer may or may not be integral with any or all data repositories.
Merely by way of example, the end device may be a cellular phone, a personal data assistant, a portable music player, a handheld computer, a notebook computer, a laptop computer, a desktop computer, a video game console, a cable television receiver, and/or a satellite television receiver. Connecting the end device with a data repository may occur in a variety of ways, including, but not limited to, an end device entering a wireless phone network, an end device entering a wireless local area network, an end device entering a wireless wide area network, an end device connecting with a wired phone network, an end device connecting with a wired local area network, an end device connecting with a wired wide area network, an end device connecting with a cable television network, and/or an end device connecting with a satellite television network.
The method may, in some cases, compare and/or provide only a portion of any data. The portion of the data compared and/or provided by the method may possibly consist of an email header, a file name, a file size, a file type, and/or other descriptive information. Multimedia data in the method may, merely by way of example, consist of a JPG, a GIF, a MPG, an AVI, a MP3, a M4A, and/or a WMA file. Multimedia data may also consist of any file that allows for storage of video, graphics, and/or audio. Non-multimedia data in the method may, merely by way of example, consist of calendar appointments, contacts, text, email, and/or settings. Other non-multimedia data types possibly used by the method may consist of files substantially constituted by text or numerical information to be viewed by a user.
In some embodiments the method may further consist of registering with one or more data repositories. Registering with a data repository may possibly consist of purchasing a service plan with a service provider, opening an email account with a service provider, and/or storing data at the data repository. In an exemplary embodiment, the method will also consist of accessing the data repository with a web browser on an end device. In another exemplary embodiment, the comparison of data on the end device with data on the data repository may occur periodically. Such comparisons may occur without user intervention and/or at a variety of intervals, including, but not limited to, every 30 seconds, every minute, every 30 minutes, every hour, every 12 hours, or every day.
In some embodiments of the invention, the data repository may be connected with a communication subsystem and further connected with a translation subsystem. The communication subsystem may direct communication with the data repository. The translation subsystem my translate communication with the data repository. In some embodiments, the data repository may be capable of performing these functions. In other embodiments, these, or other functions, may not be necessary for the method.
In an embodiment with at least two data repositories, numerous techniques may be employed to connect the end device with all data repositories. In some embodiments, the method may connect the end device with a first data repository, connect the first data repository with a second data repository, and connect the end device with the second data repository through the connection made between the first data repository and the second data repository. Connecting the end device with the second data repository through the connection made between the first data repository and the second data repository may consist of a communication between the end device and the first data repository, a communication between the first data repository and the second data repository based on the communication between the end device and the first data repository, and a communication between the first data repository and the end device based on the communication between the first data repository and the second data repository.
In some embodiments the method may authenticate the user of the end device. Multiple techniques of authenticating the user are possible. Merely by way of example, the method may receive a user name and password and verify that the user name and password are associated with data associated with the user. In other embodiments, the method may receive a GSM SIM card number associated with an end device. The method may then verify that the GSM SIM card number is associated with the end device associated with the user.
Referring now to
The system shown in
Referring to
The system shown in
The computer system 300 is shown comprising hardware elements that may be electrically coupled via a bus 390. The hardware elements may include one or more central processing units (CPUs) 310, one or more input devices 320 (e.g., a mouse, a keyboard, etc.), and one or more output devices 330 (e.g., a display device, a printer, etc.). The computer system 300 may also include one or more storage device 340. By way of example, storage device(s) 340 may be disk drives, optical storage devices, solid-state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like.
The computer system 300 may additionally include a computer-readable storage media reader 350, a communications system 360 (e.g., a modem, a network card (wireless or wired), an infra-red communication device, etc.), and working memory 380, which may include RAM and ROM devices as described above. In some embodiments, the computer system 300 may also include a processing acceleration unit 370, which can include a DSP, a special-purpose processor and/or the like.
The computer-readable storage media reader 350 can further be connected to a computer-readable storage medium, together (and, optionally, in combination with storage device(s) 340) comprehensively representing remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing computer-readable information. The communications system 360 may permit data to be exchanged with a network and/or any other computer described above with respect to the system 300.
The computer system 300 may also comprise software elements, shown as being currently located within a working memory 380, including an operating system 384 and/or other code 388. It should be appreciated that alternate embodiments of a computer system 300 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
Software of computer system 300 may include code 388 for implementing any or all of the function of the various elements of the architecture as described herein. For example, software, stored on and/or executed by a computer system such as system 300, can provide the functions of the end devices, the translation subsystems, the communication subsystems, and/or the data repositories. Methods implementable by software on some of these components will be further discussed below.
In
The method 400 may further consist of connecting the end device with the data repository 420. Merely by way of example, a cellular phone may enter a wireless phone network, wherein the wireless phone network may connect the cellular phone with the data repository; a handheld computer may enter a wireless phone network and connect with a proprietary network, wherein either the wireless phone network or the proprietary network may connect the handheld computer with the data repository; or a video game console may connect with a wired local area network, wherein the wired local area network may connect the video game console with the data repository.
The method 400 may compare data 430 on the end device with the data on the data repository to determine if data is more recent on the end device or the data repository. The method may, in other embodiments, recognize that data at the end device is new and not compare data 430 on the end device with the data on the data repository. Data may be recognized as new possibly because the data was created at the end device. Merely by way of example, a photo taken with an end device that is a cellular phone would be recognized as new when the photo was taken with the cellular phone. The method 400 may furthermore provide data 440 from the end device to the data repository or from the data repository to the end device, possibly based upon the comparison of the data or recognition that the data is new at the end device. In some embodiments a user may define the criteria for determining when and what data to provide from the end device to the data repository or from the data repository to the end device. Merely by way of example, a user may set criteria that no new multimedia data over a certain size may be provided to a particular end device. Other possible criteria may include not allowing a data repository to provide data to an end device if the difference in the age of the data is less than a certain period of time.
In
Once connected with the data repository, the cellular phone may transmit its GSM SIM Card Number and the data repository, or a system in communication therewith, may receive this authentication information 630. The data repository, or the system in communication therewith, may verify this information 635 before allowing any further activity. After authentication has occurred, the repository, or the system in communication therewith, may compare data 640 on the cellular phone with data on the data repository to determine if any data is more current or does not exist on either the cellular phone or the data repository.
In this example, it may be determined that the two non-multimedia contacts, the multimedia JPG file and the multimedia MP3 file are not located on the data repository. The cellular phone may provide the aforementioned data to the data repository 650, therefore synchronizing the data on the data repository with the data on the cellular phone.
Continuing with
Instead of accessing the data repository through the web page portal, in some embodiments the user with the notebook computer may enter a wireless local area network 615 and connect with the network 620. The notebook computer may thereafter, periodically, and without user intervention, connect to the data repository 625, compare data 640, and provide data 650 between the cellular phone and the notebook computer as necessary to synchronize the data on each. The data repository or a system in communication therewith may receive authentication information 630 and verify the authentication information 635 during such a process. In this example, and in this embodiment, the method might provide the notebook computer with the three contacts, the JPG file and the MP3 file that were previously provided to the data repository from the cellular phone.
If the user of the notebook computer in this example, using this or possibly other embodiments, inputs two non-multimedia contacts using the notebook computer's keyboard and also uploads a multimedia MPG file consisting of a video, possibly from the notebook computer's CD-ROM or internet connection, the following may occur: during the next comparison of data 640 the method may determine that the two contacts and the MPG file present on the notebook computer are not present on the data repository; the method may then provide this data 650 to the data repository, thereby synchronizing the notebook computer and the data repository. An alternative possibility is that no comparison of the data 640 may occur. The method may in this circumstance recognize that the two contacts and the MPG file are new data and provide the data 650 to the data repository, thereby synchronizing the notebook computer and the data repository.
If the user in this example, and in this embodiment, then accesses the cellular phone mentioned previously, the cellular phone, if still connected with a wireless phone network and further connected with the data repository, may at some time compare data 640 with the data repository. Based on such comparison, this embodiment of the invention may provide data header information 645 and data 650 from the data repository to the cell phone. As above, the method may not compare the data 640 on the repository with the data on the cellular phone, but may merely recognize that there is new data on the data repository which did not originate from the cellular phone and provide data header information 645 and data 650 from the data repository to the cell phone. In the present example, the embodiment may provide the data 650 of the two new contacts on the data repository to the cellular phone, but only provide data header information 645 for the MPG file if the method determines that characteristics of the system practicing the method mean that it will be inefficient to provide the entire MPG file to the cellular phone. The data header information in this example may constitute a file name, a file size, or a file type. A user may, after evaluating the data header information, possibly override the method's decision and instruct the system to provide the entire MPG file to the cellular phone.
At this point, in the example described, the cellular phone may have stored on it five contacts, one JPG file, one MP3 file, and data header information of one MPG file, if not the MPG file in its entirety; the data repository may have stored on it five contacts, one JPG file, one MP3 file and one MPG file; and the notebook computer may have stored five contacts, one JPG file, one MP3 file and one MPG file. It is thereby shown, in this embodiment, and in this example, how the method may provide synchronization of multiple end devices and a data repository. Use of other embodiments of the invention may allow for synchronization of multiple data repositories as well.
In the foregoing description, for the purposes of illustration, methods were described in a particular order. It should be appreciated that in alternate embodiments, the methods may be performed in a different order than that described. It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machine-executable instructions, which may be used to cause a machine, such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software.
The invention has now been described in detail for purposes of clarity and understanding. However, it will be appreciated that certain changes and modifications may be practiced within the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4837798 | Cohen et al. | Jun 1989 | A |
5406557 | Baudoin | Apr 1995 | A |
5410691 | Taylor | Apr 1995 | A |
5479411 | Klein | Dec 1995 | A |
5524137 | Rhee | Jun 1996 | A |
5633484 | Zancho et al. | May 1997 | A |
5689550 | Garson et al. | Nov 1997 | A |
5724410 | Parvulescu et al. | Mar 1998 | A |
5742905 | Pepe et al. | Apr 1998 | A |
5920835 | Huzenlaub et al. | Jul 1999 | A |
5974449 | Chang et al. | Oct 1999 | A |
6014429 | LaPorta et al. | Jan 2000 | A |
6081830 | Schindler | Jun 2000 | A |
6094681 | Shaffer et al. | Jul 2000 | A |
6154772 | Dunn et al. | Nov 2000 | A |
6173259 | Bijl et al. | Jan 2001 | B1 |
6345279 | Li et al. | Feb 2002 | B1 |
6353827 | Davies et al. | Mar 2002 | B1 |
6366651 | Griffith et al. | Apr 2002 | B1 |
6385611 | Cardona | May 2002 | B1 |
6407680 | Lai et al. | Jun 2002 | B1 |
6421733 | Tso et al. | Jul 2002 | B1 |
6438221 | Lee et al. | Aug 2002 | B1 |
6442589 | Takahashi et al. | Aug 2002 | B1 |
6442606 | Subbaroyan et al. | Aug 2002 | B1 |
6459776 | Aktas et al. | Oct 2002 | B1 |
6463463 | Godfrey et al. | Oct 2002 | B1 |
6483899 | Agraharam et al. | Nov 2002 | B2 |
6556217 | Makipaa et al. | Apr 2003 | B1 |
6564264 | Creswell et al. | May 2003 | B1 |
6631181 | Bates et al. | Oct 2003 | B1 |
6675261 | Shandony | Jan 2004 | B2 |
6694004 | Knoerie et al. | Feb 2004 | B1 |
6754904 | Cooper et al. | Jun 2004 | B1 |
6768789 | Wilk | Jul 2004 | B1 |
6775658 | Zothner | Aug 2004 | B1 |
6782253 | Shteyn et al. | Aug 2004 | B1 |
6799174 | Chipman et al. | Sep 2004 | B2 |
6801793 | Aarnio et al. | Oct 2004 | B1 |
6816582 | Levine | Nov 2004 | B2 |
6826173 | Kung et al. | Nov 2004 | B1 |
6826407 | Helferich | Nov 2004 | B1 |
6832259 | Hymel et al. | Dec 2004 | B2 |
6832377 | Havemose | Dec 2004 | B1 |
6879838 | Rankin et al. | Apr 2005 | B2 |
6882709 | Sheriock et al. | Apr 2005 | B1 |
6938087 | Abu-Samaha | Aug 2005 | B1 |
6964014 | Parish | Nov 2005 | B1 |
6977993 | Starbuck et al. | Dec 2005 | B2 |
6988128 | Alexander et al. | Jan 2006 | B1 |
7013331 | Das | Mar 2006 | B2 |
7069301 | Jerbi et al. | Jun 2006 | B2 |
7069309 | Dodrill et al. | Jun 2006 | B1 |
7072056 | Greaves et al. | Jul 2006 | B1 |
7076734 | Wolff et al. | Jul 2006 | B2 |
7106473 | Sekiguchi | Sep 2006 | B2 |
7110955 | Barhnart | Sep 2006 | B1 |
7120870 | Nakamura | Oct 2006 | B1 |
7188073 | Tam et al. | Mar 2007 | B1 |
7212543 | Arwald et al. | May 2007 | B1 |
7212614 | Burg et al. | May 2007 | B1 |
7219163 | Robinson et al. | May 2007 | B2 |
7224774 | Brown et al. | May 2007 | B1 |
7272662 | Chesnais et al. | Sep 2007 | B2 |
7277529 | Wuthnow et al. | Oct 2007 | B1 |
7295752 | Jain et al. | Nov 2007 | B1 |
7310329 | Vieri et al. | Dec 2007 | B2 |
7310625 | Wu | Dec 2007 | B2 |
7383308 | Groves et al. | Jun 2008 | B1 |
7385875 | May et al. | Jun 2008 | B2 |
7526572 | Omar et al. | Apr 2009 | B2 |
7551727 | Howell et al. | Jun 2009 | B2 |
7587033 | Crago et al. | Sep 2009 | B2 |
7596369 | Alperin et al. | Sep 2009 | B2 |
7688962 | Knoerie et al. | Mar 2010 | B1 |
8078476 | Alperin et al. | Dec 2011 | B2 |
8095664 | Yamaguchi | Jan 2012 | B2 |
8320535 | Alperin et al. | Nov 2012 | B2 |
8799512 | Alperin et al. | Aug 2014 | B2 |
8819751 | Alperin | Aug 2014 | B2 |
9271020 | Alperin | Feb 2016 | B2 |
20020026457 | Jensen | Feb 2002 | A1 |
20020032589 | Shah | Mar 2002 | A1 |
20020075519 | Konsella et al. | Jun 2002 | A1 |
20020076027 | Bernnan et al. | Jun 2002 | A1 |
20020082030 | Berndt et al. | Jun 2002 | A1 |
20020087704 | Chesnais et al. | Jul 2002 | A1 |
20020098831 | Castell et al. | Jul 2002 | A1 |
20020102965 | Mandahl et al. | Aug 2002 | A1 |
20020111991 | Wood et al. | Aug 2002 | A1 |
20020120451 | Kato et al. | Aug 2002 | A1 |
20020128036 | Yach et al. | Sep 2002 | A1 |
20020144273 | Reto | Oct 2002 | A1 |
20020156871 | Munarriz et al. | Oct 2002 | A1 |
20020169823 | Coulombe et al. | Nov 2002 | A1 |
20020170067 | Norstrom et al. | Nov 2002 | A1 |
20020174194 | Mooney et al. | Nov 2002 | A1 |
20020194150 | Bates et al. | Dec 2002 | A1 |
20030041058 | Ibuki et al. | Feb 2003 | A1 |
20030088633 | Chiu et al. | May 2003 | A1 |
20030097262 | Nelson | May 2003 | A1 |
20030101450 | Davidsson et al. | May 2003 | A1 |
20030120717 | Callaway et al. | Jun 2003 | A1 |
20030147369 | Singh et al. | Aug 2003 | A1 |
20030149646 | Chen et al. | Aug 2003 | A1 |
20030172139 | Srinivasan et al. | Sep 2003 | A1 |
20030172175 | McCormack et al. | Sep 2003 | A1 |
20030177408 | Fields | Sep 2003 | A1 |
20040044663 | Horompoly | Mar 2004 | A1 |
20040054719 | Daigle et al. | Mar 2004 | A1 |
20040058673 | Irlam et al. | Mar 2004 | A1 |
20040075698 | Gao | Apr 2004 | A1 |
20040091089 | Wynn | May 2004 | A1 |
20040170155 | Omar et al. | Sep 2004 | A1 |
20040199665 | Omar et al. | Oct 2004 | A1 |
20040236753 | Pocari | Nov 2004 | A1 |
20040268265 | Berger | Dec 2004 | A1 |
20050015311 | Frantz et al. | Jan 2005 | A1 |
20050015443 | Levine et al. | Jan 2005 | A1 |
20050018653 | Phillips et al. | Jan 2005 | A1 |
20050033806 | Harvey et al. | Feb 2005 | A1 |
20050037762 | Gurbani et al. | Feb 2005 | A1 |
20050053206 | Chingon et al. | Mar 2005 | A1 |
20050075097 | Lehikoinen et al. | Apr 2005 | A1 |
20050086282 | Anderson et al. | Apr 2005 | A1 |
20050089149 | Elias | Apr 2005 | A1 |
20050091327 | Koch | Apr 2005 | A1 |
20050101343 | Hsiao | May 2005 | A1 |
20050144557 | Li et al. | Jun 2005 | A1 |
20050201533 | Emam et al. | Sep 2005 | A1 |
20050235307 | Relan et al. | Oct 2005 | A1 |
20050246666 | Kalinoski et al. | Nov 2005 | A1 |
20050254635 | Koretsky et al. | Nov 2005 | A1 |
20050262542 | DeWeese et al. | Nov 2005 | A1 |
20060017983 | Syri et al. | Jan 2006 | A1 |
20060026302 | Bennett et al. | Feb 2006 | A1 |
20060095868 | Sawada et al. | May 2006 | A1 |
20060104293 | Kopp et al. | May 2006 | A1 |
20060104430 | Kirkland et al. | May 2006 | A1 |
20060104431 | Emery et al. | May 2006 | A1 |
20060116918 | Flora | Jun 2006 | A1 |
20060123082 | Digate et al. | Jun 2006 | A1 |
20060156251 | Suhail et al. | Jul 2006 | A1 |
20060168065 | Martin | Jul 2006 | A1 |
20060184624 | Thukral | Aug 2006 | A1 |
20060206941 | Collins | Sep 2006 | A1 |
20060218575 | Blair | Sep 2006 | A1 |
20060250991 | Jabri et al. | Nov 2006 | A1 |
20060265397 | Bryan et al. | Nov 2006 | A1 |
20060265427 | Cohen et al. | Nov 2006 | A1 |
20060277316 | Wang et al. | Dec 2006 | A1 |
20070016643 | Boss et al. | Jan 2007 | A1 |
20070058569 | McMenamin et al. | Mar 2007 | A1 |
20070079010 | Heredia et al. | Apr 2007 | A1 |
20070097394 | Zaima et al. | May 2007 | A1 |
20070104184 | Ku et al. | May 2007 | A1 |
20070139513 | Fang | Jun 2007 | A1 |
20070169148 | Oddo et al. | Jul 2007 | A1 |
20070174448 | Ahuja et al. | Jul 2007 | A1 |
20070198648 | Allen et al. | Aug 2007 | A1 |
20070239833 | Alperin et al. | Oct 2007 | A1 |
20070239880 | Alperin et al. | Oct 2007 | A1 |
20070239895 | Alperin et al. | Oct 2007 | A1 |
20080177616 | Nemirofsky et al. | Jul 2008 | A1 |
20110167122 | Groves et al. | Jul 2011 | A1 |
20140325538 | Alperin | Oct 2014 | A1 |
Number | Date | Country |
---|---|---|
WO 9723082 | Jun 1997 | WO |
Entry |
---|
U.S. Appl. No. 11/228,446, filed Sep. 15, 2005, Jordan Alperin. |
U.S. Appl. No. 11/255,089, filed Oct. 19, 2005, Jordan Alperin et al. |
U.S. Appl. No. 11/268,011, filed Nov. 2, 2005, Jordan Alperin et al. |
U.S. Appl. No. 11/293,028, filed Dec. 2, 2005, Jordan Alperin et al. |
U.S. Appl. No. 11/292,801, filed Dec. 2, 2005, Jordan Alperin et al. |
U.S. Appl. No. 11/399,096, filed Apr. 5, 2006, Jordan Alperin et al. |
U.S. Appl. No. 11/399,585, filed Apr. 5, 2006, Jordan Alperin et al. |
U.S. Appl. No. 11/399,097, filed Apr. 5, 2006, Jordan Alperin et al. |
U.S. Appl. No. 11/399,098, filed Apr. 5, 2006, Jordan Alperin et al. |
U.S. Appl. No. 11/400,643, filed Apr. 6, 2006, Jordan Alperin et al. |
U.S. Appl. No. 11/400,616, filed Apr. 6, 2006, Jordan Alperin et al. |
U.S. Appl. No. 11/400,644, filed Apr. 6, 2006, Jordan Alperin et al. |
U.S. Appl. No. 11/383,620, filed May 16, 2006, Jordan Alperin. |
Goodlink Business Brochure, Enterprise Edition 4.5, Good Technology, Inc., www.good.com, 4 pages. |
Comcast online storage, Comcast.net, 1 page. |
Secure Online Storage, http://www.xdrive.com, Nov. 9, 2005, 2 pages. |
Online Backup, Online Storage, Collaboration and Data Sharing, http://www.ibackup.com, Nov. 9, 2005, 1 page. |
File and Data Storage, Transfer, Delivery Since 1999, http://www.mydocsonline.com, Nov. 9, 2005, 2 pages. |
Share Videos and Photos—Online MP3 Storage and Access, http://www.streamload.com, Nov. 9, 2005, 1 page. |
Koontz, Alan “Find in Page Script”, Oct. 13, 1969, Dynamic Drive, “http:/www.dynamicdrive.com/dynamicindex11/findpage.htm”, 2 pages. |
The Web Design Resource, “Manipulating Font Size and Color”, Jun. 27, 1998, The Web Design Resource, 2 pages. |
U.S. Appl. No. 11/228,446, Final Office Action dated May 18, 2010, 15 pages. |
U.S. Appl. No. 11/228,446, Final Office Action dated Jul. 24, 2009, 11 pages. |
U.S. Appl. No. 11/228,446, Final Office Action dated Oct. 24, 2008 , 6 pages. |
U.S. Appl. No. 11/228,446, Office Action dated Jan. 4, 2010, 17 pages. |
U.S. Appl. No. 11/228,446, Office Action dated Jun. 3, 2008, 13 pages. |
U.S. Appl. No. 11/228,446, Office Action dated Mar. 3, 2009, 12 pages. |
U.S. Appl. No. 11/228,446; Interview Summary dated Nov. 28, 2011; 3 pages. |
U.S. Appl. No. 11/399,096; Final Office Action dated Dec. 6, 2011; 15 pages. |
U.S. Appl. No. 11/228,446; Issue Notification dated May 30, 2012; 1 page. |
U.S. Appl. No. 11/228,446; Examiner-Initiated Interview Summary dated Nov. 10, 2011; 2 pages. |
U.S. Appl. No. 11/255,089, Final Office Action dated Sep. 24, 2009. |
U.S. Appl. No. 11/255,089, Appeal Brief dated Apr. 26, 2010, 17 pages. |
U.S. Appl. No. 11/255,089, Office Action dated Mar. 10, 2009, 17 pages. |
U.S. Appl. No. 11/255,089, Office Action dated Oct. 8, 2008, 18 pages. |
U.S. Appl. No. 11/266,011, Office Action dated Dec. 22, 2008, 12 pages. |
U.S. Appl. No. 11/266,011, Office Action dated Aug. 19, 2010, 19 pages. |
U.S. Appl. No. 11/266,011, Office Action dated Jun. 10, 2009, 12 pages. |
U.S. Appl. No. 11/266,011, Final Office Action dated Jan. 28, 2010, 11 pages. |
U.S. Appl. No. 11/266,011; Notice of Allowance dated Oct. 7, 2011; 18 pages. |
U.S. Appl. No. 11/266,011; Issue Notification dated Apr. 11, 2012; 1 page. |
U.S. Appl. No. 11/292,801, Office Action dated Mar. 3, 2009, 9 pages. |
U.S. Appl. No. 11/293,028, Final Office Action dated Apr. 15, 2009, 12 pages. |
U.S. Appl. No. 11/293,028, Final Office Action dated Mar. 17, 2008, 11 pages. |
U.S. Appl. No. 11/293,028, Office Action dated Aug. 13, 2008, 9 pages. |
U.S. Appl. No. 11/293,028, Office Action dated Nov. 14, 2007, 11 pages. |
U.S. Appl. No. 11/293,028, Notice of Allowance dated Oct. 30, 2009, 16 pages. |
U.S. Appl. No. 11/399,096, Final Office Action dated Jun. 17, 2009, 11 pages. |
U.S. Appl. No. 11/399,096, Office Action dated Dec. 7, 2009 , 10 pages. |
U.S. Appl. No. 11/399,096, Office Action dated Jan. 22, 2009, 14 pages. |
U.S. Appl. No. 11/399,096, Final Office Action dated May 24, 2010, 12 pages. |
U.S. Appl. No. 11/399,096, Office Action dated Oct. 27, 2010, 11 pages. |
U.S. Appl. No. 11/399,096, Notice of Panel Decision from Pre-Appeal Brief Review dated May 23, 2011, 2 pages. |
U.S. Appl. No. 11/399,096, Office Action dated Jul. 12, 2011, 14 pages. |
U.S. Appl. No. 11/399,098, Notice of Allowance dated Jun. 2, 2009, 6 pages. |
U.S. Appl. No. 11/399,098, Office Action dated Aug. 25, 2008, 13 pages. |
U.S. Appl. No. 11/399,098, Terminal Disclaimer dated Nov. 25, 2008, 1 page. |
U.S. Appl. No. 11/399,098, Requirement for Election/Restriction dated Feb. 25, 2009, 6 pages. |
U.S. Appl. No. 11/399,098, Response to Requirement for Election/Restriction dated Mar. 11, 2009, 10 pages. |
U.S. Appl. No. 11/399,098, filed Apr. 5, 2006, now U.S. Pat. No. 7,596,369, 16 pages. |
U.S. Appl. No. 11/399,585, Office Action dated Mar. 24, 2009, 16 pages. |
U.S. Appl. No. 11/399,585, Final Office Action dated Nov. 4, 2009, 10 pages. |
U.S. Appl. No. 11/399,585; Office Action dated Jul. 18, 2011, 20 pages. |
U.S. Appl. No. 11/399,585, Non-Final Office Action dated Sep. 21, 2010, 15 pages. |
U.S. Appl. No. 11/399,585; Non Final Office Action dated Jan. 4, 2012; 19 pages. |
U.S. Appl. No, 11/388,585; Final Rejection dated May 1, 2012; 35 pages. |
U.S. Appl. No. 11/400,643, Final Office Action dated Jul. 27, 2009, 18 pages. |
U.S. Appl. No. 11/400,643, Office Action dated Jan. 9, 2009, 17 pages. |
U.S. Appl. No. 11/400,643; Notice of Panel Decision dated Jul. 11, 2011; 2 pages. |
U.S. Appl. No. 11/400,643; Issue Notification dated Jun. 13, 2012; 1 page. |
U.S. Appl. No. 11/400,643; Notice of Allowance dated Mar. 8, 2012; 14 pages. |
U.S. Appl. No. 11/400,644, Office Action dated Jan. 21, 2009, 16 pages. |
U.S. Appl. No. 11/400,616, Final Office Action dated Feb. 1, 2010, 16 pages. |
U.S. Appl. No. 11/400,616, Office Action dated Jul. 13, 2009, 21 pages. |
U.S. Appl. No. 11/400,616 CT; Non Final Office Action dated Mar. 8, 2012; 26 pages. |
U.S. Appl. No. 11/399,097, Final Office Action dated Sep. 1, 2010, 10 pages. |
U.S. Appl. No. 11/399,097, Office Action dated Mar. 26, 2010, 12 pages. |
U.S. Appl. No. 11/399,097, Requirement for Election/Restriction dated Jan. 26, 2010, 6 pages. |
U.S. Appl. No. 11/399,097, Response to Requirement for Election/Restriction dated Feb. 22, 2010, 1 page. |
U.S. Appl. No. 11/383,620, Final Office Action dated Mar. 28, 2011, 27 pages. |
U.S. Appl. No. 11/383,620; Non Final Office Action dated Aug. 31, 2011; 21 pages. |
U.S. Appl. No. 11/383,620; Final Office Action dated Feb. 3, 2012; 18 pages. |
U.S. Appl. No. 11/400,616; Corrected Notice of Allowability dated Sep. 7, 2012; 11 pages. |
U.S. Appl. No. 11/400,616; Corrected Notice of Allowability dated Oct. 26, 2012; 12 pages. |
U.S. Appl. No. 11/400,616; Notice of Allowance dated Jul. 3, 2012; 17 pages. |
U.S. Appl. No. 11/400,616; Issue Notification dated Nov. 7, 2012; 1 page. |
U.S. Appl. No. 11/383,620; Non-Final Office Action dated Oct. 3, 2013; 24 pages. |
U.S. Appl. No. 11/255,089; Withdrawal of Notice of Abandonment dated Oct. 10, 2013; 2 pages. |
U.S. Appl. No. 11/255,089; Non-Final Rejection dated Nov. 22, 2013; 35 pages. |
U.S. Appl. No. 11/255,089; Notice of Panel Decision dated Jul. 1, 2013; 9 pages. |
U.S. Appl. No. 11/255,089; Notice of Allowance dated Mar. 31, 2014; 36 pages. |
U.S. Appl. No. 11/383,620; Notice of Allowance dated Apr. 14, 2014; 16 pages. |
U.S. Appl. No. 11/399,097; Notice of Allowance dated Jul. 29, 2011; 20 pages. |
U.S. Appl. No. 11/399,097; Notice of Allowance dated Aug. 23, 2011; 5 pages. |
U.S. Appl. No. 11/399,097; Supplemental Notice of Allowability dated Oct. 20, 2011; 5 pages. |
U.S. Appl. No. 11/780,045; Office Communication dated Nov. 8, 2011; 2 pages. |
U.S. Appl. No. 11/399,097; Issue Notification dated Nov. 22, 2011; 1 page. |
U.S. Appl. No. 11/399,097; Supplemental Notice of Allowability dated Oct. 31, 2011; 5 pages. |
U.S. Appl. No. 11/255,089; Issue Notification dated Jul. 16, 2014; 1 page. |
U.S. Appl. No. 11/383,620; Issue Notification dated Aug. 6, 2014; 1 page. |
U.S. Appl. No. 14/330,181; Non-Final Rejection dated May 28, 2015; 36 pages. |
U.S. Appl. No. 14/330,181; Notice of Allowance dated Oct. 23, 2015; 17 pages. |
U.S. Appl. No. 14/330,181; Issue Notification dated Feb. 3, 2016; 1 page. |
Number | Date | Country | |
---|---|---|---|
20070239805 A1 | Oct 2007 | US |