DIAGNOSTIC PROCEDURES AND INTERNAL DIAGNOSTIC DEVICE IN A VEHICLE NETWORK

Abstract

Diagnostic procedure which is carried out by a gateway (600) in a vehicle network which has at least the gateway (600) and an internal diagnostic device as a plurality of communication nodes, comprising the diagnostic procedure: Sending (S703; S803), through the gateway (600), a diagnostic initiation message indicating that a diagnostic operation of an external diagnostic device (640) is to be carried out, in a broadcast manner upon detection that the external diagnostic device (640) is connected to the gateway (600), Received by the gateway (600), a negative response message (S707) as a response to the diagnostic initiation message from the internal diagnostic device, and Performing, through the gateway (600), the diagnostic procedure of the external diagnostic device (640) at a target endpoint that differs from a target endpoint specified in the negative response message, wherein the negative response message indicates that a diagnostic operation of the internal diagnostic device cannot be stopped, and the diagnostic initiation message contains at least one identifier of at least one communication node for which the diagnostic operation of the external diagnostic device (640) is to be performed, from the majority of communication nodes, and information indicating a start time of the diagnostic operation of the external diagnostic device (640).

Description

Technical field

[0001] The present invention relates to diagnostic methods and an internal diagnostic device in a vehicle network, wherein the present invention relates to a vehicle network technology and in particular a method and a device for preventing diagnostic errors due to a collision / conflict between a diagnostic operation of an external diagnostic device and a diagnostic operation of an internal diagnostic device in a vehicle network. background

[0002] The number and variety of electronic devices installed in vehicles have increased significantly with the recent digitization of vehicle components. Generally, electronic devices can be used throughout the vehicle, such as in a powertrain control system (e.g., an engine control system, an automatic transmission control system, or similar), a body control system (e.g., a body electronics control system, a comfort device control system, a lighting control system, or similar), a chassis control system (e.g., a steering device control system, a brake control system, a suspension control system, or similar), a vehicle network (e.g.,a control unit network (abbreviated: CAN; English "Controller Area Network" - also "control device area network"), a FlexRay-based network, a MOST-based network (MOST = "Media Oriented Systems Transport") or the like), a multimedia system (e.g. a navigation device system, a telematics system, an infotainment system or the like) and so on.

[0003] The electronic devices used in each of these systems are connected via a vehicle network that supports the functions of the electronic devices. For example, CAN can support a transmission rate of up to 1 Mbps (megabits per second) and automatic retransmission of conflicting messages, error detection based on a Cyclic Redundancy Control (CRC) interface, and similar features. The FlexRay-based network can support a transmission rate of up to 10 Mbps and can support simultaneous data transmission through two channels, synchronous data transmission, and similar features. The MOST-based network is a communication network for high-quality multimedia that supports a transmission rate of up to 150 Mbps.

[0004] The telematics and infotainment systems, like most advanced vehicle safety systems, require higher data rates and system expandability. CAN, FlexRay-based networks, and similar technologies cannot adequately support these requirements. MOST-based networks, in particular, can support higher data rates than CAN or FlexRay-based networks. However, implementing MOST-based networks in vehicle networks can be costly. Because of these limitations, Ethernet-based networks are frequently used as vehicle networks. Ethernet-based networks can support bidirectional communication over a single pair of turns (e.g., twisted-pair cables) and can support data rates of up to 10 Gbps (gigabits per second).

[0005] The vehicle network described above can have multiple communication nodes (e.g., electronic devices), and diagnostic procedures for these nodes can be performed by either an external or an internal diagnostic device. If a diagnostic procedure is performed simultaneously by both the external and internal diagnostic devices for a target communication node in the vehicle network, a collision / conflict between the two procedures can occur. In such a case, accurate diagnostic results cannot be obtained.

[0006] DE 11 2013 004 941 T5 discloses a gateway device comprising a request receiving section, an output section, a response receiving section, a transmission section, and an arbitration section. The request receiving section receives diagnostic requests from diagnostic tools for performing a malfunction diagnosis of an ECU located in a vehicle. The output section sends the diagnostic request to a vehicle-specific LAN to which the ECU is connected. The response receiving section receives a diagnostic response, which is sent by the ECU to the vehicle-specific LAN as a response to the diagnostic request. The transmission section transmits the diagnostic response to the corresponding diagnostic tool.If the request receive section receives a non-prioritized diagnostic request from a non-prioritized diagnostic tool at a previous time point, and receives a prioritized diagnostic request from a prioritized diagnostic tool before the end of the malfunction diagnosis requested by the non-prioritized tool at the previous time point, the arbitration section controls the output section to cancel any output of the non-prioritized diagnostic request being transmitted by the non-prioritized tool, and controls the transmission section to cancel any transmission of the non-prioritized diagnostic response to the non-prioritized tool.

[0007] US 2010 / 0262334A1 discloses a vehicle transfer system.

[0008] US 2014 / 0282470A1 discloses systems and methods for transmitting data between one or more vehicles and a control device.

[0009] US 2016 / 0 057 043 A1 discloses a diagnostic routing system and a method for a link access group. Explanation of the invention

[0010] The present invention / disclosure provides a method for preventing a diagnostic error in a vehicle network and a device for this purpose. To this end, the present invention provides a diagnostic method according to claim 1, a diagnostic method according to claim 7, and an internal diagnostic device in a vehicle network according to claim 13.

[0011] According to exemplary embodiments, a diagnostic procedure, which is initiated by a first communication node in a vehicle network (e.g., a motor vehicle network) comprising a plurality of communication nodes, may: send a diagnostic initiation message (e.g., diagnostic initiation message), indicating that a first diagnostic operation (e.g., first diagnostic procedure) is to be performed by an external diagnostic device (hereinafter also referred to as "is to be performed"), in a broadcast manner (e.g.,in response to) a detection that the external diagnostic device is connected to the first communication node, and receiving a negative response message as a response to the diagnostic initiation message from a second communication node, which acts as an internal diagnostic device, where the negative response message indicates that a second diagnostic process (e.g., second diagnostic procedure) cannot be stopped or halted by the second communication node.

[0012] The diagnostic procedure may also include performing the first diagnostic procedure after a time specified by the negative response message.

[0013] The diagnostic initiation message can contain an indicator (e.g., note, symbol) indicating that the first diagnostic process is to be carried out, at least one identifier (e.g., at least one identifier) ​​of at least one communication node for which the first diagnostic process is to be carried out, from / among the majority of communication nodes, and information indicating a start time of the first diagnostic process.

[0014] The negative response message may contain an identifier (e.g., a code) of a third communication node, which is examined by the second diagnostic process, from / among the majority of communication nodes, and information indicating a remaining time until the completion of the second diagnostic process.

[0015] The vehicle network can have an Ethernet-based vehicle network and an ECU network (CAN)-based vehicle network, and the second communication node and the third communication node can belong to the Ethernet-based vehicle network.

[0016] The vehicle network can include an Ethernet-based vehicle network and an ECU network (CAN)-based vehicle network, wherein the negative response message cannot be received if the second communication node belongs to the Ethernet-based vehicle network and the third communication node belongs to the CAN-based vehicle network, or if the second communication node belongs to the CAN-based vehicle network and the third communication node belongs to the Ethernet-based vehicle network or the CAN-based vehicle network, and wherein the first diagnostic operation can be performed if the negative response message is not received for a predetermined time.

[0017] The first diagnostic process can be carried out after receiving a diagnostic response message, which indicates that the second diagnostic process of the second communication node has been completed.

[0018] The diagnostic response message may contain an identifier (e.g., a code) of a third communication node examined by the second diagnostic process, from / among the majority of communication nodes, a type of the second diagnostic process, and a result of the second diagnostic process.

[0019] According to exemplary embodiments, a diagnostic procedure, which is carried out by a first communication node, operating as an internal diagnostic device in a vehicle network, from / among a plurality of communication nodes, may further comprise: performing a first diagnostic operation for a second communication node from / among the plurality of communication nodes; receiving a diagnostic initiation message indicating that a second diagnostic operation is to be carried out by an external diagnostic device, from a third communication node to which the external diagnostic device is connected from / among the plurality of communication nodes; determining whether the first diagnostic operation is to be stopped or should be stopped (hereinafter also referred to as "to be stopped"), based on the diagnostic initiation message; and, in response to a determination that the first diagnostic operation cannot be stopped or should be stopped,is not stoppable, sending a negative response message indicating that the initial diagnostic process cannot be stopped or is not stoppable.

[0020] The diagnostic initiation message can contain an indicator (e.g., note, symbol) indicating that the second diagnostic process is to be carried out, at least one identifier (e.g., at least one code) of at least one communication node that is examined by the second diagnostic process, from / among the majority of communication nodes, and information indicating a start time of the second diagnostic process.

[0021] The first diagnostic operation can be performed irrespective of the second diagnostic operation in response to a determination that an identifier of the second communication node is different from the at least one identifier contained in the diagnostic initiation message, and the negative response message can be sent in response to a determination that the identifier of the second communication node is identical to the at least one identifier contained in the diagnostic initiation message and the first diagnostic operation cannot be stopped.

[0022] The first diagnostic operation can be performed regardless of the second diagnostic operation in response to a determination that the completion time (e.g., termination time) of the first diagnostic operation is before the start time of the second diagnostic operation, as specified by the diagnostic initiation message, and the negative response message can be sent in response to a determination that the completion time of the first diagnostic operation is after the start time of the second diagnostic operation, as specified by the diagnostic initiation message, and that the first diagnostic operation cannot be stopped.

[0023] The negative response message may contain an identifier (e.g., a code) of the second communication node being examined by the first diagnostic process, and information indicating the remaining time until the first diagnostic process is completed.

[0024] The vehicle network can have an Ethernet-based vehicle network and an ECU network (CAN)-based vehicle network, and the first communication node and the second communication node can belong to the Ethernet-based vehicle network.

[0025] The diagnostic procedure may also include: sending a diagnostic response message indicating that the initial diagnostic process is complete when the initial diagnostic process is complete.

[0026] According to exemplary embodiments, a first communication node, which operates as an internal diagnostic device, can also include a processor and a non-volatile, computer-readable medium, which stores at least one instruction that is executed by the processor, among a plurality of communication nodes in a vehicle network.The at least one instruction executed by the processor can cause the processor to: perform a first diagnostic operation for a second communication node of / among the plurality of communication nodes; receive a diagnostic initiation message indicating that a second diagnostic operation is to be performed by an external diagnostic device from a third communication node to which the external diagnostic device is connected of / among the plurality of communication nodes; determine whether the first diagnostic operation is to be stopped, based on the diagnostic initiation message; and, in response to a determination that the first diagnostic operation cannot be stopped or is not stoppable, send a negative response message indicating that the first diagnostic operation cannot be stopped or is not stoppable.

[0027] The diagnostic initiation message can contain an indicator (e.g., note, symbol) indicating that the second diagnostic process is to be carried out, at least one identifier (e.g., at least one code) of at least one communication node that is examined by the second diagnostic process, from / among the majority of communication nodes, and information indicating a start time of the second diagnostic process.

[0028] The at least one instruction executed by the processor can cause the processor to perform a first diagnostic operation irrespective of the second diagnostic operation in response to a determination that an identifier of the second communication node is different from the at least one identifier contained in the diagnostic initiation message.

[0029] The first diagnostic process can be performed regardless of the second diagnostic process if the completion time (e.g., end time) of the first diagnostic process is before the start time of the second diagnostic process, as specified by the diagnostic initiation message.

[0030] The negative response message may contain an identifier (e.g., a code) of the second communication node being examined by the first diagnostic process, and information indicating the remaining time until the first diagnostic process is completed.

[0031] The vehicle network can have an Ethernet-based vehicle network and an ECU network (CAN)-based vehicle network, and the first communication node and the second communication node can belong to the Ethernet-based vehicle network.

[0032] According to embodiments of the present invention, if both an internal diagnostic device and an external diagnostic device are present for a vehicle network, the internal diagnostic device can perform a diagnostic operation for a target communication node and receive a diagnostic initiation message from the external diagnostic device while the diagnostic operation for the target communication node is being performed. In this case, the internal diagnostic device can stop its diagnostic operation for the target communication node. This prevents a collision / conflict between the diagnostic operations of the internal and external diagnostic devices.

[0033] If the diagnostic process of the target communication node cannot be stopped, the internal diagnostic device can send a negative response message indicating that the corresponding diagnostic process cannot be stopped. The external diagnostic device can receive this negative response message from the internal diagnostic device and will be unable to perform its diagnostic process for the target communication node for a duration specified by the received negative response message. This prevents a collision / conflict between the diagnostic processes of the internal and external diagnostic devices. Brief description of the drawings

[0034] Embodiments of the present invention / disclosure are made more vivid by describing them in detailed embodiments of the present invention / disclosure with reference to the accompanying drawings, wherein: Fig. 1 is a block diagram which represents a first embodiment of a vehicle network topology, Fig. 2 is a block diagram which represents a first embodiment of a communication node belonging to a vehicle network, Fig. 3 is a block diagram which represents a second embodiment of a communication node belonging to a vehicle network, Fig. 4 is a block diagram which represents a first embodiment of a protocol structure of a communication node forming a vehicle network, Fig.5 is a block diagram, which represents a second embodiment of a vehicle network topology, Fig. 6 is a block diagram, which represents a third embodiment of a vehicle network topology, Fig. 7 a flowchart to explain a first embodiment of a method which is described in Fig. The vehicle network shown in section 6 is used to avoid a collision between diagnostic operations, and Fig. 8 a flowchart to explain a second embodiment of a method which is described in Fig. The vehicle network shown in section 6 is carried out to avoid a collision between diagnostic operations.

[0035] It should be understood that the attached drawings are not necessarily to scale and represent a somewhat simplified depiction of various properties in order to illustrate the basic principles of the invention. The specific design features of the present invention, including, for example, specific dimensions, orientations, positions, and shapes as disclosed herein, are (at least) partially determined by the respective intended application and usage environment. Detailed description

[0036] Embodiments of the present invention are described in detail below with reference to the accompanying drawings. However, as will be clear to those skilled in the art, the described embodiments can be modified in numerous different ways without departing from the essence or scope of the present invention. Furthermore, the same reference numerals throughout the description refer to identical or similar elements.

[0037] The terminology used herein serves only to describe certain embodiments and is not intended to limit the invention. The singular forms "a," "an," "one," and "the" are used herein to include the plural forms unless the context clearly indicates otherwise. Furthermore, the terms "have" and / or "having" as used in this description specify the presence of the aforementioned features, integers, steps, processes, elements, and / or components, but do not exclude the presence or addition of one or more further features, integers, steps, processes, elements, components, and / or groups thereof. As used herein, the term "and / or" includes any and all combinations of one or more of the related items.

[0038] It is to be understood that the term "vehicle" or "vehicle-..." or any similar term used herein includes motor vehicles in general, such as passenger cars, including so-called sport utility vehicles (SUVs), buses, trucks, numerous commercial vehicles, watercraft, including a variety of boats and ships, aircraft and the like, and includes hybrid vehicles, electric vehicles, internal combustion engine vehicles, plug-in hybrid electric vehicles, hydrogen-powered vehicles and other vehicles for alternative fuels (e.g. fuels produced from resources other than petroleum).

[0039] Although embodiments are described as utilizing multiple units to perform the exemplary operations, it is understood that the exemplary operations can also be performed by a single module or multiple modules. It is also understood that a control device / control unit can perform one or more of the operations described below, and that the term control device / control unit refers to a hardware device comprising memory and a processor. The memory is configured to store the modules, and the processor is specifically configured to execute the modules to perform one or more of the operations described below. Furthermore, it is understood that the units or modules described herein can represent a control device / control unit for controlling the operation of the unit or module (e.g.,as such (may be executed / embodied).

[0040] Furthermore, the control logic of the present invention can be implemented as non-volatile, computer-readable media on a computer-readable medium (e.g., a data carrier) containing executable program instructions that are executed by means of a processor, a control unit, or the like. Examples of computer-readable media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), compact disc (CD)-ROMs, magnetic tapes, floppy disks, flash memory, chip cards (e.g., smart cards, memory cards), and optical data storage devices. The computer-readable recording medium can also be distributed in networked computer systems, so that the computer-readable media can be stored and executed in a distributed manner, e.g.,via a telematics server or a control unit network (CAN; English "Controller Area Network" - also "control device area network").

[0041] Since the present invention / disclosure can be modified in numerous ways and can take various forms, certain embodiments are shown in the accompanying drawings and described in detail in the detailed description. However, it should be understood that this description is not intended to limit the present invention / disclosure to these specific embodiments, but rather that the present invention / disclosure is intended to cover all modifications and alternatives that fall within the scope and meaning of the present invention / disclosure.

[0042] Relational terms, including, for example, "first / first / first", "second / second / second", and the like, can be used to describe different elements; however, the elements are not limited by these terms. These terms are used only to distinguish one element from another. For example, a first component may be called a second component without altering the scope of the present invention, and the second component may similarly be called the first component. The term "and / or" means any of, or a combination of, a plurality of related and described items.

[0043] When a particular component is described as "connected to" or "coupled / connected to" another component, it means that the component is directly connected to or coupled / connected to the other component, or that another component may be located between them. Conversely, when a particular component is described as "directly connected to" or "directly coupled / connected to" another component, it means that no other component is located between them.

[0044] Unless otherwise stated or evident from the context, the term "approximately" (or "about") used herein is to be understood as being within a normal tolerance in engineering, e.g., within two standard deviations of the mean. "Approximately" (or "about") may be understood as being within 10%, 9%, 8%, 7%, 6%, 5%, 4%, 3%, 2%, 1%, 0.5%, 0.1%, 0.05%, or 0.01% of the stated value. Unless otherwise clear from the context, all numerical values ​​provided herein are modified by the term "approximately".

[0045] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meanings as generally understood by a person skilled in the art in which this invention / disclosure relates. Terms such as those commonly used and found in dictionaries should be interpreted as having meanings consistent with their context-dependent meanings in engineering. Unless clearly defined, terms in this description are not to be interpreted fully and disproportionately as their formal meanings.

[0046] Embodiments of the present invention are described in detail below with reference to the accompanying drawings. When describing the invention / disclosure, the same reference numerals refer to the same or equivalent elements throughout the description of the figures, and a further description is omitted to facilitate the overall understanding of the invention / disclosure.

[0047] Fig. Figure 1 is a block diagram representing a first embodiment of a vehicle network topology.

[0048] As in Fig.As shown in Figure 1, a communication node forming a vehicle network can be a gateway (e.g., network transition device), a switch (or bridge; where in technical terms "switch" or "bridge" are also referred to as network switch / network switch / network switching device or network bridge), or an end node. Gateway 100 can be connected to at least one switch 110, 110-1, 110-2, 120, or 130 and can be configured to connect different networks. For example, Gateway 100 can support connections between a switch that supports a CAN network (or a FlexRay network, a MOST network (Media Oriented Systems Transport), or a LIN network (Local Interconnect Network)) and a switch that supports an Ethernet protocol.Each of the switches 110, 110-1, 110-2, 120, and 130 can be connected to at least one of the end nodes 111, 112, 113, 121, 122, 123, 131, 132, and 133. Each of the switches 110, 110-1, 110-2, 120, and 130 can connect the end nodes 111, 112, 113, 121, 122, 123, 131, 132, and 133 (e.g., the end nodes assigned to it) to each other and control at least one of the end nodes 111, 112, 113, 121, 122, 123, 131, 132, and 133 that is connected to the switch.

[0049] Each of the terminal nodes 111, 112, 113, 121, 122, 123, 131, 132, and 133 can have an electronic control unit (ECU) configured to control numerous types of devices installed in a vehicle (e.g., motor vehicle, especially passenger car). For example, each of the terminal nodes 111, 112, 113, 121, 122, 123, 131, 132, and 133 can have an ECU present in an infotainment device (e.g., a display device, a navigation device, and an AVM device).

[0050] The communication nodes forming the vehicle network (i.e., gateways, switches, end nodes, etc.) can be connected in a star topology, a bus topology, a ring topology, a tree topology, a mesh topology, or the like. Furthermore, each of the communication nodes forming the vehicle network can support the CAN protocol, the FlexRay protocol, the MOST protocol, the LIN protocol, the Ethernet protocol, or the like. Embodiments of the present invention can be applied to the aforementioned network topologies, and the network topology to which embodiments of the present invention are applied is not limited to those and can be configured in numerous ways.

[0051] Fig. Figure 2 is a block diagram representing a first embodiment of a communication node belonging to a vehicle network.

[0052] As in Fig. As shown in section 2, a communication node 200, which is part of a vehicle network, can be located in, for example, a vehicle network. Fig.The communication node 200, as shown in Figure 1, comprises a physical layer (PHY layer) 210 and a control unit 220. The communication node 200 may also include a controller (not shown) for power supply. In particular, the control unit 220 may be implemented as a media access control (MAC) layer. The PHY layer 210 may be configured to receive signals from or transmit signals to another communication node. The control unit 220 may be configured to control the PHY layer 210 and perform various functions (e.g., an infotainment function or the like). The PHY layer 210 and the control unit 220 may be implemented as a single system-on-a-chip (SoC) or alternatively as separate chips.

[0053] The PHY layer 210 and the control device 220 can be connected via a media-independent interface (MII) 230. The MII 230 can have an interface defined in IEEE 802.3 and can include a data interface and a management interface between the PHY layer 210 and the control device 220. A reduced MII (RMII), a Gigabit MII (GMII), a reduced GMII (RGMII), a serial GMII (SGMII), or a 10-GMII (XGMII) can be used instead of the MII 230. The data interface can have a transmit channel and a receive channel, each of which can carry an independent clock, data, and control signal. The management interface can be a two-signal interface, with one signal for the clock and one signal for the data.

[0054] The PHY layer 210 can include a PHY layer interface 211, a PHY layer processor 212, and a PHY layer memory 213. The configuration of the PHY layer 210 is not limited to these and can be designed in numerous ways. The PHY layer interface 211 can be configured to send a signal received from the control unit 220 to the PHY layer processor 212 and to send a signal received from the PHY layer processor 212 back to the control unit 220. The PHY layer processor 212 can be configured to control operations (e.g., process sequences) of the PHY layer interface 211 and the PHY layer memory 213. The PHY layer processor 212 can be configured to modulate a signal to be sent or to demodulate a received signal. The PHY layer processor 212 can be configured to control the PHY layer memory 213 to input or output a signal.The PHY layer memory 213 can be configured to store the received signal and output the stored signal based on a request from the PHY layer processor 212.

