KR102300764B1 - Diagnostic methods and devices in vehicle network - Google Patents

Abstract

A diagnostic method performed by a gateway in a vehicle network is disclosed. The gateway includes a controller unit and a PHY (physical) layer unit that manages a connection state of the controller unit and ports, and is connected to the controller unit.
The diagnosis method may include: receiving, by the controller unit, a diagnosis request message from an external diagnosis device connected to a first port; receiving, by the controller unit, a security authentication request message from the external diagnostic device when security authentication is required for the diagnosis request message; verifying, by the controller unit, the security authentication request message; and activating, by the PHY layer unit, a port connected to a target communication node to be diagnosed from among the ports when the verification of the security authentication request message is completed, under the control of the controller unit.

Description

DIAGNOSTIC METHOD AND DEVICES IN VEHICLE NETWORK

The present invention relates to vehicle network technology, and to a diagnostic method and apparatus for an Ethernet-based vehicle network.

2. Description of the Related Art As electronic components for vehicles are rapidly becoming electronic, the types and numbers of electronic devices (eg, electronic control units (ECUs)) mounted on vehicles are greatly increased. The electronic device may be largely used in a power train control system, a body control system, a chassis control system, a vehicle network, a multimedia system, and the like. The powertrain control system may refer to an engine control system, an automatic shift control system, or the like. The body control system may refer to a body electronic device control system, a convenience device control system, a lamp control system, and the like. The chassis control system may mean a steering system control system, a brake control system, a suspension control system, or the like. The vehicle network may mean a controller area network (CAN), a FlexRay-based network, a media oriented system transport (MOST)-based network, and the like. The multimedia system may refer to a navigation device system, a telematics system, an infotainment system, or the like.

These systems and electronic devices constituting each of the systems are connected through a vehicle network, and a vehicle network for supporting each function of the electronic devices is required. CAN can support a transmission rate of up to 1 Mbps, and can support automatic retransmission of collided frames and error detection based on cycle redundancy check (CRC). A FlexRay-based network can support a transmission speed of up to 10 Mbps, and can support simultaneous data transmission through two channels, synchronous data transmission, and the like. The MOST-based network is a communication network for high-quality multimedia and can support a transmission rate of up to 150Mbps.

On the other hand, vehicle telematics systems, infotainment systems, and improved safety systems require high transmission speed and system scalability, and CAN and FlexRay-based networks do not sufficiently support them. A MOST-based network can support a higher transmission speed compared to a CAN and FlexRay-based network, but it consumes a lot of cost to apply the MOST-based network to all networks of a vehicle. Due to these problems, an Ethernet-based network may be considered as a vehicle network. An Ethernet-based network can support bidirectional communication through a pair of windings, and can support transmission rates of up to 10 Gbps.

As the application of Ethernet-based vehicle networks expands, a diagnosis method different from the existing bus (BUS) type vehicle diagnosis method is required. In the Ethernet-based vehicle network, since the PHY layer unit can switch the connection of ports, a corresponding diagnostic method is required. In addition, a technology capable of maintaining vehicle security in a diagnostic method through Ethernet is required.

An object of the present invention to solve the above problems is to provide a diagnostic method and apparatus for an Ethernet-based vehicle network.

The gateway of the vehicle network according to the first embodiment of the present invention for achieving the above object includes a controller unit and a PHY (physical) layer unit connected to the controller unit and managing the connection state of ports,

The diagnostic method performed by the gateway may include: receiving, by the controller unit, a diagnostic request message from an external diagnostic device connected to a first port; receiving, by the controller unit, a security authentication request message from the external diagnostic device when security authentication is required for the diagnosis request message; verifying, by the controller unit, the security authentication request message; and when the verification of the security authentication request message is completed, activating, by the PHY layer unit, a port connected to a target communication node to be diagnosed among the ports under the control of the controller unit.

Here, when security authentication is not required for the diagnosis request message, the PHY layer unit may transmit the diagnosis request message to the target communication node without transmitting the diagnosis message to the controller unit.

Here, if the verification of the security authentication request message fails, the controller unit may end the diagnosis procedure and may not allow communication between the external diagnosis device 10 and the in-vehicle communication node.

Here, the diagnosis request message includes information on the name or function of the target communication node to be diagnosed,

The diagnosis method may further include, by the controller unit, determining at least one of an Ethernet MAC address and an Ethernet IP address of the target communication node from information on the name or function of the target communication node.

Here, the diagnosis method further includes: when the verification of the security authentication request message is completed, transmitting, by the controller unit, security authentication information for the external diagnostic device to the target communication node.

Here, the receiving of the security authentication request message may include receiving information on the service time of the external diagnostic device together.

Here, the diagnosis method may include, when the service time is over, the PHY layer unit inactivating a port connected to the target communication node under the control of the controller unit.

Here, in the diagnosis method, when the service time is over, the PHY layer unit may transmit a message excluding monitoring for the target communication node to the controller unit.

Here, the diagnostic method includes: receiving, by the PHY layer unit, a diagnostic response message from the target communication node; and

The method may further include, by the PHY layer unit, transmitting the diagnosis response message to the external diagnostic unit in a port forwarding manner under the control of the controller unit.

Here, the vehicle network includes an Ethernet-based vehicle network and a controller area network (CAN)-based vehicle network, and the target communication node may belong to the Ethernet-based vehicle network.

The gateway of the vehicle network according to the second embodiment of the present invention includes a controller unit and a PHY (physical) layer unit connected to the controller unit and managing the connection state of ports,

The gateway includes a controller unit and PHY (physical) layer units connected to the controller unit and managing the connection state of ports,

The diagnostic method may include: receiving, by the PHY layer unit, a use request message of the vehicle network from an external diagnostic device connected to a first port; determining, by the controller unit, whether the vehicle is in a stationary state; when the vehicle is stationary, setting, by the controller unit, port mirroring of the PHY layer unit such that a message received from the external diagnostic device is mirrored to a target communication node; receiving, by the PHY layer unit, a diagnostic request message from the external diagnostic device; and transmitting, by the PHY layer unit, the diagnosis request message to the target communication node by mirroring.

Here, in the step of receiving the diagnosis request message, the PHY layer unit may receive information about the service time together.

Here, the diagnosis method may include, when the service time is over, the PHY layer unit inactivating a port connected to the target communication node.

Here, the diagnostic method includes: receiving, by the PHY layer unit, a diagnostic response message from the target communication node; and transmitting, by the PHY layer unit, the diagnostic response message to the external diagnostic device.

Here, when the vehicle is not in a stationary state, the diagnosis method includes: receiving, by the PHY layer unit, a diagnosis request message including a unicast address indicating the target communication node from the external diagnosis device; determining, by the controller unit, a port ID to which the diagnosis request message is to be delivered from a unicast address indicating the target communication node; and forwarding the diagnosis request message through the port corresponding to the port ID by the PHY layer unit under the control of the controller unit.

Here, the diagnostic method includes: receiving, by the PHY layer unit, a diagnostic response message including a unicast address indicating the external diagnostic device from the target communication node; determining, by the controller unit, a port ID to which the diagnosis request message is to be transmitted from a unicast address indicating the external diagnosis device; and forwarding, by the PHY layer unit, the diagnostic response message through a port corresponding to the port ID under the control of the controller unit.

A gateway of a vehicle network according to a third embodiment of the present invention includes: a controller unit; and a PHY (physical) layer unit connected to the controller unit and managing the connection state of ports.

the controller unit receives a diagnosis request message from an external diagnosis device connected to the first port; receiving a security authentication request message from the external diagnostic device when security authentication is required for the diagnosis request message; Verifies the security authentication request message,

When the verification of the security authentication request message is completed, the PHY layer unit may activate a port connected to a target communication node to be diagnosed among the ports under the control of the controller unit.

Here, when security authentication is not required for the diagnosis message, the PHY layer unit may transmit the diagnosis request message to the target communication node without transmitting the diagnosis message to the controller unit.

Here, the diagnosis request message includes information on the name or function of the target communication node to be diagnosed,

The controller unit may determine at least one of an Ethernet MAC address and an Ethernet IP address of the target communication node from information on the name or function of the target communication node.

Here, when verification of the security authentication request message is completed, the controller unit may transmit security authentication information for the external diagnostic device to the target communication node.

Here, the controller unit may receive information on the service time of the external diagnostic device, and when the service time is over, the PHY layer unit may inactivate a port connected to the target communication node under the control of the controller unit. have.

According to the present invention, while the external diagnostic device performs diagnosis on the vehicle network, the gateway manages the connection status of ports, so that message exchange between the external diagnostic device and the target communication node can be performed. A message may be selectively delivered to a target communication node or an external diagnostic device during a diagnosis process by port mirroring, a forwarding method, or the like. In addition, security can be strengthened in the diagnostic procedure by enabling or disabling the connection of ports by the gateway in consideration of the security range and service time.

1 is a block diagram illustrating a first embodiment of a network topology of a vehicle network;
2 is a block diagram illustrating a first embodiment of a communication node constituting a vehicle network.
3 is a block diagram illustrating a second embodiment of a communication node constituting a vehicle network.
4 is a block diagram illustrating a first embodiment of a protocol structure of a communication node constituting a vehicle network.
5 is a conceptual diagram illustrating a gateway included in a vehicle network.
6 is a conceptual diagram illustrating a process in which a diagnosis request message is transmitted from an external diagnostic device to a target communication node according to a first embodiment.
7 is a conceptual diagram illustrating a second embodiment of a process in which a diagnosis request message is transmitted from the external diagnostic device 10 to a target communication node.
8 is a flowchart illustrating a first embodiment of a method for diagnosing a vehicle.
9 is a flowchart illustrating a second embodiment of a method for diagnosing a vehicle.
10 is a flowchart illustrating a second embodiment of a method for diagnosing a vehicle.

Since the present invention can have various changes and can have various embodiments, specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and it should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention.

Terms such as first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.

When a component is referred to as being “connected” or “connected” to another component, it is understood that the other component may be directly connected or connected to the other component, but other components may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that no other element is present in the middle.

The terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present application, terms such as “comprise” or “have” are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the accompanying drawings. In describing the present invention, in order to facilitate the overall understanding, the same reference numerals are used for the same components in the drawings, and duplicate descriptions of the same components are omitted.

1 is a block diagram illustrating a first embodiment of a network topology of a vehicle network;

Referring to FIG. 1 , a communication node constituting a vehicle network may mean a gateway, a switch (or a bridge), an end node, or the like. The gateway 100 may be connected to at least one switch 110 , 110 - 1 , 110 - 2 , 120 , and 130 , and may connect different networks. For example, the gateway 100 is a communication node supporting a controller area network (CAN) (or FlexRay, media oriented system transport (MOST), local interconnect network (LIN), etc.) protocol and Ethernet (ethernet). ) can be connected between switches that support the protocol. Each of the switches 110 , 110 - 1 , 110 - 2 , 120 , and 130 may be connected to at least one end node 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , and 133 . Each of the switches 110, 110-1, 110-2, 120, and 130 may interconnect the end nodes 111, 112, 113, 121, 122, 123, 131, 132, 133, and an end connected thereto The nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 and 133 may be controlled.

The end nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , and 133 may refer to electronic control units (ECUs) that control various devices included in the vehicle. For example, the end nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , 133 may be an infotainment device (eg, a display device, a navigation device, an around view). It may mean an ECU constituting an around view monitoring device).

On the other hand, communication nodes (ie, gateways, switches, end nodes, etc.) constituting the vehicle network include a star topology, a bus topology, a ring topology, a tree topology, and a mesh. It can be connected by topology or the like. In addition, each of the communication nodes constituting the vehicle network may support a CAN protocol, a FlexRay protocol, a MOST protocol, a LIN protocol, an Ethernet protocol, and the like. Embodiments according to the present invention may be applied to the network topology described above, and the network topology to which embodiments according to the present invention are applied is not limited thereto and may be configured in various ways.

2 is a block diagram illustrating a first embodiment of a communication node constituting a vehicle network.

Referring to FIG. 2 , the communication node 200 constituting the network may include a PHY layer unit 210 and a controller unit 220 . The controller unit 220 may be implemented by including a medium access control (MAC) layer. The PHY layer unit 210 may receive signals from, or transmit signals to, other communication nodes. The controller unit 220 may control the PHY layer unit 210 and may perform various functions (eg, an infotainment function, etc.). The PHY layer unit 210 and the controller unit 220 may be implemented as one SoC (System on Chip) or may be configured as separate chips.

The PHY layer unit 210 and the controller unit 220 may be connected through a media independent interface (MII) 230 . The MII 230 may mean an interface defined in IEEE 802.3, and may be composed of a data interface and a management interface between the PHY layer unit 210 and the controller unit 220 . Instead of the MII 230 , one of reduced MII (RMII), gigabit MII (GMII), reduced GMII (RGMII), serial GMII (SGMII), and XGMII (10 GMII) interfaces may be used instead of the MII 230 . The data interface may include a transmit channel and a receive channel, and each of the channels may have an independent clock, data, and control signal. The management interface may be configured as a two-signal interface, one signal for the clock and the other signal for data.

The PHY layer unit 210 may include a PHY layer interface unit 211 , a PHY layer processor 212 , and a PHY layer memory 213 . The configuration of the PHY layer unit 210 is not limited thereto, and the PHY layer unit 210 may be configured in various ways. The PHY layer interface unit 211 may transmit a signal received from the controller unit 220 to the PHY layer processor 212 , and may transmit a signal received from the PHY layer processor 212 to the controller unit 220 . The PHY layer processor 212 may control the operation of each of the PHY layer interface unit 211 and the PHY layer memory 213 . The PHY layer processor 212 may perform modulation of a signal to be transmitted or demodulation of a received signal. The PHY layer processor 212 may control the PHY layer memory 213 to input or output a signal. The PHY layer memory 213 may store the received signal, and may output the stored signal according to the request of the PHY layer processor 212 .

The controller unit 220 may perform monitoring and control for the PHY layer unit 210 through the MII 230 . The controller unit 220 may include a controller interface unit 221 , a controller processor 222 , a main memory 223 , and an auxiliary memory 224 . The configuration of the controller unit 220 is not limited thereto, and the controller unit 220 may be configured in various ways. The controller interface unit 221 may receive a signal from the PHY layer unit 210 (ie, the PHY layer interface unit 211 ) or an upper layer (not shown), and transmit the received signal to the controller processor 222 . and may transmit a signal received from the controller processor 222 to the PHY layer unit 210 or an upper layer. The controller processor 222 may further include independent memory control logic or integrated memory control logic for controlling the controller interface unit 221 , the main memory 223 and the auxiliary memory 224 . The memory control logic may be implemented by being included in the main memory 223 and the auxiliary memory 224 , or may be implemented by being included in the controller processor 222 .

Each of the main memory 223 and the auxiliary memory 224 may store a signal processed by the controller processor 222 , and may output the stored signal according to a request of the controller processor 222 . The main memory 223 may refer to a volatile memory (eg, random access memory (RAM)) that temporarily stores data required for the operation of the controller processor 222 . The auxiliary memory 224 includes operating system code (eg, a kernel and a device driver) and an application program code for performing a function of the controller unit 220 , etc. This may mean a non-volatile memory in which it is stored. A flash memory having a fast processing speed may be used as the non-volatile memory, or a hard disk drive (HDD), compact disc-read only memory (CD-ROM), etc. for storing a large amount of data this can be used The controller processor 222 may typically be configured as a logic circuit including at least one processing core. As the controller processor 222 , an ARM (Advanced RISC Machines Ltd.)-based core, an atom-based core, or the like may be used.

Meanwhile, the PHY layer unit 210 (ie, the PHY layer processor 212 ) may operate in a sleep mode, a normal mode (eg, an active mode), and the like. The PHY layer unit 210 may transition from the sleep mode to the normal mode based on the control of the controller processor 222 , and may transition from the normal mode to the sleep mode. The controller unit 220 (eg, the controller processor 222 ) may operate in a power off mode, a sleep mode, a normal mode, and the like. The controller unit 220 may transition from a power off mode to a sleep mode or a normal mode, may transition from a sleep mode to a power off mode or a normal mode, and may transition from a normal mode to a power off mode or a sleep mode. .

Here, the power off mode may mean a state in which power is not supplied to a corresponding entity (eg, the controller unit 220 ). The sleep mode may mean a state in which the minimum power for basic operation is supplied to the corresponding entity (eg, the PHY layer unit 210, the controller unit 220, etc.) (ie, a power saving state). can The normal mode may mean a state (eg, wake-up state) in which power is normally supplied to a corresponding entity (eg, PHY layer unit 210, controller unit 220, etc.). .

3 is a block diagram illustrating a second embodiment of a communication node constituting a vehicle network.

Referring to FIG. 3 , the communication node 200 may include a controller unit 220 and may further include a regulator (not shown) for supplying power. The controller unit 220 may be connected to the PHY layer unit 210 located outside the communication node 200 , and may control the PHY layer unit 210 . Each of the functions of the PHY layer unit 210 and the controller unit 220 shown in FIG. 3 may be the same as or similar to the functions of the PHY layer unit 210 and the controller unit 220 shown in FIG. 2 .

The PHY layer unit 210 may be connected to the controller unit 220 through a media independent interface 230 . The MII 230 may mean an interface defined in IEEE 802.3, and may be composed of a data interface and a management interface between the PHY layer unit 210 and the controller unit 220 . Instead of the MII 230 , one interface among RMII, GMII, RGMII, SGMII, and XGMII may be used. The data interface may include a transmit channel and a receive channel, and each of the channels may have an independent clock, data, and signal. The management interface may be configured as a two-signal interface, one signal for the clock and the other signal for data.

Meanwhile, the protocol structure of the communication node shown in FIGS. 1 to 3 may be as follows.

4 is a block diagram illustrating a first embodiment of a protocol structure of a communication node constituting a vehicle network.

Referring to FIG. 4 , the communication node may include layers 1 to 7 . Layer 1 of the communication node may support the PHY function and may support a transmission rate of 100 Mbps (megabit per second). Layer 2 of the communication node may support IEEE 802.1Q protocol, IEEE 802.1p protocol, IEEE 802.3 protocol, audio video bridging (AVB) protocol (eg, IEEE 802.1Qav protocol, IEEE 802.1Qat protocol), and the like. Layer 3 of the communication node may support internet protocol version 4 (IPv4), address resolution protocol (ARP), internet control message protocol version 4 (ICMPv4), IEEE 802.1AS, IEEE 1722, and the like. Layer 4 of the communication node may support transfer control protocol (TCP), user datagram protocol (UDP), IEEE 802.1AS, IEEE 1722, and the like. Layers 5 to 7 of the communication node may support diagnostics over internet protocol (DoIP), EthCC protocol, dynamic host configuration protocol (DHCP), SD protocol, network management (NM) protocol, IEEE 802.1AS, IEEE 1722, and the like.

The communication node described above may operate in a sleep mode or a normal mode. In the sleep mode, the PHY layer unit of the communication node may be in an enabled state, and the controller unit of the communication node may be in a disabled state. Alternatively, in the sleep mode, the PHY layer unit and the controller unit of the communication node may be in a disabled state. In the normal mode, the PHY layer unit and the controller unit of the communication node may be in an enabled state. That is, the normal mode may indicate a state in which the communication node is woken up. When a wakeup signal is received or a specific event is detected, the operation mode of the communication node may transition from the sleep mode to the normal mode. In this case, a system booting procedure of the communication node may be performed. The system booting procedure of the communication node may be performed as follows.

5 is a conceptual diagram illustrating a gateway 500 included in a vehicle network.

Referring to FIG. 5 , the gateway 500 may include a controller unit 510 and a PHY layer unit 520 . The controller unit 510 may be configured as a logic circuit including at least one processing core.

The gateway 500 may be connected to a CAN-based vehicle network. The gateway 500 may include a plurality of CAN communication channels 530 . The CAN communication channel 530 may be connected to the controller unit 510 . The gateway 500 may send and receive signals to and from a communication node belonging to the CAN-based vehicle network through the CAN communication channel 530 .

The gateway 500 may include a plurality of ports P1, P2, P3, P4, and P5. The first port P1 may be connected to the external diagnostic device 10 . The second to fifth ports P2, P3, P4, and P5 may be connected to communication nodes belonging to an Ethernet-based vehicle network. The gateway 500 may receive a message transmitted from the external diagnostic device 10 through the first port P1 . The PHY layer unit 520 may manage the connection state of the ports P1, P2, P3, P4, and P5. The PHY layer unit 520 may activate or deactivate the connection of the ports P1, P2, P3, P4, and P5. Signals may not be transmitted through a disabled port.

The gateway 500 may relay communication between the external diagnostic device 10 and a communication node belonging to the vehicle network. The external diagnostic device 10 may perform a diagnostic procedure on a communication node belonging to the vehicle network through the gateway 500 . The diagnostic procedure may be divided into four sessions. For example, the diagnostic procedure may be performed according to any one of a default session, an extended session, a security session, and a dedicated session. Some of the diagnostic procedures in the main session may not require security. The permitted range of information exchange in the basic procedure may be determined by laws and regulations.

When the external diagnostic device 10 intends to diagnose an in-vehicle electronic device, the external diagnostic device 10 may transmit a diagnosis request message to the gateway 500 . The PHY layer unit 520 may receive the diagnosis request message through the first port P1. The delivery process of the diagnosis request message may vary depending on the diagnosis range required by the diagnosis request message.

6 is a conceptual diagram illustrating a process in which a diagnosis request message is transmitted from the external diagnostic device 10 to the target communication node 600 according to the first embodiment.

Referring to FIG. 6 , when security verification is not required for the diagnosis request message, the diagnosis request message may be directly transmitted to the target communication node 600 without going through the controller unit 510 of the gateway 500 . For example, when the external diagnostic device 10 transmits a diagnosis request message requesting diagnosis within a range that does not require security, the diagnosis request message may not be transmitted to the controller unit 510 . The PHY layer unit 520 may determine whether security is required for the diagnosis request message from information included in a preamble of the diagnosis request message.

The target communication node 600 may be a communication node to be diagnosed. The target communication node 600 may belong to the Ethernet-based vehicle network 30 . The target communication node 600 may be an electric control unit (ECU) or an end node of a vehicle network. The target communication node 600 may include a controller layer unit 610 and a PHY layer unit 620 . However, in some cases, the target communication node 600 may not include the controller unit 610 . The target communication node 600 may communicate with the gateway 500 through the sixth port P6 . The PHY layer unit 620 of the target communication node 600 may manage connection states of ports included in the target communication node 600 . For example, when the PHY layer unit 620 deactivates the sixth port P6 , communication between the gateway 500 and the target communication node 600 may be restricted.

If security is not required for the diagnosis request message, the PHY layer unit 520 may not deliver the diagnosis request message to the controller unit 510 . The PHY layer unit 520 may transmit the diagnosis request message to the target communication node 600 through the second port P2 connected to the target communication node 600 . When there are a plurality of target communication nodes to be diagnosed, the PHY layer unit 620 may transmit a diagnostic request message through a plurality of ports. As another example, the PHY layer unit 620 may transmit a diagnosis request message through all ports P2, P3, P4, and P5 as well as the second port P2 to which the target communication node 600 is connected.

The embodiment described with reference to FIG. 6 may be applied when the diagnosis of the vehicle is performed according to the basic session. However, the embodiment is not limited thereto. For example, the embodiment shown in FIG. 6 may be applied to an extended session, a secure session, a dedicated session, and the like.

7 is a conceptual diagram illustrating a second embodiment of a process in which a diagnosis request message is transmitted from the external diagnostic device 10 to the target communication node 600 .

Referring to FIG. 7 , when security verification is required for the diagnosis request message, the PHY layer unit 520 may transmit the diagnosis request message to the controller unit 510 . The controller unit 510 may perform a security verification procedure. The controller unit 510 may receive the security authentication request message from the external diagnostic device 10 and verify the security authentication request message.

8 is a flowchart illustrating a first embodiment of a method for diagnosing a vehicle.

The vehicle diagnosis method illustrated in FIG. 8 may be applied to a basic session. However, the embodiment is not limited thereto. For example, the vehicle diagnosis method shown in FIG. 8 may be applied to an extended session, a secure session, and a dedicated session.

Referring to FIG. 8 , in step S810 , the external diagnostic device 10 may transmit a diagnostic request message through the first port P1 . The PHY layer unit 520 may receive the diagnostic request message. When security verification is required for the diagnosis request message, the PHY layer unit 520 may not directly transmit the diagnosis request message to the target communication node 600 . The PHY layer unit 520 may transmit a diagnosis request message to the controller unit 510 .

In step S812 , the controller unit 510 may determine the Ethernet MAC address or Ethernet IP address of the target communication node to be diagnosed from the diagnosis request message. The external diagnostic device 10 may include the name of the target communication node 600 or information on a function performed by the target communication node 600 in the diagnosis request message. The controller unit 510 may know in advance the Ethernet MAC address or Ethernet IP address of the communication node matching the name or function of the communication node in the vehicle. The controller unit 510 may determine the Ethernet MAC address or Ethernet IP address of the target communication node 600 by using pre-stored matching information from the name or function of the target communication node 600 included in the diagnosis request message.

In step S820 , the external diagnostic device 10 may transmit a security authentication request message. The external diagnostic device 10 may transmit the security authentication request message and service time information together. The service time may be information about a time at which a diagnosis service is performed. The controller unit 510 may receive the security authentication request message and service time information through the PHY layer unit 520 .

In step S822, the controller unit 510 may perform verification of the security authentication request message. The controller unit 510 may determine whether the diagnosis performed by the external diagnostic device 10 is within a permitted security range by verifying the security authentication request message. When the verification of the security authentication request message fails, the controller unit 510 may end the diagnosis procedure and may not allow communication between the external diagnosis device 10 and the in-vehicle communication node.

In step S824 , when verification of the security authentication request message is completed, the PHY layer unit 520 may transmit security authentication information for the external diagnostic device 10 to the target communication node 600 . The controller unit 510 may determine which port is connected to the target communication node 600 from the Ethernet MAC address or Ethernet IP address of the target communication node 600 determined in step S812 . The controller unit 510 may inform the PHY layer unit 520 of port information connected to the target communication node 600 . The PHY layer unit 520 may transmit the security authentication information to the target communication node 600 through the second port P2 .

In step S830 , when verification of the security authentication request message is completed, the controller unit 510 may transmit a control command to the PHY layer unit 520 . The PHY layer unit 520 may activate the second port P2 connected to the target communication node 600 under the control of the controller unit 510 .

In step S832 , the target communication node 600 may receive security authentication information from the gateway 500 . The controller unit 610 of the target communication node 600 may transmit a control command to the PHY layer unit 620 . The PHY layer unit 620 may activate the sixth port P6 connected to the gateway 500 under the control of the controller unit 610 . As the second port P2 and the sixth port P6 are activated, communication between the external diagnostic device 10 and the target communication node 600 may be allowed.

In step S840 , the target communication node 600 may perform a diagnostic function. The target communication node 600 may extract diagnostic information requested by the external diagnostic device 10 . The target communication node 600 may generate a diagnosis response message based on the diagnosis information.

In step S850, the target communication node 600 may transmit a diagnosis response message. The gateway 500 may receive a diagnostic response message through the second port P2 . The controller unit 510 may configure the PHY layer unit 510 so that the diagnostic response message received through the second port P2 is forwarded through the first port P1 . When port forwarding is set, the diagnostic response message may be transmitted to the external diagnostic device 10 without going through the controller layer unit 510 .

