US20060122744A1 - Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system - Google Patents
Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system Download PDFInfo
- Publication number
- US20060122744A1 US20060122744A1 US11/339,636 US33963606A US2006122744A1 US 20060122744 A1 US20060122744 A1 US 20060122744A1 US 33963606 A US33963606 A US 33963606A US 2006122744 A1 US2006122744 A1 US 2006122744A1
- Authority
- US
- United States
- Prior art keywords
- program
- downloading
- center
- power supply
- vehicle terminal
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
- G08G1/096805—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route
- G08G1/096827—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route where the route is computed onboard
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H04W4/04—
Definitions
- the present invention relates to a communication system having in-vehicle terminals and a center (an information center) interconnected by radiocommunication. Moreover, the present invention relates to an in-vehicle terminal employed in the communication system.
- the center wants to check if downloading the program to the in-vehicle terminal has been completed normally. Otherwise, the center wants to check if the downloaded program is operating normally while being compatible with the software and hardware environment of the in-vehicle terminal. Through this checking, the center confirms that the program has been distributed to the user. At the same time, the in-vehicle terminal can be kept safe. Moreover, after checking, the center can charge the user for the service.
- a center does not have a means for performing the checking. After a program is delivered to an in-vehicle terminal, the program is at the user's disposal. The center cannot therefore sell a program even after confirming that the program satisfies the user. Moreover, even if an abnormality occurs during downloading or after activation of a program, the center cannot cope with it swiftly.
- An object of the present invention is to provide a communication system for downloading programs from a center to in-vehicle terminals.
- the center can check if downloading has been completed normally or if a downloaded program is operating normally in an in-vehicle terminal.
- the present invention has been devised in order to accomplish the above object.
- a communication system having in-vehicle terminals and a center interconnected by radiocommunication or the like.
- the in-vehicle terminal transmits information, which indicates that the program has been activated, to the center according to the timing of activating the downloaded program.
- the timing of activating the program includes the timing that the program is activated first and the timing that the program has been activated a certain number of times or more.
- the center becomes aware that the program has been downloaded without any problem and that the program has been activated normally.
- the center can thus confirm that the user's in-vehicle terminal is safe.
- the center can use the results of checking as a criterion for charging the user.
- an in-vehicle terminal in which, if the state of communication becomes improper during downloading of a program, downloading is suspended, or downloading is automatically restarted.
- the in-vehicle terminal requests downloading of the program again.
- the state of communication becomes improper, the state of downloading attained when communication is cleared is recorded.
- the state of downloading is reported to the center. According to the state of downloading reported from the in-vehicle terminal, the center restarts downloading of the program from the middle of the program, or more particularly, downloading of a portion of the program that has not been transmitted.
- the in-vehicle terminal has either of a facility for suspending downloading when the state of communication becomes improper and a facility for automatically restarting downloading.
- both the facility for suspending downloading and the facility for automatically restarting downloading may be made available so that a user can select either of them.
- the in-vehicle terminal can cope with an event such as an ACC power supply being turned off during downloading.
- an ACC power supply may be turned off.
- the power supply of the system is changed from the ACC power supply to a +B power supply that is a backup power supply in order to continue downloading. Otherwise, downloading may be suspended or automatically restarted. Even in this case, a user can select the suspending facility or the automatically restarting facility.
- a countermeasure can be taken quickly. Consequently, the users' jobs are hardly interrupted and the users' satisfaction can be upgraded. Moreover, when it is necessary to charge users for services, it can be judged correctly whether users should be charged.
- FIG. 1 shows the configuration of a first example of communication systems in which the present invention is implemented
- FIG. 2 is a flowchart describing processing performed in the communication system shown in FIG. 1 ;
- FIG. 3 shows the configuration of a second example of communication systems in which the present invention is implemented
- FIG. 4 is a flowchart describing processing performed in the communication system shown in FIG. 3 ;
- FIG. 5 is a flowchart describing a procedure for downloading a program in the communication system shown in FIG. 3 ;
- FIG. 6 is a flowchart describing a variant of the procedure described in FIG. 5 ;
- FIG. 7 is a flowchart describing a first example of procedures for coping with an event that the ACC power supply of the communication system shown in FIG. 3 is turned off;
- FIG. 8 is a flowchart describing a second example of procedures for coping with the event that the ACC power supply of the communication system shown in FIG. 3 is turned off;
- FIG. 9 is a flowchart describing a third example of procedures for coping with the event that the ACC power supply of the communication system shown in FIG. 3 is turned off;
- FIG. 10 is a flowchart describing a first example of procedures for checking whether a program has been activated normally in the communication system shown in FIG. 3 ;
- FIG. 11 is a flowchart describing a second example of procedures for checking whether a program has been activated normally in the communication system shown in FIG. 3 ;
- FIG. 12 is a flowchart describing a procedure for automatically updating a program in the communication system shown in FIG. 3 .
- FIG. 1 shows the configuration of a communication system accommodating a center and in-vehicle terminals.
- a center 11 has a center information management unit 12 , a plurality of programs 13 to be distributed, and a communication unit 14 .
- the center information management unit 12 includes a CPU and others, and distributes or updates the programs 13 .
- the communication unit 14 transmits and receives data to and from each in-vehicle terminal 21 .
- Program information 15 that is information concerning a program itself is appended to each program 13 .
- the program 13 includes, in addition to a program itself, an information management facility 16 and an information transmission facility 17 .
- the information management facility 16 manages the program information 15
- the information transmission facility 17 transmits the program information from the in-vehicle terminal 21 to the center 11 .
- the program 13 is transmitted externally by the communication unit 14 under the control of the center information management unit 12 .
- the in-vehicle terminal 21 consists of a communication unit 24 , a storage medium 23 , a terminal information management unit 22 , and an input unit 25 .
- the communication unit 24 transmits and receives data to and from the center 11 .
- the program 13 downloaded from the center 11 is stored in the storage medium 23 .
- the terminal information management unit 22 is formed with a CPU and others.
- the input unit 25 outputs a trigger pulse when manipulated by a user or when called by any other application program.
- the center 11 transmits the requested program 13 .
- the center information management unit 12 updates such information as a date of transmission, a time of transmission, and the number of times, by which a program has been activated, in the program information 15 .
- the center information management unit 12 appends the program information 15 to the program 13 .
- the communication unit 14 transmits the program 13 .
- the in-vehicle terminal 21 stores the program 13 and program information 15 , which are received by the communication unit 24 , in the storage medium 23 .
- FIG. 2 is a flowchart describing a procedure according to which the in-vehicle terminal 2 reports normal termination of downloading to the center 11 .
- a trigger pulse is sent from the input unit 25 to the terminal information management unit 22 (step S 11 ). Consequently, the terminal information management unit 22 activates the program 13 .
- the program 13 is then activated to operate.
- the information management facility 16 of the program 13 reads the program information 15 from the program information division (step S 12 ). The information management facility 16 then checks the number of times by which the program has been activated in order to judge whether this activation is the first activation (step S 13 ).
- the program information 15 is updated at step S 14 .
- the information transmission facility 17 is used to transmit the program information 15 to the center 11 . If this activation is not the first activation, the program information 15 is updated at step S 14 . The number of times of activation is incremented by one.
- FIG. 3 shows another example of communication systems.
- a program to be downloaded from the center 11 checks, by itself, whether downloading has been completed normally and the program has been activated normally.
- the terminal information management unit 22 in the in-vehicle terminal 21 performs the checking.
- FIG. 3 Many components shown in FIG. 3 are identical to those shown in FIG. 1 . Only those components different from those in FIG. 1 will be described below.
- the center 11 is provided with programs (programs A, B, etc.) only as the programs 13 to be distributed.
- Program information 26 that is information concerning a program itself is created by the in-vehicle terminal and stored therein.
- the in-vehicle terminal 21 receives a program 13 and stores it in the storage medium 23 .
- program information 26 including a date of downloading and the number of times of activation is produced and stored in the storage medium 23 .
- the in-vehicle terminal 21 further includes a display 27 , a loudspeaker 28 , and a power management unit 29 .
- the power management unit 29 is connected to an ACC power supply 30 , a +B power supply 31 , and a ground 32 .
- the +B power supply 31 is a power supply for supplying power directly from a battery, and is used as a backup power supply for a memory.
- the ACC power supply 30 is a power supply for supplying power from the +B power supply 31 via an ignition key. When the ignition key is turned on, power is supplied from the ACC power supply 30 to every load. When the ignition key is turned off, the ACC power supply is turned off.
- the power management unit 29 normally selects the ACC power supply 30 as the power supply of the system, and, if necessary, changes the ACC power supply 30 to the +B power supply 31 .
- FIG. 4 is a flowchart describing a procedure for reporting normal termination of downloading from the in-vehicle terminal 21 .
- Steps S 21 to S 25 in the flowchart of FIG. 4 are identical to steps S 11 to 15 in FIG. 2 . Repetition will be avoided. However, according to the procedure described in FIG. 2 , steps S 11 to S 15 are carried out by the program 13 itself. Steps S 21 to S 25 in FIG. 4 are carried out by the terminal information management unit 22 . This is the main difference.
- FIG. 5 is a flowchart describing the procedure of downloading a program to the in-vehicle terminal 21 shown in FIG. 3 .
- the procedure described in FIG. 5 is carried out by the terminal information management unit 22 in the in-vehicle terminal 21 .
- step S 30 Downloading a program from the center 11 is started in response to a request issued from the in-vehicle terminal 21 (step S 30 ).
- step S 31 it is judged whether the state of communication is proper. If the state of communication is proper, one unit of communication data is saved in the storage unit 23 .
- step S 33 the state of downloading is recorded in the program information 26 .
- step S 34 it is judged whether downloading is completed. If downloading is not completed, control is returned to step S 31 . The same actions are repeated until downloading of all programs is completed. Moreover, if it is judged at step S 34 that downloading of all programs is completed, downloading is terminated at step S 35 .
- step S 41 the fact is reported to the user by voice through the speaker 28 .
- step S 31 if it is judged that the state of communication is improper, it is reported to the user by voice through the speaker 28 at step S 36 that downloading is suspended. Control is passed to step S 37 .
- downloading is suspended at step S 37 .
- the unit data stored in the storage medium 23 is deleted and processing is terminated.
- the suspension is reported to the user by voice.
- the user becomes aware of the fact that downloading is suspended. In this case, the user can re-issue a request for downloading the program to the center 11 .
- the center 11 then transmits the program from the beginning.
- step S 37 of suspending downloading is skipped but control is passed to step S 38 .
- Step 38 then waits until the state of communication to be restored.
- control is passed to step S 39 .
- step S 39 the state of downloading is recorded in the program information 26 , that is, what program data has been received is recorded in the program information 26 .
- the state of downloading is then reported from the communication unit 24 to the center 11 .
- the center 11 restarts downloading the program from a point in the program at which downloading was suspended.
- the in-vehicle terminal 21 restarts receiving a downloaded program (step S 40 ). Thereafter, control is returned to step S 31 .
- Checking the state of communication and saving data are carried out continuously.
- the in-vehicle terminal 21 when downloading is completed (step S 35 ), the fact is reported to a user by voice (step S 41 ).
- FIG. 6 shows a variant of the procedure described in FIG. 5 .
- a means for suspending downloading when the state of communication becomes improper and a means for restarting downloading are included, and either of the means can be selected by a user. For the selection, the user manipulates the input unit 25 in advance.
- FIG. 6 describes modified steps of steps S 36 to S 38 in FIG. 5 .
- step S 31 in FIG. 5 When it is judged that the state of communication is improper (step S 31 in FIG. 5 ), the fact is reported to a user by voice (step S 36 ). It is then judged at step S 42 whether a user's choice is automatic continuation. If suspension of downloading is selected, control is passed to step S 37 and downloading is suspended. If automatic continuation is selected, control is passed to step S 38 . Hereinafter, step S 38 and subsequent steps similar to those in FIG. 5 are carried out. When the state of communication becomes proper, downloading is restarted.
- the power management unit 29 in the in-vehicle terminal 21 usually selects the ACC power supply 30 as the power supply of the system. If the ignition key is removed during downloading, the ACC power supply 30 is turned off and downloading is suspended.
- the present embodiment is devised to cope with this event.
- FIG. 7 describes actions to be performed when the ACC power supply 30 is turned off.
- the power management unit 29 When detecting that the ACC power supply 30 is turned off, the power management unit 29 changes the power supply for supplying power to the in-vehicle terminal 21 from the ACC power supply to the +B power supply 31 . Consequently, downloading is continued. Moreover, when the ACC power supply 30 is restored, the power management unit 29 changes the power supply for supplying power to the in-vehicle terminal 21 from the +B power supply to the ACC power supply 30 .
- the power management unit 29 sends an interrupt to the terminal information management unit 22 .
- the terminal information management unit 22 keeps operating owing to the +B power supply 31 .
- a procedure described in FIG. 7 is started (step S 51 ). It is reported to a user using voice produced by the loudspeaker 28 or using indication made by the display 27 that the ACC power supply 30 has been turned off (step S 52 ).
- step S 53 the state of the ACC power supply 30 is checked. If the ACC power supply 30 is restored to the on state, the state attained before the interrupt is issued and described in FIG. 5 is resumed. If the ACC power supply 30 is restored immediately by manipulating the ignition key, downloading can be continued. In this case, voice may be produced or an indication may be provided by the display. If the off state of the ACC power supply 30 continues, downloading is suspended (step S 54 ). The power management unit 29 is instructed to turn off the power supply of the system (step S 55 ).
- a user turns on the ignition key.
- manipulations are performed to issue a request for downloading to the center 11 .
- the center 11 transmits a program 13 to the in-vehicle terminal 21 from the beginning.
- the state can be reported to a user. Moreover, if the off state of the ACC power supply 30 is transient, downloading can be restarted automatically.
- FIG. 8 describes a procedure of continuing downloading using the +B power supply 31 after the ACC power supply 30 is turned off. Steps S 61 to S 63 in FIG. 8 are identical to steps S 51 to S 53 in FIG. 7 . Reiteration will be avoided.
- step S 63 if it is detected that the ACC power supply 30 is still off, control is passed to step S 64 in this embodiment. Downloading is continued using the +B power supply 31 .
- step S 65 the power management unit 29 turns off the power supply of the system (step S 66 ).
- FIG. 9 describes an example of procedures according to which a user can select in advance whether downloading is suspended or continued if the ACC power supply 30 is turned off during downloading.
- Steps S 71 and S 72 are identical to steps S 51 and S 52 in FIG. 7 .
- a report is made to a user at step S 72 , it is judged at step S 73 whether the user has selected automatic continuation.
- the user uses the input unit 25 to select in advance whether downloading is suspended or continued automatically.
- step S 77 If suspension is selected, control is passed to step S 77 and downloading is suspended. If automatic continuation is selected, control is passed to step S 74 . Downloading is continued using the +B power supply 31 . At step S 75 , the state of downloading, that is, up to which unit data the program has been received is reported to the center 11 . The procedure is then terminated.
- the power management unit 29 changes the power supply of the system from the +B power supply 31 to the ACC power supply 30 .
- the power management unit 29 reports the fact to the terminal information management unit 22 . With this report, an interrupt is produced at step S 76 .
- a request for downloading is sent to the center 11 .
- the center 11 transmits data succeeding to data, which was transmitted at the time of suspension of downloading, according to the state of downloading reported at step S 75 .
- the center 11 may transmit the program 13 from the beginning.
- the terminal information management unit 22 deletes the program that was stored up to the middle thereof.
- steps S 74 to S 76 may be replaced with steps S 64 to S 66 described in FIG. 8 .
- the +B power supply 31 is used to continue downloading. After downloading is terminated, the power supply of the system is turned off.
- FIG. 10 describes an example of procedures according to which when a certain time has elapsed after activation of a program, it is judged that the program is operating normally.
- a trigger pulse is produced by the input unit 25 .
- the terminal information management unit 22 activates the program (step S 81 ).
- the program 13 operates continuously after activated.
- the terminal information management unit 22 waits until a certain time has elapsed (step S 82 ).
- the certain time has elapsed, it is reported to the center 11 that the program has been activated and the certain time has elapsed (step S 83 ). At this time, the fact that a report is sent to the center 11 may be indicated on the display 27 .
- step S 84 if the user satisfies the action of the program, the user may perform predetermined manipulations on the input unit (step S 84 ). Thus, it is reported to the center 11 that the program has been activated normally. The step S 84 may be omitted.
- the center 11 can be aware of the fact that downloading has been completed without any problem and a program is operating normally.
- FIG. 11 describes an example of procedures according to which when the number of times by which a program 13 has been activated exceeds a certain number of times, it is judged that the program is operating normally.
- Step S 91 in FIG. 11 is identical to step S 81 in FIG. 10 .
- the program is activated. With the program left activated, the number of times by which the program has been activated is checked (step S 92 ). The number of times of activation is acquired from the program information 26 . If the program has been activated a certain number of times or more, the fact is reported to the center 11 (step S 93 ).
- Step S 94 is analogous to step S 84 in FIG. 10 . Even in this embodiment, step S 94 can be omitted.
- the center 11 downloads a program 13 in response to a request sent from the in-vehicle terminal 21 . Moreover, every time a program is updated to a higher version, a user requests downloading of an updated program.
- FIG. 12 described an example of procedures according to which when a program is updated, a request for downloading the updated program is issued automatically to the center 11 . This obviates the necessity that a user must issue a request for downloading every time a program is updated.
- a user performs predetermined manipulations on the input unit 25 to designate automatic updating (step S 101 ).
- the terminal information management unit 22 reports to the program center 11 that automatic updating has been reserved (step S 102 ).
- the user may designate that downloading is performed for automatic updating during a time band during which a vehicle is not driven, for example, at midnight.
- the center 11 In response to the request, the center 11 records, in the program information 15 , that automatic updating has been reserved (step S 111 ).
- the center 11 downloads the program 13 to users who have reserved automatic updating (step S 122 ). At this time, if a time band is designated, the program is transmitted during the time band. In this case, when sensing that the in-vehicle terminal 21 is called by the center 11 , the terminal information management unit 22 in the in-vehicle terminal 21 automatically turns on the power supply of the system. Thereafter, the program is downloaded according to the actions described in FIG. 5 and FIG. 6 . Moreover, when downloading is terminated, the power supply of the system is turned off.
- the terminal information management unit 22 indicates on the display 27 that automatic updating of the program has been carried out. The user becomes aware of the fact that downloading has been carried out.
- a communication system for downloading programs from a center to in-vehicle terminals The center can readily check whether downloading has been completed normally or a program is operating normally in a in-vehicle terminal.
Abstract
In a communication system for downloading programs from a center to in-vehicle terminals, a center can check whether downloading has been completed normally or a program is operating normally in an in-vehicle terminal. According to the timing of activating a downloaded program, an in-vehicle terminal checks whether the program is activated to operate normally. The information is transmitted to the center. Based on the information, the center becomes aware of the fact that downloading has been completed without any problem and that the program is operating normally in the in-vehicle terminal.
Description
- This application is a divisional of application Ser. No. 10/288,438 filed Nov. 6, 2002, now pending, which is divisional of application Ser. No. 10/105,306, filed Mar. 26, 2002, now pending, which is divisional of application Ser. No. 09/461,423, filed Dec. 16, 1999, now U.S. Pat. No. 6,647,322.
- 1. Field of the Invention
- The present invention relates to a communication system having in-vehicle terminals and a center (an information center) interconnected by radiocommunication. Moreover, the present invention relates to an in-vehicle terminal employed in the communication system.
- 2. Description of the Related Art
- There is a communication system in which computer programs, to be installed in in-vehicle terminals, are distributed from a center by radiocommunication or the like. In the communication system, when a user wants to install a program such as a navigation system or video game in his/her in-vehicle terminal, or when a user wants to update an installed program, the user issues a request for downloading a program from his/her in-vehicle terminal to the center. The center downloads the requested program to the in-vehicle terminal by radiocommunication or the like.
- At this time, the center wants to check if downloading the program to the in-vehicle terminal has been completed normally. Otherwise, the center wants to check if the downloaded program is operating normally while being compatible with the software and hardware environment of the in-vehicle terminal. Through this checking, the center confirms that the program has been distributed to the user. At the same time, the in-vehicle terminal can be kept safe. Moreover, after checking, the center can charge the user for the service.
- In contrast, in conventional communication systems, a center does not have a means for performing the checking. After a program is delivered to an in-vehicle terminal, the program is at the user's disposal. The center cannot therefore sell a program even after confirming that the program satisfies the user. Moreover, even if an abnormality occurs during downloading or after activation of a program, the center cannot cope with it swiftly.
- This application claims priority from Japanese Application No. 11-9649, filed Jan. 18, 1999, the contents of which are incorporated hereinto by this reference.
- An object of the present invention is to provide a communication system for downloading programs from a center to in-vehicle terminals. Herein, the center can check if downloading has been completed normally or if a downloaded program is operating normally in an in-vehicle terminal.
- The present invention has been devised in order to accomplish the above object. According to the present invention, there is provided a communication system having in-vehicle terminals and a center interconnected by radiocommunication or the like. Herein, after a program is downloaded from the center to an in-vehicle terminal, the in-vehicle terminal transmits information, which indicates that the program has been activated, to the center according to the timing of activating the downloaded program. The timing of activating the program includes the timing that the program is activated first and the timing that the program has been activated a certain number of times or more.
- Consequently, the center becomes aware that the program has been downloaded without any problem and that the program has been activated normally. The center can thus confirm that the user's in-vehicle terminal is safe. Moreover, the center can use the results of checking as a criterion for charging the user.
- According to the present invention, there is provided an in-vehicle terminal in which, if the state of communication becomes improper during downloading of a program, downloading is suspended, or downloading is automatically restarted. When downloading is suspended, if necessary, the in-vehicle terminal requests downloading of the program again. For automatically restarting downloading, when the state of communication becomes improper, the state of downloading attained when communication is cleared is recorded. When the state of communication is recovered, the state of downloading is reported to the center. According to the state of downloading reported from the in-vehicle terminal, the center restarts downloading of the program from the middle of the program, or more particularly, downloading of a portion of the program that has not been transmitted.
- According to the present invention, the in-vehicle terminal has either of a facility for suspending downloading when the state of communication becomes improper and a facility for automatically restarting downloading. Alternatively, both the facility for suspending downloading and the facility for automatically restarting downloading may be made available so that a user can select either of them.
- Furthermore, according to the present invention, the in-vehicle terminal can cope with an event such as an ACC power supply being turned off during downloading. As far as an in-vehicle terminal is concerned, when an ignition key is removed during downloading, an ACC power supply may be turned off. According to the present invention, the power supply of the system is changed from the ACC power supply to a +B power supply that is a backup power supply in order to continue downloading. Otherwise, downloading may be suspended or automatically restarted. Even in this case, a user can select the suspending facility or the automatically restarting facility.
- According to the present invention, when a program is downloaded from a center to an in-vehicle terminal or when a downloaded program is operated in an in-vehicle terminal, if any trouble occurs, a countermeasure can be taken quickly. Consequently, the users' jobs are hardly interrupted and the users' satisfaction can be upgraded. Moreover, when it is necessary to charge users for services, it can be judged correctly whether users should be charged.
- The above object and features of the present invention will be more apparent from the following description of the preferred embodiment with reference to the accompanying drawings, wherein:
-
FIG. 1 shows the configuration of a first example of communication systems in which the present invention is implemented; -
FIG. 2 is a flowchart describing processing performed in the communication system shown inFIG. 1 ; -
FIG. 3 shows the configuration of a second example of communication systems in which the present invention is implemented; -
FIG. 4 is a flowchart describing processing performed in the communication system shown inFIG. 3 ; -
FIG. 5 is a flowchart describing a procedure for downloading a program in the communication system shown inFIG. 3 ; -
FIG. 6 is a flowchart describing a variant of the procedure described inFIG. 5 ; -
FIG. 7 is a flowchart describing a first example of procedures for coping with an event that the ACC power supply of the communication system shown inFIG. 3 is turned off; -
FIG. 8 is a flowchart describing a second example of procedures for coping with the event that the ACC power supply of the communication system shown inFIG. 3 is turned off; -
FIG. 9 is a flowchart describing a third example of procedures for coping with the event that the ACC power supply of the communication system shown inFIG. 3 is turned off; -
FIG. 10 is a flowchart describing a first example of procedures for checking whether a program has been activated normally in the communication system shown inFIG. 3 ; -
FIG. 11 is a flowchart describing a second example of procedures for checking whether a program has been activated normally in the communication system shown inFIG. 3 ; and -
FIG. 12 is a flowchart describing a procedure for automatically updating a program in the communication system shown inFIG. 3 . - A communication system and an in-vehicle terminal in which the present invention is implemented will be described in conjunction with the drawings below.
-
FIG. 1 shows the configuration of a communication system accommodating a center and in-vehicle terminals. - A
center 11 has a centerinformation management unit 12, a plurality ofprograms 13 to be distributed, and acommunication unit 14. The centerinformation management unit 12 includes a CPU and others, and distributes or updates theprograms 13. Thecommunication unit 14 transmits and receives data to and from each in-vehicle terminal 21. -
Program information 15 that is information concerning a program itself is appended to eachprogram 13. Theprogram 13 includes, in addition to a program itself, aninformation management facility 16 and aninformation transmission facility 17. Theinformation management facility 16 manages theprogram information 15, and theinformation transmission facility 17 transmits the program information from the in-vehicle terminal 21 to thecenter 11. Theprogram 13 is transmitted externally by thecommunication unit 14 under the control of the centerinformation management unit 12. - The in-
vehicle terminal 21 consists of acommunication unit 24, astorage medium 23, a terminalinformation management unit 22, and aninput unit 25. Thecommunication unit 24 transmits and receives data to and from thecenter 11. Theprogram 13 downloaded from thecenter 11 is stored in thestorage medium 23. The terminalinformation management unit 22 is formed with a CPU and others. Theinput unit 25 outputs a trigger pulse when manipulated by a user or when called by any other application program. - In the illustrated communication system, when a request for downloading a program is issued by the in-
vehicle terminal 21, thecenter 11 transmits the requestedprogram 13. At this time, the centerinformation management unit 12 updates such information as a date of transmission, a time of transmission, and the number of times, by which a program has been activated, in theprogram information 15. The centerinformation management unit 12 appends theprogram information 15 to theprogram 13. Thecommunication unit 14 transmits theprogram 13. - When downloading terminates normally, the in-
vehicle terminal 21 stores theprogram 13 andprogram information 15, which are received by thecommunication unit 24, in thestorage medium 23. -
FIG. 2 is a flowchart describing a procedure according to which the in-vehicle terminal 2 reports normal termination of downloading to thecenter 11. - When a user performs manipulations to select a
program 13 or when theprogram 13 is called by any other application program, a trigger pulse is sent from theinput unit 25 to the terminal information management unit 22 (step S11). Consequently, the terminalinformation management unit 22 activates theprogram 13. Theprogram 13 is then activated to operate. Moreover, theinformation management facility 16 of theprogram 13 reads theprogram information 15 from the program information division (step S12). Theinformation management facility 16 then checks the number of times by which the program has been activated in order to judge whether this activation is the first activation (step S13). - If this activation is the first activation, the
program information 15 is updated at step S14. Theinformation transmission facility 17 is used to transmit theprogram information 15 to thecenter 11. If this activation is not the first activation, theprogram information 15 is updated at step S14. The number of times of activation is incremented by one. - At the
center 11, when information is received from the in-vehicle terminal 21, the information is analyzed. It is thus checked if downloading the program to the in-vehicle terminal 21 has been completed correctly and if theprogram 13 has been activated normally. -
FIG. 3 shows another example of communication systems. In the first embodiment, a program to be downloaded from thecenter 11 checks, by itself, whether downloading has been completed normally and the program has been activated normally. In this embodiment, the terminalinformation management unit 22 in the in-vehicle terminal 21 performs the checking. - Many components shown in
FIG. 3 are identical to those shown inFIG. 1 . Only those components different from those inFIG. 1 will be described below. - The
center 11 is provided with programs (programs A, B, etc.) only as theprograms 13 to be distributed.Program information 26 that is information concerning a program itself is created by the in-vehicle terminal and stored therein. The in-vehicle terminal 21 receives aprogram 13 and stores it in thestorage medium 23. At this time,program information 26 including a date of downloading and the number of times of activation is produced and stored in thestorage medium 23. - The in-
vehicle terminal 21 further includes adisplay 27, aloudspeaker 28, and apower management unit 29. Thepower management unit 29 is connected to anACC power supply 30, a +B power supply 31, and aground 32. The +B power supply 31 is a power supply for supplying power directly from a battery, and is used as a backup power supply for a memory. TheACC power supply 30 is a power supply for supplying power from the +B power supply 31 via an ignition key. When the ignition key is turned on, power is supplied from theACC power supply 30 to every load. When the ignition key is turned off, the ACC power supply is turned off. Thepower management unit 29 normally selects theACC power supply 30 as the power supply of the system, and, if necessary, changes theACC power supply 30 to the +B power supply 31. -
FIG. 4 is a flowchart describing a procedure for reporting normal termination of downloading from the in-vehicle terminal 21. - Steps S21 to S25 in the flowchart of
FIG. 4 are identical to steps S11 to 15 inFIG. 2 . Repetition will be avoided. However, according to the procedure described inFIG. 2 , steps S11 to S15 are carried out by theprogram 13 itself. Steps S21 to S25 inFIG. 4 are carried out by the terminalinformation management unit 22. This is the main difference. - Next, a description will be made of a procedure for coping with a failure that occurs in downloading a program from the
center 11 to the in-vehicle terminal 21. Herein, downloading shall be performed in the communication system shown inFIG. 3 . However, the procedure can be adapted to the communication system shown inFIG. 1 in which a program itself performs checking. When the procedure is carried out in the communication system shown inFIG. 1 , the in-vehicle terminal must be provided with a loudspeaker and others. -
FIG. 5 is a flowchart describing the procedure of downloading a program to the in-vehicle terminal 21 shown inFIG. 3 . The procedure described inFIG. 5 is carried out by the terminalinformation management unit 22 in the in-vehicle terminal 21. - Downloading a program from the
center 11 is started in response to a request issued from the in-vehicle terminal 21 (step S30). At step S31, it is judged whether the state of communication is proper. If the state of communication is proper, one unit of communication data is saved in thestorage unit 23. At step S33, the state of downloading is recorded in theprogram information 26. At step S34, it is judged whether downloading is completed. If downloading is not completed, control is returned to step S31. The same actions are repeated until downloading of all programs is completed. Moreover, if it is judged at step S34 that downloading of all programs is completed, downloading is terminated at step S35. At step S41, the fact is reported to the user by voice through thespeaker 28. - At step S31, if it is judged that the state of communication is improper, it is reported to the user by voice through the
speaker 28 at step S36 that downloading is suspended. Control is passed to step S37. - In the first example shown in
FIG. 5 , downloading is suspended at step S37. The unit data stored in thestorage medium 23 is deleted and processing is terminated. The suspension is reported to the user by voice. The user becomes aware of the fact that downloading is suspended. In this case, the user can re-issue a request for downloading the program to thecenter 11. Thecenter 11 then transmits the program from the beginning. - In the second example shown in
FIG. 5 , step S37 of suspending downloading is skipped but control is passed to step S38. Step 38 then waits until the state of communication to be restored. When the state of communication becomes proper, control is passed to step S39. At step S39, the state of downloading is recorded in theprogram information 26, that is, what program data has been received is recorded in theprogram information 26. The state of downloading is then reported from thecommunication unit 24 to thecenter 11. - According to the state of downloading, the
center 11 restarts downloading the program from a point in the program at which downloading was suspended. The in-vehicle terminal 21 restarts receiving a downloaded program (step S40). Thereafter, control is returned to step S31. Checking the state of communication and saving data are carried out continuously. At the in-vehicle terminal 21, when downloading is completed (step S35), the fact is reported to a user by voice (step S41). -
FIG. 6 shows a variant of the procedure described inFIG. 5 . According to the first and second examples described inFIG. 5 , if the state of communication becomes improper during downloading, either suspension of downloading or automatic restart thereof can be carried out. In the example described inFIG. 6 , a means for suspending downloading when the state of communication becomes improper and a means for restarting downloading are included, and either of the means can be selected by a user. For the selection, the user manipulates theinput unit 25 in advance. -
FIG. 6 describes modified steps of steps S36 to S38 inFIG. 5 . - When it is judged that the state of communication is improper (step S31 in
FIG. 5 ), the fact is reported to a user by voice (step S36). It is then judged at step S42 whether a user's choice is automatic continuation. If suspension of downloading is selected, control is passed to step S37 and downloading is suspended. If automatic continuation is selected, control is passed to step S38. Hereinafter, step S38 and subsequent steps similar to those inFIG. 5 are carried out. When the state of communication becomes proper, downloading is restarted. - The
power management unit 29 in the in-vehicle terminal 21 usually selects theACC power supply 30 as the power supply of the system. If the ignition key is removed during downloading, theACC power supply 30 is turned off and downloading is suspended. The present embodiment is devised to cope with this event. -
FIG. 7 describes actions to be performed when theACC power supply 30 is turned off. - When detecting that the
ACC power supply 30 is turned off, thepower management unit 29 changes the power supply for supplying power to the in-vehicle terminal 21 from the ACC power supply to the +B power supply 31. Consequently, downloading is continued. Moreover, when theACC power supply 30 is restored, thepower management unit 29 changes the power supply for supplying power to the in-vehicle terminal 21 from the +B power supply to theACC power supply 30. - When the
ACC power supply 30 is turned off, thepower management unit 29 sends an interrupt to the terminalinformation management unit 22. The terminalinformation management unit 22 keeps operating owing to the +B power supply 31. With the interrupt produced because theACC power supply 30 is turned off, a procedure described inFIG. 7 is started (step S51). It is reported to a user using voice produced by theloudspeaker 28 or using indication made by thedisplay 27 that theACC power supply 30 has been turned off (step S52). - Thereafter, the state of the
ACC power supply 30 is checked (step S53). If theACC power supply 30 is restored to the on state, the state attained before the interrupt is issued and described inFIG. 5 is resumed. If theACC power supply 30 is restored immediately by manipulating the ignition key, downloading can be continued. In this case, voice may be produced or an indication may be provided by the display. If the off state of theACC power supply 30 continues, downloading is suspended (step S54). Thepower management unit 29 is instructed to turn off the power supply of the system (step S55). - To restart downloading, a user turns on the ignition key. After power is supplied to the in-
vehicle terminal 21, manipulations are performed to issue a request for downloading to thecenter 11. Thecenter 11 transmits aprogram 13 to the in-vehicle terminal 21 from the beginning. - According to the present embodiment, when the
ACC power supply 30 is turned off because the ignition key is removed during downloading, the state can be reported to a user. Moreover, if the off state of theACC power supply 30 is transient, downloading can be restarted automatically. - According to the procedure described in
FIG. 7 , when it is detected that theACC power supply 30 is off, downloading is suspended. In contrast, according to this embodiment, even after theACC power supply 30 is turned off, downloading can be continued using the +B power supply 31. -
FIG. 8 describes a procedure of continuing downloading using the +B power supply 31 after theACC power supply 30 is turned off. Steps S61 to S63 inFIG. 8 are identical to steps S51 to S53 inFIG. 7 . Reiteration will be avoided. At step S63, if it is detected that theACC power supply 30 is still off, control is passed to step S64 in this embodiment. Downloading is continued using the +B power supply 31. When downloading is completed (step S65), thepower management unit 29 turns off the power supply of the system (step S66). -
FIG. 9 describes an example of procedures according to which a user can select in advance whether downloading is suspended or continued if theACC power supply 30 is turned off during downloading. - Steps S71 and S72 are identical to steps S51 and S52 in
FIG. 7 . When a report is made to a user at step S72, it is judged at step S73 whether the user has selected automatic continuation. The user uses theinput unit 25 to select in advance whether downloading is suspended or continued automatically. - If suspension is selected, control is passed to step S77 and downloading is suspended. If automatic continuation is selected, control is passed to step S74. Downloading is continued using the +
B power supply 31. At step S75, the state of downloading, that is, up to which unit data the program has been received is reported to thecenter 11. The procedure is then terminated. - When the
ACC power supply 30 is recovered, thepower management unit 29 changes the power supply of the system from the +B power supply 31 to theACC power supply 30. Thepower management unit 29 reports the fact to the terminalinformation management unit 22. With this report, an interrupt is produced at step S76. A request for downloading is sent to thecenter 11. Thecenter 11 transmits data succeeding to data, which was transmitted at the time of suspension of downloading, according to the state of downloading reported at step S75. - In the example described in
FIG. 9 , when downloading is restarted at step S76, thecenter 11 may transmit theprogram 13 from the beginning. In this case, at step S75, the terminalinformation management unit 22 deletes the program that was stored up to the middle thereof. - In a variant of the procedure described in
FIG. 9 , steps S74 to S76 may be replaced with steps S64 to S66 described inFIG. 8 . In this case, when a user selects that if the ACC power supply is turned off, downloading is continued, the +B power supply 31 is used to continue downloading. After downloading is terminated, the power supply of the system is turned off. - A description has been made of a means for checking whether downloading has been completed without any problem. Next, a description will be made of a means enabling the
center 11 to check whether after downloading is completed without any problem, a program is operating normally while being compatible with the software and hardware environment of an in-vehicle terminal. -
FIG. 10 describes an example of procedures according to which when a certain time has elapsed after activation of a program, it is judged that the program is operating normally. - When a user performs manipulations or when any other application program calls a program, a trigger pulse is produced by the
input unit 25. The terminalinformation management unit 22 activates the program (step S81). Theprogram 13 operates continuously after activated. The terminalinformation management unit 22 waits until a certain time has elapsed (step S82). When the certain time has elapsed, it is reported to thecenter 11 that the program has been activated and the certain time has elapsed (step S83). At this time, the fact that a report is sent to thecenter 11 may be indicated on thedisplay 27. - Moreover, even when the certain time has not elapsed, if the user satisfies the action of the program, the user may perform predetermined manipulations on the input unit (step S84). Thus, it is reported to the
center 11 that the program has been activated normally. The step S84 may be omitted. - Thus, the
center 11 can be aware of the fact that downloading has been completed without any problem and a program is operating normally. -
FIG. 11 describes an example of procedures according to which when the number of times by which aprogram 13 has been activated exceeds a certain number of times, it is judged that the program is operating normally. - Step S91 in
FIG. 11 is identical to step S81 inFIG. 10 . When a user performs manipulations or when any other application program calls a program, the program is activated. With the program left activated, the number of times by which the program has been activated is checked (step S92). The number of times of activation is acquired from theprogram information 26. If the program has been activated a certain number of times or more, the fact is reported to the center 11 (step S93). - Even when the program has not been activated by the certain number of times, if the user performs predetermined manipulations (step S94), the fact is reported to the center 11 (step S93). Step S94 is analogous to step S84 in
FIG. 10 . Even in this embodiment, step S94 can be omitted. - In the aforesaid first to eighth embodiments, the
center 11 downloads aprogram 13 in response to a request sent from the in-vehicle terminal 21. Moreover, every time a program is updated to a higher version, a user requests downloading of an updated program. -
FIG. 12 described an example of procedures according to which when a program is updated, a request for downloading the updated program is issued automatically to thecenter 11. This obviates the necessity that a user must issue a request for downloading every time a program is updated. - A user performs predetermined manipulations on the
input unit 25 to designate automatic updating (step S101). The terminalinformation management unit 22 reports to theprogram center 11 that automatic updating has been reserved (step S102). At this time, the user may designate that downloading is performed for automatic updating during a time band during which a vehicle is not driven, for example, at midnight. - In response to the request, the
center 11 records, in theprogram information 15, that automatic updating has been reserved (step S111). - When the
center 11 has updated a program 13 (step S121), thecenter 11 downloads theprogram 13 to users who have reserved automatic updating (step S122). At this time, if a time band is designated, the program is transmitted during the time band. In this case, when sensing that the in-vehicle terminal 21 is called by thecenter 11, the terminalinformation management unit 22 in the in-vehicle terminal 21 automatically turns on the power supply of the system. Thereafter, the program is downloaded according to the actions described inFIG. 5 andFIG. 6 . Moreover, when downloading is terminated, the power supply of the system is turned off. - Thereafter, when the
ACC power supply 30 is turned on, the terminalinformation management unit 22 indicates on thedisplay 27 that automatic updating of the program has been carried out. The user becomes aware of the fact that downloading has been carried out. - According to the present invention, there is provided a communication system for downloading programs from a center to in-vehicle terminals. The center can readily check whether downloading has been completed normally or a program is operating normally in a in-vehicle terminal.
Claims (1)
1. A computer readable storage medium storing a program, wherein a facility for storing a downloaded program in a storage unit, and a facility for transmitting information, which indicates whether downloading has been completed normally, according to the timing of activating the stored program are implemented in a computer using said program.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/339,636 US20060122744A1 (en) | 1999-01-18 | 2006-01-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP11009649A JP2000207219A (en) | 1999-01-18 | 1999-01-18 | Communication system for between on-vehicle terminal and center, and the on-vehicle terminal used for communication system |
JP11-009649 | 1999-01-18 | ||
US09/461,423 US6647322B1 (en) | 1999-01-18 | 1999-12-16 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/105,306 US7286908B2 (en) | 1999-01-18 | 2002-03-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/288,438 US7280894B2 (en) | 1999-01-18 | 2002-11-06 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US11/339,636 US20060122744A1 (en) | 1999-01-18 | 2006-01-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/288,438 Division US7280894B2 (en) | 1999-01-18 | 2002-11-06 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060122744A1 true US20060122744A1 (en) | 2006-06-08 |
Family
ID=11726076
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/461,423 Expired - Lifetime US6647322B1 (en) | 1999-01-18 | 1999-12-16 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/105,306 Expired - Fee Related US7286908B2 (en) | 1999-01-18 | 2002-03-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/105,359 Expired - Fee Related US6631313B2 (en) | 1999-01-18 | 2002-03-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/288,438 Expired - Fee Related US7280894B2 (en) | 1999-01-18 | 2002-11-06 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/373,021 Expired - Fee Related US6760650B2 (en) | 1999-01-18 | 2003-02-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US11/339,613 Expired - Fee Related US7349769B2 (en) | 1999-01-18 | 2006-01-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US11/339,636 Abandoned US20060122744A1 (en) | 1999-01-18 | 2006-01-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
Family Applications Before (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/461,423 Expired - Lifetime US6647322B1 (en) | 1999-01-18 | 1999-12-16 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/105,306 Expired - Fee Related US7286908B2 (en) | 1999-01-18 | 2002-03-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/105,359 Expired - Fee Related US6631313B2 (en) | 1999-01-18 | 2002-03-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/288,438 Expired - Fee Related US7280894B2 (en) | 1999-01-18 | 2002-11-06 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US10/373,021 Expired - Fee Related US6760650B2 (en) | 1999-01-18 | 2003-02-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US11/339,613 Expired - Fee Related US7349769B2 (en) | 1999-01-18 | 2006-01-26 | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
Country Status (3)
Country | Link |
---|---|
US (7) | US6647322B1 (en) |
EP (8) | EP1022656A3 (en) |
JP (1) | JP2000207219A (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070232363A1 (en) * | 2006-03-31 | 2007-10-04 | Mitsumi Electric Co., Ltd. | Communication channel establishing method, communication system, and communication apparatus |
US20120323402A1 (en) * | 2011-06-16 | 2012-12-20 | Fujitsu Ten Limited | Server |
US10659287B2 (en) | 2012-05-23 | 2020-05-19 | Denso Corporation | Management server |
Families Citing this family (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000207219A (en) * | 1999-01-18 | 2000-07-28 | Fujitsu Ten Ltd | Communication system for between on-vehicle terminal and center, and the on-vehicle terminal used for communication system |
US6685978B1 (en) | 2000-04-04 | 2004-02-03 | Cp Kelco Aps | Gelled and gellable compositions for food products |
GB2361566B (en) * | 2000-04-19 | 2004-10-06 | Ncr Int Inc | Transaction terminal interface |
US6993328B1 (en) * | 2000-05-08 | 2006-01-31 | Nokia Corporation | Method for over the air mobile station management |
JP3602036B2 (en) | 2000-06-30 | 2004-12-15 | シャープ株式会社 | Program supply system and program supply method |
US7693961B2 (en) | 2000-06-30 | 2010-04-06 | Sharp Kabushiki Kaisha | Method and system for supplying programs |
JPWO2002021506A1 (en) * | 2000-09-05 | 2004-01-15 | 株式会社エヌ・ティ・ティ・ドコモ | Paid information distribution system |
JP3791314B2 (en) | 2000-09-14 | 2006-06-28 | 株式会社デンソー | In-vehicle device and service providing system |
DE10053214A1 (en) * | 2000-10-26 | 2002-05-02 | Siemens Ag | Software installation procedures |
JP4857462B2 (en) * | 2000-11-07 | 2012-01-18 | パナソニック株式会社 | Digital broadcast receiver |
JP2002181552A (en) * | 2000-12-11 | 2002-06-26 | Nippon Telegr & Teleph Corp <Ntt> | Server-type navigation system |
CN1462402A (en) * | 2001-04-24 | 2003-12-17 | 索尼株式会社 | Information processing method and device for charging |
US20040040023A1 (en) * | 2002-08-22 | 2004-02-26 | Ellis David G. | Remote identification loader |
JP4221261B2 (en) | 2003-09-04 | 2009-02-12 | 株式会社日立製作所 | Program distribution system |
JP2005092732A (en) * | 2003-09-19 | 2005-04-07 | Nec Corp | Service provision method and system in passenger vehicle |
JP2005115781A (en) * | 2003-10-09 | 2005-04-28 | Mobile Hoso Kk | Software providing method and system, terminal, and software acquisition method |
US20050216902A1 (en) * | 2004-03-23 | 2005-09-29 | General Motors Corporation | Method and system for vehicle software configuration update management |
JP2005332176A (en) | 2004-05-19 | 2005-12-02 | Sony Corp | Content acquiring method |
US7676804B2 (en) * | 2004-05-20 | 2010-03-09 | Caterpillar Inc. | Systems and method for remotely modifying software on a work machine |
JP4599953B2 (en) * | 2004-09-15 | 2010-12-15 | 株式会社デンソー | Program rewriting system and vehicle computer system |
FR2875319B1 (en) * | 2004-09-16 | 2008-04-11 | Renault Sas | ON-BOARD SYSTEM AND CALCULATOR TO PUT UP DATA UNLOADING IN CASE OF STOPPING THE COMPUTER |
KR100764791B1 (en) * | 2005-04-08 | 2007-10-11 | 엘지전자 주식회사 | System and method for scheduling device management |
US9883019B2 (en) * | 2005-04-28 | 2018-01-30 | Kyocera Corporation | Mobile communication terminal and software update method |
JP2007011734A (en) * | 2005-06-30 | 2007-01-18 | Denso Corp | On-vehicle control unit |
JP4998816B2 (en) * | 2005-07-19 | 2012-08-15 | スズキ株式会社 | Electronic controller program rewriting system |
JP4548307B2 (en) * | 2005-10-31 | 2010-09-22 | ソニー株式会社 | Separation type processing apparatus and software version updating method |
US8204611B2 (en) * | 2007-02-20 | 2012-06-19 | Caterpillar Inc. | Method for reducing quiescent power draw and machine using same |
US20080201023A1 (en) * | 2007-02-20 | 2008-08-21 | Darrel Berglund | Method for reducing quiescent power draw and machine using same |
JP2008269395A (en) | 2007-04-23 | 2008-11-06 | Fujitsu Ten Ltd | Multimedia system and navigation unit terminal |
US8938735B2 (en) * | 2007-08-31 | 2015-01-20 | Thomson Reuters Global Resources | Bootstrapper and software download manager |
US7818403B2 (en) * | 2007-09-17 | 2010-10-19 | Gm Global Technology Operations, Inc. | System for using non-standard transfer protocol from software received at client device for exchanging data with in-vehicle communications gateway |
US7822828B2 (en) * | 2007-09-17 | 2010-10-26 | Gm Global Technology Operations, Inc. | System for using non-standard transfer protocol from software received at in-vehicle communications gateway for exchanging data with client device |
US7849224B2 (en) * | 2007-09-17 | 2010-12-07 | Gm Global Technology Operations, Inc. | Method and apparatus for implementing a mobile server |
FR2921169B1 (en) * | 2007-09-19 | 2009-12-04 | Peugeot Citroen Automobiles Sa | METHOD AND SYSTEM FOR DOWNLOADING THE REACTIVITY AREA OF A FILE IN COMPUTERS OF MOTOR VEHICLES USING A DOWNLOADING TOOL |
JP2009199313A (en) * | 2008-02-21 | 2009-09-03 | Kenwood Corp | Road-to-vehicle communication system |
KR101383573B1 (en) * | 2008-08-01 | 2014-04-09 | 삼성전자주식회사 | Electronic apparatus and web-information providing method thereof |
WO2010113348A1 (en) | 2009-03-31 | 2010-10-07 | トヨタ自動車株式会社 | Device for updating software mounted on vehicle |
JP5558963B2 (en) * | 2010-08-03 | 2014-07-23 | 本田技研工業株式会社 | Program rewriting system for vehicles |
JP5558962B2 (en) * | 2010-08-03 | 2014-07-23 | 本田技研工業株式会社 | Program rewriting system for vehicles |
JP5629927B2 (en) * | 2010-11-12 | 2014-11-26 | クラリオン株式会社 | Online update method for in-vehicle devices |
JP5887952B2 (en) * | 2012-01-25 | 2016-03-16 | 株式会社デンソー | In-vehicle terminal and application execution environment program |
JP5997740B2 (en) * | 2014-09-17 | 2016-09-28 | クラリオン株式会社 | Online update method for in-vehicle devices |
US9720680B2 (en) | 2015-07-23 | 2017-08-01 | Honda Motor Co., Ltd. | Methods and apparatus for wirelessly updating vehicle systems |
US10353691B2 (en) | 2016-09-30 | 2019-07-16 | Cummins Inc. | Updating electronic controller through telematics |
TWI607912B (en) * | 2016-10-14 | 2017-12-11 | 光陽工業股份有限公司 | Program updating method and system of vehicle |
US10353696B2 (en) * | 2017-04-13 | 2019-07-16 | Blackberry Limited | Program release packages including program updates |
RU2703850C1 (en) * | 2018-05-29 | 2019-10-22 | Федеральное государственное бюджетное учреждение науки Сибирский федеральный научный центр агробиотехнологий Российской академии наук (СФНЦА РАН) | Method for remote diagnosis of internal combustion engine technical state |
US11356425B2 (en) | 2018-11-30 | 2022-06-07 | Paccar Inc | Techniques for improving security of encrypted vehicle software updates |
US11449327B2 (en) | 2018-11-30 | 2022-09-20 | Paccar Inc | Error-resilient over-the-air software updates for vehicles |
CN111614521B (en) * | 2020-05-29 | 2022-12-02 | 北京小马智行科技有限公司 | Monitoring method and device for mobile carrier, storage medium and processor |
JP7194761B2 (en) * | 2021-01-13 | 2022-12-22 | 本田技研工業株式会社 | Control system, moving object, control method, and program |
Citations (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5504801A (en) * | 1994-02-09 | 1996-04-02 | Harris Corporation | User-controlled electronic modification of operating system firmware resident in remote measurement unit for testing and conditioning of subscriber line circuits |
US5544087A (en) * | 1993-06-04 | 1996-08-06 | Sumitomo Electric Industries, Ltd. | Navigation system |
US5649187A (en) * | 1989-04-28 | 1997-07-15 | Softel, Inc. | Method and apparatus for remotely controlling and monitoring the use of computer software |
US5689825A (en) * | 1995-07-28 | 1997-11-18 | Motorola, Inc. | Method and apparatus for downloading updated software to portable wireless communication units |
US5717744A (en) * | 1994-03-16 | 1998-02-10 | Canon Kabushiki Kaisha | Data communicating apparatus having user notification capability and method |
US5752042A (en) * | 1996-06-07 | 1998-05-12 | International Business Machines Corporation | Server computer for selecting program updates for a client computer based on results of recognizer program(s) furnished to the client computer |
US5754526A (en) * | 1995-03-16 | 1998-05-19 | Fujitsu Limited | Channel switching method and channel switching controller |
US5790796A (en) * | 1996-06-14 | 1998-08-04 | Symantec Corporation | Polymorphic package files to update software components |
US5802258A (en) * | 1996-05-03 | 1998-09-01 | International Business Machines Corporation | Loosely coupled system environment designed to handle a non-disruptive host connection switch after detection of an error condition or during a host outage or failure |
US5805897A (en) * | 1992-07-31 | 1998-09-08 | International Business Machines Corporation | System and method for remote software configuration and distribution |
US5809287A (en) * | 1994-09-08 | 1998-09-15 | Compaq Computer Corporation | Automatic computer upgrading |
US5835911A (en) * | 1994-02-08 | 1998-11-10 | Fujitsu Limited | Software distribution and maintenance system and method |
US5845326A (en) * | 1995-06-19 | 1998-12-01 | Kabushiki Kaisha Toshiba | Computer system and method for obtaining memory check points and recovering from faults using the checkpoints and cache flush operations |
US5867781A (en) * | 1995-04-21 | 1999-02-02 | Siemens Aktiengesellschaft | Mobile radiotelephone system and broadcast station |
US5870610A (en) * | 1996-06-28 | 1999-02-09 | Siemens Business Communication Systems, Inc. | Autoconfigurable method and system having automated downloading |
US5874461A (en) * | 1994-12-28 | 1999-02-23 | Janssen Pharmaceutica N.V. | Use of Nebivolol as an anti-atherogenic |
US5887254A (en) * | 1996-04-26 | 1999-03-23 | Nokia Mobile Phones Limited | Methods and apparatus for updating the software of a mobile terminal using the air interface |
US5890075A (en) * | 1996-10-21 | 1999-03-30 | Lucent Technologies Inc. | Method for remotely updating data stored in a mobile terminal by a wireless telecommunications system |
US5937343A (en) * | 1994-09-13 | 1999-08-10 | At&T Corp. | Method and system for updating replicated databases in a telecommunication network system |
US5951620A (en) * | 1996-01-26 | 1999-09-14 | Navigation Technologies Corporation | System and method for distributing information for storage media |
US5956480A (en) * | 1993-11-19 | 1999-09-21 | Fujitsu Limited | Terminal and online system for tracking version of data and program |
US5974461A (en) * | 1996-06-03 | 1999-10-26 | Webtv Networks, Inc. | Method for automatically regenerating information at a client system in the event of power or communication disruption between the client system and the server |
US5999740A (en) * | 1996-11-08 | 1999-12-07 | International Computers Limited | Updating mechanism for software |
US5999876A (en) * | 1998-04-01 | 1999-12-07 | Cummins Engine Company, Inc. | Method and system for communication with an engine control module in sleep mode |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US6075467A (en) * | 1997-08-21 | 2000-06-13 | Toyota Jidosha Kabushiki Kaisha | Map data selection supporting device, and map data processing system and map data processing device including the same |
US6074435A (en) * | 1997-10-30 | 2000-06-13 | Telefonakiebolaget Lm Ericsson (Publ) | Remote software download with automatic adjustment for data access compatibility |
US6094618A (en) * | 1997-10-17 | 2000-07-25 | Toyota Jidosha Kabushiki Kaisha | On-vehicle device control system and control apparatus therein |
US6108598A (en) * | 1996-04-23 | 2000-08-22 | Mitsubishi Denki Kabusihiki Kaisha | Onboard control system for controlling devices installed on motor vehicle and method or rewriting control program and variables therefor |
US6115611A (en) * | 1996-04-24 | 2000-09-05 | Fujitsu Limited | Mobile communication system, and a mobile terminal, an information center and a storage medium used therein |
US6122682A (en) * | 1997-03-24 | 2000-09-19 | Toyota Jidosha Kabushiki Kaisha | Communication system for controlling data processing according to a state of a communication terminal device |
US6141683A (en) * | 1998-01-30 | 2000-10-31 | Lucent Technologies, Inc. | Method for remotely and reliably updating of the software on a computer with provision for roll back |
US6151708A (en) * | 1997-12-19 | 2000-11-21 | Microsoft Corporation | Determining program update availability via set intersection over a sub-optical pathway |
US6175918B1 (en) * | 1997-08-11 | 2001-01-16 | Kabushiki Kaisha Toshiba | Client computer, initialization processing method applied to client computer, and computer program product used in client computer |
US6195678B1 (en) * | 1996-09-03 | 2001-02-27 | Fujitsu Limited | Remote resource management system for automatically downloading required files from application server depending on contents of selected files on requesting computer |
US6195547B1 (en) * | 1998-09-24 | 2001-02-27 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for a previously activated mobile station to challenge network mobile station knowledge during over the air activation |
US6195546B1 (en) * | 1997-03-14 | 2001-02-27 | Nortel Networks Limited | Method and apparatus for network initiated parameter updating |
US6199204B1 (en) * | 1998-01-28 | 2001-03-06 | International Business Machines Corporation | Distribution of software updates via a computer network |
US6230082B1 (en) * | 1997-10-03 | 2001-05-08 | Toyota Jidosha Kabushiki Kaisha | Vehicle-use data backup system and on-vehicle terminal apparatus comprised in the system |
US6237039B1 (en) * | 1998-06-30 | 2001-05-22 | Webtv Networks, Inc. | Method and apparatus for downloading auxiliary data to a client from a network during client idle periods |
US6266774B1 (en) * | 1998-12-08 | 2001-07-24 | Mcafee.Com Corporation | Method and system for securing, managing or optimizing a personal computer |
US6282709B1 (en) * | 1997-11-12 | 2001-08-28 | Philips Electronics North America Corporation | Software update manager |
US6289510B1 (en) * | 1998-03-12 | 2001-09-11 | Fujitsu Limited | Online program-updating system and computer-readable recording medium storing a program-updating program |
US6347398B1 (en) * | 1996-12-12 | 2002-02-12 | Microsoft Corporation | Automatic software downloading from a computer network |
US6367077B1 (en) * | 1997-02-27 | 2002-04-02 | Siebel Systems, Inc. | Method of upgrading a software application in the presence of user modifications |
US6377886B1 (en) * | 1997-07-31 | 2002-04-23 | Honda Giken Kogyo Kabushiki Kaisha | Navigation apparatus and medium recording program therefor |
US6396805B2 (en) * | 1997-03-25 | 2002-05-28 | Intel Corporation | System for recovering from disruption of a data transfer |
US6438750B1 (en) * | 1999-06-18 | 2002-08-20 | Phoenix Technologies Ltd. | Determining loading time of an operating system |
US6490616B1 (en) * | 1999-06-14 | 2002-12-03 | Wind River International, Ltd. | Method and apparatus for incremental download from server to client |
US6526447B1 (en) * | 1999-12-14 | 2003-02-25 | International Business Machines Corporation | Apparatus for restarting interrupted data transfer and method therefor |
US6647322B1 (en) * | 1999-01-18 | 2003-11-11 | Fujitsu Ten Limited | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US6870907B1 (en) * | 1997-10-17 | 2005-03-22 | Sony Corporation | Data distribution system, distribution equipment, terminal equipment and data distribution method |
Family Cites Families (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5014234A (en) * | 1986-08-25 | 1991-05-07 | Ncr Corporation | System with software usage timer and counter for allowing limited use but preventing continued unauthorized use of protected software |
JPH0375947A (en) | 1989-08-18 | 1991-03-29 | Pfu Ltd | Access control system for host cooperation system |
US5151907A (en) * | 1990-02-20 | 1992-09-29 | Robbins Walter A | Auxiliary power supply for continuation of computer system operation during commercial AC power failure |
JPH03252818A (en) | 1990-03-02 | 1991-11-12 | Fujitsu Ltd | Down load control system |
JPH0557945A (en) | 1991-05-09 | 1993-03-09 | Seiko Epson Corp | Controlling circuit for energization of heating element |
JPH0512000A (en) | 1991-07-03 | 1993-01-22 | Fujitsu Ten Ltd | Terminal software version changing method |
JPH05257753A (en) | 1992-03-03 | 1993-10-08 | Nec Corp | Fault alarm output circuit of peripheral controller |
JPH06131163A (en) | 1992-10-20 | 1994-05-13 | Fujitsu Ltd | Remote maintenance system |
US5418837A (en) * | 1993-07-30 | 1995-05-23 | Ericsson-Ge Mobile Communications Inc. | Method and apparatus for upgrading cellular mobile telephones |
DE69323424T2 (en) * | 1993-09-15 | 1999-06-17 | Texas Instruments Deutschland | A transponder system |
US6094575A (en) * | 1993-11-01 | 2000-07-25 | Omnipoint Corporation | Communication system and method |
JP3424305B2 (en) | 1994-02-17 | 2003-07-07 | 富士ゼロックス株式会社 | Service billing method and device |
US6732358B1 (en) * | 1994-03-24 | 2004-05-04 | Ncr Corporation | Automatic updating of computer software |
JPH08147169A (en) | 1994-11-17 | 1996-06-07 | Fujitsu Ltd | Network connector |
JPH08255129A (en) | 1995-03-16 | 1996-10-01 | Toshiba Corp | Client device and data selecting method |
JPH08263405A (en) | 1995-03-28 | 1996-10-11 | Mitsubishi Electric Corp | Software distribution system |
JPH08328867A (en) | 1995-06-06 | 1996-12-13 | Canon Inc | Program confirmation method for digital signal processor and digital signal processor system |
JPH09218788A (en) | 1996-02-09 | 1997-08-19 | Fujitsu Ltd | Inservice direct down loading system |
US5790664A (en) * | 1996-02-26 | 1998-08-04 | Network Engineering Software, Inc. | Automated system for management of licensed software |
US5940074A (en) * | 1996-06-03 | 1999-08-17 | Webtv Networks, Inc. | Remote upgrade of software over a network |
US6151643A (en) * | 1996-06-07 | 2000-11-21 | Networks Associates, Inc. | Automatic updating of diverse software products on multiple client computer systems by downloading scanning application to client computer and generating software list on client computer |
JPH1011293A (en) | 1996-06-27 | 1998-01-16 | Nec Corp | Information processor |
JPH1055260A (en) | 1996-08-08 | 1998-02-24 | Matsushita Electric Ind Co Ltd | Multi-task management system |
GB2318008B (en) * | 1996-09-16 | 2001-02-14 | Minorplanet Ltd | Monitoring vehicle positions |
JPH10171635A (en) | 1996-10-09 | 1998-06-26 | N T T Data Tsushin Kk | System and method for managing software resource in distributed environments |
US6963923B1 (en) * | 1997-02-10 | 2005-11-08 | International Business Machines Corporation | Method for file transfer restarts using standard internet protocol |
US6049892C1 (en) * | 1997-02-24 | 2002-06-04 | Ethos Software Corp | Process and apparatus for downloading data from a server computer to a client computer |
JPH10240654A (en) | 1997-02-28 | 1998-09-11 | Toshiba Corp | Portable information equipment and data transfer control method |
JP4138064B2 (en) | 1997-02-28 | 2008-08-20 | 富士通株式会社 | User management and service system for computer-related products |
US6123737A (en) * | 1997-05-21 | 2000-09-26 | Symantec Corporation | Push deployment of software packages using notification transports |
JPH114483A (en) | 1997-06-13 | 1999-01-06 | Sumitomo Electric Ind Ltd | Navigation system |
JPH11272353A (en) * | 1998-03-19 | 1999-10-08 | Toshiba Corp | Clock supply circuit and data transfer circuit |
-
1999
- 1999-01-18 JP JP11009649A patent/JP2000207219A/en active Pending
- 1999-12-15 EP EP99310077A patent/EP1022656A3/en not_active Ceased
- 1999-12-15 EP EP05014969A patent/EP1596296A3/en not_active Withdrawn
- 1999-12-15 EP EP05014966A patent/EP1596293A3/en not_active Withdrawn
- 1999-12-15 EP EP05014964A patent/EP1594056A3/en not_active Withdrawn
- 1999-12-15 EP EP05014967A patent/EP1596294A3/en not_active Withdrawn
- 1999-12-15 EP EP05014965A patent/EP1596292A3/en not_active Withdrawn
- 1999-12-15 EP EP05014970A patent/EP1596297A3/en not_active Withdrawn
- 1999-12-15 EP EP05014968A patent/EP1596295A3/en not_active Withdrawn
- 1999-12-16 US US09/461,423 patent/US6647322B1/en not_active Expired - Lifetime
-
2002
- 2002-03-26 US US10/105,306 patent/US7286908B2/en not_active Expired - Fee Related
- 2002-03-26 US US10/105,359 patent/US6631313B2/en not_active Expired - Fee Related
- 2002-11-06 US US10/288,438 patent/US7280894B2/en not_active Expired - Fee Related
-
2003
- 2003-02-26 US US10/373,021 patent/US6760650B2/en not_active Expired - Fee Related
-
2006
- 2006-01-26 US US11/339,613 patent/US7349769B2/en not_active Expired - Fee Related
- 2006-01-26 US US11/339,636 patent/US20060122744A1/en not_active Abandoned
Patent Citations (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5649187A (en) * | 1989-04-28 | 1997-07-15 | Softel, Inc. | Method and apparatus for remotely controlling and monitoring the use of computer software |
US5805897A (en) * | 1992-07-31 | 1998-09-08 | International Business Machines Corporation | System and method for remote software configuration and distribution |
US5544087A (en) * | 1993-06-04 | 1996-08-06 | Sumitomo Electric Industries, Ltd. | Navigation system |
US5956480A (en) * | 1993-11-19 | 1999-09-21 | Fujitsu Limited | Terminal and online system for tracking version of data and program |
US5835911A (en) * | 1994-02-08 | 1998-11-10 | Fujitsu Limited | Software distribution and maintenance system and method |
US5504801A (en) * | 1994-02-09 | 1996-04-02 | Harris Corporation | User-controlled electronic modification of operating system firmware resident in remote measurement unit for testing and conditioning of subscriber line circuits |
US5717744A (en) * | 1994-03-16 | 1998-02-10 | Canon Kabushiki Kaisha | Data communicating apparatus having user notification capability and method |
US5809287A (en) * | 1994-09-08 | 1998-09-15 | Compaq Computer Corporation | Automatic computer upgrading |
US5937343A (en) * | 1994-09-13 | 1999-08-10 | At&T Corp. | Method and system for updating replicated databases in a telecommunication network system |
US5874461A (en) * | 1994-12-28 | 1999-02-23 | Janssen Pharmaceutica N.V. | Use of Nebivolol as an anti-atherogenic |
US5754526A (en) * | 1995-03-16 | 1998-05-19 | Fujitsu Limited | Channel switching method and channel switching controller |
US5867781A (en) * | 1995-04-21 | 1999-02-02 | Siemens Aktiengesellschaft | Mobile radiotelephone system and broadcast station |
US5845326A (en) * | 1995-06-19 | 1998-12-01 | Kabushiki Kaisha Toshiba | Computer system and method for obtaining memory check points and recovering from faults using the checkpoints and cache flush operations |
US5689825A (en) * | 1995-07-28 | 1997-11-18 | Motorola, Inc. | Method and apparatus for downloading updated software to portable wireless communication units |
US5951620A (en) * | 1996-01-26 | 1999-09-14 | Navigation Technologies Corporation | System and method for distributing information for storage media |
US6108598A (en) * | 1996-04-23 | 2000-08-22 | Mitsubishi Denki Kabusihiki Kaisha | Onboard control system for controlling devices installed on motor vehicle and method or rewriting control program and variables therefor |
US6115611A (en) * | 1996-04-24 | 2000-09-05 | Fujitsu Limited | Mobile communication system, and a mobile terminal, an information center and a storage medium used therein |
US5887254A (en) * | 1996-04-26 | 1999-03-23 | Nokia Mobile Phones Limited | Methods and apparatus for updating the software of a mobile terminal using the air interface |
US5802258A (en) * | 1996-05-03 | 1998-09-01 | International Business Machines Corporation | Loosely coupled system environment designed to handle a non-disruptive host connection switch after detection of an error condition or during a host outage or failure |
US5974461A (en) * | 1996-06-03 | 1999-10-26 | Webtv Networks, Inc. | Method for automatically regenerating information at a client system in the event of power or communication disruption between the client system and the server |
US5752042A (en) * | 1996-06-07 | 1998-05-12 | International Business Machines Corporation | Server computer for selecting program updates for a client computer based on results of recognizer program(s) furnished to the client computer |
US5790796A (en) * | 1996-06-14 | 1998-08-04 | Symantec Corporation | Polymorphic package files to update software components |
US5870610A (en) * | 1996-06-28 | 1999-02-09 | Siemens Business Communication Systems, Inc. | Autoconfigurable method and system having automated downloading |
US6195678B1 (en) * | 1996-09-03 | 2001-02-27 | Fujitsu Limited | Remote resource management system for automatically downloading required files from application server depending on contents of selected files on requesting computer |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US5890075A (en) * | 1996-10-21 | 1999-03-30 | Lucent Technologies Inc. | Method for remotely updating data stored in a mobile terminal by a wireless telecommunications system |
US5999740A (en) * | 1996-11-08 | 1999-12-07 | International Computers Limited | Updating mechanism for software |
US6347398B1 (en) * | 1996-12-12 | 2002-02-12 | Microsoft Corporation | Automatic software downloading from a computer network |
US6367077B1 (en) * | 1997-02-27 | 2002-04-02 | Siebel Systems, Inc. | Method of upgrading a software application in the presence of user modifications |
US6195546B1 (en) * | 1997-03-14 | 2001-02-27 | Nortel Networks Limited | Method and apparatus for network initiated parameter updating |
US6122682A (en) * | 1997-03-24 | 2000-09-19 | Toyota Jidosha Kabushiki Kaisha | Communication system for controlling data processing according to a state of a communication terminal device |
US6396805B2 (en) * | 1997-03-25 | 2002-05-28 | Intel Corporation | System for recovering from disruption of a data transfer |
US6377886B1 (en) * | 1997-07-31 | 2002-04-23 | Honda Giken Kogyo Kabushiki Kaisha | Navigation apparatus and medium recording program therefor |
US6175918B1 (en) * | 1997-08-11 | 2001-01-16 | Kabushiki Kaisha Toshiba | Client computer, initialization processing method applied to client computer, and computer program product used in client computer |
US6075467A (en) * | 1997-08-21 | 2000-06-13 | Toyota Jidosha Kabushiki Kaisha | Map data selection supporting device, and map data processing system and map data processing device including the same |
US6230082B1 (en) * | 1997-10-03 | 2001-05-08 | Toyota Jidosha Kabushiki Kaisha | Vehicle-use data backup system and on-vehicle terminal apparatus comprised in the system |
US6094618A (en) * | 1997-10-17 | 2000-07-25 | Toyota Jidosha Kabushiki Kaisha | On-vehicle device control system and control apparatus therein |
US6870907B1 (en) * | 1997-10-17 | 2005-03-22 | Sony Corporation | Data distribution system, distribution equipment, terminal equipment and data distribution method |
US6074435A (en) * | 1997-10-30 | 2000-06-13 | Telefonakiebolaget Lm Ericsson (Publ) | Remote software download with automatic adjustment for data access compatibility |
US6282709B1 (en) * | 1997-11-12 | 2001-08-28 | Philips Electronics North America Corporation | Software update manager |
US6151708A (en) * | 1997-12-19 | 2000-11-21 | Microsoft Corporation | Determining program update availability via set intersection over a sub-optical pathway |
US6199204B1 (en) * | 1998-01-28 | 2001-03-06 | International Business Machines Corporation | Distribution of software updates via a computer network |
US6141683A (en) * | 1998-01-30 | 2000-10-31 | Lucent Technologies, Inc. | Method for remotely and reliably updating of the software on a computer with provision for roll back |
US6289510B1 (en) * | 1998-03-12 | 2001-09-11 | Fujitsu Limited | Online program-updating system and computer-readable recording medium storing a program-updating program |
US5999876A (en) * | 1998-04-01 | 1999-12-07 | Cummins Engine Company, Inc. | Method and system for communication with an engine control module in sleep mode |
US6237039B1 (en) * | 1998-06-30 | 2001-05-22 | Webtv Networks, Inc. | Method and apparatus for downloading auxiliary data to a client from a network during client idle periods |
US6195547B1 (en) * | 1998-09-24 | 2001-02-27 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for a previously activated mobile station to challenge network mobile station knowledge during over the air activation |
US6266774B1 (en) * | 1998-12-08 | 2001-07-24 | Mcafee.Com Corporation | Method and system for securing, managing or optimizing a personal computer |
US6647322B1 (en) * | 1999-01-18 | 2003-11-11 | Fujitsu Ten Limited | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system |
US6490616B1 (en) * | 1999-06-14 | 2002-12-03 | Wind River International, Ltd. | Method and apparatus for incremental download from server to client |
US6438750B1 (en) * | 1999-06-18 | 2002-08-20 | Phoenix Technologies Ltd. | Determining loading time of an operating system |
US6526447B1 (en) * | 1999-12-14 | 2003-02-25 | International Business Machines Corporation | Apparatus for restarting interrupted data transfer and method therefor |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070232363A1 (en) * | 2006-03-31 | 2007-10-04 | Mitsumi Electric Co., Ltd. | Communication channel establishing method, communication system, and communication apparatus |
US8014441B2 (en) * | 2006-03-31 | 2011-09-06 | Mitsumi Electric Co., Ltd. | Communication channel establishing method, communication system, and communication apparatus |
US20120323402A1 (en) * | 2011-06-16 | 2012-12-20 | Fujitsu Ten Limited | Server |
US8965627B2 (en) * | 2011-06-16 | 2015-02-24 | Fujitsu Ten Limited | Distance based vehicle updating server |
US10659287B2 (en) | 2012-05-23 | 2020-05-19 | Denso Corporation | Management server |
Also Published As
Publication number | Publication date |
---|---|
US6631313B2 (en) | 2003-10-07 |
JP2000207219A (en) | 2000-07-28 |
EP1596296A3 (en) | 2007-01-10 |
EP1596292A2 (en) | 2005-11-16 |
EP1594056A3 (en) | 2007-01-10 |
US7286908B2 (en) | 2007-10-23 |
EP1594056A2 (en) | 2005-11-09 |
EP1596294A3 (en) | 2007-01-10 |
EP1596297A2 (en) | 2005-11-16 |
EP1596297A3 (en) | 2007-01-10 |
EP1022656A3 (en) | 2003-02-26 |
US20050246069A1 (en) | 2005-11-03 |
US20020103578A1 (en) | 2002-08-01 |
EP1596293A3 (en) | 2007-01-10 |
US7280894B2 (en) | 2007-10-09 |
EP1596295A3 (en) | 2007-01-10 |
EP1596296A2 (en) | 2005-11-16 |
US7349769B2 (en) | 2008-03-25 |
US20060122743A1 (en) | 2006-06-08 |
US20020103579A1 (en) | 2002-08-01 |
EP1596294A2 (en) | 2005-11-16 |
EP1596292A3 (en) | 2007-01-24 |
US20030139857A1 (en) | 2003-07-24 |
US6760650B2 (en) | 2004-07-06 |
EP1596293A2 (en) | 2005-11-16 |
EP1596295A2 (en) | 2005-11-16 |
US6647322B1 (en) | 2003-11-11 |
EP1022656A2 (en) | 2000-07-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6760650B2 (en) | Communication system for communication between in-vehicle terminals and center, and in-vehicle terminal employed in communication system | |
EP1087294B1 (en) | Method and apparatus of remotely updating firmware of a communication device | |
US7623853B2 (en) | System and method for over the air programming | |
US5689640A (en) | Method and system for downloading data to network nodes | |
EP1931111B9 (en) | Wireless communication apparatus and wireless communication method | |
WO2009081502A1 (en) | Communication terminal | |
JP2002152821A (en) | Program update method for mobile terminal and the mobile terminal | |
EP2512100B1 (en) | Mobile communication system and mobile terminal device | |
JPH08249163A (en) | Software version control device for network system | |
JP2005100435A (en) | Communication system between onboard terminal and center, and onboard terminal to be used for communication system | |
JP2007052781A (en) | Communication system between on-vehicle terminal and center, and on-vehicle terminal used for communication system | |
JP2000293366A (en) | Method for updating module for set top box | |
EP3982254A1 (en) | Server, software update system, distribution method, and non-transitory storage medium | |
JP3475000B2 (en) | Peripheral equipment installation system, terminal processor, and central processor | |
CN111722856A (en) | Method and device for upgrading firmware in vehicle-mounted microcontroller | |
CN112954035B (en) | Server restarting method, device, equipment and storage medium | |
JP2003229974A (en) | System and method for updating software installed in portable telephone terminal | |
JPH0778111A (en) | Information processor having function for developing program through transmission medium | |
JP2022154449A (en) | OTA master, update control method, and update control program | |
JPH09146814A (en) | Data base assuarance system | |
JPH09282148A (en) | Method and system for automatically updating program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |