WO2012001771A1 - 制御装置 - Google Patents
制御装置 Download PDFInfo
- Publication number
- WO2012001771A1 WO2012001771A1 PCT/JP2010/061057 JP2010061057W WO2012001771A1 WO 2012001771 A1 WO2012001771 A1 WO 2012001771A1 JP 2010061057 W JP2010061057 W JP 2010061057W WO 2012001771 A1 WO2012001771 A1 WO 2012001771A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- vehicle
- information
- right holder
- program
- control device
- Prior art date
Links
- 238000012423 maintenance Methods 0.000 claims description 29
- 230000008672 reprogramming Effects 0.000 abstract description 29
- 238000000034 method Methods 0.000 description 62
- 238000010586 diagram Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 4
- 238000007792 addition Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 210000000554 iris Anatomy 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 210000001525 retina Anatomy 0.000 description 2
- 210000003462 vein Anatomy 0.000 description 2
- 230000010365 information processing Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
Definitions
- This invention relates to the control apparatus which changes the control content of the control means mounted in the vehicle.
- the present invention has been made to solve the above-described problem, and an object of the present invention is to provide a control device that can promote the change of the control content and can improve the security.
- a control device is a control device that changes the control content of a control means mounted on a vehicle, and has the authority to execute the change of the control content. And a change guide setting unit for setting and outputting a notification of a change in control content to the right holder when the right holder is specified by the right holder specifying unit. And.
- a right holder having the authority to execute the change of the control content is specified based on the information related to the vehicle, and the control content change guide notification is set and output to the right holder. To do. Therefore, since it is possible to avoid changes in the control content by a person other than the right holder, security can be improved. In addition, since the right holder who can change the control content is notified of the change of the control content, the frequency of the change of the control content is increased compared to the case where the user who cannot change the control content is notified and the control content is changed. Implementation of content changes can be promoted. As described above, in the control device, it is possible to promote the change of the control content and improve the security.
- the information processing device further comprises a determination means for determining whether the vehicle is owned by an individual or a corporation based on information relating to the vehicle, and the right holder specifying means specifies the right holder according to the result determined by the determination means. It is preferable. In this case, since it is determined whether the vehicle is privately owned or corporate-owned, the right holder can be specified in accordance with each feature.
- the change guidance setting means is preferably set so as to guide the change of the control content to the manager who manages the vehicle when the right holder is specified as a legal person by the right holder specifying means. In this case, it is possible to prevent a change in control content from being notified to a person who belongs to a corporation or borrows a vehicle from the corporation. As a result, it is possible to further promote the change of the control content and improve the security.
- Information related to the vehicle body includes vehicle body number information indicating the vehicle body number, maintenance record information related to the vehicle maintenance record, parking lot information related to the contract details of the parking lot that the vehicle user has contracted, and the vehicle user
- vehicle body number information indicating the vehicle body number
- maintenance record information related to the vehicle maintenance record indicating the vehicle body number
- parking lot information related to the contract details of the parking lot that the vehicle user has contracted
- the vehicle user Preferably, it is at least one of automobile insurance information relating to the contents of the existing automobile insurance and navigation setting information relating to the contents set by the user in the navigation system mounted on the vehicle.
- the right holder can be well identified. The right holder is the owner of the vehicle.
- the control means is an electronic control device
- the right holder specifying means specifies a right holder having authority to execute a program change of the electronic control device based on information relating to the vehicle
- the change guide setting means is
- the right holder is specified by the right holder specifying means, it is preferable to set and output a notice of program change guidance for the right holder. According to such a configuration, the change (update, addition, deletion) of the program of the electronic control device can be promoted, and the security can be improved.
- FIG. 1 is a configuration diagram of a program update system including a program distribution center which is a control device according to an embodiment of the present invention.
- FIG. 2 is a diagram showing the configuration of the program distribution center.
- FIG. 3 is a flowchart showing the operation of the program distribution center.
- FIG. 4 is a flowchart showing the operation of the program distribution center.
- FIG. 5 is a flowchart showing the operation of the program distribution center.
- FIG. 6 is a flowchart showing the operation of the program distribution center.
- FIG. 7 is a sequence diagram showing a vehicle and owner specifying process.
- FIG. 8 is a sequence diagram illustrating a vehicle owner identification process when customer information cannot be acquired.
- FIG. 9 is a sequence diagram showing a right holder identification process in the personal vehicle.
- FIG. 10 is a sequence diagram illustrating a right holder identification process in a corporate vehicle.
- FIG. 1 is a configuration diagram of a program update system including a program distribution center which is a control device according to an embodiment of the present invention.
- the program update system 1 includes a program distribution center 2, a data center 3, an operator center 4, and a vehicle 5.
- the program distribution center 2, the data center 3, and the operator center 4 are connected to be communicable with each other via a network.
- the data center 3 is operated by an automobile manufacturer, for example, and is a program update (hereinafter referred to as reprogramming) that is a change in the control content of an ECU (Electronic Control Unit) that is an electronic control device (control means) of the vehicle 5 such as an automobile. Provide guidance and instructions for additions and deletions.
- the data center 3 includes an information DB (database) 30 that holds various data relating to the vehicle.
- the information DB 30 is installed in the vehicle 5, a vehicle information DB that stores vehicle information related to the vehicle 5, a maintenance record DB that stores information related to the maintenance history of the vehicle 5, a driver learning DB that stores driver learning information such as driving characteristics of the driver. It is comprised from the navigation setting information DB which stores the navigation setting information regarding the setting (home setting etc.) of the navigation system to be performed. Further, the data center 3 manages customer information specified from the driver learning information and the navigation setting information.
- the data center 3 transfers the data output from the program distribution center 2 or the operator center 4 to the vehicle 5 and transfers the data transmitted from the vehicle 5 to the program distribution center 2 or the operator center 4.
- the operator center 4 is a center where an operator is stationed and supports management and monitoring of reprogramming executed on each vehicle 5 by the operator.
- the operator center 4 has a data communication function and transmits / receives data to / from the data center 3. Therefore, data communication between the operator center 4 and the vehicle 5 is performed via the data center 3.
- the operator center 4 When the operator center 4 receives repro data (scheduled reprogram start time, processing time, vehicle stop position, etc.) transmitted from the program distribution center 2, the operator center 4 secures an operator during reprogramming based on the repro data. It is determined whether or not it can be performed, and the operator securing information is transmitted to the program distribution center 2. Here, when the operator can be secured, the operator waits before the scheduled start time. At this time, the operator center 4 connects to the reserved vehicle 5 and notifies the driver that the operator will execute reprogramming near the destination under the monitoring of the operator. When the ECU 54 of the reserved vehicle 5 is automatically connected to the operator center 4, the operator center 4 responds to the waiting operator.
- repro data scheduled reprogram start time, processing time, vehicle stop position, etc.
- the operator center 4 includes a customer information DB 40.
- the customer information DB 40 stores customer information associated with vehicle information in the vehicle information DB of the data center 3.
- the operator center 4 is connected to the contract information DB 6 and the usage information DB 7 via the network NW.
- the contract information DB 6 and the usage information DB 7 are, for example, database servers shared on the network.
- the contract information DB 6 is a database that stores information related to the participation (contract) of the car insurance that the user of the vehicle 5 subscribes, information related to the user's parking lot contract, and the like.
- the contract information DB 6 is linked with a database of an insurance company or a management company that manages a parking lot, and contract information of the user of the vehicle 5 is acquired and stored.
- the usage information DB 7 is a database (vehicle management system) that stores schedules of companies that have company vehicles and commercial vehicles, rental car companies, and the like.
- the usage information DB 7 stores a schedule input to the scheduler by a personal user's personal computer, a mobile phone of the owner who owns the vehicle, a PDA (Personal Digital Assistant), or the like.
- the program distribution center 2 is a program update device (control device) that updates and manages the program of the ECU 54 by remote control.
- the program distribution center 2 includes a vehicle information acquisition unit 21, a program management DB 22, a user information acquisition unit 23, a right holder determination unit (determination means) 24, and a right holder identification unit (right holder). (Specifying means) 25 and a repro guidance execution unit (change guidance setting means) 26.
- the program distribution center 2 has a data communication function, and transmits / receives data to / from the data center 3. Therefore, data communication between the program distribution center 2 and the vehicle 5 is performed via the data center 3.
- the program update device that is the program distribution center 2 is a server device including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication module, and the like.
- the vehicle information acquisition unit 21 is a part that acquires various information related to the vehicle 5.
- the vehicle information acquisition unit 21 needs to be updated when an update program is newly stored in the program management DB 22 that manages the program of the electronic control device by a business operator that supports each vehicle 5. Get information about the vehicle.
- the vehicle information acquisition unit 21 sends a vehicle information acquisition request for requesting acquisition of information regarding the vehicle type / year and a vehicle body number information acquisition request for requesting acquisition of information regarding the vehicle body number of the vehicle 5 to the vehicle 5.
- the vehicle information and the vehicle body number information are acquired from the vehicle 5.
- the vehicle information acquisition unit 21 also requests a navigation setting information request for requesting acquisition of navigation setting information of the navigation system 53 mounted on the vehicle 5, a navigation information acquisition request for requesting acquisition of navigation information, and biometric authentication information.
- a biometric authentication information request is transmitted to the vehicle 5, and navigation setting information, navigation information, and biometric authentication information are acquired from the vehicle 5.
- the vehicle information acquisition unit 21 outputs the acquired various types of information to the user information acquisition unit 23, the right holder determination unit 24, and the right holder identification unit 25.
- the user information acquisition unit 23 is a part that acquires information of a user who owns the vehicle 5 that needs to be updated. Upon receiving the vehicle body number information output from the vehicle information acquisition unit 21, the user information acquisition unit 23 transmits a customer information acquisition request for requesting acquisition of customer information associated with the vehicle body number information to the operator center 4. Customer information is acquired from the operator center 4. In addition, the user information acquisition unit 23, based on the body number information, maintenance requester information indicating the maintenance requester from maintenance record information (stored in the maintenance information DB of the data center 3) owned by the dealer or the maintenance factory, Other information that can identify the person is obtained.
- the user information acquisition unit 23 receives a contract information acquisition request (request for acquisition of contract information (automobile insurance subscriber information, parking lot information) associated with the maintenance requester information).
- a contract information acquisition request request for acquisition of contract information (automobile insurance subscriber information, parking lot information) associated with the maintenance requester information).
- the vehicle insurance information acquisition request and the parking lot information acquisition request) are transmitted to the contract information DB 6, and the contract information is acquired from the contract information DB 6.
- the user information acquisition unit 23 transmits a usage information acquisition request for requesting acquisition of usage information of the vehicle 5 (a usage status or a reservation status of a rental car or the like) to the usage information DB 7 and acquires the usage information from the usage information DB 7. .
- the user information acquisition part 23 transmits the luck characteristic information acquisition request which requests
- the user information acquisition unit 23 transmits a learning information acquisition request for requesting acquisition of learning information related to the history of driving characteristic information to the data center 3, and acquires learning information from the data center 3.
- the user information acquisition unit 23 outputs the acquired various information to the right holder determination unit 24 and the right holder identification unit 25.
- the right holder judgment unit 24 is a part that judges whether the vehicle 5 is privately owned or corporation-owned.
- the right holder determination unit 24 determines whether the vehicle 5 is a vehicle to be reprogrammed based on various types of information (information on the vehicle) acquired by the vehicle information acquisition unit 21 and the user information acquisition unit 23. It is determined whether the user is an individual or a corporation.
- the right holder determination unit 24 outputs determination result information indicating the determination result to the right holder specifying unit 25. Specific processing of the right holder determination unit 24 will be described later with reference to the flowcharts of FIGS.
- the right holder specifying unit 25 is a part that specifies the right holder having reprogramming authority in the vehicle 5, that is, the owner of the vehicle 5. Upon receiving the determination result information output from the right holder determination unit 24, the right holder specifying unit 25 performs a process of specifying a user having reprogramming update authority based on the determination result information, Identify.
- the right holder specifying unit 25 specifies a right holder in an individual or a corporation based on biometric authentication information, navigation information, navigation setting information, driving characteristic information, and learning information (information on the vehicle).
- the right holder specifying unit 25 outputs right holder information regarding the right holder to the repro guidance execution unit 26. Specific processing of the right holder specifying unit 25 will be described later with reference to the flowcharts of FIGS.
- the repro guidance execution unit 26 is a part that performs reprogramming guidance.
- the repro guidance execution unit 26 sets a notification of reprogramming guidance according to the right holder information, and performs the programming guidance.
- the repro guidance execution unit 26 performs repro guidance when the owner of the vehicle 5 is an individual and the right holder is specified.
- the repro guidance execution unit 26 informs the administrator and the management department that the right holder does not drive at all when the owner of the vehicle 5 is a corporation and the right holder is specified. To the driver.
- the repro guidance execution unit 26 transmits repro data relating to the set reprogramming guidance to the operator center 4 via the data center 3.
- the repro guidance execution unit 26 obtains the right holder's schedule from the scheduler at the time of repro guidance to the right holder who is an individual, and sets a time for performing reprogramming update guidance based on the schedule. it can.
- the repro guidance execution unit 26 sets a reprogramming guidance method to the user based on the user specific information. Specifically, the repro guidance execution unit 26 acquires the characteristic information of the user of the vehicle 5 from the data center 3, and based on this characteristic information (gender, age, usage status of the navigation system, reprogramming execution frequency, etc.). Set the reprogramming guidance method to the user.
- a program update guidance method there is a method in which only the reprogramming notification (the user updates the program according to the guide) or the operator of the operator center 4 directly guides the update procedure to the user.
- the vehicle 5 includes a communication unit 51, various sensors 52, a navigation system 53, and an ECU 54.
- the communication unit 51 is a part that transmits and receives data to and from the data center 3.
- the communication unit 51 receives data transmitted from the data center 3 and outputs the data to the ECU 54, and transmits data output from the ECU 54 to the data center 3.
- the sensor 52 is a part that acquires biometric authentication information, information such as a seating position, and information related to a driving state (accelerator operation, brake operation, steering wheel steering, etc.) of the driver.
- the sensor 52 acquires information relating to, for example, fingerprints, retinas, irises, veins, voices, DNA, etc. as biometric authentication information.
- the sensor 52 outputs the acquired information to the ECU 54.
- the navigation system 53 measures the absolute position of the vehicle 5 on the ground surface by GPS (Global Positioning System), compares it with map information stored separately, identifies the position of the vehicle on the map, and displays it on the display. To do. In the navigation system 53, an input from the user is received, and an operation according to the input and acquisition of information according to the operation are performed.
- the navigation system 53 is capable of data communication with the operator center 4 by the communication unit 51. Also, a voice call with the operator center 4 is possible.
- the ECU 54 is a part that supervises processing related to reprogramming.
- the ECU 54 manages an ECU to be reprogrammed (not shown), accepts a request for reprogramming, determines whether or not to perform reprogramming (determines whether or not the vehicle is stopped, etc.), notifies a reprogramming operation procedure, and sensor 52 A process of learning and transmitting the driving characteristics of the driver based on the information obtained by the above is performed.
- Driving characteristics are information related to accelerator operation, brake operation, etc.
- the accelerator operation In the case of accelerator operation, the accelerator operation after traveling for a certain period of time after the start of travel (accelerator operation from stop to start, accelerator opening timing during travel) ), And in the case of a brake operation, the data is related to the brake operation (stopping, decelerating, curving (linked to the map information of the navigation system 53)) after traveling for a certain period of time after the start of traveling. is there.
- the driving characteristics are data in which an accelerator operation and a brake operation are combined, and are vehicle speed, accelerator opening, and brake ON data after traveling for a certain period of time after starting traveling. In the ECU 54, the driving characteristics are learned for each travel, the travel start point and the travel end point are linked, and sequentially transmitted to the data center 3.
- 3 to 6 are flowcharts showing the operation of the program distribution center.
- the process is executed according to the flow of determining whether or not the vehicle is a reprogramming guidance target vehicle, identifying the vehicle, identifying the owner, identifying the guidance target person, and performing the reprogramming guidance. .
- vehicle identification owner identification processing
- vehicle information vehicle type, year
- vehicle information acquisition unit 21 step S01
- the right owner determination unit 24 determines the vehicle model to be reprogrammed based on the vehicle information (step S02), and determines whether the vehicle model is the vehicle to be guided (step S02). S03). If it is determined that the vehicle is a guidance target vehicle type, the process proceeds to step S04. On the other hand, if it is not determined that the vehicle is a guidance target vehicle type, the reprogramming guidance is stopped (step S05), and the process ends.
- step S04 vehicle number information related to the vehicle number of the vehicle 5 is acquired by the vehicle information acquisition unit 21.
- step S06 a process for collecting customer information from the customer information DB 40 of the operator center 4 based on information identifying the vehicle 5 such as a body number is performed by the user information acquisition unit 23 (step S06). And it is judged whether customer information was acquired from customer information DB40 (Step S07). If it is determined that the customer information has been acquired from the customer information DB 40, the process proceeds to step S08. On the other hand, if it is not determined that the customer information has been acquired from the customer information DB 40, the process proceeds to step S10 shown in FIG.
- step S08 it is determined whether or not the registration is an individual in the customer information. If it is determined that the registration is an individual, the process proceeds to step S20 shown in FIG. On the other hand, if it is not determined that the registration is an individual, the process proceeds to step S40 shown in FIG.
- step S10 the maintenance record information stored in the maintenance information DB of the information DB 30 of the data center 3 is referred to by the user information acquisition unit 23 (step S10). Then, based on the customer information, the right holder determination unit 24 determines whether there is maintenance record information associated with the customer information (step S11). If it is determined that there is a maintenance information record, maintenance requester information associated with the maintenance record information is acquired (step S12). On the other hand, if it is not determined that there is maintenance record information, the process proceeds to step S13.
- step S13 usage information is acquired from the contract information DB 6 by the user information acquisition unit 23. Specifically, car insurance subscriber information and parking lot information (contract information) are acquired from the contract information DB 6. Then, the right holder determination unit 24 determines whether or not the acquired various types of information match (step S14). If it is determined that the acquired various information matches, the process proceeds to step S15. On the other hand, if it is not determined that the acquired information matches, the process proceeds to step S16.
- step S15 the right holder determination unit 24 determines whether or not the registered information is an individual. If it is determined that the registered information is an individual, the process proceeds to step S20 shown in FIG. On the other hand, if the registration information is not determined to be an individual, the process proceeds to step S40 shown in FIG.
- step S16 navigation setting information (home setting, destination setting) of the navigation system 53 is acquired from the vehicle 5. Then, the owner is estimated from the acquired navigation setting information, and whether or not the vehicle is a personally owned vehicle is determined by the right holder determination unit 24 (step S17). If it is determined that the vehicle is privately owned, the process proceeds to step S20 shown in FIG. On the other hand, if it is not determined that the vehicle is privately-owned, a process when it cannot be specified is performed (step S18), and the process ends.
- step S17 navigation setting information (home setting, destination setting) of the navigation system 53 is acquired from the vehicle 5. Then, the owner is estimated from the acquired navigation setting information, and whether or not the vehicle is a personally owned vehicle is determined by the right holder determination unit 24 (step S17). If it is determined that the vehicle is privately owned, the process proceeds to step S20 shown in FIG. On the other hand, if it is not determined that the vehicle is privately-owned, a process when it cannot be specified is performed (step S18), and the process ends.
- the biometric authentication information is collected by the user information acquisition unit 23 (step S20).
- the biometric authentication information is acquired by the various sensors 52 of the vehicle 5 and is information such as fingerprints, retinas, irises, veins, voices, and DNAs.
- the right holder identification unit 25 determines whether or not biometric authentication information has been acquired (step S21). If it is determined that biometric information has been acquired, the process proceeds to step S22. On the other hand, if it is not determined that biometric authentication information has been acquired, the process proceeds to step S24.
- step S22 the acquired biometric authentication information and the registered information are collated by the right holder specifying unit 25. Then, as a result of the collation, it is determined by the right holder specifying unit 25 whether or not an individual has been specified (step S23). If it is determined that the individual has been identified, the process proceeds to step S31. On the other hand, if it is not determined that the individual has been identified, the process proceeds to step S24.
- step S24 navigation information of the navigation system 53 is collected.
- the navigation information is information regarding Bluetooth telephone registration information registered for connection with the user's mobile phone via Bluetooth (Bluetooth) and connection information with the user's mobile phone.
- the right holder identification unit 25 determines whether or not navigation information has been acquired (step S25). If it is determined that the navigation information has been acquired, the process proceeds to step S26. On the other hand, if it is determined that the navigation information has not been acquired, the process proceeds to step S28.
- step S26 the inquiry of the Bluetooth telephone registration information is performed by the right holder specifying unit 25. Specifically, based on the Bluetooth telephone registration information, a database in which mobile phone user information is registered is inquired. Then, as a result of the inquiry, it is determined by the right holder specifying unit 25 whether or not an individual has been specified (step S27). If it is determined that the individual has been identified, the process proceeds to step S31. On the other hand, if it is determined that the individual has been identified, the process proceeds to step S28.
- step S28 the right holder specifying unit 25 determines whether or not the driving specifying information has been acquired.
- the driving characteristic information is information related to the user's accelerator, brake, steering wheel operation, seat seating position, and the like. If it is determined that the driving characteristic information has been acquired, the process proceeds to step S29. On the other hand, if it is not determined that the driving characteristic information has been acquired, a process when the specification is impossible is performed (step S33), and the process ends.
- step S29 learning information is acquired from the data center 3, and collation is performed by the right holder identifying unit 25. Specifically, the driving characteristic history information stored in the learning information DB of the information DB 30 of the data center 3 is collated with the acquired driving characteristic information. If it is determined as a result of the collation that the individual has been identified, the right holder of the vehicle 5 is identified (step S31), and reprogramming guidance is performed by the repro guidance execution unit 26 (step S32). On the other hand, if it is not determined that the individual has been identified, the process proceeds to step S33, and the process ends.
- step S40 the right holder determination unit 24 determines whether or not the registration information indicates a corporation. If it is determined that the registration information indicates a corporation, the process proceeds to step S41. On the other hand, if it is not determined that the registration information indicates a corporation, the process proceeds to step S45.
- step S41 navigation information of the navigation system 53 is collected by the vehicle information acquisition unit 21.
- the navigation information is information indicating the current location of the vehicle 5 and information indicating the destination. Thereby, when the vehicle 5 is a rental car, it can be determined whether the vehicle 5 has been returned to the right holder. Then, the right holder determination unit 24 determines whether or not the right holder can be determined from the navigation information (step S42). If it is determined from the navigation information that the right holder can be determined, a corporation handling process is performed (step S46), and the process ends. The corporate correspondence processing is set to notify the driver that the reprogramming guidance to the manager of the vehicle 5 or the management department is to be communicated, and to carry out contact by letter or mail. On the other hand, if it is not determined that the right holder can be determined from the navigation information, the process proceeds to step S43.
- the usage information in the usage information DB 7 is collected by the user information acquisition unit 23 (step S43). Then, the right holder determination unit 24 determines whether or not the right holder can be determined from the usage information (step S44). If it is determined that the right holder can be determined from the usage information, a corporation handling process is performed (step S46), and the process ends. On the other hand, if it is not determined that the right holder can be determined from the navigation information, the unspecified time process is performed (step S45), and the process ends.
- FIG. 7 is a sequence diagram showing a vehicle and owner specifying process.
- a vehicle information acquisition request for requesting acquisition of vehicle information related to the vehicle type / year type is transmitted from the program distribution center 2 to the vehicle 5 (step S51).
- vehicle information is acquired and transmitted to the program distribution center 2 (step S52).
- vehicle number information acquisition information for requesting acquisition of vehicle number information relating to the vehicle number of the vehicle 5 is transmitted from the program distribution center 2 to the vehicle 5 (step S53).
- the body number information is acquired and transmitted to the program distribution center 2 (step S54).
- a customer information acquisition request for requesting acquisition of customer information associated with the vehicle body number information is transmitted from the program distribution center 2 to the operator center 4 (step S55).
- the operator center 4 that has received the customer information acquisition request transmitted from the program distribution center 2 acquires the customer information associated with the vehicle body number information from the customer information DB, and transmits this customer information to the program distribution center 2. (Step S56).
- the owner of the vehicle 5 is specified.
- FIG. 8 is a sequence diagram illustrating a vehicle owner identification process when customer information cannot be acquired.
- a maintenance record information acquisition request for requesting acquisition of maintenance record information related to the maintenance record of the vehicle 5 is transmitted from the program distribution center 2 to the data center 3 (step S61).
- the maintenance information of the vehicle 5 is acquired from the maintenance record information DB, and this maintenance information is transmitted to the program distribution center 2 (step S62). .
- a car insurance information acquisition request for requesting acquisition of car insurance information related to insurance to which the vehicle 5 joins is transmitted from the program distribution center 2 to the contract information DB 6 (step S63).
- the contract information DB 6 that has received the car insurance information acquisition request transmitted from the program distribution center 2 the car insurance information of the vehicle 5 is acquired, and this car insurance information is transmitted to the program distribution center 2 (step S64).
- requires acquisition of the parking lot information regarding the parking lot of the vehicle 5 from the program distribution center 2 is transmitted to contract information DB6 (step S65).
- the contract information DB 6 that has received the parking information acquisition request transmitted from the program distribution center 2 the vehicle 5 parking information is acquired, and this parking information is transmitted to the program distribution center 2 (step S66).
- a navigation setting information acquisition request for requesting acquisition of navigation setting information of the navigation system 53 is transmitted from the program distribution center 2 to the vehicle 5 (step S67).
- the navigation setting information is acquired, and this navigation setting information is transmitted to the program distribution center 2 (step S68).
- the owner of the vehicle 5 is specified based on the received various information.
- FIG. 9 is a sequence diagram showing a right holder identification process in the personal vehicle.
- a biometric information acquisition request for requesting acquisition of biometric information is first transmitted from the program distribution center 2 to the vehicle 5 (step S71).
- the biometric authentication information is acquired by the sensor 52, and this biometric information is transmitted to the program distribution center 2 (step S72).
- a navigation information acquisition request for requesting acquisition of navigation information is transmitted from the program distribution center 2 to the vehicle 5 (step S73).
- the navigation information of the navigation system 53 is acquired, and this navigation information is transmitted to the program distribution center 2 (step S74).
- an operation characteristic information acquisition request for requesting acquisition of operation characteristic information is transmitted from the program distribution center 2 to the data center 3 (step S75).
- the driving characteristic information of the vehicle 5 is acquired, and this driving characteristic information is transmitted to the program distribution center 2 (step S76).
- a learning information acquisition request for requesting acquisition of learning information is transmitted from the program distribution center 2 to the data center 3 (step S77).
- the learning information (history of characteristic information) of the vehicle 5 is acquired from the learning information DB, and this learning information is transmitted to the program distribution center 2.
- the program distribution center 2 identifies the right holder of the vehicle 5 based on the above-described various information, notifies the vehicle 5 of reprogramming guidance, and implements reprogramming guidance (step S79).
- FIG. 10 is a sequence diagram illustrating a right holder identification process in a corporate vehicle.
- a navigation information acquisition request for requesting acquisition of navigation information is first transmitted from the program distribution center 2 to the vehicle 5 (step S81).
- vehicle 5 In the vehicle 5 that has received the navigation information acquisition request transmitted from the program distribution center 2, navigation information is acquired from the navigation system 53, and this navigation information is transmitted to the program distribution center 2 (step S82).
- a usage information acquisition request for requesting acquisition of usage information is transmitted from the program distribution center 2 to the usage information DB 7 (step S83).
- usage information DB 7 that has received the usage information acquisition request transmitted from the program distribution center 2
- usage information (information indicating the usage status and reservation status of the rental car, etc.) is acquired, and this usage information is transmitted to the program distribution center 2.
- Step S84 In the program distribution center 2, the right holder of the vehicle 5 is specified based on the above-mentioned various information, the vehicle 5 is notified of reprogramming guidance, and reprogramming guidance is performed (step S85).
- the program distribution center 2 is a program update device for updating a program of an ECU mounted on the vehicle 5, and has the authority to execute the program update based on information related to the vehicle 5.
- the right holder is specified by the right holder specifying unit 25, and the repro guidance execution unit 26 sets and outputs a notification of program update guidance to the right holder. Accordingly, it is possible to avoid updating the program by a person other than the right holder, so that security can be improved.
- the frequency of the program update is increased compared with the case where the user who cannot perform the program update is notified and the program update is promoted. Can be made.
- the program distribution center 2 can promote program updates and improve security.
- a right holder determination unit 24 that determines whether the vehicle 5 is owned by an individual or a corporation based on information related to the vehicle, the right holder identification unit 25 is a result of determination by the right holder determination unit 24.
- the right holder is specified according to In this case, since the right holder determination unit 24 determines whether the vehicle 5 is privately owned or corporate owned (managed), the right holder can be specified in accordance with each feature.
- the repro guidance execution unit 26 sets a program update guide and notifies the manager who manages the vehicle 5. In this case, it is possible to prevent the program update from being notified to a person who belongs to the corporation or borrows a vehicle from the corporation. As a result, it is possible to further promote program updates and improve security.
- the right holder judgment unit 24 and the right holder identification unit 25 are vehicle body number information indicating the vehicle body number of the vehicle 5, maintenance record information regarding the maintenance record of the vehicle 5, and contract details of the parking lot to which the user of the vehicle 5 is contracted. Based on information relating to the vehicle body, such as parking information relating to, car insurance information relating to the contents of automobile insurance contracted by the user of the vehicle 5, and navigation setting information relating to the contents set by the user in the navigation system mounted on the vehicle 5 Thus, the right holder of the vehicle 5 is specified. Therefore, the right holder can be identified well.
- the present invention is not limited to the above embodiment.
- the program distribution center 2, the data center 3, and the operator center 4 are provided independently, but the program distribution center 2, the data center 3, and the operator center are provided. 4 may be the same center.
- the program update device may be mounted on the vehicle 5.
- the control device of the present invention is applied to reprogramming of the re-ECU.
- the control device may be applied to rewriting an FPGA (Field Programmable Gate Array) program serving as a control means.
- the FPGA is a gate array in which a logic circuit can be written, and a program in the logic circuit can be rewritten (change of control contents).
- a function is realized by reading a program from a memory.
Abstract
Description
図3に示すように、まず車両情報(車種、年式)が車両情報取得部21によって車両5から取得される(ステップS01)。車両情報が取得されると、この車両情報に基づいてリプログラムの案内対象車種の判断が権利者判断部24によって実施され(ステップS02)、案内対象車種であるか否かが判断される(ステップS03)。案内対象車種であると判断された場合には、ステップS04に進む。一方、案内対象車種であると判断されなかった場合には、リプログラミングの案内が中止され(ステップS05)、処理が終了する。
続いて、図4に示すように、データセンター3の情報DB30の整備情報DBに格納されている整備記録情報がユーザ情報取得部23によって参照される(ステップS10)。そして、顧客情報に基づいて、当該顧客情報に紐付けられた整備記録情報があるか否かが権利者判断部24によって判断される(ステップS11)。整備情報記録があると判断された場合には、整備記録情報に紐付けられた整備依頼者情報が取得される(ステップS12)。一方、整備記録情報があると判断されなかった場合には、ステップS13に進む。
次に、図5に示すように、車両5の所有者が個人であると判断された場合には、生体認証情報がユーザ情報取得部23によって収集される(ステップS20)。生体認証情報は、車両5の各種センサ52によって取得されるものであり、指紋、網膜、虹彩、静脈、音声、DNA等の情報である。そして、生体認証情報が取得されたか否かが権利者特定部25によって判断される(ステップS21)。生体認証情報が取得されたと判断された場合には、ステップS22に進む。一方、生体認証情報が取得されたと判断されなかった場合には、ステップS24に進む。
また、図6に示すように、ステップS40では、登録情報が法人を示しているか否かが権利者判断部24によって判断される。登録情報が法人を示していると判断された場合には、ステップS41に進む。一方、登録情報が法人を示していると判断されなかった場合には、ステップS45に進む。
Claims (6)
- 車両に搭載される制御手段の制御内容を変更する制御装置であって、
前記制御内容の変更を実行することについての権限を有する権利者を前記車両に係る情報に基づいて特定する権利者特定手段と、
前記権利者特定手段によって前記権利者が特定された場合に、前記権利者に対する前記制御内容の変更案内の通知を設定して出力する変更案内設定手段と、
を備えることを特徴とする制御装置。 - 前記車両が個人の所有又は法人の所有であるのかを前記車両に係る情報に基づいて判断する判断手段を更に備え、
前記権利者特定手段は、前記判断手段によって判断された結果に応じて、前記権利者を特定する請求項1記載の制御装置。 - 前記変更案内設定手段は、前記権利者が法人であると前記権利者特定手段によって特定された場合には、前記車両を管理する管理者に対して前記制御内容の変更を案内するように設定する請求項2記載の制御装置。
- 前記車体に係る情報は、前記車両の車体番号を示す車体番号情報、前記車両の整備記録に関する整備記録情報、前記車両のユーザが契約している駐車場の契約内容に関する駐車場情報、前記車両のユーザが契約している自動車保険の内容に関する自動車保険情報、前記車両に搭載されたナビゲーションシステムにおいてユーザによって設定された内容に関するナビ設定情報の少なくとも一つである請求項1~3のいずれか一項記載の制御装置。
- 前記権利者は、前記車両の所有者である請求項1~4のいずれか一項記載の制御装置。
- 前記制御手段は、電子制御装置であり、
前記権利者特定手段は、前記電子制御装置のプログラムの変更を実行することについての権限を有する権利者を前記車両に係る情報に基づいて特定し、
前記変更案内設定手段は、前記権利者特定手段によって前記権利者が特定された場合に、前記権利者に対する前記プログラムの変更案内の通知を設定して出力する請求項1~5のいずれか一項記載の制御装置。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2010/061057 WO2012001771A1 (ja) | 2010-06-29 | 2010-06-29 | 制御装置 |
US13/807,606 US9201843B2 (en) | 2010-06-29 | 2010-06-29 | Control device |
EP10854068.3A EP2590103B1 (en) | 2010-06-29 | 2010-06-29 | Control device |
CN201080067818.5A CN102959553B (zh) | 2010-06-29 | 2010-06-29 | 控制装置 |
JP2012522377A JP5418677B2 (ja) | 2010-06-29 | 2010-06-29 | 制御装置 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2010/061057 WO2012001771A1 (ja) | 2010-06-29 | 2010-06-29 | 制御装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012001771A1 true WO2012001771A1 (ja) | 2012-01-05 |
Family
ID=45401526
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/061057 WO2012001771A1 (ja) | 2010-06-29 | 2010-06-29 | 制御装置 |
Country Status (5)
Country | Link |
---|---|
US (1) | US9201843B2 (ja) |
EP (1) | EP2590103B1 (ja) |
JP (1) | JP5418677B2 (ja) |
CN (1) | CN102959553B (ja) |
WO (1) | WO2012001771A1 (ja) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014198517A (ja) * | 2013-03-29 | 2014-10-23 | 本田技研工業株式会社 | 制御仕様変更システム、制御仕様データサーバ及び仕様可変車両 |
CA2983017A1 (en) * | 2015-04-24 | 2016-10-27 | Audatex North America, Inc. | Apparatus and method for providing a digital garage |
US10255579B2 (en) * | 2016-06-09 | 2019-04-09 | Mastercard International Incorporated | System and method for incremental object tracking and progressive remittance |
DE102016213346A1 (de) * | 2016-07-21 | 2018-01-25 | Robert Bosch Gmbh | Verfahren und Vorrichtung zum Weiterverarbeiten zumindest eines Parameters einer Fahrt oder eines Ereignisses eines Fahrzeugs für ein Fahrzeug |
DE102016216983A1 (de) * | 2016-09-07 | 2018-03-08 | Robert Bosch Gmbh | Vorrichtung und Verfahren zum Aktualisieren zumindest einer in einem Fahrzeug angeordneten Sensoreinrichtung und Sensorsystem für ein Fahrzeug |
US11348385B2 (en) * | 2018-11-07 | 2022-05-31 | Hyundai Motor Company | Method and system for managing event data |
JP7218623B2 (ja) * | 2019-03-08 | 2023-02-07 | 住友電装株式会社 | 車載更新装置、更新処理システム、更新処理方法及びコンピュータプログラム |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004192278A (ja) | 2002-12-10 | 2004-07-08 | Sumitomo Electric Ind Ltd | 通信システム及び車載ゲートウェイ装置 |
JP2005141600A (ja) * | 2003-11-10 | 2005-06-02 | Nec Corp | 車両番号による情報配信システムとその方法並びにサーバ装置とそのプログラム |
JP2007065856A (ja) * | 2005-08-30 | 2007-03-15 | Fujitsu Ten Ltd | 情報書き換えシステムおよび情報書き換え装置 |
JP2008239021A (ja) * | 2007-03-28 | 2008-10-09 | Denso Corp | 車両制御装置及びそのデータ書換システム |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6275911B1 (en) * | 1996-09-20 | 2001-08-14 | Denso Corporation | Memory writing device for an electronic device |
US6657535B1 (en) * | 1998-08-31 | 2003-12-02 | Hawkeye Global, Inc. | System for signaling a device at a remote location |
WO2000070530A1 (en) * | 1999-05-19 | 2000-11-23 | I.D. Systems, Inc. | Fully automated vehicle rental system |
US6988034B1 (en) * | 2002-09-04 | 2006-01-17 | Harman International Industries, Incorporated | Navigation radio for fleet car usage |
US6882729B2 (en) * | 2002-12-12 | 2005-04-19 | Universal Electronics Inc. | System and method for limiting access to data |
JP2004196154A (ja) * | 2002-12-19 | 2004-07-15 | Sony Corp | 搭乗環境制御システム、搭乗環境制御装置、搭乗環境制御方法 |
US7401233B2 (en) * | 2003-06-24 | 2008-07-15 | International Business Machines Corporation | Method, system, and apparatus for dynamic data-driven privacy policy protection and data sharing |
WO2005060153A1 (en) * | 2003-12-15 | 2005-06-30 | Philips Intellectual Property & Standards Gmbh | Use-authorization device for security-related applications |
JP4184256B2 (ja) * | 2003-12-25 | 2008-11-19 | 本田技研工業株式会社 | 商品管理システム |
JP2006077508A (ja) * | 2004-09-10 | 2006-03-23 | Denso Corp | スマートエントリーシステム |
US8060753B2 (en) * | 2005-03-07 | 2011-11-15 | The Boeing Company | Biometric platform radio identification anti-theft system |
US9183572B2 (en) * | 2005-10-25 | 2015-11-10 | Curtis M. Brubaker | System and method for obtaining revenue through the display of hyper-relevant advertising on moving objects |
US7493211B2 (en) | 2005-12-16 | 2009-02-17 | General Electric Company | System and method for updating geo-fencing information on mobile devices |
JP4623128B2 (ja) * | 2008-04-21 | 2011-02-02 | 株式会社デンソー | 車両制御装置 |
US7864029B2 (en) * | 2008-05-19 | 2011-01-04 | Gm Global Technology Operations, Inc. | Vehicle-setting-based driver identification system |
US8665062B2 (en) * | 2008-06-30 | 2014-03-04 | Telecom Italia S.P.A. | Method and system for communicating access authorization requests based on user personal identification as well as method and system for determining access authorizations |
US20100087987A1 (en) * | 2008-10-08 | 2010-04-08 | Gm Global Technoloogy Operations, Inc. | Apparatus and Method for Vehicle Driver Recognition and Customization Using Onboard Vehicle System Settings |
JP4636171B2 (ja) * | 2008-12-17 | 2011-02-23 | トヨタ自動車株式会社 | 車両用生体認証システム |
DE102010002928B4 (de) * | 2010-03-16 | 2023-11-02 | Bayerische Motoren Werke Aktiengesellschaft | Kraftfahrzeugkonfigurationssystem |
US8841881B2 (en) * | 2010-06-02 | 2014-09-23 | Bryan Marc Failing | Energy transfer with vehicles |
JP5395036B2 (ja) * | 2010-11-12 | 2014-01-22 | 日立オートモティブシステムズ株式会社 | 車載ネットワークシステム |
-
2010
- 2010-06-29 WO PCT/JP2010/061057 patent/WO2012001771A1/ja active Application Filing
- 2010-06-29 EP EP10854068.3A patent/EP2590103B1/en active Active
- 2010-06-29 US US13/807,606 patent/US9201843B2/en active Active
- 2010-06-29 CN CN201080067818.5A patent/CN102959553B/zh active Active
- 2010-06-29 JP JP2012522377A patent/JP5418677B2/ja active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004192278A (ja) | 2002-12-10 | 2004-07-08 | Sumitomo Electric Ind Ltd | 通信システム及び車載ゲートウェイ装置 |
JP2005141600A (ja) * | 2003-11-10 | 2005-06-02 | Nec Corp | 車両番号による情報配信システムとその方法並びにサーバ装置とそのプログラム |
JP2007065856A (ja) * | 2005-08-30 | 2007-03-15 | Fujitsu Ten Ltd | 情報書き換えシステムおよび情報書き換え装置 |
JP2008239021A (ja) * | 2007-03-28 | 2008-10-09 | Denso Corp | 車両制御装置及びそのデータ書換システム |
Non-Patent Citations (1)
Title |
---|
KEIICHI YAMACHIKA: "Soko ga Shiritai Windows Server Update Services(Dai 12 Kai)", 28 January 2009 (2009-01-28) * |
Also Published As
Publication number | Publication date |
---|---|
EP2590103A1 (en) | 2013-05-08 |
CN102959553A (zh) | 2013-03-06 |
JP5418677B2 (ja) | 2014-02-19 |
JPWO2012001771A1 (ja) | 2013-08-22 |
CN102959553B (zh) | 2016-04-20 |
EP2590103A4 (en) | 2014-01-15 |
US20130103230A1 (en) | 2013-04-25 |
US9201843B2 (en) | 2015-12-01 |
EP2590103B1 (en) | 2019-07-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5418677B2 (ja) | 制御装置 | |
US20140380505A1 (en) | Access Control for Personalized User Information Maintained by a Telematics Unit | |
CN110214308A (zh) | 控制装置、程序更新方法和计算机程序 | |
US20170349139A1 (en) | Anti-theft system for driverless vehicle | |
US10919496B2 (en) | Method and apparatus for wireless valet key configuration and relay | |
CN104702589A (zh) | 用于虚拟钥匙传送的方法和设备 | |
JP6521704B2 (ja) | 遠隔操作管理方法、遠隔操作管理装置、遠隔操作システム | |
US20190228383A1 (en) | System and method of servicing a vehicle | |
JP2012014253A (ja) | 制御装置 | |
WO2019174551A1 (zh) | 移动终端的身份验证方法及装置、存储介质、电子装置 | |
US7450030B2 (en) | Method for authorisation in a telematic centre using two databases containing data characterising the motor vehicle or a mobile radio connection | |
CN110197057A (zh) | 当授权用户改变时对车辆进行保护 | |
JP2020526824A (ja) | アクセス権限および走行権限を付与する方法 | |
JP2015103058A (ja) | アプリケーション制御装置およびアプリケーション制御方法 | |
US11263848B2 (en) | Temporary and customized vehicle access | |
JP2023060005A (ja) | サーバ装置、情報処理方法、プログラム及び記憶媒体 | |
US20230106867A1 (en) | Cloud-based management of user accounts, user profiles and user devices associated with a vehicle | |
CN108416933B (zh) | 共享单车的使用方法、系统及计算机可读存储介质 | |
US11418337B2 (en) | Method of secrets injection for autonomous vehicles | |
JP2017215889A (ja) | 制御装置、プログラム更新方法、およびコンピュータプログラム | |
JP2019175184A (ja) | サーバ装置、情報通信方法、プログラム及び記憶媒体 | |
JP2019175185A (ja) | データ構造、車載端末機、情報通信方法、プログラム及び記憶媒体 | |
US11897500B2 (en) | Secure management of digital authentication information for autonomous vehicles | |
JP6867062B1 (ja) | 認証用システム、携帯端末、プログラム、及び車載器 | |
TWI524300B (zh) | 利用所在位置預約乘坐車輛之系統及其方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080067818.5 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10854068 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2012522377 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13807606 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010854068 Country of ref document: EP |