In step S860 , the PHY layer unit 520 may transmit a diagnostic response message to the external diagnostic device 10 in a port forwarding manner under the control of the controller unit 510 . The PHY layer unit 520 may forward the diagnostic response message through the first port P1 to which the external diagnostic device 10 is connected.

In step S870 , when the service time is over, the controller unit 510 may limit the diagnostic service by changing the setting of the PHY layer unit 520 . For example, the controller unit 510 may change the setting of the PHY layer unit 520 so that the second port P2 to which the target communication node 600 is connected is deactivated. The PHY layer unit 520 may inactivate the second port P2 or the second to fifth ports P2, P3, P4, and P5 under the control of the controller unit 510 . As another example, the controller unit 510 may change the setting of the PHY layer unit 520 so that the first port P1 to which the external diagnostic device 10 is connected is deactivated. The PHY layer unit 520 may deactivate the first port P1 under the control of the controller unit 510 . As another example, as another example, the controller unit 510 may change the setting of the PHY layer unit 520 so that all ports of the gateway 500 are deactivated. The PHY layer unit 520 may inactivate the first to fifth ports P1 , P2 , P3 , P4 , and P5 under the control of the controller unit 510 . By the operations of the controller unit 510 and the PHY layer unit 520 described above, when the service time is over, the port forwarding setting may be released. In addition, message exchange between the external diagnostic device 10 and the target communication node 600 may be restricted.

In the above description, a case has been described in which the PHY layer unit 520 deactivates at least one of the ports in order to limit the diagnostic service. However, the embodiment is not limited thereto. For example, the PHY layer unit 520 may block diagnostic services while keeping the pods active. In this case, under the control of the controller unit 510 , the PHY layer unit 520 may not transmit the message received from the external diagnostic device 10 through other ports. Also, the message received from the target communication node 600 may not be delivered to the external diagnostic device 10 .

As another example, in step S870 , when the service time is over, the controller unit 510 may partially limit the diagnostic service. For example, the controller unit 510 may configure the PHY layer unit 520 so that a message excluding monitoring for the target communication node 600 is transmitted to the controller unit 510 . The PHY layer unit 520 may deliver a message except for monitoring to the controller unit 510 without directly forwarding it in the port forwarding method. The controller unit 510 may determine whether the message is delivered. The controller unit 510 may not allow the PHY layer unit 520 to forward the message if it determines that the message delivery is inappropriate. In this case, communication between the external diagnostic device 10 and the target communication node 600 may be partially restricted. The controller unit 510 may prevent the external diagnostic device 10 from accessing the target communication node 600 unrestrictedly.

9 is a flowchart illustrating a second embodiment of a method for diagnosing a vehicle.

The vehicle diagnosis method illustrated in FIG. 9 may be applied to sessions other than the basic session. However, the embodiment is not limited thereto. For example, the vehicle diagnosis method shown in FIG. 9 may be applied to a basic session as well.

Referring to FIG. 9 , in step S910 , the external diagnostic device 10 may transmit a communication authentication request message for communication with the vehicle network. The PHY layer unit 520 may receive the communication authentication request message through the first port (P1). The communication authentication request message may include identification information of the external diagnostic device 10 and information on a diagnostic range of the external diagnostic device 10 . The PHY layer unit 520 may transmit a communication authentication request message to the controller unit 510 .

In step S920 , the controller unit 510 may verify the communication authentication request message. The controller unit 510 may determine whether the diagnostic range of the external diagnostic device 10 falls within a security allowable range. When determining that the diagnostic range of the external diagnostic device 10 is not permitted, the controller unit 510 may end the diagnostic procedure.

In step S930 , when communication authentication for the external diagnostic device 10 is completed, the external diagnostic device 10 may transmit a vehicle network use request message. The PHY layer unit 520 may receive the vehicle network use request message through the first port P1. The PHY layer unit 520 may transmit the vehicle network use request message to the controller unit 510 .

In operation S940 , the controller unit 510 may determine whether the vehicle is in a stopped state after receiving the vehicle network use request message. The controller unit 510 may determine whether the vehicle is in a stopped state based on vehicle speed, gear information, vehicle location information, and the like. When the vehicle speed is measured as 0 km/h, the controller unit 510 may determine that the vehicle is in a stopped state. When the gear is in the parked state, the controller unit 510 may determine that the vehicle is in a stopped state. The controller unit 510 may determine that the vehicle is in a stationary state when the location of the vehicle confirmed from the GPS location signal does not change.

In step S950 , when it is determined that the vehicle is in a stopped state, the controller unit 510 may configure the PHY layer unit so that the PHY layer unit performs port mirroring. The controller unit 510 may cause a message received from the external diagnostic device 10 to be mirrored to the target communication node 600 . The controller unit 510 may receive the diagnosis request message and configure the PHY layer unit 520 so that the message received from the first port P1 is mirrored to the second port P2 . The controller unit 510 may set the destination of the message received from the first port P1 as the second port P2 .

The controller unit 510 may set up mirroring from the external diagnostic device 10 toward the Ethernet-based communication nodes connected to the gateway 500 . The controller unit 510 may limit mirroring from the Ethernet-based communication nodes connected to the gateway 500 toward the external diagnostic device 10 . Accordingly, the message transmitted by the target communication node 600 may not be mirrored.

The PHY layer unit 520 does not forward the message received through the first port P1 to the controller unit 510, but can be transferred to the target communication node 600 through the second port P2 by a mirroring operation. have.

Although the case in which the destination port of port mirroring is set to one of the second ports P2 has been described, the embodiment is not limited thereto. For example, when there are a plurality of target communication nodes, a message received through the first port P1 may be mirrored to be transmitted through the plurality of ports.

In step S960 , the external diagnostic device 10 may transmit a diagnostic request message. The external diagnostic device 10 may transmit service time information together. The PHY layer unit 520 may transmit the service time information to the controller unit 510 .

In step S962 , the PHY layer unit 520 may transmit the diagnostic request message to the target communication node 600 through the second port P2 by mirroring. The PHY layer unit 520 may transmit a diagnostic request message to a plurality of communication nodes through a plurality of ports.

In step S970 , the target communication node 600 may perform a diagnostic function. The target communication node 600 may extract diagnostic information requested by the external diagnostic device 10 . The target communication node 600 may generate a diagnosis response message based on the diagnosis information.

In step S980 , the target communication node 600 may transmit a diagnostic response message. The gateway 500 may receive a diagnostic response message through the second port P2 . The controller unit 510 may configure the PHY layer unit 520 so that the diagnostic response message received through the second port P2 is forwarded through the first port P1 .

In step S982 , the PHY layer unit 520 may forward the diagnostic response message to the external diagnostic device 10 through the first port P1 .

In step S990 , when the service time is over, the controller unit 510 may inactivate the second port P2 connected to the target communication node 600 by changing the setting of the PHY layer unit 520 . As another example, the controller unit 510 may configure the PHY layer unit 520 so that the second to fifth ports P2, P3, P4, and P5 are deactivated. The controller unit 510 may configure the PHY layer unit 520 such that the first to fifth ports P1, P2, P3, P4, and P5 are deactivated.

By the operation of the controller unit 510 and the PHY layer unit 520 , when the service time is over, port mirroring and message forwarding may be stopped. In addition, message exchange between the external diagnostic device 10 and the target communication node 600 may be restricted.

10 is a flowchart illustrating a second embodiment of a method for diagnosing a vehicle.

In the description of the embodiment of FIG. 10 , contents overlapping those of FIG. 9 will be omitted. The vehicle diagnosis method illustrated in FIG. 10 may be applied to sessions other than the basic session. However, the embodiment is not limited thereto. For example, the vehicle diagnosis method shown in FIG. 10 may be applied to a basic session as well.

Referring to FIG. 10 , in step S1040 , the controller unit 510 may determine whether the vehicle is in a stopped state.

In step S1042 , if the vehicle is not in a stationary state, the controller unit 510 may transmit a one-side forwarding request message through the PHY layer unit 520 . The target communication node 600 and the external diagnostic device 10 may receive the one-side forwarding request message. The target communication node 600 and the external diagnostic device 10 may include a unicast address in a message generated after receiving the one-side forwarding request message. The target communication node 600 and the external diagnostic device 10 may set the destination of the message to one communication node. Accordingly, the message transmitted by the external diagnostic device 10 may be transmitted to one target communication node 600 . The unicast address may include information for identifying a port to which a communication node that is a destination of a message is connected.

In step S1050 , the external diagnostic device 10 may transmit a diagnosis request message and service time information. The diagnosis request message may include a unicast address indicating the target communication node 600 . The PHY layer unit 520 may receive the diagnosis request message and service time information. The PHY layer unit 520 may transmit the diagnosis request message and service time information to the controller unit 510 . The controller unit 510 may determine the port ID of the second port P2 to which the target communication node 600 that is the destination of the message is connected from the unicast address included in the diagnosis request message.

For example, the unicast address may include an index key capable of identifying the destination of the message. The controller unit 510 may determine the communication node that matches the index key, and may determine the port ID to which the message will be forwarded. The controller unit 510 may determine a port ID of a port to which the diagnosis request message is transmitted from the unicast address included in the diagnosis request message.

In step S1052 , the PHY layer unit 520 may forward the diagnosis request message through the second port P2 under the control of the controller unit 510 .

In step S1060, the target communication node 600 may perform a diagnostic function. The target communication node 600 may extract diagnostic information requested by the external diagnostic device 10 . The target communication node 600 may generate a diagnosis response message based on the diagnosis information.

In step S1070 , the target communication node 600 may transmit a diagnostic response message. The diagnostic response message may include a unicast address indicating the external diagnostic device 10 . The unicast address may include an index key for identifying the external diagnostic device 10 . The controller unit 510 may determine the port ID of the port through which the diagnostic response message is to be transmitted from the index key.

In step S1072 , the PHY layer unit 520 may forward the diagnostic response message through the first port P1 under the control of the controller unit 510 .

In step S1080 , when the service time is over, the controller unit 510 may inactivate the second port P2 connected to the target communication node 600 by changing the setting of the PHY layer unit 520 . As another example, the controller unit 510 may configure the PHY layer unit 520 to deactivate the second to fifth ports P2, P3, P4, and P5. The controller unit 510 may configure the PHY layer unit 520 such that the first to fifth ports P1, P2, P3, P4, and P5 are deactivated.

By the operation of the controller unit 510 and the PHY layer unit 520, when the service time is over, one-side forwarding may be stopped. In addition, message exchange between the external diagnostic device 10 and the target communication node 600 may be restricted.

A gateway and a method for diagnosing a gateway according to embodiments of the present invention have been described above with reference to FIGS. 1 to 10 . According to the above-described embodiments, message exchange between the external diagnostic device and the target communication node may be performed by the gateway managing the connection status of ports while the external diagnostic device performs diagnosis on the vehicle network. A message may be selectively delivered to a target communication node or an external diagnostic device during a diagnosis process by port mirroring, a forwarding method, or the like. In addition, security can be strengthened in the diagnostic procedure by enabling or disabling the connection of ports by the gateway in consideration of the security range and service time.

The methods according to the present invention may be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the computer-readable medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software.

Examples of computer-readable media include hardware devices specially configured to store and carry out program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as at least one software module to perform the operations of the present invention, and vice versa.

Although it has been described with reference to the above embodiments, it will be understood by those skilled in the art that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. will be able

Claims (20)

A diagnostic method performed by a gateway in a vehicle network, comprising:
The gateway manages the connection state of the controller unit and ports, and includes a PHY (physical) layer unit connected to the controller unit,
receiving, by the controller unit, a diagnosis request message from an external diagnosis device connected to a first port;
receiving, by the controller unit, a security authentication request message and information on a service time of the external diagnostic device from the external diagnostic device when security authentication is required for the diagnostic request message;
verifying, by the controller unit, the security authentication request message;
activating, by the PHY layer unit, a port connected to a target communication node to be diagnosed among the ports under the control of the controller unit within the service time when the verification of the security authentication request message is completed; and
and limiting message exchange between the external diagnostic device and the target communication node when the service time is over. The method according to claim 1,
If security authentication is not required for the diagnosis request message, the PHY layer unit forwards the diagnosis request message to the target communication node without forwarding the diagnosis message to the controller unit. The method according to claim 1,
If the verification of the security authentication request message fails, the controller unit terminates the diagnostic procedure and does not allow communication between the external diagnostic device (10) and the in-vehicle communication node. The method according to claim 1,
The diagnosis request message includes information on the name or function of the target communication node to be diagnosed,
and determining, by the controller unit, at least one of an Ethernet MAC address and an Ethernet IP address of the target communication node from the name or function information of the target communication node. The method according to claim 1,
and when verification of the security authentication request message is completed, transmitting, by the controller unit, security authentication information for the external diagnostic device to the target communication node. delete The method according to claim 1,
When the service time is over, the PHY layer unit deactivating a port connected to the target communication node under the control of the controller unit; including, a diagnostic method. delete The method according to claim 1,
receiving, by the PHY layer unit, a diagnostic response message from the target communication node; and
and transmitting, by the PHY layer unit, the diagnostic response message to the external diagnostic device in a port forwarding manner under the control of the controller unit. The method according to claim 1,
The vehicle network includes an Ethernet-based vehicle network and a controller area network (CAN)-based vehicle network, and the target communication node belongs to the Ethernet-based vehicle network. A diagnostic method performed by a gateway in a vehicle network, comprising:
The gateway includes a controller unit and PHY (physical) layer units connected to the controller unit and managing the connection state of ports,
receiving, by the PHY layer unit, a use request message of the vehicle network from an external diagnostic device connected to a first port;
determining, by the controller unit, whether the vehicle is in a stationary state;
setting, by the controller unit, port mirroring of the PHY layer unit such that a message received from the external diagnostic device is mirrored to a target communication node when the vehicle is in a stationary state;
receiving, by the PHY layer unit, a diagnostic request message from the external diagnostic device; and
and the PHY layer unit forwarding the diagnosis request message to the target communication node by mirroring. 12. The method of claim 11,
In the step of receiving the diagnosis request message, the PHY layer unit also receives information on service time. 13. The method of claim 12,
and when the service time is over, deactivating, by the PHY layer unit, a port connected to the target communication node. 12. The method of claim 11,
receiving, by the PHY layer unit, a diagnostic response message from the target communication node; and
and transmitting, by the PHY layer unit, the diagnostic response message to the external diagnostic device. 12. The method of claim 11,
If the vehicle is not stationary,
receiving, by the PHY layer unit, a diagnostic request message including a unicast address indicating the target communication node from the external diagnostic device;
determining, by the controller unit, a port ID to which the diagnosis request message is to be delivered from a unicast address indicating the target communication node; and
and, under the control of the controller unit, the PHY layer unit forwarding the diagnosis request message through a port corresponding to the port ID. 16. The method of claim 15,
receiving, by the PHY layer unit, a diagnostic response message including a unicast address indicating the external diagnostic device from the target communication node;
determining, by the controller unit, a port ID to which the diagnosis request message is to be transmitted from a unicast address indicating the external diagnosis device; and
and, under the control of the controller unit, the PHY layer unit forwarding the diagnosis response message through a port corresponding to the port ID. A gateway in a vehicle network, comprising:
controller unit; and
It is connected to the controller unit, and includes a PHY (physical) layer unit that manages the connection state of the ports (Port);
the controller unit receives a diagnosis request message from an external diagnosis device connected to the first port; if security authentication is required for the diagnosis request message, receive a security authentication request message and information on a service time of the external diagnosis device from the external diagnostic device;
verify the security authentication request message;
the PHY layer unit activates a port connected to a target communication node to be diagnosed among the ports under the control of the controller unit within the service time when the verification of the security authentication request message is completed; and
When the service time expires, the gateway restricts message exchange between the external diagnostic device and the target communication node. 18. The method of claim 17,
If security authentication is not required for the diagnosis message, the PHY layer unit forwards the diagnosis request message to the target communication node without forwarding the diagnosis message to the controller unit. 18. The method of claim 17,
The diagnosis request message includes information on the name or function of the target communication node to be diagnosed,
The controller unit determines at least one of an Ethernet MAC address and an Ethernet IP address of the target communication node from information on a name or function of the target communication node. 18. The method of claim 17,
When the service time is over, the PHY layer unit deactivates a port connected to the target communication node under the control of the controller unit.

Images