CN115051975A - ECU remote upgrading method based on vehicle-mounted Ethernet - Google Patents

ECU remote upgrading method based on vehicle-mounted Ethernet Download PDF

Info

Publication number
CN115051975A
CN115051975A CN202110219134.2A CN202110219134A CN115051975A CN 115051975 A CN115051975 A CN 115051975A CN 202110219134 A CN202110219134 A CN 202110219134A CN 115051975 A CN115051975 A CN 115051975A
Authority
CN
China
Prior art keywords
data
ecu
vehicle
tbox
upgrading
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.)
Pending
Application number
CN202110219134.2A
Other languages
Chinese (zh)
Inventor
尹磊
王滔
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
WM Smart Mobility Shanghai Co Ltd
Original Assignee
WM Smart Mobility Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by WM Smart Mobility Shanghai Co Ltd filed Critical WM Smart Mobility Shanghai Co Ltd
Priority to CN202110219134.2A priority Critical patent/CN115051975A/en
Publication of CN115051975A publication Critical patent/CN115051975A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • G06F8/654Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L2012/40208Bus networks characterized by the use of a particular bus standard
    • H04L2012/40215Controller Area Network CAN

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Small-Scale Networks (AREA)

Abstract

The invention provides an ECU remote upgrading method based on a vehicle-mounted Ethernet, which comprises the following steps: the vehicle-mounted remote terminal TBOX receives the upgrade data from the TSP; the TBOX sends the upgrading data to a central gateway through a vehicle-mounted Ethernet interface; the central gateway sends upgrading data to an ECU to be upgraded; the ECU to be upgraded executes upgrading operation after receiving the upgrading data, sends the complex data back to the central gateway after finishing the upgrading operation, and replies the data including upgrading result information; the central gateway sends the complex data back to the TBOX through the vehicle-mounted Ethernet interface; TBOX sends back the complex data to the TSP.

Description

ECU remote upgrading method based on vehicle-mounted Ethernet
Technical Field
The invention relates to the field of automotive electronics, in particular to application of a vehicle-mounted Ethernet.
Background
An ECU (electronic Control unit) electronic Control unit, also called as a driving computer or a vehicle-mounted computer, generally has more than 50 ECUs in one automobile at present, and plays different roles in different parts of the automobile. The ECUs are connected through a CAN bus, the CAN bus is equivalent to a neural network of an automobile, and any vehicle-mounted ECU CAN be controlled through the CAN bus.
With the rapid development of the computing power and hardware of the processor, the demand of ADAS, high-quality vehicle-mounted entertainment, remote diagnosis and other newly added functions, the number of the ECUs in the vehicle is continuously increased, so that the network bandwidth demand of the ECU is increased explosively, and the vehicle-mounted Ethernet is distinguished in a plurality of vehicle-mounted networks due to the unique advantages of the vehicle-mounted Ethernet.
In the prior art, the ECU can only communicate with the outside through one vehicle-mounted OBD interface. The OBD interface is a 16-pin interface which is required by modern automobiles according to international standards ISO 15031, Road vehicles, Communication between vehicles and external equipment for the requirements of the emissions, and is used for realizing the diagnosis of nodes on each path of CAN channel in a vehicle network, the collection and the test of CAN messages and the like. However, due to physical limitation and functional limitation, the OBD interface of the vehicle cannot meet the communication requirement of the ECU, and further cannot realize the real remote upgrade of the ECU, thereby greatly limiting the development of the intelligent car networking.
In order to overcome the defects in the prior art, an urgent need exists in the art for an ECU remote upgrade method based on a vehicle-mounted ethernet, which is used for introducing the vehicle-mounted ethernet into the control management of a vehicle ECU, so as to get rid of the physical limitation of an OBD interface, reduce the cost of wiring harnesses interconnected in a vehicle while meeting the bandwidth requirement, and realize the remote upgrade of the vehicle-mounted ECU.
Disclosure of Invention
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
In order to overcome the defects in the prior art, the invention provides the ECU remote upgrading method based on the vehicle-mounted Ethernet, which solves the physical limitation that the vehicle-mounted ECU can only communicate with the outside through an OBD interface in the prior art, enables the direct remote diagnosis of the vehicle to be possible, and realizes the real remote upgrading of the vehicle-mounted ECU.
One aspect of the present invention provides an ECU remote upgrade method based on a vehicle ethernet, including: the vehicle-mounted remote terminal TBOX receives the upgrade data from the TSP; the TBOX sends the upgrading data to a central gateway through a vehicle-mounted Ethernet interface; the central gateway sends upgrading data to an ECU to be upgraded; the ECU to be upgraded executes upgrading operation after receiving the upgrading data, sends the complex data to the central gateway after finishing the upgrading operation, and replies the data including upgrading result information; the central gateway sends the complex data back to the TBOX through the vehicle-mounted Ethernet interface; TBOX sends back the complex data to the TSP.
In one embodiment, preferably, the TBOX sending the upgrade data to the central gateway through the in-vehicle ethernet interface comprises: the TBOX converts the received upgrade data from a wireless protocol format into a DoIP protocol format; and then sending the upgrade data in the DoIP protocol format to the central gateway.
In one embodiment, the onboard Ethernet interface is preferably a 100BASE-T1 interface.
In one embodiment, preferably, the upgrade data includes a logical address and a flag bit of the ECU to be upgraded, the flag bit identifies a data protocol format used by the ECU to be upgraded, and the sending, by the central gateway, the upgrade data to the ECU to be upgraded includes: and the central gateway converts the protocol format of the upgrading data according to the zone bit, converts the upgrading data into a data protocol format used by the ECU to be upgraded, and then sends the upgrading data after format conversion to the ECU to be upgraded according to the logic address.
In one embodiment, optionally, the data formats recognizable by the ECU to be upgraded include a CAN protocol format and a CAN FD protocol format.
In one embodiment, preferably, the central gateway sending the complex data back to TBOX comprises: the central gateway performs protocol conversion on the reply data and converts the reply data into a DoIP protocol format; and sending the upgrade data in the DoIP protocol format to the TBOX.
In one embodiment, preferably, TBOX sending back complex data to TSP comprises: TBOX converts the received reply data into a wireless protocol format; then sending the reply data in the wireless protocol format to the TSP
Another aspect of the present invention provides a vehicle-mounted ECU network architecture based on a vehicle-mounted ethernet, including: the system comprises a TBOX, a central gateway and at least one ECU, wherein the TBOX is connected with the central gateway through a vehicle-mounted Ethernet interface, and a vehicle-mounted remote terminal TBOX receives upgrade data from a TSP; the TBOX sends the upgrading data to a central gateway through a vehicle-mounted Ethernet interface; the central gateway sends upgrading data to an ECU to be upgraded; the ECU to be upgraded executes upgrading operation after receiving the upgrading data, sends the complex data back to the central gateway after finishing the upgrading operation, and replies the data including upgrading result information; the central gateway sends the complex data back to the TBOX through the vehicle-mounted Ethernet interface; TBOX sends the complex data back to the TSP.
In one embodiment, the onboard Ethernet interface is preferably a 100BASE-TI interface.
In one embodiment, the ECU is preferably connected to the central gateway via a CAN or CAN FD bus, and the TBOX communicates with the TSP via wireless communication.
The ECU remote upgrading method based on the vehicle-mounted Ethernet is used for introducing the vehicle-mounted Ethernet into the control management of the vehicle ECU, so that the physical limitation of an OBD interface is eliminated, the weight and the cost of a wiring harness network interconnected in a vehicle are reduced while the bandwidth is increased and the data transmission rate is improved, the space is saved, the remote direct diagnosis of the vehicle becomes possible, and the remote upgrading of the vehicle ECU is realized in the true sense.
Drawings
The above features and advantages of the present disclosure will be better understood upon reading the detailed description of embodiments of the disclosure in conjunction with the following drawings. In the drawings, components are not necessarily drawn to scale, and components having similar relative characteristics or features may have the same or similar reference numerals.
FIG. 1 is a flow chart of a method for remote upgrading of an Ethernet-based ECU provided by the present invention;
FIG. 2 is a schematic diagram of a prior art ECU network architecture;
FIG. 3 is a diagram illustrating a prior art remote upgrade data communication scheme for an ECU;
FIG. 4 is a schematic diagram of an ECU network architecture according to an embodiment of an aspect of the present invention; and
FIG. 5 is a schematic diagram of a remote upgrade data communication method of an ECU according to another embodiment of the present invention.
For clarity, a brief description of the reference numerals is given below:
201 OBD interface
202 TBOX
203 central gateway
204 ECU1
205 ECU2
206 ECU3
301 TSP
Detailed Description
The following description is given by way of example of the present invention and other advantages and features of the present invention will become apparent to those skilled in the art from the following detailed description. While the invention will be described in connection with the preferred embodiments, there is no intent to limit its features to those embodiments. On the contrary, the invention is described in connection with the embodiments for the purpose of covering alternatives or modifications that may be extended based on the claims of the present invention. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. The invention may be practiced without these particulars. Moreover, some of the specific details have been left out of the description in order to avoid obscuring or obscuring the focus of the present invention.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
Additionally, the terms "upper," "lower," "left," "right," "top," "bottom," "horizontal," "vertical" and the like as used in the following description are to be understood as referring to the segment and the associated drawings in the illustrated orientation. The relative terms are used for convenience of description only and do not imply that the described apparatus should be constructed or operated in a particular orientation and therefore should not be construed as limiting the invention.
It will be understood that, although the terms first, second, third, etc. may be used herein to describe various elements, regions, layers and/or sections, these elements, regions, layers and/or sections should not be limited by these terms, but rather are used to distinguish one element, region, layer and/or section from another element, region, layer and/or section. Thus, a first component, region, layer or section discussed below could be termed a second component, region, layer or section without departing from some embodiments of the present invention.
An electronic Control unit (ecu), also called a traveling computer or a vehicle-mounted computer, is composed of a Microprocessor (MCU), a memory (ROM, RAM), an input/output interface (I/O), an analog-to-digital converter (a/D), and a large-scale integrated circuit such as a shaping circuit and a driving circuit, as in a general computer. The program stored in the ECU continuously compares and calculates the signals collected from the sensors, and then converts the calculation result into a control signal to control the work of the controlled object. The ECU is widely used in various parts of an automobile, and plays a role of a great importance.
Fig. 2 is a schematic diagram of a network architecture of an ECU in the prior art, as shown in fig. 2, each ECU (204, 205, 206) of a vehicle is connected to a central gateway 203 through a CAN or CAN FD bus, and the central gateway 203 is connected to an OBD interface 201 of the vehicle through an OBD _ CAN bus.
With the development of intelligent internet of vehicles, the application of TBOX is required to be introduced to realize the intelligent control of vehicles. The TBOX is called a vehicle-mounted intelligent terminal, and is used as a unique control unit capable of being networked on a vehicle in a vehicle network, and is used for acquiring information such as the position and the state of the vehicle and monitoring and controlling the information.
As shown in fig. 2, if each ECU of the vehicle is controlled by using TBOX, a CAN communication interface is provided on TBOX202 to connect with an OBD _ CAN interface of the vehicle, so that data communication between TBOX202 and each ECU (204, 205, 206) is realized through OBD interface 201 of the vehicle, and for example, TBOX202 is used as a diagnostic device to diagnose the existence of a fault in the ECU network of the vehicle.
Fig. 3 is a schematic diagram of a remote upgrade data communication method of an ECU in the prior art, as shown in fig. 3, in the prior art, if a certain vehicle-mounted ECU (ECU 2 in fig. 3) needs to be upgraded remotely, firstly, a TBOX202 receives upgrade data sent from a remote service provider TSP 301 in a wireless communication manner, converts the upgrade data from a wireless communication protocol format into a CAN protocol format, sends the upgrade data in the CAN protocol format to an OBD interface 201 of the vehicle through a CAN bus, sends the upgrade data in the CAN protocol format to a central gateway 203 through the OBD interface 201, the upgrade data includes a logical address of the ECU to be upgraded, and the central gateway 203 identifies the ECU needing to be upgraded as an ECU2205 according to the logical address, and then sends the upgrade data to the ECU2205 needing to be upgraded through the CAN bus.
The ECU2205 executes the upgrade operation after receiving the upgrade data, and sends the reply data after finishing the upgrade, and sequentially returns the reply data to the central gateway 203, the OBD interface 201 and the TBOX202 through the CAN bus. After receiving the reply data, TBOX202 converts the reply data in CAN protocol format into wireless communication protocol format, and sends the wireless communication protocol format to TSP 301. Thus, the remote upgrading process of the ECU is completed.
Therefore, in the prior art, as shown in fig. 3, the diagnosis of the vehicle ECU and the work of the CAN message collection test and the like are realized by the OBD interface, which means that the ECU CAN only communicate with the outside through the OBD interface in the prior art. The OBD interface is a 16-pin interface which is required by modern automobiles according to international standards ISO 15031, Road vehicles, Communication between vehicles and external equipment for the requirements of the modern automobiles, and can not meet the increasing ECU Communication requirements due to physical limitation and functional limitation, can not realize the real remote upgrade of the ECU, and limits the development of intelligent vehicle networking.
Aiming at the defects in the prior art, the invention provides an ECU remote upgrading method based on a vehicle-mounted Ethernet, which is used for introducing the vehicle-mounted Ethernet into the control management of the vehicle ECU, so that the physical limitation of an OBD interface is eliminated, the weight and the cost of a wiring harness network interconnected in a vehicle are reduced while the bandwidth is increased and the data transmission rate is improved, and the real vehicle-mounted ECU remote upgrading is realized.
Fig. 4 is a schematic diagram of an ECU network architecture according to an embodiment of an aspect of the present invention.
One aspect of the present invention provides a vehicle-mounted ECU network architecture, as shown in fig. 4, the vehicle-mounted ECU network architecture provided by the present invention includes TBOX202, central gateway 203 and at least one ECU, where TBOX and central gateway are connected through a vehicle-mounted ethernet interface, and a vehicle-mounted remote terminal TBOX receives upgrade data from TSP; the TBOX sends the upgrading data to a central gateway through a vehicle-mounted Ethernet interface; the central gateway sends upgrading data to an ECU to be upgraded; the ECU to be upgraded executes upgrading operation after receiving the upgrading data, sends the complex data back to the central gateway after finishing the upgrading operation, and replies the data including upgrading result information; the central gateway sends the complex data back to the TBOX through the vehicle-mounted Ethernet interface; TBOX sends the complex data back to the TSP. The ECU in the network architecture in the embodiment shown in fig. 4 includes an ECU 1204 and an ECU 2205. The examples are only for clearly illustrating the network architecture of the present invention, and are not intended to limit the scope of the present invention, and it should be understood that one or more ECUs may be disposed in the vehicle-mounted network according to actual needs.
TBOX202 is connected to central gateway 203 via a vehicle-mounted Ethernet interface. In this embodiment, the onboard Ethernet interface is a 100BASE-T1 interface. 100BASE-T1(IEEE 802.3bw) is a new physical layer (PHY) communication protocol developed by automotive companies in conjunction with leading Integrated Circuit (IC) manufacturers and system developers. 100BASE-T1 enables communication of audio, video, networked automobiles, firmware/software and calibration data in a vehicle using an Audio Video Bridging (AVB) set of Ethernet protocols at 100Mbps communication speed over a single pair of unshielded twisted pair cables. These aspects are important for conveying various types of information in automotive systems and enable 100BASE-T1 to carry different types of data (low and high priority versus high and low priority, time synchronization, etc.) with various priorities. By using techniques such as superposition, coding, and scrambling schemes (and some passive components) for them, 100BASE-T1 may reduce electromagnetic interference (EMI), reduce wiring weight, cost, and footprint, as compared to conventional fast ethernet (100BASE-TX) solutions.
Faster firmware/software updates and calibration speeds can be achieved using the 100BASE-T1 ethernet interface, thereby reducing downtime for vehicle updates. It is understood that the 100BASE-T1 ethernet interface is a preferred ethernet interface in the prior art for the vehicle ECU scenario, and the advantageous choice changes with the time and technology, so the 100BASE-T1 ethernet interface is only used to clearly illustrate the beneficial effects of the present invention, but not to limit the protection scope of the present invention, and the appropriate ethernet interface can be selected to connect the TBOX202 and the central gateway 203 according to the actual requirements.
Each vehicle-mounted ECU is connected to the central gateway 203 by CAN or CAN FD. CAN is an abbreviation of Controller Area Network (hereinafter CAN) and is a serial communication protocol standardized by ISO international. In the automotive industry, various electronic control systems have been developed for the purpose of safety, comfort, convenience, low power consumption, and low cost. Since the types of data used for communication between these systems and the requirements for reliability are different, the number of harnesses is increased in many cases because the systems are formed of a plurality of buses. In order to meet the demand for "reducing the number of wire harnesses" and "performing high-speed communication of a large amount of data through a plurality of LANs", the german electric company bosch company developed a CAN communication protocol for automobiles in 1986. Since then, CAN is standardized by ISO11898 and ISO11519, which are already standard protocols for automotive networks in europe. The CAN bus network has the advantages of strong data communication real-time performance among nodes, short development period and international standardization. However, with the intellectualization of automobiles, more and more data are needed to be exchanged by each controller, the frequency is higher and higher, the traditional CAN is limited by the fact that the transmission rate is 1Mbps at most (500 kbps is common at present), meanwhile, the non-information data contained in the traditional CAN is more than 50%, namely, only less than half of the data on the CAN line is really useful information, and the rest is non-data information used for protocol control, so that the CAN FD protocol of the CAN upgrading version is generated. CAN FD is an abbreviation of CAN with Flexible Data rate, inherits the main characteristics of the traditional CAN bus, simultaneously supports the Data transmission rate of up to 5Mbps, improves the false frame missing rate, and is considered as the next generation mainstream automobile bus system. In the existing automobile on the market, an ECU bus network in which CAN and CAN FD coexist is ubiquitous.
The TBOX202 and the TSP 301 transmit communication data therebetween by wireless communication, and the TBOX202 receives the data message transmitted by the TSP 301 and transmits the data to the TSP 301 by wireless. TBOX is called a vehicle-mounted intelligent terminal, and serves as the only control unit capable of being networked with a vehicle body, and plays a role in monitoring and controlling the state of the vehicle body, and the TBOX has the greatest value in the connectivity with an external network. The TBOX is mainly used to collect vehicle-related information including position information, attitude information, vehicle state information, etc., and then transmit the information to the TSP platform through wireless communication. Meanwhile, a user can use a mobile phone APP and a Web client to issue an instruction to the TBOX terminal through the TSP platform to control and operate the vehicle. Tsp (telematics Service provider) is a remote Service provider, and transmits data to TBOX in a wireless communication manner.
Different from the prior art, the vehicle-mounted ECU network architecture provided by the invention is not connected with the TBOX through an OBD physical interface of a vehicle, but through an Ethernet interface of a central gateway. When the TBOX is used as a vehicle diagnostic instrument, two OBD diagnostic channels do not need to be additionally arranged aiming at different ECUs using CAN and ECUs using CAN FD, the physical limitation of OBD interfaces is eliminated, the transmission bandwidth and the transmission rate of an ECU network are greatly increased, the harness weight and the cost of a vehicle-mounted network are reduced, and the space is saved.
Fig. 5 is a schematic diagram illustrating a remote upgrade data communication method of the ECU according to another embodiment of the present invention. Fig. 1 is a flowchart of an ethernet-based ECU remote upgrade method provided by the present invention.
Referring to fig. 5 and fig. 1, the ethernet-based ECU remote upgrade method provided by the present invention specifically includes the following steps based on the ECU network architecture provided by the present invention:
step 101: the in-vehicle remote terminal TBOX202 receives the upgrade data from TSP 301.
Step 102: TBOX202 sends the upgrade data to the central gateway through the onboard ethernet interface.
In one embodiment, TBOX202 sending the upgrade data to the central gateway over the onboard ethernet interface includes: and the TBOX converts the received upgrade data from a wireless protocol into a DoIP protocol, and then sends the upgrade data in the DoIP protocol format to the central gateway. DoIP is an abbreviation of Diagnostic communication over Internet Protocol, defined by ISO13400 series of standards, i.e. Diagnostic communication via network Protocol as the name implies. The network protocol herein refers to four-layer protocols of layer 4 to layer 1, i.e., a transport layer, a network layer, a data link layer, and a physical layer, in the OSI seven-layer model. With the DoIP protocol, faster diagnostic responses can be obtained, and the time to transfer large amounts of data for software updates and parameter downloads is shorter, making remote direct diagnostics possible. It should be noted that the DoIP protocol is only a preferred embodiment to illustrate the technical effect of the present invention, and is not used to limit the protection scope of the present invention.
In one embodiment, the onboard Ethernet interface is a 100BASE-T1 interface. The 100BASE-T1 interface is specifically developed when the ECU network architecture provided by the present invention is described above, and is not described herein again. It is understood that the interface 100BASE-T1 is only used for clearly illustrating the technical effects of the present invention, and is not used for limiting the scope of the present invention.
As shown in fig. 1, the ethernet-based ECU remote upgrade method provided by the present invention further includes:
step 103: and the central gateway sends the upgrading data to the ECU to be upgraded.
The upgrading data comprises a logical address and a zone bit of the ECU to be upgraded, the central gateway acquires whether the ECU to be upgraded adopts the CAN or CAN FD protocol according to the zone bit, then converts the upgrading data in the DoIP protocol format into a data format which CAN be identified by the ECU to be upgraded, and finally sends the upgrading data after protocol conversion to the ECU to be upgraded according to the logical address. As shown in fig. 5, in this embodiment, the central gateway 203 receives upgrade data in the DoIP protocol format sent by the TBOX202, identifies an ECU to be upgraded as the ECU2205 according to a logical address in the upgrade data, and determines that the CAN FD bus used by the ECU2205 is connected to the central gateway 203 according to a flag bit in the upgrade data, so that the central gateway 203 converts the received upgrade data in the DoIP protocol format into data in the CAN FD protocol format and sends the data to the ECU 2205.
Referring to fig. 1 again, the ethernet-based ECU remote upgrade method provided by the present invention further includes:
step 104: and the ECU to be upgraded executes upgrading operation after receiving the upgrading data, and sends the reply data to the central gateway after finishing the upgrading operation, wherein the reply data comprises information such as an upgrading result.
In the embodiment shown in fig. 5, the ECU2205 receives the upgrade data in the CAN FD protocol format transmitted by the central gateway 203, and performs the corresponding upgrade operation. After the upgrade is completed, the complex data is sent back to the central gateway 203 through the CAN FD bus. The reply data includes information such as an upgrade result.
It CAN be understood that, if the ECU to be upgraded communicates using data in the CAN protocol format, in step 103, the central gateway 203 converts the received data in the DoIP format into data in the CAN format and sends the converted data to the ECU, and after the ECU completes the upgrade operation, the reply data sent to the central gateway 203 is also in the CAN format.
The Ethernet-based ECU remote upgrading method further comprises the following steps of 105: and the central gateway sends the reply data to the TBOX through the vehicle-mounted Ethernet interface.
In the embodiment shown in fig. 5, after the reply data is sent to the central gateway 203 by the ECU2205, the reply data is converted from the CAN FD protocol format to the DoIP protocol format by the central gateway 203, and then sent to the TBOX202 through the vehicle ethernet interface 100BASE-T1, corresponding to the process of sending the upgrade data.
Finally, step 106: the TBOX sends the reply data to the TSP.
In fig. 5, TBOX202 converts the received reply data in DoIP protocol format into wireless communication protocol format, and then wirelessly transmits the converted reply data back to TSP 301. When TSP 301 finally receives the reply data from ECU2205, the upgrade of ECU2205 is completed.
While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more embodiments, occur in different orders and/or concurrently with other acts from that shown and described herein or not shown and described herein, as would be understood by one skilled in the art.
The ECU remote upgrading method based on the vehicle-mounted Ethernet is used for introducing the vehicle-mounted Ethernet into the control management of the vehicle ECU, so that the physical limitation of an OBD interface is eliminated, the weight and the cost of a wiring harness network interconnected in a vehicle are reduced while the bandwidth is increased and the data transmission rate is improved, the space is saved, the remote direct diagnosis of the vehicle becomes possible, and the remote upgrading of the vehicle ECU is realized in the true sense. A
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. An ECU remote upgrading method based on vehicle-mounted Ethernet comprises the following steps:
the vehicle-mounted remote terminal TBOX receives the upgrade data from the TSP;
the TBOX sends the upgrading data to a central gateway through a vehicle-mounted Ethernet interface;
the central gateway sends the upgrading data to an ECU to be upgraded;
the ECU to be upgraded executes upgrading operation after receiving the upgrading data, and sends back complex data to the central gateway after finishing the upgrading operation, wherein the reply data comprises upgrading result information;
the central gateway sends the reply data to the TBOX through the vehicle-mounted Ethernet interface;
the TBOX sends the reply data to the TSP.
2. The ECU remote upgrade method of claim 1, wherein the TBOX sending the upgrade data to a central gateway over a vehicle ethernet interface comprises:
the TBOX converts the received upgrade data from a wireless protocol format into a DoIP protocol format;
and then sending the upgrading data in the DoIP protocol format to the central gateway.
3. The ECU remote upgrade method of claim 2, wherein the in-vehicle ethernet interface is a 100BASE-T1 interface.
4. The ECU remote upgrade method of claim 1, wherein the upgrade data includes a logical address of the ECU to be upgraded and a flag bit identifying a data protocol format used by the ECU to be upgraded, and the sending of the upgrade data to the ECU to be upgraded by the central gateway includes:
and the central gateway performs protocol format conversion on the upgrading data according to the zone bit, converts the upgrading data into a data protocol format used by the ECU to be upgraded, and then sends the upgrading data after format conversion to the ECU to be upgraded according to the logic address.
5. The ECU remote upgrade method according to claim 4, wherein the data formats recognizable by the ECU to be upgraded include a CAN protocol format and a CAN FD protocol format.
6. The ECU remote upgrade method of claim 1, wherein the central gateway sending the reply data to the TBOX comprises:
the central gateway performs protocol conversion on the reply data to convert the reply data into a DoIP protocol format;
and sending the upgrade data in the DoIP protocol format to the TBOX.
7. The ECU remote upgrade method of claim 1, wherein the TBOX sending the reply data to the TSP comprises:
the TBOX converts the received reply data into a wireless protocol format;
and then sending the reply data in the wireless protocol format to the TSP.
8. An in-vehicle ethernet-based in-vehicle ECU network architecture comprising: TBOX, a central gateway and at least one ECU, wherein the TBOX is connected with the central gateway through a vehicle-mounted Ethernet interface,
the vehicle-mounted remote terminal TBOX receives the upgrade data from the TSP;
the TBOX sends the upgrading data to a central gateway through the vehicle-mounted Ethernet interface;
the central gateway sends the upgrading data to an ECU to be upgraded;
the ECU to be upgraded executes upgrading operation after receiving the upgrading data, and sends back complex data to the central gateway after finishing the upgrading operation, wherein the reply data comprises upgrading result information;
the central gateway sends the reply data to the TBOX through the vehicle-mounted Ethernet interface;
the TBOX sends the reply data to the TSP.
9. The in-vehicle ECU network architecture of claim 8, wherein the in-vehicle ethernet interface is a 100BASE-TI interface.
10. The in-vehicle ECU network architecture of claim 8, wherein the ECUs are connected to the central gateway via CAN or CAN FD bus, and the TBOX communicates with the TSP via wireless communication.
CN202110219134.2A 2021-02-26 2021-02-26 ECU remote upgrading method based on vehicle-mounted Ethernet Pending CN115051975A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110219134.2A CN115051975A (en) 2021-02-26 2021-02-26 ECU remote upgrading method based on vehicle-mounted Ethernet

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110219134.2A CN115051975A (en) 2021-02-26 2021-02-26 ECU remote upgrading method based on vehicle-mounted Ethernet

Publications (1)

Publication Number Publication Date
CN115051975A true CN115051975A (en) 2022-09-13

Family

ID=83156291

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110219134.2A Pending CN115051975A (en) 2021-02-26 2021-02-26 ECU remote upgrading method based on vehicle-mounted Ethernet

Country Status (1)

Country Link
CN (1) CN115051975A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116208490A (en) * 2023-03-07 2023-06-02 中国第一汽车股份有限公司 Vehicle software remote upgrading method and system, vehicle and storage medium
CN116437337A (en) * 2023-06-13 2023-07-14 江铃汽车股份有限公司 Multi-communication type OTA upgrading system and method for vehicle-mounted bus and vehicle

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180102939A1 (en) * 2016-10-07 2018-04-12 Hyundai Motor Company Software update method and apparatus for vehicle
CN108696424A (en) * 2017-04-07 2018-10-23 上汽通用汽车有限公司 Vehicle communication system
WO2019004173A1 (en) * 2017-06-26 2019-01-03 株式会社オートネットワーク技術研究所 In-vehicle communication system, in-vehicle relay device, and relay program
CN111258611A (en) * 2020-01-22 2020-06-09 重庆长安汽车股份有限公司 Method for upgrading firmware of whole vehicle in air
CN111343064A (en) * 2020-02-29 2020-06-26 东风汽车集团有限公司 System and method for upgrading software of automobile control system
CN112187744A (en) * 2020-09-14 2021-01-05 北京航空航天大学 OTA (over the air) upgrading method for vehicle-mounted domain architecture CAN (controller area network) bus DoS (DoS) attack
CN112261130A (en) * 2020-10-21 2021-01-22 宝能(广州)汽车研究院有限公司 Vehicle, OTA (over the air) upgrading system and OTA upgrading method for vehicle

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180102939A1 (en) * 2016-10-07 2018-04-12 Hyundai Motor Company Software update method and apparatus for vehicle
CN108696424A (en) * 2017-04-07 2018-10-23 上汽通用汽车有限公司 Vehicle communication system
WO2019004173A1 (en) * 2017-06-26 2019-01-03 株式会社オートネットワーク技術研究所 In-vehicle communication system, in-vehicle relay device, and relay program
CN111258611A (en) * 2020-01-22 2020-06-09 重庆长安汽车股份有限公司 Method for upgrading firmware of whole vehicle in air
CN111343064A (en) * 2020-02-29 2020-06-26 东风汽车集团有限公司 System and method for upgrading software of automobile control system
CN112187744A (en) * 2020-09-14 2021-01-05 北京航空航天大学 OTA (over the air) upgrading method for vehicle-mounted domain architecture CAN (controller area network) bus DoS (DoS) attack
CN112261130A (en) * 2020-10-21 2021-01-22 宝能(广州)汽车研究院有限公司 Vehicle, OTA (over the air) upgrading system and OTA upgrading method for vehicle

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
严娟等: "基于以太网OTA远程升级的研究", 上海汽车 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116208490A (en) * 2023-03-07 2023-06-02 中国第一汽车股份有限公司 Vehicle software remote upgrading method and system, vehicle and storage medium
CN116437337A (en) * 2023-06-13 2023-07-14 江铃汽车股份有限公司 Multi-communication type OTA upgrading system and method for vehicle-mounted bus and vehicle

Similar Documents

Publication Publication Date Title
US11146420B2 (en) Method for transmitting data via a serial communication bus, bus interface, and computer program
CN109491357B (en) Apparatus for performing diagnostic operations on a plurality of controllers and related method and vehicle
CN108303964A (en) A kind of network connector and Vehicular diagnostic method
US11475721B2 (en) Method for performing vehicle remote diagnosis and related devices
Huo et al. A survey of in-vehicle communications: Requirements, solutions and opportunities in IoT
CN115051975A (en) ECU remote upgrading method based on vehicle-mounted Ethernet
CN101947938A (en) Hybrid power CAN network communication system
CN114545906A (en) Vehicle-mounted Ethernet gateway and vehicle
CN111124443A (en) Vehicle, vehicle equipment and vehicle instrument upgrading method
CN110562275B (en) Multichannel dual-redundancy rail transit vehicle reconnection system and method
CN201659856U (en) Automobile tire detection device based on CAN bus
CN206096835U (en) Formula automobile communication system is monopolized to non -
CN112422392A (en) Whole-vehicle network system of hydrogen energy automobile
Perişoară et al. Automotive ethernet architecture for the connected dacia logan electric vehicle
CN111031515A (en) Vehicle-mounted wireless multi-system hybrid networking method
CN213094238U (en) Automobile diagnosis equipment based on DoIP diagnosis technology
KR101165854B1 (en) Self-Diagnosis System For MOST System
Manoj et al. Automotive Networks: A Review
CN212473351U (en) CAN bus arrangement structure based on electric light truck
Kurt et al. In-vehicle network for conventional and next-generation vehicles
Pheanis et al. Vehicle-Bus Interface with GMLAN for Data Collection.
CN215244706U (en) CAN bus arrangement structure based on diesel extended-range electric light truck
CN215932410U (en) Bus network architecture of working machine and working machine
CN219761329U (en) Vehicle communication system and vehicle
Kumbhare et al. Study of KWP2000, CAN, and UDS Communication Protocols for Automotive Diagnostic

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination