DE102021209058A1 - System and method for managing the update of a vehicle's electronic control unit - Google Patents

Abstract

A system and method for managing an electronic control unit (ECU) update of a vehicle is configured to provide an ECU update service for a vehicle to which over-the-air (OTA) technology is not applied, regardless of time . The system includes a first communication device that sends a vehicle ECU update guidance message to a user terminal, a second communication device that sends an update file to the vehicle when the vehicle enters a short-distance communication area, and a controller that updates the vehicle's ECU managed.

Description

CROSS REFERENCE TO A RELATED APPLICATION

This application claims the benefit of Korean Patent Application No. 10-2021-0046144 , filed with the Korean Intellectual Property Office on April 8, 2021, the entire contents of which are incorporated herein by reference.

BACKGROUND

(a) Technical Field

The present disclosure relates to a system and method for managing software updates for each electronic control unit (ECU) in a vehicle.

(b) Description of the Prior Art

Electronization of vehicle parts is an ongoing trend, and the types and number of electronic devices installed in a vehicle have increased. The electronic devices can be used in a drive control system, a body control system, a chassis control system, an in-vehicle network, a multimedia system, and the like. The powertrain control system may include an engine control system, an automatic shift control system, and the like. The body control system may include a body electronics control system, a convenience device control system, a lamp control system, and the like. The chassis control system may include a steering control system, a brake control system, a suspension control system, and the like. The vehicle network may include a Controller Area Network (CAN), a FlexRay-based network, a Media Oriented System Transport (MOST)-based network, and the like. The multimedia system may include a navigation system, a telematics system, an infotainment system, and the like.

Such systems and electronic devices constituting each of the systems are connected to each other via an in-vehicle network, and an in-vehicle network for supporting a function of each of the electronic devices is required. The Controller Area Network (CAN) can support a transmission speed of up to 1 Mbit/s and support automatic retransmission of collided frames, error detection based on a cycle redundancy check (CRC), and the like. The FlexRay-based network can support a transmission speed of up to 10 Mbit/s and support the simultaneous transmission of data over two channels, synchronous data transmission and the like. The MOST-based network, which is a high-quality multimedia communication network, can support a maximum transmission speed of 150 Mbps.

In one example, the vehicle's telematics system, infotainment system, enhanced safety system, and the like require high transmission speed, system scalability, and the like, but the CAN, FlexRay-based network, and the like are unable to fully support these requirements. The MOST-based network can support higher transmission speed than the CAN and FlexRay-based network, but it is expensive to apply the MOST-based network to all networks of the vehicle. Because of these issues, an Ethernet-based network can be considered as a vehicle network. The Ethernet-based network can support two-way communication through a pair of windings and support a maximum transmission speed of 10 Gbps.

Each of the electronic devices connected to each other via the vehicle network has an ECU, and at least one kind of software is installed in each ECU. Therefore, the number of types of software installed in each ECU in the vehicle ranges from tens to hundreds, so a method for managing updates for them is required.

In general, a driver of a vehicle that does not have over-the-air (OTA) technology (over-the-air software update) applied needs to go directly to a service center and enlist the help of an administrator (such as a service technician) to update the ECU in the vehicle. That is, a conventional scheme for updating the vehicle's ECU receives update data from a wired administrator terminal and updates the software of the ECU based on the received update data. Such a conventional system has the problem that the driver has to bring his vehicle for maintenance, and that updates are typically not performed outside of working hours (e.g. on weekends or holidays) when the administrator is not working because of the administrator's help is required.

The facts described in this background are for better understanding of the background of the invention, which may include matters other than the prior art that are already known to those skilled in the art to which this technology belongs.

SUMMARY

One aspect of the present disclosure provides a system and method for managing updating of an electronic control unit (ECU) of a vehicle, having a cloud server that manages updating of each ECU in the vehicle and an edge server that hosts is located in a predetermined zone and communicates with the cloud server, and transmits the update data of the ECU to the vehicle in a short-distance communication scheme, thereby providing an ECU update service for a vehicle to which over-the-air (OTA) technology is applied is not applied regardless of time.

The technical problems to be solved by the present inventive concept are not limited to the above problems, and any other technical problems not mentioned here will become apparent to those skilled in the art to which the present disclosure pertains be clearly understood in the following description.

According to an aspect of the present disclosure, an apparatus for managing update of an ECU of a vehicle includes a first communication device that sends an update guidance message for the ECU (Electronic Control Unit) of the vehicle to a user terminal, a second communication device that sends an update file to the vehicle, when the vehicle enters a short-distance communication area, and a controller that manages updating of the vehicle's ECU.

In one implementation, the controller can manage update history information for each user, and at least one of an updated ECU, an update date, an update time, or an update version can be recorded in the update history information.

In one implementation, the controller may notify the user terminal that there is no ECU to be updated when there is no ECU to be updated in the vehicle that has entered the short-distance communication range.

In an implementation, the controller may detect an error in a process of receiving the update file of each ECU for each vehicle model.

In one implementation, the controller may perform a rollback, reverting a software version of the ECU to a software version prior to receiving the update file, when an error occurs in the process of updating the vehicle's ECU.

In one implementation, the controller can report the presence of an error in the update file to the user terminal.

In one implementation, the controller may adjust at least a transmission period or transmission time of the guidance message based on preset conditions.

According to another aspect of the present disclosure, a method for managing update of an ECU of a vehicle includes transmitting an update guidance message for the ECU (Electronic Control Unit) of the vehicle to a user terminal through a first communication device, transmitting an update file to the vehicle through a second communication device when the vehicle enters a short-distance communication area, and managing updating of the vehicle's ECU by a controller.

In one implementation, managing updating the vehicle's ECU may include managing update history information, wherein at least one of an updated ECU, an update date, an update time, or an update version is recorded in the update history information.

In one implementation, transmitting the update file may further include notifying the user terminal that there is no ECU to be updated when there is no ECU to be updated in the vehicle that has entered the short-distance communication range.

In one implementation, managing the updating of the vehicle's ECU may include rolling back a software version of the ECU to a software version prior to the update when an error occurs in the process of updating the vehicle's ECU.

In one implementation, managing the updating of the vehicle's ECU may further include notifying the user terminal that there is an error in the update file.

In an implementation, transmitting the update file may further include adjusting at least one of a transmission period or a transmission time of the guidance message based on preset conditions.

character list

• 1 ist ein Blockdiagramm eines ECU-Aktualisierungsverwaltungsystems für ein Fahrzeug gemäß einer Ausführungsform der vorliegenden Offenbarung;
• 2 ist ein Blockdiagramm einer ECU-Aktualisierungsverwaltungsvorrichtung eines Fahrzeugs gemäß einer Ausfuhrungsform der vorliegenden Offenbarung;
• 3 ist ein Flussdiagramm eines Verfahrens zum Aktualisieren einer ECU eines Fahrzeugs gemäß einer Ausführungsform der vorliegenden Offenbarung; und
• 4 ist ein Blockdiagramm, das ein Computersystem zum Ausführen eines Verfahrens zum Aktualisieren einer ECU eines Fahrzeugs gemäß einer Ausführungsform der vorliegenden Offenbarung zeigt.

The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings:

• 1 12 is a block diagram of an ECU update management system for a vehicle according to an embodiment of the present disclosure;
• 2 12 is a block diagram of an ECU update management device of a vehicle according to an embodiment of the present disclosure;
• 3 12 is a flow chart of a method for updating an ECU of a vehicle according to an embodiment of the present disclosure; and
• 4 12 is a block diagram showing a computer system for executing a method for updating an ECU of a vehicle according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

It is understood that the term "vehicle" or other similar term as used herein includes motor vehicles in general, such as: B. Passenger cars including sport utility vehicles (SUV), buses, trucks, various commercial vehicles, watercraft including a variety of boats and ships, airplanes and the like, and hybrid vehicles, electric vehicles, plug-in hybrid electric vehicles, hydrogen-powered vehicles and other vehicles with alternative fuel (e.g. fuels derived from resources other than petroleum). A hybrid vehicle is a vehicle that has two or more sources of power, e.g. B. both gasoline-powered and electrically powered vehicles.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a” and “the” include the plural forms as well, unless the context clearly indicates otherwise. It is further understood that the terms "comprises" and/or "comprising" when used in this specification specify the presence of particular features, integers, steps, operations, elements and/or components, but not the presence or Exclude addition of one or more other characteristics, integers, steps, operations, elements, components and/or groups thereof. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. Unless expressly stated otherwise, the word "comprise" and variants such as "includes" or "comprising" shall be understood to mean the inclusion of the named elements but not the exclusion of other elements. In addition, the terms "unit", "-er", "-or" and "module" described in the specification refer to units for processing at least one function and operation and can be implemented by hardware components or software components and combinations thereof.

Furthermore, the control logic of the present disclosure may be embodied as a non-transitory computer-readable medium on a computer-readable medium containing executable program instructions that are executed by a processor, controller, or the like. Examples of computer-readable media include ROM, RAM, compact disc (CD)-ROMs, magnetic tape, floppy disks, flash drives, smart cards, and optical data storage devices. The computer-readable medium may also be distributed in network-coupled computer systems such that the computer-readable medium is stored and executed in a distributed manner, e.g. B. by a telematics server or a controller area network (CAN).

Hereinafter, some embodiments of the present disclosure will be described in detail with reference to example drawings. When adding the reference numbers to the components of each drawing, it should be noted that the identical or equivalent component is referred to with the identical number, even if they are shown on different drawings. Further, in the description of the embodiment of the present disclosure, a detailed description of the related known configuration or function will be omitted if it is found to impair the understanding of the embodiment of the present disclosure.

When describing the components of the embodiment according to the present disclosure, terms such as first, second, A, B, (a), (b), and the like may be used. These terms are used only to distinguish the components from other components, and the terms do not limit the type, order, or sequence of the components. Unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It is further understood that terms, as defined in commonly used dictionaries, should be construed to have a meaning consistent with their meaning in the context of the relevant art and not in an idealized or excessive manner be construed in the formal sense unless expressly so defined herein.

1 12 is a block diagram of an ECU update management system for a vehicle according to an embodiment of the present disclosure.

As in 1 1, a vehicle ECU update management system according to an embodiment of the present disclosure may include a cloud server 100 , an edge server 200 , a database (DB) 210 , a vehicle terminal 300 , and a user terminal 400 . In this context, the edge server 200 may also be referred to as the vehicle's ECU update management device.

Each of the components is described. First, the cloud server 100 can communicate with the edge server 200, the vehicle terminal 300, and the user terminal 400. In this regard, the cloud server 100 can transmit an update file (i.e., a software update file) of each ECU for each vehicle model to the edge server 200 located in each zone, receive user information from the user terminal 400 to register a user, and store terms of service set by the user.

The cloud server 100 may include a database (DB) storing the update file of each ECU for each vehicle model, a DB accumulating and storing real-time location information of the vehicle received from the vehicle terminal 300, and a DB storing information about various service conditions (e.g., whether to notify a new update, a new update notification time, an update type, an update cycle, an update time, an update destination, and the like) set by the user.

The cloud server 100 may recommend an update zone (or an optimal edge server) to the vehicle based on vehicle location history data.

The edge server 200, which is a server installed for each predetermined zone to perform edge computing, basically manages updating of each ECU in the vehicle. Therefore, the user needs to place the vehicle in the predetermined zone to get the ECU update.

The edge server 200 can communicate with the cloud server 100 , other edge servers, the vehicle terminal 300 and the user terminal 400 . In this connection, the edge server 200 can perform short-range communication with the vehicle terminal 300 and the user terminal 400 . In this context, short-range communication may include Bluetooth™, Radio Frequency Identification (RFID), Infrared Communication (Infrared Data Association; IrDA), Ultra Wide Band (UWB), ZigBee, Near Field Communication (NFC), Wireless Universal Serial Bus (Wireless USB) and the like. In addition, the edge server 200 can perform remote communication (mobile communication) with the vehicle terminal 300 and the user terminal 400 . For example, the edge server 200 can transmit an ECU update guidance message to the user terminal 400 via the mobile communication.

The edge server 200 may have the DB 210 that stores communication history information in which a date and time when communication with the cloud server 100 took place and a name and the like of transmitted/received data are recorded information about a vehicle model owned by each customer, update history information in which a type of updated ECU for each customer, an update date, an update time, an update version, and the like is recorded, and an update file of each ECU for each vehicle model obtained from the cloud server 100 was received. In this regard, the edge server 200 can share the update history information with other edge servers.

The edge server 200 can detect various errors (packet loss, hacking, and the like) occurring in a process of receiving the update file of each ECU for each drive vehicle model from the cloud server 100, and compare the update file of each ECU for each vehicle model stored in the cloud server 100 with the update file of each ECU for each vehicle model stored in the DB 210 to monitor whether the latest update file of each ECU for each vehicle model is stored in DB 210.

When an error occurs in the process of updating the vehicle's ECU, the edge server 200 can notify the user terminal 400 that there is an error in the update file, roll back a software version of the ECU to a software version before updating by the update file resets and update again with a normal update file.

When a new update file is received from the cloud server 100 , the edge server 200 can forward the ECU update to the user terminal 400 . In this regard, the edge server 200 can set a routing scheme based on the service condition information (e.g., whether to notify the new update, the new update notification time, the update type, the update cycle, the update time, the update destination, and the like) set by the user. determine.

The edge server 200 may notify the user terminal 400 of the location of an official A/S center when inspection by an administrator is required in connection with ECU updating of the vehicle.

The edge server 200 can determine whether there is an ECU to be updated in the vehicle based on the update history information when the vehicle enters a short-distance communication area, and notify a driver of the vehicle that there is no ECU to be updated. In this regard, the edge server 200 may notify that the vehicle's ECUs are not the update target via an electronic board or a speaker, or notify the user terminal 400 that the vehicle's ECUs are not the update target. When the ECU is to be updated, the edge server 200 can update the ECU. As such, when the update of the ECU is completed, the edge server 200 can update the update history information.

The vehicle terminal 300 can be implemented as a telematics terminal, for example, and can communicate with the edge server 200 via the short-range communication. That is, the vehicle terminal 300 can receive the update data of the ECU from the edge server 200 via the short-distance communication.

The user terminal 400 may include a mobile phone, a tablet, a wearable device, and the like, and may communicate with the edge server 200 via the short-range communication. That is, the user terminal 400 can receive various notification information, guidance information, and the like from the edge server 200 via the short-distance communication. In addition, the user terminal 400 can access the cloud server 100 or the edge server 200 to set various conditions related to the ECU update.

2 12 is a block diagram of an ECU update management device of a vehicle according to an embodiment of the present disclosure.

As in 2 As shown, an ECU update management device 200 of a vehicle according to an embodiment of the present disclosure may include a memory 10 , a mobile communication device 20 , a short-distance communication device 30 , an output device 40 , and a controller 50 . Specifically, components may be combined with each other to be implemented as one component, or some components may be omitted depending on a method for implementing the vehicle ECU update management device 200 according to an embodiment of the present disclosure.

Each of the components is described below. First, the memory 10 can store various logics, algorithms and programs involved in the process of transmitting the vehicle ECU (Electronic Control Unit) update guidance message to the user terminal 400, transmitting the update file to the vehicle when the vehicle enters the short-distance communication range, and managing the vehicle's ECU updates.

Such memory 10 may include at least one type of recording media (storage media) of a memory of a flash memory type, a hard disk type, a micro type, a card type (e.g., a secure digital card (SD card) or an eXtream digital card (XD card)) and the like, and memory of random access memory (RAM), static RAM (SRAM), read only memory (ROM), programmable ROM (PROM), electronic type erasable PROM (EEPROM), magnetic RAM (MRAM), magnetic disk and optical disk.

The mobile communication device 20 can perform the long-distance communication with the vehicle terminal 300 and the user terminal 400 .

The short-distance communication device 30 can perform the short-distance communication with the vehicle terminal 300 and the user terminal 400 . In this regard, the short-range communication device 30 may perform the short-range communication in a scheme that is at least one of the following: Bluetooth™, Radio Frequency Identification (RFID), Infrared Communication (Infrared Data Union; IrDA), Ultra Wide Band (UWB), ZigBee, Near Field Communication (NFC), Wireless Universal serial bus (wireless USB) and/or the like.

The output device 40 may include a visual output device and an audible output device, where the visual output device may include the electrical panel and the audible output device may include the speaker.

The controller 50 can perform overall control such that each of the components can normally perform a function thereof. The controller 50 can be implemented in hardware, software, or a combination of hardware and software. Preferably, the controller 50 can be implemented as a microprocessor, but is not limited to such.

Specifically, the controller 50 can perform various controls in the process of transmitting the vehicle ECU (Electronic Control Urtit) update guidance message to the user terminal 400, transmitting the update file of the ECU to the vehicle when the vehicle enters the short-distance communication area, and managing the ECU -Perform an update of the vehicle. In this connection, the controller 50 can set a transmission period and a transmission time of the guidance message based on the conditions specified by the user.

The controller 50 can manage the update history information in which the updated ECU, update date, update time, and update version are recorded for each user. That is, the controller 50 can manage the update history information in which at least one of the updated ECU, update date, update time, and/or update version is recorded for each user.

If there is no update target ECU in the vehicle that has entered the short-distance communication area, the controller 50 may notify the user terminal that there is no ECU to be updated. In this regard, the controller 50 may transmit a notification message via the mobile communication device 20 or the notification message via the short-distance communication device 30 .

The controller 50 can recognize the transmission error (the packet loss and the like) in the process of receiving the update file of each ECU for each vehicle model from the cloud server 100 .

When the error occurs in the process of updating the vehicle's ECU, the controller 50 may perform the rollback of returning the software version of the ECU to the software version before the update. That is, the controller 50 can control the ECU to perform the rollback. In this connection, the controller 50 can notify the user terminal 400 of the error in the update file through the mobile communication device 20 or the short-distance communication device 30 .

3 12 is a flow chart of a method for updating an ECU of a vehicle according to an embodiment of the present disclosure.

First, the mobile communication device 20 transmits the update guidance for the ECU (Electronic Control Unit) of the vehicle to the user terminal (301).

Thereafter, the short-distance communication device 30 transmits the update file to the vehicle when the vehicle enters the short-distance communication area (302).

Thereafter, the controller 50 manages an ECU update history of the vehicle (303). In this regard, the controller 50 can manage not only the ECU update history of the vehicle but also the ECU update data, ECU update monitor, and the like.

4 12 is a block diagram showing a computer system for executing a method for updating an ECU of a vehicle according to FIG of an embodiment of the present disclosure.

With reference to 4 For example, the above-described method for updating the vehicle's ECU according to an embodiment of the present disclosure can also be implemented with a computer system. A computer system 1000 may include at least a processor 1100, a memory 1300, a user interface input device 1400, a user interface output device 1500, a memory 1600, and a network interface 1700 connected via a system bus 1200.

Processor 1100 may be a central processing unit (CPU) or semiconductor device that performs processing of instructions stored in memory 1300 and/or memory 1600. Memory 1300 and memory 1600 may include various types of volatile or non-volatile storage media. For example, memory 1300 may include read only memory (ROM) 1310 and random access memory (RAM) 1320 .

Thus, the operations of the method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware or in a software module executed by processor 1100, or a combination thereof. The software module may reside on a storage medium (i.e., memory 1300 and/or memory 1600), such as a memory card. B. a RAM, a flash memory, a ROM, an EPROM, an EEPROM, a register, a hard disk, a solid state drive (SSD), a removable disk and a CD-ROM. The example storage medium is coupled to processor 1100, which can read and write information from and to the storage medium. In another method, the storage medium can be integrated into the processor 1100 . The processor and storage medium may reside in an application specific integrated circuit (ASIC). The ASIC can reside in the user terminal. In another approach, the processor and storage medium may reside as individual components in the user terminal.

The above description is only for illustrating the technical idea of the present disclosure, and various modifications and changes can be made by those skilled in the art without departing from the essential characteristics of the present disclosure.

Therefore, the embodiments disclosed in the present disclosure are not intended to limit the technical idea of the present disclosure but to illustrate the present disclosure, and the scope of the technical idea of the present disclosure is not limited by the embodiments. The scope of the present disclosure should be construed to be covered by the scope of the appended claims, and any technical ideas that fall within the scope of the claims should be construed to be included in the scope of the present disclosure.

The system and the method for managing the update of the ECU of the vehicle according to an embodiment of the present disclosure as described above have the cloud server that manages the update of each electronic control unit (ECU) in the vehicle and the edge server, which is located in the predetermined zone and communicates with the cloud server, and the edge server transmits the update data of the ECU to the vehicle in the short-distance communication scheme, thereby providing the ECU update service for the vehicle to which the over-the- Air (OTA) technology is not applied, regardless of the time.

Although the present disclosure has been described with reference to exemplary embodiments and the accompanying drawings, the present disclosure is not limited thereto but can be variously modified and changed by those skilled in the art to which the present disclosure pertains without departing from the spirit and scope of the present disclosure, which is claimed in the following claims.

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• KR 1020210046144 [0001]

Claims (14)

An apparatus for managing an electronic control unit (ECU) update of a vehicle, the apparatus comprising: a first communication device configured to transmit a vehicle ECU update guidance message to a user terminal; a second communication device configured to transmit an update file to the vehicle when the vehicle enters a short-distance communication range; and a controller configured to manage updating of the vehicle's ECU. The device after claim 1 wherein the controller is configured to manage update history information, wherein at least one of an updated ECU, an update date, an update time, and an update version is recorded in the update history information. The device after claim 1 wherein the controller is configured to notify the user terminal that there is no ECU to be updated when there is no ECU to be updated in the vehicle that has entered the short-distance communication area. The device after claim 1 , further comprising a DB for storing an update file for each ECU for each vehicle model received from a cloud server. The device after claim 4 , wherein the controller is configured to detect an error in a process of receiving the update file of each ECU for each vehicle model. The device after claim 1 wherein the controller is configured to roll back the rollback of a software version of the ECU to a software version before the update when an error occurs in the process of updating the vehicle's ECU. The device after claim 6 , wherein the controller is configured to notify the user terminal that there is an error in the update file. The device after claim 1 , wherein the controller is configured to adjust at least one of a transmission period and a transmission time of the guidance message based on preset conditions. A method for managing an update of an electronic control unit (ECU) of a vehicle, the method comprising: transmitting a vehicle ECU update guidance message to a user terminal through a first communication device; transmitting, by a second communication device, an update file to the vehicle when the vehicle enters a short-distance communication range; and Manage, through a controller, the updating of the vehicle's ECU. The procedure after claim 9 wherein the managing of updating the ECU of the vehicle comprises: managing update history information, wherein at least one of an updated ECU, an update date, an update time, and an update version is recorded in the update history information. The procedure after claim 9 wherein the transferring of the update file further comprises: notifying the user terminal that there is no ECU to be updated when there is no ECU to be updated in the vehicle that has entered the short-distance communication area. The procedure after claim 9 wherein managing the updating of the vehicle's ECU comprises: rolling back a software version of the ECU to a software version before the update when an error occurs in the process of updating the vehicle's ECU. The procedure after claim 12 wherein managing the updating of the vehicle's ECU further comprises: notifying the user terminal of the existence of an error in the update file. The procedure after claim 9 , wherein transmitting the update file further comprises: adjusting at least one of a transmission period and a transmission time of the guidance message based on preset conditions.

Images