Module 19 - C101

C101: Introduction to Communications Protocols and Their Uses in ITS Applications

HTML of the PowerPoint Presentation

(Note: This document has been converted from a PowerPoint presentation to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)

 

Slide 1:

Welcome - Graphic image of introductory slide. Please see the Extended Text Description below.

(Extended Text Description: Slide 1: Welcome - Graphic image of introductory slide. A large dark blue rectangle with a wide, light grid pattern at the top half and bands of dark and lighter blue bands below. There is a white square ITS logo box with words “Standards ITS Training” in green and blue on the middle left side. The word “Welcome” in white is to the right of the logo. Under the logo box are the words “RITA Intelligent Transportation Systems Joint Program Office.”)

 

Slide 2:

C101: Introduction to Communications Protocols and Their Uses in ITS Applications

 

Slide 3:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 4:

Instructor

Portrait photo of Raman K Patel, Ph.D., P.E., President, RK Patel Associates, Inc., New York, NY, USA.

Raman K. Patel, Ph.D., P.E.

President

RK Patel Associates, Inc. New York, NY, USA

 

Slide 5:

Target Audience

 

Slide 6:

Recommended Prerequisite(s)

 

Slide 7:

Curriculum Path (Non-SEP)

Curriculum Path (Non-SEP). Please see the Extended Text Description below.

(Extended Text Description: A graphical illustration indicating the sequence of training modules for the standards that include Systems Engineering Process content. Each module is represented by a box with the name of the module in it and an arrow showing the logical flow of the modules and the current module highlighted. The first box is labeled “I101 Using ITS Standards: An Overview.” An arrow from this box connects it to a highlighted box labeled “A101 Introduction to Acquiring Standards-based ITS Systems,” representing this module. An arrow from this box connects it to a box labeled “A102 Introduction to User Needs Identification.” An arrow from this box connects it to a box located at the start of the next line labeled “A201 Details on Acquiring Standards-based ITS Systems.” An arrow from this box connects it to a box labeled “A202 Understanding and Writing User Needs when ITS Standards Do Not Have SEP Content. An arrow from this box connects to A103 “A103 Introduction to ITS Standards Requirements Development.” An arrow from this box connects to “A203 Writing Requirements When ITS Standards Do Not Have SEP Content” and a final arrow connects to last box labeled as “C101 Introduction to Communications Protocols and their Uses in ITS Applications.” )

 

Slide 8:

Curriculum Path

Curriculum Path. Please see the Extended Text Description below.

