I. Field of the Invention
The present invention generally relates to wireless networks and computer communications across wireless networks. More particularly, the invention relates to the updating of the version of an application or data resident on a wireless device when the wireless device connects to a download server that has a more recent version of the wireless device resident application or data.
II Description of the Related Art
Wireless devices, such as cellular telephones, communicate packets including voice and data over a wireless network. Cellular telephones themselves are being manufactured with increased computing capabilities and are becoming tantamount to personal computers and hand-held personal digital assistants (“PDAs”). Some wireless devices, such as select cellular telephones, may have an installed application programming computer platform that allows software developers to create software applications that operate on the wireless device.
It is anticipated that systems and methods will be developed to download applications to a wireless device. Accordingly, it is desirable to have a system and method by which applications and data on a wireless device may be updated efficiently, taking into account the environment, constraints and impacts of transferring information in a wireless network.
Embodiments of the invention include systems and methods for selectively updating the versions of stored datasets on a wireless device that selectively communicates to a wireless network and downloads datasets, such as software applications, information and other data, from download servers on the wireless network. One system includes one or more wireless devices where each wireless device has a computer platform with at least one data file resident thereon, and the wireless device is in selective communication to a wireless network and downloads datasets from download servers across the wireless network. The computer platform of the wireless device further has a resident dataset version summary file that identifies the version of each resident dataset, and the version summary file is updated whenever a resident dataset is updated. This system also includes one or more download servers that are in selective communication to the wireless network and are each selectively in communication with the one or more wireless devices and selectively downloading datasets thereto, with each download server updating its resident datasets that are selectively downloadable to wireless devices and recording the version of each specific updated downloaded server resident dataset.
In one embodiment, when the wireless device attempts to communicate with a download server across the wireless network, the computer platform of the wireless device compares the version of each specific resident dataset listed in the resident dataset version summary file with the version of the downloadable dataset resident on the download server to thereby determine if the version of the wireless device resident dataset is different from the version of the download server resident dataset. The stored record indicating the version of the download server resident dataset can be held in a update summary file resident on the download server, and upon a wireless device attempting to communicate with at least one download server across the wireless network, the computer platform of the wireless device comparing the update file of the download server to the version summary file of the wireless device to thereby determine if the versions of the wireless device resident datasets are different from the versions of the download server resident datasets. The simple comparison of the update summary files will inform the wireless device if a more recent version of any of the wireless device datasets is present on the download server without needing to make the comparison sequentially, i.e., comparing dataset to dataset.
After the wireless device determines the version of the wireless device resident dataset is different from the version of the download server resident dataset, the computer platform of the wireless device downloads the download server resident dataset to supplant the wireless device resident version and be executable on the wireless device. To download the more recent version of the dataset from the download server, the computer platform of the wireless device can prompt the user of the wireless device to communicate with the download server to download the different version of the download server resident dataset to be executable on the wireless device. This function is especially useful if the owner of the wireless device will be charged for the network connection time to download the new version of the application or data from the download server. Otherwise, the computer platform of the wireless device can automatically download the different download server resident dataset to be executable on the wireless device once the newer version of the dataset is detected on the download server.
A method for selectively updating the versions of stored datasets on a wireless device includes communicating from the wireless device to the download server across the wireless network, comparing, at the computer platform of the wireless device, the version of each specific resident dataset listed in the resident dataset version summary file with the version of the downloadable dataset resident on the download server; and determining if the version of the wireless device resident dataset is different from the version of the download server resident dataset based upon the comparison. The method may include, upon determining the version of the wireless device resident dataset is different from the version of the download server resident dataset, downloading the different download server resident dataset to the computer platform of the wireless device from the download server to be executable on the wireless device. To download the new version on the download server, the method can include prompting the user of the wireless device to communicate with the download server to download the different version of the download server resident dataset to be executable on the wireless device or such downloading can be done automatically upon determining the download server resident dataset is a different version than the wireless device resident dataset.
If the stored records indicating the version of the download server resident dataset is held in a version update summary file resident on the download server, comparing the wireless device and download server datasets may be performed by comparing at the computer platform of the wireless device the version update summary file of the download server to the version summary file of the wireless device to thereby determine if the versions of the wireless device resident datasets are different from the versions of the download server resident datasets.
The above method may include a wireless device that can perform the above functions in creating and comparing wireless device version summary file with an update summary file of the download server to determine if the versions of the wireless device resident datasets are different from the versions of the download server resident datasets. Further, because the method is executable on the computer platform of the wireless device, the method may include a program, in a computer readable medium, that directs a wireless device having a computer platform to perform the steps of the method.
Systems and methods are anticipated that provide for the downloading of software applications to a wireless device. Software applications can come pre-loaded at the time the wireless device is manufactured, or the user may later request that additional programs be downloaded over cellular telecommunication carrier networks, where the programs are executable on the wireless device. As a result, users of wireless devices can customize their wireless devices with programs, such as games, printed media, stock updates, news, or any other type of information or program available for download from application download servers through the wireless network.
In one scenario, if the user of the wireless device desires to download and use a software application or other data using a wireless network, the user will typically either call a service provider or contact the service provider through other means, such as through an Internet access, and the service provider will either transmit the application or data to the wireless device across the wireless network or allow the user access a network site where the application or data is downloadable or accessible. To connect to the application download server, the wireless device bridges a communication connection to the wireless network, such as a cellular network, and then attempts to contact an application download server where the desired software application is resident. Once the wireless device contacts the application download server, an initial connection is made and the application download server determines what applications and data are available to the wireless device and sends the appropriate information, such as a menu, for display on the wireless device so the user can learn of the available applications and data. After access is provided to the downloadable applications, the user of the wireless device can download any of the available applications or data.
A problem that may arise is that the version of the application or data that the wireless device downloads to be resident thereupon can be updated or altered at the application download server, and the wireless device resident application or data has no simple manner to be likewise updated. The update problem is exacerbated as the wireless device does not always communicate with the application download server every time the wireless device bridges a communication to the wireless network. Because the communication connection from the wireless device to the application download server can be expensive (especially in a cellular network), it is otherwise very expensive for the wireless device to periodically connect to the application download server and check for more recent version of application or software. Furthermore, while each wireless device resident application or data can be checked against its parallel version resident on the download server every time a connection is made to the download server, such checking would lengthen the connection time and cause more expense to the wireless device owner.
Accordingly, systems and methods consistent with the present invention include updating applications and data resident on a wireless device with the most recent version stored on a download server that the wireless device is connected to. Such systems and methods should be able to determine if more recent versions of the wireless device resident applications and data are present on the download server without significantly lengthening the connection duration in order to effect a full comparison of all wireless device resident applications and data. It is thus to the provision of such a system and method of checking and updating wireless device resident applications and data that the present invention is primarily directed.
It is an object to provide systems and methods whereby the datasets, such as applications, information and other data, resident on a wireless device can be updated with the most recent version of the dataset resident on a download server that the wireless device is connected to. The present invention allows a rapid determination as to whether more recent versions of the wireless device resident datasets are present on the download server, and such determination does not significantly lengthen the connection duration between the wireless device and download server. The present invention thus provides an advantage in that it gives a wireless device the ability to quickly execute a full comparison of dataset versions with a download server and download any newer version of a wireless device resident dataset.
With reference to the figures in which like numerals represent like elements throughout,
The application download server 16 is shown here on a local server-side network 26 with other computer elements in communication with the wireless network 14, such as a database 28 with stored applications and data that contains software applications and data that are accessible and downloadable to the wireless devices 12, 18, 20, 22. There is also shown other network servers, such as server 30 and stand-alone network server 32. The servers 30 and 32 can be application or data download servers, or other types of servers that interact with the wireless devices 12, 18, 20, 22 as are known in the art. The servers 16, 30, 32 may have software applications, patches, files, keys, graphics data, compression algorithms, and any type of general data, collectively referred to hereinafter as “datasets,” resident thereupon that can be accessed by the wireless devices 12, 18, 20, 22 as is further described herein. It should be noted that server-side functions as described herein can be performed on one server, such as application download server 16. Further, a computer server-side computer platform can provide separate services and processes to the wireless devices 12, 18, 20, 22 across the wireless network 14.
The wireless device, such as cellular telephone 12, has a computer platform 50 that can receive and execute software applications and display data transmitted from the application download server 16 or other network servers 30, 32. The computer platform 50 may also include an application-specific integrated circuit (“ASIC”) 52, or other processor, microprocessor, logic circuit, or other data processing device. The ASIC 52 or other processor executes the application programming interface (“API”) layer 54 that interfaces with any resident programs in the memory 56 of the wireless device. The memory can be comprised of read-only or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards, or any memory common to computer platforms. The computer platform 50 also includes a local database 58 that can hold the software applications, file, or data not actively used in memory 56, such as the software applications or downloaded from the application download server 16. The local database 58 is typically comprised of one or more flash memory cells, but can be any secondary or tertiary storage device as known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape, or soft or hard disk.
The wireless device, such as cellular telephone 12, can access and download many types of applications, such as games and stock monitors, or simply data such as news and sports-related data. The downloaded data can be immediately displayed on the display or stored in the local database 58 when not in use. The software applications can be treated as a regular software application resident on the wireless device 12, 18, 20, 22, and the user of the wireless device can selectively upload stored resident applications from the local database 58 to memory 56 for execution on the API 54. The end-user of the wireless device 12, 18, 20, 22 can also selectively delete a software application from the local database 58 whereby other applications and data can be downloaded into the cleared storage space.
With reference to
The present invention allows the creation of “summary files” of the versions of some or all datasets resident on the wireless device 12, 18, 20, 22 or download server, such as application download server 16. As shown in
The system 10 thus selectively updates the versions of stored datasets on a wireless device 12, 18, 20, 22 attempting to communicate with at least one download server (application download server 16) across the wireless network 14, through the computer platform 50 of the wireless device comparing the version of each specific resident dataset listed in the resident dataset version summary file 72 with the version of the downloadable dataset resident on the download server, preferably stored in a download server dataset update summary 70, to thereby determine if the version of the wireless device resident dataset is different from the version of the download server resident dataset. And upon determining the version of the wireless device resident dataset is different from the version of the download server resident dataset, the computer platform 50 of the wireless device can download the download server resident dataset to overwrite the old version of the application or data resident and be executable on the wireless device 12, 18, 20, 22. Other methods can be used on the download server 16, 30, 32 to provide version information to wireless devices 12, 18, 20, 22, such as a header for each dataset file, a direct comparison of the dataset after a predetermined duration since download, or a command can be present in the wireless device-download server handshake that informs the wireless device to compare a specific dataset to determine if the wireless device has the most recent version.
The download server dataset update summary file 70 can identify the versions of files or datasets resident on the download server, such as a graphics data that is present in a welcome screen file, device drivers such as a graphics driver file, and the chess file 66. The wireless device dataset version summary file 72 has parallel files to those resident on the download server dataset update summary file 70 and can compare each version of the datasets through a simple file comparison between the download server dataset update summary file 70 and the wireless device dataset version summary file 72 and locate different version numbers. The summary files 70 and 72 are shown here as having a greater number indicating a more recent version of the dataset. Other systems and method could be used to indicate the version difference as would be known in the art, such as an alphanumeric or other symbolic system that is predefined such that the computer platform 50 of the wireless device 12, 18, 20, 22 can determine if an individual download server resident dataset is a newer version than the wireless device resident dataset.
In the structure shown in
The specific process executing on the wireless device, such as cellular telephone 12, is shown in the flowchart of
A determination is then made as to whether the download server resident dataset is a more recent version than the wireless device resident dataset, as shown at decision 90. If the download server dataset is not more recent at decision 90, then the process returns to step 88 to fetch the next download server resident dataset version. If the download server resident dataset is a more recent version at decision 90, then the wireless device downloads to the computer platform 50 the more recent version of the dataset from the download server, as shown at step 92. A check is made to determine if the more recent version of the dataset was downloaded, as shown at decision 94. If the more recent version of the dataset was not downloaded at decision 92, then the user of the wireless device is informed of the failure to download the more recent dataset version, as shown at step 96, and the process continues to decision 98. Otherwise, if the more recent dataset version was downloaded at decision 94, then a determination is made as to whether there are any further datasets resident on the download server that are parallel to datasets resident on the wireless device 12, 18, 20, 22, as shown at decision 98.
If there are more parallel datasets on the download server at decision 98, then the process returns to step 88 wherein another parallel download server resident dataset is fetched. If there are no further parallel download server resident datasets present at decision 98, then the downloaded datasets are installed and integrated on the computer platform 50 of the wireless device 12, 18, 20, 22 as shown at step 100, and the interconnection between the wireless device and application download server 16 is begun, as shown at step 102. The interconnection between the wireless device and download server typically provides a menu or other data connectivity therebetween. After the interconnection is begun at step 102, the version update process is terminated.
The system 10 thus provides a method for selectively updating the versions of stored datasets on a wireless device 12, 18, 20, 22 including communicating from the wireless device 12, 18, 20, 22 to the download server 16, 30, 32 across the wireless network 14, comparing, at the computer platform 50 of the wireless device, the version of each specific resident dataset listed in the resident dataset version summary file 72 with the version of the downloadable dataset resident on the download server 16, 30, 32, and determining if the version of the wireless device resident dataset is different from the version of the download server resident dataset based upon the comparison. The method may further include downloading the different download server resident dataset to the computer platform 50 of the wireless device 12, 18, 20, 22 from the download server 16, 30, 32 to be executable on the wireless device upon determining the version of the wireless device resident dataset is different from the version of the download server resident dataset.
If the download server 16, 30, 32 stores the record indicating the version of the download server resident dataset in a version update file 70 the step of comparing, at the computer platform 50 of the wireless device 12, 18, 20, 22, the version of each specific resident dataset listed in the resident dataset version summary file 72 with the version of the downloadable dataset resident on the download server, is comparing the update summary file 70 of the download server to the version summary file 72 of the wireless device to thereby determine if the versions of the wireless device resident datasets are different from the versions of the download server resident datasets. The method can also include either prompting the user of the wireless device 12, 18, 20, 22 to communicate with the download server 16, 30, 32 to download the different version of the download server resident dataset to be executable on the wireless device, or automatically downloading the different download server resident dataset to the computer platform 50 of the wireless device upon determining the download server resident dataset is a different version than the wireless device resident dataset.
The invention further includes a wireless device 12, 18, 20, 22 including a computer platform 50 with at least one file resident thereon where the wireless device 12, 18, 20, 22 in selective communication to one or more network servers across a wireless network 14 with each network server selectively downloading datasets to the wireless device 12, 18, 20, 22. Upon the wireless device 12, 18, 20, 22 attempting to communicate with a download server 16, 30, 32 across the wireless network 13, the computer platform 50 of the wireless device compares the version of each specific resident dataset listed in the resident dataset version summary file 72 with the version of the downloadable dataset resident on the download server 16, 30, 32 to thereby determine if the version of the wireless device resident dataset is different from the version of the download server resident dataset. Preferably, upon determining the version of the wireless device resident dataset is different from the version of the download server resident dataset, the computer platform 50 of the wireless device downloads the download server resident dataset. The computer platform 50 of the wireless device can prompt the user of the wireless device 12, 18, 20, 22 to communicate with the download server 16, 30, 32 to download the different version of the download server resident dataset, or automatically download the different download server resident dataset to be executable on the wireless device 12, 18, 20, 22.
In one embodiment with an update summary file 70 resident on the download server, the computer platform 50 of the wireless device 12, 18, 20, 22 compares the update summary file 70 of the download server to the version summary file 72 of the wireless device to thereby determine if the versions of the wireless device resident datasets are different from the versions of the download server resident datasets.
The present invention includes a program resident in a computer readable medium, where the program directs a wireless device having a computer platform to perform the inventive steps of the method. The computer readable medium can be the memory 56 of the computer platform 50 of the cellular telephone 12, or other wireless device 18, 20, 22, or can be in a local database, such as local database 58 of the cellular telephone 12. Further, the computer readable medium can be in a secondary storage media that is loadable onto a wireless device computer platform, such as a magnetic disk or tape, optical disk, hard disk, flash memory, or other storage media as is known in the art.
The present invention may be implemented, for example, by operating portion(s) of the wireless network 14 to execute a sequence of machine-readable instructions, such as wireless platform 50, the application download server 16, and any other network server 30, 32. The instructions can reside in various types of signal-bearing or data storage primary, secondary, or tertiary media. The media may comprise, for example, RAM (not shown) accessible by, or residing within, the components of the wireless network 14. Whether contained in RAM, a diskette, or other secondary storage media, the instructions may be stored on a variety of machine-readable data storage media, such as DASD storage (e.g., a conventional “hard drive” or a RAID array), magnetic tape, electronic read-only memory (e.g., ROM, EPROM, or EEPROM), flash memory cards, an optical storage device (e.g. CD-ROM, WORM, DVD, digital optical tape), paper “punch” cards, or other suitable data storage media including digital and analog transmission media.
While the foregoing disclosure shows illustrative embodiments of the invention, it should be noted that various changes and modifications could be made herein without departing from the scope of the invention as defined by the appended claims. Furthermore, although elements of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
Number | Name | Date | Kind |
---|---|---|---|
5155847 | Kirouac et al. | Oct 1992 | A |
5473772 | Halliwell et al. | Dec 1995 | A |
5564051 | Halliwell et al. | Oct 1996 | A |
5612682 | DeLuca et al. | Mar 1997 | A |
5761618 | Lynch et al. | Jun 1998 | A |
5848064 | Cowan | Dec 1998 | A |
5913213 | Wikstrom et al. | Jun 1999 | A |
5920821 | Seazholtz et al. | Jul 1999 | A |
5995756 | Herrmann | Nov 1999 | A |
6006034 | Heath et al. | Dec 1999 | A |
6009274 | Fletcher et al. | Dec 1999 | A |
6023620 | Hansson | Feb 2000 | A |
6031830 | Cowan | Feb 2000 | A |
6061683 | Alonso | May 2000 | A |
6074434 | Cole et al. | Jun 2000 | A |
6128489 | Seazholtz et al. | Oct 2000 | A |
6167567 | Chiles et al. | Dec 2000 | A |
6199204 | Donohue | Mar 2001 | B1 |
6272333 | Smith | Aug 2001 | B1 |
6272677 | Lam et al. | Aug 2001 | B1 |
6308061 | Criss et al. | Oct 2001 | B1 |
6314565 | Kenner et al. | Nov 2001 | B1 |
6327617 | Fawcett | Dec 2001 | B1 |
6360366 | Heath et al. | Mar 2002 | B1 |
6389423 | Sakakura | May 2002 | B1 |
6397060 | Oikawa | May 2002 | B1 |
6418554 | Delo et al. | Jul 2002 | B1 |
6493871 | McGuire et al. | Dec 2002 | B1 |
6564048 | Sugita | May 2003 | B1 |
6590881 | Wallace et al. | Jul 2003 | B1 |
6636872 | Heath et al. | Oct 2003 | B1 |
6643506 | Criss et al. | Nov 2003 | B1 |
6687901 | Imamatsu | Feb 2004 | B1 |
6735625 | Ponna | May 2004 | B1 |
6735766 | Chamberlain et al. | May 2004 | B1 |
6748209 | Lipsit | Jun 2004 | B2 |
6754894 | Costello et al. | Jun 2004 | B1 |
6789255 | Pedrizetti et al. | Sep 2004 | B1 |
6807415 | Sato | Oct 2004 | B2 |
6832373 | O'Neill | Dec 2004 | B2 |
6868455 | Ariyama | Mar 2005 | B1 |
6877037 | Adachi | Apr 2005 | B1 |
6909898 | Mielke et al. | Jun 2005 | B2 |
6961764 | Mizoguchi | Nov 2005 | B2 |
6966060 | Young et al. | Nov 2005 | B1 |
6970960 | Sarfati | Nov 2005 | B1 |
7080371 | Arnaiz et al. | Jul 2006 | B1 |
7127712 | Noble et al. | Oct 2006 | B1 |
7140013 | Te'eni et al. | Nov 2006 | B2 |
7149508 | Herle | Dec 2006 | B2 |
7149792 | Hansen et al. | Dec 2006 | B1 |
7194258 | Okita et al. | Mar 2007 | B2 |
7243163 | Friend et al. | Jul 2007 | B1 |
7287097 | Friend et al. | Oct 2007 | B1 |
7391759 | Wallace et al. | Jun 2008 | B2 |
7415706 | Raju et al. | Aug 2008 | B1 |
7512638 | Jhaveri et al. | Mar 2009 | B2 |
7516451 | Peng | Apr 2009 | B2 |
7529780 | Braginsky et al. | May 2009 | B1 |
7530065 | Ciudad et al. | May 2009 | B1 |
7555750 | Lilley | Jun 2009 | B1 |
7596720 | Curtis et al. | Sep 2009 | B2 |
7603447 | Hodgson | Oct 2009 | B2 |
7657886 | Chen et al. | Feb 2010 | B1 |
7669197 | O'Neill et al. | Feb 2010 | B1 |
7676792 | Irie et al. | Mar 2010 | B2 |
7698698 | Skan | Apr 2010 | B2 |
7747567 | Teegan et al. | Jun 2010 | B2 |
7752626 | Pandey et al. | Jul 2010 | B1 |
7788662 | Haselden et al. | Aug 2010 | B2 |
7797695 | Motta | Sep 2010 | B2 |
7840957 | Kumashiro et al. | Nov 2010 | B2 |
7844964 | Marolia | Nov 2010 | B2 |
7870412 | Maes | Jan 2011 | B2 |
7958502 | Motta et al. | Jun 2011 | B2 |
7971199 | Chen | Jun 2011 | B1 |
7974613 | Shanker et al. | Jul 2011 | B1 |
7987449 | Marolia et al. | Jul 2011 | B1 |
8245218 | Giambalvo et al. | Aug 2012 | B2 |
8311981 | Braginsky et al. | Nov 2012 | B2 |
8316224 | Vidal et al. | Nov 2012 | B2 |
8340635 | Herz et al. | Dec 2012 | B2 |
8443361 | Vidal et al. | May 2013 | B2 |
8495621 | Traut et al. | Jul 2013 | B2 |
8522232 | Carter et al. | Aug 2013 | B1 |
8555273 | Chia et al. | Oct 2013 | B1 |
8595715 | Ward et al. | Nov 2013 | B2 |
8612398 | Jarrett et al. | Dec 2013 | B2 |
8612516 | Mallur et al. | Dec 2013 | B2 |
8612961 | Stewart | Dec 2013 | B2 |
8620272 | Ganatra et al. | Dec 2013 | B2 |
8635608 | Ramesh et al. | Jan 2014 | B2 |
8762977 | Olsson et al. | Jun 2014 | B2 |
8893109 | Birtwhistle et al. | Nov 2014 | B2 |
8918775 | Carpenter et al. | Dec 2014 | B1 |
20010029178 | Criss et al. | Oct 2001 | A1 |
20010029605 | Forbes et al. | Oct 2001 | A1 |
20010048728 | Peng | Dec 2001 | A1 |
20010052052 | Peng | Dec 2001 | A1 |
20010053688 | Rignell et al. | Dec 2001 | A1 |
20020016956 | Fawcett | Feb 2002 | A1 |
20020077094 | Leppanen | Jun 2002 | A1 |
20020078209 | Peng | Jun 2002 | A1 |
20020091799 | Katz et al. | Jul 2002 | A1 |
20020100035 | Kenyon et al. | Jul 2002 | A1 |
20020131404 | Mehta et al. | Sep 2002 | A1 |
20020157090 | Anton, Jr. | Oct 2002 | A1 |
20020177437 | Chesavage et al. | Nov 2002 | A1 |
20020178178 | Peng | Nov 2002 | A1 |
20020194578 | Irie et al. | Dec 2002 | A1 |
20030023516 | Sharrow et al. | Jan 2003 | A1 |
20030046676 | Cheng et al. | Mar 2003 | A1 |
20030078036 | Chang et al. | Apr 2003 | A1 |
20030100297 | Riordan et al. | May 2003 | A1 |
20030105847 | Jennery et al. | Jun 2003 | A1 |
20030124974 | Asami | Jul 2003 | A1 |
20030145315 | Aro et al. | Jul 2003 | A1 |
20040003266 | Moshir et al. | Jan 2004 | A1 |
20040003389 | Reynar et al. | Jan 2004 | A1 |
20040006630 | Friend et al. | Jan 2004 | A1 |
20040015953 | Vincent | Jan 2004 | A1 |
20040024795 | Hind et al. | Feb 2004 | A1 |
20040038675 | Criss et al. | Feb 2004 | A1 |
20040068724 | Gardner et al. | Apr 2004 | A1 |
20040107417 | Chia et al. | Jun 2004 | A1 |
20040117785 | Kincaid | Jun 2004 | A1 |
20040158817 | Okachi et al. | Aug 2004 | A1 |
20040181790 | Herrick | Sep 2004 | A1 |
20040188510 | Sprigg et al. | Sep 2004 | A1 |
20040188511 | Sprigg et al. | Sep 2004 | A1 |
20040205745 | Piazza | Oct 2004 | A1 |
20040224674 | O'Farrell et al. | Nov 2004 | A1 |
20040230965 | Okkonen | Nov 2004 | A1 |
20050044235 | Balahura et al. | Feb 2005 | A1 |
20050118991 | Koganti et al. | Jun 2005 | A1 |
20050132357 | Shell et al. | Jun 2005 | A1 |
20050268296 | Marolia et al. | Dec 2005 | A1 |
20060031262 | Satoh et al. | Feb 2006 | A1 |
20060206888 | Mavrinac et al. | Sep 2006 | A1 |
20060277408 | Bhat et al. | Dec 2006 | A1 |
20070006222 | Maier et al. | Jan 2007 | A1 |
20070074203 | Curtis et al. | Mar 2007 | A1 |
20070169073 | O'Neill et al. | Jul 2007 | A1 |
20070169093 | Logan et al. | Jul 2007 | A1 |
20070293212 | Quon et al. | Dec 2007 | A1 |
20080003991 | Sievers et al. | Jan 2008 | A1 |
20080028385 | Brown et al. | Jan 2008 | A1 |
20080148250 | Motta | Jun 2008 | A1 |
20080270481 | Augustine | Oct 2008 | A1 |
20080270485 | Yu et al. | Oct 2008 | A1 |
20080281828 | Swartz et al. | Nov 2008 | A1 |
20090077263 | Koganti et al. | Mar 2009 | A1 |
20100242034 | Rugh et al. | Sep 2010 | A1 |
20110078675 | Van et al. | Mar 2011 | A1 |
20110252415 | Ricci | Oct 2011 | A1 |
20120180037 | McCaleb et al. | Jul 2012 | A1 |
20130047145 | Cui | Feb 2013 | A1 |
20130139139 | Mallur et al. | May 2013 | A1 |
20130198732 | Fujita | Aug 2013 | A1 |
20130326493 | Poonamalli et al. | Dec 2013 | A1 |
20140053145 | Steigleder | Feb 2014 | A1 |
20140128054 | Koganti et al. | May 2014 | A1 |
20140130035 | Desai et al. | May 2014 | A1 |
20140208306 | Halder et al. | Jul 2014 | A1 |
Number | Date | Country |
---|---|---|
1288199 | Mar 2001 | CN |
1937533 | Mar 2007 | CN |
19543843 | May 1997 | DE |
0841615 | May 1998 | EP |
0959635 | Nov 1999 | EP |
1672545 | Jun 2006 | EP |
2348721 | Oct 2000 | GB |
1198477 | Aug 1989 | JP |
5210507 | Aug 1993 | JP |
08106393 | Apr 1996 | JP |
9292980 | Nov 1997 | JP |
10021061 | Jan 1998 | JP |
10049354 | Feb 1998 | JP |
11110197 | Apr 1999 | JP |
11225359 | Aug 1999 | JP |
H11331937 | Nov 1999 | JP |
11514760 | Dec 1999 | JP |
2000132355 | May 2000 | JP |
2000132397 | May 2000 | JP |
2000276335 | Oct 2000 | JP |
2001043073 | Feb 2001 | JP |
2001053882 | Feb 2001 | JP |
2001101219 | Apr 2001 | JP |
2001251380 | Sep 2001 | JP |
2001256053 | Sep 2001 | JP |
2001296994 | Oct 2001 | JP |
2001337832 | Dec 2001 | JP |
2001356912 | Dec 2001 | JP |
2002215692 | Aug 2002 | JP |
2002278767 | Sep 2002 | JP |
2005174048 | Jun 2005 | JP |
2008536344 | Sep 2008 | JP |
2009134589 | Jun 2009 | JP |
2012091840 | May 2012 | JP |
19990057991 | Jul 1999 | KR |
1020020009741 | Feb 2002 | KR |
20030030044 | Apr 2003 | KR |
20030033396 | May 2003 | KR |
20040069963 | Aug 2004 | KR |
2233033 | Jul 2004 | RU |
361057 | Jun 1999 | TW |
448404 | Aug 2001 | TW |
473660 | Jan 2002 | TW |
503368 | Sep 2002 | TW |
WO9102313 | Feb 1991 | WO |
WO9729606 | Aug 1997 | WO |
WO9838820 | Sep 1998 | WO |
WO 99045465 | Sep 1999 | WO |
WO-00035117 | Jun 2000 | WO |
WO00077614 | Dec 2000 | WO |
WO0169888 | Sep 2001 | WO |
WO0193030 | Dec 2001 | WO |
WO02046914 | Jun 2002 | WO |
WO02075525 | Sep 2002 | WO |
WO-03083667 | Oct 2003 | WO |
WO-2007056954 | May 2007 | WO |
Entry |
---|
Advisory Action mailed Dec. 4, 2006, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Advisory Action mailed Jan. 22, 2010, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Advisory Action mailed Jul. 17, 2008, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Advisory Action mailed Mar. 19, 2009, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Advisory Action mailed Sep. 10, 2007, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Appeal Brief mailed Dec. 9, 2008, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Appeal Brief mailed Mar. 25, 2010, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Final Office Action mailed Dec. 17, 2007, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Final Office Action mailed Dec. 18, 2008, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Final Office Action mailed Dec. 24, 2009, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Final Office Action mailed Jul. 22, 2008, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Final Office Action mailed Jul. 23, 2009, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Final Office Action mailed Jun. 27, 2007, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Final Office Action mailed Mar. 9, 2007, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Final Office Action mailed May 18, 2004, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Final Office Action mailed Nov. 2, 2005, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Final Office Action mailed Oct 6, 2006, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
International Search Report—PCT/US03/02895, International Searching Authority—US, Jul. 9, 2003. |
Non-Final Office Action mailed Apr. 7, 2010, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Non-Final Office Action mailed Jan. 26, 2005, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Non-Final Office Action mailed Jan. 29, 2007, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Non-Final Office Action mailed Jul. 7, 2003, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Non-Final Office Action mailed Jul. 26, 2007, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Non-Final Office Action mailed Jun. 12, 2008, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Non-Final Office Action mailed Mar. 3, 2008, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Non-Final Office Action mailed May 1, 2006, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Non-Final Office Action mailed May 28, 2009, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Non-Final Office Action mailed Nov. 28, 2007, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Non-Final Office Action mailed Oct. 31, 2006, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Final Office Action mailed Apr. 17, 2008, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Response to Final Office Action mailed Aug. 26, 2007, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Final Office Action mailed Aug. 29, 2007, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Final Office Action mailed Dec. 4, 2006, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Final Office Action mailed Dec. 27, 2005, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Final Office Action mailed Feb. 18, 2009, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Final Office Action mailed Jan. 22, 2010, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Response to Final Office Action mailed Mar. 16, 2010, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Final Office Action mailed Mar. 30, 2006, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Final Office Action mailed May 9, 2007, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Final Office Action mailed Nov. 21, 2006, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Final Office Action mailed Sep. 20, 2004, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Final Office Action mailed Sep. 22, 2008, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Final Office Action mailed Sep. 23, 2009, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Response to Non-Final Office Action mailed Apr. 22, 2007, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Non-Final Office Action mailed Apr. 28, 2005, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Non-Final Office Action mailed Aug. 23, 2006, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Non-Final Office Action mailed Aug. 30, 2009, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Non-Final Office Action mailed Dec. 23, 2007, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Non-Final Office Action mailed Jan. 9, 2004, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Non-Final Office Action mailed Jan. 31, 2007, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Non-Final Office Action mailed Mar. 4, 2008, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Response to Non-Final Office Action mailed Mar. 24, 2009, for U.S. Appl. No. 10/740,355, filed Dec. 18, 2003. |
Response to Non-Final Office Action mailed May 26, 2008, for U.S. Appl. No. 10/061,875, filed Jan. 31, 2002. |
Response to Non-Final Office Action mailed Sep. 17, 2008, for U.S. Appl. No. 10/975,973, filed Oct. 27, 2004. |
Supplementary European Search Report—EP03715962, Search Authority—Munich Patent Office, Nov. 24, 2010. |
Dolgolaptev, V.G., “Rabota v Windows 95 na primerakh”, (Operation in Windows 95 by Examples)—Moscow, Vostochnaya Knizhnaya Kompania (East Book Company), published on 1997, 464 pp. |
Castro P., et al., “Before-Commit Client State Management Services for AJAX Applications”, Hot Topics in Web Systems and Technologies, 2006. Hotweb '06. 1ST IEEE Workshop on, IEEE, PI, Nov. 1, 2006, pp. 1-12, XP031082790, ISBN: 978-1-4244-0595-4, abstract sections I., II.C, II.D, III., IV.F, IV.G, V.C, V.D, VII. |
Mesbah A., et al., “An Architectural Style for AJAX”, Software Architecture, 2007, WICSA '07. The Working IEEE/IFIP Conference on Jan. 1, 2007, pp. 1-10, XP031013840 ISBN: 978-0-7695-2744-4, abstract sections 2.2, 4.2, 4.3, 4.4. |
Open Mobile Alliance, “DS Protocol Approved Version 1.2 OMA-TS-DS—Protocol-V1—2-2-20060710-A”, Internet Citation, [Online] Jul. 10, 2006, XP002456758.Retrieved from the Internet: <URL:http://www.openmobilealliance.org/release—program/docs/DS/V1—2-2-200607 10-A/OMA-TS-DS-Protocol-V1—2-20060710-A.pdf> [retrieved on Oct. 26, 2007] sections 5., 6.12, 9. |
OMA “SyncML HTTP Binding,” Approved version 1.2—Feb. 21, 2007, Open Mobile Alliance, OMA-TS-SyncML—HTTPBinding-V1—2-20070221-A, pp. 1-24. |
Baggiolini et al., “Toward Automatic, Run-time Fault Management for Component-Based Applications”, 1998 Springer, pp. 1-5, <http://link.springercom/content/pdf/10.1007/3-540-69687-3—67.pdf>. |
Oma “SyncML Meta Information,” Approved version 1.2—Feb. 21, 2007, Open Mobile Alliance, OMA-TS-SyncML—Metalnfo-V1—2-20070221-A, pp. 1-25. |
Oma “SyncML OBEX Binding,” Approved version 1.2—Feb. 21, 2007, Open Mobile Alliance, OMA-TS-SyncML—OBEXBinding-V1—2-20070221-A, pp. 1-30. |
Oma “SyncML Representation Protocol,” Approved version 1.2—Feb. 21, 2007, Open Mobile Alliance, OMA-SyncML-RepPro-V1—2-20070221-A, pp. 1-60. |
Oma “SyncML Server Alerted Notification,” Approved version 1.2—Feb. 21, 2007, Open Mobile Alliance, OMA-TS-SyncML—SAN-V1—2-20070221-A, pp. 1-17. |
Oma “SyncML WSPBinding,” Approved version 1.2—Feb. 21, 2007, Open Mobile Alliance, OMA-TS-SyncML—WSPBinding-V1—2-20070221-A, pp. 1-17. |
SyncML Representation Protocol, Version 1.0.1, [retrieved on Jun. 15, 2001], 105 pages, Retrieved from the Internet: URL: http://www.syncml.org/docs/syncml—represent—v101—20010615.pdf. |
Tijs Van Der Storm., “Continuous Release and Upgrade of Component-Based Software”, 2005 ACM, Sep. 5, 2005, SMC'05, pp. 43-57, http://dl.acm.org/results.cfm?h=1&cfid=603384239&cftoken=64589296. |
Grundy et al., “Engineering Plug-In SW Components to Support Collaborative Work”, Software—Practice and Experience, 2002, vol. 32, Wiley, pp. 938-1013. <https://www.cs.auckland.ac.nz/˜john. . ./spe2002.p. . .>. |
La Manna V.P, “Dynamic Software Update for Component-based Distributed Systems”, Jun. 2011, Boulder, Colorado, USA, pp. 1-8; <http://dl.acm.org/results.cfm?h=1&source—query=&&cfid=304794976&cftoken=79323359>. |
Tromcek Z., “Semi-Automatic Component Upgrade with RefactoringNG”, 2011 IEEE, pp. 907-910, http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6078310. |
Gui N., et al., “A Framework for Adaptive Real-Time Applications: the Declarative Real-Time OSGi Component Model”, ACM, ARM, Leuven, Belgium, Dec. 1, 2008,. pp. 35-40. |
Lucredio D., et al., “Orion—A Component-Based Software Engineering Environment”, Journal of Object Technology, vol. 3, No. Apr. 4, 2004, pp. 51-74. |
Yang X., et al., “A Component-based Software Framework for Product Lifecycle Information Management for Consumer Products”, Consumer Electronics, IEEE Transactions on, May 2007, pp. 1195-1203. |
Anosi., et al., “Managing and Assessing the Risk of Component Upgrades”, 2012 IEEE, Please'12, Jun. 4, 2012, pp. 9-12. |
Gu., et al., “Low-disruptive Dynamic Updating of Java Applications”, 2014 Elsevier, vol. 56, Issue 9, Sep. 2014, pp. 1086-1098. |
Nguyen T N., “Component-based Software Update Process in Collaborative Software Development”, 2008 IEEE, APSEC'08, Dec. 3-5, 2008, pp. 437-444. |
Number | Date | Country | |
---|---|---|---|
20030143991 A1 | Jul 2003 | US |