ISO/TS 20684-5:2022
(Main)Intelligent transport systems — Roadside modules SNMP data interface — Part 5: Logs
Intelligent transport systems — Roadside modules SNMP data interface — Part 5: Logs
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc. Field devices often need to exchange information with other external entities (managers). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided several individual parts. This document specifies the user needs, requirements and design elements that are used to record timestamped information in a log for later retrieval. This allows a manager to determine the state of a particular object instance nearly simultaneously when the trigger action occurs without frequent polling. NOTE 1 There are similarities between certain portions of NTCIP 1103. NOTE 2 ISO 20684-1 provides additional details about how the ISO 20684 series relates to the overall ITS architecture.
Systèmes de transport intelligents — Interface de données SNMP pour les modules en bord de route — Partie 5: Journal d'événements
General Information
Standards Content (Sample)
TECHNICAL ISO/TS
SPECIFICATION 20684-5
First edition
2022-10
Intelligent transport systems —
Roadside modules SNMP data
interface —
Part 5:
Logs
Systèmes de transport intelligents — Interface de données SNMP pour
les modules en bord de route —
Partie 5: Journal d'événements
Reference number
© ISO 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Conformance . 2
5 User needs . 3
5.1 Log user-defined exceptions . 3
5.1.1 Log user-defined exceptions user need . 3
5.1.2 Log user-defined exception design overview . 3
5.1.3 Graphical relationships. 3
6 Requirements . 4
6.1 Log . 4
6.1.1 Log definition . 4
6.1.2 Log data exchange requirements . 5
6.1.3 Log capability requirements . 5
6.2 Log event factory . 5
6.2.1 Log event factory definition . 5
6.2.2 Log event factory data exchange requirements . 5
6.3 Log manager . 6
6.3.1 Log manager definition . 6
6.3.2 Log management data exchange requirements . 6
6.3.3 Log management capability requirements . 7
7 Dialogues . 7
7.1 Clear old events from a log . 7
8 Security vulnerabilities . 7
Annex A (normative) Management information base (MIB) . 8
Annex B (normative) Requirements traceability matrix (RTM) .19
Bibliography .22
iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
A list of all parts in the ISO 20684 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
Introduction
0.1 Background
The need for standardized communication with ITS field devices is growing around the world.
Several countries have adopted Simple Network Management Protocol (SNMP) based field device
communication standards.
There is a growing view and empirical evidence that standardizing this activity will result in improved
ITS performance, reduced cost, reduced deployment time, and improved maintainability. The ISO 20684
series extends ISO 15784-2 by defining the management information necessary to monitor, configure
and control features of field devices. The data elements defined in all parts of ISO 20684 series may be
used with any protocol but were designed with an expectation that they would be used with one of the
ISO 15784-2 protocols.
By using this approach, agencies can specify open procurements and systems can be expanded
geographically in an open and non-proprietary manner, which reduces costs, speeds up deployment,
and simplifies integration.
0.2 Overview
SNMP is a collection of well-thought-out and well-proven concepts and principles. SNMP employs the
sound principles of abstraction and standardization. This has led to SNMP being widely accepted as the
prime choice for communication between management systems and devices on the internet and other
communications networks.
The original implementation of SNMP was used to manage network devices such as routers and
switches. Since then, the use of SNMP has grown into many areas of application on the internet and has
also been used successfully over various serial communications networks.
This document defines management information for ITS field devices following the SNMP conventions.
0.3 Document approach and layout
This document defines:
a) the conformance requirements for this document (Clause 4);
b) a set of user needs for user-defined trigger conditions that can “fire” to initiate actions (Clause 5);
c) a set of detailed requirements for the identified user needs (Clause 6);
d) custom dialogues for the logging feature (Clause 7);
e) security considerations for the information defined in this document (Clause 8);
f) the management information bases that define the data for the defined requirements (Annex A);
g) the requirements traceability matrix (RTM) that traces the requirements to the design elements
(Annex B).
v
TECHNICAL SPECIFICATION ISO/TS 20684-5:2022(E)
Intelligent transport systems — Roadside modules SNMP
data interface —
Part 5:
Logs
1 Scope
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic
signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS)
environments, etc.
Field devices often need to exchange information with other external entities (managers). Field devices
can be quite complex, necessitating the standardization of many data concepts for exchange. As such,
the ISO 20684 series is divided several individual parts.
This document specifies the user needs, requirements and design elements that are used to record
timestamped information in a log for later retrieval. This allows a manager to determine the state of
a particular object instance nearly simultaneously when the trigger action occurs without frequent
polling.
NOTE 1 There are similarities between certain portions of NTCIP 1103.
NOTE 2 ISO 20684-1 provides additional details about how the ISO 20684 series relates to the overall ITS
architecture.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 20684-1:2021, Intelligent transport systems — Roadside modules SNMP data interface — Part 1:
Overview
ISO/TS 20684-7, Intelligent transport systems – Roadside modules SNMP data interface – Part 7: Support
features
IETF RFC 2578, Structure of Management Information Version 2 (SMIv2), April 1999.
IETF RFC 2579, Textual Conventions for SMIv2, April 1999.
IETF RFC 2580, Conformance Statements for SMIv2, April 1999.
IETF RFC 3411, An Architecture for Describing Simple Network Management Protocol (SNMP) Management
Frameworks, December 2002.
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 20684-1 apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
4 Conformance
This clause follows the rules defined in ISO 20684-1. Table 1 traces each user need to a set of software
features. Table 2 traces each feature to a set of requirements. For a full understanding of these tables
and codes, see ISO 20684-1.
Table 1 — User need and feature conformance
Need Requirement Conformance
5.1: Log user-defined exceptions M
6.1: Log M
6.3: Log manager M
20684-7 6.2: UTC clock M
20684-7 6.4: Object group O
Table 2 — Requirement conformance
Feature Requirement Conformance
6.1: Log
6.1.2.1: Determine log capabilities M
6.1.2.2: Configure global logging limits M
6.1.2.3: Verify global logging configuration M
6.1.2.4: Retrieve logged event M
6.1.3.1: Maximum data size M
6.2: Log event factory
6.2.2.1: Configure a log event factory M
6.2.2.2: Verify configuration of log event factory M
6.2.2.3: Toggle log even
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.