NTCIP 2101:2001 v01.19

Transcription

1 A Joint Standard of AASHTO, ITE, and NEMA NTCIP 2101:2001 v01.19 National Transportation Communications for ITS Protocol Point to Multi-Point Protocol Using RS-232 Subnetwork Profile November 26, 2001 Published by American Association of State Highway and Transportation Officials (AASHTO) 444 North Capitol Street., N.W., Suite 249 Washington, D.C Institute of Transportation Engineers (ITE) th Street, N.W., Suite 300 West Washington, D.C National Electrical Manufacturers Association (NEMA) 1300 North 17th Street, Suite 1847 Rosslyn, Virginia AASHTO / ITE / NEMA. All rights reserved.

2 2001 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Except for the MIB or the PRL, do not copy without written permission of either AASHTO, ITE, or NEMA. Do Not Copy Without Written Permission 2001 AASHTO / ITE / NEMA

3 Page i ACKNOWLEDGEMENTS This publication was prepared by the NTCIP Profiles Working Group, which is a subdivision of the Joint Committee on the NTCIP. The Joint Committee is organized under a Memorandum of Understanding among the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). The Joint Committee on the NTCIP consists of six representatives from each of the standards organizations, and provides guidance for NTCIP development. At the time that this document was prepared, the following individuals were active members of the NTCIP Profiles Working Group: Jas Bhullar Doug Crawford Bob De Roche Bob Force Bud Kent Paul Lim-Hing Bob Martindale Amit Misra Alex Mousadi Kenneth Vaughn Other individuals providing input to the document, include: Bob Barrett Joey Baumgartner Thomas Bryer Blake Christie Ken Earnest Dave Kingery Don Ninke Brian Paulsmeyer Dale Peabody Jeff Racz Joerg Nu Rosenbohm Dan Vanada Hoi Wong Gary Workman In addition to the many volunteer efforts, recognition is also given to those organizations who supported the efforts of the working groups by providing comments and funding for the standard, including: ARINC Caltrans NTCIP DMS Working Group Eagle Traffic Control Systems Econolite Control Products Federal Highway Administration ITE Iteris JPL Mastec Ministry of Transportation, Ontario Minnesota Department of Transportation 2001 AASHTO / ITE / NEMA Do Not Copy Without Written Permission

4 Page ii Mitretek Naztec PB Farradyne Peek Traffic Systems Robert De Roche Consulting Skyline Products Southwest Research Institute Trevilon VHB Virginia Department of Transportation Do Not Copy Without Written Permission 2001 AASHTO / ITE / NEMA

5 Page iii FOREWORD This document uses only metric units. This document defines a subnetwork profile that is a combination of standards intended to meet specific requirements for data transfers to and from roadside devices in either a networked or direct-connect environment. This document is an NTCIP Subnetwork Profile Standard. Subnetwork Profile (SP) Standards provide definitions and requirements for the data link and physical layers of a communications stack that follows the OSI Basic Reference Model. The text includes mandatory requirements in Annex A that are defined as normative. For more information about NTCIP standards, visit the NTCIP Web Site at For a hardcopy summary of NTCIP information, contact the NTCIP Coordinator at the address below. In preparation of this NTCIP document, input of users and other interested parties was sought and evaluated. Inquires, comments, and proposed or recommended revisions should be submitted to: Approvals NTCIP Coordinator National Electrical Manufacturers Association 1300 North 17th Street, Suite 1847 Rosslyn, VA fax: (703) ntcip@nema.org This document was separately balloted and approved by AASHTO, ITE, and NEMA after recommendation by the Joint Committee on the NTCIP. Each organization has approved this standard as the following standard type, as of the date: History AASHTO Standard Specification; December 2000 ITE Software Standard; May 2001 NEMA Standard; May 2001 From 1996 to 1999, this document was referenced as NEMA TS 3.SP-PMPP232. However, to provide an organized numbering scheme for the NTCIP documents, this document is now referenced as NTCIP The technical specifications of NTCIP 2101 are identical to the former reference, except as noted in the development history below: TS 3.SP-PMPP232 v August 1998 Accepted as a User Comment Draft by the Joint Committee on the NTCIP. NTCIP 2101 v October 1999 Accepted as a Recommended Standard by the Joint Committee on the NTCIP. Approved by AASHTO and ITE. NTCIP 2101 v April 2001 Approved by NEMA after disposition of Ballot Comment AASHTO / ITE / NEMA Do Not Copy Without Written Permission

