JP2005159864A - Data communication system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To manage sleep/wake-up statuses of all nodes in a system where nodes of different status management schemes are mixed. <P>SOLUTION: The data communication system comprises a gateway device so that, in sleep transition, when sleep conditions are established in all the nodes corresponding to one status management scheme, the sleep status is notified according to the other status management scheme and when sleep conditions are established in all the nodes corresponding to the other status management scheme, the sleep status is notified according to the one status management scheme. In wake-up transition, when a wake-up condition is established in at least one node corresponding to the one status management scheme, the wake-up status is notified according to the other status management scheme and when a wake-up condition is established in at least one node corresponding to the other status management scheme, the wake-up status is notified according to the one status management scheme. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a data communication system in which nodes arranged in various parts of a vehicle or the like are connected by a network, and more particularly to network management between two network systems having different status management methods.

  Conventionally, there is known a vehicular data communication system in which nodes such as a switch system node, a lamp system node, and a meter system node arranged in each part in a vehicle are connected by a network. In this system, a unique ID (identification information) is assigned to each node, and each node periodically transmits a data frame to which a unique ID is added to other nodes via the network. Multiple communication can be performed.

As a system for performing such multiplex communication, there is a multiplex transmission apparatus that can efficiently allocate data IDs by sharing one data ID among a plurality of nodes (see, for example, Patent Document 1).
JP 2000-83033 A

  In the data communication system as described above, each node identifies a data frame transmitted from another node by an ID, and receives each ID by a separate reception buffer. Thereby, the status (sleep / wake-up) of all other nodes can be managed in each node.

  However, with the diversification of functions, a new system may be connected to an existing system. That is, this is a case where a new system configured by nodes having a status management method different from that of the existing system is integrated into the existing system.

  When system integration as described above is performed, each node corresponding to the existing system cannot recognize the status even if it receives a frame transmitted from the node corresponding to the new system, and sleep / You cannot manage wakeups. Similarly, each node corresponding to the new system cannot recognize the status even if it receives a frame transmitted from a node corresponding to the existing system, and cannot manage sleep / wakeup. It can happen.

  Therefore, when building a system with a mix of nodes with different status management methods by integrating an existing system with a new system, change the software on all nodes connected to the existing system to It is necessary to be able to recognize the status of the node corresponding to the system, resulting in an increase in cost and an increase in development man-hours.

  Here, the existing system is described as “existing system”, and the newly constructed system is described as “new system”. However, the meanings of “existing system” and “new system” are described above. The present invention is not limited, and the same problem may occur when the status management methods are different even in the integration of existing systems or newly constructed systems.

  An object of the present invention is to provide a data communication system capable of managing sleep / wake-up of all nodes in a system in which nodes having different status management methods coexist.

  In order to solve the above-mentioned problem, the invention of claim 1 is characterized in that a first node group consisting of a plurality of nodes whose sleep / wake-up is controlled by a first status management method, and a sleep / wakeup by a second status management method. In a data communication system in which a second node group consisting of a plurality of nodes whose wake-up is controlled is connected on a transmission line, when a sleep condition is established in all nodes belonging to the first node group, When each node belonging to the second node group is notified of a sleep state according to the second status management method, and when a sleep condition is established in all nodes belonging to the second node group, Notifying each node belonging to the first node group of a sleep state in accordance with the first status management method, and the first node When the wake-up condition is satisfied in at least one node belonging to the second node group, a wake-up state is notified to each node belonging to the second node group according to the second status management method. When the wake-up condition is satisfied in at least one node belonging to the second node group, the wake-up state is notified to each node belonging to the first node group according to the first status management method. A gateway device is provided.

  According to a second aspect of the present invention, in the first aspect, when the gateway device receives a data frame including status information indicating that the sleep condition is established from all nodes belonging to the first node group, the second node Status frame including status information that does not satisfy sleep condition is stopped for each node that belongs to the group, and status frame that includes status information that does not satisfy the sleep condition from the node belonging to the second node group Is not received for a predetermined period of time, a data frame including status information indicating that the sleep condition is established is transmitted to each node belonging to the first node group, and at least one belonging to the first node group. When a data frame including status information indicating that the sleep condition is not satisfied is received from one node, the second A status frame including status information indicating that the sleep condition is not satisfied is transmitted to each node belonging to the node group, and a status frame including status information indicating that the sleep condition is not satisfied is received from the node belonging to the second node group. In this case, a data frame including status information indicating that the sleep condition is not satisfied is transmitted to each node belonging to the first node group.

  According to a third aspect of the present invention, in the first or second aspect, each node belonging to the first node group, as a first status management method, satisfies the sleep condition when the sleep condition of the own node is satisfied. When a data frame including status information is transmitted and a data frame including status information that does not satisfy the sleep condition is not received from another node or the gateway device within a predetermined time, a transition is made to the sleep state and the own node is woken up. When the condition is satisfied, a data frame including status information indicating that the sleep condition is not satisfied is transmitted after a predetermined time elapses, and the wakeup state is entered. Each node belonging to the second node group receives a second status. As a management method, when the sleep condition of the own node is satisfied, status information indicating that the sleep condition is not satisfied is displayed. When the status frame containing status information that does not satisfy the sleep condition is not received from another node or the gateway device within a predetermined time, the process shifts to the sleep state, and the wake-up condition of the own node When is established, a status frame including status information indicating that the sleep condition is not established is transmitted after a predetermined time has elapsed, and the wakeup state is entered.

  According to a fourth aspect of the present invention, in any one of the first to third aspects, each node belonging to the first node group has a first status management method in which a sleep condition is not established or is not established in a wake-up state. A data frame including status information indicating that the sleep condition has been established is periodically transmitted. In the sleep state, the periodic transmission of the data frame is stopped, and each node belonging to the second node group has a second status management method as follows: In the wake-up state, a status frame including status information indicating that the sleep condition is not satisfied is periodically transmitted. In the sleep state, the periodic transmission of the status frame is stopped.

  A fifth aspect of the present invention is the data frame creation means according to any one of the second to fourth aspects, wherein the gateway device creates at least a data frame including status information indicating that the sleep condition is satisfied or not. A status frame creating means for creating a status frame including status information that the sleep condition is not satisfied; and a data frame or a status frame created by the own apparatus connected to the transmission path and transmitted to another node. A communication control unit that receives a data frame or a status frame transmitted from the network, a plurality of data reception buffers that receive the data frame transmitted from another node, and the status frame transmitted from another node Status reception buffer and received frame The type of the frame is determined based on the identification information included in the received information. If the received frame is a data frame, the received frame is received in the data reception buffer specified by the identification information, and the received frame is a status frame. For example, when receiving a data frame including status information indicating that a sleep condition is established from all nodes belonging to the first node group in a wake-up state, the status identification frame received in the status reception buffer When the status frame is not received from a node belonging to the second node group for a predetermined time, a process of transmitting a data frame including status information indicating that the sleep condition is established is executed. , At least belonging to the first node group When a data frame including status information that does not satisfy the sleep condition is received from one node, the status frame is transmitted, and when the status frame is received from a node belonging to the second node group, sleep And an ID management unit that executes a process of transmitting a data frame including status information that does not satisfy the condition.

  The invention of claim 6 is characterized in that, in any one of claims 1 to 5, the gateway device is provided in one node belonging to the first node group or the second node group. To do.

  A seventh aspect of the present invention is characterized in that, in any one of the first to sixth aspects, the node provided with the gateway device is a display system node.

  According to the present invention, by providing a gateway device corresponding to a different status management method, it is possible to manage sleep / wakeup for all nodes in the system, so that the existing system and the new system are integrated. Thus, when constructing a system in which nodes with different status management methods coexist, it is not necessary to change the software of all the nodes belonging to the existing system, thereby reducing costs and reducing development man-hours.

  Hereinafter, an embodiment when the data communication system according to the present invention is applied to a vehicular data communication system will be described.

  FIG. 1 is an overall configuration diagram of a vehicular data communication system according to the present embodiment. On a bus line (transmission path) 40 for transmitting and receiving data, nodes 11A, 11B, and 11C and nodes 21A, 21B, and 21C corresponding to each electrically controlled device are connected. Each node corresponds to, for example, a switch system node, a lamp system node, a meter system node, a door control system node, and the like.

  In this embodiment, the nodes 11A, 11B, and 11C are a first node group whose sleep / wake-up is controlled by the first status management method, and are referred to as a first network management system (hereinafter referred to as a first NM system). ) Is managed as a node belonging to 10. The nodes 21A, 21B, and 21C are a second node group whose sleep / wake-up is controlled by the second status management method, and are connected to a second network management system (hereinafter referred to as a second NM system) 20. Managed as a node to which it belongs.

  Since the first NM system 10 and the second NM system 20 have different status management methods, it is not possible to manage sleep / wake-up based on data frames transmitted from the other system. Therefore, each node belonging to each system does not execute processing for the data frame received from the node of the counterpart system.

  In the following description, the nodes 11A to 11C are collectively referred to as “node 11”, and the nodes 21A to 21C are collectively referred to as “node 21”. Further, the nodes 11A to 11C and the nodes 21A to 21C are collectively referred to as “nodes”.

  The gateway device (hereinafter referred to as GW) 30 manages the status (sleep / wake-up) regarding all nodes belonging to the first NM system 10 and the second NM system 20 connected on the common bus line 40. Execute. The configuration and operation of the gateway device 30 will be described later.

  Next, the configuration of the node 11 belonging to the first NM system 10 and the status management method will be described.

  FIG. 2 is a block diagram illustrating a functional configuration of the node 11, and illustrates a configuration of an arbitrary one of the nodes 11A, 11B, and 11C.

  The node 11 includes a communication IC 12, a buffer unit 13, a status control unit 14, and a CPU 15, and is further connected to a functional unit 16 corresponding to the above-described switch and lamp.

  The communication IC 12 is connected to the bus line 40, receives a frame transmitted from another node 11 or GW 30 belonging to the first NM system 10, and transmits a frame created by the own node from the bus line 40. In the communication IC 12, when the bus line 40 is an optical fiber cable, an electrical signal-optical signal conversion process is performed.

  The buffer unit 13 includes a data reception buffer for receiving a data frame transmitted from another node 11 or GW 30 belonging to the first NM system 10.

  The status control unit 14 refers to data transmitted from the function unit 16 and a reception buffer (to be described later) of the buffer unit 13 to control sleep / wakeup of the own node.

  The CPU 15 executes various controls according to the data from the function unit 16 and adds a data frame by adding data from the function unit 16 connected to the own node and a unique ID for identifying this data. Processing as a data frame creation means to be created is executed.

  In FIG. 2, in order to make the functions realized by the node 11 easy to understand, the CPU 15 and the status control unit 14 are shown for each function. However, these functions may be realized by a single-chip CPU. .

  Next, the first status management method will be described. FIG. 3 is an explanatory diagram showing a data structure of a data frame in the first status management method. The data frame includes a header part that is an ID unique to each node and a data part that indicates the state of the function part 16. The header part consists of 11 bits, and is composed of a 3-bit data ID and an 8-bit physical node address (source address). The data ID in this embodiment is fixed at “011”. The data portion is composed of a 2-bit status (status information) and 1 to 8 bytes of data. In this embodiment, the status is “00” when the sleep condition is satisfied, and the status is “01” when the sleep condition is not satisfied.

  In the normal transmission standby state (wake-up state), the node 11 periodically transmits a data frame including the status “01” in which the sleep condition is not satisfied at regular intervals (for example, every 100 ms). When the sleep condition of the own node is satisfied, a data frame including a status “00” indicating that the sleep condition is satisfied is transmitted, and the sleep condition is not satisfied from another node 11 or GW 30 within a predetermined time (for example, 200 ms). When the data frame including the status “01” is not received, the sleep mode is entered. Then, after shifting to the sleep state, the transmission of the data frame including the status that the sleep condition is satisfied or the sleep condition is not satisfied is stopped. Further, when the wake-up condition of the own node is satisfied, after a predetermined time (for example, 50 ms) elapses, a data frame including the status “01” in which the sleep condition is not satisfied is transmitted, and the normal transmission standby state is entered.

  Here, the reception buffer of the node 11 will be described. As shown in FIG. 3, the reception buffer for data reception provided in the node 11 includes reception buffers 1 to 3. Among these, the reception buffers 1 and 2 are buffers for receiving data frames transmitted from the other two nodes 11 belonging to the first NM system 10, and the reception buffer 3 is transmitted from the GW 30. This is a buffer for receiving incoming data frames. Each node 11 refers to the 11 bits of the header portion of the received data frame, and stores the data frame in the reception buffers 1 to 3 for receiving data specified by the 11 bits. In these reception buffers, received data frames are sequentially overwritten. That is, the contents of the reception buffers 1 to 3 are updated in real time.

  The sleep / wake-up control described above shows the basic operation in the first status management method, and actually other frame transmission and internal control are executed.

  Next, the configuration of the node 21 belonging to the second NM system 20 and the status management method will be described.

  FIG. 4 is a block diagram showing a functional configuration of the node 21, and shows a configuration of any one of the nodes 21A, 21B, and 21C.

  The node 21 includes a communication IC 22, a frame identification unit 23, a buffer unit 24, a status control unit 25, and a CPU 26, and is further connected to a functional unit 27 corresponding to the above-described switch and lamp.

  The communication IC 22 is connected to the bus line 40, receives a frame transmitted from another node 21 or GW 30 belonging to the second NM system 20, and sends a frame created by the own node to each node and the GW 30. Send. In the communication IC 22, when the bus line 40 is an optical fiber cable, an electrical signal-optical signal conversion process is performed.

  The frame identification unit 23 refers to the ID (identification information) of a frame transmitted from another node 21 or GW 30 belonging to the second NM system 20, and identifies whether the frame is a data frame or a status frame. . Here, when the ID bit string includes “1” at the head, it is determined as a status frame and received in a reception buffer for status reception (not shown) of the buffer unit 24. Further, if the ID bit string does not include “1” at the head, for example, “011...”, It is determined as a data frame, and the buffer unit 24 is identified by 11 bits of the ID (not shown) Receive in the receive buffer for data reception. The data structure of the status frame will be described later.

  The buffer unit 24 receives a data frame transmitted from another node 21 belonging to the second NM system 20 and the GW 30, and receives a data frame, and a status for receiving a status frame. And a reception buffer for reception.

  The status control unit 25 refers to data transmitted from the function unit 27 and a reception buffer (to be described later) of the buffer unit 24 to control sleep / wakeup of the own node.

  The CPU 26 executes various controls according to the data from the function unit 27, and adds a data frame by adding data from the function unit 27 connected to its own node and a unique ID for identifying this data. Processing as data frame creation means to be created and processing as status frame creation means for creating a status frame by adding the ID to the current status (sleep / wakeup) of the own node are executed.

  In FIG. 4, in order to make it easy to understand the functions realized by the node 21, the CPU 26, the status control unit 25, and the frame identification unit 23 are shown for each function. However, these functions are realized by a one-chip CPU. It may be.

  Next, the second status management method will be described. FIG. 5 is an explanatory diagram showing the data structure of the data frame and the status frame.

  In the present embodiment, the structure of the data frame in the second NM system 20 is the same as that of the first NM system 10 (see FIG. 3), and the 2-bit data portion contains a status “00” when the sleep condition is satisfied. ", Or when the sleep condition is not established, the status" 01 "is set.

  On the other hand, the header part of the status frame consists of 11 bits, and is composed of a 3-bit status ID and an 8-bit physical node address. In this embodiment, the status ID is fixed at “111”, and the status of the data portion is fixed at “01”, where the sleep condition is not satisfied. In the following description, a status frame including the status “01” in which the sleep condition is not satisfied is appropriately abbreviated as “status frame”.

  In the normal transmission standby state, the node 21 periodically transmits a data frame including a status “01” in which the sleep condition is not satisfied and a status frame at regular intervals (for example, every 100 ms). Further, when the sleep condition of the own node is satisfied, the periodic transmission of the status frame is stopped, and when the status frame is not received from another node 21 or the GW 30 within a predetermined time (for example, 200 ms), the sleep state is entered. Transition. After shifting to the sleep state, transmission of not only the status frame but also the data frame is stopped. Further, when the wake-up condition of the own node is satisfied, after a predetermined time (for example, 50 ms) elapses, the status frame is transmitted and the normal transmission standby state is entered.

  Here, the reception buffer of the node 21 will be described. As shown in FIG. 5, the reception buffer for data reception provided in the node 21 includes reception buffers 1 to 4. Among these, the reception buffer 1 is a buffer for receiving status frames transmitted from the other two nodes 21 or GWs 30 belonging to the second NM system 20. The reception buffers 2 and 3 are buffers for receiving data frames transmitted from the other two nodes 21 belonging to the second NM system 20, and the reception buffer 4 is transmitted from the GW 30. This is a buffer for receiving data frames.

  When the node 21 receives a frame from another node 21 or the GW 30, it identifies whether it is a data frame or a status frame based on the header portion of the frame. For example, when the header portion of the received frame includes “1” at the head, it is determined as a status frame and is received by the reception buffer 1 for status reception in the buffer unit 24. In this case, since it is not necessary for the node 21 to recognize from which node the status frame is transmitted, if the leading bit is “1”, the header portion is masked with “1xxxxxxxxxx” (after that) The status frame is received by the reception buffer 1 for status reception. In this way, control for masking and receiving a part of the header part is provided as a mask function of the CAN controller, for example.

  Further, by analyzing the 11-bit header portion using a reading tool, it is possible to determine from which node the status frame is transmitted.

  Status frames received from other nodes 21 or GWs 30 are sequentially overwritten in the reception buffer 1 for status reception. The status control unit 25 periodically reads out from the reception buffer 1 for status reception to check whether or not a status frame has been received.

  Further, if the header portion of the received frame is a bit string such as “011...” That does not include “1” at the head, it is determined as a data frame, and reception for data reception specified by 11 bits of the header portion is performed. Data frames are stored in buffers 2-4. In the reception buffers 2 to 4 for receiving data, data frames received from the corresponding nodes 21 or GWs 30 are overwritten sequentially. That is, the contents of the reception buffers 1 and 2 to 4 are updated in real time.

  The sleep / wake-up control described above shows the basic operation in the second status management method, and actually other frame transmission and internal control are executed.

  In the second NM system 20 described above, status frames for status management are transmitted and received between each node 21 and GW 30, and status frames from other nodes 21 and GW 30 are shared by using a common reception buffer using an existing mask function. In this way, each node 21 and GW 30 recognizes its status and manages its sleep / wake-up even when an unexpected node (a node whose ID cannot be identified) that is not assumed at the time of system construction is connected. can do.

  According to this, it is not necessary to change the software of all the nodes 21 and GWs 30 connected to the system every time an unexpected node is connected, and this does not cause an increase in cost or an increase in development process. Further, since there is no need to have dedicated reception buffers as many as the number of connected nodes, the number of reception buffers can be reduced, and the expandability of the system can be improved.

  The second NM system 20 can manage the sleep / wakeup of other nodes by referring to not only the status frame but also the status that the sleep condition is satisfied / sleep condition is not included in the data frame. it can. Therefore, when the first NM system 10 is an existing system and the second NM system 20 is a new system, each node 21 belonging to the second NM system 20 does not have to go through the GW 30, It is possible to identify the ID of each node 11 belonging to one NM system 10 and receive each ID by an individual reception buffer. In this case, it is necessary to provide reception buffers corresponding to all connected nodes. However, when managing sleep / wake-up of other nodes using only status frames, only a common reception buffer is required. The buffer capacity can be reduced.

  Next, a processing procedure when controlling sleep / wakeup in the nodes 11 and 21 belonging to each of the systems will be described.

  FIG. 6 is a flowchart showing a processing procedure when a wakeup transition is made in the node 11 belonging to the first NM system 10.

  The status control unit 14 of the node 11 determines whether or not the wakeup condition in the node 11 is established (step S1), and if Yes, transmits a wakeup ID code (step S2). The wakeup ID code is a data frame dedicated to wakeup transmitted when a wakeup event occurs, and is transmitted before transmitting a data frame including a status “01” in which the sleep condition is not satisfied.

  When 50 ms elapses after transmitting the wakeup ID code (Yes in step S3), the CPU 15 creates a data frame including a status “01” indicating that the sleep condition is not satisfied, and transmits the data frame to the other nodes 11 and the GW 30 (step S4). . After the data frame transmission, the normal transmission standby state is entered (step S5).

  The normal transmission standby state refers to a state in which data frames and the like can be transmitted / received between the other nodes 11 and the GW 30. Thereafter, the node 11 periodically transmits a data frame including a status “01” in which the sleep condition is not satisfied until the sleep condition of the node 11 is satisfied.

  The processing from the above steps S1 to S5 indicates a wake-up transition from the own node.

  On the other hand, if NO in step S1, it is determined whether a wakeup ID code has been received from another node 11 or GW 30 (step S6). If NO, the process ends. If Yes, the process shifts to the wake-up standby state (step S7), and whether or not a data frame including the status “01” indicating that the sleep condition is not satisfied is received from another node 11 or the GW 30 by 100 ms. Judgment is made (steps S8 and S9). Here, when the data frame is received before 100 ms elapses (Yes in step S8), the process shifts to a normal transmission standby state (step S5). When 100 ms elapses without receiving the data frame (Yes in step S9), the process shifts to the sleep state (step S10) and the process is terminated.

  The processes in steps S6 to S10 indicate a wake-up transition from another node 11 or GW 30.

  FIG. 7 is a flowchart illustrating a processing procedure when the sleep transition is performed. The status control unit 14 of the node 11 determines whether or not the sleep condition in the node 11 is established (step S11), and if Yes, periodically transmits a data frame including the sleep condition establishment status “00”. (Step S12), it is determined whether or not a data frame including a status “01” indicating that the sleep condition is not satisfied is received from another node 11 or the GW 30 by the elapse of 200 ms (Steps S13 and S14). Here, when the data frame is received before 200 ms elapses (Yes in step S13), the process is terminated without shifting to the sleep state (the same is true when No in step S11). On the other hand, when 200 ms elapses without receiving the data frame (Yes in step S14), the process shifts to a sleep standby state (step S15). Thereafter, when 3 seconds have passed (Yes in step S16), the process shifts to the sleep state (step S17). After shifting to the sleep state, the periodic transmission of the data frame including the status “00” indicating that the sleep condition is established is stopped.

  FIG. 8 is a flowchart showing a processing procedure when a wake-up transition is performed in the node 21 belonging to the second NM system 20.

  The status control unit 25 of the node 21 determines whether or not the wakeup condition at the node is established (step S21), and if Yes, transmits the wakeup ID code (step S22).

  When 50 ms elapses after transmitting the wakeup ID code (Yes in step S23), the CPU 26 creates a status frame and transmits it to the other nodes 21 and the GW 30 (step S24). After the status frame is transmitted, the normal transmission standby state is entered (step S25). Thereafter, the node 21 periodically transmits a data frame and a status frame including a status “01” in which the sleep condition is not satisfied until the sleep condition of the own node is satisfied.

  The processing from step S21 to step S25 indicates a wake-up transition from the own node.

  On the other hand, if NO in step S21, it is determined whether a wake-up ID code has been received from another node 21 or GW 30 (step S26). If NO, the process ends. If Yes, the process shifts to a wake-up standby state (step S27), and whether or not a status frame has been received from another node 21 or GW 30 is determined whether or not 100 ms has elapsed (step S28, S29). Here, when a status frame is received before 100 ms has elapsed (Yes in step s28), a transition is made to a normal transmission standby state (step S25). If 100 ms elapses without receiving the status frame (Yes in step S29), the process shifts to the sleep state (step S30) and the process is terminated.

  The processing from step S26 to step S30 indicates a wake-up transition from another node 21 or GW 30.

  FIG. 9 is a flowchart illustrating a processing procedure when the sleep transition is performed. Here, transmission / reception of a data frame including the status “01” in which the sleep condition is not satisfied will be omitted.

  The status control unit 25 of the node 21 determines whether or not the sleep condition in the node 21 is established (step S31), and if yes, stops the periodic transmission of the status frame (step S32), and other nodes 21 Alternatively, it is determined whether a status frame from the GW 30 has been received before 200 ms has elapsed (steps S33 and S34). Here, when the status frame is received before 200 ms elapses (Yes in step S33), the process is terminated without shifting to the sleep state (the same applies to the case of No in step S31). On the other hand, when 200 ms elapses without receiving a status frame (Yes in step S34), the process shifts to a sleep standby state (step S35). Thereafter, when 3 seconds have passed (Yes in step S36), the process shifts to the sleep state (step S37).

  In step S32, even after the periodic transmission of the status frame is stopped, the transmission of the data frame including the status “00” indicating that the sleep condition is established is continued until the status frame is shifted to the sleep state.

  In the second NM system 20, the periodic transmission of only the status frame is stopped when the sleep condition is satisfied, and the periodic transmission of the data frame is continued until the sleep state is shifted to. This is because if the periodic transmission of data frames is stopped when the sleep condition is met, the frame transmission is stopped by sleep when the communication is interrupted after communication of the status frame (communication is disabled due to an error, etc.). This is because it cannot be determined whether or not a communication interruption has occurred on the bus line. Therefore, even if the periodic transmission of the status frame is stopped, the cause of the communication interruption can be determined by continuing the periodic transmission of the data frame. In this case, if the status in the data frame immediately before the communication interruption is “00”, it is considered that the sleep condition has already been established, and therefore it can be determined that there is no problem even if the communication is interrupted. On the other hand, if the status in the data frame immediately before the communication interruption is “01”, it can be determined that an error occurs during communication (application operation), and therefore it is necessary to take an appropriate measure for the application at that node. For example, when it is determined that an error has occurred during the closing operation of the auto slide door, a measure such as stopping the door drive is taken.

  Next, the configuration of the GW 30 and status management for each NM system will be described.

  FIG. 10 is a block diagram illustrating a functional configuration of the GW 30. The GW 30 includes a communication IC 31, a frame identification unit 32, a buffer unit 33, an ID management unit 34, and a CPU 35.

  The communication IC 31 is connected to the bus line 40 and receives frames transmitted from the node 11 belonging to the first NM system 10 and the node 21 belonging to the second NM system 20 and is created by each unit described later. The frame thus transmitted is transmitted to the node 11 belonging to the first NM system 10 and the node 21 belonging to the second NM system 20 via the bus line 40. In the communication IC 31, when the bus line 40 is an optical fiber cable, an electrical signal-optical signal conversion process is performed.

  The frame identification unit 32 refers to the ID (identification information) of the frame transmitted from the node 21 belonging to the second NM system 20 and identifies whether the frame is a data frame or a status frame. Here, when the ID bit string includes “1” at the head, it is determined as a status frame and received in a reception buffer for status reception (not shown) of the buffer unit 33. Further, if the ID bit string does not include “1” at the head, for example, “011...”, It is determined as a data frame, and the buffer unit 33 is identified by 11 bits of the ID (not shown) Receive in the receive buffer for data reception. Since the GW 30 recognizes the IDs of all nodes belonging to the first NM system 10 and the second NM system 20, by referring to the header part of the received data frame, It is possible to specify the transmitting node and the NM system to which the node belongs.

  The buffer unit 33 is used for data reception for receiving a data frame transmitted from the node 11 belonging to the first NM system 10 and a data frame transmitted from the node 21 belonging to the second NM system 20. A reception buffer and a status reception buffer for receiving a status frame transmitted from the node 21 belonging to the second NM system 20 are provided (not shown).

  When the ID management unit 34 receives the data frame including the status “00” indicating that the sleep condition is satisfied from all the nodes 11 belonging to the first NM system 10 with reference to the buffer unit 33, the ID management unit 34 transmits the status frame. A transmission stop request is issued to the CPU 35 so as to stop. That is, the GW 30 transmits a status frame (to each node 21) while receiving a data frame including the status “01” that does not satisfy the sleep condition from the node 11 belonging to the first NM system 10. Therefore, when all the nodes 11 belonging to the first NM system 10 are in the sleep standby state, the status frame is not transmitted.

  When a status frame is not received from the node 21 belonging to the second NM system 20 for a predetermined time, a transmission request is issued to the CPU 35 so as to transmit a data frame including a status “00” that satisfies the sleep condition. . That is, while receiving a status frame from the node 21 belonging to the second NM system 20, the GW 30 transmits a data frame including the status “01” that the sleep condition is not satisfied (to each node 11). Therefore, when all the nodes 21 belonging to the second NM system 20 enter the sleep standby state, a data frame including the status “00” indicating that the sleep condition is satisfied is transmitted.

  When a data frame including a status “01” that does not satisfy the sleep condition is received from at least one node 11 belonging to the first NM system 10, a status frame is transmitted (to each node 21). As described above, a transmission request is issued to the CPU 35.

  Further, when a status frame is received from the node 21 belonging to the second NM system 20, the CPU 35 is configured to transmit a data frame including a status “01” in which the sleep condition is not satisfied (to each node 11). Issue a send request.

  The CPU 35 controls the entire GW 30 and, in response to the transmission stop request issued from the ID management unit 34, stops the transmission of the status frame from the communication IC 31 and the transmission request issued from the ID management unit 34. In response, processing as data frame creation means for creating a data frame including a status “01” indicating that the sleep condition is not satisfied, or a data frame including a status “00” indicating that the sleep condition is satisfied, and issued from the ID management unit 34 In response to the transmission request, processing as status creating means for creating a status frame is executed.

  In FIG. 10, in order to make the functions realized by the GW 30 easier to understand, the functions are shown as the frame identification unit 32, the ID management unit 34, and the CPU 35 for each function. However, these functions are realized by a single-chip CPU. There may be.

  Next, a processing procedure for controlling sleep / wakeup between the first NM system 10 and the second NM system 20 in the GW 30 will be described. Here, only the exchange of frames necessary for sleep / wakeup control will be described, and description of other processes, such as the process of identifying received frames, and transmission / reception of wakeup ID codes, etc. will be omitted. To do.

  FIG. 11 is a flowchart showing a processing procedure when a wake-up transition is made between both NM systems.

  When the GW 30 receives a data frame including the status “01” indicating that the sleep condition is not satisfied from the node 11 belonging to the first NM system 10 (Yes in Step S41), after 30 ms has elapsed (Yes in Step S42), A status frame is created and transmitted from the bus line 40 to each node (step S43). By transmitting this status frame, each node 21 belonging to the second NM system 20 can recognize that there is a node on the bus line 40 where the sleep condition is not satisfied. If No in step S41, it is determined whether a status frame has been received from the node 21 belonging to the second NM system 20 (step S44). If No, the process ends. If Yes, after 30 ms have elapsed (Yes in step S45), a data frame including a status “01” indicating that the sleep condition is not satisfied is created and transmitted from the bus line 40 (step S46). By transmitting this data frame, each node 11 belonging to the first NM system 10 can recognize that there is a node on the bus line 40 where the sleep condition is not satisfied.

  FIG. 12 is a flowchart showing a processing procedure when a sleep transition is made between both NM systems.

  The GW 30 refers to the reception buffers of all the nodes 11 belonging to the first NM system 10, and when all the statuses are the status “00” indicating that the sleep condition is established (Yes in step S51), transmits the status frame. Is stopped (step S52). That is, since the GW 30 transmits a status frame from the node 11 belonging to the first NM system 10 while receiving a data frame including the status “01” indicating that the sleep condition is not satisfied, By stopping the frame transmission, the node 21 belonging to the second NM system 20 can determine the transition to the sleep standby state as shown in FIG. If NO in step S51, it is determined whether a status frame has been received from the node 21 belonging to the second NM system 20 (step S53). If YES, the process ends. If “No”, after 30 ms has elapsed (Yes in step S54), a data frame including a status “00” indicating that the sleep condition is satisfied is created and transmitted from the bus line 40 (step S55). By transmitting this data frame, each node 11 belonging to the first NM system 10 recognizes that the sleep condition has been established in all the nodes 21 belonging to the second NM system 20 managed by the GW 30. Can do.

  As described above, it is possible to manage sleep / wake-up for all nodes by providing a gateway apparatus corresponding to each status management system in a data communication system in which nodes having different status management systems are mixed. Therefore, when connecting a new system configured with an unexpected node to an existing system, the software of all nodes connected to the existing system can be changed to recognize the status from the unexpected node. In addition, since existing nodes that do not need to be changed can be connected as they are, it is possible to achieve cost reduction and reduction in development man-hours.

