A middleware model supporting time-triggered message-triggered objects for standard Linux systems

  • Authors:

  • Stephen F. Jenks;Kane Kim;Yuqing Li;Sheng Liu;Liangchen Zheng;Moon H. Kim;Hee-Yong Youn;Kyung Hee Lee;Dong-Myung Seol

  • Affiliations:

  • University of California, Irvine, USA;University of California, Irvine, USA;University of California, Irvine, USA;University of California, Irvine, USA;University of California, Irvine, USA;KonKuk University, Seoul, South Korea;SungKyunKwan University, Suwon, South Korea;ETRI, Daejeon, South Korea;ETRI, Daejeon, South Korea

  • Venue:
  • Real-Time Systems
  • Year:
  • 2007

Quantified Score

Hi-index 0.00

Visualization

Abstract

The Time-triggered Message-triggered Object (TMO) programming and specification scheme came out of an effort to remove the limitations of conventional object structuring techniques in developing real-time (RT) distributed computing components and composing distributed computing applications out of such components and others. It is a natural and syntactically small but semantically powerful extension of the object oriented (OO) design and implementation techniques which allows the system designer to specify in natural and yet precise forms timing requirements imposed on data and function components of high-level distributed computing objects. TMO Support Middleware (TMOSM) was devised to be an efficient middleware architecture that can be easily adapted to many commercial-off-the-shelf (COTS) hardware + kernel operating system platforms to form efficient TMO execution engines. However, up until 2003, its adaptations were done for Microsoft Windows platforms only. As we have been developing and refining an adaptation of TMOSM to the Linux 2.6 operating system platform in recent years, TMOSM has been refined to possess further improved modularity and portability. This paper presents the refined TMOSM as well as the techniques developed for efficient adaptation of TMOSM to the Linux 2.6 platform.