6 Page iv NTCIP 2101:2001 v November 2001 Formatted for printing: incremented version number and revised date; modified and reorganized front matter to conform to NTCIP 8002; revised the Annex A Reproduction Notice; updated references to TS 3.4 to NTCIP 1201:1996 v Do Not Copy Without Written Permission 2001 AASHTO / ITE / NEMA

7 Page v INTRODUCTION The context of the NTCIP is one part of the Intelligent Transportation Systems standardization activities covering base standards, profiles, and registration mechanisms. Base Standards define procedures and rules for providing the fundamental operations associated with communications and information that is exchanged over fixed-point communications links. Profiles define subsets or combinations of base standards used to provide specific functions or services. Profiles prescribe particular subsets or options available in base standards necessary for accomplishing a particular function or service. This provides a basis for the development of uniform, nationally recognized conformance. Registration Mechanisms provide a means to specify and uniquely identify detailed parameters within the framework of base standards and/or profiles. Within the Joint Committee on the NTCIP, the Profiles Working Group is concerned with the methodology of defining profiles, and the definition and documentation of profiles in Standards Publications. This document is intended to provide a complete subnetwork profile (SP) that specifies the communications over an asynchronous, half-duplex or full-duplex dedicated digital circuit. This SP specifies the requirements for an unbalanced connectionless operation. This subnetwork profile can be used with different transport profiles (TP) addressing the network and transport layers with protocols such as UDP or TCP, or it can be used directly with an application profile (AP) such as the Simple Transportation Management Framework. The objective is to facilitate the specification of ITS systems characterized by a high degree of interoperability and interchangeability of its components. This publication defines a subnetwork profile that is a combination of standards intended to meet specific requirements for data transfers to and from roadside devices in either a networked or direct-connect environment. The purpose of this standard is to provide the information necessary to establish a connection using the Point to Multi-Point Protocol (PMPP) via an RS-232 interface. This combination of protocols and standards has been combined in a profile termed SP-PMPP232 within the NTCIP. The SP-PMPP232 is a subnetwork specification and uses protocols and standards to address the Data Link Layer (Layer 2 of the OSI Reference Model) and Physical Layer (Layer 1 of the OSI Reference Model) to manage connected devices that coexist on a common channel. The SP-PMPP232 supports a variety of upper layer protocols over a common physical implementation. It contains mandatory requirement statements that are applicable to all devices claiming conformance to this standard. It also contains options and conditional requirements, which may be applicable to a specific environment in which a device is used. In 1992, the NEMA 3-TS Transportation Management Systems and Associated Control Devices Section began the effort to develop the NTCIP. The Transportation Section s purpose was to respond to user needs to include standardized systems communication in the NEMA TS 2 standard, Traffic Controller Assemblies. Under the guidance of the Federal Highway Administration s NTCIP Steering Group, the NEMA effort was expanded to include the development of communications standards for all transportation field devices that could be used in an Intelligent Transportation Systems (ITS) network. In September 1996, an agreement was executed among AASHTO, ITE, and NEMA to jointly develop, approve, and maintain the NTCIP standards. The Joint Committee on the NTCIP created the Profiles Working Group to develop a method for organizing Class Profiles. The first meeting of the working group was in September After research into how national and international standards organizations combine protocols and standards to address all seven layers of the OSI Basic Reference Model, the committee adopted the approach defined in the NTCIP Profile Framework. Following that approach, a protocol stack was specified by application, transport, and subnetwork profiles. An application profile addresses the 2001 AASHTO / ITE / NEMA Do Not Copy Without Written Permission

8 Page vi application, presentation, and session layers. A transport profile addresses the transport and network layers. A subnetwork profile addresses the data link and physical layers. The NTCIP - Point to Multi-Point Protocol Using RS-232 Subnetwork Profile (SP - PMPP232) is a subnetwork profile for use in center-toroadside communications. Do Not Copy Without Written Permission 2001 AASHTO / ITE / NEMA

9 Page vii If you are not willing to abide by the following notices, return these materials immediately. Joint AASHTO, ITE, and NEMA NTCIP Management Information Base and Data Dictionary DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base ( MIB ) or Data Dictionary ( DD ), AASHTO / ITE / NEMA extends the following permissions: (i) you may make and/or distribute unlimited copies (including derivative works) of the MIB, including copies for commercial distribution, provided that (a) each copy you make and/or distribute contains this Notice and (b) each derivative work of the MIB uses the same module name followed by -, followed by your Internet Assigned Number Authority (IANA)-assigned enterprise number; (ii) use of the MIB is restricted in that the syntax field may be modified only to reflect a more restrictive subrange or enumerated values; (iii) the description field may be modified but only to the extent that: (a) only those bit values or enumerated values that are supported are listed; and (b) the more restrictive subrange is expressed. These materials are delivered AS IS without any warranties as to their use or performance. AASHTO / ITE / NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE, OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL, OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential, or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP Profile Requirements List REPRODUCTION NOTICE AASHTO / ITE / NEMA extend permission to the purchaser of this standards publication to make and/or distribute unlimited copies (including derivative works, which will then be known as PICS) of the excerpt identified as the Profile Requirements List, including copies for commercial distribution, provided that each copy made or distributed contains the notice Based on an NTCIP Profile Requirements List. Used by permission of AASHTO / ITE / NEMA. Disclaimer The information in this publication was considered technically sound by the consensus of persons engaged in the development and approval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreement among every person participating in the development of this document. AASHTO, ITE, and NEMA standards and guideline publications, of which the document contained herein is one, are developed through a voluntary consensus standards development process. This process brings together volunteers and/or seeks out the views of persons who have an interest in the topic 2001 AASHTO / ITE / NEMA Do Not Copy Without Written Permission

10 Page viii covered by this publication. While AASHTO, ITE, and NEMA administer the process and establish rules to promote fairness in the development of consensus, they do not write the document and they do not independently test, evaluate, or verify the accuracy or completeness of any information or the soundness of any judgments contained in their standards and guideline publications. AASHTO, ITE, and NEMA disclaim liability for any personal injury, property, or other damages of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on this document. AASHTO, ITE, and NEMA disclaim and make no guaranty or warranty, express or implied, as to the accuracy or completeness of any information published herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposes or needs. AASHTO, ITE, and NEMA do not undertake to guarantee the performance of any individual manufacturer or seller s products or services by virtue of this standard or guide. In publishing and making this document available, AASHTO, ITE, and NEMA are not undertaking to render professional or other services for or on behalf of any person or entity, nor are AASHTO, ITE, and NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered by this publication may be available from other sources, which the user may wish to consult for additional views or information not covered by this publication. AASHTO, ITE, and NEMA have no power, nor do they undertake to police or enforce compliance with the contents of this document. AASHTO, ITE, and NEMA do not certify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliance with any health or safety related information in this document shall not be attributable to AASHTO, ITE, or NEMA and is solely the responsibility of the certifier or maker of the statement. NTCIP is a trademark of AASHTO / ITE / NEMA. Do Not Copy Without Written Permission 2001 AASHTO / ITE / NEMA

11 Page ix CONTENTS Section 1 GENERAL Scope Profile-Protocol-Layer Relationships References Normative References Informative References Definitions Abbreviations and Acronyms Section 2 CONFORMANCE General Requirements Data Link Layer Requirements Protocol Parameters Addressing Control Field Initial Protocol Identifiers (IPI) Information Field Length FCS Field Modes of Operation Frame Types Procedures Physical Layer Requirements Interface RS-232 Data Rate and Programmable Bit Rates Duplexing Buffering (Frame Size) Data Link Layer / Internet Protocol Interface MIB Requirements The HDLC Group The RS232 Group The RS232 Asynchronous Group The HDLC Group Address Group Annex A PMPP SUBNETWORK PROFILE REQUIREMENT LISTS... A-1 A.1 Introduction... A-1 A.1.1 Notation... A-1 A.2 Standards Referenced... A-3 A.3 PICS Requirements List... A-4 A.3.1 Implementation Identification... A-4 A.3.2 Global Statement of Conformance... A-4 A.4 Basic Requirements... A-5 A.5 Data Link Layer... A-6 A.6 Physical Layer Conformance List... A-9 A.7 Mandatory Object Definitions if SNMP is used... A-11 A.7.1 HDLC Group... A-11 A.7.2 RS232 Asynchronous Group... A-12 A.7.3 HDLC Group Address Group... A AASHTO / ITE / NEMA Do Not Copy Without Written Permission

12 Page x <This page is intentionally left blank> Do Not Copy Without Written Permission 2001 AASHTO / ITE / NEMA

13 Page 1-1 Section 1 GENERAL 1.1 SCOPE This standard is applicable to transportation related devices that must operate in a typical primary/secondary configuration where one device is the designated primary while one or more other devices are connected to one channel acting as secondaries. As a subnetwork profile, it specifies a set of protocols and standards applicable to the data link and physical layers of the OSI Reference Model. The SP-PMPP232 is intended to provide an interoperability standard for the Physical and Data Link Layer aspects of communications in transportation related devices. The primary purpose of this standard is to provide a simple data exchange tool that uses a connectionless delivery mechanism. This subnetwork profile lists the requirements for an implementation using an unbalanced mode of operation for the data link layer that have been derived from the High-Level Data Link Control (HDLC) standard. This subnetwork profile defines not only the definition of the physical and the data link layer protocols but also the interface definition between the data link layer and higher layer protocols. 1.2 PROFILE-PROTOCOL-LAYER RELATIONSHIPS A profile defines a combination of base standards and/or other profiles that collectively perform the intended function. The definition of Subnetwork Profiles and their functions and responsibilities are defined within NTCIP Profile Framework. This profile references computer communications and transportation protocol standards for the Data Link and Physical Layers of the OSI Reference Model. The OSI Reference Model defines seven layers, each performing a particular role in the transmission of data over a medium. This subnetwork profile defines the first two layers. The first layer, the Physical Layer, deals with how the bits of information are transmitted over a communications channel. It deals with the mechanical and electrical interfaces, and the physical transmission medium. The second layer, the Data Link Layer, has the task of transforming the information that came in over the wire into data that appears to be free of transmission errors. It should incorporate mechanisms to insure the integrity of the data and provide a method of insuring that, if need be, no data is lost. An unbalanced configuration provides for only one primary station and one or more secondary stations to operate as point- to-point or point-to-multipoint, half duplex or full duplex, and stop/start (asynchronous) transmission. An unbalanced configuration is a scenario where a designated primary station is responsible for controlling the interchange of data with each secondary station and for establishing and maintaining the link. This subnetwork profile requires a Primary/Secondary relationship between devices and controllers (i.e., this profile does not support contention-based communications). The profile will function on low speed communications links that may either be full or half duplex. This SP does not address higher layer functionality such as routing, segmentation and re-transmission of data packets, nor is it concerned with the application(s) residing in the device. This Subnetwork Profile does not address the organization and definition of the information related to transportation device's end application. Additionally, it does not require a particular Transport Profile or Application Profile. However, it does indicate a particular mechanism to identify higher layer protocols by means of the Initial Protocol Identifier (IPI). The IPI is directly analogous to the Protocol Identifier employed in the Point-to-Point protocol. It provides a mechanism to permit multiplexing messages generated by 2001 AASHTO / ITE / NEMA Do Not Copy Without Written Permission