Design of a communication middleware for distributed real-time safety systems in java [Diseflo de un software de intermediación de comunicación para sistemas distribuidos de tiempo real crfticos en java]
Tejera D.,University Folitecnica Of Madrid |
Alonso A.,University Folitecnica Of Madrid |
De Miguel M.A.,University Folitecnica Of Madrid
RIAI - Revista Iberoamericana de Automatica e Informatica Industrial | Year: 2013
Distributed real-time embedded systems are becoming increasingly important to society. More demands will be made on them and greater reliance will be placed on the delivery of their services. A relevant subset of them is high-integrity or hard real-time systems, where failure can cause loss of life, environmental harm, or significant financial loss. Additionally, the evolution of communication networks and paradigms as well as the necessity of demanding processing power and fault tolerance, motivated the interconnection between electronic devices; many of the communications have the possibility of transferring data at a high speed. The concept of distributed systems emerged as systems where different parts are executed on several nodes that interact with each other via a communication network. Java's popularity, facilities and platform independence have made it an interesting language for the real-time and embedded community. This was the motivation for the development of RTSJ (Real-Time Specification for Java), which is a language extension intended to allow the development of real-time systems. The use of Java in the development of high-integrity systems requires strict development and testing techniques. However, neither RTSJ nor its profiles provide facilities to develop distributed real-time applications. This is an important issue, as most of the current and future systems will be distributed. The Distributed RTSJ (DRTSJ) Expert Group was created under the Java community process (JSR-50) in order to define appropriate abstractions to overcome this problem. Currently there is no formal specification. The aim of this work is to describe the design and develop a communication middleware that is suitable for the development of distributed hard real-time systems in Java, based on the integration between the RM1 (Remote Method invocation) model and the HRTJ profile. it has been designed and implemented keeping in mind the main requirements such as the predictability and reliability in the timing behavior and the resource usage. The design starts with the definition of a computational model which identifies among other things: the communication model, most appropriate underlying network protocols, the analysis model, and a subset of Java for hard real-time systems. in the design, the remote references are the basic means for building distributed applications which are associated with all nonfunctional parameters and resources needed to implement synchronous or asynchronous remote invocations with real-time attributes. The proposed middleware separates the resource allocation from the execution itself by defining two phases and a specific threading mechanism that guarantees a suitable timing behavior. it also includes mechanisms to monitor the functional and the timing behavior, it provides independence from network protocol defining a network interface and modules. The JRMP protocol was modified to include two phases, non-functional parameters, and message size optimizations. Although serialization is one of the fundamental operations to ensure proper data transmission, current implementations are not suitable for hard real-time systems and there are no alternatives. This work proposes a predictable serialization that introduces a new com piler to generate optimized code according to the computational model. The proposed solution has the advantage of allowing us to schedule the communications and to adjust the memory usage at compilation time. in order to validate the design and the implementation a demanding validation process was carried out with emphasis in the functional behavior, the memory usage, the processor usage (the end-to-end response time and the response time in each functional block) and the network usage (real consumption according to the calculated consumption). © 2013 CEA.