RIPlink reference architecture
Software components and interfaces
The RIPlink Reference Architecture defines software components and interfaces, to allow modular and interoperable implementation of RIPlink across various devices and non-IP networks.
The RIPlink Reference Architecture software components are:
- The RSP Gateway which is part of the RIPlink Gateway is independent from the non-IP network. RSP Gateway does interface to the RIPlink Gateway TCP/UDP/IP stack. RSP Gateway implements the Remote Socket Protocol server side.
- The RSP Client which is part of the RIPlink Device and is independent from the non-IP network. RSP Client exposes the RIPlink portable socket APIs to the IP Application running on RIPlink Device. RSP Client implements the Remote Socket Protocol client side.
- The Gateway Adapter and Client Adapter are respectively part of RIPlink Gateway and RIPlink Device, and dependent of the non-IP network. They perform a reliable transport channel of the Remote Socket Protocol between RSP Client and RSP Gateway, adapted to the non-IP network specificities. Gateway Adapter manages in addition non-IP network specific addressing.
How to use it?
RIPlink Reference Architecture allows easy integration and testing of various RIPlink building components to form a complete system, mapped onto various hardware architectures.
- with RSP protocol, Gateway Adapter and RSP Gateway may run on different processors, as well as Client Adapter and RSP Client may run on different processors.
- with CRSP API specification, Client Adapter and RSP Client can be integrated as two well defined software components.
- with a stable socket API, IP Application can be more easily integrated on different RSP Clients, but also on regular IP stack.
Of course, it is developer choice to follow or not the specification for interfaces that would remain internal to an implementation.
Read next...
More...
Internal resources
External links
