Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TS 26048-1:2025 — SNMP Data Interface for Intelligent Transport Field Devices
Intelligent transport systems — Field device Simple Network Management Protocol (SNMP) data interface — Part 1: Global objects
Introduction: Standardizing ITS Field Device Management
Modern intelligent transport systems (ITS) rely on a vast array of field devices — traffic signals, variable message signs (VMS), environmental sensor stations, ramp meters, CCTV cameras, and more. Managing these devices across a city-wide or regional network presents a formidable challenge: how do you monitor the operational status of thousands of devices from different manufacturers, configure them remotely, diagnose faults, and ensure they operate reliably 24/7?
ISO/TS 26048-1:2025 answers this question by defining a standardized Simple Network Management Protocol (SNMP) data interface for ITS field devices. Part 1 focuses on global objects — the common management information applicable to virtually all ITS field devices, regardless of type or manufacturer.
SNMP is the de facto standard for network management in IT environments. By bringing SNMP to ITS field devices, this standard enables traffic management centres to use the same tools and workflows they already use for network infrastructure management, reducing training needs and integration costs.
Architecture and Design Principles
Standardized MIB Structure
The standard defines a Management Information Base (MIB) — a structured collection of managed objects that can be accessed via SNMP. The MIB uses ASN.1 (Abstract Syntax Notation One) notation, following the conventions established in the broader SNMP standards community (IETF RFCs).
| MIB Component | Description | Example Objects |
|---|---|---|
| System group | Basic device identification and status | sysDescr, sysName, sysLocation, sysUpTime |
| Authentication | User authentication and access control | authUserTable, authFailCount |
| Device information | Hardware and firmware identification | deviceManufacturer, deviceModel, deviceSerialNumber, firmwareVersion |
| Enclosure monitoring | Physical cabinet/enclosure status | enclosureTemp, enclosureHumidity, doorSwitch, lockStatus |
| Power supply | Electrical supply monitoring | supplyVoltage, batteryStatus, mainsFailCount |
| Environmental sensors | Ambient conditions | ambientTemp, ambientLight, precipitation, windSpeed |
| Event logging | System event recording | eventLogTable, eventSeverity, eventTime |
| Triggers and notifications | Alarm and event-driven actions | triggerTable, notificationChannel, actionConfig |
Communications Architecture
The standard follows a three-tier architecture:
- ITS field device — the physical equipment with an SNMP agent (e.g., a traffic signal controller)
- Communications network — the IP-based network (wired, wireless, cellular) connecting field devices to the management centre
- Network Management Station (NMS) — the central system running SNMP manager software that polls devices and receives traps (autonomous notifications)
This architecture supports both polling (NMS periodically requests data from devices) and trap-based (devices autonomously send notifications when specific conditions occur) management paradigms.
Key User Needs and Functional Requirements
Authentication and Access Control
The standard requires that field devices support SNMPv3 security features, including authentication and encryption. The MIB defines objects for managing user credentials, access levels (read-only, read-write, admin), and monitoring failed authentication attempts — crucial for cybersecurity in critical transport infrastructure.
Environmental and Enclosure Monitoring
One of the most valuable features of the standard is comprehensive environmental monitoring of the field device enclosure (typically a roadside cabinet). The MIB supports monitoring of:
- Internal temperature and humidity (with configurable alarm thresholds)
- Door switch status (tamper detection)
- Heating, ventilation, and cooling (HVAC) component status
- Power supply voltage, battery backup status, and mains fail count
- Auxiliary port monitoring for connected peripheral devices
Engineering insight: Remote monitoring of enclosure climate is often the single most impactful feature for reducing field maintenance costs. A roadside traffic cabinet in direct sunlight can reach internal temperatures of 70 °C — well beyond the operating range of most electronics. Early detection of cooling failures prevents catastrophic equipment damage and reduces emergency maintenance dispatches.
Trigger and Notification System
The standard defines a sophisticated event-driven notification system that allows field devices to autonomously report conditions requiring attention. Key elements include:
- Scheduled triggers: Generate events at specific times (e.g., daily status report at 02:00)
- Day plan triggers: Generate events according to a weekly/daily schedule pattern
- Condition-based triggers: Generate events when monitored values cross thresholds (e.g., enclosure temperature > 65 °C)
- Notification channels: Define how notifications are delivered — SNMP traps, syslog, or email
- Action selection: Associate specific actions (e.g., send trap, log event, execute command) with trigger conditions
Engineering Best Practices for Deployment
MIB Versioning and Management
The standard requires that MIB files be versioned and accessible via the ISO maintenance portal. Each field device should expose its MIB file location and version through standard SNMP objects, enabling NMS software to automatically retrieve and load the correct MIB for each device type.
Efficient Data Exchange
For large ITS deployments with hundreds or thousands of field devices, efficient data exchange is critical. The standard supports:
- Bulk data retrieval using SNMP GetBulkRequest — retrieving large tables in a single operation rather than hundreds of individual GetRequests
- Data snapshot recording — capturing a series of data snapshots at configurable intervals for post-event analysis
- Configurable data logging — defining which parameters are logged and at what resolution based on operational needs
When deploying SNMP management for ITS field devices, network segmentation is critical. Field devices should be on a dedicated management VLAN with strict firewall rules. SNMP traps and management traffic should never traverse the same network segment as passenger-facing ITS services (Wi-Fi, traveller information) to prevent denial-of-service attacks from affecting traffic control operations.
Frequently Asked Questions
Q: What SNMP version does ISO/TS 26048-1 require?
A: The standard supports SNMPv3 for production deployments due to its security features (authentication and encryption). SNMPv2c may be used in isolated, physically secured environments, but this is not recommended for traffic management systems where tampering could have public safety implications.
A: The standard supports SNMPv3 for production deployments due to its security features (authentication and encryption). SNMPv2c may be used in isolated, physically secured environments, but this is not recommended for traffic management systems where tampering could have public safety implications.
Q: Does this standard cover application-specific objects beyond the global objects?
A: Part 1 (this document) covers only global objects common to all ITS field devices. Future parts will define application-specific MIB objects for particular device types such as traffic signals (Part 2), variable message signs (Part 3), and environmental sensors (Part 4).
A: Part 1 (this document) covers only global objects common to all ITS field devices. Future parts will define application-specific MIB objects for particular device types such as traffic signals (Part 2), variable message signs (Part 3), and environmental sensors (Part 4).
Q: How does this standard relate to existing ITS communications protocols like NTCIP (US) or DATEX II (Europe)?
A: ISO/TS 26048-1 complements rather than replaces these protocols. While NTCIP and DATEX II focus on application-layer data exchange for specific ITS services, this standard addresses device-level management — monitoring the health, status, and configuration of the field device itself (power, temperature, enclosure, firmware), which is not covered by those protocols.
A: ISO/TS 26048-1 complements rather than replaces these protocols. While NTCIP and DATEX II focus on application-layer data exchange for specific ITS services, this standard addresses device-level management — monitoring the health, status, and configuration of the field device itself (power, temperature, enclosure, firmware), which is not covered by those protocols.
Q: What happens if a field device loses connectivity to the NMS?
A: The standard requires that devices continue operating autonomously during communication outages. Events are timestamped and stored in the local event log. When connectivity is restored, the NMS can retrieve the buffered events using bulk SNMP queries. The MIB includes objects for tracking “last communication” timestamps and missed poll counts to help operators identify connectivity issues.
A: The standard requires that devices continue operating autonomously during communication outages. Events are timestamped and stored in the local event log. When connectivity is restored, the NMS can retrieve the buffered events using bulk SNMP queries. The MIB includes objects for tracking “last communication” timestamps and missed poll counts to help operators identify connectivity issues.
