scope:

This document specifies a mechanism to exchange data and messages in the following cases.

a) Between a traffic management centre and ITS roadside equipment for traffic management

b) Between ITS roadside equipment used for traffic management

The scope of this document does not include the communication between traffic management centre and in-vehicle units, between ITS roadside equipment and in-vehicle units, in-vehicle communication, in-cabinet communication or motion video transmission from a camera or recorded media.

This document is suitable for use when both of the following conditions apply:

- When the data to be exchanged can be defined as one or more elements that can be retrieved or stored. The protocol can support a wide variety of devices and has adopted the concept of a management information base (MIB), which identifies the configuration, control, and monitoring parameters for ITS roadside equipment. This standardized approach is commonly used for network management applications for devices such as routers, switches, bridges, and firewalls. It is also used in many countries to control devices such as dynamic message signs.

- When guaranteed, deterministic, real-time exchange of data is not critical. SNMP operations are typically fairly fast, but the underlying network can cause delays in delivering messages or even lost messages; thus, the protocol is not appropriate for applications that require reliable sub-second communications.

This document can be used for:

- Intermittent exchange of any defined data. Normal SNMP operations allow messages to be structured by combining any group of elements into a retrieval or storage request.

- Repeated, frequent exchanges of the same message structure (with potentially different values), even on relatively low-bandwidth links.¹⁾

- Allowing ITS roadside equipment to issue exception reports when special conditions arise.²⁾

This document defines how to securely exchange data to manage ITS roadside equioment, also known as field devices. The definition of data for the management of ITS field devices, known as Management Information Bases (MIBs), is defined separately in the ISO 26048 series, regional standards, vendor specifications, and/or project specifications.

¹⁾ The dynamic object feature, defined in ISO 26048-1, can be used to eliminate a considerable amount of overhead that is normally associated with SNMP communications.

²⁾ Exception reporting uses SNMP notifications in combination with the notification management features defined in ISO 26048-1.