(Extended Text Description: A graphical illustration showing a top box labeled “C101 Introduction to Communications Protocols and Their Use in ITS Applications.” From this top box, two arrows point to two titles of identical three-element vertical arrays, the left one labeled “Center-to-Field Standards” and the right one labeled “Center-to-Center Standards.” The top boxes are labeled “A3xxa User Needs,” the middle boxes are labeled “A3xxb Requirements,” and the bottom boxes are labeled “T3xx Test Plan.”

 

Slide 9:

Learning Objectives

  1. Be familiar with the basic terminology of the communications process used in NTCIP.
  2. Explain how the NTCIP Framework (Stack) fulfills functional requirements to meet operational needs.
  3. Describe Center-to-Field (C2F) applications and their related NTCIP Standards.
  4. Describe Center-to-Center (C2C) applications and their related NTCIP Standards.

 

Slide 10:

Learning Objective #1 — Be familiar with the basic terminology of the communications process used in NTCIP

 

Slide 11:

Learning Objective #1

Let's Ask Ourselves a Question

"What is the first thing we do when we meet someone?"

 

Slide 12:

Learning Objective #1

We Observe Some "Protocol"

We greet each other with a hand shake....begin conversation... How are you?

A clip art on right top corner of the slide showed two men greeting each other with handshaking gesture. This slide depicts that when we meet people, we typically hand shake-that is a protocol.

 

Slide 13:

Learning Objective #1

Computers Observe Protocol

The slide has a graphic that show two computers connected with a two way arrow heads. The computer set up on both ends has a monitor, a keyboard and mouse, and a vertical tower.

While two computers don't shake hands physically, they do observe some rules—conventions—to begin conversation or communication.

That is what a protocol is about.

 

Slide 14:

Learning Objective #1

What is a Communications Protocol?

Ref. IEEE 610 Std.

 

Slide 15:

Learning Objective #1

Example

Central Management Station. Please see the Extended Text Description below.

(Extended Text Description: A graphic shows a text box that reads “Central Management Station”. This box is connected to a box on right labeled as “Sign Controller”. From this sign controller box, an arrow connects to overhead gentry–sign housing with a message displayed as “Lincoln Tunnel Closed”. Together this graphical example explains how a central management station can display a message on a sign located in the field and control it remotely. )

 

Slide 16:

Learning Objective #1

Parts of a Communications Protocol

 

Slide 17:

Learning Objective #1

What is a Standard?

A standard defines the rules for the exchanges of the data and establishes a format and mandatory definition for the data elements and sequences of exchanges. The standard will include both mandatory (normative) requirements and optional (informative) information to assist in using the standard.

 

Slide 18:

Learning Objective #1

Example of a Standard:

Manual on Uniform Traffic Control Devices (MUTCD)

"When a sign is used to indicate that traffic is always required to stop, a STOP (R1-1) shall be used."

"The STOP sign shall be an octagon with a white legend and border on a red background."

Example of a Standard. Please see the Extended Text Description below.

(Extended Text Description: There are two separate graphics:. The first one shows a title cover page of Manual on Uniform Traffic control Devices (MUTCD). The background is in light blue and the cover page shows a three head traffic signal and an overhead sign with gentry. A second separate graphic underneath the MUTCD tile page show a red background octagonal STOP sign known as R1-1. )

Source: FHWA

 

Slide 19:

Learning Objective #1

ITS Standards

Deal with Data (Information) Structures and Communications, and some ITS Hardware

Benefits

 

Slide 20:

Learning Objective #1

Communications Protocol and Compatibility

"Compatibility is the ability of two or more systems or components to perform their required functions while sharing the same hardware or software environment."

Ref. IEEE 610 Std.

When both ends use the same communications protocols they achieve compatibility.

At the bottom of the text on slide, there are two square boxes: the first box on left is letter A, and the second on right is letter B. Both ends are connected with a two-head arrow.

 

Slide 21:

Learning Objective #1

Illustration

Compatibility

Illustration - Compatibility. Please see the Extended Text Description below.

(Extended Text Description: The slide shows a photo of a computer workstation on the left corner. A two way arrow is shown as a communication channel that connects to the work station. A traffic signal head connects vertically to the arrow as Original equipment. Next to the traffic signal, a vertical combination of traffic controller, camera and a sign is attached as second source equipment. The graphic illustrates that compatibility is achieved when different devices share a communication channel, in this case original traffic signal and newly added equipment. )

 

Slide 22:

Learning Objective #1

How to Achieve Interoperability?

Ref. IEEE 610 Std.

This slide has similar boxes shown in slide 20 above. It states that when both ends have compatibility (use same protocols) and use the same message definitions for the information level, they achieve interoperability.

 

Slide 23:

Learning Objective #1

Interchangeability

Interchangeability. Please see the Extended Text Description below.

(Extended Text Description: A computer clip art is connected to a two way arrow as a communication channel. A graphic of a traffic controller, sign and a camera hangs off the channel. Two separate curved arrows are shown to replace the original camera with a different camera. The graphic conveys that camera can be interchanged or swapped out without losing the original device’s functionality. )

 

Slide 24:

Learning Objective #1

What is a dialog?

At the bottom of the text on slide, there are two square boxes: the first box on left is letter A, and the second on right is letter B. Both ends are connected with a two-head arrow. Overlapped is the text: Connection between the devices is the basis of a dialog.

 

Slide 25:

Learning Objective #1

Benefits of a Common Protocol

Procurement through Multiple Vendors-Cost Savings

Benefits of a Common Protocol. Please see the Extended Text Description below.

(Extended Text Description: The slide graphic begins with a photo of a computer workstation on the left corner. A two way arrow is shown as a communication channel that connects to the work station. The first benefit shown is labeled as “Remote Management Capability” with a graphic of a traffic signal. The second graphic is with two traffic controllers reads “Easier System Expansion” and demonstrates second benefit. The third graphic shows a sign to convey a benefit of industry standard. The last graphic of swapping a camera indicates benefit of multiple vendors for same equipment. Last text box states “Multiple Devices Common Low-Layers”. )

 

Slide 26:

Learning Objective #1

What is a Communications Process?

At the bottom of the text on slide, there are two square boxes: the first box on left is letter A, and the second on right is letter B. Both ends are connected with a two-head arrow. Overlapped is the text: Communication Process

 

Slide 27:

Learning Objective #1

Open Systems Interconnection (OSI) Reference Model (RM)

Structured Approach: Each Layer Performs a Specific Function with an Assigned Protocol

Open Systems Interconnection (OSI) Reference Model (RM). Please see the Extended Text Description below.

(Extended Text Description: The slide has two text boxes with one way arrow in between pointing from left to right. A text box on the left side of the slide shows a closed communication process with the text "Communcation Process (Monolithic, complex, unstructured closed-program). A seven layer box with names is shown on the right. The bottom Physical Layer is labeled as 1 and topmost Application Layer is 7. From bottom to top, the layers are: 1 Physical Layer, 2 Data Link Layer, 3 Network Layer, 4 Transport Layer, 5 Session Layer, 6 Presentation Layer, 7 Application Layer.)

 

Slide 28:

Learning Objective #1

Understanding the Logical Structure of the OSI-RM

Upper three layers provide application services-user requirements.

Intermediate transport layer separates or masks upper and lower layers.

Lower three layers provide end-to-end-network services.

Understanding the Logical Structure of the OSI-RM. Please see the Extended Text Description below.

(Extended Text Description: A seven layer stack is shown on the right of the slide. Layer 7, 6, and 5 are grouped together with aligned text on the left-“Upper layers provide application services-user requirements”. The middle layer (4) is Transport layer. The bottom three layers (1, 2 and 3) are called “Lower layers provide end-to-end-network services”. From bottom to top, the layers are: 1 Physical Layer, 2 Data Link Layer, 3 Network Layer, 4 Transport Layer, 5 Session Layer, 6 Presentation Layer, 7 Application Layer.)

 

Slide 29:

Learning Objective #1

NTCIP Framework

A graphic of the communication levels of the NTCIP standards. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: NTCIP Framework: A graphic of the communication levels of the NTCIP standards. The bottom level is the Plant Level and includes boxes for Dial-up, Fiber, Coax, Wireless, Twisted Pair, and Leased Line. The next higher level is called the Subnetwork Level and includes PPP, Ethernet, and PMPP. The next level is called the Transport Level and includes TCP/IP, UDP/IP, and T2/NULL. The next level is called the Application Level and includes C2C XML, DATEX, FTP, TFTP, SNMP, and STMP. The next level is called the Information Level and includes C2C Messages, Files, Data Objects, and Dynamic Objects. These boxes are connected to an overarching box also in the Information Level labeled Functional Area Data Dictionaries with the left hand side identifying C2C Data Dictionaries and the right hand side labeled NTCIP Data Dictionaries. )

Note: At each level, there are profile standards to choose from. A profile standard is a collection of standards. (23xx, 22xx, and 21xx are profile standards.)

 

Slide 30:

Learning Objective #1

Information Level

Provides Data Dictionary Standards. Please see the Extended Text Description below.

(Extended Text Description: The slide contains the following text and a stack of five vertical text boxes connected to each other on the right:

Provides Data Dictionary Standards

This slide shows five vertical test boxes connected with each other. The first box is Information Level, followed by Application Level, followed by Transport Level, followed by Subnetwork Level and final one is Plant Level. A straight arrow from the first bullet on slide points to Information level box on right. )

 

Slide 31:

Learning Objective #1

Application Level

Provides Standards to Exchange Data/Information. Please see the Extended Text Description below.

(Extended Text Description: The slide contains the following text and a stack of five vertical text boxes connected to each other on the right:

Provides Standards to Exchange Data/Information

The five vertical boxes on the right are the same as Slide 30, except the arrow from first bullet points to Application level box on right. )

 

Slide 32:

Learning Objective #1

Transport Level

Provides Transport Protocols. Please see the Extended Text Description below.

(Extended Text Description: The slide contains the following text and a stack of five vertical text boxes connected to each other on the right:

Provides Transport Protocols

The five vertical boxes on the right are the same as Slide 30, except the arrow from first bullet points to Transport Level box on right. )

 

Slide 33:

Learning Objective #1

Subnetwork Level

Provides Subnetwork Protocols Standards for Network Services. Please see the Extended Text Description below.

(Extended Text Description: The slide contains the following text and a stack of five vertical text boxes connected to each other on the right:

Provides Subnetwork Protocols Standards for Network Services

The five vertical boxes on the right are the same as Slide 30, except the arrow from first bullet points to Subnetwork Level box on right. )

 

Slide 34:

Learning Objective #1

Plant Level

Plant Level includes Physical Layer. Please see the Extended Text Description below.

(Extended Text Description: The slide contains the following text and a stack of five vertical text boxes connected to each other on the right:

Plant Level includes Physical Layer

The five vertical boxes on the right on the right are the same as Slide 30, except the arrow from first bullet points to Plant level box on right. )

 

Slide 35:

Learning Objective #1

Illustration-1

Communications Process for C2F Dialogs

Communications Process for C2F Dialogs. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: The slide shows two photos: one on the left shows a TMC operator with the series of wall mounted video displays shown in the background. The photo on the right show an operational dynamic messages sign on a gentry in the field with a displayed message: “All crossings to new York closed”. Both photos are connected with C2F text and details underneath. Detail text shows three text boxes: Information level NTCIP 1203 DMS. Application Level SMNP and Transport Level protocol. This slide conveys how a TMC uses standards to conduct the C2F communications process. )

 