In the above-described embodiment, an example in which the GW 30 is connected as an independent device on the bus line has been described. However, a specific node may have a GW function. FIG. 13 is a block diagram showing a configuration when a node 21 belonging to the second NM system 20 has a GW function, and the same parts as those in FIG. 4 are denoted by the same reference numerals. As shown in FIG. 10, by connecting an ID management unit 34 (see FIG. 10) between the CPU 26 and the buffer unit 24, a specific node 21 can have a GW function.
When a specific node 21 has a GW function, it is necessary to determine whether or not the sleep condition of the own node is established in the wake-up transition / sleep transition process by the GW.

  As a node having a GW function, a node having a sufficient capacity for the CPU and the buffer unit is suitable. Specifically, a node that plays an important role on the system and that causes the down of the node to lead to the down of the application, such as a display node that controls a meter or the like, is preferable.

  Furthermore, in the above-described embodiment, the first NM system 10 that manages the status by the data frame and the second NM system 20 that manages the status by the status frame have been described as examples. However, the status is determined by the status information of the data frame. Even between managed systems, the status of each node cannot be managed if the data structure of the status information is different. For this reason, by providing a GW corresponding to the status management method of the counterpart system as in this embodiment, it becomes possible to manage sleep / wakeup for all nodes.

  In addition, even if the systems that manage the status by the same status frame, if the data structure of the status frame is different, the status of each other node cannot be managed. By providing a GW corresponding to the status management method, it becomes possible to manage sleep / wake-up for all nodes.

1 is an overall configuration diagram of a vehicle data communication system according to an embodiment. The block diagram which shows the functional structure of the node which belongs to a 1st NM system. Explanatory drawing which shows the data structure of the data frame in a 1st status management system. The block diagram which shows the functional structure of the node which belongs to a 2nd NM system. Explanatory drawing which shows the data structure of the data frame and status frame in a 2nd status management system. The flowchart which shows the process sequence in the case of wake-up transition in the node which belongs to a 1st NM system. The flowchart which shows the process sequence in the case of making a sleep transition in the node which belongs to a 1st NM system. The flowchart which shows the process sequence in the case of wake-up transition in the node which belongs to a 2nd NM system. The flowchart which shows the process sequence in the case of making a sleep transition in the node which belongs to a 2nd NM system. The block diagram which shows the functional structure of GW. The flowchart which shows the process sequence in the case of wake-up transition between both NM systems in GW. The flowchart which shows the process sequence in the case of making a sleep transition between both NM systems in GW. The block diagram which shows the structure at the time of giving the function of GW to the node which belongs to a 2nd NM system.

Explanation of symbols

1 to 4 ... reception buffer 10 ... first NM system 11, 21 ... node 12, 22, 31 ... communication IC
13, 24, 33 ... buffer unit 14, 25 ... status control unit 15, 26, 35 ... CPU
16, 27 ... function part 20 ... second NM system 23, 32 ... frame identification part 30 ... GW
34 ... ID management unit 40 ... Bus line

Claims (7)

A first node group consisting of a plurality of nodes whose sleep / wake-up is controlled by the first status management method, and a second node consisting of a plurality of nodes whose sleep / wake-up is controlled by the second status management method In a data communication system in which nodes are connected to a transmission line,
When a sleep condition is established in all nodes belonging to the first node group, a sleep state is notified to each node belonging to the second node group according to the second status management method, and When a sleep condition is established in all nodes belonging to the second node group, a sleep state is notified to each node belonging to the first node group according to the first status management method, and When at least one node belonging to the first node group satisfies the wake-up condition, the wake-up state is notified to each node belonging to the second node group according to the second status management method. In addition, when the wake-up condition is satisfied in at least one node belonging to the second node group, it belongs to the first node group That for each node, the data communication system, characterized in that a gateway device to notify the wakeup state according to the first status management method.   When the gateway apparatus receives a data frame including status information indicating that the sleep condition is satisfied from all the nodes belonging to the first node group, the gateway device stops transmitting a status frame including status information indicating that the sleep condition is not satisfied, When a status frame including status information indicating that the sleep condition is not satisfied is not received for a predetermined time from a node belonging to the second node group, a data frame including status information indicating that the sleep condition is satisfied is transmitted, and When a data frame including status information that does not satisfy the sleep condition is received from at least one node belonging to one node group, a status frame including status information that does not satisfy the sleep condition is transmitted, and the second frame The sleep condition is not satisfied from the nodes belonging to the node group. When receiving the status frame containing Tasu information, the data communication system of claim 1, wherein transmitting the data frame including the status information of the sleep condition not satisfied. As a first status management method, each node belonging to the first node group transmits a data frame including status information on the establishment of the sleep condition when the sleep condition of the own node is established, and within a predetermined time When a data frame including status information indicating that the sleep condition is not satisfied is not received from another node or the gateway device, the process shifts to a sleep state. When the wake-up condition of the own node is satisfied, the sleep condition is not determined after a predetermined time has elapsed. Send a data frame containing the status information of the establishment and execute the process to shift to the wake-up state,
As a second status management method, each node belonging to the second node group stops transmission of a status frame including status information indicating that the sleep condition is not satisfied, when the sleep condition of the own node is satisfied. When a status frame including status information indicating that the sleep condition is not satisfied is not received from another node or the gateway device within the time, the process shifts to the sleep state, and when the wake-up condition of the own node is satisfied, a predetermined time elapses. Transmitting a status frame including status information that the sleep condition is not satisfied and executing a process of shifting to a wake-up state;
The data communication system according to claim 1 or 2. Each node belonging to the first node group periodically transmits a data frame including status information indicating that the sleep condition is not established or the sleep condition is established in the wake-up state as a first status management method, and in the sleep state, Stop periodic transmission of the data frame,
As a second status management method, each node belonging to the second node group periodically transmits a status frame including status information indicating that the sleep condition is not satisfied in the wake-up state, and in the sleep state, Stop regular sending,
The data communication system according to any one of claims 1 to 3. The gateway device is at least
A data frame creating means for creating a data frame including status information indicating that the sleep condition is satisfied or the sleep condition is not satisfied;
A status frame creating means for creating a status frame including status information indicating that the sleep condition is not satisfied;
A communication control unit that is connected to the transmission path, transmits a data frame or a status frame created by the own device to another node, and receives a data frame or a status frame transmitted from another node;
A plurality of data receiving buffers for receiving the data frames transmitted from other nodes;
A status reception buffer for receiving the status frame transmitted from another node;
Based on the identification information included in the received frame, the type of the frame is determined. If the received frame is a data frame, the received frame is received in the data reception buffer specified by the identification information. If it is a frame, a frame identification unit that receives the status reception buffer;
In a wake-up state, when a data frame including status information indicating that the sleep condition is established is received from all the nodes belonging to the first node group, the transmission of the status frame is stopped, and the second node group When the status frame is not received for a predetermined time from the node to which it belongs, a process of transmitting a data frame including status information for establishing the sleep condition is executed, and at least one node belonging to the first node group in the sleep state When a data frame including status information indicating that the sleep condition is not satisfied is received, the status frame is transmitted, and when the status frame is received from a node belonging to the second node group, the sleep condition is not satisfied Data frame containing status information An ID management unit that executes a process of transmitting,
The data communication system according to any one of claims 2 to 4, further comprising:   The data communication system according to any one of claims 1 to 5, wherein the gateway device is provided in one node belonging to the first node group or the second node group. The data communication system according to any one of claims 1 to 6, wherein the node provided with the gateway device is a display node.

Images