Search
×
FR

Placeholder headline

This is just a placeholder headline

API STD 521: Guide for Pressure-relieving and Depressuring Systems – Edition 6

$

682

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 653: Tank Inspection, Repair, Alteration, and Reconstruction – Edition 4

$

507

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z662:19 – Oil and gas pipeline systems

$

1197

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series-18: Storage of hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z246.2-14 – Emergency preparedness and response for petroleum and natural gas industry systems

$

596

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series:22 – Storage of hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z731-09 (R2014) – Emergency Preparedness and Response

$

177

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z662:23 – Oil and gas pipeline systems

$

1197

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series:26 – Storage of Hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA B51:24 Boiler, Pressure Vessel, and Pressure Piping Code

$

389

BUY NOW

ISO 15784:2024

ISO 15784:2024 Intelligent transport systems – Data exchange involving roadside modules communication – Part 2: Centre to field device communications using Simple Network Management Protocol (SNMP)

CDN $251.00

Description

This document specifies a mechanism for exchanging data and messages in the following cases:

a)       exchange between a traffic management centre and ITS roadside equipment for traffic management;

b)       exchange between ITS roadside equipment used for traffic management.

This document is not applicable to:

     communication between traffic management centres and in-vehicle units;

     communication between ITS roadside equipment and in-vehicle units;

     in-vehicle communication;

     in-cabinet communication;

     motion video transmission from a camera or recorded media.

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

1)       The data to be exchanged can be defined as one or more elements that can be retrieved or stored – SNMP 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 regions to control devices such as dynamic message signs.

2)       Guaranteed, deterministic, real-time exchange of data is not critical – SNMP operations typically require less than 100 ms, but the underlying network can cause multi-second delays in delivering messages or even lost messages; thus, SNMP is not intended 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;

NOTE 1        The dynamic object feature, defined in ISO/TS 26048-1, can be used to eliminate a considerable amount of overhead that is normally associated with SNMP communications to make it more suitable for low-bandwidth links.

     allowing ITS roadside equipment to issue exception reports when special conditions arise.

NOTE 2        Exception reporting uses SNMP notifications in combination with the notification management features defined in ISO/TS 26048-1.

Edition

2

Published Date

2024-06-26

Status

PUBLISHED

Pages

19

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

This document specifies a mechanism for exchanging data and messages in the following cases:

a)       exchange between a traffic management centre and ITS roadside equipment for traffic management;

b)       exchange between ITS roadside equipment used for traffic management.

This document is not applicable to:

-     communication between traffic management centres and in-vehicle units;

-     communication between ITS roadside equipment and in-vehicle units;

-     in-vehicle communication;

-     in-cabinet communication;

-     motion video transmission from a camera or recorded media.

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

1)       The data to be exchanged can be defined as one or more elements that can be retrieved or stored – SNMP 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 regions to control devices such as dynamic message signs.

2)       Guaranteed, deterministic, real-time exchange of data is not critical – SNMP operations typically require less than 100 ms, but the underlying network can cause multi-second delays in delivering messages or even lost messages; thus, SNMP is not intended 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;

NOTE 1        The dynamic object feature, defined in ISO/TS 26048-1, can be used to eliminate a considerable amount of overhead that is normally associated with SNMP communications to make it more suitable for low-bandwidth links.

-     allowing ITS roadside equipment to issue exception reports when special conditions arise.

NOTE 2        Exception reporting uses SNMP notifications in combination with the notification management features defined in ISO/TS 26048-1.

Previous Editions

Can’t find what you are looking for?

Please contact us at: