RSP Protocol

Introduction

The Remote Socket Protocol (RSP) is a simple Remote Procedure Call (RPC) protocol specifically conceived and optimized for RIPlink technology.

As defined in RIPlink Reference Architecture, it is used between the RSP Gateway and the Gateway Adapter, transported over the non-IP network, and then used between Client Adapter and RSP Client.

RSP is independent of the non-IP network used for a specific RIPlink implementation. However, the way RSP is transported over a non-IP network may be adapted to optimize its efficiency.

There are some minor differences on using RSP on the Gateway or on the Device:

RSP messages contain an extra parameter to identify the target/source RSP Client when transported on the Gateway (between RSP Gateway and Gateway Adapter)
Few RSP messages are used on Gateway only, for RSP Gateway - Gateway Adapter initiation
Few RSP messages are used on Device only, for RSP Client - Client Adapter initiation

Main features

RSP protocol contains ~20 messages to be supported on RIPlink Gateway or on RIPlink Device, allowing to:

Initiate between RSP Gateway and Gateway Adapter, and between RSP Client and Client Adapter
Manage binding (connection) between the RIPlink Gateway and a RIPlink Devices
Manage sockets between a RIPlink Device and a RIPlink Gateway
Send and receive TCP and UDP data on a socket

Each message parameter list and format is provided in the RIPlink specification.

Flow chart example

The flow chart below illustrates how RSP protocol can be used to connect to a TCP server, exchange data over that connection, and close that connection.

Detailed flow charts for each situation is illustrated in the RIPlink specification.

RIPlink menu

RSP Protocol

Introduction

Main features

Flow chart example

Read next...

More...

Internal resources

External links

Search

Login