Slide 36:

Learning Objective #1

Illustration-2

Communications Processes for C2C Dialogs

Communications Processes for C2C Dialogs. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: This slide shows the same TMC operation photo in above slide 34, and has a photo of another operational TMC on the right. Between the two photos is a C2C standard shown as: Information Level TMDD standard, Application Level NTCIP 2306 XML Profile, and Transport Level TCP/IP standard. This slide conveys how TMCs conduct a C2C communication process with C2C standards. )

Note: A Profile Standard is a Combination of Standards. NTCIP 2304 DATEX is also a C2C Profile.

 

Slide 37:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 38:

Learning Objective #1

C2F Device Data Standards are Located at:

Answer Choices

  1. Information Level
  2. Application Level
  3. Transport Level
  4. Subnetwork Level

 

Slide 39:

Learning Objective #1

Review of Answers

A small graphical green and yellow check mark representing correct.a) Information Level
Correct, because Information Level does provide C2F device data standards.

 

A small graphical red and yellow X representing incorrect.b) Application Level
Incorrect, because C2F data standards define data only, while the Application Level houses only the protocols.

 

A small graphical red and yellow X representing incorrect.c) Transport Level
Incorrect, because Transport Level protocols are used for data transfer and they are not device data standards.

 

A small graphical red and yellow X representing incorrect.d) Subnetwork Level
Incorrect, because Subnetwork Level protocols are used for sharing a communication channel and they are not device data standards.

 

Slide 40:

Summary of Learning Objective #1

Be familiar with the basic terminology of the communications process used in the NTCIP.

 

Slide 41:

Summary of Learning Objective #1 (cont.)

Be familiar with the basic terminology of the communications process used in the NTCIP.

 

Slide 42:

Learning Objective #2 — Explain how the NTCIP Framework (Stack) fulfills functional requirements to meet operational needs.

 

Slide 43:

Learning Objective #2

What Problem is NTCIP Addressing?

Inability to communicate between different vendors' devices or share a communication channel

 

Slide 44:

Learning Objective #2

Solution Offered by the NTCIP Framework

 

Slide 45:

Learning Objective #2

NTCIP-Based Device Data Standards

Devices from multiple-vendors can share a communication channel.

NTCIP-Based Device Data Standards. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: NTCIP-Based Device Data Standards: The slide shows 11 square boxes: One on top right corner is marked TMC and is shaded in RED. From the TMC box is a downward arrow is shown in RED. The arrow’s either side is a series of square boxes that lists device data standards. The left side standard begins with Environmental Sensor station and ends in Traffic sensor systems at bottom box. The right side standards begin with Actuated Signal controllers and ends in Field Master-SSM. Each square is shaded green and has NTCP 12xx number. This slide thus serves as an inventory list with NTCIP 12xx numbers. )

 

Slide 46:

Learning Objective #2

Data Dictionaries

Information Level: NTCIP 12xx

 

Slide 47:

Learning Objective #2

What is an Object?

"A data structure used to monitor or control one feature, attribute, or controllable aspect of a manageable device" -NTCIP Standards

The slide has three bubbles or elliptical circles, first is marked with Object 1, second with Object 2 and last with Object n.

 

Slide 48:

Learning Objective #2

Management Information Base (MIB)

CCTV MIB contains over 70 objects. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: The graphic has a rectangular box that contains three bubbles or elliptical circles marked as Object 1, Object 2 and last one Object 70, from which a one way ends into a CCTV MIB cylindrical container. Next to it is image of CCTV camera. Together this layout conveys that 70 objects make up a CCTV MIB used for Camera. )

Illustration: CCTV MIB contains over 70 objects.

 

Slide 49:

Learning Objective #2

Protocol/MIB Relationship

The slide shows three text boxes. Please see the Extended Text Description below.

(Extended Text Description: The slide shows three text boxes: First is marked “MIB provides objects with values”, second “SNMP operations manipulate values of objects” and last “Behavior of the device function altered”. There is an arrow from the first box to next and from second to third box. This shows how they are related to each other. )

 

Slide 50:

Learning Objective #2

Information Level C2C Data Dictionaries

 

Slide 51:

Learning Objective #2

Traffic Management Data Dictionary (TMDD)

Supports C2C System Interface Design

 

Slide 52:

Learning Objective #2

Other Functional Area C2C Dictionaries

See Participant Student Supplement for where to find these standards.

 

Slide 53:

Learning Objective #2

How to Combine a Set of Standards for C2F?

Create a Stack by Selecting a Protocol at Each Level

 

Slide 54:

Learning Objective #2

Example of DMS Deployment Stack

DMS Dialogs can be carried out with this Stack.

The slide is the same as Slide 35, but has a list of specific standards. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: The slide is the same as Slide 35, but has a list of specific standards pointing to C2F in the middle, with their numbers, including NTCIP 1203 DMS, NTCIP 2301 SNMP, NTCIP 2202 UDP/IP, NTCIP 2103 PPP.)

 

Slide 55:

Learning Objective #2

How to Combine a Set of Standards for C2C?

Create a Stack by Selecting a Protocol at Each Level

Example: Traffic Management

 

Slide 56:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 57:

Learning Objective #2

NTCIP 12xx Device Standards Provide:

Answer Choices

  1. Management Information Base (MIB) for each field device
  2. Application protocols such as Simple Network Management Protocol (SNMP) and Simple Transportation Management Protocol (STMP)

 

Slide 58:

Learning Objective #2

Review of answers

A small graphical green and yellow check mark representing correct.a) Management Information Base (MIB) for each field device
Correct, because NTCIP 12xx series standards provide a device-specific MIB.

 

A small graphical red and yellow X representing incorrect.b) Application protocols such as SNMP and STMP
Incorrect, because application level protocols are covered by NTCIP 23xx series standards.

 

Slide 59:

Summary of Learning Objective #2

Explain how the NTCIP Framework (Stack) fulfills functional requirements to meet operational needs.

 

Slide 60:

Learning Objective #3 — Describe Center-to-Field (C2F) applications and their elated NTCIP Standards

Operational Needs

 

Slide 61:

Learning Objective #3

Operational Needs

C2F Standards Supports Management Stationfor:

  1. Configuring a device (parameters)
  2. Monitoring a device and gathering data
  3. Controlling device functions or actions
  4. Retrieving logged/events reports when something "unexpected" happens
    (Exception reporting by agent)

 

Slide 62:

Learning Objective #3

C2F Protocols

Protocols Available for Managing Field Devices:

  1. Simple Network Management Protocol (SNMP)
  2. Simple Transportation Management Protocol (STMP)
  3. File Transfer Protocol (FTP)
  4. Trivial File Transfer Protocol (TFTP)

 

Slide 63:

Learning Objective #3

Simple Network Management Protocol

(SNMP)

 

Slide 64:

Learning Objective #3

SNMP Network Management Model

Provides Capability for Remote Management

SNMP Network Management Model. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: The slide conveys SNMP capability for remote management, by showing two components: on Left Management Station and on right Managed Device. Under the Management Station, three small boxes are shown: Management application, MIB and SNMP Manager. The right side shows Managed Device under which SNMP Agent, MIB and Managed Information are shown. A red solid line connects SNMP Manager on left to SNMP Agent on right. )

 

Slide 65:

Learning Objective #3

Key Components of a SNMP Model

 

Slide 66:

Learning Objective #3

SNMP Operations

 

Slide 67:

Learning Objective #3

SNMP Messages

Request Messages (Retrieval/Modification operations)

Response Messages (Retrieval operations)

 

Slide 68:

Learning Objective #3

Exception Reporting

 

Slide 69:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 70:

Learning Objective #3

To gather data from a detector station, the central SNMP Manager initiates:

Answer Choices

  1. GetRequest message
  2. SetRequest message
  3. Trap message
  4. GetResponse message

 

Slide 71:

Learning Objective #3

Review of Answers

A small graphical green and yellow check mark representing correct.a) GetRequest message
Correct, because GetRequest retrieves values from the agent of the detector station.

 

A small graphical red and yellow X representing incorrect.b) SetRequest message
Incorrect, because SetRequest message is for modifying a value.

 

A small graphical red and yellow X representing incorrect.c) Trap message
Incorrect, because Trap message does not apply; it is not issued by the SNMP manager.

 

A small graphical red and yellow X representing incorrect.d) GetResponse message
Incorrect, because GetResponse message only returns a value requested by GetRequest message._

 

Slide 72:

Learning Objective #3

Simple Transportation Management

Protocol (STMP)

 

Slide 73:

Learning Objective #3

Simple Transportation Management Protocol (STMP) (cont.)

 

Slide 74:

Learning Objective #3

File Transfer Protocol (FTP)

 

Slide 75:

Learning Objective #3

Trivial File Transfer Protocol (TFTP)

 

Slide 76:

Learning Objective #3

Illustration

The slide has a photo of a TMC with operator, and connects to a field DMS device on right. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: The slide has a photo of a TMC with operator, and connects to a field DMS device on right. On the right side, DMS controller box is shown with Agent in it. TMC is connected with one arrow to Agent with Request message and another arrow from the agent to TMC with response message. The DMS sign in box reads DMS Message and it is connected to DMS controller. Together this slide conveys that a TMC makes requests the status of the DMS to the agent which then sends a response with a value back to the TMC. )

 

Slide 77:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 78:

Learning Objective #3

Which of the following is a preferred protocol for monitoring a DMS?

Answer Choices

  1. SNMP
  2. FTP
  3. STMP
  4. NTCIP 2306 XML

 

Slide 79:

Learning Objective #3

Review of answers

A small graphical green and yellow check mark representing correct.a) SNMP
Correct, because SNMP is typically used by convention to interface with the DMS in the field.

 

A small graphical red and yellow X representing incorrect.b) FTP
Incorrect, because FTP is only used for file transfer.

 

A small graphical red and yellow X representing incorrect.c) STMP
Incorrect, because STMP can be used only in ASC applications and by convention it is not typically used for DMS or other devices.

 

A small graphical red and yellow X representing incorrect.d) NTCIP 2306 XML
Incorrect, because NTCIP 2306 XML is a profile standard used in C2C applications.

 

Slide 80:

Summary of Learning Objective #3

Describe Center-to-Field (C2F) applications and their related NTCIP Standards

 

Slide 81:

Learning Objective #4 — Describe Center-to-Center (C2C) applications and their elated NTCIP Standards

 

Slide 82:

Learning Objective #4

C2C Terminology

NTCIP 2304 DATEX Application Profile Standard

NTCIP 2306 XML Application Profile Standard

 

Slide 83:

Learning Objective #4

Operational Needs (C2C)

System Interface Supports Information Exchange

  1. Need to Share Event Information
  2. Need to Provide Control of Devices, Share Status, and Data
  3. Need to Provide Roadway Network Data
  4. Need to Share Data for Archiving

At the bottom of the slide, two boxes are marked as Traffic Management center and are connected with a two way arrow. The arrow states C2C communications.

 

Slide 84:

Learning Objective #4

Types of Generic Dialogs (TMDD)

Dialogs are a logical sequences of messages put together to conduct a "conversation" between centers.

  1. Request/Response - Information Sharing
  2. Subscription - Information Updates
  3. Publication - Published Information

 

Slide 85:

Learning Objective #4

NTCIP 2306 XML Application Profile

 

Slide 86:

Learning Objective #4

Introduction to Web Service

Introduction to Web Service Illustration. Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: The figure show a big rectangul in which a circle is shown marked as Center System. This circle is separated by a solid line. Next are two small circles each marked as OP1 and OP2. Both have one way arrow coming in as Message Input and one way arrow going out as Message Output. Underneath the two OP circle is System Interface. This conveys that the operations performed by system interface use messages. )

 

Slide 87:

Learning Objective #4

SOAP (Simple Object Access Protocol)

SOAP (Simple Object Access Protocol). Please see the Extended Text Description below.

(Extended Text Description: Relevant description from author's notes: The slide has a graphic entitled "SOAP Encodes XML Message," that shows a rectangular shape in which four vertical rectangles are shown: first is marked Envelope, second and third are marked Header and last one a Body. Underneath are boxes with the text "Carries Messages Required" pointing to Envelope, "Carry Instruction Optional" pointing to Header boxes, and "Carry Message Content Required" pointing to Body. The slide conveys three parts of SOAP message. )

 

Slide 88:

Learning Objective #4

NTCIP 2306 Implementation

Table 3 Profile Requirements to Solution Trace (Profile Requirements List)

Profile Requirements List (PRL)

NTCIP 2306 v01 Section

Mandatory / Optional

Profile Requirement

Project Requirement

1.0

SOAP over HTTP

 

 

 

 

 

a) WSDL Request-Response

 

O

 

 

 

- WSDL General

6.1

M

 

 

 

- Definitions

6.2

M

PR 3.1

 

 

- Types/Schema

6.3

M

PR 3.1, 3.2

 

 

Slide 89:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 90:

Learning Objective #4

Which of the following is NOT applicable to C2C?

Answer Choices

  1. NTCIP 2306 XML
  2. SNMP
  3. SOAP
  4. WSDL

 

Slide 91:

Learning Objective #4

Review of Answers

A small graphical red and yellow X representing incorrect.a) NTCIP 2306 XML
Incorrect, because NTCIP 2306 XML is applicable to C2C as a profile standard.

 

A small graphical green and yellow check mark representing correct.b) SNMP
Correct, because SNMP applies to C2F only.

 

A small graphical red and yellow X representing incorrect.c) SOAP
Incorrect, because SOAP is the transport protocol used in NTCIP 2306 XML.

 

A small graphical red and yellow X representing incorrect.d) WSDL
Incorrect, because WSDL is used in C2C as a language standard.

 

Slide 92:

Summary of Learning Objective #4

Describe Center-to-Center (C2C) applications and their related NTCIP Standards

 

Slide 93:

What We Have Learned

  1. We have learned that the NTCIP Family of standards are based on the ISO's OSI-RM
  2. Two categories of the N CIP communications standards are C2F and C2C .
  3. NTCIP objects are based on th ASN.1 anguage representation, which is an ISO standard.
  4. NTCIP 12xx series device data standards are located at the Information Level

 

Slide 94:

What We Have Learned (cont.)

  1. SNMP s used for remote management of ITS devices located in the field.
  2. Specifically, SNMP performs Retrieval and Modification operations to manage a field device.
  3. C2C standards used in the traffic management applications include the TMDD and NTCIP 2306 XML

 

Slide 95:

Resources

 

Slide 96:

Questions? A placeholder graphic image with word Questions? at the top, and an image of a lit light bulb on the lower right side.

 

Slide 97:

Additional Communications Modules

C201: Introduction to Simple Network Management Protocol (SNMP) and its Applications in the Field Devices Based on NTCIP Standards

C202: Introduction to the Application Level Protocols for Center-to-Center Communications System Interface Implementation (NTCIP 2306 XML)