WO2009098616A1 - Topologie en anneau, contrôleur d’anneau et procédé - Google Patents
Topologie en anneau, contrôleur d’anneau et procédé Download PDFInfo
- Publication number
- WO2009098616A1 WO2009098616A1 PCT/IB2009/050359 IB2009050359W WO2009098616A1 WO 2009098616 A1 WO2009098616 A1 WO 2009098616A1 IB 2009050359 W IB2009050359 W IB 2009050359W WO 2009098616 A1 WO2009098616 A1 WO 2009098616A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ring
- message
- node
- interface
- controller
- Prior art date
Links
Classifications
-
- 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/42—Loop networks
Definitions
- the invention relates to a ring topology as claimed in claim 1 , a ring controller as claimed in claim 8 and method to control a data transmission within a ring topology as claimed in claim 12.
- Automotive vehicles are using a large number of electronic units to control the actuation or performance of actuators or components of the vehicle. Such electronic units are usually connected to a communication network. Such dependable automotive communication networks typically rely on time-triggered communication protocols like TTP/C (Time Triggered Protocol Class C) or FlexRay, based on broadcast data or messages according to a pre-determined TDMA (Time Division Multiple Access) scheme.
- a typical fault-tolerant time-triggered network consists of two or more communication channels, to which different nodes are connected. Such nodes are typically control units of electronically controlled devices. Each of those nodes consists e.g. of bus drivers, a communication controller and/or eventually a bus guardian device for each bus driver and the application host.
- the bus driver creates the connection to the data channel and writes the information to be sent via the data bus to the channel and it reads the signals from other nodes or units from the channel.
- both bus- and star-topologies can be combined in one network.
- a central star-coupler can connect not only a number of nodes on individual base, but also small sub-networks, each containing a number of nodes connected to a bus.
- the FlexRay protocol as been as today is specified for a speed of 10 Mbit/s and supports bus-, star- and hybrid topologies as mentioned above.
- the FlexRay protocol additionally allows other protocols on top of it. Messages with their own identifiers for example could be applied to allow the identification of additional services not addressed by the FlexRay protocol it selves.
- a ring-topology requires less cabling.
- a network with N nodes connected in a ring requires 2N connectors and bus-drivers. Because each node can reach any other node in two directions, it has redundant interconnection of the nodes by nature.
- the inventive ring topology of nodes comprises a node which contains at least one host and a ring controller with two interfaces and a arbitrary amount of nodes are connected by means of a data connection between respective interfaces of two different nodes, and all nodes are connected to a ring structure and the connection between the interfaces is a FlexRay connection.
- the ring controller of a node is able to transmit data via an interface to another interface of another node by means of the FlexRay connection. Furthermore it is of advantage that the ring controller of a node is able to receive data from an interface from another interface of another node by means of the
- FlexRay connection and additionally it is of advantage that the ring controller of a node is able to copy data received from an interface to the host of the node. Furthermore it is of advantage that the ring controller of a node is able to forward data received from an interface (24,25) to another interface.
- the ring controller of the last receiving node terminates the circulation of a data message.
- the first transmitting ring controller of a message terminates the transmission of the message after receiving the message again. Furthermore it is of advantage that the ring controller of a predetermined node terminates the forwarding of a data message in the ring, whereby for each data message a node is assigned to terminate the message forwarding.
- the ring controller that inserted a message terminates the forwarding of the message after receiving the same message circulated in the ring.
- the object of the invention concerning the ring controller will be solved using a ring controller for the use within the above mentioned ring topology characterised in that the controller contains two interfaces and each interface is connected to a bus driver, the bus driver is connected to a protocol engine and the protocol engine is connected to a controller host interface which is extended by an function that is able to recognize if a received message is meant for forwarding in order to put it into a message buffer determined for forwarding the message, wherein the controller host interface is connected to a message buffer.
- the object of the invention concerning the method will be solved by the method to control a data transmission within a ring topology of nodes wherein a node contains at least one a host and a ring controller with two interfaces and wherein an arbitrary amount of nodes are connected by means of a data connection between respective interfaces of two different nodes, and all nodes are connected to a ring structure and the connection between the interfaces is a FlexRay connection, wherein the ring controller of a node is able to transmit data via an interface to another interface of another node by means of the FlexRay connection and/or the ring controller of a node is able to receive data from an interface from another interface of another node by means of the FlexRay connection and/or the ring controller of a node is able to copy data received from an interface to the host of the node.
- Fig. 1 shows a schematic diagram of an inventive ring topology
- Fig. 2 shows a diagram of the function of a ring controller
- Fig. 3 shows a diagram of the function of a ring controller
- Fig. 4 shows a diagram of the function of a ring controller
- Fig. 5 shows a diagram of the function of a ring controller
- Fig. 6 shows a diagram of a ring-topology of a number of nodes or clusters
- Fig. 7 shows a diagram of a ring-topology of a number of nodes or clusters
- Fig. 8 shows a node with host and ring controller
- Fig. 9 shows a node with host and ring controller.
- a ring topology can be build by using every node as a two-way gateway between two FlexRay sub-networks; a separate FlexRay network is used as link between every two nodes connected in the ring topology.
- a new protocol is added on top of the existing FlexRay protocol. This new protocol is based on the store-and-forward principle. It defines the handling of messages in each node. These messages can be freely allocated to different slots at each FlexRay interface.
- the protocol defines the insertion, extraction, forwarding and termination of the messages.
- the invention is described starting from an abstract definition of the required communication functions for a node in the ring-topology, followed by an overview of the building blocks inside a node and finally the mapping of the functions to these building blocks.
- Figure 1 shows an example of an inventive ring topology 1 for four FlexRay nodes 2, 3, 4, 5.
- the mentioned number of nodes is only an example and not limited.
- These nodes 2, 3, 4, 5 are containing respectively a host 6, 7, 8, 9 and a ring controller 10, 11, 12, 13 and are connected with two other nodes via the ring controller 10, 11, 12 and 13 by means of two FlexRay connections or interfaces FlexRay-1 to FlexRay-4 14, 15, 16, 17.
- Each FlexRay connection or interface 14, 15, 16, 17 allows transmitting and receiving frames.
- the inventive embodiment contains four independent FlexRay clusters, whereby each FlexRay cluster connects two nodes 2, 3, 4, 5.
- Each FlexRay cluster has its own schedule, but preferably the schedules are identical to realize symmetrical performance in the ring.
- the following Figures 2 to 5 demonstrate the basic communication functions for a node as shown in figure 1 and which are labelled with the references 2, 3, 4, 5.
- Fig. 2 shows the insertion functions of a ring controller 20. If the host 21 transmits a message 22 towards the other nodes, the ring controller 20 can send this message 22 in two different directions 23.
- the direction 23 is determined by the configuration of the ring controller 20 e.g. by a message address lookup table. Transmission of a message 22 in one direction 23 will be sufficient for non-redundant communication. In this case the configuration can be optimised by choosing the direction having the shortest number of FlexRay clusters to the destination hosts. Insertion of the message on both FlexRay interfaces supports the realization of redundant communication.
- Fig. 3 shows the extraction functions of the ring controller 20. A message 22 is received by one of the two interfaces 24 of the ring and offered to the host 21 for reception.
- Message reception can be realised by message filtering techniques, e.g. with a message address lookup table.
- a node can extract a message 22 from one of the interfaces 24 for non- redundant communication and from both interfaces for redundant communication
- Fig. 4 shows the forwarding functions of the ring controller 20.
- the ring controller 20 forwards a message 22 received from one of the two interfaces 24 to the other interface 25 without forwarding the message to the host.
- the function can be realised in two different directions. For non-redundant communication one direction will be sufficient. For redundant communication both directions are needed in parallel.
- the configuration of the forwarding functions can be realised with message address tables.
- Fig. 5 shows a combination of extraction and forwarding functions.
- the ring controller 20 receiving a message 22 on one of the two interfaces 24 forwards it to the other interface 25 and in parallel offers e.g. a copy 26 of this message 22 to the host 21. Again this can be realised in one direction in the ring for non-redundant communication, but also in two directions for redundant communication.
- Fig. 6 shows a diagram 30 of a ring topology of a network 31 of four nodes 2, 3, 4, 5 and the usage of the above described functions for a non-redundant communication embodiment. Every node may represent a cluster of nodes, as explained above.
- Node 1, 2 sends a message 36 to node 2, 3 and to node 3, 4.
- the ring controller 1, 10 inserts the message 36 on its interface 38 connected to the FlexRay 1 connection 14.
- the ring controller 2, 11 extracts the message from its FlexRay 1 interface 41 and forwards it to its FlexRay 2 interface 42.
- the ring controller 2, 11 offers the message 36 or a copy of the message to host 2 of node 2, 3.
- the ring controller 2, 11 transfers the message to the interface 42 and transmits the message to the FlexRay 2 connection 15.
- the ring controller 3, 12 receives the message via the interface 45 and the ring controller 3, 12 extracts the message from its FlexRay 2 interface 45 and offers it to host 3, 8. Since it does not forward the message, ring controller 3, 12 terminates the transmission of the message on the ring.
- the ring 48 can be configured such that the ring controller that is last in the chain of destinations for this message terminates the message on the ring 48. This will result in efficient usage of the available bandwidth in the ring 48, but requires dedicated configuration of each of the nodes 2, 3, 4, 5. In case a new ring controller is added to the ring 48, or an existing one is removed from the ring 48 re-configuration requires quite some overhead.
- Fig. 7 A more flexible configuration method for regarding re-configuration is shown in Fig. 7.
- the ring controller (RCl) 10 that inserts a message 36 into the ring 48 also terminates the message after the message 36 has travelled through the complete ring 48 and has been received by the sending ring controller 10 again. All other ring controllers (RC2, RC3, RC 4) of the other nodes node 2, node 3 and node 4 forward this message 36 and if needed offer the message or a copy of the message to the respective hosts host2, host 3, host 4.
- Redundant communication can be realised by applying this method for both directions on the ring 48.
- RCl inserts the message on both its interfaces 38, 49, and the ring controllers RC 2, RC 3 and RC 4 are forwarding the message 36 in both directions, and after travelling trough the complete ring, the ring controller RCl, 10 extracts the message 36 on both its interfaces 38, 49 and terminates the travelling of the message 36 on the ring 48.
- Fig. 8 shows an embodiment of the structure 50 of a ring controller 51 in a node 52 of the network.
- the FlexRay interfaces 53, 54 are interfaces, each containing a bus driver (BD) 55, 56, a protocol engine (PE) 57, 58 and a Controller Host Interface (CHI) 59, 60.
- BD bus driver
- PE protocol engine
- CHI Controller Host Interface
- a Controller Host Interface is extended (Ext) 61,62 with extension 61,62 with extra functionality. This function of the extension is able to interpret the address field of the message.
- Communication between Controller Host Interface 59, 60 and the host 63 is arranged via message buffers 64, 65. These buffers 64, 65 can be realised separately e.g.
- the forwarding function in this embodiment of the invention is located in the ring controller. It can be realised in different ways. One method is to place the forwarding function FW, 66 between reception forwarding buffers and transmission forwarding buffers 64, 65. A message extracted from one FlexRay interface by the Controller Host Interface CHI 59, 60 is stored in a reception forwarding buffer 64, 65. From there it is copied by the forwarding function 66 into the transmission forwarding buffer 64, 65 of the other FlexRay interface. In case the message needs to be offered to the host, the Controller Host Interface CHI 59, 60 copies it into a host reception buffer as well.
- FIG. 9 shows an alternative method. It shows that the forward buffer 70 is placed between the two Controller Host Interfaces 71, 72. This could be realised by applying a shared memory. A message extracted from one FlexRay interface is stored in a forwarding buffer 70 by the Controller Host Interface CHI 71, 72. From there it is read by the second Controller Host Interface CHI 72, 71 to insert into the second FlexRay interface.
- FlexRay subsystems each point-to-point connection within a FlexRay ring might be realised with a two-node FlexRay cluster. This might prevent failures of a single node from affecting the overall ring structure. Furthermore it is possible to use the FlexRay protocol either in a one-channel or a two-channel configuration.
- the second channel can be used to increase the bandwidth, the data integrity and/or the link reliability. If the same message is inserted on both channels and handled identically by all nodes then the data integrity is increased since the receiving nodes can compare the message received on both channels and compare it for deviations. If different messages are being sent on both channels, the bandwidth is increased.
- the second channel can also be used for link reliability, by sending the same message in one direction on the first channel and in another direction on a second channel. Since FlexRay is only a half- duplex protocol, this reduces the propagation delay of messages by restricting the direction within which messages can travel on a ring.
- the FlexRay feature of hardware supported 'message IDs' might be used to identify the messages, which is normally done via the FlexRay slot ID.
- Each message ID is uniquely given to a certain message type containing specific signals and only one node has the right to insert a message with said message ID. Any node 'interested' in this message can recognise the message by its 'message ID' and offer the contained data to its application.
- the FlexRay cycle might contain two static slots, where each node in the cluster is assigned one of them. According to the invention it is proposed to use two slots to exchange data or network information or management information, e.g., to slowly synchronise all the FlexRay clusters making up the ring.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
Abstract
La présente invention concerne une topologie en anneau (1) de nœuds (2, 3, 4, 5). Un nœud contient au moins un hôte (6, 7, 8, 9) et un contrôleur d’anneau (10, 11, 12, 13) possédant deux interfaces et une quantité prédéfinie de nœuds qui sont connectés à l’aide d’une connexion de données entre des interfaces respectives de deux nœuds différents. Tous les nœuds sont connectés à une structure d’anneau et la connexion entre les interfaces consiste en une connexion FlexRay.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP08101302 | 2008-02-06 | ||
EP08101302.1 | 2008-02-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009098616A1 true WO2009098616A1 (fr) | 2009-08-13 |
Family
ID=40810845
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2009/050359 WO2009098616A1 (fr) | 2008-02-06 | 2009-01-29 | Topologie en anneau, contrôleur d’anneau et procédé |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2009098616A1 (fr) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2566110A1 (fr) * | 2011-08-30 | 2013-03-06 | Siemens Aktiengesellschaft | Procédé de transmission de télégrammes dans un système d'automatisation |
WO2013041351A1 (fr) * | 2011-09-19 | 2013-03-28 | Siemens Aktiengesellschaft | Procédé de fonctionnement d'un réseau de communication et dispositif de réseau |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6028837A (en) * | 1996-08-27 | 2000-02-22 | National Semiconductor Corporation | Ether ring architecture for local area networks |
GB2357390A (en) * | 1999-12-16 | 2001-06-20 | 3Com Corp | Duplex Ethernet ring discards packets after one circuit |
KR100789444B1 (ko) * | 2006-09-29 | 2007-12-28 | 엘에스산전 주식회사 | 패킷 무한 루프 방지가 가능한 링 토폴로지 이더넷네트워크의 통신 패킷 처리 장치 및 통신 패킷 처리 방법 |
WO2009003557A2 (fr) * | 2007-06-30 | 2009-01-08 | Bayerische Motoren Werke Aktiengesellschaft | Véhicule automobile |
-
2009
- 2009-01-29 WO PCT/IB2009/050359 patent/WO2009098616A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6028837A (en) * | 1996-08-27 | 2000-02-22 | National Semiconductor Corporation | Ether ring architecture for local area networks |
GB2357390A (en) * | 1999-12-16 | 2001-06-20 | 3Com Corp | Duplex Ethernet ring discards packets after one circuit |
KR100789444B1 (ko) * | 2006-09-29 | 2007-12-28 | 엘에스산전 주식회사 | 패킷 무한 루프 방지가 가능한 링 토폴로지 이더넷네트워크의 통신 패킷 처리 장치 및 통신 패킷 처리 방법 |
EP1906598A1 (fr) * | 2006-09-29 | 2008-04-02 | LS Industrial Systems Co., Ltd | Appareil de traitement des paquets de communication et procédé pour réseau Ethernet à topologie en anneau permettant de neutraliser les boucles permanentes de paquets |
WO2009003557A2 (fr) * | 2007-06-30 | 2009-01-08 | Bayerische Motoren Werke Aktiengesellschaft | Véhicule automobile |
Non-Patent Citations (1)
Title |
---|
HALL B ET AL: "A FlexRay-Based Braided-Ring Availability", PAPER NO. 2007-01-1492. PRESENTED AT SAE CONGRESS 2007,, 1 January 2007 (2007-01-01), pages 73 - 86, XP009119616 * |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2566110A1 (fr) * | 2011-08-30 | 2013-03-06 | Siemens Aktiengesellschaft | Procédé de transmission de télégrammes dans un système d'automatisation |
CN102970194A (zh) * | 2011-08-30 | 2013-03-13 | 西门子公司 | 用于在自动化系统中传输电报的方法 |
JP2013051684A (ja) * | 2011-08-30 | 2013-03-14 | Siemens Ag | 自動化システムにおけるメッセージの伝送方法 |
US8984092B2 (en) | 2011-08-30 | 2015-03-17 | Siemens Aktiengesellschaft | Method for transmitting telegrams in an automation system |
CN102970194B (zh) * | 2011-08-30 | 2017-07-28 | 西门子公司 | 用于在自动化系统中传输电报的方法 |
WO2013041351A1 (fr) * | 2011-09-19 | 2013-03-28 | Siemens Aktiengesellschaft | Procédé de fonctionnement d'un réseau de communication et dispositif de réseau |
CN103797467A (zh) * | 2011-09-19 | 2014-05-14 | 西门子公司 | 用于运行通信网络的方法和网络装置 |
JP2014533449A (ja) * | 2011-09-19 | 2014-12-11 | シーメンス アクチエンゲゼルシヤフトSiemens Aktiengesellschaft | 通信ネットワークの動作方法及びネットワークシステム |
US10454848B2 (en) | 2011-09-19 | 2019-10-22 | Siemens Aktiengesellschaft | Method for operating a communication network, and network arrangement |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9137042B2 (en) | Cluster coupler in a time triggered network | |
US6445711B1 (en) | Method of and apparatus for implementing and sending an asynchronous control mechanism packet used to control bridge devices within a network of IEEE STD 1394 serial buses | |
CN101512986B (zh) | 用于时间触发通信协议的智能星形耦合器以及使用时间触发协议在网络内的节点之间进行通信的方法 | |
US9225556B2 (en) | Multiplexed packet local area networking using an Ethernet physical layer device | |
US7508824B2 (en) | Method and system for transmitting data via switchable data networks | |
US8571044B2 (en) | Gateway for data transfer between serial buses | |
US20080192772A1 (en) | Low-Weight Hybrid Deterministic Highspeed Data Bus | |
US11451412B2 (en) | Method for enabling nodes of heterogeneous communication protocols to share a single bus by adapting to one of the heterogeneous communication protocols and device for said method | |
US7668182B2 (en) | Synchronous multi-cluster network architecture | |
CN114174953A (zh) | 低复杂度以太网节点(len)一个端口 | |
US10079763B2 (en) | Method for data communication with reduced overhead in a real-time capable Ethernet data network | |
US20090279540A1 (en) | Cluster coupler in a time triggered network | |
US7843966B2 (en) | Communication system for flexible use in different application scenarios in automation technology | |
CN109412695B (zh) | 一种基于星形拓扑结构的光纤can2.0b总线路由系统 | |
WO2009098616A1 (fr) | Topologie en anneau, contrôleur d’anneau et procédé | |
JP4850704B2 (ja) | データ伝送方法および装置 | |
JP2006519532A5 (fr) | ||
JP2006109258A (ja) | 通信方法及び通信装置 | |
An et al. | Analysis of CAN FD to CAN message routing method for CAN FD and CAN gateway | |
US6275884B1 (en) | Method for interconnecting components within a data processing system | |
KR102236241B1 (ko) | 이종의 통신방식들의 노드들이 단일 버스를 공유하여 통신할 수 있게 하는 방법과 기기, 그리고 그 방법에 의해 구축된 네트워크 | |
CN115550095B (zh) | Lin通信电路以及在lin总线之间通信的方法 | |
KR102144631B1 (ko) | 이종 통신방식의 노드들이 단일 버스를 공유하여 통신할 수 있게 하는 방법과 그 방법을 위한 기기 | |
KR102161951B1 (ko) | 링 토폴로지 네트워크에서의 경로 자동 구성을 위한 메시지 전달 방법 | |
JP2012005003A (ja) | 通信ネットワークシステム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09709369 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 09709369 Country of ref document: EP Kind code of ref document: A1 |