Manual
LCom
Page 78 of 158
5.9 MSSI
The “MSSI” protocol was specified in co-operation with AsfinAG Austria, to provide
an “open protocol” (based on open standards – SOAP, i.e. HTTP and XML) that not
only allows to transfer measurement data from road weather stations and camera
pictures within the AsfinAG Network, but allows the transfer of any measurement
data in any unit without restrictions.
The “AsfinAG compliant” MSSI protocol is a “subset” of the MSSI protocol, in that the
type and unit/encoding of sensor values is limited by AsfinAG to a specific set of
sensors.
A detailed description of the protocol is provided in the MSSI documentation and the
AsfinAG documentation.
The MSSI protocol in the LCom is independent from other “uplink protocols”, i.e.
MSSI can be used in addition to TLS, TLSoIP or NTCIP.
However, if the same “source” sensor (UMB sensor channel) is used for both
protocols (the “uplink” protocol and MSSI), the same value mapping/encoding (except
the specific NTCIP scaling, see above) is used for both protocols, i.e. the
encoding/unit of the sensor value is identical.
Note that you can of course configure an UMB “TLS” channel (that reports values in
the appropriate TLS encoding) to be only reported via TLS (by setting the MSSI type
and/or ID of the sensor to 0), and a different UMB channel (that, for example, reports
the standard SI unit °C for temperature) to be only reported via MSSI (by setting the
TLS FG/Type and Channel to 0), where both UMB sensor channels actually refer to
the same physical sensor.
The MSSI protocol is based on a
“SOAP” service. The station (the LCom) is the
SOAP
“server” (provides the service/data) and the data center (e.g. SmartView3) is
the SOAP client, i.e. connects to the client and requests the data (or other operation).
Please note the following limitations in relation to the MSSI specification:
