New demands for invehicle networks

Krug, Markus; Schedl, Anton

doi:10.1109/eurmic.1997.617383

Cited by 17 publications

(4 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…2) The IDB-1394 Network: IDB-1394 is an automotive version of IEEE 1394 for in-vehicle multimedia and telematic applications jointly developed by the IDB Forum 7 and the 1394 Trade Association. 8 The system architecture of IDB-1394 permits existing IEEE 1394 consumer electronics devices to interoperate with embedded automotive grade devices. IDB-1394 supports a data rate of 100 Mb/s over a twisted pair or POF, with a maximum number of embedded devices which are limited to 63 nodes.…”

Section: Multimedia Networkmentioning

confidence: 99%

Trends in Automotive Communication Systems

et al. 2005

View full text Add to dashboard Cite

The use of networks for communications between the electronic control units (ECU) of a vehicle in production cars dates from the beginning of the 1990s. The specific requirements of the different car domains have led to the development of a large number of automotive networks such as Local Interconnect Network, J1850, CAN, TTP/C, FlexRay, media-oriented system transport, IDB1394, etc. This paper first introduces the context of in-vehicle embedded systems and, in particular, the requirements imposed on the communication systems. Then, a comprehensive review of the most widely used automotive networks, as well as the emerging ones, is given. Next, the current efforts of the automotive industry on middleware technologies, which may be of great help in mastering the heterogeneity, are reviewed. Finally, we highlight future trends in the development of automotive communication systems.

show abstract

Section: Multimedia Networkmentioning

confidence: 99%

Trends in Automotive Communication Systems

et al. 2005

View full text Add to dashboard Cite

show abstract

“…X-by-Wire is a generic term referring to the replacement of mechanical or hydraulic systems by fully electrical/electronic ones, which led and still leads to new design methods for developing them safely [100] and, in particular, for mastering the interferences between functions [4]. Chassis and powertrain functions operate mainly as closed-loop control systems and their implementation is moving towards a time-triggered approach [82,44,76,72], which facilitates composability (i.e. ability to integrate individually developed components) and deterministic real-time behavior of the system.…”

Section: Car Domains and Their Evolutionmentioning

confidence: 99%

In-Vehicle Communication Networks: A Historical Perspective and Review

deLong¹

2017

Industrial Communication Technology Handbook

View full text Add to dashboard Cite

The use of networks for communications between the Electronic Control Units (ECU) of a vehicle in production cars dates from the beginning of the 90s. The specic requirements of the dierent car domains have led to the development of a large number of automotive networks such as LIN, CAN, CAN FD, FlexRay, MOST, automotive Ethernet AVB, etc.. This report rst introduces the context of in-vehicle embedded systems and, in particular, the requirements imposed on the communication systems. Then, a review of the most widely used, as well as the emerging automotive networks is given. Next, the current eorts of the automotive industry on middleware technologies which may be of great help in mastering the heterogeneity, are reviewed, with a special focus on the proposals of the AUTOSAR consortium. Finally, we highlight future trends in the development of automotive communication systems. * This technical report is an updated version of two earlier review papers on automotive networks: N.

show abstract

“…WCRT is strongly determined by the parameters of Direct NM which include the number of nodes, T T'yp » and T Max' The worst case design of relationship of TTyp and TMax is shown in (1) , (2) and (3) [8]: (2) TMax Imax == 3TTyp Imin (3) where n is the number of nodes. The minimum value ofT Typ affects the busload more than the upper value.…”

Section: B Experiments Ofdirect Nmmentioning

confidence: 99%

“…Network Management (NM) monitors the network status of nodes in order to achieve reliable communication. An in-vehicle network uses NM mechanisms to collect network information in order to implement a fault-tolerant in-vehicle network [3].…”

Section: Introductionmentioning

confidence: 99%

Comparison of two types of OSEK network management for CAN

Son

Seo

Kim

et al. 2009

2009 IEEE International Symposium on Industrial Electronics

View full text Add to dashboard Cite

As the number of electronic control units (ECUs) in vehicles increases, ECUs can create a large and complicated invehicle network. Therefore, in-vehicle networks need a network management algorithm for improved reliability. The Open System and Corresponding Interfaces for Automotive Electronics/Vehicle Distributed Executive (OSEKNDX) set a goal of being the industry standard for real-time operating systems used in vehicle systems. OSEKNDX includes a reliable network management algorithm, OSEK Network Management (OSEK NM). It has two types of management mechanisms: Direct NM, and Indirect NM. These have opposite characteristics and different management performance. This paper explains the effective factor of network management performance, and proves it using a real application experiment.Direct NM and Indirect NM are implemented to Controller Area Network (CAN), and performance is analyzed using real applications. The result of this paper contributes that as a case of network situation, application engineer selects two types of OSEK NM for the best performance.

show abstract

New demands for invehicle networks

Cited by 17 publications

References 3 publications

Trends in Automotive Communication Systems

Trends in Automotive Communication Systems

In-Vehicle Communication Networks: A Historical Perspective and Review

Comparison of two types of OSEK network management for CAN

Contact Info

Product

Resources

About