US20050050538A1 - Software distribution system and software receiving terminal apparatus - Google Patents

Software distribution system and software receiving terminal apparatus Download PDF

Info

Publication number
US20050050538A1
US20050050538A1 US10/843,487 US84348704A US2005050538A1 US 20050050538 A1 US20050050538 A1 US 20050050538A1 US 84348704 A US84348704 A US 84348704A US 2005050538 A1 US2005050538 A1 US 2005050538A1
Authority
US
United States
Prior art keywords
software
update
distribution
terminal apparatus
step
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/843,487
Inventor
Yukihiro Kawamata
Kimiya Yamaashi
Masato Horita
Original Assignee
Yukihiro Kawamata
Kimiya Yamaashi
Masato Horita
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to JP11-244787 priority Critical
Priority to JP24478799A priority patent/JP2001067232A/en
Priority to US09/648,451 priority patent/US6820259B1/en
Application filed by Yukihiro Kawamata, Kimiya Yamaashi, Masato Horita filed Critical Yukihiro Kawamata
Priority to US10/843,487 priority patent/US20050050538A1/en
Publication of US20050050538A1 publication Critical patent/US20050050538A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • G06F8/64Retargetable
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates

Abstract

A terminal apparatus has a reception unit for receiving a data group or a program group distributed from a satellite or a ground distribution system, and an update sequence management unit. The update sequence management unit searches data or a program of the terminal apparatus to be updated and data or a program necessary for updating the data or the program of the terminal apparatus, from the data group or the program group, determines an update sequence of the searched program or data, and updates the program or data of the terminal apparatus in accordance with the determined update sequence.

Description

    BACKGROUND OF THE INVENTION
  • The present invention relates to a distribution system for distributing data or programs and a receiving terminal apparatus for receiving distributed data or programs, respectively via a satellite or a ground station.
  • Conventionally, distribution of data or programs (hereinafter described as software) is generally conducted by using storage media. Generally, a user installs distributed software by using storage media. If software can be automatically updated (including installation of new software), it is very convenient. In addition, without particular knowledge, new software can be updated and many people can use latest software.
  • Techniques regarding renewal of software is disclosed, for example, in JP-A-11-98477.
  • SUMMARY OF THE INVENTION
  • If all of distributed software received at a receiving terminal apparatus-can be automatically updated simply in the reception order of software, the process at the receiving terminal apparatus is easy. However, in this case, data or programs which are required not to be altered may be installed during update. Problems such as an inability of using the terminal apparatus may occur.
  • If a user is required to check distributed data or programs and determine the data or programs used for update and the update sequence, highly sophisticated technical knowledge is necessary and a work load is required.
  • It is an object of the present invention to provide a distribution system capable of correctly and easily updating software.
  • It is another object of the present invention to provide a terminal apparatus capable of easily executing a necessary update process in accordance with distributed software.
  • According to one aspect of the present invention, the contents of data or programs and installation condition data are distributed separately from distribution of data or programs.
  • According to another aspect of the present invention, distributed data or a program is checked whether it is required to be updated, and distributed data or program used for update are selected from distributed data and programs. After the update sequence of distributed data and programs is determined, they are updated. In this manner, a terminal apparatus easy to use can be provided.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a diagram showing the structure of a system according to a first embodiment of the invention.
  • FIG. 2 is a diagram showing the structure of the system of the first embodiment.
  • FIG. 3 is a flow chart illustrating the operation to be executed by a station of the first embodiment.
  • FIG. 4 is a flow chart illustrating the operation to be executed by a terminal apparatus of the first embodiment.
  • FIG. 5 is a flow chart illustrating the operation to be executed by the terminal apparatus of the first embodiment.
  • FIG. 6 is a flow chart illustrating the operation to be executed by the terminal apparatus of the first embodiment.
  • FIG. 7 shows a list of software distributed from the station of the first embodiment.
  • FIG. 8 is a terminal information table of the terminal apparatus of the first embodiment.
  • FIG. 9 is a diagram showing an extraction sequence for software relevant to the software possessed by the terminal apparatus of the first embodiment.
  • FIG. 10 is a diagram showing an extraction sequence for software relevant to the software possessed by the terminal apparatus of the first embodiment.
  • FIG. 11 is an installation sequence table according to the first embodiment.
  • FIG. 12 is a diagram showing the structure of a system according to a second embodiment of the invention.
  • FIG. 13 is a flow chart illustrating the operation to be executed by a software management center of the second embodiment.
  • FIG. 14 is a flow chart illustrating the operation to be executed by a terminal apparatus of the second embodiment.
  • FIG. 15 is a flow chart illustrating the operation to be executed by the terminal apparatus of the second embodiment.
  • FIG. 16 is a display window used in an “update software acquisition mode” at the terminal apparatus of the second embodiment.
  • FIG. 17 is a display window used in an “update software acquisition mode” at the terminal apparatus of the second embodiment.
  • FIG. 18 is a display window used in an “update software acquisition mode” at the terminal apparatus of the second embodiment.
  • FIG. 19 is a display window used when a distribution start signal is received.
  • FIG. 20 is a display window used while distributed software is received.
  • DETAILED DESCRIPTION OF THE EMBODIMENTS
  • The first embodiment of this invention will be described with reference to FIGS. 1 to 11. FIG. 1 is a diagram showing the structure of a system according to the first embodiment. The system of this embodiment is constituted of a terminal apparatus 150 and a station 100 which distributes data or programs to the terminal apparatus 150. Although the terminal apparatus for receiving data or programs may be mounted on a fixed facility, in this embodiment it is assumed that the terminal apparatus is mounted on a mobile unit. As an example of such a mobile unit, vehicles distributed in a broad area are used by way of example. The terminal apparatus may not be movable, and not only the vehicles but also other various mobile units may be used such as those used for overland transport and marine transport, and air planes.
  • Although a variety of apparatuses may be used as the terminal apparatus of the mobile unit, a typical example, a terminal apparatus with a car navigation function, is used in the following description.
  • Although there are many available media for distributing data or programs (hereinafter described as software) to be distributed, the system is assumed to use a satellite.
  • Either a geostationary satellite or a mobile satellite may be used. In Japan, a geostationary satellite has a small angle of incidence so that buildings and geographical features greatly influence communications. The angle of incidence of a mobile satellite is determined by its orbit. By properly selecting an orbit, the mobile satellite can move along an orbit just above Japan. In this case, radio waves can be transmitted along a zenith direction.
  • The system shown in FIG. 1 distributes software by using a satellite as described above. The terminal apparatus 150 with a car navigation function receives distributed software and updates by itself software already possessed by the apparatus.
  • This system has: the station 100 for distributing software to the terminal apparatus 150; and the apparatus 150 for receiving distributed software, the apparatus having a function of updating software possessed by the apparatus.
  • The station 100 has: a distribution side communication unit 115 for distributing software to update software possessed by the terminal apparatus 150 and distributing a list of software to be distributed; a distribution software database 120 for storing distribution software; an encryption unit 110 for enciphering software before it is distributed to the terminal apparatus 150; a distribution software list management unit 125 for managing a distribution software list described with the names and distribution time of distribution software; an update contents management unit 130 for managing the update contents of software possessed by the terminal apparatus 150; and a distribution side control unit 105 for issuing a distribution command to the distribution side communication unit 115, issuing an encryption command to the software encryption unit 110 and managing the whole control flow.
  • The terminal apparatus 150 has: a navigation unit 195 for searching necessary map information, displaying a map, and displaying a present location of the user; a software update unit 160 for updating software of the navigation unit 195; a terminal side communication unit 155 for receiving software and a distribution software list distributed from the station 100; a software temporary storage unit 185 for temporarily storing software received at the terminal side communication unit 155; a software recovery unit 165 for recovering the original software of the navigation unit 195 once updated by the software update unit 160; an update sequence management unit 190 for selecting software or software group required to be updated, from the distribution software list sent from the station 100, and managing the update order of the selected software or software group; a decryption unit 170 for deciphering software distributed from the station 100; an input unit 175 for inputting a decryption key necessary for deciphering software at the decryption unit 170; a display unit 197 for displaying map information or search information; and a terminal side control unit 180 for issuing a software update command to the software update unit 160, issuing a software recovery command to the software recovery unit 170, and issuing an update sequence command to the update sequence management unit 190.
  • FIG. 2 illustrates how software is distributed from the station 100 to the terminal apparatus in the vehicle. The station 100 distributes software and a distribution software list to a number of vehicles (vehicles 220, 225, 230 and 235) via an artificial satellite, e.g., a super ellipsoidal orbit satellite 210. The vehicles 220, 225, 230 and 235 transmit update contents to the station via the super ellipsoidal orbit satellite 210.
  • The super ellipsoidal orbit satellite 210 moves along an orbit (angle of incidence: 70° or larger) so that the vehicles 220, 225, 230 and 235 can see the super ellipsoidal orbit satellite 210 in the zenith direction. By using such a satellite for software distribution, it becomes possible to prevent communication between the vehicles and satellite 210 from being interfered by high architectures such as buildings. Since only direct waves from the satellite are received, it is possible to suppress the influence of reflected waves which generate noises.
  • An example shown in FIG. 2 is most preferable. However, the embodiment is also applicable to the environments that the angle of incidence of the satellite 210 is low, there are obstacles in the communication paths, or reflected waves, or radio waves are transmitted via an intermediary.
  • FIGS. 3 to 6 are flow charts illustrating the operation of the first embodiment. The flow chart of FIG. 3 illustrates the operation of the station 100, and the flow charts of FIGS. 4 to 6 illustrate the operation of the terminal apparatus 150.
  • At Step 300 shown in FIG. 3, the distribution list management unit 125 forms a distribution software list describing therein the distribution contents of software and distribution schedule, the list being distributed from the station 100. In forming the distribution software list, the distribution list management unit 125 inquires version information of a software group stored in the distribution software database 120 and determines a distribution time in accordance with each of stored software. An example of the distribution software list is shown in FIG. 7.
  • Next, at Step 305 the distribution side communication unit 115 transmits a distribution start signal for 30 seconds to a number of terminal apparatuses 150 in the vehicles, to thereafter follow Step 310. This distribution start signal is transmitted in response to a command from the distribution side control unit 105 which uses a predetermined schedule.
  • On the side of the terminal apparatus 150, at Step 400 shown in FIG. 4 if the terminal apparatus 150 is not used, a standby mode is entered in order to lower a power consumption of the terminal apparatus 150. The standby mode is a mode in which the frequency of control clocks is lowered to lower the execution speed of a command and suppress the power consumption and hence heat generation.
  • If the terminal apparatus 150 is in use for another purpose, the apparatus 150 operates for that purpose. For example, at Step 400 the terminal apparatus 150 may be in use for navigation by using the navigation unit 195 and display unit 197. If the terminal apparatus has another function, it may be in use for this function.
  • After the distribution start signal is transmitted from the station 100 at Step 305, it is checked at Step 405 whether the terminal communication unit 155 has received the distribution start signal. If received, at Step 410 the terminal side control unit 180 sets a reception mode so that the software group and distribution software list to be distributed can be received. FIG. 19 shows a display window of the display unit 197 used when the terminal apparatus 150 is used for the navigation purpose. After a reception of the distribution start signal is detected at Step 405, as shown in FIG. 19, information indicating a reception of the distribution start signal is displayed in a display area 1904 under a navigation display area 1902.
  • If there is no distribution from the station 100 and no distribution start signal is received at Step 405, then the standby mode continues or the terminal apparatus operates for its function to wait for the distribution start signal at Step 405.
  • On the side of the station 100, at Step 310 the distribution side communication unit 115 distributes the distribution software list formed by the distribution software list management unit 125 to the terminal apparatus 150 to thereafter follow Step 315.
  • On the side of the terminal apparatus 150, at Step 415 the terminal side communication unit 155 receives the distribution software list distributed from the station 100 to thereafter follow Step 420. When the list is received at Step 415, a display window shown in FIG. 20 appears and the navigation function is stopped to receive distribution software.
  • From Step 420 to Step 525, the update sequence management unit 190 selects software to be installed and checks an installation sequence.
  • At Step 420 the terminal side control unit 180 initializes a distribution number r of reference software in the received distribution software list, to r=0.
  • The distribution software list will be described. FIG. 7 shows a distribution software list 700 distributed from the station 100. The distribution software list 700 stores therein: a distribution time 705 of each piece of software; a software number 710 sequentially and uniquely assigned to each piece of software, starting from “1”; a name 715 of distribution software; an installation type 720 indicating whether the software is update software or new software; a name (including a version) 725 of software updated by distribution software (up-data); a name (including a version) 730 of software to be updated by distribution software (up-data); an apparatus 735 compatible with installation software; and compatible software 740.
  • At Step 425 the terminal side control unit 180 increments the distribution number r of the reference software in the received distribution software list by “1”. Next, at Step 430 the terminal side control unit 180 checks whether the distribution software list contains software having the distribution number r, in order to confirm whether all software in the distribution software list has been referred to. If the distribution software list contains software having the distribution number r, i.e., if all software in the distribution software list is not still referred to, then the flow advances to Step 435, whereas if the distribution software list does not contain software having the distribution number r, i.e., if all software in the distribution software list has been referred to, then the flow advances to Step 600.
  • At Step 435, the update sequence management unit 190 refers to the software having the distribution number r in the distribution software list. At Step 440 the update sequence management unit 190 checks whether the reference software having the distribution number r is software already scheduled to install. If it is the software already scheduled to install, the flow returns to Step 425, whereas if not, the flow advances to Step 445. At Step 445 the update sequence management unit 190 checks whether the reference software is already possessed or not, by referring to the terminal information table 162 and checking whether the table contains software having the same name.
  • The terminal information table 162 will be described. FIG. 8 shows a terminal information table 162. The terminal information table 162 stores therein: a navi type number 805 representative of a type number of the terminal apparatus 150; an application name (including a version) 810 of an application possessed by the terminal apparatus 150; a driver name (including a version) 815 of a driver possessed by the terminal apparatus 150; a plug-in name (including a version) 820 of a plug-in possessed by the terminal apparatus 150; and a map data name (including a version) 825 of map data possessed by the terminal apparatus 150.
  • If it is determined at Step 445 that the reference software has been possessed already, the flow returns to Step 425, whereas if it is determined that the reference software is not still possessed, the flow advances to Step 450.
  • At Step 450 the update sequence management unit 190 checks whether the reference software is compatible with the terminal apparatus 150, by referring to the compatible apparatus 735 in the distribution software list and the navi type number 805 in the terminal information table 162. If the software is compatible with the terminal apparatus 150, the flow advances to Step 500, whereas if not, the flow returns to Step 425.
  • From Step 500 to Step 525, the update sequence management unit 190 extracts relevant software necessary for installing the reference software and determines the installation order of the reference software and relevant software.
  • A method of extracting relevant software will be described. The relevant software is a software group necessary for installing the reference software. Consider now, for example, the case wherein software “voice guide plug-in” in the distribution software list 700 is installed. FIG. 9 illustrates an example of extracting relevant software necessary for installing the software “voice guide plug-in”. In installing software “voice guide plug-in” 900, compatible software necessary for running the “voice guide plug-in” 900 is checked by referring to the terminal information table 162 and checking whether the compatible software is already possessed. If it is already possessed, it is not necessary to install the relevant software, whereas if not possessed, the present software is required to be changed to the compatible software with version-up. Therefore, in order to search up-data for version-up, the compatible software is detected from the software name 730 after update in the distribution software list 700. The compatible software “navigator Ver. 4.0 or higher” for the “voice guide plug-in” 900 is not written in the terminal information table 162. Therefore, from the software name 730 after update in the distribution software list 700, software “navigator Ver. 5.0” and “navigator Ver. 4.0” is detected.
  • Software necessary for updating to “navigator Ver. 5.0” is “navigator up-data Ver. 5.0” 905 and software necessary for updating to “navigator Ver. 4.0” is “navigator up-data Ver. 4.0” 910. It is checked whether these pieces of software 905 and 910 can be installed or not. First, compatible apparatuses with the software “navigator up-data Ver. 5.0” 905 and “navigator up-data Ver. 4.0” 910 are checked. Since the compatible apparatus with “navigator up-data Ver. 5.0” ” is “Navi300”, this software cannot be installed. Since the compatible apparatus with “navigator up-data Ver. 4.0” is either “Navi3000” or “Navi2000”, this software can be installed. Next, the compatible software with “navigator up-data Ver. 4.0” 910 is checked. From the distribution software list 700, it can be understood that the compatible software with “navigator up-data Ver. 4.0” 910 is “navi driver Ver. 4.0”. It is checked from the terminal information table 162 whether the navi driver Ver. 4.0” is already possessed. Since the driver “navi driver Ver. 4.0” is not still possessed, up-data necessary for driver version-up is searched. Namely, “navi driver Ver. 4.0” is detected from the software name 730 after update in the distribution software list 700.
  • Next, “driver up-data Ver. 4.0” 920 for updating to “navi driver ver. 4.0” is checked. From the distribution software list 700, it can be understood that the compatible apparatus with “driver up-data Ver. 4.0” 920 is either “Navi2000” or “Navi3000”. It can therefore be understood that the terminal apparatus is compatible. It can then be understood that the compatible software is not required to use additional software necessary for running. It can further be understood that the software before update “navi driver Ver. 3.0” is written in the terminal information table 162, i.e., it is already possessed. From the above checks, it can be understood that “driver up-date Ver. 4.0” can be updated.
  • Next, “navigator up-date Ver. 4.0” 910 is again checked to confirm the software before update “navigator up-date Ver. 4.0” 910. The software before update “navigator Ver. 3.0” for “navigator up-date Ver. 4.0” 910 is not written in the terminal information table 162. Therefore, “navigator Ver. 3.0” is detected from the software name 730 after update in the distribution software list 700.
  • Then, “navigator up-date Ver. 3.0” 915 necessary for updating to “navigator Ver.3.0” is checked. From the distribution software list 700, it can be understood that the compatible apparatus with “navigator up-date Ver. 3.0” 915 is either “Navi2000” or “Navi3000” and that the apparatus is compatible. Since the “driver up-data Ver. 4.0” already scheduled to install can update the present driver to the compatible software “navi driver Ver. 4.0”, it can be understood that the driver software is compatible. The software name before update “navigator Ver. 2.0” of “navigator up-date Ver. 3.0” 915 is written in the terminal information table, i.e., this software is already possessed. From the above checks, it can be understood that “navigator up-date Ver. 3.0” 915 can be installed.
  • Since “navigator up-date Ver. 4.0” 905 can be installed as described above, “voice guide plug-in” 900 can also be installed.
  • Next, the installation order of relevant software will be described. The relevant software is sequentially installed from the most downstream side of software searched in a chain manner toward the reference software. In the case of “voice guide plug-in”, for example, the installation order from the earliest becomes as in the following:
      • (1) “driver up-data Ver. 4.0”, 920;
      • (2) “navigator up-data Ver. 3.0” 915;
      • (3) “navigator up-data Ver. 4.0”, 910; and
        as the last reference software,
      • (4) “voice guide plug-in” 900.
  • Similarly, consider the case wherein “map data '99 version” is installed. FIG. 10 illustrates an example of extracting relevant software necessary for installing “map data '99 version”.
  • In installing “map data '99 version” 1000, compatible software necessary for running the “map data '99 version” 1000 is checked by referring to the compatible software name 740 in the distribution software list 700. The compatible software with “map data '99 version” is either “navigator Ver. 5.0” or “navigator Ver. 4.0”. The compatible apparatus with “navigator Ver. 5.0” is “Navi3000” so that the terminal apparatus is not compatible. However, “navigator Ver. 4.0” is software scheduled to install when “voice guide plug-in” 900 is installed. Therefore, “map data '99 version” 1000 can be installed.
  • Relevant software necessary for installing the reference software is extracted in a chain manner as described above, and thereafter the reference software is installed from Step 500 to Step 525.
  • First, at Step 500 the update sequence management unit 190 checks relevant software necessary for the reference software. If it is determined at Step 505 that the relevant software is all software already scheduled to install or software already possessed, the flow advances to Step 525, whereas if there is relevant software to be installed, the flow advances to Step 510. At Step 510 the update sequence management unit 190 checks whether the relevant software group can be installed or not, by checking the compatible software 740 of the distribution software list 700 and the terminal information table 162. Next, at Step 515 it is determined whether the relevant software group can be installed or not, by extracting the relevant software in the chain manner. In this case, it is also checked whether the total data amount of the software group to be installed is smaller than the capacity of the software temporary storage unit 185, by checking the software data size 745 written in the distribution software list 700. Namely, if the software can be stored in terms of capacity, it can be installed, whereas if not, it cannot be installed. If it is determined that the software can be installed, the flow advances to Step 520, whereas if not, i.e., if the relevant software group is collected insufficiently, the flow returns to Step 425. At Step 520 the update sequence management unit 190 determines the installation order of the relevant software group necessary for installing the reference software, in the manner described earlier. As described earlier, it is assumed herein that the relevant software is sequentially installed from the most downstream side of software searched in a chain manner toward the reference software. Next, at Step 525 the update sequence management unit 190 determines the installation order of the reference software. In this example, the installation order of the reference software is set to the next order to the installation orders of the relevant software determined at Step 520. Thereafter, the flow returns to Step 425.
  • The flow from Step 420 to Step 525 will be described more in detail with reference to the distribution software list 700.
  • First, software “Internet browser Ver. 1.0” having the distribution number (1) of the distribution software list 700 is referred to, which is determined as capable of being installed and given a first installation order. Next, “3D viewer plug-in” having the distribution number (2) is referred to, which is already possessed and not installed. Next, “voice guide line plug-in” having the distribution number (3) is referred to, for which the relevant software is extracted in the chain manner as described above. Therefore, the second installation order is given to “driver up-data Ver. 4.0”, the third installation order is given to “navigator up-data Ver. 3.0”, the fourth installation order is given to “navigator up-data Ver. 4.0”, and the fifth installation order is given to “voice guide plug-in”. Next, “map data '99 version” having the distribution number (4) is referred to. Since the relevant software “navigator Ver. 4.0” is already scheduled to install, the sixth installation order is given to “map data '99 Version”. Next, “driver up-data Ver. 5.0” having the distribution number (5) is referred to, with which the terminal equipment is not compatible so that it is not installed. Next, “navigator up-data Ver. 5.0” having the distribution number (6) is referred to, with which the terminal equipment is not compatible so that it is not installed. Next, “driver up-data Ver. 4.0” having the distribution number (7) is referred to, which is already scheduled to install so that it is not given a new installation order. Similarly, “navigator up-data Ver. 4.0” having the distribution number (8) to be referred next is already scheduled to install so that it is not given a new installation order.
  • Since “navi driver Ver. 3.0” is already updated, “driver up-data Ver. 3.0” having the distribution number (9) to be referred next, is not installed. Since “navigator up-data Ver. 3.0” having the distribution number (10) to be referred next is already scheduled to install, a new installation order is not given. Since the terminal apparatus 150 has updated software for “driver up-data Ver. 2.0” having the distribution number (11) and “navigator up-data Ver. 2.0” having the distribution number (12), these two pieces of software are not installed.
  • With the above process, at Step 530 the update sequence management unit 190 forms an installation sequence table writing the installation sequence. FIG. 11 shows an installation sequence table. The installation sequence table 1100 has an installation order 1105 and a name 1110 of software to be installed. The contents of the installation sequence table 1100 for the distribution software list 700 are:
      • 1st: “Internet browser Ver. 1.0”
      • 2nd: “driver up-data Ver. 4.0”
      • 3rd: “navigator up-data Ver. 3.0”
      • 4th: “navigator up-data Ver. 4.0”
      • 5th: “sound guide plug-in”
      • 6th: “map data 99′ version”
        This installation sequence table is managed by the update sequence management unit 190.
  • Next, a software distribution process at the station 100 and a software reception process at the terminal apparatus 150 will be described. First, the process at the station 100 will be described.
  • At Step 315 the distribution software encryption unit 110 enciphers a distribution software group by using a cipher key in order for the third party not to tap the software. The cipher key information necessary for encryption is informed in advance to a user of the terminal apparatus 150. A user inputs in advance this cipher key information to the input unit 175 of the terminal apparatus 150. In this way, the terminal apparatus 150 can decipher the enciphered software. Next, at Step 320 the distribution side communication unit 115 distributes the software group enciphered at Step 315.
  • Next, the process at the terminal apparatus 150 will be described.
  • In the process from Step 600 to Step 620, a software group necessary for installation is received from software distributed from the station 100, in accordance with the installation sequence table 1100, and deciphered.
  • At Step 600 the terminal side control unit 180 determines from the received distribution software list whether the distribution end time has lapsed, i.e., whether all software has been transmitted. If transmitted, the flow advances to Step 655 whereat the display unit 197 displays a message indicating “distribution end” to thereafter follow Step 665. If not transmitted, the flow advances to Step 605.
  • At Step 605 the terminal side communication unit 155 receives the software distributed from the station 100.. Next, at Step 610 the update sequence management unit 190 determines whether the software received at Step 605 is the software written in the installation sequence table. If so, the flow advances to Step 615, whereas if not, the flow returns to Step 600.
  • At Step 615 the decryption unit 170 deciphers the software written in the received installation sequence table, and the deciphered software is temporarily stored in the software temporary storage unit 185. Next, at Step 620 the terminal side control unit 180 checks whether all software necessary for installation written in the installation sequence table has been received. If not, the flow returns to Step 600, whereas if received, the flow advances to Step 625.
  • In the process from Step 625 to Step 650, the navigation unit 195 installs the received software in the navigation unit 195 in accordance with the installation sequence table.
  • At Step 625 the software possessed by the navigation unit 195 before the installation is backed up in the software temporary storage unit 185 in order for the software recovery unit 165 to recover the state of software before the installation in case the installation is failed.
  • Next, at Step 630 the software update unit 160 installs the software received by the process from Step 600 to Step 620 in the navigation unit 195, in accordance with the installation order written in the installation sequence table.
  • Next, at Step 635 the update sequence management unit 190 determines whether the software installation at Step 630 has succeeded. If succeeded, the flow advances to Step 650 whereat the display unit 197 displays a message “update success” to thereafter follow Step 660. If the installation failed, the flow advances to Step 640.
  • At Step 640, in order to recover the state of the software in the navigation unit 195 before the installation, the software recovery unit 165 installs the software before update backed up in the software temporary storage unit 185, in the navigation unit 195. At Step 645 the display unit 197 displays a message “update failure” to thereafter follow Step 660.
  • At Step 660 the terminal side communication unit 155 transmits the updated contents of the software of the navigation unit 195, i.e., the software name and version, to the station 100 to thereafter follow Step 665. On the side of the station 100, at Step 325 the distribution side communication unit 115 receives the updated contents transmitted from the terminal apparatus 150. The updated contents are managed by the update contents management unit 130. In this manner, the updated contents at each terminal apparatus can be recognized.
  • At Step 665 the terminal side control unit 150 enters the standby mode in order to suppress the power consumption at the terminal apparatus 150, to thereafter return to Step 405.
  • In this embodiment, software is distributed by using the satellite. Software may be distributed by using a digital ground wave broadcasting station. In this case, portable telephones, PHSes or the like are used for communications between terminal apparatuses and the digital ground wave broadcasting station.
  • As described above, during automatic update of a software group at each terminal apparatus, a plurality piece of relevant software can be updated without any dependency problem.
  • Next, the second embodiment of the invention will be described with reference to FIGS. 12 to 18. FIG. 12 shows the structure of a system according to the second embodiment of the invention. In this embodiment, upon an update information transmission request from a user, information on hardware and software of a terminal apparatus or car navigation terminal apparatus in a vehicle is transmitted to a software management center via a satellite distribution system capable of transmitting and receiving radio waves in the zenith direction. In accordance with the information on hardware and software of the car navigation terminal apparatus, the software management center selects a software group to be updated and calculates an installation order or update sequence in order to ensure the installation without any dependency problem. The software management center transmits the selected software group and the calculated update sequence to the car navigation terminal apparatus via the satellite distribution system capable of transmitting and receiving radio waves in the zenith direction. The car navigation terminal apparatus temporarily stores the received information. Upon an update request from the user, the software is updated by using the temporarily stored software and update sequence.
  • This system has a software management center 1200 and a car navigation terminal apparatus 1250. In accordance with information on hardware and software of the car navigation terminal apparatus 1250 received from the apparatus, the software management center 1200 selects a software group necessary for updating the software of the car navigation terminal apparatus 1250 and calculates an update sequence of the software group to ensure installation without any dependence problem. Thereafter, the software management center 1200 transmits the selected software group and calculated update sequence. The terminal apparatus 1250 transmits information on its hardware and software to the software management center 1200 and receives the software group necessary for update and the update sequence sent from the software management center 1200 to update the software of the terminal apparatus 1250.
  • The software management center 1200 has: a distribution side communication unit 115 for transmitting software used for updating software of the terminal apparatus 1250 and an update sequence table for updating the software and for receiving the name and version of hardware and software of the terminal apparatus 1250 transmitted therefrom; an update software database 120 for storing software necessary for updating the software of the terminal apparatus 1250; an update software management unit 1205 for managing an update software list of the software stored in the update software database 120; an update sequence management unit 190 for selecting a necessary software group in accordance with the update software list of the software stored in the update software database 120 and managing the update sequence of the selected software group; and a distribution side control unit 105 for issuing a transmission command to the distribution side communication unit 115 and managing the whole control flow.
  • The update software list is generally the same as the distribution software list of the first embodiment. The different point is that the item “software distribution time” in the distribution software list is excluded. The update software list writes the following items:
      • (1) a distribution number sequentially and uniquely assigned to each piece of software, starting from “1”;
      • (2) a name of software;
      • (3) an installation type indicating whether the software is update software or new software;
      • (4) a name (including a version) of software updated by distribution software (up-data);
      • (5) a name (including a version) of software to be updated by distribution software (up-data); and
      • (6) an apparatus compatible with installation software and compatible software.
  • The terminal apparatus 1250 has: a navigation unit 195 for searching necessary map information, displaying a map, and displaying a present location of the user; a software update unit 160 for updating software of the navigation unit 195; a terminal side communication unit 155 for receiving software and an update sequence list transmitted from the software management center 1250; a software temporary storage unit 185 for temporarily storing software received at the terminal side communication unit 155; a software decryption unit 165 for recovering the original software of the navigation unit 195 once updated by the software update unit 160; an input unit 175 for manipulating a button for transmitting a software update request to the software management center 1200 and manipulating a button for starting software update; a display unit 197 for displaying map information or search information; and a terminal side control unit 180 for issuing a software update command to the software update unit 160, and issuing a software recovery command to the software recovery unit 170.
  • FIGS. 16 to 18 show display windows of the display unit 197 used for a software update work. The software update work includes an “update software acquisition mode” and a “software update mode”. In the “update software acquisition mode”, information on hardware and software of the terminal apparatus 1250 is transmitted to the software management center 1200, and a software group necessary for the update and an update sequence table are received from the software management center 1200. In the “software update mode”, the software of the terminal apparatus 1250 is updated. FIG. 16 is a display window first displayed when an update request is transmitted to the software management center 1200 in the “update software acquisition mode”. FIG. 17 is a display window displayed while the update request is transmitted in the “update software acquisition mode”, i.e., while the software management center 1200 selects a necessary software group and calculates an update sequence. FIG. 18 is a display window displayed when software is updated in the “software update mode”.
  • FIGS. 13 to 15 are flow charts illustrating the operation of the second embodiment of the invention. FIG. 13 is a flow chart illustrating the operation to be executed by the software management center 1250. FIG. 14 is a flow chart illustrating the operation to be executed by the terminal apparatus 1250 during the “update software acquisition mode”. FIG. 15 is a flow chart illustrating the operation to be executed by the terminal apparatus 1250 during the “software update mode”.
  • When a user wishes to update software, the user makes the input unit 175 display the display window 1600 for the “update software acquisition mode”. In order to display the display window 1600, the user makes the input unit 175 display a mode setting dialog 1630 to be used for setting a mode, and in this state, an update software acquisition mode item 1640 is selected. In this manner, the display window 1600 is displayed.
  • The display window 1600 has an update request button 1610 for transmitting a software update request to the software management center 1600 and a cancel button 1620 for cancelling the software update process. When the user designates either the update request button 1610 or cancel button 1620, the flow starts at Step 1400.
  • At Step 1400 a start process of starting the “update software acquisition mode” for the terminal apparatus is executed. Next, at Step 1405 it is determined which one of the update request button 1610 and cancel button 1620 is designated. If the update request button 1610 is designated, the flow advances to step 1410, whereas if the cancel button 1620 is designated, the flow advances to Step 1425. At Step 1410 the terminal communication unit 155 transmits the names and versions of hardware and software possessed by the terminal apparatus and written in the terminal information table 162, to the software management center 1200 via the satellite capable of transmitting and receiving radio waves in the zenith direction. By using such a satellite, a user can transmit necessary information even in an urban district where influence of buildings is susceptible and in a rural district where a dead zone of portable telephones is broad, so long as the user can see the sky.
  • On the side of the software management center 1200, reception of information from the terminal apparatus is prepared at Step 1300. At Step 1305 the distribution side communication unit 115 continues a polling operation until the software update request is issued from a terminal apparatus. If an update request is received at Step 1305, the flow advances to Step 1310 whereat the distribution side communication unit 115 receives the names and versions of hardware and software written in the terminal information table 162 and transmitted from the terminal apparatus 1250. Next, at Steps 1315 and 1320, in accordance with the update software list managed by the update software management unit 1205, the update sequence management unit 190 selects a software group necessary for updating the software of the terminal apparatus 1250 and calculates an update sequence to ensure the update by the selected software group without any dependence problem, i.e., calculates an installation sequence table. The process of selecting a software group and the process of calculating the update sequence are the same as those corresponding processes of the first embodiment (from Step 420 to Step 530). The update software list management unit 1205 updates the update software list each time the contents of the distribution software database 120 are updated.
  • Next, at Step 1325 the distribution side communication unit 115 transmits the software group necessary for update selected by the update sequence management unit 190 and the install sequence table writing the update sequence of the selected software group, to the terminal apparatus 1250 via the satellite capable of transmitting and receiving radio waves in the zenith direction. Thereafter, the flow returns to Step 1305 to continue the polling operation for a new update request.
  • Next, on the side of the terminal apparatus 1250, at Step 1415 the terminal side communication unit 155 receives the update software group and installation sequence table necessary for updating the software of the terminal apparatus 1250. During the process from Step 1410-to Step 1415, the display window 1700 is displayed on the display unit 197, the display window indicating the state of under transmission of an update request (i.e., during the process of selecting the necessary software group and the process of calculating the update sequence, respectively by the software management center 1200). A message indicating “under transmission” is displayed in the display window 1700.
  • Next, at Step 1420 the received update software group and installation sequence table are stored in the software temporary storage unit 185. At Step 1425 the terminal side control unit 180 executes an “update software acquisition mode” end process.
  • After the terminal side control unit 180 executes an “update software acquisition mode” end process, the terminal side control unit 180 starts the process for the “software update mode” and the display window 1800 is displayed on the display unit 197.
  • The display window 1800 displays the reception contents (contents 1830 stored in the software temporary storage unit 185) and has a software update start button 1810 for starting the update of the software of the terminal apparatus 1250 and a cancel button 1820 for cancelling the update of the software.
  • The start process for the “software update mode” by the terminal side control unit 180 is executed at Step 1500. Next, at Step 1505 it is determined which one of the software update button 1810 and cancel button 1820 was designated by the user by using the input unit 175. If the software update start button 1810 is designated, the flow advances to Step 1510, whereas the cancel button 1820 is designated, the flow advances to Step 1545.
  • If it is determined at Step 1505 that the cancel button was designated, the update process is terminated and an end process is executed at Step 1545. However, a user may display the mode setting dialog 1630 and select the “software update mode” 1650 by using the input unit 175, to call again the installation process. In this case, the received software group and installation sequence table stored in the software temporary storage unit 185 are used for updating the software of the terminal apparatus 1250. In this manner, either the case wherein the user wishes to use the car navigation terminal apparatus immediately after the reception end or the case wherein the user wishes not to update the software immediately after the reception end, can be dealt with.
  • At Step 1510 the software possessed by the navigation unit 195 before the installation is backed up in the software temporary storage unit 185 in order for the software recovery unit 165 to recover the state of software before the installation in case the installation is failed.
  • Next, at Step 1515 the software update unit 160 installs the software group stored in the software temporary storage unit 185, in the navigation unit 195, in accordance with the installation sequence in the installation sequence table stored in the software temporary storage unit 185.
  • Next, at Step 1520 the software update unit 160 determines whether the software update at Step 1515 has succeeded. If succeeded, the flow advances to Step 1525, whereas if failed, the flow advances to Step 1535.
  • If succeeded, at Step 1525 the software name and version of the updated software are written in the terminal information table 162. At Step 1530 a message “update success” is displayed on the display unit 197.
  • If failed, at Step 1535, in order to recover the state of the software in the navigation unit 195 before the update, the software recovery unit 165 installs the software before update backed up in the software temporary storage unit 185, in the navigation unit 195. At Step 1540 the display unit 197 displays a message “update failure” to thereafter follow Step 1545.
  • At Step 1545 the terminal side control unit 180 executes an end process for the “software update mode”.
  • As described above, during automatic update of a software group at each terminal apparatus, a plurality piece of relevant software can be updated without any dependency problem. Further, the software management center is provided with the update sequence management unit so that the circuit of the terminal apparatus can be simplified. Since the software temporary storage unit for temporarily storing a software group necessary for the update is provided, a user can update the software at any time the user desires.
  • According to the first and second embodiments, an update sequence management means is provided for extracting up-data in a chain manner necessary for updating software and managing the update sequence of the extracted up-data. Therefore, a plurality piece of relevant software can be updated without any dependency problem.
  • Updating is possible even if a user has no highly sophisticated technical knowledge.
  • Even if there occurs any trouble during updating, a user without technical knowledge can recover the original state, which provides a high reliability.
  • An apparatus or system easy to use can be provided.

Claims (4)

1. A software update system comprising:
a station for distributing a distribution software list in advance of distributing a data group or a program group for a terminal apparatus by using a broadcasting system or a distribution system; and
the terminal apparatus for automatically updating a data group or a program group of the terminal apparatus by using the data group or program group distributed from the station and the distribution software list,
wherein said distribution software list describes therein a name of the program group or data group to be distributed, a distribution time of the program group or data group to be distributed, a name of compatible software necessary for operation of a program or data of the program group or data group, a name of a program or data of the program group or data group before update, and a name of a program or data of the program group or data group after update.
2. A software update system according to claim 1, wherein said station includes a reception unit for receiving update contents of software for said terminal apparatus transmitted therefrom, and an update contents management unit for managing the update contents of the software for said terminal apparatus.
3. A software update system according to claim 1, wherein said station further includes a distribution unit for distributing software to said terminal apparatus along a zenith direction.
4. A software update system according to claim 1, wherein map information, navigation software, or system software of a vehicle information terminal is updated.
US10/843,487 1999-08-31 2004-05-12 Software distribution system and software receiving terminal apparatus Abandoned US20050050538A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP11-244787 1999-08-31
JP24478799A JP2001067232A (en) 1999-08-31 1999-08-31 Distribution system and receiving terminal device for software
US09/648,451 US6820259B1 (en) 1999-08-31 2000-08-28 Software distribution system and software receiving terminal apparatus
US10/843,487 US20050050538A1 (en) 1999-08-31 2004-05-12 Software distribution system and software receiving terminal apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10/843,487 US20050050538A1 (en) 1999-08-31 2004-05-12 Software distribution system and software receiving terminal apparatus

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/648,451 Continuation US6820259B1 (en) 1999-08-31 2000-08-28 Software distribution system and software receiving terminal apparatus

Publications (1)

Publication Number Publication Date
US20050050538A1 true US20050050538A1 (en) 2005-03-03

Family

ID=17123930

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/648,451 Active 2021-08-26 US6820259B1 (en) 1999-08-31 2000-08-28 Software distribution system and software receiving terminal apparatus
US10/843,487 Abandoned US20050050538A1 (en) 1999-08-31 2004-05-12 Software distribution system and software receiving terminal apparatus

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/648,451 Active 2021-08-26 US6820259B1 (en) 1999-08-31 2000-08-28 Software distribution system and software receiving terminal apparatus

Country Status (2)

Country Link
US (2) US6820259B1 (en)
JP (1) JP2001067232A (en)

Cited By (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020122068A1 (en) * 2001-03-01 2002-09-05 Taizo Tsuruoka Entertainment device, menu display method, and information recording medium
US20050044280A1 (en) * 1994-05-31 2005-02-24 Teleshuttle Technologies, Llc Software and method that enables selection of one of a plurality of online service providers
US20050132351A1 (en) * 2003-12-12 2005-06-16 Randall Roderick K. Updating electronic device software employing rollback
US20060009217A1 (en) * 2004-06-28 2006-01-12 Christoffer Lunden System and method for product registration and activation
US20060048134A1 (en) * 2004-08-31 2006-03-02 Microsoft Corporation Multiple patching
US20060048130A1 (en) * 2004-08-31 2006-03-02 Microsoft Corporation Patch sequencing
US20060048129A1 (en) * 2004-08-31 2006-03-02 Microsoft Corporation Patch un-installation
US20060048131A1 (en) * 2004-08-31 2006-03-02 Microsoft Corporation Elevated patching
US20060112152A1 (en) * 2004-11-22 2006-05-25 Microsoft Corporation Smart patching by targeting particular prior versions of a file
US20060265696A1 (en) * 2005-05-23 2006-11-23 International Business Machines Corporation Method and system for data migration between versions of software
US20070038991A1 (en) * 2005-08-10 2007-02-15 Cisco Technology, Inc. Method and apparatus for managing patchable software systems
US20080028395A1 (en) * 2006-07-27 2008-01-31 Giovanni Motta User Experience And Dependency Management In A Mobile Device
US20080046371A1 (en) * 2006-08-21 2008-02-21 Citrix Systems, Inc. Systems and Methods of Installing An Application Without Rebooting
US20080175372A1 (en) * 2000-11-17 2008-07-24 Jeffrey Brunet Operator network that routes customer care calls based on subscriber / device profile and csr skill set
US20080301670A1 (en) * 2007-05-31 2008-12-04 Microsoft Corporation Content distribution infrastructure
US20090045922A1 (en) * 2007-08-16 2009-02-19 James Kosecki Data collection system having EIR terminal interface node
US20090094378A1 (en) * 2007-10-09 2009-04-09 Microsoft Corporation Software Deployment Using Client Location
CN101421586A (en) * 2006-09-01 2009-04-29 爱信艾达株式会社;丰田自动车株式会社 Map updating system
US20090118941A1 (en) * 2007-11-05 2009-05-07 Gm Global Technology Operations, Inc. Method and apparatus for dynamic output torque limiting for a hybrid powertrain system
US20090125900A1 (en) * 2007-11-14 2009-05-14 Continental Teves, Inc. Systems and Methods for Updating Device Software
US20090247145A1 (en) * 2008-03-28 2009-10-01 Samsung Electronics Co., Ltd. Method and apparatus for software update of terminals in a mobile communication system
US20090288071A1 (en) * 2008-05-13 2009-11-19 Microsoft Corporation Techniques for delivering third party updates
US20110113422A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Programmatic Creation Of Task Sequences From Manifests
US20110113070A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Software Stack Building Using Logically Protected Region Of Computer-Readable Medium
US20110113418A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Cross-Updating Of Software Between Self-Service Financial Transaction Machines
US20110113416A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Network-Enhanced Control Of Software Updates Received Via Removable Computer-Readable Medium
US20110113424A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Distribution Of Software Updates
US20110113415A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Multiple Invocation Points In Software Build Task Sequence
US20110113413A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Software Updates Using Delta Patching
US20110238572A1 (en) * 2010-03-25 2011-09-29 Bank Of America Corporation Remote Control Of Self-Service Terminal
US20120264376A1 (en) * 1997-10-22 2012-10-18 American Vehicular Sciences Llc Information Transmittal Techniques for Vehicles
US20130159996A1 (en) * 2011-12-16 2013-06-20 Hsiu-Ping Lin Systems for downloading location-based application and methods using the same
US8539123B2 (en) 2011-10-06 2013-09-17 Honeywell International, Inc. Device management using a dedicated management interface
US8555273B1 (en) * 2003-09-17 2013-10-08 Palm. Inc. Network for updating electronic devices
US8578361B2 (en) 2004-04-21 2013-11-05 Palm, Inc. Updating an electronic device with update agent code
US8621123B2 (en) 2011-10-06 2013-12-31 Honeywell International Inc. Device management using virtual interfaces
US8677348B1 (en) 2005-10-17 2014-03-18 Cisco Technology, Inc. Method and apparatus for determining least risk install order of software patches
DE102012023647A1 (en) 2012-12-03 2014-06-05 Audi Ag Method for updating stored data to control device of motor vehicle, has activating specific vehicle mode in depending on type of control devices when mistake in form of incorrect transfer of data or storage of data is determined
US8893110B2 (en) 2006-06-08 2014-11-18 Qualcomm Incorporated Device management in a network
US20150007157A1 (en) * 2013-06-28 2015-01-01 Samsung Electronics Co., Ltd. Method and apparatus for updating application
US9497092B2 (en) 2009-12-08 2016-11-15 Hand Held Products, Inc. Remote device management interface
US9740465B1 (en) 2016-11-16 2017-08-22 Vector Launch Inc. Orchestration of software application deployment in a satellite platform
US9740473B2 (en) 2015-08-26 2017-08-22 Bank Of America Corporation Software and associated hardware regression and compatibility testing system
US9819742B1 (en) 2017-07-19 2017-11-14 Vector Launch Inc. Bandwidth aware state transfer among satellite devices
US20170329599A1 (en) * 2016-05-11 2017-11-16 Hyundai Motor Company System and method for providing software updates
US9960837B1 (en) 2017-07-19 2018-05-01 Vector Launch Inc. Pseudo-geosynchronous configurations in satellite platforms
US9991951B2 (en) 2016-10-19 2018-06-05 Vector Launch Inc. Peer state transfer among satellite devices
US9998207B1 (en) 2017-07-19 2018-06-12 Vector Launch Inc. Orbital network layering in satellite platforms
US10021509B2 (en) 2016-03-25 2018-07-10 At&T Mobility Ii Llc Methods and apparatus to provide an update via a satellite connection
US10069935B1 (en) 2017-07-19 2018-09-04 Vector Launch Inc. Role-specialization in clustered satellite platforms
US10084534B2 (en) 2016-10-19 2018-09-25 Vector Launch Inc. State transfer among virtualization-enabled satellite platforms

Families Citing this family (60)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU770741B2 (en) * 1999-12-08 2004-03-04 Japan Cash Machine Co., Ltd. Method and apparatus for renewing software in a software-operated machine
US20020026436A1 (en) * 2000-08-31 2002-02-28 Rafael Joory Supplanting application setup data and preserving the application setup data that has been supplanted
US8479189B2 (en) 2000-11-17 2013-07-02 Hewlett-Packard Development Company, L.P. Pattern detection preprocessor in an electronic device update generation system
EP1337917A4 (en) * 2000-11-17 2009-04-08 Hewlett Packard Development Co System and method for updating and distributing information
KR100813788B1 (en) * 2000-12-11 2008-03-13 주식회사 케이티 Method for Distributing of application software using by Mobile Communication System
US7574481B2 (en) * 2000-12-20 2009-08-11 Microsoft Corporation Method and system for enabling offline detection of software updates
US7418700B2 (en) * 2001-01-29 2008-08-26 Microsoft Corporation System and method to facilitate installation and/or removal of components
KR100400542B1 (en) * 2001-02-28 2003-10-08 엘지전자 주식회사 System software upgrade apparatus and method using advertisement for digital television
US8458689B2 (en) * 2001-03-30 2013-06-04 Roderick A. Barman Method and apparatus for reprogramming engine controllers
JP2002318692A (en) * 2001-04-19 2002-10-31 Sony Corp Installation support system, installation support device, installation support method, program for supporting installation and recording medium in which the same program is recorded
US6993760B2 (en) * 2001-12-05 2006-01-31 Microsoft Corporation Installing software on a mobile computing device using the rollback and security features of a configuration manager
US7409685B2 (en) 2002-04-12 2008-08-05 Hewlett-Packard Development Company, L.P. Initialization and update of software and/or firmware in electronic devices
JP4408033B2 (en) * 2002-09-24 2010-02-03 株式会社リコー Remote management system
WO2004034687A1 (en) * 2002-10-10 2004-04-22 Action Engine Corporation Method and apparatus for remote control and updating of wireless mobile devices
US7725889B2 (en) * 2003-01-13 2010-05-25 Hewlett-Packard Development Company, L.P. Mobile handset capable of updating its update agent
GB2402297B (en) * 2003-05-15 2005-08-17 Sun Microsystems Inc Update dependency control for multi-master replication
DE10340372A1 (en) * 2003-09-02 2005-03-24 Robert Bosch Gmbh A method of installing a program component
US7080279B2 (en) * 2003-12-03 2006-07-18 International Business Machines Corporation Autonomic rollback
US7574706B2 (en) * 2003-12-15 2009-08-11 Microsoft Corporation System and method for managing and communicating software updates
US7478381B2 (en) * 2003-12-15 2009-01-13 Microsoft Corporation Managing software updates and a software distribution service
US7546594B2 (en) * 2003-12-15 2009-06-09 Microsoft Corporation System and method for updating installation components using an installation component delta patch in a networked environment
US8526940B1 (en) 2004-08-17 2013-09-03 Palm, Inc. Centralized rules repository for smart phone customer care
JP2006099307A (en) * 2004-09-29 2006-04-13 Hitachi Ltd Method for installing application set in distribution server
JP4788128B2 (en) * 2004-11-10 2011-10-05 セイコーエプソン株式会社 Execution environment service system, execution environment maintenance unit and execution environment improvement methods
EP1739552A1 (en) * 2005-06-21 2007-01-03 Hewlett-Packard Development Company, L.P. Software installation method and computer system
US20070027971A1 (en) * 2005-07-26 2007-02-01 Sunil Marolia Device management network with notifications comprising multiple choice prompts
US7752651B2 (en) * 2005-09-26 2010-07-06 Bea Systems Inc. System and method for propagating security information in a web portal system
US7730477B2 (en) * 2005-09-26 2010-06-01 Bea Systems Inc. System and method for propagation in a web portal system
US7793285B2 (en) * 2006-03-31 2010-09-07 Ricoh Company, Ltd. Web installer driver and management through a remote network
US8170540B2 (en) * 2006-09-07 2012-05-01 Qualcomm Incorporated System and methods for remotely upgrading software applications
US8914786B2 (en) * 2007-03-23 2014-12-16 Zumobi, Inc. Systems and methods for controlling application updates across a wireless interface
US20090106749A1 (en) * 2007-10-23 2009-04-23 Wolfgang Daum System, method, and computer software code for determining whether a change in a subsystem is compatible with a system
US8332838B2 (en) * 2007-11-14 2012-12-11 Continental Automotive Systems, Inc. Systems and methods for updating device software
JP2010079546A (en) * 2008-09-25 2010-04-08 Hitachi Software Eng Co Ltd Program distribution updating system
JP2010166407A (en) * 2009-01-16 2010-07-29 Nippon Hoso Kyokai <Nhk> Device, device and program for obtaining program
DE102009018761A1 (en) 2009-04-27 2010-10-28 Bayerische Motoren Werke Aktiengesellschaft Method for updating software components
US8713557B2 (en) * 2009-06-25 2014-04-29 Ricoh Company, Ltd. Peer-to-peer method of deploying and managing executable code and associated plug-ins
US8739153B2 (en) * 2009-06-25 2014-05-27 Ricoh Company, Ltd. Centralized utility for automated retrieval, distribution/installation, and licensing management of software updates using peer-to-peer communication
JP5333035B2 (en) * 2009-08-12 2013-11-06 株式会社リコー Remote management system, management system, device, program updating method, program, and recording medium
JP5293522B2 (en) * 2009-09-14 2013-09-18 株式会社リコー Management system, management method, and management program
US8352803B2 (en) * 2010-06-07 2013-01-08 Alcatel Lucent Framework for managing failures in outbound messages
JP6143154B2 (en) * 2011-09-21 2017-06-07 Necエンジニアリング株式会社 Communication system, delivery device, the receiving device, communication method, and program
US8922393B2 (en) * 2011-11-16 2014-12-30 Flextronics Ap, Llc Parking meter expired alert
JP2014182571A (en) * 2013-03-19 2014-09-29 Denso Corp On-vehicle electronic control device program rewriting system and on-vehicle relay device
JP2014191641A (en) * 2013-03-27 2014-10-06 Fujitsu Ltd Installation program and installation method
JP2015232815A (en) * 2014-06-10 2015-12-24 カルソニックカンセイ株式会社 On-vehicle program updating device
US20160012401A1 (en) * 2014-07-08 2016-01-14 Navico Holding As Methods for Discovering and Purchasing Content for Marine Electronics Device
US9529580B2 (en) * 2015-01-21 2016-12-27 Ford Global Technologies, Llc Vehicle control update methods and systems
JP6361671B2 (en) * 2016-03-02 2018-07-25 住友電気工業株式会社 Program update system, a program updating method, a relay device and a computer program
US20180012197A1 (en) 2016-07-07 2018-01-11 NextEv USA, Inc. Battery exchange licensing program based on state of charge of battery pack
US9928734B2 (en) 2016-08-02 2018-03-27 Nio Usa, Inc. Vehicle-to-pedestrian communication systems
US20180127001A1 (en) 2016-11-07 2018-05-10 NextEv USA, Inc. Feedback Performance Control and Tracking
US10249104B2 (en) 2016-12-06 2019-04-02 Nio Usa, Inc. Lease observation and event recording
US10074223B2 (en) 2017-01-13 2018-09-11 Nio Usa, Inc. Secured vehicle for user use only
US9984572B1 (en) 2017-01-16 2018-05-29 Nio Usa, Inc. Method and system for sharing parking space availability among autonomous vehicles
US10031521B1 (en) 2017-01-16 2018-07-24 Nio Usa, Inc. Method and system for using weather information in operation of autonomous vehicles
US10286915B2 (en) 2017-01-17 2019-05-14 Nio Usa, Inc. Machine learning for personalized driving
US10234302B2 (en) 2017-06-27 2019-03-19 Nio Usa, Inc. Adaptive route and motion planning based on learned external and internal vehicle environment
US10369974B2 (en) 2017-07-14 2019-08-06 Nio Usa, Inc. Control and coordination of driverless fuel replenishment for autonomous vehicles
US10369966B1 (en) 2018-05-23 2019-08-06 Nio Usa, Inc. Controlling access to a vehicle using wireless access devices

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6115549A (en) * 1997-02-12 2000-09-05 Novell, Inc. Directory-services-based software distribution apparatus and method
US6199204B1 (en) * 1998-01-28 2001-03-06 International Business Machines Corporation Distribution of software updates via a computer network
US6230098B1 (en) * 1997-09-17 2001-05-08 Toyota Jidosha Kabushiki Kaisha Map data processing apparatus and method, and map data processing system
US6378127B1 (en) * 1998-09-21 2002-04-23 Microsoft Corporation Software installation and validation using custom actions
US6499109B1 (en) * 1998-12-08 2002-12-24 Networks Associates Technology, Inc. Method and apparatus for securing software distributed over a network

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH09218788A (en) * 1996-02-09 1997-08-19 Fujitsu Ltd Inservice direct down loading system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6115549A (en) * 1997-02-12 2000-09-05 Novell, Inc. Directory-services-based software distribution apparatus and method
US6230098B1 (en) * 1997-09-17 2001-05-08 Toyota Jidosha Kabushiki Kaisha Map data processing apparatus and method, and map data processing system
US6199204B1 (en) * 1998-01-28 2001-03-06 International Business Machines Corporation Distribution of software updates via a computer network
US6378127B1 (en) * 1998-09-21 2002-04-23 Microsoft Corporation Software installation and validation using custom actions
US6499109B1 (en) * 1998-12-08 2002-12-24 Networks Associates Technology, Inc. Method and apparatus for securing software distributed over a network

Cited By (112)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9484078B2 (en) 1994-05-31 2016-11-01 Intellectual Ventures I Llc Providing services from a remote computer system to a user station over a communications network
US20050044280A1 (en) * 1994-05-31 2005-02-24 Teleshuttle Technologies, Llc Software and method that enables selection of one of a plurality of online service providers
US9484077B2 (en) 1994-05-31 2016-11-01 Intellectual Ventures I Llc Providing services from a remote computer system to a user station over a communications network
US9111604B2 (en) 1994-05-31 2015-08-18 Intellectual Ventures I Llc Software and method that enables selection of on-line content from one of a plurality of network content service providers in a single action
US8407682B2 (en) * 1994-05-31 2013-03-26 Intellectual Ventures I Llc Software and method that enables selection of one of a plurality of online service providers
US8812620B2 (en) 1994-05-31 2014-08-19 Intellectual Property I LLC Software and method that enables selection of one of a plurality of online service providers
US8499030B1 (en) 1994-05-31 2013-07-30 Intellectual Ventures I Llc Software and method that enables selection of one of a plurality of network communications service providers
US8719339B2 (en) 1994-05-31 2014-05-06 Intellectual Ventures I Llc Software and method that enables selection of one of a plurality of online service providers
US8635272B2 (en) 1994-05-31 2014-01-21 Intellectual Ventures I Llc Method for distributing a list of updated content to a user station from a distribution server wherein the user station may defer installing the update
US20120264376A1 (en) * 1997-10-22 2012-10-18 American Vehicular Sciences Llc Information Transmittal Techniques for Vehicles
US8892271B2 (en) * 1997-10-22 2014-11-18 American Vehicular Sciences Llc Information Transmittal Techniques for Vehicles
US20080175372A1 (en) * 2000-11-17 2008-07-24 Jeffrey Brunet Operator network that routes customer care calls based on subscriber / device profile and csr skill set
US8848899B2 (en) 2000-11-17 2014-09-30 Qualcomm Incorporated Operator network that routes customer care calls based on subscriber / device profile and CSR skill set
US20020122068A1 (en) * 2001-03-01 2002-09-05 Taizo Tsuruoka Entertainment device, menu display method, and information recording medium
US8555273B1 (en) * 2003-09-17 2013-10-08 Palm. Inc. Network for updating electronic devices
US20050132351A1 (en) * 2003-12-12 2005-06-16 Randall Roderick K. Updating electronic device software employing rollback
US8578361B2 (en) 2004-04-21 2013-11-05 Palm, Inc. Updating an electronic device with update agent code
US20060009217A1 (en) * 2004-06-28 2006-01-12 Christoffer Lunden System and method for product registration and activation
US20060048131A1 (en) * 2004-08-31 2006-03-02 Microsoft Corporation Elevated patching
US20060048134A1 (en) * 2004-08-31 2006-03-02 Microsoft Corporation Multiple patching
US7552431B2 (en) 2004-08-31 2009-06-23 Microsoft Corporation Multiple patching in a single installation transaction
US7552430B2 (en) * 2004-08-31 2009-06-23 Microsoft Corporation Patch sequencing
US20060048130A1 (en) * 2004-08-31 2006-03-02 Microsoft Corporation Patch sequencing
US7703090B2 (en) 2004-08-31 2010-04-20 Microsoft Corporation Patch un-installation
US7747998B2 (en) 2004-08-31 2010-06-29 Microsoft Corporation Elevated patching
US20060048129A1 (en) * 2004-08-31 2006-03-02 Microsoft Corporation Patch un-installation
US20060112152A1 (en) * 2004-11-22 2006-05-25 Microsoft Corporation Smart patching by targeting particular prior versions of a file
US20060265696A1 (en) * 2005-05-23 2006-11-23 International Business Machines Corporation Method and system for data migration between versions of software
US7861239B2 (en) * 2005-05-23 2010-12-28 International Business Machines Corporation Data migration between versions of software
US20070038991A1 (en) * 2005-08-10 2007-02-15 Cisco Technology, Inc. Method and apparatus for managing patchable software systems
US7870547B2 (en) * 2005-08-10 2011-01-11 Cisco Technology, Inc. Method and apparatus for managing patchable software systems
US8677348B1 (en) 2005-10-17 2014-03-18 Cisco Technology, Inc. Method and apparatus for determining least risk install order of software patches
US8893110B2 (en) 2006-06-08 2014-11-18 Qualcomm Incorporated Device management in a network
US9081638B2 (en) 2006-07-27 2015-07-14 Qualcomm Incorporated User experience and dependency management in a mobile device
US8752044B2 (en) 2006-07-27 2014-06-10 Qualcomm Incorporated User experience and dependency management in a mobile device
US20080028395A1 (en) * 2006-07-27 2008-01-31 Giovanni Motta User Experience And Dependency Management In A Mobile Device
US20080046371A1 (en) * 2006-08-21 2008-02-21 Citrix Systems, Inc. Systems and Methods of Installing An Application Without Rebooting
US8769522B2 (en) * 2006-08-21 2014-07-01 Citrix Systems, Inc. Systems and methods of installing an application without rebooting
US20090172031A1 (en) * 2006-09-01 2009-07-02 Aisin Aw Co., Ltd. Map Updating System
US8392367B2 (en) 2006-09-01 2013-03-05 Aisin Aw Co., Ltd. Map updating system
CN101421586A (en) * 2006-09-01 2009-04-29 爱信艾达株式会社;丰田自动车株式会社 Map updating system
US20080301670A1 (en) * 2007-05-31 2008-12-04 Microsoft Corporation Content distribution infrastructure
US8762984B2 (en) 2007-05-31 2014-06-24 Microsoft Corporation Content distribution infrastructure
US20090045922A1 (en) * 2007-08-16 2009-02-19 James Kosecki Data collection system having EIR terminal interface node
US8025233B2 (en) 2007-08-16 2011-09-27 Hand Held Products, Inc. Data collection system having EIR terminal interface node
US9929906B2 (en) 2007-08-16 2018-03-27 Hand Held Products, Inc. Data collection system having EIR terminal interface node
US8925818B2 (en) 2007-08-16 2015-01-06 Hand Held Products, Inc. Data collection system having EIR terminal interface node
US8297508B2 (en) 2007-08-16 2012-10-30 Hand Held Products, Inc. Data collection system having EIR terminal interface node
US9509801B2 (en) 2007-08-16 2016-11-29 Hand Held Products, Inc. Data collection system having EIR terminal interface node
US20110090057A1 (en) * 2007-08-16 2011-04-21 Hand Held Products, Inc. Data collection system having eir terminal interface node
US7857222B2 (en) 2007-08-16 2010-12-28 Hand Held Products, Inc. Data collection system having EIR terminal interface node
US9258188B2 (en) 2007-08-16 2016-02-09 Hand Held Products, Inc. Data collection system having EIR terminal interface node
US8556174B2 (en) 2007-08-16 2013-10-15 Hand Held Products, Inc. Data collection system having EIR terminal interface node
US8756318B1 (en) * 2007-10-09 2014-06-17 Microsoft Corporation Software deployment using client location
US20090094378A1 (en) * 2007-10-09 2009-04-09 Microsoft Corporation Software Deployment Using Client Location
US20090118941A1 (en) * 2007-11-05 2009-05-07 Gm Global Technology Operations, Inc. Method and apparatus for dynamic output torque limiting for a hybrid powertrain system
US8397228B2 (en) * 2007-11-14 2013-03-12 Continental Automotive Systems, Inc. Systems and methods for updating device software
US20090125900A1 (en) * 2007-11-14 2009-05-14 Continental Teves, Inc. Systems and Methods for Updating Device Software
US8396464B2 (en) * 2008-03-28 2013-03-12 Samsung Electronics Co., Ltd Method and apparatus for software update of terminals in a mobile communication system
US20090247145A1 (en) * 2008-03-28 2009-10-01 Samsung Electronics Co., Ltd. Method and apparatus for software update of terminals in a mobile communication system
US20090288071A1 (en) * 2008-05-13 2009-11-19 Microsoft Corporation Techniques for delivering third party updates
US20110113422A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Programmatic Creation Of Task Sequences From Manifests
US20110113413A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Software Updates Using Delta Patching
US20110113415A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Multiple Invocation Points In Software Build Task Sequence
US8671402B2 (en) * 2009-11-09 2014-03-11 Bank Of America Corporation Network-enhanced control of software updates received via removable computer-readable medium
US20110113417A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Network-Enhanced Control Of Software Updates Received Via Removable Computer-Readable Medium
US20110113414A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Software Updates Using Delta Patching
US8584113B2 (en) * 2009-11-09 2013-11-12 Bank Of America Corporation Cross-updating of software between self-service financial transaction machines
US20110113424A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Distribution Of Software Updates
US20110113416A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Network-Enhanced Control Of Software Updates Received Via Removable Computer-Readable Medium
US20110113420A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Distribution Of Software Updates
US9176898B2 (en) 2009-11-09 2015-11-03 Bank Of America Corporation Software stack building using logically protected region of computer-readable medium
US20110113418A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Cross-Updating Of Software Between Self-Service Financial Transaction Machines
US20110113070A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Software Stack Building Using Logically Protected Region Of Computer-Readable Medium
US20110113226A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Distribution Of Software Updates
US9128799B2 (en) 2009-11-09 2015-09-08 Bank Of America Corporation Programmatic creation of task sequences from manifests
US20110113419A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Programmatic Creation Of Task Sequences From Manifests
US8972974B2 (en) 2009-11-09 2015-03-03 Bank Of America Corporation Multiple invocation points in software build task sequence
US9122558B2 (en) 2009-11-09 2015-09-01 Bank Of America Corporation Software updates using delta patching
US20110113421A1 (en) * 2009-11-09 2011-05-12 Bank Of America Corporation Programmatic Creation Of Task Sequences From Manifests
US9497092B2 (en) 2009-12-08 2016-11-15 Hand Held Products, Inc. Remote device management interface
US20110238572A1 (en) * 2010-03-25 2011-09-29 Bank Of America Corporation Remote Control Of Self-Service Terminal
US8918564B2 (en) 2011-10-06 2014-12-23 Honeywell International Inc. Device management using virtual interfaces
US8539123B2 (en) 2011-10-06 2013-09-17 Honeywell International, Inc. Device management using a dedicated management interface
US8868803B2 (en) 2011-10-06 2014-10-21 Honeywell Internation Inc. Managing data communication between a peripheral device and a host
US9298667B2 (en) 2011-10-06 2016-03-29 Honeywell International, Inc Device management using virtual interfaces cross-reference to related applications
US10049075B2 (en) 2011-10-06 2018-08-14 Honeywell International, Inc. Device management using virtual interfaces
US8621123B2 (en) 2011-10-06 2013-12-31 Honeywell International Inc. Device management using virtual interfaces
US9053055B2 (en) 2011-10-06 2015-06-09 Honeywell International Device management using virtual interfaces cross-reference to related applications
US20130159996A1 (en) * 2011-12-16 2013-06-20 Hsiu-Ping Lin Systems for downloading location-based application and methods using the same
US9430206B2 (en) * 2011-12-16 2016-08-30 Hsiu-Ping Lin Systems for downloading location-based application and methods using the same
DE102012023647A1 (en) 2012-12-03 2014-06-05 Audi Ag Method for updating stored data to control device of motor vehicle, has activating specific vehicle mode in depending on type of control devices when mistake in form of incorrect transfer of data or storage of data is determined
US9959107B2 (en) * 2013-06-28 2018-05-01 Samsung Electronics Co., Ltd. Method and apparatus for updating application
US20150007157A1 (en) * 2013-06-28 2015-01-01 Samsung Electronics Co., Ltd. Method and apparatus for updating application
US9740473B2 (en) 2015-08-26 2017-08-22 Bank Of America Corporation Software and associated hardware regression and compatibility testing system
US10021509B2 (en) 2016-03-25 2018-07-10 At&T Mobility Ii Llc Methods and apparatus to provide an update via a satellite connection
US10203949B2 (en) * 2016-05-11 2019-02-12 Hyundai Motor Company System and method for providing software updates
US20170329599A1 (en) * 2016-05-11 2017-11-16 Hyundai Motor Company System and method for providing software updates
US10305582B2 (en) 2016-10-19 2019-05-28 Vector Launch Inc. State transfer among satellite platforms
US10084534B2 (en) 2016-10-19 2018-09-25 Vector Launch Inc. State transfer among virtualization-enabled satellite platforms
US10250319B2 (en) 2016-10-19 2019-04-02 Vector Launcy Inc. Task transfer among satellite devices
US9991951B2 (en) 2016-10-19 2018-06-05 Vector Launch Inc. Peer state transfer among satellite devices
WO2018093399A1 (en) * 2016-11-16 2018-05-24 Vector Launch Inc. Orchestration of software application deployment in a satellite platform
US9740465B1 (en) 2016-11-16 2017-08-22 Vector Launch Inc. Orchestration of software application deployment in a satellite platform
US9875091B1 (en) 2016-11-16 2018-01-23 Vector Launch Inc. User-initiated software application deployment to an orbital satellite platform
US9998207B1 (en) 2017-07-19 2018-06-12 Vector Launch Inc. Orbital network layering in satellite platforms
US9960837B1 (en) 2017-07-19 2018-05-01 Vector Launch Inc. Pseudo-geosynchronous configurations in satellite platforms
US10225001B2 (en) 2017-07-19 2019-03-05 Vector Launch Inc. Orbital network layering
US9819742B1 (en) 2017-07-19 2017-11-14 Vector Launch Inc. Bandwidth aware state transfer among satellite devices
US10270521B2 (en) 2017-07-19 2019-04-23 Vector Launch Inc. Pseudo-geosynchronous communications in satellite platforms
US10306019B2 (en) 2017-07-19 2019-05-28 Vector Launch Inc. Variable role-specialization among computing devices of computing platforms
US10069935B1 (en) 2017-07-19 2018-09-04 Vector Launch Inc. Role-specialization in clustered satellite platforms

Also Published As

Publication number Publication date
JP2001067232A (en) 2001-03-16
US6820259B1 (en) 2004-11-16

Similar Documents

Publication Publication Date Title
US7088952B1 (en) Apparatus for transmitting program information, communicating system, method of transmitting program information, method of instructing program recording operation, and method of instructing program purchasing operation
JP4092207B2 (en) gps assistance message and a method therefor in cellular communication network
AU2005262838B2 (en) System and method for wireless asset tracking
US6198914B1 (en) Emergency call system
US6490521B2 (en) Voice-controlled navigation device utilizing wireless data transmission for obtaining maps and real-time overlay information
US8594003B2 (en) Method of estimating location of mobile device in transportation using WiFi
JP4579540B2 (en) Aircraft Takishi planning system and method
US7142810B2 (en) Method of communicating with a quiescent vehicle
US20080165032A1 (en) Apparatus and method of providing schedule and route
US6529159B1 (en) Method for distributing location-relevant information using a network
US6014090A (en) Method and apparatus for delivering local information to travelers
US6580390B1 (en) Method and system for global positioning system mask angle optimization
JP3425276B2 (en) Information notification system
EP0911607A2 (en) Moving body terminal device having update means concerning new menu items
US7917158B2 (en) Method and system for location management and location information providing system
US5510798A (en) Multiple-accuracy GPS system
JP3372021B2 (en) Map information providing system
US7715781B2 (en) System, method and computer program product for receiving data from a satellite radio network
JP2887815B2 (en) The mobile station position monitoring system
US6664922B1 (en) Method for distributing location-relevant information using a network
US8924566B1 (en) Method and apparatus for computing over a wide area network
US20020067288A1 (en) Received information processing apparatus
US7783421B2 (en) Navigation device, navigation method, navigation program, server device, and navigation information distribution system
US7184744B1 (en) GPS enabled emergency messaging system
US20020042266A1 (en) System and methods for conserving wireless resources

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION