WO2020032122A1 - Dispositif de commande électronique, système de commande électronique de véhicule, procédé de commande d'exécution de réécriture, programme de commande d'exécution de réécriture et structure de données de spécification - Google Patents
Dispositif de commande électronique, système de commande électronique de véhicule, procédé de commande d'exécution de réécriture, programme de commande d'exécution de réécriture et structure de données de spécification Download PDFInfo
- Publication number
- WO2020032122A1 WO2020032122A1 PCT/JP2019/031177 JP2019031177W WO2020032122A1 WO 2020032122 A1 WO2020032122 A1 WO 2020032122A1 JP 2019031177 W JP2019031177 W JP 2019031177W WO 2020032122 A1 WO2020032122 A1 WO 2020032122A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- ecu
- cgw
- rewriting
- data storage
- 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.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
- B60R16/0231—Circuits relating to the driving or the functioning of the vehicle
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0644—Management of space entities, e.g. partitions, extents, pools
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/656—Updates while running
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
Definitions
- ECU Electronic Control Unit
- FIG. 128 is a diagram showing an aspect of executing rollback.
- FIG. 129 is a diagram illustrating an aspect of executing rollback.
- FIG. 130 is a diagram showing a mode of executing rollback;
- FIG. 131 is a functional block diagram of a display control unit for rewriting progress status;
- FIG. 132 is a flowchart showing a rewriting progress display control process.
- FIG. 133 is a flowchart showing a display control process of rewriting progress status;
- FIG. 134 is a diagram showing a rewriting progress screen.
- FIG. 135 is a diagram showing a rewriting progress screen.
- FIG. 136 is a diagram showing a screen of the rewriting progress status.
- FIG. 137 is a diagram showing a rewriting progress screen.
- FIG. 129 is a diagram illustrating an aspect of executing rollback.
- FIG. 130 is a diagram showing a mode of executing rollback;
- FIG. 131 is
- FIG. 224 is an overall sequence diagram showing a mode of rewriting an application program.
- FIG. 225 is an overall sequence diagram showing a mode of rewriting an application program.
- FIG. 226 is an overall sequence diagram illustrating an aspect of rewriting an application program.
- FIG. 227 is an overall sequence diagram illustrating an aspect of rewriting an application program.
- FIG. 228 is an overall sequence diagram illustrating a mode of rewriting an application program.
- FIG. 229 is an overall sequence diagram illustrating an aspect of rewriting an application program.
- FIG. 230 is an overall sequence diagram showing a mode of rewriting an application program.
- FIG. 231 is an overall sequence diagram illustrating a mode of rewriting an application program.
- FIG. 232 is an overall sequence diagram showing a mode of rewriting an application program.
- FIG. 232 is an overall sequence diagram showing a mode of rewriting an application program.
- FIG. 262 is a diagram schematically illustrating processing performed between the supplier, the center device, and the vehicle-side system in the fifth embodiment.
- FIG. 263 is a sequence diagram (part 1) illustrating a processing procedure performed between the supplier, the center device, and the vehicle-side system.
- FIG. 264 is a sequence diagram (part 2) illustrating a processing procedure performed between the supplier, the center device, and the vehicle-side system.
- FIG. 265 is a sequence diagram (part 3) illustrating a processing procedure performed between the supplier, the center device, and the vehicle-side system.
- FIG. 266 is a modification (part 1) of the first embodiment, and shows a data format of a package DB in a case where a plurality of packages correspond to one campaign.
- FIG. 1 is a sequence diagram (part 1) illustrating a processing procedure performed between the supplier, the center device, and the vehicle-side system.
- the embedded single-sided single memory has a difference engine work area, an application program area, and a boot program area.
- version information, parameter data, an application program, firmware, and a normal time vector table are arranged.
- boot program, a progress status point 2, a progress status point 1, start determination information, wireless reprog firmware, wired reprog firmware, a start determination program, and a boot time vector table are arranged. ing.
- the microcomputer 33 temporarily saves the application program as old data in the difference engine work area.
- the microcomputer 33 reads out the old data once saved in the difference engine work area, and uses the difference engine included in the replog firmware downloaded from the outside to transfer new data from the read out old data and the difference data stored in the RAM 33c. Restore.
- the microcomputer 33 When the microcomputer 33 generates new data from the old data and the difference data, the microcomputer 33 writes the new data and rewrites the application program.
- the center device 3 Upon receiving the download completion notification signal from the master device 11, the center device 3 notifies the portable terminal 6 of the completion of the download.
- the mobile terminal 6 displays a download completion notification screen (A3). The user can confirm that the download has been completed on the download completion notification screen displayed on the mobile terminal 6, and can set the rewriting start time of the application program on the vehicle side.
- the one-sided suspend memory ECU completes the writing of the write data and completes the rewriting of the application program, it ends the installation phase in the boot process and shifts from the boot process to the activation wait state. That is, the one-side suspend memory ECU does not start on the new side (side B) in which the application program has been rewritten and does not start the old side (side A) when the activation phase is not performed.
- the one-plane independent memory ECU completes the writing of the write data and completes the rewriting of the application program, it ends the installation phase in the boot process and waits for activation (t12).
- the center device 3 executes a distribution package transmission determination program to perform a distribution package transmission determination process.
- the center device 3 In the case where the center device 3 is suitable for updating a program or the like using the distribution package, a license contract has been established, the vehicle position is within a predetermined range registered in advance by the user, and the setting of the alarm function of the vehicle is not performed.
- the campaign information can be transmitted to the master device 11 when it is activated and no failure information of the ECU 19 is generated. That is, in the center device 3, the license contract has not been concluded, the vehicle position is out of a predetermined range such as a position far away from home, the alarm function setting of the vehicle has been disabled, or the ECU 19 has failed.
- the center device 3 transmits the campaign information to the master device 11 for a vehicle that may be updated against the user's intention or a vehicle that may fail to be installed even if the download is successful. You can choose not to send.
- the download possibility determination unit 67b determines whether there is a possibility that the download cannot be completed normally. Note that the determination by the download possibility determination unit 67b is performed on the condition that the “download start” button 503a is operated by the user on the download approval screen 503 shown in FIGS. 34 and 35. Further, the download possibility determination unit 67b may be configured to determine the determination item in the center device 3 as well. That is, the download possibility determination unit 67b determines that the download is possible, for example, when the setting of the alarm function of the vehicle is enabled or when no failure information of the ECU 19 is generated.
- the download execution unit 67c downloads the distribution package from the center device 3 when the download possibility determination unit 67b determines that the vehicle state is a state in which the distribution package can be downloaded. That is, the download execution unit 67c executes the download of the distribution package after confirming that the download can be normally completed.
- the DCM 12 executes a write data transfer determination program to perform a write data transfer determination process.
- a process in the case where the CGW 13 requests the DCM 12 to acquire write data in accordance with an installation instruction from the center device 3 will be described.
- the transferred write data is delivered to the rewrite target ECU 19.
- the CGW 13 determines that the data communication between the center device 3 and the DCM 12 is not a connection but is interrupted (S403). : NO), a write data acquisition request is not transmitted to the DCM 12, and the write data acquisition determination process is performed. To the end.
- the in-vehicle system 4 can notify the center device 3 of the progress of the installation, and the progress can be displayed on the mobile terminal 6 one by one. it can.
- the CGW 13 may perform the write data acquisition determination process during the acquisition of the write data. In this case, if the CGW 13 determines that the data communication is in the connected state during the acquisition of the write data, the CGW 13 continues the acquisition of the write data. Suspend data acquisition.
- the CGW 13 performs a security access key management process to extract a random value corresponding to the rewrite target ECU 19 from the analysis result of the rewrite specification data, and stores the random number in the secure area 78a.
- the decryption is performed using the decryption key corresponding to the rewriting target ECU 19 to generate the security access key.
- the data storage surface information transmission unit 80b transmits the acquired surface information as one of the ECU configuration information from the DCM 12 to the center device 3. Send.
- the data storage surface information transmitting unit 80b may transmit the ECU configuration information to the center device 3 every time the IG switch 42 is turned on or off, or may transmit the ECU configuration information to the center device 3 in response to a request from the center device 3. May be transmitted. Further, the data storage surface information transmitting unit 80b may transmit not only the two-surface memory ECU and the one-surface suspend memory ECU but also the one-side single memory ECU together with the ECU configuration including the surface information.
- map data such as, for example, map data or the like, which has the property of being updated one by one, because there is a concept of two sides and a version.
- the rollback method specifying unit 86b specifies the first rollback processing, the second rollback processing, or the third rollback processing according to the memory type and the data type.
- the rollback execution unit 86c instructs the rewrite target ECU 19 to perform rollback according to the rollback method, and operates the rewrite target ECU 19 with the old program. That is, the rollback execution unit 86c performs a rollback to return the operation state of the rewrite target ECU 19 to a state before the start of the rewriting of the application program.
- the rewrite target ECU 19 may execute the application program on the operation side (old side) before the switching, in all the processes from S1811 to S1821. Also, the rewriting target ECU 19 executes the processing from S1811 to S1819 by the application program on the operation side (old side) before switching, and restarts after performing S1819, so that the processing from S1820 to S1821 is switched. May be executed by the application program of the operation side (new side).
- the rewrite target ECU 19 starts the information notification processing when the state changes from the stop state or the sleep state to the activation state, or when, for example, the IG power is turned on or a notification request is received from the CGW 13. .
- the rewriting target ECU 19 starts the information notification process, the rewriting target ECU 19 uniquely identifies the identification information capable of uniquely identifying the application program and the parameter data relating to the operation side and the non-operation side, and the location of the operation side and the non-operation side in the memory.
- the CGW 13 is notified of possible identification information.
- the identification information may be, for example, information corresponding to a different identification ID between the wire rewrite request and the wireless rewrite request, or information corresponding to the same ID but different data for the wire rewrite request and the wireless rewrite request. There may be. That is, any information may be used as long as it is possible to distinguish between a wired rewrite request and a wireless rewrite request.
- the microcomputer 33 determines whether a wireless rewrite request has occurred (S1943), and determines whether the completion condition of the state transition management is satisfied (S1944). If the microcomputer 33 determines that a wireless rewrite request has occurred during execution of the vehicle control process (S1943: YES), the microcomputer 33 starts a rewrite exclusion process when a wireless rewrite request occurs (S1944). When the microcomputer 33 starts the rewrite exclusion process when a wireless rewrite request is generated, the microcomputer 33 determines whether or not the first state is in transition to the wired rewrite session, that is, whether or not the first state is the wired rewrite session. (S1961).
- the CGW 13 determines what percentage of the installation has been completed based on the notification from the rewrite target ECU 19.
- the CGW 13 notifies the in-vehicle display 7 and the center device 3 of progress indicating what percentage of the installation has been completed.
- the CGW 13 repeats these processes until the installation for all the rewrite target ECUs 19 is completed.
- the CGW 13 notifies the in-vehicle display 7 and the center device 3 of the progress of the completion of the installation phase.
- Display information is data constituting various screens (a campaign notification screen, an installation screen, etc.) involved in rewriting an application program.
- the display control program is a program that implements a function equivalent to a web browser.
- the property information is information that defines a display character, a display position, a color, and the like.
- the information transmitting unit 54c transmits the write data stored in the write data storage unit 54a and the display control information stored in the display control information storage unit 54b to the master device 11.
- the information transmitting unit 54c transmits the write data to the plurality of rewrite target ECUs 19 to the master device 11 as one package.
- the display control information may include phase identification information indicating in which phase the information is to be displayed. For example, the phase identification information indicates which phase of the campaign notification phase, the download phase, the installation phase, and the activate phase to display.
- the CGW 13 instructs the in-vehicle display 7 to display a screen involved in rewriting the application program using the display control information.
- the in-vehicle display 7 displays display information using display control information in accordance with an instruction from the CGW 13.
- the user may set the corresponding "on / off" buttons 513a to 513d to off. By setting it to off, the display of the content that requires the user's consent is omitted. If the user does not bother with the display of the campaign notification or the activation screen, for example, but feels that the download or the installation screen display is bothersome, the user sets the campaign notification to ON using the “ON / OFF” button 513a and turns the download “ON / OFF”.
- the button 513b may be set to off, the installation may be set to off by the "on / off” button 513c, and the activate may be set to on by the "on / off” button 513d.
- the CGW 13 determines whether or not the customization mode is set by the user's customization operation (S2405, corresponding to a customization mode determination procedure). Do).
- the CGW 13 determines that the customization mode is set (S2405: YES)
- the CGW 13 shifts to display instruction processing according to the setting content of the customization operation (S2406, corresponding to a screen display instruction procedure), and responds to the rewriting of the application program.
- the in-vehicle display 7 is instructed to perform the screen display according to the customization mode.
- a screen display transmitted and received between the CGW 13, the DCM 12, the in-vehicle display 7, the center device 3, and the meter device 45, and a message framework related to user operations will be described.
- the CGW 13 and the DCM 12 are connected by CAN or Ethernet, and the DCM 12 and the in-vehicle display 7 are connected by USB.
- the CGW 13 performs data communication with the in-vehicle display 7 via the DCM 12.
- the data transmitted by the diagnostic communication from the CGW 13 is subjected to protocol conversion by the DCM 12 and received by the in-vehicle display 7 from the DCM 12 by USB communication.
- Data transmitted from the in-vehicle display 7 by USB communication is subjected to protocol conversion by the DCM 12 and received by the CGW 13 from the DCM 12 by diagnostic communication.
- the CGW 13 acquires information on a user operation on the in-vehicle display 7 via the DCM 12.
- the DCM 12 is provided with a protocol conversion function, and the portable terminal 6 and the in-vehicle display 7 can be handled by the CGW 13 similarly.
- the CGW 13 can arbitrate the results of user operations on a plurality of operation terminals and manage the current progress.
- the process from accepting the download to the ECU 19 of the one-sided suspend memory to the execution of the installation is performed, and the meter device 45 turns on the indicator 46 during this period.
- the CGW 13 finishes the phase during the execution of the installation on the ECU 19 of the one-side suspend memory the CGW 13 performs the process from accepting the download to the ECU 19 of the one-side single memory to accepting the installation, and the meter device 45 turns on the indicator 46 during this period.
- the ECU 19 includes an instruction determination unit 108a, a first power supply self-holding enabling unit 108b, a first stop condition satisfaction determination unit 108c, and a first power supply And a self-holding stop 108d.
- the instruction determination unit 108a determines whether the CGW 13 has issued an instruction to activate the first power supply self-holding circuit.
- the CGW 13 determines whether or not the vehicle power supply is off (S2601, corresponding to a vehicle power supply determination procedure).
- the CGW 13 determines whether the application program is being rewritten (S2602, corresponding to a rewriting determination procedure).
- the CGW 13 activates the second power supply self-holding circuit (S2603, corresponding to the second power supply self-holding activation procedure), and turns on the power supply in the rewriting target ECU 19.
- the necessity of self-holding is determined (S2604, corresponding to a power self-holding determination procedure).
- the CGW 14 delays the frequency of transmitting write data to the ECU (ID1).
- the monitoring is terminated when the installation to all the rewrite target ECUs 19 is completed. In the case of a single-sided memory, it is not possible to end the installation in the middle of the installation, so it is necessary to confirm that there is a sufficient remaining battery level before the start of the installation.
- the CGW 13 upon receiving the activation completion notification from the ECU (ID1), the ECU (ID2), and the ECU (ID3), the CGW 13 notifies the in-vehicle display 7 that the program update has been completed as a progress status (S5415).
- the in-vehicle display 7 displays that the program update has been completed (S5416).
- the CGW 13 does not notify the in-vehicle display 7 of the progress.
- the CGW 13 requests the power management ECU 20 to turn off the IG power (S5418).
- the power management ECU 20 requests the power control circuit 43 to cut off the power supply to return to the power state in which the IG switch is turned off before the start of the installation.
- the ECU (ID1), the ECU (ID2), the ECU (ID4), the ECU (ID5), and the ECU (ID6) And becomes a stop state.
- a second bus 15 In addition to the first bus 14, a second bus 15, a third bus 16, a fourth bus 17, and a fifth bus 18 are connected to the CGW 13 as buses inside the vehicle. Are connected, and a power management ECU 20 is connected via a bus 18.
- the DCM 12, the CGW 13, and the ECU 19 have a power supply self-holding function. That is, when the vehicle power is switched from the ACC power supply or the IG power supply to the + B power supply in the activated state, the DCM 12, the CGW 13, and the ECU 19 shift from the activated state to the sleep state or the stopped state immediately after the switching. Instead, even immediately after the switching, the driving state is maintained for a predetermined period of time and the driving power source is held by itself.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Mechanical Engineering (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Automation & Control Theory (AREA)
- Stored Programmes (AREA)
Abstract
Ce dispositif de commande électronique (19) comprend: une unité d'exécution d'installation (104f) pour générer l'exécution des données de paramètre et/ou d'un programme d'application qui est stocké sur un premier côté de stockage de données, qui est un côté d'exploitation, et pour écrire des données de mise à jour acquises d'un dispositif externe dans un second côté de stockage de données, qui est un côté sans exploitation, réécrivant ainsi le second côté de stockage de données; et une unité d'exécution d'activation (104g) pour passer du côté d'exploitation du premier côté de stockage de données au second côté de stockage de données. L'unité d'exécution d'installation réécrit le second côté de stockage de données pendant qu'un véhicule peut se déplacer ou est stationné. L'unité d'exécution d'activation commute le côté d'exploitation du premier côté de stockage de données au second côté de stockage de données pendant que le véhicule est stationné.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| DE112019004061.8T DE112019004061T5 (de) | 2018-08-10 | 2019-08-07 | Elektronische Steuerungseinheit, elektronisches Fahrzeugsteuerungssystem, Neuschreibausführungsverfahren, Neuschreibausführungsprogramm und Datenstrukturspezifikationsdaten |
| CN201980056027.3A CN112602057B (zh) | 2018-08-10 | 2019-08-07 | 电子控制装置及系统、改写的执行控制方法、记录介质 |
| US17/167,373 US11822366B2 (en) | 2018-08-10 | 2021-02-04 | Electronic control unit, vehicle electronic control system, rewrite execution method, rewrite execution program, and data structure of specification data |
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2018-151429 | 2018-08-10 | ||
| JP2018151429 | 2018-08-10 | ||
| JP2019129970A JP7484096B2 (ja) | 2018-08-10 | 2019-07-12 | 電子制御装置、書換えの実行制御方法及び書換えの実行制御プログラム |
| JP2019-129970 | 2019-07-12 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US17/167,373 Continuation US11822366B2 (en) | 2018-08-10 | 2021-02-04 | Electronic control unit, vehicle electronic control system, rewrite execution method, rewrite execution program, and data structure of specification data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2020032122A1 true WO2020032122A1 (fr) | 2020-02-13 |
Family
ID=69414709
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/JP2019/031177 Ceased WO2020032122A1 (fr) | 2018-08-10 | 2019-08-07 | Dispositif de commande électronique, système de commande électronique de véhicule, procédé de commande d'exécution de réécriture, programme de commande d'exécution de réécriture et structure de données de spécification |
Country Status (2)
| Country | Link |
|---|---|
| JP (1) | JP7383967B2 (fr) |
| WO (1) | WO2020032122A1 (fr) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20220004375A1 (en) * | 2020-07-02 | 2022-01-06 | Toyota Jidosha Kabushiki Kaisha | Software update device, software update method, non-transitory storage medium, and vehicle |
| JPWO2022069914A1 (fr) * | 2020-09-29 | 2022-04-07 | ||
| US20220342660A1 (en) * | 2021-04-23 | 2022-10-27 | Denso Corporation | Center device and in-vehicle electronic control device |
| CN116946043A (zh) * | 2023-06-02 | 2023-10-27 | 上海理想汽车科技有限公司 | 车辆电源模块重置方法、相关设备及车辆 |
Families Citing this family (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP7490518B2 (ja) | 2020-09-29 | 2024-05-27 | 本田技研工業株式会社 | 制御システム、移動体、プログラム、及び制御方法 |
| JP7204726B2 (ja) | 2020-12-22 | 2023-01-16 | 本田技研工業株式会社 | 制御システム、移動体、サーバ、制御方法、更新制御方法、及びプログラム |
| JP7284143B2 (ja) | 2020-12-25 | 2023-05-30 | 本田技研工業株式会社 | 制御システム、移動体、制御方法及びプログラム |
| JP7194761B2 (ja) | 2021-01-13 | 2022-12-22 | 本田技研工業株式会社 | 制御システム、移動体、制御方法、及びプログラム |
| JP7194760B2 (ja) | 2021-01-13 | 2022-12-22 | 本田技研工業株式会社 | 制御システム、移動体、制御方法及びプログラム |
| JP7307755B2 (ja) | 2021-01-14 | 2023-07-12 | 本田技研工業株式会社 | 制御システム、移動体、サーバ、制御方法、及びプログラム |
| JP7333350B2 (ja) * | 2021-01-14 | 2023-08-24 | 本田技研工業株式会社 | 制御システム、移動体、制御方法及びプログラム |
| JP7257428B2 (ja) | 2021-01-14 | 2023-04-13 | 本田技研工業株式会社 | 情報処理装置、制御システム、システム、情報処理方法、制御方法、及びプログラム |
| JP7291734B2 (ja) | 2021-01-14 | 2023-06-15 | 本田技研工業株式会社 | 制御システム、移動体、情報処理装置、制御方法、情報処理方法及びプログラム |
| JP7250056B2 (ja) | 2021-03-09 | 2023-03-31 | 本田技研工業株式会社 | 制御システム、移動体及び通信制御方法 |
| JP7217767B2 (ja) | 2021-03-19 | 2023-02-03 | 本田技研工業株式会社 | 更新管理サーバ、更新管理方法、及びプログラム |
| JP7320547B2 (ja) | 2021-03-19 | 2023-08-03 | 本田技研工業株式会社 | プログラム更新制御装置、プログラム更新制御方法、及びプログラム |
| JP7289867B2 (ja) | 2021-03-30 | 2023-06-12 | 本田技研工業株式会社 | 更新制御装置、移動体、更新制御方法、及びプログラム |
| JP7683350B2 (ja) * | 2021-06-29 | 2025-05-27 | 株式会社デンソー | 車載通信システム,センタ装置,車両側システム及び車載通信の更新データ検証方法 |
| JP7707884B2 (ja) * | 2021-12-13 | 2025-07-15 | トヨタ自動車株式会社 | 制御装置、管理方法 |
| JP7501545B2 (ja) | 2022-01-11 | 2024-06-18 | トヨタ自動車株式会社 | 制御システム、および、制御システムの制御方法 |
| JP7633215B2 (ja) * | 2022-02-15 | 2025-02-19 | 本田技研工業株式会社 | プログラム管理装置、プログラム管理方法、及び、記録媒体 |
| US12461737B2 (en) | 2022-02-15 | 2025-11-04 | Honda Motor Co., Ltd. | Program management device, program management method, and recording medium |
| JP2024141658A (ja) * | 2023-03-29 | 2024-10-10 | 株式会社デンソー | 更新情報通知装置、車両システム及び更新情報通知プログラム |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4548601B2 (ja) * | 2005-04-20 | 2010-09-22 | 株式会社デンソー | 自動車用制御ユニット |
| JP2018065410A (ja) * | 2016-10-17 | 2018-04-26 | トヨタ自動車株式会社 | ソフトウエア更新制御装置 |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4248624B2 (ja) * | 1998-07-03 | 2009-04-02 | 株式会社デンソー | 内燃機関用電子制御装置。 |
| JP2006331185A (ja) * | 2005-05-27 | 2006-12-07 | Fujitsu Ten Ltd | 制御装置、書換装置、書換方法および書換プログラム |
| JP5658200B2 (ja) * | 2012-06-19 | 2015-01-21 | Necプラットフォームズ株式会社 | 通信装置および起動プログラムコード選択方法 |
| JP6358286B2 (ja) * | 2016-06-02 | 2018-07-18 | 住友電気工業株式会社 | 制御装置、プログラム更新方法、およびコンピュータプログラム |
| JP6390644B2 (ja) * | 2016-03-02 | 2018-09-19 | 住友電気工業株式会社 | プログラム更新システム、プログラム更新方法及びコンピュータプログラム |
| JP6519708B2 (ja) * | 2016-10-27 | 2019-05-29 | 住友電気工業株式会社 | 制御装置、プログラム更新方法、およびコンピュータプログラム |
| JP6334776B1 (ja) * | 2017-04-20 | 2018-05-30 | 三菱電機株式会社 | 電子制御装置 |
-
2019
- 2019-08-07 WO PCT/JP2019/031177 patent/WO2020032122A1/fr not_active Ceased
- 2019-10-10 JP JP2019186886A patent/JP7383967B2/ja active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4548601B2 (ja) * | 2005-04-20 | 2010-09-22 | 株式会社デンソー | 自動車用制御ユニット |
| JP2018065410A (ja) * | 2016-10-17 | 2018-04-26 | トヨタ自動車株式会社 | ソフトウエア更新制御装置 |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20220004375A1 (en) * | 2020-07-02 | 2022-01-06 | Toyota Jidosha Kabushiki Kaisha | Software update device, software update method, non-transitory storage medium, and vehicle |
| JPWO2022069914A1 (fr) * | 2020-09-29 | 2022-04-07 | ||
| WO2022069914A1 (fr) | 2020-09-29 | 2022-04-07 | 日産自動車株式会社 | Système de commande électronique de véhicule et procédé permettant de mettre à jour un programme utilisé dans celui-ci |
| CN116113924A (zh) * | 2020-09-29 | 2023-05-12 | 日产自动车株式会社 | 车辆用电子控制系统和用于该系统的程序的更新方法 |
| EP4224313A4 (fr) * | 2020-09-29 | 2023-11-15 | Nissan Motor Co., Ltd. | Système de commande électronique de véhicule et procédé permettant de mettre à jour un programme utilisé dans celui-ci |
| JP7500749B2 (ja) | 2020-09-29 | 2024-06-17 | 日産自動車株式会社 | 車両用電子制御システム及びこれに用いるプログラムの更新方法 |
| JP2024110987A (ja) * | 2020-09-29 | 2024-08-16 | 日産自動車株式会社 | 車両用電子制御システム及びこれに用いるプログラムの更新方法 |
| US12223310B2 (en) | 2020-09-29 | 2025-02-11 | Nissan Motor Co., Ltd. | Vehicle electronic control system, and method for updating program used therein |
| JP7683088B2 (ja) | 2020-09-29 | 2025-05-26 | 日産自動車株式会社 | 車両用電子制御システム及びこれに用いるプログラムの更新方法 |
| US20220342660A1 (en) * | 2021-04-23 | 2022-10-27 | Denso Corporation | Center device and in-vehicle electronic control device |
| US11989550B2 (en) * | 2021-04-23 | 2024-05-21 | Denso Corporation | Center device and in-vehicle electronic control device |
| CN116946043A (zh) * | 2023-06-02 | 2023-10-27 | 上海理想汽车科技有限公司 | 车辆电源模块重置方法、相关设备及车辆 |
Also Published As
| Publication number | Publication date |
|---|---|
| JP7383967B2 (ja) | 2023-11-21 |
| JP2020027666A (ja) | 2020-02-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020032196A1 (fr) | Système de communication d'informations de véhicule | |
| WO2020032200A1 (fr) | Dispositif central, procédé de génération de données de spécifications et programme de génération de données de spécifications | |
| JP2020027627A (ja) | 車両用電子制御システム、車両用マスタ装置、データ格納面情報の送信制御方法及びデータ格納面情報の送信制御プログラム | |
| JP2020027631A (ja) | 車両用プログラム書換えシステム、車両用マスタ装置、進捗状態の同期制御方法及び進捗状態の同期制御プログラム | |
| JP2020027640A (ja) | 電子制御装置、書換えの実行制御方法及び書換えの実行制御プログラム | |
| WO2020032122A1 (fr) | Dispositif de commande électronique, système de commande électronique de véhicule, procédé de commande d'exécution de réécriture, programme de commande d'exécution de réécriture et structure de données de spécification | |
| JP2020028121A (ja) | 車両用マスタ装置、更新データの配信制御方法、更新データの配信制御プログラム及び諸元データのデータ構造 | |
| JP2020027636A (ja) | 車両用マスタ装置、更新データの検証方法及び更新データの検証プログラム | |
| JP2020027628A (ja) | 車両用電子制御システム、配信パッケージのダウンロード判定方法及び配信パッケージのダウンロード判定プログラム | |
| JP2020027630A (ja) | 車両用マスタ装置、ロールバックの実行制御方法、ロールバックの実行制御プログラム及び諸元データのデータ構造 | |
| JP2020027638A (ja) | 車両用マスタ装置、車両用電子制御システム、アクティベート要求の指示方法及びアクティベート要求の指示プログラム | |
| JP2020027629A (ja) | 車両用マスタ装置、インストールの指示判定方法及びインストールの指示判定プログラム | |
| WO2020032046A1 (fr) | Système de commande électronique de véhicule, procédé de commande de transfert de fichier, programme de commande de transfert de fichier, et structure de données de données de spécification | |
| JP2020027634A (ja) | 電子制御装置、車両用電子制御システム、差分データの整合性判定方法及び差分データの整合性判定プログラム | |
| JP2020027635A (ja) | 電子制御装置、リトライポイントの特定方法及びリトライポイントの特定プログラム | |
| JP2020027633A (ja) | 車両用マスタ装置、書換え対象のグループ管理方法、書換え対象のグループ管理プログラム及び諸元データのデータ構造 | |
| JP2020027637A (ja) | 車両用マスタ装置、非書換え対象の電源管理方法及び非書換え対象の電源管理プログラム | |
| WO2020032195A1 (fr) | Système de communication d'informations de véhicule | |
| WO2020032043A1 (fr) | Système de commande électronique de véhicule, procédé de détermination de téléchargement d'un progiciel de distribution et programme de détermination de téléchargement d'un progiciel de distribution | |
| JP2020027632A (ja) | 電子制御装置、車両用電子制御システム、アクティベートの実行制御方法及びアクティベートの実行制御プログラム | |
| WO2020032121A1 (fr) | Dispositif maître de véhicule, procédé de vérification de données de mise à jour et programme de vérification de données de mise à jour | |
| WO2020032199A1 (fr) | Système de communication d'informations de véhicule | |
| JP2020027641A (ja) | 車両用電子制御システム、センター装置、車両用マスタ装置、表示制御情報の送信制御方法、表示制御情報の受信制御方法、表示制御情報の送信制御プログラム及び表示制御情報の受信制御プログラム | |
| JP2020027665A (ja) | 車両用電子制御システム | |
| WO2020032044A1 (fr) | Dispositif maître de véhicule, procédé de détermination d'instruction d'installation, et programme de détermination d'instruction d'installation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19848026 Country of ref document: EP Kind code of ref document: A1 |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 19848026 Country of ref document: EP Kind code of ref document: A1 |