[0055] The control unit 220 can be configured to monitor and control the PHY layer 210 using the MII 230. The control unit 220 can have a control unit interface 221, a control unit processor 222, a main memory 223, and an auxiliary memory 224. The control unit processor 222 is an electrical circuit that performs various functions described below. The design of the control unit 220 is not limited to this, and the control unit 220 can be configured in numerous ways. The control unit interface 221 can be configured to receive a signal from the PHY layer 210 (e.g., the PHY layer interface 211) or a higher layer.The upper layer (not shown) receives the signal, sends the received signal to the control device processor 222, and sends the signal received by the control device processor 222 to the PHY layer 210 or the higher layer. The control device processor 222 may further comprise independent memory control logic or integrated memory control logic for controlling the control device interface 221, main memory 223, and auxiliary memory 224. The memory control logic may be implemented such that it is contained in the main memory 223 and auxiliary memory 224, or it may be implemented such that it is contained within the control device processor 222.

[0056] Each of the main memory 223 and the auxiliary memory 224 can be configured to store a signal processed by the control device processor 222 and to output the stored signal based on a request from the control device processor 222. The main memory 223 can be volatile memory (e.g., RAM) configured to temporarily store data required for the operation of the control device processor 222. The auxiliary memory 224 can be non-volatile memory in which operating system code (e.g., a system kernel and a device driver) and application program code for performing a function of the control device 220 can be stored. Flash memory, which has a high processing speed, a hard disk drive (HDD), or a compact disc read-only storage device (CD-ROM) can be used for large-capacity data storage.(for large-volume data storage) can be used as the non-volatile memory. The control device processor 222 can typically include a logic circuit comprising at least one processor core. A core from an ARM family (where ARM stands for "Advanced RISC Machines") or a core from an Atom family can be used as the control device processor 222.

[0057] The PHY layer 210 (i.e., the PHY layer processor 212) can be in a sleep mode (e.g., hibernation, such as standby mode), a normal mode (e.g., active mode), or the like. Based on the control of the PHY layer processor 212, the PHY layer 210 can transition from sleep mode to normal mode and vice versa. The control unit 220 (i.e., the control unit processor 222) can be in a power-off mode, sleep mode, normal mode, and the like. The control unit 220 can transition from power-off mode to sleep mode or normal mode, and vice versa.

[0058] The term "power shutdown mode" can refer to a state in which the corresponding unit (e.g., the control unit 220) is not supplied with power. "Sleep mode" can refer to a state (i.e., a power-saving state) in which the corresponding unit (e.g., the PHY layer 210, the control unit 220, etc.) is supplied with minimal power for basic operation. "Normal mode" can refer to a state (i.e., a wake-up or awake state) in which the corresponding unit (e.g., the PHY layer 210, the control unit 220, etc.) is supplied with power normally.

[0059] The in Fig. The communication node 200 shown can, however, be designed as follows.

[0060] Fig. Figure 3 is a block diagram that represents a second embodiment of a communication node belonging to a vehicle network.

[0061] With reference to Fig.3. The communication node 200 can include the PHY layer 210, the control device 220, a power circuit (e.g., current / voltage supply circuit) 240, an OR gate 250, a power controller 260, and the like. Each of the PHY layer 210 and the control device 220, which are in Fig. Figure 3 shows the same as or similar to the PHY layer 210 and control unit 220, which are in Fig. 2 are shown.

[0062] The PHY layer 210 can have multiple pins (e.g., P11, P12, P13, P14, and P15). PHY layer 210 can output a signal to instruct power supply, a signal to instruct power shutdown, etc., through P11. For example, a HIGH signal (e.g., a signal with a high voltage level relative to the LOW signal) output by P11 of PHY layer 210 can indicate power supply, and a LOW signal (e.g., a signal with a low voltage level relative to the HIGH signal) output by P11 of PHY layer 210 can indicate power shutdown. Pin P11 of PHY layer 210 can also be designated as an inhibit pin.

[0063] Alternatively, the PHY layer 210 can output an interrupt signal via P11. For example, a HIGH signal output by P11 of the PHY layer 210 can symbolize an interrupt signal, and this interrupt signal can be received at P22 of the control unit 220. The interrupt signal can initiate a transition from sleep mode to normal mode. Pin P11 can be used to designate an interrupt pin (e.g., an interrupt pin).

[0064] Electrical energy or power can be supplied to PHY layer 210 via P12 from the power circuit 240. PHY layer 210 can receive signals instructing a transition from sleep mode to normal mode, and signals instructing a transition from normal mode to sleep mode, via P13. For example, a HIGH signal input through P13 of PHY layer 210 can instruct the transition from sleep mode to normal mode, and a LOW signal input through P13 of PHY layer 210 can instruct the transition from normal mode to sleep mode. Pin P13 of PHY layer 210 can be designated as an enable pin.

[0065] The P14 pin of PHY layer 210 can be used for xMII, and the P15 pin of PHY layer 210 can be used for an administrative data input / output (MDIO) interface. For example, PHY layer 210 can send signals (e.g., Ethernet-related signals) to and from the controller 220 using P14 and P15. The configuration and / or design of each pin from the plurality of pins available in PHY layer 210 is not limited to the one described above, and each pin from the plurality of pins available in PHY layer 210 can be configured in various ways.

[0066] The control unit 220 can have multiple connections (e.g., P21, P22, P23, P24, and P25). Electrical energy or power can be supplied to the control unit 220 from the power circuit 240 via P21. The control unit 220 can receive an interrupt signal via P22. For example, a HIGH signal input through P22 of the control unit 220 can symbolize an interrupt signal. Upon receiving the interrupt signal, the control unit 220 can switch from sleep mode to normal mode. Connection P22 of the control unit 220 can be designated as an interrupt terminal.

[0067] The control unit 220 can output a signal instructing a transition from sleep mode to normal mode, a signal instructing a transition from normal mode to sleep mode, and the like, via P23. For example, a HIGH signal output by P23 of the control unit 220 can instruct the transition from sleep mode to normal mode, and a LOW signal output by P23 of the control unit 220 can instruct the transition from normal mode to sleep mode. The P23 pin of the control unit 220 can be designated as the EN pin (also called the "EN pin").

[0068] The P24 pin of the 220 controller can be used for xMII, and the P25 pin of the 220 controller can be used for the MDIO interface. For example, the 220 controller can send signals (e.g., Ethernet-related signals) to and receive signals from the 210 PHY layer using P24 and P25. The 220 controller can detect a local wake-up signal (e.g., a local event) using P26. For example, a HIGH signal input through P26 of the 220 controller can indicate a local wake-up signal. The P26 pin of the 220 controller can be designated as a WAKE pin.The design and / or configuration of each connection from the plurality of connections available in the control unit 220 is not limited to the one(s) described above, and each connection from the plurality of connections available in the control unit 220 can be designed in various ways.

[0069] The power circuit 240 can have multiple connections (e.g., P31, P32, and P33). The power circuit 240 can receive a signal to initiate the supply of current, a signal to initiate a current shutdown, and the like, via P33. For example, a HIGH signal input to the power circuit 240 via P33 can indicate the supply of current, and a LOW signal input to the power circuit 240 via P33 can indicate the shutdown of the current. The power circuit 240 can supply current based on the signal input via P33. For example, the power circuit 240 can supply energy or power (e.g., by supplying electrical current) to the control unit 220 via P31 and to the PHY layer 210 via P32.The design and / or specification of each connection from the plurality of connections present in the power circuit 240 is not limited to the one(s) described above, and each connection from the plurality of connections present in the power circuit 240 can be designed in various ways.

[0070] The OR gate 250 can receive a control signal (e.g., a HIGH signal or a LOW signal) from any unit (e.g., the control device 220) and a control signal (e.g., a HIGH signal or a LOW signal) from the PHY layer 210. The OR gate 250 can perform an OR operation on the control signals received from the unit and the PHY layer 210 and can output the result of the OR operation. The result of the OR operation can be inputted to P33 of the power circuit 240.

[0071] An input terminal of the power controller 260 can be connected to P32 of the power circuit 240, and an output terminal of the power controller 260 can be connected to P12 of the PHY layer 210. If the voltage of the power supplied to the power circuit 240 exceeds a predetermined threshold (e.g., 3.3V), then the power controller 260 can regulate the voltage of the supplied power to the predetermined threshold or less and supply the power exhibiting the regulated voltage to the PHY layer 210.

[0072] A protocol structure of the in Fig. The communication node shown in 1 to 3 may, meanwhile, be as follows.

[0073] Fig. Figure 4 is a block diagram, which represents a first embodiment of a protocol structure of a communication node forming a vehicle network.

[0074] As in Fig.As shown in Figure 4, a communication node can have layers 1 through 7. Layer 1 of the communication node can support PHY functions and a transmission rate of 100 megabits per second (Mbps). Layer 2 of the communication node can support the IEEE 802.1Q protocol, the IEEE 802.1p protocol, the IEEE 802.3 protocol, the Audio / Video Bridging (AVB) protocol (e.g., IEEE 802.1Qav protocol, IEEE 802.1Qat protocol), and similar protocols. Layer 3 of the communication node can support Internet Protocol version 4 (IPv4), the Address Resolution Protocol (ARP), Internet Control Message Protocol version 4 (ICMPv4), IEEE 802.1AS, IEEE 1722, and similar protocols. Layer 4 of the communication node can support the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), IEEE 802.1AS, IEEE 1722 and the like.Layers 5 to 7 of the communication node can support the Diagnostics over Internet Protocol (DoIP), the EthCC protocol, the Dynamic Host Configuration Protocol (DHCP), the SD protocol, the Network Management (NM) protocol, IEEE 802.1AS, IEEE 1722 and the like.

[0075] The following description outlines methods for preventing diagnostic errors in a vehicle network. Even if a procedure (e.g., sending or receiving a signal) to be performed at the first communication node is described below, the corresponding second communication node can perform a procedure (e.g., receiving or sending the signal) that corresponds to the procedure performed at the first communication node. That is, if the operation (e.g., a process, a sequence of actions, an operation, etc.) of the first communication node is described, the corresponding second communication node can perform an operation corresponding to the operation of the first communication node.Conversely, if the operation of the second communication node is described, the corresponding first communication node can perform an operation corresponding to the operation of the second communication node.

[0076] Fig. Figure 5 is a block diagram representing a second embodiment of a vehicle network topology.

[0077] With reference to Fig. 5. A CAN-based vehicle network can have multiple end nodes 511 to 516. In the CAN-based vehicle network, the multiple end nodes 511 to 516 can be interconnected via a bus line. This means that communication between the multiple end nodes 511 to 516 can take place via the bus line.

[0078] An external diagnostic device 520 can be connected to the CAN-based vehicle network via a connector and perform diagnostic operations (e.g., diagnostic procedures, diagnostic methods) for the majority of end nodes 511 to 516 belonging to the CAN-based vehicle network. If the sixth end node 516 supports a diagnostic function, it can also perform diagnostic operations for the other end nodes 511 to 515 in the CAN-based vehicle network. In this case, the sixth end node 516, which supports the diagnostic function, can be referred to as an "internal diagnostic device." Each of the internal diagnostic device (e.g., the sixth end node 516) and the external communication node 520 can be an on-board diagnostic (ODB) device.The diagnostic procedure performed by the internal diagnostic device can be the same as, or similar to, the diagnostic procedure performed by the external diagnostic device 520. Alternatively, the diagnostic procedure performed by the internal diagnostic device can be different from the diagnostic procedure of the external diagnostic device 520.

[0079] If the internal diagnostic device and the external diagnostic device 520 perform diagnostic operations simultaneously, a diagnostic result may not be accurate due to a collision / conflict between the diagnostic operations. However, since the communication path (i.e., the bus line) in the CAN-based vehicle network is shared by all end nodes 511 to 516, the internal diagnostic device can verify (e.g., confirm for itself) that the diagnostic operation is being performed by the external diagnostic device 520 by receiving a diagnosis-related message (e.g., a diagnostic request message) from the external diagnostic device 520.For example, the internal diagnostic device can perform a monitoring operation on the diagnostic message from the external diagnostic device 520 before the internal diagnostic device performs its diagnostic operation, in order to verify that the external diagnostic device 520 is performing the diagnostic operation. The internal diagnostic device, having confirmed that the diagnostic operation is being performed by the external diagnostic device, cannot perform its own diagnostic operation. Therefore, the diagnostic operation of the external diagnostic device 520 cannot conflict with or collide with the diagnostic operation of the internal diagnostic device.

[0080] In the Ethernet-based vehicle network (e.g., the one in Fig.However, in the vehicle network shown in Figure 1, a communication path is not shared among the end nodes belonging to the vehicle network, so the diagnostic process of the internal diagnostic device can conflict with or collide with the diagnostic process of the external diagnostic device. For example, if the diagnostic process of the internal diagnostic device and the diagnostic process of the external diagnostic device are performed simultaneously in the Ethernet-based vehicle network, a diagnostic-related message (e.g., a diagnostic request message) from the internal diagnostic device cannot be received by the external diagnostic device, and vice versa.Therefore, the internal diagnostic device cannot verify whether the external diagnostic device is performing the diagnostic process, and the external diagnostic device cannot verify whether the internal diagnostic device is performing the diagnostic process. For this reason, the diagnostic process performed by the internal diagnostic device may conflict with or collide with the diagnostic process performed by the external diagnostic device.

[0081] To prevent conflicts / collisions between the diagnostic processes of the internal and external diagnostic devices in the Ethernet-based vehicle network, the internal diagnostic device's diagnostic process can be performed after a predetermined time (e.g., 10 seconds) after the vehicle starts. However, both the internal and external diagnostic devices cannot perform their diagnostic processes between the vehicle's start time and the predetermined time, even if the external diagnostic device is not connected to the Ethernet-based vehicle network. In this case, vehicle problems occurring between the start time and the predetermined time cannot be detected, and consequently, serious problems may arise while the vehicle is being driven.

[0082] Furthermore, each of the internal and external diagnostic devices can perform a software update function for a communication node (e.g., an end node) in the Ethernet-based vehicle network. However, if the diagnostic process of the external diagnostic device is detected during the software update by the internal diagnostic device, the internal diagnostic device should stop the software update, which may result in a software update failure. Since a fault verification process of the updated software, for example, after a transition from an "ignition-off state" to an "ignition-on state" (e.g.,Since the software update process is performed during a final stage (e.g., a change in the ignition switch state from off to on), it can be difficult to detect the fault if the software update process is stopped before completion. Because the internal diagnostic device does not know when the external diagnostic device should perform its diagnostic operation (or when the external diagnostic device should connect to the Ethernet-based vehicle network), the software update process may be blocked by the internal diagnostic device within the Ethernet-based vehicle network.

[0083] Fig. Figure 6 is a block diagram representing a third embodiment of a vehicle network topology.

[0084] With reference to Fig.6. A vehicle network can include a gateway 600, switches 610, 620, and 630, end nodes 611, 612, 621, 622, 631, 632, and 633, and the like. The communication nodes 600, 610, 611, 612, 620, 621, 622, 630, 631, 632, and 633 belonging to the vehicle network can have the same or a similar configuration as the one described in Fig. 2 and Fig. The 3 communication nodes shown have 200 and can have the same or a similar protocol structure as those in Fig. They have the protocol structure shown in section 4.

[0085] The vehicle network can be either an Ethernet-based or a CAN-based vehicle network. The Ethernet-based vehicle network can include a first switch 610, a second switch 620, a first end node 611, a second end node 612, a third end node 621, a fourth end node 622, and so on. The first end node 611 and the second end node 612 can be connected to the first switch 610, and the third end node 621 and the fourth end node 622 can be connected to the second switch 620. The CAN-based vehicle network can include a third switch 630, a fifth end node 631, a sixth end node 632, a seventh end node 633, and so on. The fifth end node 631, the sixth end node 632, and the seventh end node 633 can be connected to the third switch 630 via a bus line.

[0086] The Gateway 600 can support communication between the Ethernet-based vehicle network and the CAN-based vehicle network. For example, the Gateway 600 can be connected to the first switch 610 and the second switch 620, which belong to the Ethernet-based vehicle network, and can also be connected to the third switch 630, which belongs to the CAN-based vehicle network.

[0087] The diagnostic process (e.g., a diagnostic procedure) for the communication nodes belonging to the vehicle network can be performed by an external diagnostic device 640 or an internal diagnostic device. Both the external and the internal diagnostic devices can be OBD devices. The external diagnostic device 640 can be connected to the gateway 600 via a connector and can perform diagnostic operations for the communication nodes after being connected to the gateway 600. The internal diagnostic device can be an end node that performs diagnostic functions for / among the end nodes 611, 612, 621, 622, 631, 632, and 633 belonging to the vehicle network. For example, at least one of the end nodes 611, 612, 621, and 622 belonging to the Ethernet-based vehicle network can be the internal diagnostic device.Alternatively, at least one of the end nodes 631, 632 and 633, which belong to the CAN-based vehicle network, can be the internal diagnostic device.

[0088] The external diagnostic device 640 or the internal diagnostic device can perform diagnostic operations on the at least one end node, and the end node being examined (e.g., undergoing diagnosis) by the external diagnostic device 640 or the internal diagnostic device can be referred to as a 'target end node'. If the external diagnostic device 640 is connected to the gateway 600, the diagnostic operation of the internal diagnostic device may conflict with the diagnostic operation of the external diagnostic device 640. Procedures for preventing a collision (hereinafter referred to simply as 'collision') between the diagnostic operation of the internal diagnostic device and the diagnostic operation of the external diagnostic device 640 are described below.The method for preventing collisions between diagnostic operations can vary depending on the type of vehicle network to which each of the internal diagnostic device and the target endpoint belongs (e.g., Ethernet-based vehicle network or CAN-based vehicle network). This means that different methods for preventing collisions between diagnostic operations can be applied to each of the scenarios described in Table 1 below. [Table 1] Location of the internal diagnostic device Location of the destination terminal node Scenario 1 Ethernet-based vehicle network Ethernet-based vehicle network Scenario 2 Ethernet-based vehicle network CAN-based vehicle network Scenario 3 CAN-based vehicle network Ethernet-based vehicle network Scenario 4 CAN-based vehicle network CAN-based vehicle network

[0089] A in Fig. The procedure shown in Figure 7 for preventing a collision between diagnostic processes can be applied to Scenario 1; another, in Fig. The procedure shown in Figure 8 for preventing a collision between diagnostic processes can be applied to scenario 2, which is described in Fig. 7 or Fig. The 8 described procedures can be applied to scenario 3, and that in Fig.The 8 described procedures can be applied to scenario 4.

[0090] Fig. Figure 7 is a flowchart to explain a first embodiment of a method described in Figure 7. Fig. The vehicle network shown in Figure 6 is used to avoid a collision between diagnostic operations.

[0091] With reference to Fig. 7. Can a gateway that is in Fig. The gateway 600 shown in section 6 can be a target endpoint of any of the endpoints 611, 612, 621 and 622, which belong to the Ethernet-based vehicle network that is in Fig. As shown in Figure 6, an internal diagnostic device can be an end node which is different from the end node designated as the target end node, from / among the end nodes 611, 612, 621 and 622, which belong to the Ethernet-based vehicle network that is in Fig.As shown in section 6, they belong to, or can be, the internal diagnostic device of one of the end nodes 631, 632 and 633, which belong to the CAN-based vehicle network that is in Fig. Figure 6 shows, belonging, being. For example, the target end node may be the first end node 611 and the internal diagnostic device may be the fourth end node 622 or the fifth end node 631.

[0092] The internal diagnostic device can perform a diagnostic operation for the target endpoint (S701). The external diagnostic device can be connected to the gateway while the diagnostic operation is being performed between the internal diagnostic device and the target endpoint. In this case, the gateway (or the external diagnostic device) can generate a diagnostic initiation message (S702), which indicates that a diagnostic operation is to be performed by the external diagnostic device (hereinafter referred to as "to be performed"). The diagnostic initiation message can contain at least one information element from those listed in Table 2 below. [Table 2] Information element Description Diagnostic initiation indicator Indicates that a diagnostic procedure is to be performed by the external diagnostic device. Identifier Specifies an identifier for the target endpoint to be examined by the external diagnostic device. For example, the diagnostic initiation message can contain an identifier for at least one target endpoint. Alternatively, an identifier included in the diagnostic initiation message can specify all endpoints belonging to the vehicle network. type of diagnosis Specifies the type of diagnostic procedure (e.g., software update procedure, etc.) to be performed by the external diagnostic device. Diagnosis time Specifies the execution time (e.g., a start time or duration) of the diagnostic procedure to be performed by the external diagnostic device.

[0093] The gateway can send the diagnostic initiation message in a broadcast manner (S703). The diagnostic initiation message can therefore be sent to all communication nodes belonging to the vehicle network. The internal diagnostic device can receive the diagnostic initiation message and verify (e.g., confirm for itself) that the diagnostic operation of the external diagnostic device is to be carried out based on the received diagnostic initiation message. Furthermore, the internal diagnostic device can determine whether a diagnostic operation carried out by the internal diagnostic device should be stopped for the target end node (S704). Step S704 can be performed according to the type of information element present in the diagnostic initiation message. 1) A case where the diagnostic initiation message indicates that the diagnostic process of the external diagnostic device is to be carried out.

[0094] In response to receiving the diagnostic initiation message, the internal diagnostic device can stop its diagnostic operation for the target endpoint if it is possible to do so. If, however, it is impossible to stop its diagnostic operation for the target endpoint, the internal diagnostic device can generate a negative response message indicating that it is impossible to stop its diagnostic operation (S705). For example, the internal diagnostic device may determine that it is impossible to stop the diagnostic operation for the target endpoint if a software update operation is (currently) being performed on the target endpoint. The negative response message can contain at least one information element from those listed in Table 3 below. [Table 3] Information element Description Identifier Specifies an identifier of the target terminal node examined by the internal diagnostic device. type of diagnosis Specifies the type of diagnostic procedure (e.g., software update procedure, etc.) performed by the internal diagnostic device. Time remaining Indicates a remaining time until completion of the diagnostic process performed by the internal diagnostic device or a completion time (termination time) of the diagnostic process performed by the internal diagnostic device.

[0095] The internal diagnostic device can send the negative response message (S706). The negative response message can be broadcast and can be sent periodically until the diagnostic operation performed by the internal diagnostic device is complete. The gateway (or external diagnostic device) can receive the negative response message, and the diagnostic operation of the external diagnostic device can be performed taking into account the information contained in the negative response message (S707). For example, the external diagnostic device can perform diagnostic operations for end nodes other than the end node specified by the identifier contained in the negative response message. Alternatively, the external diagnostic device can perform the diagnostic operation after a time specified by the remaining time contained in the negative response message.Alternatively, the external diagnostic device may not perform the diagnostic procedure if the negative response message is received, and may perform the diagnostic procedure if the negative response message is not received for a predetermined time (e.g., over a predetermined period of time).

[0096] Conversely, if the diagnostic process for the target terminal node is stopped or completed, the internal diagnostic device can generate a diagnostic response message (S708). The diagnostic response message can indicate that the diagnostic process has been stopped or completed by the internal diagnostic device. The diagnostic response message can contain at least one information element from those listed in Table 4 below. [Table 4] Information element Description Identifier Specifies an identifier of the target terminal node examined by the internal diagnostic device. type of diagnosis Specifies the type of diagnostic procedure performed by the internal diagnostic device (e.g. Software update process, etc.). Diagnostic result Indicates a result of the diagnostic process performed by the internal diagnostic device.

[0097] The internal diagnostic device can send the diagnostic response message (S709). The diagnostic response message can be sent in a broadcast mode. The gateway (or the external diagnostic device) can receive the diagnostic response message from the internal diagnostic device and can verify or confirm the information contained in the diagnostic response message. The diagnostic procedure of the external diagnostic device can be performed after the diagnostic response message has been received. 2) A case where the diagnostic initiation message contains the information elements listed in Table 2

[0098] In response to receiving the diagnosis initiation message, the internal diagnostic device can compare the identifier specified by the diagnosis initiation message with the identifier of the target end node. If the identifier specified by the diagnosis initiation message differs from the identifier of the target end node, the internal diagnostic device can perform the diagnosis operation for the target end node regardless of, or without regard to, the diagnosis operation of the external diagnostic device. In the case that the identifier specified by the diagnosis initiation message is identical to the identifier of the target end node, the internal diagnostic device can determine the diagnosis time (i.e., the start time of the diagnosis operation of the external diagnostic device) specified by the diagnosis initiation message and a completion time of its own diagnosis operation (i.e.,The completion times of the diagnostic process of the internal diagnostic device are compared. If the start time of the diagnostic process of the external diagnostic device is after the completion of the diagnostic process of the internal diagnostic device, the internal diagnostic device can perform the diagnostic process for the target end node regardless of the diagnostic process of the external diagnostic device.

[0099] If, however, the start time of the external diagnostic device's diagnostic operation precedes the completion of the internal diagnostic device's diagnostic operation, the internal diagnostic device can stop its diagnostic operation for the target endpoint if it is possible to do so. If it is impossible to stop its diagnostic operation for the target endpoint, the internal diagnostic device can generate a negative response message indicating that it is impossible to stop its diagnostic operation (S705). For example, the internal diagnostic device might determine that it is impossible to stop its diagnostic operation for the target endpoint if a software update operation is (currently) being performed for the target endpoint. The negative response message can contain at least one information element from those listed in Table 3 above.

[0100] The internal diagnostic device can send the negative response message (S706). The negative response message can be broadcast and can be sent periodically until the diagnostic operation performed by the internal diagnostic device is complete. The gateway (or external diagnostic device) can receive the negative response message, and the diagnostic operation of the external diagnostic device can be performed taking into account the information contained in the negative response message (S707). For example, the external diagnostic device can perform diagnostic operations for end nodes other than the end node specified by the identifier contained in the negative response message. Alternatively, the external diagnostic device can perform the diagnostic operation after a time specified by the remaining time contained in the negative response message.Alternatively, the external diagnostic device may not perform the diagnostic procedure if the negative response message is received, and may perform the diagnostic procedure if the negative response message is not received for a predetermined time (e.g., over a predetermined period of time).

[0101] Conversely, if the diagnostic process for the target endpoint is stopped or completed, the internal diagnostic device can generate a diagnostic response message (S708). The diagnostic response message can indicate that the diagnostic process has been stopped or completed by the internal diagnostic device. The diagnostic response message can contain at least one piece of information from the information elements listed in Table 4 above. The internal diagnostic device can send a diagnostic response message (S709). The diagnostic response message can be broadcast. The gateway (or external diagnostic device) can receive the diagnostic response message from the internal diagnostic device and can verify or acknowledge the information elements contained in the diagnostic response message.The diagnostic process of the external diagnostic device can be performed after the diagnostic response message has been received.

[0102] Fig. Figure 8 is a flowchart to explain a second embodiment of a method described in Figure 8. Fig. The vehicle network shown in Figure 6 is used to avoid a collision between diagnostic operations.

[0103] With reference to Fig. 8. Can a gateway that is in Fig. The gateway 600 shown in Figure 6 can be used, and an external diagnostic device can be connected to the gateway 600. If the procedure is applied to scenario 2 of Table 1, a target end node can be one of the end nodes 631, 632, and 633, which belong to the CAN-based vehicle network shown in Figure 6. Fig. Figure 6 shows that the end nodes 611, 612, 621 and 622 belong to the Ethernet-based vehicle network that is in Fig.Figure 6 shows that the target end nodes belong to the Ethernet-based vehicle network shown in Table 1. In the case that the procedure is applied to scenario 3 of Table 1, the target end node can be one of the end nodes 611, 612, 621, and 622, which belong to the Ethernet-based vehicle network shown in Table 1. Fig. As shown in Figure 6, the internal diagnostic device can be one of the end nodes 631, 632 and 633, which belong to the CAN-based vehicle network that is in Fig. 6 is shown. In the case that the procedure is applied to scenario 4 of Table 1, the target end node can be one of the end nodes 631, 632 and 633, which belong to the CAN-based vehicle network that is shown in Fig. As shown in Figure 6, the internal diagnostic device can be a different end node than the end node designated as the target end node, from end nodes 631, 632 and 633, which belong to the CAN-based vehicle network that is in Fig. 6 is shown, belong, be.

[0104] The internal diagnostic device can perform a diagnostic operation for the target endpoint (S801). The external diagnostic device can be connected to the gateway while the diagnostic operation is being performed between the internal diagnostic device and the target endpoint. In this case, the gateway (or the external diagnostic device) can generate a diagnostic initiation message indicating that a diagnostic operation is to be performed by the external diagnostic device (S802). The diagnostic initiation message can contain at least one information element from those listed in Table 2 above.

[0105] The gateway can broadcast the diagnostic initiation message (S803). The diagnostic initiation message can therefore be sent to all communication nodes belonging to the vehicle network. The internal diagnostic device can receive the diagnostic initiation message and verify (e.g., confirm) that the diagnostic operation of the external diagnostic device is to be carried out based on the received diagnostic initiation message. To prevent a collision between the diagnostic operation of the internal diagnostic device and the diagnostic operation of the external diagnostic device, the internal diagnostic device can then stop its diagnostic operation for the target end node (S804).

[0106] If the diagnostic process for the target terminal node is stopped, the internal diagnostic device can generate a diagnostic initiation message (S805). The diagnostic response message can indicate that the diagnostic process has been stopped by the internal diagnostic device. The diagnostic response message can contain at least one piece of information from the information elements listed in Table 4 above. The internal diagnostic device can send the diagnostic response message (S806). The diagnostic response message can be broadcast. The gateway (or external diagnostic device) can receive the diagnostic response message from the internal diagnostic device and can verify or acknowledge the information elements contained in the diagnostic response message.If a negative response message is not received in response to the diagnostic initiation message, or if the diagnostic response message is received by the internal diagnostic device, the external diagnostic device can perform its diagnostic operation.

[0107] The methods according to embodiments of the present invention / disclosure can be implemented as program instructions that are executable by a variety of computers and are stored on a computer-readable medium. The computer-readable medium can comprise a program instruction, a data file, a data structure, or a combination thereof. The program instructions stored on the computer-readable medium can be specifically designed and configured for the present invention or can be publicly known and accessible to those skilled in the art of computer software. Examples of the computer-readable medium can include a hardware device, such as ROM, RAM, and flash memory, specifically configured to store and execute the program instructions.Examples of program instructions include machine code, which is generated, for example, by a compiler, as well as code in higher-level programming languages, which can be executed by a computer using an interpreter. The exemplary hardware device described above can be configured to function as at least one software module to carry out the operation / execution of the present invention, and vice versa.

Claims

[1] Diagnostic procedure which is carried out by a gateway (600) in a vehicle network which has at least the gateway (600) and an internal diagnostic device as a plurality of communication nodes, comprising the diagnostic procedure: Sending (S703; S803), through the gateway (600), a diagnostic initiation message indicating that a diagnostic operation of an external diagnostic device (640) is to be carried out, in a broadcast manner upon detection that the external diagnostic device (640) is connected to the gateway (600), Received by the gateway (600), a negative response message (S707) as a response to the diagnostic initiation message from the internal diagnostic device, and Performing, through the gateway (600), the diagnostic procedure of the external diagnostic device (640) at a target endpoint that differs from a target endpoint specified in the negative response message, wherein the negative response message indicates that a diagnostic operation of the internal diagnostic device cannot be stopped, and the diagnostic initiation message contains at least one identifier of at least one communication node for which the diagnostic operation of the external diagnostic device (640) is to be performed, from the majority of communication nodes, and information indicating a start time of the diagnostic operation of the external diagnostic device (640). [2] Diagnostic method according to claim 1, wherein the diagnostic process of the external diagnostic device (640) is carried out after a time specified by the negative response message. [3] Diagnostic method according to any one of claims 1 to 2, wherein the negative response message includes an identifier of the target terminal node being examined by the diagnostic process of the internal diagnostic device from the plurality of communication nodes and information indicating a remaining time until the completion of the diagnostic process of the internal diagnostic device. [4] Diagnostic method according to claim 3, wherein the vehicle network comprises an Ethernet-based vehicle network and an ECU network (CAN)-based vehicle network, and the internal diagnostic device and the target end node specified in the negative response message belong to the Ethernet-based vehicle network. [5] Diagnostic method according to any one of claims 2 to 4, wherein the diagnostic process of the external diagnostic device (640) is carried out at the target end node specified in the negative response message after receiving a diagnostic response message indicating that the diagnostic process of the internal diagnostic device at the target end node specified in the negative response message has been completed. [6] Diagnostic method according to claim 5, wherein the diagnostic response message includes an identifier of the target terminal node examined by the diagnostic process of the internal diagnostic device, a type of the diagnostic process of the internal diagnostic device and a result of the diagnostic process of the internal diagnostic device. [7] Diagnostic procedure which is carried out by an internal diagnostic device in a vehicle network which has at least a gateway (600), the internal diagnostic device and a target terminal node as a plurality of communication nodes, comprising the diagnostic procedure: Performing, through the internal diagnostic device, a diagnostic operation of the internal diagnostic device (S701; S801) for the target terminal node from the plurality of communication nodes; Received by the internal diagnostic device, a diagnostic initiation message (S703; S803) which has an indicator indicating that a diagnostic operation of an external diagnostic device (640) is to be carried out, from the gateway (600) to which the external diagnostic device (640) is connected, from the plurality of communication nodes, wherein the diagnostic initiation message further includes: at least one identifier of at least one communication node for which the diagnostic process of the external diagnostic device (640) is to be carried out, of the plurality of communication nodes and information which specifies a start time of the diagnostic process of the external diagnostic device (640); Identify, using the internal diagnostic device, whether the at least one identifier is different from an identifier of the target terminal node, by comparing the at least one identifier with the identifier of the target terminal node; Comparing the start time of the diagnostic process of the external diagnostic device (640) and a completion time of the diagnostic process of the internal diagnostic device based on the identification; Determine (S704) whether to stop the diagnostic process of the internal diagnostic device, by the internal diagnostic device, based on a result of the comparison; and In response to a determination that the diagnostic process of the internal diagnostic device cannot be stopped, the internal diagnostic device sends (S706) a negative response message indicating that the diagnostic process of the internal diagnostic device cannot be stopped. [8] Diagnostic method according to claim 7, wherein the diagnostic process of the internal diagnostic device is carried out irrespective of the diagnostic process of the external diagnostic device (640) in response to a determination that the identifier of the target end node is different from the at least one identifier contained in the diagnostic initiation message, and wherein the negative response message (S706) is sent in response to a determination that the identifier of the target end node is identical to the at least one identifier contained in the diagnostic initiation message and the diagnostic process of the internal diagnostic device cannot be stopped. [9] Diagnostic method according to claim 7 or 8, wherein the diagnostic process of the internal diagnostic device is carried out irrespective of the diagnostic process of the external diagnostic device (640) in response to a determination that the completion time of the diagnostic process of the internal diagnostic device is before the start time of the diagnostic process of the external diagnostic device (640), which is specified by the diagnostic initiation message, and wherein the negative response message (S706) is sent in response to a determination that the completion time of the diagnostic process of the internal diagnostic device is after the start time of the diagnostic process of the external diagnostic device (640), which is specified by the diagnostic initiation message, and the diagnostic process of the internal diagnostic device cannot be stopped. [10] Diagnostic method according to any one of claims 7 to 9, wherein the negative response message includes the identifier of the target terminal node being examined by the diagnostic process of the internal diagnostic device and information indicating the remaining time until completion of the diagnostic process of the internal diagnostic device. [11] Diagnostic method according to any one of claims 7 to 10, wherein the vehicle network comprises an Ethernet-based vehicle network and an ECU network (CAN)-based vehicle network, and the internal diagnostic device and the target end node belong to the Ethernet-based vehicle network. [12] Diagnostic method according to any one of claims 7 to 11, further comprising sending, through the internal diagnostic device, a diagnostic response message (S709) indicating that the diagnostic process of the internal diagnostic device is complete when the diagnostic process of the internal diagnostic device is complete. [13] An internal diagnostic device in a vehicle network comprising the internal diagnostic device, a target terminal node and a gateway (600) as a plurality of communication nodes, wherein the internal diagnostic device comprises a processor and a memory which stores at least one instruction that is executed by the processor, wherein the at least one instruction is configured to: Performing a diagnostic procedure of the internal diagnostic device for the target terminal node from the majority of communication nodes; Receiving a diagnostic initiation message, which includes an indicator that a diagnostic operation of an external diagnostic device (640) is to be performed, from the gateway (600) to which the external diagnostic device (640) is connected, from the plurality of communication nodes, wherein the diagnostic initiation message further includes: at least one identifier of at least one communication node for which the diagnostic process of the external diagnostic device (640) is to be carried out, of the plurality of communication nodes and information which specifies a start time of the diagnostic process of the external diagnostic device (640); Identify, using the internal diagnostic device, whether the at least one identifier is different from an identifier of the target terminal node, by comparing the at least one identifier with the identifier of the target terminal node; Comparing a start time of the diagnostic process of the external diagnostic device (640) and a completion time of the diagnostic process of the internal diagnostic device based on the identification; Determine whether the diagnostic process of the internal diagnostic device should be stopped, based on a result of the comparison; and In response to a determination that the diagnostic process of the internal diagnostic device cannot be stopped, a negative response message is sent indicating that the diagnostic process of the internal diagnostic device cannot be stopped. [14] The internal diagnostic device according to claim 13, wherein the at least one instruction executed by the processor causes the processor to perform the diagnostic operation of the internal diagnostic device irrespective of the diagnostic operation of the external diagnostic device (640) in response to a determination that an identifier of the target terminal node is different from the at least one identifier contained in the diagnostic initiation message. [15] The internal diagnostic device according to claim 13 or 14, wherein the at least one instruction executed by the processor causes the processor to perform the diagnostic operation of the internal diagnostic device irrespective of the diagnostic operation of the external diagnostic device (640) in response to a determination that the completion time of the diagnostic operation of the internal diagnostic device is before the start time of the diagnostic operation of the external diagnostic device (640) specified by the diagnostic initiation message. [16] The internal diagnostic device according to any one of claims 13 to 15, wherein the negative response message includes the identifier of the target terminal node being examined by the diagnostic process of the internal diagnostic device and information indicating the remaining time until the completion of the diagnostic process of the internal diagnostic device. [17] The internal diagnostic device according to any one of claims 13 to 16, wherein the vehicle network comprises an Ethernet-based vehicle network and an ECU network (CAN)-based vehicle network, and the internal diagnostic device and the target end node belong to the Ethernet-based vehicle network.

Images