We propose middleware which works on widely-used commercial off-the-shelf platforms (UDP/IP, FastEthernet, and Windows NT or commercial real-time kernels) to realize real-time distributed services for plant monitoring and control systems. It is not suitable to use TCP/IP for the systems because of its unpredictable re-transmission, while, as well known, UDP/IP does not guarantee certain arrivals of packets and it is also not acceptable for the systems. With UDP/IP, packets are lost mainly because of collisions in a network and buffer overflows. To avoid these packet losses, the middleware controls scheduling of all the packets transmitted between the nodes in a distributed system and prevents excessive collisions and buffer overflows. The middleware provides a necessary set of functions for plant monitoring and control applications. The middleware on each node in a distributed system consists of library functions and run-time modules. An application program on the node is required to use these library functions according to the rules the middleware provides. In this way the middleware can manage all the traffic among the nodes in the system. Receiving requests from the application via library functions, the run-time module of the middleware schedules transmission of messages to other nodes, avoiding unexpected delivery delays or buffer overflows. The module also guarantees application-to-application quality of service (QoS), such as transmission period and delivery deadline, required by the applications. This is achieved by assigning the resources not shared by other services to each distributed service and scheduling these resources so as not to violate the assignment. Here, resources include maximum numbers of packets which a node can receive or send in a specific period (20 msec, for example). We show implementation of the middleware to make it clear how to guarantee application-to-application QoS with some application examples.
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Copy
Ichiro MIZUNUMA, Ikuyoshi HIROSHIMA, Satoshi HORIIKE, "MidART--Middleware for Real-Time Distributed Systems for Industrial Applications" in IEICE TRANSACTIONS on Information,
vol. E84-D, no. 4, pp. 465-476, April 2001, doi: .
Abstract: We propose middleware which works on widely-used commercial off-the-shelf platforms (UDP/IP, FastEthernet, and Windows NT or commercial real-time kernels) to realize real-time distributed services for plant monitoring and control systems. It is not suitable to use TCP/IP for the systems because of its unpredictable re-transmission, while, as well known, UDP/IP does not guarantee certain arrivals of packets and it is also not acceptable for the systems. With UDP/IP, packets are lost mainly because of collisions in a network and buffer overflows. To avoid these packet losses, the middleware controls scheduling of all the packets transmitted between the nodes in a distributed system and prevents excessive collisions and buffer overflows. The middleware provides a necessary set of functions for plant monitoring and control applications. The middleware on each node in a distributed system consists of library functions and run-time modules. An application program on the node is required to use these library functions according to the rules the middleware provides. In this way the middleware can manage all the traffic among the nodes in the system. Receiving requests from the application via library functions, the run-time module of the middleware schedules transmission of messages to other nodes, avoiding unexpected delivery delays or buffer overflows. The module also guarantees application-to-application quality of service (QoS), such as transmission period and delivery deadline, required by the applications. This is achieved by assigning the resources not shared by other services to each distributed service and scheduling these resources so as not to violate the assignment. Here, resources include maximum numbers of packets which a node can receive or send in a specific period (20 msec, for example). We show implementation of the middleware to make it clear how to guarantee application-to-application QoS with some application examples.
URL: https://global.ieice.org/en_transactions/information/10.1587/e84-d_4_465/_p
Copy
@ARTICLE{e84-d_4_465,
author={Ichiro MIZUNUMA, Ikuyoshi HIROSHIMA, Satoshi HORIIKE, },
journal={IEICE TRANSACTIONS on Information},
title={MidART--Middleware for Real-Time Distributed Systems for Industrial Applications},
year={2001},
volume={E84-D},
number={4},
pages={465-476},
abstract={We propose middleware which works on widely-used commercial off-the-shelf platforms (UDP/IP, FastEthernet, and Windows NT or commercial real-time kernels) to realize real-time distributed services for plant monitoring and control systems. It is not suitable to use TCP/IP for the systems because of its unpredictable re-transmission, while, as well known, UDP/IP does not guarantee certain arrivals of packets and it is also not acceptable for the systems. With UDP/IP, packets are lost mainly because of collisions in a network and buffer overflows. To avoid these packet losses, the middleware controls scheduling of all the packets transmitted between the nodes in a distributed system and prevents excessive collisions and buffer overflows. The middleware provides a necessary set of functions for plant monitoring and control applications. The middleware on each node in a distributed system consists of library functions and run-time modules. An application program on the node is required to use these library functions according to the rules the middleware provides. In this way the middleware can manage all the traffic among the nodes in the system. Receiving requests from the application via library functions, the run-time module of the middleware schedules transmission of messages to other nodes, avoiding unexpected delivery delays or buffer overflows. The module also guarantees application-to-application quality of service (QoS), such as transmission period and delivery deadline, required by the applications. This is achieved by assigning the resources not shared by other services to each distributed service and scheduling these resources so as not to violate the assignment. Here, resources include maximum numbers of packets which a node can receive or send in a specific period (20 msec, for example). We show implementation of the middleware to make it clear how to guarantee application-to-application QoS with some application examples.},
keywords={},
doi={},
ISSN={},
month={April},}
Copy
TY - JOUR
TI - MidART--Middleware for Real-Time Distributed Systems for Industrial Applications
T2 - IEICE TRANSACTIONS on Information
SP - 465
EP - 476
AU - Ichiro MIZUNUMA
AU - Ikuyoshi HIROSHIMA
AU - Satoshi HORIIKE
PY - 2001
DO -
JO - IEICE TRANSACTIONS on Information
SN -
VL - E84-D
IS - 4
JA - IEICE TRANSACTIONS on Information
Y1 - April 2001
AB - We propose middleware which works on widely-used commercial off-the-shelf platforms (UDP/IP, FastEthernet, and Windows NT or commercial real-time kernels) to realize real-time distributed services for plant monitoring and control systems. It is not suitable to use TCP/IP for the systems because of its unpredictable re-transmission, while, as well known, UDP/IP does not guarantee certain arrivals of packets and it is also not acceptable for the systems. With UDP/IP, packets are lost mainly because of collisions in a network and buffer overflows. To avoid these packet losses, the middleware controls scheduling of all the packets transmitted between the nodes in a distributed system and prevents excessive collisions and buffer overflows. The middleware provides a necessary set of functions for plant monitoring and control applications. The middleware on each node in a distributed system consists of library functions and run-time modules. An application program on the node is required to use these library functions according to the rules the middleware provides. In this way the middleware can manage all the traffic among the nodes in the system. Receiving requests from the application via library functions, the run-time module of the middleware schedules transmission of messages to other nodes, avoiding unexpected delivery delays or buffer overflows. The module also guarantees application-to-application quality of service (QoS), such as transmission period and delivery deadline, required by the applications. This is achieved by assigning the resources not shared by other services to each distributed service and scheduling these resources so as not to violate the assignment. Here, resources include maximum numbers of packets which a node can receive or send in a specific period (20 msec, for example). We show implementation of the middleware to make it clear how to guarantee application-to-application QoS with some application examples.
ER -