US20190190772A9 - Method and apparatus for diagnosing network - Google Patents
Method and apparatus for diagnosing network Download PDFInfo
- Publication number
- US20190190772A9 US20190190772A9 US14/802,741 US201514802741A US2019190772A9 US 20190190772 A9 US20190190772 A9 US 20190190772A9 US 201514802741 A US201514802741 A US 201514802741A US 2019190772 A9 US2019190772 A9 US 2019190772A9
- Authority
- US
- United States
- Prior art keywords
- message
- communication node
- diagnosis
- response message
- operation method
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 230000006854 communication Effects 0.000 claims abstract description 134
- 238000004891 communication Methods 0.000 claims abstract description 134
- 238000003745 diagnosis Methods 0.000 claims abstract description 113
- 230000004044 response Effects 0.000 claims abstract description 106
- 230000005540 biological transmission Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000004804 winding Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
Definitions
- the CAN may support a transmission rate of up to 1 Mbps and may support auto retransmission of colliding messages, error detection-based on a cycle redundancy interface (CRC), etc.
- the FlexRay-based network may support a transmission rate of up to 10 Mbps and may support simultaneous transmission of data through two channels, synchronous data transmission, etc.
- the MOST-based network is a communication network for high-quality to multimedia, which may support a transmission rate of up to 150 Mbps.
- the telematics system, the infortainment system, and an enhanced safety system of a vehicle require high transmission rates and system expandability.
- the CAN, FlexRay-based network, or the like may not sufficiently support the requirements.
- the MOST-based network may support a higher transmission rate than the CAN and the FlexRay-based network.
- an Ethernet based network may be considered as a vehicle network.
- the Ethernet-based network may support bi-directional communication through one pair of windings and may support a transmission rate of up to 10 Gbps.
- An Ethernet-based vehicle network may include a plurality of communication nodes. Accordingly, there is a need for a method for diagnosing a state (that is, a normal state or a fault state) of each communication node and a state of a channel (or port) to which the communication node is connected.
- example embodiments of the present invention are provided to substantially obviate one or more problems due to limitations and disadvantages of the related art.
- an operation method of a first communication node includes checking whether each of communication nodes connected to the first communication node is in a fault state based on a first message and a first response message in response to the first message transmitted between the communication nodes; and generating a diagnosis response message including identification information of the communication node that is in a fault state or normal state.
- the first message may be an NM message.
- the first communication node may determine that a communication node from which the first response message is to be transmitted is in a fault state.
- the identification information may be at least one of an Internet protocol (IP) address, a port number, and a medium access control (MAC) address.
- IP Internet protocol
- MAC medium access control
- an operation method of a first communication node includes transmitting a first message to at least one communication node connected to the first communication node; checking whether the at least one communication node connected to the first communication node is in a fault state based on a reception state of a first response to message in response to the first message; and generating a diagnosis response message including identification information of the communication node that is in a fault state or normal state.
- the first communication node may determine that a communication node from which the first response message is to be transmitted is in a fault state.
- the first communication node may be a switch or bridge, and the at least one communication node connected to the first communication node may be an end node.
- the diagnosis response message may be generated when a diagnosis request message is received from an OBD device.
- each of the first message, the first response message, the diagnosis request message, and the diagnosis response message may be a message generated based on an Ethernet protocol.
- the operation method may further include transmitting the diagnosis response message to an OBD device.
- an operation method of an on-board diagnostics device includes transmitting a diagnosis request message to a first communication node and receiving, from the first communication node, a diagnosis response message including identification information of a communication node that is in a fault state or normal state among the at least one communication node connected to the first communication node.
- the identification information may be at least one of an IP address, a port number, and a MAC address.
- FIG. 1 is a block diagram showing a vehicle network topology according to an embodiment
- FIG. 3 is a block diagram for describing a method for diagnosing a vehicle network using an on-board diagnostics (OBD) device according to an embodiment
- FIG. 4 is a block diagram for describing a method for diagnosing a vehicle network using an OBD device according to another embodiment
- FIG. 5 is a sequence chart showing a network diagnosis method according to an embodiment of the present invention.
- FIG. 6 is a sequence chart showing a network diagnosis method according to another embodiment of the present invention.
- FIG. 7 is a block diagram showing an example of a message used in an Ethernet-based vehicle network.
- first, second, and the like may be used for describing various elements, but the elements should not be limited by the terms. These terms are only used to distinguish one element from another.
- a first component may be named a second component without being departed from the scope of the present invention and the second component may also be similarly named the first component.
- the term ‘and/or’ means any one or a combination of a plurality of related and described items.
- FIG. 1 is a block diagram showing a vehicle network topology according to an embodiment.
- a communication node may denote a gateway, a switch (or bridge), or an end node.
- the gateway 100 may be connected with at least one switch 110 , 110 - 1 , 110 - 2 , 120 , and 130 and configured to connect different networks.
- the gateway 100 may connect a switch that supports a controller area network (CAN) (FlexRay, media oriented system transport (MOST), or local interconnect network (LIN)) protocol and a switch that supports an Ethernet protocol.
- CAN controller area network
- MOST media oriented system transport
- LIN local interconnect network
- the switches 110 , 110 - 1 , 110 - 2 , 120 , and 130 may be connected with at least one end nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , and 133 .
- the switches 110 , 110 - 1 , 110 - 2 , 120 , and 130 may interconnect and control the end nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , and 133 .
- the end nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , and 133 may denote an electronic control unit (ECU) that controls various types of devices included in a vehicle.
- ECU electronice control unit
- the end nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , and 133 may denote an ECU constituting an infortainment device (e.g., a display device, a navigation device, and an around view monitoring device).
- Communication nodes that is, a gateway, a switch, an end node, or the like
- Communication nodes constituting a vehicle network may be connected in a star topology, bus topology, ring topology, tree topology, mesh topology, etc.
- the communication nodes constituting the vehicle network may support a CAN protocol, FlexRay protocol, MOST protocol, LIN protocol, or Ethernet protocol.
- Embodiments of the present invention may be applied to the above-described network topology.
- the network topology to which embodiments of the present invention are to be applied is not limited thereto and may be configured in various ways.
- the PHY layer block 210 and the controller 220 may be connected through a media independent interface (MII) 230 .
- the MII 230 may denote an interface defined in the IEEE 802.3 and may include a data interface and a management interface between the PHY layer block 210 and the controller 220 .
- One of a reduced MII (RMII), a gigabit MII (GMII), a reduced GMII (RGMII), a serial GMII (SGMII), a 10 GMII (XGMII) may be used instead of the MII 230 .
- a data interface may include a transmission channel and a reception channel, each of which may have an independent clock, data, and a control signal.
- the management interface may include a two-signal interface. One is a signal for the clock, and the other is a signal for the data.
- the PHY layer block 210 may include a PHY layer interface unit 211 , a PHY layer processor 212 , and a PHY layer buffer 213 .
- the configuration of the PHY layer block 210 is not limited thereto, and the PHY layer block 210 may be configured in various ways.
- PHY layer interface unit 211 may transmit a signal received from the controller 220 to the PHY layer processor 212 and may transmit a signal received from the PHY layer processor 212 to the controller 220 .
- the PHY layer processor 212 may control operations of the PHY layer interface unit 211 and the PHY layer buffer 213 .
- the PHY layer processor 212 may modulate a signal to be transmitted or demodulate a received signal.
- the PHY layer processor 212 may control the PHY layer buffer 213 to input or output a signal.
- the PHY layer buffer 213 may store the received signal and may output the stored signal according to a request from the PHY layer processor 212 .
- the controller 220 may monitor and control the PHY layer block 210 through the MII 230 .
- the controller 220 may include a controller interface unit 221 , a core 222 , a main memory 223 , and a sub memory 224 .
- the configuration of the controller 220 is not limited thereto, and the controller 220 may be configured in various ways.
- the controller interface unit 221 may receive a signal from the PHY layer block 210 (that is, the PHY layer interface 211 ) or an upper layer (not shown), transmit the received signal to the core 222 , and transmit the signal received from the core 222 to the PHY layer block 210 or upper layer.
- the core 222 may further include an independent memory control logic or an integrated memory control logic for controlling the controller interface unit 221 , the main memory 223 , and the sub memory 224 .
- the memory control logic may be implemented to be included in the main memory 223 and the sub memory 224 or may be implemented to be included in the core 222 .
- Each of the main memory 223 and the sub memory 224 may store a signal processed by the core 222 and may output the stored signal according to a request from the core 222 .
- the main memory 223 may denote a volatile memory (e.g., a random access memory (RAM)) that temporarily stores data needed for the operation of the core 222 .
- the sub memory 224 may denote a non-volatile memory in which an operating system code (e.g., a to kernel and a device driver) and an application program code for performing a function of the controller 220 are stored.
- a flash memory having a high processing speed or a hard disc drive (HDD) or a compact disc-read only memory (CD-ROM) for large capacity data storage may be used as the non-volatile memory.
- the core 222 may include a logic circuit including at least one processing core.
- a core of an Advanced RISC Machines (ARM) family or a core of an Atom family may be used as the core 222 .
- a method performed by a communication node and a corresponding counterpart communication node, which belong to a vehicle network, will be described below.
- a method e.g., signal transmission or reception
- a second communication node corresponding thereto may perform a method (e.g., signal reception or transmission) corresponding to the method performed by the first communication node. That is, when an operation of the first communication node is described, the second communication node corresponding thereto may perform an operation corresponding to the operation of the first communication node. On the contrary, when an operation of the second communication node is described, the first communication node may perform an operation corresponding to an operation of a switch.
- FIG. 3 is a block diagram for describing a method for diagnosing a vehicle network using an on-board diagnostics (OBD) device according to an embodiment.
- OBD on-board diagnostics
- end nodes 310 , 311 , 312 , 313 , and 314 may constitute the vehicle network described with reference to FIG. 1 and may support an Ethernet protocol.
- Each of the end nodes 310 , 311 , 312 , 313 , and 314 may denote the communication node 200 described with reference to FIG. 2 .
- the end nodes 310 , 311 , 312 , 313 , and 314 may be connected to the same or different switches.
- the end nodes 310 , 311 , 312 , 313 , and 314 may be connected with an OBD device 300 on a one-to-one basis. That is, in order to diagnose the state of the end node 310 and the state of the channel to which the end node 310 is connected, the OBD device 300 may be physically connected with the end node 310 on a one-to-one basis.
- the OBD device 300 may generate a diagnosis request message and may transmit the generated diagnosis request message to the end node 310 .
- the end node 310 may generate a diagnosis response message, which is a response to the diagnosis request message, and may transmit the generated diagnosis response message to the OBD device 300 .
- the end node 310 may transmit an acknowledgement (ACK) message, which is a response to the diagnosis request message, to the OBD device 300 .
- ACK acknowledgement
- the OBD device 300 may determine that the end node 310 and the channel to which the end node 310 is connected are in a normal state. On the contrary, upon not receiving the diagnosis response message (or ACK message), which is the response to the diagnosis request message from the end node 310 , within the period of time from the transmission end time of the diagnosis request message, the OBD device 300 may determine that the end node 310 and the channel to which the end node 310 is connected are in a fault state.
- the OBD device 300 may determine states of the remaining end nodes 311 , 312 , 313 , and 314 by performing the above-described procedure with the end nodes 311 , 312 , 313 , and 314 .
- the vehicle network may include a very large number of end nodes.
- a procedure in which the OBD device 300 and the end node are physically connected on a one-to-one basis and a procedure in which a message is exchanged between the OBD device 300 and the end node may be performed on all the end nodes constituting the vehicle network. In this case, it costs much time to determine the states of all the end nodes constituting the vehicle network.
- FIG. 4 is a block diagram for describing a method for diagnosing a vehicle network using an OBD device according to another embodiment.
- switches 410 , 420 , and 430 and end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may constitute the vehicle network described with reference to FIG. 1 and may support an Ethernet protocol.
- Each of the switches 410 , 420 , and 430 and end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may denote the communication node 200 described with reference to FIG. 2 .
- the first switch 410 may be connected with the end nodes 411 , 412 , and 413 via respective ports and may be connected with the second switch 420 .
- the second switch 420 may be connected with the end nodes 421 , 422 , and 423 via respective ports and may be connected with the first switch 410 and the third switch 430 .
- the third switch 430 may be connected with the end nodes 431 , 432 , and 433 via respective ports and may be connected with the second switch 420 .
- An OBD device 400 may be connected to one communication node (e.g., the third switch 430 ) belonging to the vehicle network in order to diagnose a state of the vehicle network. That is, the OBD device 400 may be connected on a one-to-one basis not with only one communication node, but with all the communication nodes constituting the vehicle network. In this case, through one communication node connected thereto, the OBD device 400 may acquire diagnosis information regarding states of a plurality of communication nodes constituting the vehicle network and states of channels to which the plurality of communication nodes are connected. A method of acquiring the diagnosis information regarding the plurality of communication nodes constituting the vehicle network will be described below in detail.
- the first end node 411 , the fourth end node 421 , and the seventh end node 431 may belong to a first system (e.g., a power train control system) included in a vehicle.
- the second end node 412 , the fifth end node 422 , and the eighth end node 432 may belong to a second system (e.g., a body control system) included in the vehicle.
- the third end node 413 , the sixth end node 423 , and the ninth end node 433 may belong to a third system (e.g., a multimedia system) included in the vehicle.
- the end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 connected to the respective switches 410 , 420 , and 430 may belong to different systems.
- Each of the switches 410 , 420 , and 430 and end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may have topology information regarding the vehicle network.
- each of the switches 410 , 420 , and 430 and end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may receive a message including the topology information regarding the vehicle network from its upper communication node (e.g., a switch, a gateway, etc.) and may check the topology of the vehicle network through the received message.
- its upper communication node e.g., a switch, a gateway, etc.
- the topology information regarding the vehicle network may be pre-stored in the switches 410 , 420 , and 430 and end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 .
- the switches 410 , 420 , and 430 and end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may check the topology of the vehicle network on the basis of the stored information.
- the end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may have respective unique Internet protocols (IPs).
- IPs Internet protocols
- respective IP addresses may be set to the end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 .
- each of the switches 410 , 420 , and 430 and end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may receive a message including an IP address from its upper communication node (e.g., a switch, a gateway, etc.) and may set the IP address included in the received message as its own IP address.
- the IP address may be pre-stored in each of the end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 .
- each of the end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may set the pre-stored IP address as its own IP address.
- the IP address may have a form of “10.xxx.yyy.zz.”
- the segment “xxx” in the IP address may indicate a vehicle system to which a corresponding communication node belongs. That is, communication nodes belonged to the same system may have the same “xxx.”
- the segment “xxx” in IP addresses of the first end node 411 , the fourth end node 421 , and the seventh end node 431 may be set to be “100.”
- the segment “xxx” in IP addresses of the second end node 412 , the fifth end node 422 , and the eighth end node 432 may be set to be “ 200 .”
- the segment “xxx” in IP addresses of the third end node 413 , the sixth end node 423 , and the ninth end node 433 may be set to be “300.”
- the segment “yyy” in the IP address may indicate a class of a corresponding communication node.
- the segment “yyy” in an IP address of a communication node in the lowest class (that is, an end node) among the communication nodes constituting the vehicle network may be set to be “001,” and the segment “yyy” in an IP address of a communication node in the second lowest class may be set to be “002.”
- the segment “zz” in the IP address may denote an index used to distinguish the communication nodes that belong to a class indicated by “yyy” among the communication nodes that belong to a system indicated by “xxx.” Accordingly, the communication nodes that belong to a class indicated by “yyy” among the communication nodes that belong to a system indicated by “xxx” may have different “zz.”
- the IP addresses of the end nodes 411 , 412 , 413 , 421 , 422 , 423 , 431 , 432 , and 433 may be set as shown in
- the details of the method of setting an IP address of a communication node constituting a vehicle network are not limited to those described above, and the IP address of to the communication node may be set in various ways.
- FIG. 5 is a sequence chart showing a network diagnosis method according to an embodiment of the present invention
- FIG. 6 is a sequence chart showing a network diagnosis method according to another embodiment of the present invention.
- the second switch 420 and the end nodes 421 , 422 , and 423 connected to the second switch 420 may be diagnosed similarly or identically to methods to be described below.
- FIG. 7 is a block diagram showing an example of a message used in an Ethernet-based vehicle network.
- an Ethernet protocol-based message 700 may include a physical (PHY) header, a MAC frame, and a frame check sequence (FCS) field 708 .
- the MAC frame may be generated by the controller 220 of the communication node 200 .
- the PHY header may include a preamble 701 and a start frame delimiter (SFD) field 702 .
- the preamble 701 may have a size of 7 octets and may be used for timing synchronization.
- the SFD field 702 may have a sequence of “ 10101011 .”
- the MAC frame may be positioned behind the SFD field 702 .
- the MAC frame may include only an MAC header or may include the MAC header and a logic link control (LLC) frame.
- the MAC header may include a destination address (DA) field 703 , a source address (SA) field 704 , and a length/type field 705 .
- the DA field 703 may have a size of 6 octets to and may include identification information (e.g., an MAC address) of the communication node that receives the MAC frame.
- the SA field 704 may have a size of 6 octets and may include identification information (e.g., an MAC address) of the communication node that transmits the MAC frame.
- the length/type field 705 may have a size of 2 octets and may indicate the length of the data field 706 or an Ethernet type that is supported by a communication node that transmits the protocol-based Ethernet frame 700 .
- the length/type field 705 may indicate the length of the data field 706 .
- the length/type field 705 may indicate an Ethernet type.
- the LLC frame may include the data field 706 and may further include a pad field 707 if necessary (e.g., in order to satisfy a minimum size of the MAC frame). In this case, the pad field 707 may be added behind the data field 706 .
- the first end node 411 may transmit a first message in a broadcast, multicast or unicast manner (S 500 ).
- the first message may denote a network management (NM) message.
- the second end node 412 may transmit a first response message, which is a response to the first message, to the first end node 411 (S 501 ).
- the second end node 412 may transmit the first response message to the first end node 411 within a predefined period of time from a reception time of the first message.
- the first switch 410 may acquire the first message transmitted from the first end node 411 and the first response message transmitted from the second end node 412 .
- the first switch 410 may determine that the second end node 412 and the channel (or port) connected to the second end node 412 are in a normal state.
- the first switch 410 may acquire identification information (e.g., MAC address) of the second end node 412 through the SA field included in the first response message.
- the first switch 410 may acquire an IP address, a port address, etc. corresponding to the MAC address of the second end node 412 from the already known topology information of the vehicle network.
- the first switch 410 may determine that the third end node 413 and the channel (or port) connected to the third end node 413 are in a fault state. For example, the first switch 410 may check an end node that transmits the first response message through the SA field included in the first response message. On the basis of the check result, the first switch 410 may check the third end node that does not transmit the first response message among the end nodes connected to the switch 1 410 and may determine the third end node 413 that does not transmit the first response message is in a fault state.
- the second end node 412 may transmit the first message in a broadcast, multicast, or unicast manner (S 502 ).
- the first message may denote an NM message.
- the first end node 411 may transmit the first response message, which is a response to the first message, to the second end node 412 (S 503 ).
- the first end node 411 may transmit the first response message to the second end node 412 within a predefined period of time from a reception time of the first message.
- the first switch 410 may determine that the third end node 413 and the channel (or port) connected to the third end node 413 are in a fault state.
- the first switch 410 may acquire an IP address, a port address, an MAC address, etc. of the third end node 413 that is determined to be in a fault state from the already known topology information of the vehicle network.
- the third end node 413 that is in a fault state may not transmit the first message and the first response message.
- the channel (or port) to which the third end node 413 is connected is in a fault state although the third end node 413 is in a normal state, the first message and first response message transmitted from the third end node 413 are not received by the first switch 410 , the first end node 411 , and the second end node 412 .
- the first switch 410 may transmit a first message in a broadcast, multicast, or unicast manner (S 510 ).
- the first message may denote an NM message.
- the first end node 411 may transmit a first response message (e.g., an ACK message), which is a response to the first message, to the first switch 410 (S 511 ).
- the first end node 411 may transmit the first response message to the first switch 410 within a predefined period of time from a reception time of the first message.
- the third end node 413 that is in a fault state may not transmit the first response message, which is a response to the first message.
- the first response message transmitted from the third end node 413 is not received by the first switch 410 .
- the first switch 410 may determine that the third end node 413 and the channel (or port) connected to the third end node 413 are in a fault state.
- the first switch 410 may acquire an IP address, a port address, an MAC address, etc. of the third end node 413 that is determined to be in a fault state from the already known topology information of the vehicle network.
- the OBD device 400 may generate a diagnosis request message in order to diagnose the fault state of the vehicle network.
- the diagnosis request message may include at least one an indicator that request identification information of a communication node that is in a fault state (or a communication node that is connected to a channel (or port) that is in a fault state), an indicator that requests identification information of a communication node that is in a normal state (or a communication node that is connected a channel (or port) that is in a normal state), and an indicator that requests information regarding a state (that is, a normal state or fault state) of a communication mode constituting the vehicle network.
- the indicator may be included in an MAC header or data field of the diagnosis request message.
- the OBD device 400 may transmit the diagnosis request message in a broadcast, multicast, or unicast manner (S 520 ).
- the first switch 410 may generate a bitmap indicating states of the first end node 411 , the second end node 412 , and the third end node 413 and generate a diagnosis response message including the bitmap.
- the bitmap may be included in at least one of the to MAC header and the data field of the diagnosis response message.
- the first switch 410 and the OBD device 400 are aware of the order between the end nodes 411 , 412 , and 413 in the bitmap.
- the first switch 410 may transmit the diagnosis response message to the OBD device 400 in a broadcast, multicast, or unicast manner (S 522 ). That is, the diagnosis response message may be transmitted to the OBD device 400 through the second switch 420 and the third switch 430 .
- the OBD device 400 may check the states of the end nodes 411 , 412 , and 413 connected to the first switch 410 (S 523 ). The OBD device 400 may determine that the first end node 411 and the second end node 412 are in a normal state and the third end node 413 is in a fault state.
- the diagnosis response message is generated after the diagnosis request message is received.
- the order in which the diagnosis response message is generated is not limited thereto.
- the diagnosis response message may be generated before the diagnosis request message is received.
- the first switch 410 may transmit the previously generated diagnosis response message to the OBD device 400 upon receiving the diagnosis request message.
- the methods according to embodiments of the present invention may be implemented as program instructions executable by a variety of computers and recorded on a computer readable medium.
- the computer readable medium may include a program instruction, a data file, a data structure, or a combination thereof.
- the program instructions recorded on the computer readable medium may be designed and configured specifically for the present invention or can be publicly known and available to those who are skilled in the field of computer software.
- Examples of the computer readable medium may include a hardware device such as ROM, RAM, and flash memory, which are specifically configured to store and execute the program instructions.
- Examples of the program instructions include machine codes made by, for example, a compiler, as well as high-level language codes executable by a computer, using an interpreter.
- the above exemplary hardware device can be configured to operate as at least one software module in order to perform the operation of the present invention, and vice versa.
- a state that is, a normal state or a fault state
- a state of a channel (or port) to which the communication node is connected A communication node and channel in a fault state may be quickly repaired based on the determination result.
- the performance of the vehicle network may be enhanced.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
- This application claims priority to U.S. patent application Ser. No. 62/026,343 filed on Jul. 18, 2014, U.S. patent application Ser. No. 62/026,335 filed on Jul. 18, 2014, and Korean Patent Application No. 2015-0098909 filed on Jul. 13, 2015 in the Korean Intellectual Property Office (KIPO), the entire contents of which are hereby incorporated by reference.
- 1. Technical Field
- Example embodiments of the present invention relate in general to a network diagnosis technique and more specifically to a method and apparatus for diagnosing a state of a communication node constituting a network and a state of a channel (or port) to which the communication node is connected.
- 2. Related Art
- Along with the rapid digitalization of vehicle parts, the number and types of electronic devices installed in a vehicle are being significantly increased. Electronic devices may be largely used in a power train control system, a body control system, a chassis control system, a vehicle network, a multimedia system, or the like. The power train control system may denote an engine control system, an automatic transmission control system, etc. The body control system may denote a body electronic equipment control system, a convenience apparatus control system, a lamp control system, etc. The chassis control system may denote a steering apparatus control system, a brake control system, a suspension control system, etc. The vehicle network may denote a controller area network (CAN), a FlexRay-based network, a media oriented system transport (MOST)-based network, etc. The multimedia system may denote a navigation apparatus system, a telematics system, an infortainment system, etc.
- Such systems and electronic devices constituting each of the systems are connected through the vehicle network, which is required to support functions of the electronic devices. The CAN may support a transmission rate of up to 1 Mbps and may support auto retransmission of colliding messages, error detection-based on a cycle redundancy interface (CRC), etc. The FlexRay-based network may support a transmission rate of up to 10 Mbps and may support simultaneous transmission of data through two channels, synchronous data transmission, etc. The MOST-based network is a communication network for high-quality to multimedia, which may support a transmission rate of up to 150 Mbps.
- Meanwhile, the telematics system, the infortainment system, and an enhanced safety system of a vehicle require high transmission rates and system expandability. However, the CAN, FlexRay-based network, or the like may not sufficiently support the requirements. The MOST-based network may support a higher transmission rate than the CAN and the FlexRay-based network. However, it costs a great deal to apply the MOST-based network to all vehicle networks. Due to these limitations, an Ethernet based network may be considered as a vehicle network. The Ethernet-based network may support bi-directional communication through one pair of windings and may support a transmission rate of up to 10 Gbps.
- An Ethernet-based vehicle network may include a plurality of communication nodes. Accordingly, there is a need for a method for diagnosing a state (that is, a normal state or a fault state) of each communication node and a state of a channel (or port) to which the communication node is connected.
- Accordingly, example embodiments of the present invention are provided to substantially obviate one or more problems due to limitations and disadvantages of the related art.
- Example embodiments of the present invention provide a method for diagnosing a state of a communication node constituting a network and a state of a channel (or port) to which the communication node is connected.
- Example embodiments of the present invention also provide an apparatus for diagnosing a state of a communication node constituting a network and a state of a channel (or port) to which the communication node is connected.
- In some example embodiments, an operation method of a first communication node includes checking whether each of communication nodes connected to the first communication node is in a fault state based on a first message and a first response message in response to the first message transmitted between the communication nodes; and generating a diagnosis response message including identification information of the communication node that is in a fault state or normal state.
- Here, the first message may be an NM message.
- Here, when the first response message in response to the first message is not received within a predefined period of time, the first communication node may determine that a communication node from which the first response message is to be transmitted is in a fault state.
- Here, the first communication node may be a switch or bridge, and each of the communication nodes connected to the first communication node may be an end node.
- Here, the identification information may be at least one of an Internet protocol (IP) address, a port number, and a medium access control (MAC) address.
- Here, the diagnosis response message may be generated when a diagnosis request message is received from an OBD device.
- Here, each of the first message, the first response message, the diagnosis request message, and the diagnosis response message may be a message generated based on an Ethernet protocol.
- In addition, the operation method may further include transmitting the diagnosis response message to an OBD device.
- Here, the diagnosis response message may be transmitted in a broadcast manner.
- In other example embodiments, an operation method of a first communication node includes transmitting a first message to at least one communication node connected to the first communication node; checking whether the at least one communication node connected to the first communication node is in a fault state based on a reception state of a first response to message in response to the first message; and generating a diagnosis response message including identification information of the communication node that is in a fault state or normal state.
- Here, when the first response message in response to the first message is not received within a predefined period of time, the first communication node may determine that a communication node from which the first response message is to be transmitted is in a fault state.
- Here, the first communication node may be a switch or bridge, and the at least one communication node connected to the first communication node may be an end node.
- Here, the identification information may be at least one of an IP address, a port number, and a MAC address.
- Here, the diagnosis response message may be generated when a diagnosis request message is received from an OBD device.
- Here, each of the first message, the first response message, the diagnosis request message, and the diagnosis response message may be a message generated based on an Ethernet protocol.
- In addition, the operation method may further include transmitting the diagnosis response message to an OBD device.
- In still other example embodiments, an operation method of an on-board diagnostics device includes transmitting a diagnosis request message to a first communication node and receiving, from the first communication node, a diagnosis response message including identification information of a communication node that is in a fault state or normal state among the at least one communication node connected to the first communication node.
- Here, the first communication node may be a switch or bridge, and the at least one communication node connected to the first communication node may be an end node.
- Here, each of the diagnosis request message and the diagnosis response message may be a message generated based on an Ethernet protocol.
- Here, the identification information may be at least one of an IP address, a port number, and a MAC address.
- Example embodiments of the present invention will become more apparent by describing in detail example embodiments of the present invention with reference to the accompanying drawings, in which:
-
FIG. 1 is a block diagram showing a vehicle network topology according to an embodiment; -
FIG. 2 is a block diagram showing a communication node constituting a vehicle network according to an embodiment; -
FIG. 3 is a block diagram for describing a method for diagnosing a vehicle network using an on-board diagnostics (OBD) device according to an embodiment; -
FIG. 4 is a block diagram for describing a method for diagnosing a vehicle network using an OBD device according to another embodiment; -
FIG. 5 is a sequence chart showing a network diagnosis method according to an embodiment of the present invention; -
FIG. 6 is a sequence chart showing a network diagnosis method according to another embodiment of the present invention; and -
FIG. 7 is a block diagram showing an example of a message used in an Ethernet-based vehicle network. - Since the present invention may be variously modified and have several exemplary embodiments, specific exemplary embodiments will be shown in the accompanying drawings to and be described in detail in the detailed description. It should be understood, however, that it is not intended to limit the present invention to the specific embodiments but, on the contrary, the present invention is to cover all modifications and alternatives falling within the spirit and scope of the present invention.
- Relational terms such as first, second, and the like may be used for describing various elements, but the elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first component may be named a second component without being departed from the scope of the present invention and the second component may also be similarly named the first component. The term ‘and/or’ means any one or a combination of a plurality of related and described items.
- When it is mentioned that a certain component is “coupled with” or “connected with” another component, it should be understood that the certain component is directly “coupled with” or “connected with” to the other component or a further component may be located therebetween. In contrast, when it is mentioned that a certain component is “directly coupled with” or “directly connected with” another component, it will be understood that a further component is not located therebetween.
- In the following description, the technical terms are used only for explaining a specific exemplary embodiment while not limiting the present disclosure. The singular forms ‘a,’ ‘an,’ and ‘the’ include plural reference unless the context clearly dictates otherwise. In the present specification, it will be understood that the terms “have,” “comprise,” “include,” and the like are used to specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
- Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as terms that are generally used and have been in dictionaries should be construed as having meanings matched with contextual meanings in the art. In this description, unless defined clearly, terms are not ideally, excessively construed as formal meanings.
- Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the invention, in order to facilitate the entire understanding of the invention, like numbers refer to like elements throughout the description of the figures and the repetitive description thereof will be omitted.
-
FIG. 1 is a block diagram showing a vehicle network topology according to an embodiment. - Referring to
FIG. 1 , a communication node may denote a gateway, a switch (or bridge), or an end node. Thegateway 100 may be connected with at least oneswitch 110, 110-1, 110-2, 120, and 130 and configured to connect different networks. For example, thegateway 100 may connect a switch that supports a controller area network (CAN) (FlexRay, media oriented system transport (MOST), or local interconnect network (LIN)) protocol and a switch that supports an Ethernet protocol. Theswitches 110, 110-1, 110-2, 120, and 130 may be connected with at least oneend nodes switches 110, 110-1, 110-2, 120, and 130 may interconnect and control theend nodes - The
end nodes end nodes - Communication nodes (that is, a gateway, a switch, an end node, or the like) constituting a vehicle network may be connected in a star topology, bus topology, ring topology, tree topology, mesh topology, etc. In addition, the communication nodes constituting the vehicle network may support a CAN protocol, FlexRay protocol, MOST protocol, LIN protocol, or Ethernet protocol. Embodiments of the present invention may be applied to the above-described network topology. The network topology to which embodiments of the present invention are to be applied is not limited thereto and may be configured in various ways.
-
FIG. 2 is a block diagram showing a communication node constituting a vehicle network according to an embodiment. - Referring to
FIG. 2 , acommunication node 200 constituting a network may include aPHY layer block 210 and acontroller 220. In this case, thecontroller 220 may be implemented to include a medium access control (MAC) layer. APHY layer block 210 may receive or transmit signals from or to another communication node. Thecontroller 220 may control thePHY layer block 210 and perform various functions (e.g., an infortainment function). ThePHY layer block 210 and thecontroller 220 may be implemented as one system on chip (SoC) and may be implemented as separate chips. - The
PHY layer block 210 and thecontroller 220 may be connected through a media independent interface (MII) 230. TheMII 230 may denote an interface defined in the IEEE 802.3 and may include a data interface and a management interface between thePHY layer block 210 and thecontroller 220. One of a reduced MII (RMII), a gigabit MII (GMII), a reduced GMII (RGMII), a serial GMII (SGMII), a 10 GMII (XGMII) may be used instead of theMII 230. A data interface may include a transmission channel and a reception channel, each of which may have an independent clock, data, and a control signal. The management interface may include a two-signal interface. One is a signal for the clock, and the other is a signal for the data. - The
PHY layer block 210 may include a PHYlayer interface unit 211, aPHY layer processor 212, and aPHY layer buffer 213. The configuration of thePHY layer block 210 is not limited thereto, and thePHY layer block 210 may be configured in various ways. The - PHY
layer interface unit 211 may transmit a signal received from thecontroller 220 to thePHY layer processor 212 and may transmit a signal received from thePHY layer processor 212 to thecontroller 220. ThePHY layer processor 212 may control operations of the PHYlayer interface unit 211 and thePHY layer buffer 213. ThePHY layer processor 212 may modulate a signal to be transmitted or demodulate a received signal. ThePHY layer processor 212 may control thePHY layer buffer 213 to input or output a signal. ThePHY layer buffer 213 may store the received signal and may output the stored signal according to a request from thePHY layer processor 212. - The
controller 220 may monitor and control thePHY layer block 210 through theMII 230. Thecontroller 220 may include acontroller interface unit 221, acore 222, amain memory 223, and asub memory 224. The configuration of thecontroller 220 is not limited thereto, and thecontroller 220 may be configured in various ways. Thecontroller interface unit 221 may receive a signal from the PHY layer block 210 (that is, the PHY layer interface 211) or an upper layer (not shown), transmit the received signal to thecore 222, and transmit the signal received from thecore 222 to thePHY layer block 210 or upper layer. Thecore 222 may further include an independent memory control logic or an integrated memory control logic for controlling thecontroller interface unit 221, themain memory 223, and thesub memory 224. The memory control logic may be implemented to be included in themain memory 223 and thesub memory 224 or may be implemented to be included in thecore 222. - Each of the
main memory 223 and thesub memory 224 may store a signal processed by thecore 222 and may output the stored signal according to a request from thecore 222. Themain memory 223 may denote a volatile memory (e.g., a random access memory (RAM)) that temporarily stores data needed for the operation of thecore 222. Thesub memory 224 may denote a non-volatile memory in which an operating system code (e.g., a to kernel and a device driver) and an application program code for performing a function of thecontroller 220 are stored. A flash memory having a high processing speed or a hard disc drive (HDD) or a compact disc-read only memory (CD-ROM) for large capacity data storage may be used as the non-volatile memory. Typically, thecore 222 may include a logic circuit including at least one processing core. A core of an Advanced RISC Machines (ARM) family or a core of an Atom family may be used as thecore 222. - A method performed by a communication node and a corresponding counterpart communication node, which belong to a vehicle network, will be described below. Although a method (e.g., signal transmission or reception) performed by a first communication node will be described below, a second communication node corresponding thereto may perform a method (e.g., signal reception or transmission) corresponding to the method performed by the first communication node. That is, when an operation of the first communication node is described, the second communication node corresponding thereto may perform an operation corresponding to the operation of the first communication node. On the contrary, when an operation of the second communication node is described, the first communication node may perform an operation corresponding to an operation of a switch.
-
FIG. 3 is a block diagram for describing a method for diagnosing a vehicle network using an on-board diagnostics (OBD) device according to an embodiment. - Referring to
FIG. 3 ,end nodes FIG. 1 and may support an Ethernet protocol. Each of theend nodes communication node 200 described with reference toFIG. 2 . Theend nodes end nodes end nodes end nodes OBD device 300 on a one-to-one basis. That is, in order to diagnose the state of theend node 310 and the state of the channel to which theend node 310 is connected, theOBD device 300 may be physically connected with theend node 310 on a one-to-one basis. - When the
OBD device 300 and theend node 310 may be connected on a one-to-one basis, theOBD device 300 may generate a diagnosis request message and may transmit the generated diagnosis request message to theend node 310. Upon receiving the diagnosis request message from theOBD device 300, theend node 310 may generate a diagnosis response message, which is a response to the diagnosis request message, and may transmit the generated diagnosis response message to theOBD device 300. Alternatively, upon receiving the diagnosis request message from theOBD device 300, theend node 310 may transmit an acknowledgement (ACK) message, which is a response to the diagnosis request message, to theOBD device 300. Upon receiving a diagnosis response message (or ACK message), which is a response to the diagnosis request message from theend node 310, within a predefined period of time from a transmission end time of the diagnosis request message, theOBD device 300 may determine that theend node 310 and the channel to which theend node 310 is connected are in a normal state. On the contrary, upon not receiving the diagnosis response message (or ACK message), which is the response to the diagnosis request message from theend node 310, within the period of time from the transmission end time of the diagnosis request message, theOBD device 300 may determine that theend node 310 and the channel to which theend node 310 is connected are in a fault state. - The
OBD device 300 may determine states of the remainingend nodes end nodes OBD device 300 and the end node are physically connected on a one-to-one basis and a procedure in which a message is exchanged between theOBD device 300 and the end node may be performed on all the end nodes constituting the vehicle network. In this case, it costs much time to determine the states of all the end nodes constituting the vehicle network. -
FIG. 4 is a block diagram for describing a method for diagnosing a vehicle network using an OBD device according to another embodiment. - Referring to
FIG. 4 , switches 410, 420, and 430 and endnodes FIG. 1 and may support an Ethernet protocol. Each of theswitches nodes communication node 200 described with reference toFIG. 2 . Thefirst switch 410 may be connected with theend nodes second switch 420. Thesecond switch 420 may be connected with theend nodes first switch 410 and thethird switch 430. Thethird switch 430 may be connected with theend nodes second switch 420. - An
OBD device 400 may be connected to one communication node (e.g., the third switch 430) belonging to the vehicle network in order to diagnose a state of the vehicle network. That is, theOBD device 400 may be connected on a one-to-one basis not with only one communication node, but with all the communication nodes constituting the vehicle network. In this case, through one communication node connected thereto, theOBD device 400 may acquire diagnosis information regarding states of a plurality of communication nodes constituting the vehicle network and states of channels to which the plurality of communication nodes are connected. A method of acquiring the diagnosis information regarding the plurality of communication nodes constituting the vehicle network will be described below in detail. - The
first end node 411, thefourth end node 421, and theseventh end node 431 may belong to a first system (e.g., a power train control system) included in a vehicle. Thesecond end node 412, thefifth end node 422, and theeighth end node 432 may belong to a second system (e.g., a body control system) included in the vehicle. Thethird end node 413, thesixth end node 423, and theninth end node 433 may belong to a third system (e.g., a multimedia system) included in the vehicle. That is, theend nodes respective switches - Each of the
switches nodes switches nodes switches nodes switches nodes - The
end nodes end nodes switches nodes end nodes end nodes - The IP address may have a form of “10.xxx.yyy.zz.” The segment “xxx” in the IP address may indicate a vehicle system to which a corresponding communication node belongs. That is, communication nodes belonged to the same system may have the same “xxx.” For example, the segment “xxx” in IP addresses of the
first end node 411, thefourth end node 421, and theseventh end node 431 may be set to be “100.” For example, the segment “xxx” in IP addresses of thesecond end node 412, thefifth end node 422, and theeighth end node 432 may be set to be “200.” For example, the segment “xxx” in IP addresses of thethird end node 413, thesixth end node 423, and theninth end node 433 may be set to be “300.” - The segment “yyy” in the IP address may indicate a class of a corresponding communication node. For example, the segment “yyy” in an IP address of a communication node in the lowest class (that is, an end node) among the communication nodes constituting the vehicle network may be set to be “001,” and the segment “yyy” in an IP address of a communication node in the second lowest class may be set to be “002.” The segment “zz” in the IP address may denote an index used to distinguish the communication nodes that belong to a class indicated by “yyy” among the communication nodes that belong to a system indicated by “xxx.” Accordingly, the communication nodes that belong to a class indicated by “yyy” among the communication nodes that belong to a system indicated by “xxx” may have different “zz.” The IP addresses of the
end nodes -
TABLE 1 Type of Communication Node IP Address End node 1 10.100.001.01 End node 210.200.001.01 End node 310.300.001.01 End node 4 10.100.001.02 End node 510.200.001.02 End node 610.300.001.02 End node 7 10.100.001.03 End node 810.200.001.03 End node 910.300.001.03 - The details of the method of setting an IP address of a communication node constituting a vehicle network are not limited to those described above, and the IP address of to the communication node may be set in various ways.
-
FIG. 5 is a sequence chart showing a network diagnosis method according to an embodiment of the present invention, andFIG. 6 is a sequence chart showing a network diagnosis method according to another embodiment of the present invention. - Referring to
FIGS. 5 and 6 , switches 410, 420, and 430,end nodes OBD device 400 may constitute the vehicle network described with reference toFIG. 4 . That is, theswitches end nodes OBD device 400 may correspond to the configurations of the elements having the same numerals in the vehicle network shown inFIG. 4 . In addition, theswitches end nodes OBD device 400 may have topology information regarding the vehicle network. The topology information of the vehicle network may include an IP address, a port address, and an MAC address of each of the communication nodes constituting the vehicle network. A network to which network diagnosis methods according to embodiments of the present invention are applied is not limited to the vehicle network shown inFIG. 4 . The network diagnosis methods according to embodiments of the present invention may be applied to various networks. The network diagnosis methods according to embodiments of the present invention will be described on the basis of thefirst switch 410 and theend nodes first switch 410. However, thesecond switch 420 and theend nodes third switch 430 and theend nodes - The network diagnosis method shown in
FIG. 5 and the network diagnosis method shown inFIG. 6 may have the same operations from S520 but different operations before S520. That is, message transmission/reception operations S500, S501, S502, and S503 for checking whether theend nodes FIG. 5 are different from message transmission/reception operations S510, S511, and S512 for checking whether theend nodes FIG. 6 . A message (e.g., a first message, a first response message, a diagnosis request message, a diagnosis response message, etc.) used in embodiments of the present invention may denote a message that is generated based on an Ethernet protocol. The message that is generated based on the Ethernet protocol may be as follows. -
FIG. 7 is a block diagram showing an example of a message used in an Ethernet-based vehicle network. - Referring to
FIG. 7 , an Ethernet protocol-basedmessage 700 may include a physical (PHY) header, a MAC frame, and a frame check sequence (FCS)field 708. The MAC frame may be generated by thecontroller 220 of thecommunication node 200. The PHY header may include apreamble 701 and a start frame delimiter (SFD)field 702. Thepreamble 701 may have a size of 7 octets and may be used for timing synchronization. TheSFD field 702 may have a sequence of “10101011.” - The MAC frame may be positioned behind the
SFD field 702. The MAC frame may include only an MAC header or may include the MAC header and a logic link control (LLC) frame. The MAC header may include a destination address (DA)field 703, a source address (SA)field 704, and a length/type field 705. TheDA field 703 may have a size of 6 octets to and may include identification information (e.g., an MAC address) of the communication node that receives the MAC frame. TheSA field 704 may have a size of 6 octets and may include identification information (e.g., an MAC address) of the communication node that transmits the MAC frame. - The length/
type field 705 may have a size of 2 octets and may indicate the length of thedata field 706 or an Ethernet type that is supported by a communication node that transmits the protocol-basedEthernet frame 700. For example, when a first octet value included in the length/type field 705 is less than or equal to the decimal value 1500, the length/type field 705 may indicate the length of thedata field 706. When the first octet value included in the length/type field 705 is more than or equal to the decimal value 1536, the length/type field 705 may indicate an Ethernet type. The LLC frame may include thedata field 706 and may further include apad field 707 if necessary (e.g., in order to satisfy a minimum size of the MAC frame). In this case, thepad field 707 may be added behind thedata field 706. - Referring back to
FIGS. 5 and 6 , in the network diagnosis method according to an embodiment of the present invention, thefirst end node 411 may transmit a first message in a broadcast, multicast or unicast manner (S500). Here, the first message may denote a network management (NM) message. Upon receiving the first message from thefirst end node 411, thesecond end node 412 may transmit a first response message, which is a response to the first message, to the first end node 411 (S501). In this case, thesecond end node 412 may transmit the first response message to thefirst end node 411 within a predefined period of time from a reception time of the first message. - The
first switch 410 may acquire the first message transmitted from thefirst end node 411 and the first response message transmitted from thesecond end node 412. Upon receiving the first response message from thesecond end node 412 within a predefined period of time from the reception time of the first message, thefirst switch 410 may determine that thesecond end node 412 and the channel (or port) connected to thesecond end node 412 are in a normal state. In addition, thefirst switch 410 may acquire identification information (e.g., MAC address) of thesecond end node 412 through the SA field included in the first response message. Thefirst switch 410 may acquire an IP address, a port address, etc. corresponding to the MAC address of thesecond end node 412 from the already known topology information of the vehicle network. - Upon not receiving the first response message from the
third end node 413 within a predefined period of time from the reception time of the first message, thefirst switch 410 may determine that thethird end node 413 and the channel (or port) connected to thethird end node 413 are in a fault state. For example, thefirst switch 410 may check an end node that transmits the first response message through the SA field included in the first response message. On the basis of the check result, thefirst switch 410 may check the third end node that does not transmit the first response message among the end nodes connected to theswitch 1 410 and may determine thethird end node 413 that does not transmit the first response message is in a fault state. Here, when thethird end node 413 is in a fault state, or a channel (or port) between thefirst switch 410 and thethird end node 413 is in a fault state, thefirst switch 410 may not receive the first response message from thethird end node 413 within a predefined period of time from the reception time of the first message. Thefirst switch 410 may acquire an IP address, a port address, an MAC address, etc. of thethird end node 413 that is determined to be in a fault state from the already known topology information of the vehicle network. - Next, the
second end node 412 may transmit the first message in a broadcast, multicast, or unicast manner (S502). Here, the first message may denote an NM message. Upon receiving the first message from thesecond end node 412, thefirst end node 411 may transmit the first response message, which is a response to the first message, to the second end node 412 (S503). In this case, thefirst end node 411 may transmit the first response message to thesecond end node 412 within a predefined period of time from a reception time of the first message. - The
first switch 410 may acquire the first message transmitted from thesecond end node 412 and the first response message transmitted from thefirst end node 411. Upon receiving the first response message from thefirst end node 411 within a predefined period of time from the reception time of the first message, thefirst switch 410 may determine that thefirst end node 411 and the channel (or port) connected to thefirst end node 411 are in a normal state. In addition, thefirst switch 410 may acquire identification information (e.g., MAC address) of thefirst end node 411 through the SA field included in the first response message. Thefirst switch 410 may acquire an IP address, a port address, etc. corresponding to the MAC address of thefirst end node 411 from the already known topology information of the vehicle network. - Upon not receiving the first response message from the
third end node 413 within a predefined period of time from the reception time of the first message, thefirst switch 410 may determine that thethird end node 413 and the channel (or port) connected to thethird end node 413 are in a fault state. Thefirst switch 410 may acquire an IP address, a port address, an MAC address, etc. of thethird end node 413 that is determined to be in a fault state from the already known topology information of the vehicle network. - The
third end node 413 that is in a fault state may not transmit the first message and the first response message. When the channel (or port) to which thethird end node 413 is connected is in a fault state although thethird end node 413 is in a normal state, the first message and first response message transmitted from thethird end node 413 are not received by thefirst switch 410, thefirst end node 411, and thesecond end node 412. - Next, in the network diagnosis method according to another embodiment of the present invention, the
first switch 410 may transmit a first message in a broadcast, multicast, or unicast manner (S510). Here, the first message may denote an NM message. Upon to receiving the first message from thefirst switch 410, thefirst end node 411 may transmit a first response message (e.g., an ACK message), which is a response to the first message, to the first switch 410 (S511). In this case, thefirst end node 411 may transmit the first response message to thefirst switch 410 within a predefined period of time from a reception time of the first message. Upon receiving the first message from thefirst switch 410, thesecond end node 412 may transmit a first response message (e.g., an ACK message), which is a response to the first message, to the first switch 410 (S512). In this case, thesecond end node 412 may transmit the first response message to thefirst switch 410 within a predefined period of time from a reception time of the first message. - Since the
first switch 410 has acquired the first response message from thefirst end node 411 and thesecond end node 412 within a predefined period of time from the transmission time of the first message, thefirst switch 410 may determine that thefirst end node 411 and the second end node 412 (or channels (or ports) connected to thefirst end node 411 and the second end node 412) are in a normal state. Thefirst switch 410 may acquire identification information (e.g., MAC address) of thefirst end node 411 and thesecond end node 412 through the SA field included in the response message. Thefirst switch 410 may acquire IP addresses, port addresses, etc. corresponding to the MAC addresses of thefirst end node 411 and thesecond end node 412 from the already known topology information of the vehicle network. - The
third end node 413 that is in a fault state may not transmit the first response message, which is a response to the first message. When the channel (or port) to which thethird end node 413 is connected is in a fault state although thethird end node 413 is in a normal state, the first response message transmitted from thethird end node 413 is not received by thefirst switch 410. Upon not receiving the first response message from thethird end node 413 within a predefined period of time from the transmission time of the first message, thefirst switch 410 may determine that thethird end node 413 and the channel (or port) connected to thethird end node 413 are in a fault state. Thefirst switch 410 may acquire an IP address, a port address, an MAC address, etc. of thethird end node 413 that is determined to be in a fault state from the already known topology information of the vehicle network. - Next, the
OBD device 400 may generate a diagnosis request message in order to diagnose the fault state of the vehicle network. The diagnosis request message may include at least one an indicator that request identification information of a communication node that is in a fault state (or a communication node that is connected to a channel (or port) that is in a fault state), an indicator that requests identification information of a communication node that is in a normal state (or a communication node that is connected a channel (or port) that is in a normal state), and an indicator that requests information regarding a state (that is, a normal state or fault state) of a communication mode constituting the vehicle network. Here, the indicator may be included in an MAC header or data field of the diagnosis request message. TheOBD device 400 may transmit the diagnosis request message in a broadcast, multicast, or unicast manner (S520). - The diagnosis request message may be transmitted to the
first switch 410 through thesecond switch 420 and thethird switch 430. For example, thethird switch 430 physically connected with theOBD device 400 may receive the diagnosis request message from theOBD device 400 and may transmit the diagnosis request message in a broadcast manner when the diagnosis request message is transmitted in the broadcast manner. Thesecond switch 420 physically connected with thethird switch 430 may receive the diagnosis request message from thethird switch 430 and may transmit the diagnosis request message in a broadcast manner when the diagnosis request message is transmitted in the broadcast manner. Thefirst switch 410 physically connected with thesecond switch 420 may receive the diagnosis request message from thesecond switch 420. - Alternatively, the
third switch 430 physically connected with theOBD device 400 to may receive the diagnosis request message from theOBD device 400, and may route the diagnosis request message to thesecond switch 420 connected with thefirst switch 410 when a DA address included in the diagnosis request message indicates thefirst switch 410. Thesecond switch 420 physically connected with thethird switch 430 may receive the diagnosis request message from thethird switch 430 and may transmit the diagnosis request message to thefirst switch 410 when the DA address included in the diagnosis request message indicates thefirst switch 410. Thefirst switch 410 physically connected with thesecond switch 420 may receive the diagnosis request message from thesecond switch 420. - Upon receiving the diagnosis request message, the
first switch 410 may check information requested by the diagnosis request message (or information requested by an indicator included in the diagnosis request message) and may generate a diagnosis response message including the requested information (S521). When the diagnosis request message (or the indicator included in the diagnosis request message) requests identification information of a communication node that is in a fault state, thefirst switch 410 may generate a diagnosis response message including identification information of thethird end node 413. Alternatively, when the diagnosis request message (or the indicator included in the diagnosis request message) requests identification information of a communication node that is in a normal state, thefirst switch 410 may generate a diagnosis response message including identification information of thefirst end node 411 and thesecond end node 412. Here, the identification information may be included in at least one of a MAC header and a data field of the diagnosis response message. - Alternatively, when the diagnosis request message (or the indicator included in the diagnosis request message) requests state information of a communication node constituting the vehicle network, the
first switch 410 may generate a bitmap indicating states of thefirst end node 411, thesecond end node 412, and thethird end node 413 and generate a diagnosis response message including the bitmap. The bitmap may be included in at least one of the to MAC header and the data field of the diagnosis response message. Here, it is assumed that thefirst switch 410 and theOBD device 400 are aware of the order between theend nodes first end node 411, the second bit in the bitmap may indicate the state of thesecond end node 412, and the third bit in the bitmap may indicate the state of thethird end node 413. In addition, when the bit is set to the binary value 0, this may indicate that a corresponding communication node (or a channel (or port) connected to the corresponding communication node) is in a normal state. When the bit is set to thebinary value 1, this may indicate that the corresponding communication node (or the channel (or port) connected to the corresponding communication node) is in a fault state. In this case, thefirst switch 410 may set the bitmap as “001” and may generate a diagnosis response message including “001.” The details of the bitmap setting method are not limited to those described above, and the bitmap may be set in various ways. - Next, the
first switch 410 may transmit the diagnosis response message to theOBD device 400 in a broadcast, multicast, or unicast manner (S522). That is, the diagnosis response message may be transmitted to theOBD device 400 through thesecond switch 420 and thethird switch 430. Upon receiving the diagnosis response message, theOBD device 400 may check the states of theend nodes OBD device 400 may determine that thefirst end node 411 and thesecond end node 412 are in a normal state and thethird end node 413 is in a fault state. In embodiments of the present invention, it has been described that the diagnosis response message is generated after the diagnosis request message is received. However, the order in which the diagnosis response message is generated is not limited thereto. For example, the diagnosis response message may be generated before the diagnosis request message is received. Thefirst switch 410 may transmit the previously generated diagnosis response message to theOBD device 400 upon receiving the diagnosis request message. - The methods according to embodiments of the present invention may be implemented as program instructions executable by a variety of computers and recorded on a computer readable medium. The computer readable medium may include a program instruction, a data file, a data structure, or a combination thereof. The program instructions recorded on the computer readable medium may be designed and configured specifically for the present invention or can be publicly known and available to those who are skilled in the field of computer software.
- Examples of the computer readable medium may include a hardware device such as ROM, RAM, and flash memory, which are specifically configured to store and execute the program instructions. Examples of the program instructions include machine codes made by, for example, a compiler, as well as high-level language codes executable by a computer, using an interpreter. The above exemplary hardware device can be configured to operate as at least one software module in order to perform the operation of the present invention, and vice versa.
- According to an embodiment of the present invention, it is possible to easily determine a state (that is, a normal state or a fault state) of each of communication nodes constituting a vehicle network and a state of a channel (or port) to which the communication node is connected. A communication node and channel in a fault state may be quickly repaired based on the determination result. Thus the performance of the vehicle network may be enhanced.
- While the example embodiments of the present invention and their advantages have been described in detail, it should be understood that various changes, substitutions and alterations may be made herein without departing from the scope of the invention.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/802,741 US10749738B2 (en) | 2014-07-18 | 2015-07-17 | Method and apparatus for diagnosing network |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201462026335P | 2014-07-18 | 2014-07-18 | |
US201462026343P | 2014-07-18 | 2014-07-18 | |
KR2015-0098909 | 2015-07-13 | ||
KR1020150098909A KR102337548B1 (en) | 2014-07-18 | 2015-07-13 | Method for diagnosing network and apparatus for the same |
US14/802,741 US10749738B2 (en) | 2014-07-18 | 2015-07-17 | Method and apparatus for diagnosing network |
Publications (3)
Publication Number | Publication Date |
---|---|
US20170019295A1 US20170019295A1 (en) | 2017-01-19 |
US20190190772A9 true US20190190772A9 (en) | 2019-06-20 |
US10749738B2 US10749738B2 (en) | 2020-08-18 |
Family
ID=55021993
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/802,741 Active 2036-09-19 US10749738B2 (en) | 2014-07-18 | 2015-07-17 | Method and apparatus for diagnosing network |
Country Status (3)
Country | Link |
---|---|
US (1) | US10749738B2 (en) |
KR (1) | KR102337548B1 (en) |
DE (1) | DE102015213378A1 (en) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10298540B2 (en) * | 2016-04-01 | 2019-05-21 | Lg Electronics Inc. | Method and network node for transmitting IP address information, and method and user equipment for receiving IP address information |
KR102300764B1 (en) * | 2016-09-12 | 2021-09-10 | 현대자동차주식회사 | Diagnostic methods and devices in vehicle network |
KR102286050B1 (en) * | 2017-06-23 | 2021-08-03 | 현대자동차주식회사 | Method for preventing diagnostic errors in vehicle network and apparatus for the same |
WO2019239189A1 (en) * | 2018-06-13 | 2019-12-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Robust node failure detection mechanism for sdn controller cluster |
KR102536586B1 (en) | 2018-09-20 | 2023-05-26 | 삼성전자주식회사 | Electronic device using a wifi communication and method of operating the same |
CN111835627B (en) * | 2019-04-23 | 2022-04-26 | 华为技术有限公司 | Communication method of vehicle-mounted gateway, vehicle-mounted gateway and intelligent vehicle |
CN110635958B (en) * | 2019-11-05 | 2022-04-29 | 北京知道创宇信息技术股份有限公司 | Network fault diagnosis method, device and storage medium |
US11768728B2 (en) * | 2021-12-16 | 2023-09-26 | Nio Technology (Anhui) Co., Ltd. | Routing multiple diagnostic pathways |
CN114338464A (en) * | 2021-12-30 | 2022-04-12 | 深圳Tcl新技术有限公司 | Fault diagnosis method, device, equipment and computer readable storage medium |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030033463A1 (en) * | 2001-08-10 | 2003-02-13 | Garnett Paul J. | Computer system storage |
DE10145906A1 (en) * | 2001-09-18 | 2003-04-10 | Bosch Gmbh Robert | Method for carrying out remote diagnosis in a motor vehicle, vehicle diagnosis module and service center |
US8279759B1 (en) * | 2005-03-07 | 2012-10-02 | Verizon Services Corp. | Protocol inter-worked ping mechanism |
US20080002691A1 (en) * | 2006-06-29 | 2008-01-03 | Qi Emily H | Device, system and method of multicast/broadcast communication |
US7903569B2 (en) * | 2008-11-25 | 2011-03-08 | At&T Intellectual Property I, L.P. | Diagnosing network problems in an IPV6 dual stack network |
JP2010206697A (en) * | 2009-03-05 | 2010-09-16 | Honda Motor Co Ltd | Onboard communication network system and malfunction diagnostic method of the same |
CN101699410B (en) | 2009-11-11 | 2012-07-18 | 中兴通讯股份有限公司 | Single plate hardware fault detection method and device |
JP5637190B2 (en) * | 2012-07-27 | 2014-12-10 | トヨタ自動車株式会社 | Communication system and communication method |
KR101427872B1 (en) * | 2012-12-20 | 2014-08-08 | 현대오트론 주식회사 | System and method for transmitting and receiving data based on ethernet |
US20150227404A1 (en) * | 2014-02-11 | 2015-08-13 | Wipro Limited | Systems and methods for smart service management in a media network |
CN105141434B (en) * | 2014-05-26 | 2019-03-26 | 华为技术有限公司 | The fault detection method and device of business chain |
-
2015
- 2015-07-13 KR KR1020150098909A patent/KR102337548B1/en active IP Right Grant
- 2015-07-16 DE DE102015213378.8A patent/DE102015213378A1/en active Pending
- 2015-07-17 US US14/802,741 patent/US10749738B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
KR102337548B1 (en) | 2021-12-08 |
DE102015213378A1 (en) | 2016-01-21 |
US10749738B2 (en) | 2020-08-18 |
US20170019295A1 (en) | 2017-01-19 |
KR20160096526A (en) | 2016-08-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10749738B2 (en) | Method and apparatus for diagnosing network | |
US10212234B2 (en) | Operation method of communication node in network | |
US10382221B2 (en) | Communication method based on automotive safety integrity level in vehicle network and apparatus for the same | |
US10693668B2 (en) | Operation method of communication node in network | |
US10484235B2 (en) | Power management method in network and apparatus for the same | |
KR102234210B1 (en) | Security method for ethernet based network | |
US10715423B2 (en) | Method of transmitting data based on priorities in network | |
US11063868B2 (en) | Operation method of a communication node in network | |
US10715417B2 (en) | Method for configuring stream communication path in network | |
KR20160025452A (en) | Operation method of communication node in network | |
US20180145848A1 (en) | Method and apparatus for reproducing contents based on presentation time in automotive network | |
KR102446092B1 (en) | Method for diagnosing link status in network | |
US10764210B2 (en) | Operation method of communication node for mirroring in vehicle network | |
KR102355085B1 (en) | Operation method of communication node for selective wakeup in vehicle network | |
US11330057B2 (en) | Operation methods of communication node in network | |
KR102162288B1 (en) | Communication method based on multi path in network | |
KR102362611B1 (en) | Method for transmitting and receiving data in automotive network and apparatus for the same | |
KR102610921B1 (en) | Method and apparatus for setting backup path in automotive network | |
KR102233213B1 (en) | Method for setting communication path of stream in network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: HYUNDAI MOTOR COMPANY, KOREA, REPUBLIC OF Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KIM, DONG OK;SEO, KANG WOON;CHAE, JUN BYUNG;AND OTHERS;REEL/FRAME:036151/0667 Effective date: 20150713 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
FEPP | Fee payment procedure |
Free format text: PETITION RELATED TO MAINTENANCE FEES GRANTED (ORIGINAL EVENT CODE: PTGR); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |