An Efficient Sensor Network Architecture Using Open Platform in Vehicle Environment

  • Hong-bin Yim
  • Pyung-sun Park
  • Hee-seok Moon
  • Jae-il Jung
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4412)


Vehicles have been developed with an objective of safety. A large number of sensors will be required in Advanced Safety Vehicles that provide intelligent and automatic services in future ITS(Intelligent Transport Systems) circumstances. Because current in-vehicle networks must be changed to add new sensors, the number of sensors that can be added is restricted in current in-vehicle networks. To manage the sensors more efficiently and to provide extensibility, we propose a SCSN (Smart Car Sensor Network), which is an in-vehicle architecture based on AMI-C and OSGi standards. In this architecture, Vehicle Interface (VI), defined in the AMI-C standard, performs as a gateway in an AMI-C network. An integrated VI structure has been developed to provide a Vehicle Service (VS) on a standard platform. An interworking structure with a CAN(Controller Area Network) interface is implemented to provide an efficient VI. In current telematics architecture, time delay occurs between the CAN network start-up time and the platform booting time. Message loss occurs during this time delay. In this paper, we propose an efficient gateway architecture to minimize message loss due to this time delay. The efficiency of this platform has been verified using CANoe, which is a vehicle-network simulation tool.


SCSN(Smart Car Sensor Network) Telematics ITS Sensor Network Sensor Network Gateway Sensor Clustering Node. 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Shuai, P., et al.: A Study on an algorithm of a Network Node for CAN-Based Wiring System Using Polling Structure. In: IPC-13, pp. 1105–1108 (2005)Google Scholar
  2. 2.
    Chang-hee, C.: Trends of Telematics Based or Network for Vehicle. Auto Journal 27(6), 9–16 (2005)Google Scholar
  3. 3.
  4. 4.
    AMI-C 1003: AMI-C Release 2 Architectural Overview v1.00Google Scholar
  5. 5.
    Mahmud, S.M., Alles, S.: In-Vehicle Network Architecture for the Next-Generation Vehicles. SP-1918, pp. 99-108, SAE (2005)Google Scholar
  6. 6.
    AMI-C 1003: AMI-C Release 2 Architectural Overview v1.00 (2003)Google Scholar
  7. 7.
    Abowd, P., Rushton, G.: Extensible and Upgradable Vehicle Electrical, Electronic, and Software Architectures. SAE Transactions 111, 495–498 (2002)Google Scholar
  8. 8.
  9. 9.
    Kapadia, V., Bai, V., Parthasarathy, G.: Telematics System Architecture. WHITE PAPER, wipro Ltd. (2005)Google Scholar
  10. 10.
  11. 11.
  12. 12.
    AMI-C 4002: AMI-C Requirements and specifications for Human Machine Interfaces v1.00 (2003)Google Scholar
  13. 13.
    AMI-C 3001: AMI-C Requirements and guidelines for software host platforms v1.00 (2003)Google Scholar
  14. 14.
    AMI-C 2002: AMI-C Common Message Set v1.01 (2003)Google Scholar
  15. 15.
    AMI-C 2001: AMI-C Network protocol requirements for vehicle interface access v1.00 (2003)Google Scholar

Copyright information

© Springer Berlin Heidelberg 2007

Authors and Affiliations

  • Hong-bin Yim
    • 1
  • Pyung-sun Park
    • 1
  • Hee-seok Moon
    • 1
  • Jae-il Jung
    • 1
  1. 1.Department of Electrical and Computer Engineering Hanyang University, 17 Haengdang-dong, Sungdong-gu, Seoul, 133-791Korea

Personalised recommendations