aztech c2c interface specification - consystec home · initial draft aztech™ center-to-center...

INITIAL DRAFT

AZTech™ Center-to-Center (C2C) Interface Specification

(Version 1.1)

Prepared by

Consensus Systems Technologies Corp.

SubCarrier Systems Corp.

Prepared for

Maricopa County Department of Transportation

Arizona Department of Transportation

AZTech™

September 12, 2006

AZTech™ Center-to-Center Interface Specification

Table of Contents

INITIAL DRAFT.............................................................................................................................i AZTech™ Center-to-Center (C2C) Interface Specification ...........................................................i (Version 1.1).................................................................................................................................... i Prepared by...................................................................................................................................... i Consensus Systems Technologies Corp.......................................................................................... i SubCarrier Systems Corp.................................................................................................................i Prepared for......................................................................................................................................i Maricopa County Department of Transportation ............................................................................i Arizona Department of Transportation............................................................................................i AZTech™........................................................................................................................................ i ........................................................................................................................................................ i September 12, 2006......................................................................................................................... i Table of Contents.............................................................................................................................i ........................................................................................................................................................v Revision History............................................................................................................................ vi1 Introduction ................................................................................................................................... 1

1.1 Project Background ................................................................................................................ 1 1.2 Specification Development Approach ................................................................................... 1 1.3 Document Organization ........................................................................................................ 2

2 General Requirements ................................................................................................................... 2 2.1 References .............................................................................................................................. 2 2.2 Conformance Statement ......................................................................................................... 3 2.3 Glossary of Terms .................................................................................................................. 3

3 Application Profile for Center-to-Center Communications and PICS ......................................... 4 4 Center Interface Dialog Definitions .............................................................................................. 6

4.1 Dialogs and WSDL Operations ............................................................................................. 6 4.1.1 Dialog – DL_DMSControlRequest ................................................................................. 7 4.1.2 Dialog – DL_DMSInventoryRequest ............................................................................ 7 4.1.3 Dialog – DL_DMSInventoryUpdateSubscriptionPublication ........................................ 9 4.1.4 Dialog – DL_DMSStatusRequest ................................................................................. 10 4.1.5 Dialog – DL_DMSStatusUpdateSubscriptionPublication ............................................ 11 4.1.6 Dialog – DL_DMSArchiveStatusSubscriptionPublication ........................................... 12 4.1.7 Dialog – DL_ESSStatusRequest ................................................................................... 13 4.1.8 Dialog – DL_TMSControlRequest ............................................................................... 14 4.1.9 Dialog – DL_TMSInventoryRequest ............................................................................ 15 4.1.10 Dialog – DL_TMSInventoryUpdateSubscriptionPublication ..................................... 16 4.1.11 Dialog – DL_TMSStatusRequest ............................................................................... 17 4.1.12 Dialog – DL_TMSStatusUpdateSubscriptionPublication .......................................... 18 4.1.13 Dialog – DL_TMSTimingPlanDetailRequest ............................................................. 19 4.1.14 Dialog – DL_TMSArchiveStatusSubscriptionPublication ......................................... 20 4.1.15 Dialog – DL_CancelSubscriptionRequest .................................................................. 21 4.1.16 Dialog – DL_DeviceCancelControlRequest ............................................................... 22

4.2 Web Services Description Language Worksheet ................................................................. 22

i


5 Center Interface Message, Data Frame, and Data Element Definitions ..................................... 26 5.1 Message: CancelSubscriptionRequest-AZTech ................................................................... 26 5.2 Message: DeviceArchiveStatusSubscription-AZTech ......................................................... 26 5.3 Message: DeviceCancelControlRequest-AZTech ............................................................... 27 5.4 Message: DeviceControlSubscriptionResponse-AZTech .................................................... 28 5.5 Message: DeviceInventoryRequest-AZTech ....................................................................... 29 5.6 Message: DeviceInventorySubscription-AZTech ................................................................ 29 5.7 Message: DeviceStatusRequest-AZTech ............................................................................. 30 5.8 Message: DeviceStatusSubscription-AZTech ..................................................................... 30 5.9 Message: DMSControlRequest-AZTech ............................................................................. 31 5.10 Message: DMSInventoryPublication-AZTech .................................................................. 31 5.11 Message: DMSInventoryResponse-AZTech ..................................................................... 32 5.12 Message: DMSStatusPublication AZTech ........................................................................ 32 5.13 Message: DMSStatusResponse-AZTech ........................................................................... 33 5.14 Message: ESSStatusResponse-AZTech ............................................................................. 33 5.15 Message: TimingPlanDetailResponse-AZTech ................................................................. 34 5.16 Message: TMSControlRequest-AZTech ........................................................................... 35 5.17 Message: TMSInformationResponse-AZTech .................................................................. 36 5.18 Message: TMSInformationTimingPlanDetailRequest-AZTech ........................................ 36 5.19 Message: TMSInventoryPublication-AZTech ................................................................... 37 5.20 Message: TMSInventoryResponse-AZTech ...................................................................... 37 5.21 Message: TMSStatusPublication-AZTech ......................................................................... 38 5.22 Message: TMSStatusResponse-AZTech ........................................................................... 38 5.23 Data Frame: AuthorizationSet ........................................................................................... 39 5.24 Data Frame: BroadcastAlerts ............................................................................................. 40 5.25 Data Frame: C2C Message Publication ............................................................................. 40 5.26 Data Frame: C2C Message Subscription ........................................................................... 40 5.27 Data Frame: C2C_MessageReceipt ................................................................................... 41 5.28 Data Frame: C2C_SubscriptionTimeFrame ...................................................................... 41 5.29 Data Frame: ContactDetails ............................................................................................... 42 5.30 Data Frame: Controller-log-entry ...................................................................................... 42 5.31 Data Frame: DateTimePair ................................................................................................ 42 5.32 Data Frame: DetectionLane ............................................................................................... 43 5.33 Data Frame: DetectorDetails .............................................................................................. 43 5.34 Data Frame: DMSDeviceStatus ......................................................................................... 44 5.35 Data Frame: ESSStatus ...................................................................................................... 44 5.36 Data Frame: EXT_LRMS_Distance .................................................................................. 45 5.37 Data Frame: EXT_LRMS_Height ..................................................................................... 48 5.38 Data Frame: Filters ............................................................................................................ 48 5.39 Data Frame: IntersectionDevicesSummary ....................................................................... 49 5.40 Data Frame: IntersectionSummaryStatus .......................................................................... 50 5.41 Data Frame: OrganizationInformationLong ...................................................................... 51 5.42 Data Frame: OrganizationInformationShort ...................................................................... 51 5.43 Data Frame: Overlap .......................................................................................................... 52 5.44 Data Frame: Phase-details .................................................................................................. 52 5.45 Data Frame: Phase ............................................................................................................. 52

ii


5.46 Data Frame: RampMeterControl ....................................................................................... 53 5.47 Data Frame: RampMeterInventory .................................................................................... 54 5.48 Data Frame: RampMeterStatus .......................................................................................... 54 5.49 Data Frame: Schedule-entry .............................................................................................. 55 5.50 Data Frame: SignalControlInventory ................................................................................. 55 5.51 Data Frame: Special-function ............................................................................................ 57 5.52 Data Frame: SubscriptionAction ........................................................................................ 57 5.53 Data Frame: SubscriptionType .......................................................................................... 57 5.54 Data Frame: TimingPlan .................................................................................................... 58 5.55 Data Element: BroadcastAlertsItem .................................................................................. 58 5.56 Data Element: CONTACT_EmailAddress_text ................................................................ 59 5.57 Data Element: CONTACT_Identifier_identifier ............................................................... 59 5.58 Data Element: CONTACT_PersonName_text .................................................................. 59 5.59 Data Element: CONTACT_PersonTitle_text .................................................................... 60 5.60 Data Element: CONTACT_PhoneAlternate_text .............................................................. 60 5.61 Data Element: CONTACT_PhoneNumber_text ................................................................ 60 5.62 Data Element: DETECTOR_Identifier_identifier ............................................................. 60 5.63 Data Element: DETECTOR_IntersectionApproachName_text ........................................ 61 5.64 Data Element: DETECTOR_LaneNumber_code .............................................................. 61 5.65 Data Element: DETECTOR_Type_code ........................................................................... 61 5.66 Data Element: DEVICE_AcknowledgeControl_code ....................................................... 62 5.67 Data Element: DEVICE_CommandEndTime_utc ............................................................ 63 5.68 Data Element: DEVICE_CommandRequestPriority_number ........................................... 63 5.69 Data Element: DEVICE_Identifier_identifier ................................................................... 64 5.70 Data Element: DEVICE_OperationalStatus_code ............................................................. 64 5.71 Data Element: DEVICE_RequestIdentifier_identifier ...................................................... 65 5.72 Data Element: DEVICE_Type_code ................................................................................. 65 5.73 Data Element: EXT_ATIS_Date ....................................................................................... 66 5.74 Data Element: EXT_ATIS_Time ...................................................................................... 66 5.75 Data Element: EXT_DmsMessageBeacon ........................................................................ 67 5.76 Data Element: EXT_DmsMessageMultiString .................................................................. 67 5.77 Data Element: EXT_DmsMessageNumber ....................................................................... 68 5.78 Data Element: EXT_DmsMessageTimeRemaining .......................................................... 68 5.79 Data Element: EXT_DmsSignTechnology ........................................................................ 68 5.80 Data Element: EXT_EssAirTemperature .......................................................................... 69 5.81 Data Element: EXT_EssAvgWindDirection ..................................................................... 70 5.82 Data Element: EXT_EssAvgWindSpeed ........................................................................... 70 5.83 Data Element: EXT_EssPrecipYesNo ............................................................................... 70 5.84 Data Element: EXT_EssSolarRadiation ............................................................................ 71 5.85 Data Element: EXT_EssVisibility ..................................................................................... 71 5.86 Data Element: EXT_EssWindSituation ............................................................................. 71 5.87 Data Element: EXT_LRMS_HorizontalDatum ................................................................. 72 5.88 Data Element: EXT_LRMS_Latitude ................................................................................ 73 5.89 Data Element: EXT_LRMS_Longitude ............................................................................ 73 5.90 Data Element: EXT_LRMS_VerticalDatum ..................................................................... 73 5.91 Data Element: EXT_LRMS_VerticalLevel ....................................................................... 74

iii


5.92 Data Element: EXT_PatternCycleTime ............................................................................. 74 5.93 Data Element: EXT_PatternOffsetTime ............................................................................ 75 5.94 Data Element: FreeText ..................................................................................................... 75 5.95 Data Element: InformationalText ...................................................................................... 75 5.96 Data Element: INTERSECTION_Name_text ................................................................... 75 5.97 Data Element: LINK_Direction_code ............................................................................... 76 5.98 Data Element: LINK_RouteDesignator_identifier ............................................................ 77 5.99 Data Element: MaxOverlaps .............................................................................................. 77 5.100 Data Element: MaxPhases ............................................................................................... 77 5.101 Data Element: METER_Status_code ............................................................................... 77 5.102 Data Element: ORGANIZATION_CenterIdentifier_identifier ....................................... 78 5.103 Data Element: ORGANIZATION_Identifier_identifier .................................................. 78 5.104 Data Element: ORGANIZATION_Name_text ................................................................ 79 5.105 Data Element: ORGANIZATION_SubOrganizationName_text .................................... 79 5.106 Data Element: PhaseNumber ........................................................................................... 79 5.107 Data Element: Phase-Signal-State ................................................................................... 80 5.108 Data Element: RAMP_CurrentState_code ...................................................................... 80 5.109 Data Element: RAMP_ExitRoadwayName_text ............................................................. 81 5.110 Data Element: RAMP_LaneNumber_quantity ................................................................ 81 5.111 Data Element: ReturnAddress .......................................................................................... 82 5.112 Data Element: SECTION_Identifier_identifier ............................................................... 82 5.113 Data Element: SECURITY_Password_text ..................................................................... 82 5.114 Data Element: SECURITY_UserName_text ................................................................... 82 5.115 Data Element: SpecialFunctionList ................................................................................. 83 5.116 Data Element: SplitPhase ................................................................................................. 83 5.117 Data Element: SplitTime .................................................................................................. 84 5.118 Data Element: SubscriptionActionItem ........................................................................... 84 5.119 Data Element: SubscriptionCount .................................................................................... 85 5.120 Data Element: SubscriptionFrequency ............................................................................ 85 5.121 Data Element: SubscriptionID ......................................................................................... 85 5.122 Data Element: SubscriptionName .................................................................................... 86 5.123 Data Element: SubscriptionTypeItem .............................................................................. 86 5.124 Data Element: TimeInterval ............................................................................................. 87 5.125 Data Element: TIMING.PLAN_Identifier_identifier ...................................................... 87 5.126 Data Element: TIMING.PLAN_Name_text .................................................................... 87 5.127 Data Element: Volume-data ............................................................................................. 87

Appendix A – Requirements Traceability Matrix........................................................................ 89 Appendix B - Web Services Description Language Listing.......................................................114 Appendix C - XML Schema Listing...........................................................................................121

Appendix A Requirements Traceability MatrixAppendix B Web Services Description Language ListingAppendix C XML Schema Listing

iv


v


Revision History

Filename Version Date Author Comment

AZTech C2C Interface Specification_v1.doc

1.0 08/16/06 M. Insignares / D. Kelley

Initial Draft

AZTech C2C Interface Specification_v1.1.doc

1.1 09/12/06 M. Insignares / K. Akwabi

Quality Control Review by KHA

vi


1 Introduction

1.1 Project BackgroundThe Maricopa County Department of Transportation (MCDOT), Arizona Department of Transportation (ADOT), and AZTech™ were awarded a federally funded grant in 2004 to deploy an end-to-end communications system to improve public safety and transportation collaboration in the Phoenix metropolitan area. This deployment will result in the expansion of the AZTech™ program, and work towards the deployment of an integrated emergency and transportation operations communications network.

This (Draft) AZTech Center-to-Center Specification has been developed through the consensus input of regional stakeholders to standardize the communication interfaces of center systems. Only the center’s interface (the way the center appears to other centers) is being standardized, the center system software, design, algorithms and methodologies that implement the interface, provided by numerous system integrators and vendors, are not covered by this specification.

1.2 Specification Development ApproachFollowing a Systems Engineering Methodology, a user-needs assessment and concept of operations (ConOps) were developed. Based on the ConOps, functional requirements and stakeholder agreement were developed. The figure below shows the application of the 'VEE' model to the development of the AZTech C2C Interface Specification Development.

1


The system functional requirements for DMS (Dynamic Message Signs) and TMS (Traffic Management Systems) are the basis for development of the technical specifications for information exchange among centers in the region.

Stepping from problem (requirements) to solution (design) a requirements traceability matrix (RTM) was developed to document how the analysis of requirements translates to the project-specific design of center interfaces. The RTM is shown in Appendix A.

1.3 Document Organization

This document is comprised of five Sections and three Appendices.

• Section 1 - Introduction. This section provides an overview of the document and introductory material.

• Section 2 - General Requirements. Contains a list of references to other documents, a conformance statement, and a glossary of terms.

• Section 3 - Application Profile and Transport. Addresses the application level and transport standards for this specification.

• Section 4 - Center Interface Dialog Definitions. Contains a listing of required dialogs and messages and a mapping of the dialogs and messages to a WSDL worksheet.

• Section 5 - Center Interface Message, Data Frame, and Data Element Definitions. Contains a description of all messages, data frames, and data elements.

• Appendix A - Requirements Traceability Matrix. Shows the RTM in table form.• Appendix B - Web Services Description Language Listing.• Appendix C - XML Schema Listing.

2 General RequirementsThis specification is based on project and ITS standards information contained in other documents. All the documents listed in Table 2.1 are available on the project web site. The documents and standards referenced provide background information necessary to understand this specification’s design content. The RTM provides a bridge between the AZTech functional requirements and the design elements contained in this specification.

2.1 ReferencesTable 2-1. References

Organization Document Title Date

AZTech AZTech Transportation and Public Safety Center-to-Center Needs Assessment and Concept of Operations

May 27, 2005

AZTech AZTech Transportation and Public Safety Center-to-Center Dynamic Message Sign (DMS) and Traffic Management Systems (TMS) Functional Requirements

January 3, 2006

NTCIP NTCIP 2306 v01.68 - Application Profile for XML Message February 8, 2006

2


Encoding and Transport in ITS Center-to-Center Communications

NTCIP NTCIP 9010 v01.09 - Information Report, XML in Center-to-Center Communications

November 23, 2004

ITE/AASHTO Traffic Management Center-to-Center Communications {Advanced Traffic Management Data Dictionary (TMDD) and Message Sets (MS)} version 2.1

June 30, 2004

2.2 Conformance Statement

A center’s interface conforms with this specification as follows:

1. A WSDL document and XML Schema exist that conform with the WSDL contained in the Appendix. Each implementing center must replace the WSDL Service EndPoint (contained in the service section of the WSDL) with an appropriate URI. The WSDL SoapAction named “dummy.cgi” (contained in the binding section of the WSDL) must be replaced with an appropriate EndPoint suffix, OR replaced by the following string “’ ‘” (double-quote single-quote space single-quote double-quote), which indicates a blank SoapAction. The URL designation of the SOAP EndPoint of an implementing center is the concatenation of the service and binding section EndPoints.

2. A center system shall demonstrate the support of the web services described in the WSDL and XML Schema by: 1) XML message inputs and outputs described in the WSDL can be reproduced under a system test, 2) XML messages validate against the referenced schema, 3) messages can be exchanged using the dialogs defined in the WSDL.

3. XML Messages are encoded using the SOAP.4. Soap EndPoints are accessible via HTTP.5. The transport for HTTP is TCP/IP and the SOAP EndPoint may be accessed via an IP PING and TCP

traceroute.

2.3 Glossary of Terms

The following glossary defines terms and acronyms used in this standard.

Table 2-2. Glossary of Terms

Term Definition

AASHTO American Association of State Highway and Transportation Officials

AP Application Profile

C2C Center-to-Center

FTP File Transfer Protocol, a file transfer protocol of the IETF.

GZIP A file compression standard of the IETF.

HTTP Hypertext Transfer Protocol

HTTPS Secure HTTP (Hypertext Transfer Protocol)

IETF Internet Engineering Task Force

3


Term Definition

IP Internet Protocol

ITE Institute of Transportation Engineers

ITIS International Traveler Information System (SAE J2540-1)

ITS Intelligent Transportation Systems

LRMS Location Referencing Message Specification

MIME Multipurpose Internet Mail Extensions (IETF RFC 1521)

MS/ETMCC Message Sets for External Traffic Management Center Communications

NEMA National Electrical Manufacturers Association

NTCIP National Transportation Communications for ITS Protocol

NTCIP 9010 NTCIP Information Report on ITS Center-to-Center Communications

PICS Profile Implementation Conformance Statement

PN Profile Need

PR Profile Requirement

PRL Profile Requirements List

SAE Society of Automotive Engineers

SOAP Simple Object Access Protocol

TCP Transmission Control Protocol

TMDD Traffic Management Data Dictionary, a joint standard of ITE/AASHTO

W3C World Wide Web Consortium

WSDL Web Services Description Language

XML eXtensible Markup Language

3 Application Profile for Center-to-Center Communications and PICS

The AZTech C2C Interface Specification shall use the Application Profile for XML Message Encoding and Transport for ITS Center to Center Communications, NTCIP 2306 (NTCIP C2C XML). AZTech centers shall communicate XML messages using the SOAP encoding of XML over the HTTP protocol, and both the request-response and subscription-publication message patterns.

A Project Implementation Conformance Statement (PICS) (taken directly from the 2306 standard) for the project is shown below.

Table 3-3. NTCIP 2306 PICS (Profile Implementation Conformance Statement)

4


Profile Requirements List (PRL)

NTCIP 2306

Section

NTCIP 2306 Mandatory /

Optional

NTCIP 2306 Profile

Require- ment

Project Require-

ment

1.0 SOAP over HTTPa) WSDL Request-Response M Y- WSDL General 6.1 M Y- Definitions 6.2 M PR 3.1 Y- Types/Schema 6.3 M PR 3.1, 3.2 Y- Message 6.4 M PR 3.3 Y- PortType (Interfaces) 7.1.1 M PR 4.1.1 Y- Binding (Transport) 7.1.2 M PR 4.1.2a Y- Service (Transport) 7.1.3 M PR 4.1.2a Y

b) WSDL Publish-Subscribe M Y- WSDL General 6.1 M Y- Definitions 6.2 M PR 3.1 Y- Types/Schema 6.3 M PR 3.1, 3.2 Y- Message 6.4 M PR 3.3 Y- PortType (Interfaces) 6.5, 7.2.1 M PR 4.2.1 Y- Binding (Transport) 7.2.2 M PR 4.2.2a Y- Service (Transport) 7.2.3 M PR 4.2.2a Y

c) Message Encoding YSOAP 4.2.2 M PR 1.2,

4.2.1a, 4.2.1bY

d) Message Transport YHTTP 5.1.3 M PR 2.1a,

4.1.2a, 4.2.2aY

HTTPS 5.1.4, 6.6 O PR 2.1b Y

2.0 XML over HTTPa) WSDL Request Only (XML Direct)

O N

- WSDL General 6.1 M N- Definitions 6.2 M PR 3.1 N- Types/Schema 6.3 M PR 3.1, 3.2 N- Message 6.4 M PR 3.3 N- PortType (Interfaces) 8.1.1 M PR 4.4.1, 3.4 N- Binding (Transport) 8.1.2 M PR 4.4.2a N- Service (Transport) 8.3 M PR 4.4.2a N

b) WSDL Request-Response O N- WSDL General 6.1 M N- Definitions 6.2 M PR 3.1 N- Types/Schema 6.3 M PR 3.1, 3.2 N- Message 6.4 M PR 3.3 N- PortType (Interfaces) 8.2.1 M PR 4.1.1 N- Binding (Transport) 8.2.2 M PR 4.1.2b N- Service (Transport) 8.3 M PR 4.1.2b N

d) Message Encoding NXML Text 4.1.2 M PR 1.1a, N

5


Profile Requirements List (PRL)

NTCIP 2306

Section

NTCIP 2306 Mandatory /

Optional

NTCIP 2306 Profile

Require- ment

Project Require-

ment

4.2.2bXML Gzip 4.1.2 O PR 1.1 a,

4.2.2bN

e) Message Transport NHTTP 5.1.1,

5.1.2M PR 2.1a,

4.2.2bN

HTTPS 5.1.4, 6.6 O PR 2.1a, 4.2.2b

N

3.0 XML over FTP Na) WSDL Request Only (XML Direct)

O N

- WSDL General 6.1 M N- Definitions 6.2 M PR 3.1 N- Types/Schema 6.3 M PR 3.1, 3.2 N- Message 6.4 M PR 3.3 N- PortType (Interfaces) 9.1.2 M PR 4.4.1, 3.4 N- Binding (Transport) 9.1.3 M PR 4.4.2b N- Service (Transport) 9.1.4 M PR 4.4.2b N

b) Message Encoding (one of the following)

N

XML Text 4.1.1 O PR 1.1a, 4.4.2b

N

XML Gzip 4.1.2 O PR 1.1b, 4.4.2b

N

c) Message Transport NFTP 5.2.1 M PR 2.2a,

4.4.2bN

4 Center Interface Dialog Definitions

4.1 Dialogs and WSDL OperationsThis section contains a series of UML diagrams that illustrate the operations, message inputs and outputs of the AZTech C2C information exchange dialogs. Each diagram shows a ‘Center’ and ‘Other Center’. The ‘Other Center’ represents a requester / subscriber, while the ‘Center’ is the responder / publisher.

WSDL Operations are shown next to the grey vertical box on the UML lifeline and have the prefix ‘OP_’. Messages that represent the inputs and outputs to the operation (also read as center function), start with the ‘MSG_’ prefix.

For a complete description of the system functional requirements associated with each dialog, please consult the Requirements Traceability Matrix contained in the Appendix.

6


4.1.1 Dialog – DL_DMSControlRequestThe figure below illustrates the operations, message inputs and outputs of the DMSControlRequest Dialog.

Figure 4-1. DL_DMSControlRequest

Center Other Center

MSG_DMSControlRequest-AZTech

MSG_DeviceControlSubscriptionResponse-AZTech

OP_DMSControlRequest()

4.1.2 Dialog – DL_DMSInventoryRequest The figure below illustrates the operations, message inputs and outputs of the DMSInventoryRequest Dialog.

Figure 4-2. DL_DMSInventoryRequest

7


Center Other Center

MSG_DeviceInventoryRequest-AZTech

MSG_DMSInventoryResponse-AZTech

OP_DMSInventoryRequest()

8


4.1.3 Dialog – DL_DMSInventoryUpdateSubscriptionPublicationThe figure below illustrates the operations, message inputs and outputs of the DMSInventoryUpdateSubscriptionPublication Dialog.

Figure 4-3. DL_DMSInventoryUpdateSubscriptionPublication

Center Other Center

OP_DeviceInventoryUpdateSubscription()

MSG_DeviceInventorySubscription-AZTech



MSG_DMSInventoryPublication-AZTech OP_SubscriberDMSInventoryUpdate()

9


4.1.4 Dialog – DL_DMSStatusRequestThe figure below illustrates the operations, message inputs and outputs of the DMSStatusRequest Dialog.

Figure 4-4. DL_DMSStatusRequest

Center Other Center

MSG_DeviceStatusRequest-AZTech

MSG_DMSStatusResponse-AZTech

OP_DMSStatusRequest()

10


4.1.5 Dialog – DL_DMSStatusUpdateSubscriptionPublicationThe figure below illustrates the operations, message inputs and outputs of the DMSStatusUpdateSubscriptionPublication Dialog.

Figure 4-5. DL_DMSStatusUpdateSubscriptionPublication

Center Other Center

OP_DeviceStatusUpdateSubscription()

MSG_DeviceStatusSubscription -AZTech



MSG_DMSStatusPublication-AZTech OP_SubscriberDMSStatusUpdate()

11


4.1.6 Dialog – DL_DMSArchiveStatusSubscriptionPublicationThe figure below illustrates the operations, message inputs and outputs of the DMSArchiveStatusSubscriptionPublication Dialog.

Figure 4-6. DL_DMSArchiveStatusSubscriptionPublication

Center Other Center

OP_DeviceArchiveStatusSubscription ()

MSG_DeviceArchiveStatusSubscription -AZTech



MSG_DMSStatusPublication-AZTech OP_SubscriberDMSArchiveStatusUpdate()

12


4.1.7 Dialog – DL_ESSStatusRequestThe figure below illustrates the operations, message inputs and outputs of the ESSStatusRequest Dialog.

Figure 4-7. DL_ESSStatusRequest

Center Other Center


MSG_ESSStatusResponse-AZTech

OP_ESSStatusRequest()

13


4.1.8 Dialog – DL_TMSControlRequestThe figure below illustrates the operations, message inputs and outputs of the TMSControlRequest Dialog.

Figure 4-8. DL_TMSControlRequest

Center Other Center

MSG_TMSControlRequest-AZTech


OP_TMSControlRequest()

14


4.1.9 Dialog – DL_TMSInventoryRequestThe figure below illustrates the operations, message inputs and outputs of the TMSInventoryRequest Dialog.

Figure 4-9. DL_TMSInventoryRequest

Center Other Center

MSG_DeviceInventoryRequest-AZTech

MSG_TMSInventoryResponse-AZTech

OP_TMSInventorylRequest()

15


4.1.10 Dialog – DL_TMSInventoryUpdateSubscriptionPublicationThe figure below illustrates the operations, message inputs and outputs of the TMSInventoryUpdateSubscriptionPublication Dialog.

Figure 4-10. DL_TMSInventoryUpdateSubscriptionPublication

Center Other Center

OP_DeviceInventoryUpdateSubscription()

MSG_DeviceInventorySubscription-AZTech



MSG_TMSInventoryPublication-AZTech OP_SubscriberTMSInventoryUpdate()

16


4.1.11 Dialog – DL_TMSStatusRequestThe figure below illustrates the operations, message inputs and outputs of the TMSStatusRequest Dialog.

Figure 4-11. DL_TMSStatusRequest

Center Other Center


MSG_TMSStatusResponse-AZTech

OP_TMSStatusRequest()

17


4.1.12 Dialog – DL_TMSStatusUpdateSubscriptionPublicationThe figure below illustrates the operations, message inputs and outputs of the TMSStatusUpdateSubscriptionPublication Dialog.

Figure 4-12. DL_TMSStatusUpdateSubscriptionPublication

Center Other Center

OP_DeviceStatusUpdateSubscription()

MSG_DeviceStatusSubscription -AZTech



MSG_TMSStatusPublication-AZTech OP_SubscriberTMSStatusUpdate()

18


4.1.13 Dialog – DL_TMSTimingPlanDetailRequestThe figure below illustrates the operations, message inputs and outputs of the TMSTimingPlanDetailRequest Dialog.

Figure 4-13. DL_TMSTimingPlanDetailRequest

Center Other Center

MSG_TMSTimingPlanDetailRequest-AZTech

MSG_TMSTimingPlanDetailResponse-AZTech

OP_TMSTimingPlanDetailRequest()

19


4.1.14 Dialog – DL_TMSArchiveStatusSubscriptionPublicationThe figure below illustrates the operations, message inputs and outputs of the TMSArchiveStatusSubscriptionPublication Dialog.

Figure 4-14. DL_TMSArchiveStatusSubscriptionPublication

Center Other Center

OP_DeviceArchiveStatusSubscription ()

MSG_DeviceArchiveStatusSubscription -AZTech


MSG_DeviceControlSubscriptionResponse

MSG_TMSStatusPublication-AZTech OP_SubscriberTMSArchiveStatusUpdate()

20


4.1.15 Dialog – DL_CancelSubscriptionRequestThe figure below illustrates the operations, message inputs and outputs of the CancelSubscriptionRequest Dialog.

Figure 4-15. DL_CancelSubscriptionRequest

Center Other Center

MSG_CancelSubscriptionRequest-AZTech


OP_CancelSubscriptionRequest()

21


4.1.16 Dialog – DL_DeviceCancelControlRequestThe figure below illustrates the operations, message inputs and outputs of the DeviceCancelControlRequest Dialog.

Figure 4-16. DL_DeviceCancelControlRequest

Center Other Center

MSG_DeviceCancelControlRequest-AZTech


OP_DeviceCancelControlRequest()

4.2 Web Services Description Language WorksheetThe worksheet provided below lists the system interface elements (operations, message encoding, message inputs, message outputs, and transport) in table form. The worksheet was developed through analysis of the required dialogs, shown above. This table provides the information necessary to further develop the WSDL.

22


Table 4-4. Web Services Definition Language Worksheet

Service Encoding Transport Operation Message Input Message Output Msg. Pattern

aztechSoapHttpService SOAP HTTP OP_CancelSubscriptionRequest MSG_DMSControlRequest-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

R/R

aztechSoapHttpService SOAP HTTP OP_DMSControlRequest MSG_DMSControlRequest-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

R/R

aztechSoapHttpService SOAP HTTP OP_DMSInventorylRequest MSG_DeviceInventoryRequest-AZTech MSG_DMSInventoryResponse-AZTech R/R

aztechSoapHttpService SOAP HTTP OP_DMSStatusRequest MSG_DeviceStatusRequest-AZTech MSG_DMSStatusResponse-AZTech R/R

aztechSoapHttpService SOAP HTTP OP_DeviceArchiveStatusSubscription MSG_DeviceArchiveStatusSubscription-AZTech


Sub

aztechSoapHttpService SOAP HTTP OP_DeviceCancelControlRequest MSG_DeviceCancelControlRequest-AZTech


R/R

aztechSoapHttpService SOAP HTTP OP_DeviceInventoryUpdateSubscription MSG_DeviceInventorySubscription-AZTech


Sub

aztechSoapHttpService SOAP HTTP OP_DeviceStatusUpdateSubscription MSG_DeviceStatusSubscription-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

Sub

aztechSoapHttpService SOAP HTTP OP_ESSStatusRequest MSG_DeviceStatusRequest-AZTech MSG_ESSStatusResponse-AZTech R/R

aztechSoapHttpService SOAP HTTP OP_TMSControlRequest MSG_TMSControlRequest-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

R/R

aztechSoapHttpService SOAP HTTP OP_TMSInventorylRequest MSG_DeviceInventoryRequest-AZTech MSG_TMSInventoryResponse-AZTech R/R

aztechSoapHttpService SOAP HTTP OP_TMSStatusRequest MSG_DeviceStatusRequest-AZTech MSG_TMSStatusResponse-AZTech R/R

aztechSoapHttpService SOAP HTTP OP_TMSTimingPlanDetailRequest MSG_TMSTimingPlanDetailRequest-AZTech

MSG_TMSTimingPlanDetailResponse-AZTech

R/R

aztechSubscriberCallbackService

SOAP HTTP OP_SubscriberDMSArchiveStatusUpdate MSG_DeviceStatusPublication-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

Pub


SOAP HTTP OP_SubscriberDMSInventoryUpdate MSG_DMSInventoryPublication-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

Pub


SOAP HTTP OP_SubscriberDMSStatusUpdate MSG_DMSStatusPublication-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

Pub

23


Service Encoding Transport Operation Message Input Message Output Msg. Pattern


SOAP HTTP OP_SubscriberTMSArchiveStatusUpdate MSG_TMSStatusPublication-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

Pub


SOAP HTTP OP_SubscriberTMSInventoryUpdate MSG_TMSInventoryPublication-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

Pub


SOAP HTTP OP_SubscriberTMSStatusUpdate MSG_TMSStatusPublication-AZTech MSG_DeviceControlSubscriptionResponse-AZTech

Pub

MSG Patterns:R/R - Request/ResponseSub – SubscriptionPub – Publication 1-Way - One-Way

Table 4-5. Mapping of WSDL Message Names to XML Schema Elements

Message SchemaElementMSG_CancelSubscriptionRequest-AZTech aztech:cancelSubscriptionRequest-AZTechMSG_DeviceArchiveStatusSubscription-AZTech aztech:deviceArchiveStatusSubscription-AZTechMSG_DeviceCancelControlRequest-AZTech aztech:deviceCancelControlRequest-AZTechMSG_DeviceControlSubscriptionResponse-AZTech aztech:deviceControlSubscriptionResponse-AZTechMSG_DeviceInventoryRequest-AZTech aztech:deviceInventoryRequest-AZTechMSG_DeviceInventorySubscription-AZTech aztech:deviceInventorySubscription-AZTechMSG_DeviceStatusRequest-AZTech aztech:deviceStatusRequest-AZTechMSG_DeviceStatusSubscription-AZTech aztech:deviceStatusSubscription-AZTechMSG_DMSControlRequest-AZTech aztech:dMSControlRequest-AZTechMSG_DMSInventoryResponse-AZTech aztech:dMSInventoryResponse-AZTechMSG_DMSInventoryPublication-AZTech aztech:dMSInventoryPublication-AZTechMSG_DMSStatusResponse-AZTech aztech:dMSStatusResponse-AZTechMSG_DMSStatusPublication-AZTech aztech:dMSStatusPublication-AZTechMSG_ESSStatusResponse-AZTech aztech:eSSStatusResponse-AZTechMSG_TMSControlRequest-AZTech aztech:tMSControlRequest-AZTechMSG_TMSInventoryResponse-AZTech aztech:tMSInventoryResponse-AZTechMSG_TMSInventoryPublication-AZTech aztech:tMSInventoryPublication-AZTechMSG_TMSStatusResponse-AZTech aztech:tMSStatusResponse-AZTechMSG_TMSStatusPublication-AZTech aztech:tMSStatusPublication-AZTechMSG_TMSTimingPlanDetailRequest-AZTech aztech:tMSInformationTimingPlanDetailRequest-AZTechMSG_TMSTimingPlanDetailResponse-AZTech aztech:timingPlanDetailResponse-AZTech

24


25


5 Center Interface Message, Data Frame, and Data Element Definitions

This section lists all the data concepts used in the AZTech XML schema. Note that when a data concept was used, it was taken from another standard and was moved into the AZTech namespace to avoid confusion with the ITS standard from which it came. Messages used in this specification have the term “-AZTech” added to their descriptive, ASN and XML names to aid in this as well. Therefore, any namsespace prefixes in the elements have been removed and all elements appear in the common local namsespace. This has produced a “flat” schema with no further imports.

Text dealing with data concepts meaning were extracted (and then revised) from the final adopted TMDD V2.1 and produce this document.

The original TMDD V2.1 ASN.1 description has been included in the descriptions below. Data concepts not applicable to the project were commented out and a comment added to indicate new project-specific elements as needed. The XML representation indicates the “new” AZTech data concept.

5.1 Message: CancelSubscriptionRequest-AZTechUse: AZTech C2C - Cancel Subscription Request Message, Based on AZTech Device Cancel Control Request Messages for DMS and Signals.

The message meets the data requirements outlined in the January 03, 2006 AZTech Functional Requirements document, as found on Section 4.7 and starting on page 32.

ASN.1 Representation: CancelSubscriptionRequest-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, request-id Device-request-identifier, -- #3108 ... }XML Representation: <xs:element name="cancelSubscriptionRequest-AZTech" type="CancelSubscriptionRequest-AZTech"/><xs:complexType name="CancelSubscriptionRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType>

5.2 Message: DeviceArchiveStatusSubscription-AZTechUse: AZTech C2C - Device Archive Status Information Subscription

The message meets the data requirements outlined in the January 03, 2006 AZTech Functional Requirements document, as found on Section 3.5 and starting on page 17 and Section 4.6 and starting on

26


page 30.

ASN.1 Representation: DeviceArchiveStatusSubscription-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, request-id Device-request-identifier, -- #3108 command-start-time DateTimePair, command-end-time DateTimePair, -- note that XML time is used -- Items below added by Azdot to meet local needs archive-frequency TimeInterval, request-send-time Time, request-send-date Date, -- consider combing to make -- one time element here filters Filters, ...

XML Representation: <xs:element name="deviceArchiveStatusSubscription-AZTech" type="DeviceArchiveStatusSubscription-AZTech"/><xs:complexType name="DeviceArchiveStatusSubscription-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="command-start-time" type="DateTimePair" /> <xs:element name="command-end-time" type="DateTimePair" /> <xs:element name="archive-frequency" type="TimeInterval" /> <xs:element name="request-send-time" type="Time" /> <xs:element name="request-send-date" type="Date" /> <xs:element name="filters" type="Filters" /> </xs:sequence></xs:complexType>

5.3 Message: DeviceCancelControlRequest-AZTechUse: AZTech C2C - Device Cancel Control Request Message, Based on TMDD Device Control Response Messages for DMS and Signals


ASN.1 Representation: DeviceCancelControlRequest-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, device-type Device-type, -- #3747 device-id Device-identifier, --#3701 request-id Device-request-identifier, --#3717 -- Items below added by Azdot to meet local needs freeText FreeText, ...

27


XML Representation: <xs:element name="deviceCancelControlRequest-AZTech" type="DeviceCancelControlRequest-AZTech"/><xs:complexType name="DeviceCancelControlRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-type" type="Device-type" /> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

5.4 Message: DeviceControlSubscriptionResponse-AZTechUse: AZTech C2C - Device Message Response

Based on TMDD Device Control Response Messages for DMS and Signals Also used to acknowledge the following: a Device Inventory Update Subscriptions for DMS and Signals, Device Inventory Update Subscriptions, Device Status Update Subscriptions, Subscription Cancellations, Archival Subscription Cancellations.

ASN.1 Representation: DeviceControlSubscriptionResponse-AZTech ::= SEQUENCE { organization-owning OrganizationInformationLong, organization-requesting OrganizationInformationShort, authorization AuthorizationSet, request-id Device-request-identifier, --#3717 device-id Device-identifier, --#3701 request-status Device-acknowledge-control, -- Below in std but not used -- center-id Organization-center-identifier, -#-3217 -- operator-id Device-organization-operator-identifier, -#-3706 -- request-response Device-acknowledge-control, -#-3763 -- operator-last-revised Event-update-operator-last-revised OPTIONAL, -#-3295 -- response-plan-id Event-response-plan-identifier OPTIONAL -#-3269 -- Items below added by Azdot to meet local needs freeText FreeText, ... }

XML Representation: <xs:element name="deviceControlSubscriptionResponse-AZTech" type="DeviceControlSubscriptionResponse-AZTech"/><xs:complexType name="DeviceControlSubscriptionResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationLong" /> <xs:element name="organization-requesting" type="OrganizationInformationShort" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="request-status" type="Device-acknowledge-control" /> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

28


5.5 Message: DeviceInventoryRequest-AZTechUse: AZTech C2C - Device Inventory Request and Subscription Message, Based on TMDD DMS and Intersection (Signal) Inventory Request Messages

ASN.1 Representation: DeviceInventoryRequest-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, device-type Device-type, -- 3747 -- does having Device-type here limit us to requesting -- only one type of device in the next line?? device-list SEQUENCE (SIZE(1..100000)) OF Device-identifier, -- 3701 -- an id = 0 means request all -- Items below added by Azdot to meet local needs request-id Device-request-identifier, -- 3717 ...

XML Representation: <xs:element name="deviceInventoryRequest-AZTech" type="DeviceInventoryRequest-AZTech"/><xs:complexType name="DeviceInventoryRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-type" type="Device-type" /> <xs:element name="device-list" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="100000"> <xs:element name="device" type="Device-identifier" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType>

5.6 Message: DeviceInventorySubscription-AZTechUse: AZTech C2C - Device Inventory Subscription Message. Based on AZTech Device Inventory Request Message Content of message enclosed in SOAP Body

ASN.1 Representation: DeviceInventorySubscription-AZTech ::= SEQUENCE { c2cMessageSubscription C2cMessageSubscription, deviceInventoryRequest DeviceInventoryRequest-AZTech, ... }

XML Representation: <xs:element name="deviceInventorySubscription-AZTech" type="DeviceInventorySubscription-AZTech"/><xs:complexType name="DeviceInventorySubscription-AZTech" > <xs:sequence> <xs:element name="c2cMessageSubscription" type="C2cMessageSubscription" /> <xs:element name="deviceInventoryRequest" type="DeviceInventoryRequest-AZTech" /> </xs:sequence></xs:complexType>

29


5.7 Message: DeviceStatusRequest-AZTechUse: AZTech C2C - Device Status Information Request Message

Based on TMDD DMS and Intersection (Signal) Status Request Messages

ASN.1 Representation: DeviceStatusRequest-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, -- same question for device type here as before device-type Device-type, -- 3747 device-list SEQUENCE (SIZE(1..100000)) OF Device-identifier, -- 3701 -- an id = 0 means request all -- Items below added by Azdot to meet local needs request-id Device-request-identifier, -- 3717 ... }

XML Representation: <xs:element name="deviceStatusRequest-AZTech" type="DeviceStatusRequest-AZTech"/><xs:complexType name="DeviceStatusRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-type" type="Device-type" /> <xs:element name="device-list" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="100000"> <xs:element name="device" type="Device-identifier" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType>

5.8 Message: DeviceStatusSubscription-AZTechUse: AZTech C2C - Device Status Subscription Message, Based on AZTech Device Status Request Message Content of message enclosed in SOAP Body

ASN.1 Representation: DeviceStatusSubscription-AZTech ::= SEQUENCE { c2cMessageSubscription C2cMessageSubscription, deviceStatusRequest DeviceStatusRequest-AZTech, ... }

XML Representation: <xs:element name="deviceStatusSubscription-AZTech" type="DeviceStatusSubscription-AZTech"/><xs:complexType name="DeviceStatusSubscription-AZTech" > <xs:sequence> <xs:element name="c2cMessageSubscription" type="C2cMessageSubscription" /> <xs:element name="deviceStatusRequest" type="DeviceStatusRequest-AZTech" /> </xs:sequence></xs:complexType>

30


5.9 Message: DMSControlRequest-AZTechUse: AZTech C2C - DMS Control Request Message, Based on TMDD DMS Control Request Message


ASN.1 Representation: DMSControlRequest-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, device-id Device-identifier, -- 3701 request-id Device-request-identifier, -- 3717 dms-beacon-control DmsMessageMultiString, -- 3900 dms-message DmsMessageMultiString, -- 3901 message-number DmsMessageNumber, -- 3902 command-request-priority Device-command-request-priority, -- 3711 command-start-time DateTimePair, command-end-time DateTimePair, -- Items below added by Azdot to meet local needs freeText FreeText, ... }

XML Representation: <xs:element name="dMSControlRequest-AZTech" type="DMSControlRequest-AZTech"/><xs:complexType name="DMSControlRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="dms-beacon-control" type="DmsMessageMultiString" /> <xs:element name="dms-message" type="DmsMessageMultiString" /> <xs:element name="message-number" type="DmsMessageNumber" /> <xs:element name="command-request-priority" type="Device-command-request-priority" /> <xs:element name="command-start-time" type="DateTimePair" /> <xs:element name="command-end-time" type="DateTimePair" /> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

5.10 Message: DMSInventoryPublication-AZTechUse: AZTech C2C - DMS Inventory Update Publication Message

Based on AZTech C2C DMS Inventory Response Message

ASN.1 Representation: DMSInventoryPublication-AZTech ::= SEQUENCE { c2cMessagePublication C2cMessagePublication, dMSInventory DMSInventoryResponse-AZTech, ... }

XML Representation: <xs:element name="dMSInventoryPublication-AZTech" type="DMSInventoryPublication-AZTech"/><xs:complexType name="DMSInventoryPublication-AZTech" >

31


<xs:sequence> <xs:element name="c2cMessagePublication" type="C2cMessagePublication" /> <xs:element name="dMSInventory" type="DMSInventoryResponse-AZTech" /> </xs:sequence></xs:complexType>

5.11 Message: DMSInventoryResponse-AZTechUse: AZTech C2C - DMS Inventory Response Message, Based on TMDD DMS Inventory Message and the DMSDeviceStatus data frame.


ASN.1 Representation: DMSInventoryResponse-AZTech ::= SEQUENCE { organization-owning OrganizationInformationLong, organization-requesting OrganizationInformationShort, devices SEQUENCE (SIZE(0..10000)) OF DMSDeviceStatus, -- note AzDot additions here -- Items below added by Azdot to meet local needs request-id Device-request-identifier, -- 3717 ... }

XML Representation: <xs:element name="dMSInventoryResponse-AZTech" type="DMSInventoryResponse-AZTech"/><xs:complexType name="DMSInventoryResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationLong" /> <xs:element name="organization-requesting" type="OrganizationInformationShort" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="device" type="DMSDeviceStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType>

5.12 Message: DMSStatusPublication AZTechUse: AZTech C2C - DMS Status Information Response Message used in replying to a subscription request.

ASN.1 Representation: DMSStatusPublication-AZTech ::= SEQUENCE { c2cMessagePublication C2cMessagePublication, dMSStatus DMSStatusResponse-AZTech, ... }

32


XML Representation: <xs:element name="dMSStatusPublication-AZTech" type="DMSStatusPublication-AZTech"/><xs:complexType name="DMSStatusPublication-AZTech" > <xs:sequence> <xs:element name="c2cMessagePublication" type="C2cMessagePublication" /> <xs:element name="dMSStatus" type="DMSStatusResponse-AZTech" /> </xs:sequence></xs:complexType>

5.13 Message: DMSStatusResponse-AZTechUse: AZTech C2C - DMS Status Information Response Message


ASN.1 Representation: DMSStatusResponse-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, devices SEQUENCE (SIZE(0..10000)) OF DMSDeviceStatus, -- using: TMDD.DMSDeviceStatus -- note AzDot additions here -- Items below added by Azdot to meet local needs request-id Device-request-identifier, -- 3717 ... }

XML Representation: <xs:element name="dMSStatusResponse-AZTech" type="DMSStatusResponse-AZTech"/><xs:complexType name="DMSStatusResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="device" type="DMSDeviceStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType>

5.14 Message: ESSStatusResponse-AZTechUse: AZTech C2C - Environmental Sensor Station Status Response Message, Based on TMDD ESS Status Message

ASN.1 Representation: ESSStatusResponse-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong,

33


devices SEQUENCE (SIZE(0..10000)) OF ESSStatus, -- Items below added by Azdot to meet local needs request-id Device-request-identifier, -- 3717 ... }

XML Representation: <xs:element name="eSSStatusResponse-AZTech" type="ESSStatusResponse-AZTech"/><xs:complexType name="ESSStatusResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="device" type="ESSStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType>

5.15 Message: TimingPlanDetailResponse-AZTechUse: AZTech C2C - Timing Plan Detail Response Message, Based on TMDD Intersection Device Status Message.


ASN.1 Representation: TimingPlanDetailResponse-AZTech ::= SEQUENCE { --organization-owning OrganizationInformationShort, -- do we not need at least the owner? --organization-requesting OrganizationInformationLong, --authorization AuthorizationSet, device-id Device-identifier, center-id Organization-center-identifier, plans SEQUENCE (SIZE(0..255)) OF TimingPlan, -- Items below added by Azdot to meet local needs maxPhases MaxPhases, phase-details Phase-details, -- req states: movement for each phase, NBT, NBL, NBR etc.. -- the split for each phase ...

XML Representation: <xs:element name="timingPlanDetailResponse-AZTech" type="TimingPlanDetailResponse-AZTech"/><xs:complexType name="TimingPlanDetailResponse-AZTech" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="center-id" type="Organization-center-identifier" /> <xs:element name="plans" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="255"> <xs:element name="plan" type="TimingPlan" /> </xs:sequence>

34


</xs:complexType> </xs:element> <xs:element name="maxPhases" type="MaxPhases" /> <xs:element name="phase-details" type="Phase-details" /> </xs:sequence></xs:complexType>

5.16 Message: TMSControlRequest-AZTechUse: AZTech C2C - Intersection Control Request Message, Based on TMDD Signal Control Timing Plan Request.


ASN.1 Representation: TMSControlRequest-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, device-id Device-identifier, -- 3701 request-id Device-request-identifier, -- 3717 timing-plan-id TimingPlan-identifier, -- note change of element name from std command-request-priority Device-command-request-priority, command-start-time DateTimePair, command-end-time DateTimePair, -- Items below added by AzDot to meet local needs -- ramp meter thresshold request rampMeterControl-req RampMeterControl OPTIONAL, -- requested special function from this device special-functions-req SEQUENCE (SIZE(0..8)) OF Special-function, freeText FreeText, ...

}

XML Representation: <xs:element name="tMSControlRequest-AZTech" type="TMSControlRequest-AZTech"/><xs:complexType name="TMSControlRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="timing-plan-id" type="TimingPlan-identifier" /> <xs:element name="command-request-priority" type="Device-command-request-priority" /> <xs:element name="command-start-time" type="DateTimePair" /> <xs:element name="command-end-time" type="DateTimePair" /> <xs:element name="rampMeterControl-req" type="RampMeterControl" minOccurs="0"/> <xs:element name="special-functions-req" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="special-functions-req-item" type="Special-function" /> </xs:sequence> </xs:complexType>

35


</xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

5.17 Message: TMSInformationResponse-AZTechUse: AZTech C2C - Intersection Information Response Message, Based on TMDD Signal Control Inventory Message plus ramp meter details, and detector inventory.


ASN.1 Representation: TMSInformationResponse-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, -- Items below added by Azdot to meet local needs -- below line handles each Intersection in turn intersections SEQUENCE (SIZE(0..10000)) OF IntersectionDevicesSummary, freeText FreeText, ... }

XML Representation: <xs:element name="tMSInformationResponse-AZTech" type="TMSInformationResponse-AZTech"/><xs:complexType name="TMSInformationResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="intersections" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="intersection" type="IntersectionDevicesSummary" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

5.18 Message: TMSInformationTimingPlanDetailRequest-AZTechUse: AZTech C2C - Intersection Information and Timing Plan Detail Request Message, information request handling is managed via multiple WSDL operations

ASN.1 Representation: TMSInformationTimingPlanDetailRequest-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong, authorization AuthorizationSet, devices SEQUENCE (SIZE(1..100000)) OF Device-identifier, -- 3701 -- an id = 0 means request all -- Items below added by Azdot to meet local needs request-id Device-request-identifier, -- 3717 ...

36


}

XML Representation: <xs:element name="tMSInformationTimingPlanDetailRequest-AZTech" type="TMSInformationTimingPlanDetailRequest-AZTech"/><xs:complexType name="TMSInformationTimingPlanDetailRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="100000"> <xs:element name="device" type="Device-identifier" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType>

5.19 Message: TMSInventoryPublication-AZTechUse: AZTech C2C - TMS Inventory Update Publication Message, Based on AZTech C2C TMS Inventory Response Message


ASN.1 Representation: TMSInventoryPublication-AZTech ::= SEQUENCE { c2cMessagePublication C2cMessagePublication, signalControlInventory TMSInventoryResponse-AZTech, ... }

XML Representation: <xs:element name="tMSInventoryPublication-AZTech" type="TMSInventoryPublication-AZTech"/><xs:complexType name="TMSInventoryPublication-AZTech" > <xs:sequence> <xs:element name="c2cMessagePublication" type="C2cMessagePublication" /> <xs:element name="signalControlInventory" type="TMSInventoryResponse-AZTech" /> </xs:sequence></xs:complexType>

5.20 Message: TMSInventoryResponse-AZTechUse: AZTech C2C - TMS Inventory Response Message, Based on TMDD Signal Control Inventory Message

ASN.1 Representation: TMSInventoryResponse-AZTech ::= SEQUENCE { organization-owning OrganizationInformationLong, organization-requesting OrganizationInformationShort, authorization AuthorizationSet, intersections SEQUENCE (SIZE(0..10000)) OF IntersectionDevicesSummary,

37


-- Problem: The AzTech spec wants an update verb for -- item mentioned here, this could be hard to do. -- let alone hard to build. ... }

XML Representation: <xs:element name="tMSInventoryResponse-AZTech" type="TMSInventoryResponse-AZTech"/><xs:complexType name="TMSInventoryResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationLong" /> <xs:element name="organization-requesting" type="OrganizationInformationShort" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="intersections" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="intersection" type="IntersectionDevicesSummary" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence></xs:complexType>

5.21 Message: TMSStatusPublication-AZTechUse: AZTech C2C - Intersection Status Response Message, Based on TMDD Intersection Status and Ramp Meter Status Messages.

ASN.1 Representation: TMSStatusPublication-AZTech ::= SEQUENCE { c2cMessagePublication C2cMessagePublication, deviceStatus TMSStatusResponse-AZTech, ... }

XML Representation: <xs:element name="tMSStatusPublication-AZTech" type="TMSStatusPublication-AZTech"/><xs:complexType name="TMSStatusPublication-AZTech" > <xs:sequence> <xs:element name="c2cMessagePublication" type="C2cMessagePublication" /> <xs:element name="deviceStatus" type="TMSStatusResponse-AZTech" /> </xs:sequence></xs:complexType>

5.22 Message: TMSStatusResponse-AZTechUse: AZTech C2C - Intersection Status Response Message, Based on TMDD Intersection Status and Ramp Meter Status Messages.


ASN.1 Representation: TMSStatusResponse-AZTech ::= SEQUENCE { organization-owning OrganizationInformationShort, organization-requesting OrganizationInformationLong,

38


authorization AuthorizationSet, devices SEQUENCE (SIZE(1..100)) OF IntersectionSummaryStatus, -- several Azdot needs here -- Items below added by Azdot to meet local needs request-id Device-request-identifier, -- 3717 ...

}

XML Representation: <xs:element name="tMSStatusResponse-AZTech" type="TMSStatusResponse-AZTech"/><xs:complexType name="TMSStatusResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="100"> <xs:element name="device" type="IntersectionSummaryStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType>

5.23 Data Frame: AuthorizationSetUse: A data frame which contains the authorization information provided by a user as credentials for a message. Typically this information is validated against an X.509 certificate using XMLSEC methods. The contents of this data frame should be suppressed if the message is to be relayed to other down stream machines after the authorization has competed. The entire message should be deleted if the authorization fails.

ASN.1 Representation: AuthorizationSet ::= SEQUENCE { user-id Security-user-name, -- #3108 password Security-password, -- #3109 hashtime DateTimePair, -- XML style date and time hash IA5String (SIZE(10..20)), -- the securty hash determined by -- the x.509 cert in base-64 form ... }

XML Representation: <xs:complexType name="AuthorizationSet" > <xs:sequence> <xs:element name="user-id" type="Security-user-name" /> <xs:element name="password" type="Security-password" /> <xs:element name="hashtime" type="DateTimePair" /> <xs:element name="hash" > <xs:simpleType> <xs:restriction base="xs:string"> <xs:minLength value="10"/>

39


<xs:maxLength value="20"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence></xs:complexType>

5.24 Data Frame: BroadcastAlertsUse: A collection of BroadcastAlertsItem items

ASN.1 Representation: BroadcastAlerts ::= SEQUENCE (SIZE(1..2)) OF BroadcastAlertsItem

XML Representation: <xs:complexType name="BroadcastAlerts" > <xs:sequence minOccurs="1" maxOccurs="2"> <xs:element name="broadcastAlert" type="BroadcastAlertsItem" /> </xs:sequence></xs:complexType>

5.25 Data Frame: C2C Message PublicationUse: This is a data frame used in the response to the subscription process.

ASN.1 Representation: C2cMessagePublication ::= SEQUENCE { informationalText InformationalText OPTIONAL, subscriptionID SubscriptionID, subscriptionName SubscriptionName OPTIONAL, subscriptionFreq SubscriptionFrequency OPTIONAL, subscriptionCount SubscriptionCount OPTIONAL, ... }

XML Representation: <xs:complexType name="C2cMessagePublication" > <xs:sequence> <xs:element name="informationalText" type="InformationalText" minOccurs="0"/> <xs:element name="subscriptionID" type="SubscriptionID" /> <xs:element name="subscriptionName" type="SubscriptionName" minOccurs="0"/> <xs:element name="subscriptionFreq" type="SubscriptionFrequency" minOccurs="0"/> <xs:element name="subscriptionCount" type="SubscriptionCount" minOccurs="0"/> </xs:sequence></xs:complexType> In addition, this item may be used by data structures in other ITS standards.

Remarks: Update to use the C2C schema fragments for this part!

5.26 Data Frame: C2C Message SubscriptionUse: This is a data frame used in the subscription process.

ASN.1 Representation: C2cMessageSubscription ::= SEQUENCE { informationalText InformationalText OPTIONAL, returnAddress ReturnAddress, subscriptionAction SubscriptionAction, subscriptionType SubscriptionType, subscriptionID SubscriptionID,

40


subscriptionName SubscriptionName OPTIONAL, subscriptionTimeFrame SubscriptionTimeFrame OPTIONAL, subscriptionFrequency SubscriptionFrequency, broadcastAlerts BroadcastAlerts OPTIONAL, ... }

XML Representation: <xs:complexType name="C2cMessageSubscription" > <xs:sequence> <xs:element name="informationalText" type="InformationalText" minOccurs="0"/> <xs:element name="returnAddress" type="ReturnAddress" /> <xs:element name="subscriptionAction" type="SubscriptionAction" /> <xs:element name="subscriptionType" type="SubscriptionType" /> <xs:element name="subscriptionID" type="SubscriptionID" /> <xs:element name="subscriptionName" type="SubscriptionName" minOccurs="0"/> <xs:element name="subscriptionTimeFrame" type="SubscriptionTimeFrame" minOccurs="0"/> <xs:element name="subscriptionFrequency" type="SubscriptionFrequency" /> <xs:element name="broadcastAlerts" type="BroadcastAlerts" minOccurs="0"/> </xs:sequence></xs:complexType> In addition, this item may be used by data structures in other ITS standards.

5.27 Data Frame: C2C_MessageReceiptUse: AAA An empty definition field.

ASN.1 Representation: C2cMessageReceipt ::= SEQUENCE { informationalText InformationalText, ... }

XML Representation: <xs:complexType name="C2cMessageReceipt" > <xs:sequence> <xs:element name="informationalText" type="InformationalText" /> </xs:sequence></xs:complexType>

5.28 Data Frame: C2C_SubscriptionTimeFrameUse: Time frame during which (the) subscriber requests that (the) publication be active.

ASN.1 Representation: SubscriptionTimeFrame ::= SEQUENCE { start DateTimePair, end DateTimePair, ... } -- using XML values

XML Representation: <xs:complexType name="SubscriptionTimeFrame" > <xs:sequence> <xs:element name="start" type="DateTimePair" /> <xs:element name="end" type="DateTimePair" /> </xs:sequence></xs:complexType>

41


5.29 Data Frame: ContactDetailsUse: A collection of contact data elements defined by TMDD and refined for use by AzDot

ASN.1 Representation: ContactDetails ::= SEQUENCE { contact-id Contact-identifier, --3105 person-name Contact-person-name OPTIONAL, --3206 person-title Contact-person-title OPTIONAL, --3349 -- organization-id Organization-identifier OPTIONAL, -#-3343 -- organization-name Organization-name OPTIONAL, -#-3344 phone-number Contact-phone-number OPTIONAL, --3207 phone-alternate Contact-phone-alternate OPTIONAL, --3113 -- mobile-number Contact-mobile-phone-number OPTIONAL, -#-3350 -- fax-number Contact-phone-fax OPTIONAL, -#-3205 -- pager-id Contact-pager-identifier OPTIONAL, -#-3346 -- pager-number Contact-pager-number OPTIONAL, -#-3347 email-address Contact-email-address OPTIONAL, --3204 -- radio-unit Contact-radio-unit-identifier OPTIONAL, -#-3208 -- address-line1 Contact-mailing-address-line1 OPTIONAL, -#-3339 -- address-line2 Contact-mailing-address-line2 OPTIONAL, -#-3340 -- city Contact-mailing-address-city OPTIONAL, -#-3338 -- state Contact-mailing-address-state OPTIONAL, -#-3341 -- zip-code Contact-mailing-address-zip OPTIONAL, -#-3342 -- country Contact-mailing-address-country OPTIONAL -#-3373 ... }

XML Representation: <xs:complexType name="ContactDetails" > <xs:sequence> <xs:element name="contact-id" type="Contact-identifier" /> <xs:element name="person-name" type="Contact-person-name" minOccurs="0"/> <xs:element name="person-title" type="Contact-person-title" minOccurs="0"/> <xs:element name="phone-number" type="Contact-phone-number" minOccurs="0"/> <xs:element name="phone-alternate" type="Contact-phone-alternate" minOccurs="0"/> <xs:element name="email-address" type="Contact-email-address" minOccurs="0"/> </xs:sequence></xs:complexType>

5.30 Data Frame: Controller-log-entryUse: A data frame with the time of the entry and the entry (text) itself.

ASN.1 Representation: Controller-log-entry ::= SEQUENCE { time DateTimePair, text FreeText, ... }XML Representation: <xs:complexType name="Controller-log-entry" > <xs:sequence> <xs:element name="time" type="DateTimePair" /> <xs:element name="text" type="FreeText" /> </xs:sequence></xs:complexType>

5.31 Data Frame: DateTimePairUse: A representation of date, time, and time zone in the standard XML formats.

42

ASN.1 Representation: DateTimePair ::= SEQUENCE { date Date, time Time, offset Time, ... } -- expressed in basic XML date and time

XML Representation: <xs:simpleType name="DateTimePair"> <xs:restriction base="xs:dateTime"/></xs:simpleType>

5.32 Data Frame: DetectionLaneUse: Used asis from TMDD with only formatting clean up changes.

ASN.1 Representation: DetectionLane ::= SEQUENCE { approach-name Detector-intersection-approach-name OPTIONAL, --3505 lane-number Detector-lane-number OPTIONAL, --3506 ... }

XML Representation: <xs:complexType name="DetectionLane" > <xs:sequence> <xs:element name="approach-name" type="Detector-intersection-approach-name" minOccurs="0"/> <xs:element name="lane-number" type="Detector-lane-number" minOccurs="0"/> </xs:sequence></xs:complexType>

5.33 Data Frame: DetectorDetailsUse: Taken from the TMDD data frame by the same name and adjusted to meet AZTech needs.

ASN.1 Representation: DetectorDetails ::= SEQUENCE { detector-id Detector-identifier, --3504 -- detector-name Detector-name OPTIONAL, -#-3520 -- detector-location LRMS.GeoLocation OPTIONAL, -- simple lat-long added here device-latitude Latitude, device-longitude Longitude, -- route-designator Link-route-designator OPTIONAL, -#-3030 -- linear-reference Link-location-linear-reference OPTIONAL, -#-3855 -- linear-reference-version Link-location-linear-reference-version OPTIONAL, -#-3854 -- detector-link-id Detector-link-identifier OPTIONAL, -#-3507 link-direction Link-direction OPTIONAL, --3008 detector-type Detector-type, --3514 detection-lanes SEQUENCE (SIZE(1..64)) OF DetectionLane, -- note "s" added to above name -- last-update-time DateTimeZone OPTIONAL -- Added by AZTech setback Distance, -- setback form stop bar ...

43


XML Representation: <xs:complexType name="DetectorDetails" > <xs:sequence> <xs:element name="detector-id" type="Detector-identifier" /> <xs:element name="device-latitude" type="Latitude" /> <xs:element name="device-longitude" type="Longitude" /> <xs:element name="link-direction" type="Link-direction" minOccurs="0"/> <xs:element name="detector-type" type="Detector-type" /> <xs:element name="detection-lanes" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="64"> <xs:element name="detection-lane" type="DetectionLane" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="setback" type="Distance" /> </xs:sequence></xs:complexType>

5.34 Data Frame: DMSDeviceStatusUse: In TMDD this is documented a message, here is it used as a data frame.

ASN.1 Representation: DMSDeviceStatus ::= SEQUENCE { -- organization-information OrganizationInformation, -- Confirm above is never in fact used or needed -- operator-id Organization-center-operator-identifier, -#-3112 device-id Device-identifier, --3701 dms-device-status Device-operational-status, --3716 dms-current-message DmsMessageMultiString, --3901 message-time-remaining DmsMessageTimeRemaining OPTIONAL, --3904 -- message-source-mode NTCIP.DmsMsgSourceMode OPTIONAL, -#-3905 -- associated-event-id Event-response-plan-identifier OPTIONAL, -#-3269 last-comm-time DateTimePair, ...

XML Representation: <xs:element name="dMSDeviceStatus" type="DMSDeviceStatus"/><xs:complexType name="DMSDeviceStatus" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="dms-device-status" type="Device-operational-status" /> <xs:element name="dms-current-message" type="DmsMessageMultiString" /> <xs:element name="message-time-remaining" type="DmsMessageTimeRemaining" minOccurs="0"/> <xs:element name="last-comm-time" type="DateTimePair" /> </xs:sequence></xs:complexType>

5.35 Data Frame: ESSStatusUse: Note that in the TMDD standard this is a message. Here it is treated as a data frame.

ASN.1 Representation: ESSStatus ::= SEQUENCE { center-id Organization-center-identifier OPTIONAL, --3217 -- operator-id Device-organization-operator-identifier, -#-3706 device-id Device-identifier, --3701 device-status Device-operational-status, --3716 -- device-name Device-name OPTIONAL, -#-3709 avg-wind-direction EssAvgWindDirection, --3910

44


avg-wind-speed EssAvgWindSpeed OPTIONAL, --3911 wind-situation EssWindSituation OPTIONAL, --3935 air-temperature EssAirTemperature OPTIONAL, --3908 precip-yes-no EssPrecipYesNo OPTIONAL, --3921 solar-radiation EssSolarRadiation OPTIONAL, --3926 visibility EssVisibility OPTIONAL, --3932 -- visibility-situation NTCIP.EssVisibilitySituation OPTIONAL, -#-3933 -- surface-status NTCIP.EssSurfaceStatus OPTIONAL,-#-3929 -- pave-treat-type NTCIP.EssPaveTreatProductType OPTIONAL -#-3918 ... }

XML Representation: <xs:element name="eSSStatus" type="ESSStatus"/><xs:complexType name="ESSStatus" > <xs:sequence> <xs:element name="center-id" type="Organization-center-identifier" minOccurs="0"/> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="device-status" type="Device-operational-status" /> <xs:element name="avg-wind-direction" type="EssAvgWindDirection" /> <xs:element name="avg-wind-speed" type="EssAvgWindSpeed" minOccurs="0"/> <xs:element name="wind-situation" type="EssWindSituation" minOccurs="0"/> <xs:element name="air-temperature" type="EssAirTemperature" minOccurs="0"/> <xs:element name="precip-yes-no" type="EssPrecipYesNo" minOccurs="0"/> <xs:element name="solar-radiation" type="EssSolarRadiation" minOccurs="0"/> <xs:element name="visibility" type="EssVisibility" minOccurs="0"/> </xs:sequence></xs:complexType>

5.36 Data Frame: EXT_LRMS_DistanceUse: A choice of distance values, in integer or REAL expressions, in different English and metric units. Note that the data elements for REAL representations are suffixed with Dec.

ASN.1 Representation: Distance ::= CHOICE { m INTEGER (-10000000..10000000), mDec REAL (-10000000..10000000), mm INTEGER (-1000000..1000000), mmDec REAL (-1000000..1000000), dm INTEGER (-1000000..1000000), dmDec REAL (-1000000..1000000), yd INTEGER (-17600000..17600000), ydDec REAL (-17600000..17600000), ft INTEGER (-52800000..52800000), ftDec REAL (-52800000..52800000), in INTEGER (-1000000..1000000), inDec REAL (-1000000..1000000), mi INTEGER (-10000..10000), miDec REAL (-10000..10000), km INTEGER (-10000..10000), kmDec REAL (-10000..10000) }

XML Representation: <xs:complexType name="Distance" > <xs:choice> <xs:element name="m" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-10000000"/> <xs:maxInclusive value="10000000"/>

45

</xs:restriction> </xs:simpleType> </xs:element> <xs:element name="mDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-10000000"/> <xs:maxInclusive value="10000000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="mm" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="mmDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="dm" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="dmDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="yd" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-17600000"/> <xs:maxInclusive value="17600000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="ydDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-17600000"/> <xs:maxInclusive value="17600000"/> </xs:restriction> </xs:simpleType> </xs:element>   

46

<xs:element name="ft" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-52800000"/> <xs:maxInclusive value="52800000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="ftDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-52800000"/> <xs:maxInclusive value="52800000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="in" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="inDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="mi" > <xs:simpleType> <xs:restriction base="xs:short"> <xs:minInclusive value="-10000"/> <xs:maxInclusive value="10000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="miDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-10000"/> <xs:maxInclusive value="10000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="km" > <xs:simpleType> <xs:restriction base="xs:short"> <xs:minInclusive value="-10000"/> <xs:maxInclusive value="10000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="kmDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-10000"/> <xs:maxInclusive value="10000"/> </xs:restriction>

47

</xs:simpleType> </xs:element>    </xs:choice></xs:complexType>

5.37 Data Frame: EXT_LRMS_HeightUse: A vertical height expressed as either an altitude with reference to a vertical datum, or a vertical level from -127 to +127, where level 0 is the ground surface, or ground level of a structure.

ASN.1 Representation: Height ::= CHOICE { altdatum SEQUENCE { altitude Distance, verticalDatum VerticalDatum OPTIONAL }, verticalLevel VerticalLevel }

XML Representation: <xs:complexType name="Height" > <xs:choice> <xs:element name="altdatum" > <xs:complexType> <xs:sequence> <xs:element name="altitude" type="Distance" /> <xs:element name="verticalDatum" type="VerticalDatum" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="verticalLevel" type="VerticalLevel" /> </xs:choice></xs:complexType>

5.38 Data Frame: FiltersUse: Filters used in the subscription message process.

ASN.1 Representation: Filters ::= SEQUENCE { dms-status-information BOOLEAN, -- subscription to DMS status information -- included true/false (yes/no) ess-status-information BOOLEAN, -- subscription to ESS status information -- included true/false (yes/no) ... }

XML Representation: <xs:complexType name="Filters" > <xs:sequence> <xs:element name="dms-status-information" > <xs:simpleType> <xs:restriction base="xs:boolean"/> </xs:simpleType> </xs:element> <xs:element name="ess-status-information" >

48


<xs:simpleType> <xs:restriction base="xs:boolean"/> </xs:simpleType> </xs:element> </xs:sequence></xs:complexType>

5.39 Data Frame: IntersectionDevicesSummaryUse: A composite data frame developed for AZTech use which combines the elements of the TMDD:IntersectionDeviceStatus along with sequences of timing plans, detector lists, ramp meters, and schedule times to provide a complete summary of the intersection. Note that this data frame provides inventory information about the devices, the IntersectionDeviceStatus data frame provides current status of these same devices.

ASN.1 Representation: IntersectionDevicesSummary ::= SEQUENCE { -- Items below added by Azdot to meet local needs -- controls at this Intersection signalControlInformation SEQUENCE (SIZE(0..64)) OF SignalControlInventory, -- plans used at this Intersection timing-plans SEQUENCE (SIZE(0..255)) OF TimingPlan, -- detectors detectors SEQUENCE (SIZE(0..64)) OF DetectorDetails, -- use schedules schedule-plans SEQUENCE (SIZE(0..64)) OF Schedule-entry, maxOverlaps MaxOverlaps, overlaps SEQUENCE (SIZE(0..64)) OF Overlap, -- Ramp Meters rampMeters SEQUENCE (SIZE(0..64)) OF RampMeterInventory, freeText FreeText, ... }

XML Representation: <xs:complexType name="IntersectionDevicesSummary" > <xs:sequence> <xs:element name="signalControlInformation" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="signalControlInformation-item" type="SignalControlInventory" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="timing-plans" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="255"> <xs:element name="timing-plan" type="TimingPlan" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="detectors" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="detector" type="DetectorDetails" />

49


</xs:sequence> </xs:complexType> </xs:element> <xs:element name="schedule-plans" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="schedule-plan" type="Schedule-entry" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="maxOverlaps" type="MaxOverlaps" /> <xs:element name="overlaps" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="overlap" type="Overlap" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="rampMeters" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="rampMeter" type="RampMeterInventory" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

5.40 Data Frame: IntersectionSummaryStatusUse: A composite data frame developed for AZTech use which combines current status elements of several device types to provide a complete summary of the intersection. Note that this data frame provides current status information about the devices, the IntersectionDeviceSummary data frame provides inventory information about these same devices.

ASN.1 Representation: IntersectionSummaryStatus ::= SEQUENCE { -- information about the primary control device primaryDevice SignalControlInventory, -- reports local time -- and battery state -- Items below added by Azdot to meet local needs -- Current time plan (added by DCK, not in req) currentTimingPlan TimingPlan,

-- Detector status at this Intersection detectors SEQUENCE (SIZE(0..64)) OF DetectorDetails, -- Ramp Meters rates rampMeters SEQUENCE (SIZE(0..64)) OF RampMeterStatus, -- Active special functions of the device specialFuntions SEQUENCE (SIZE(0..8)) OF Special-function, freeText FreeText, ...

XML Representation: <xs:complexType name="IntersectionSummaryStatus" > <xs:sequence> <xs:element name="primaryDevice" type="SignalControlInventory" /> <xs:element name="currentTimingPlan" type="TimingPlan" /> <xs:element name="detectors" >

50


<xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="detector" type="DetectorDetails" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="rampMeters" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="rampMeter" type="RampMeterStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="specialFuntions" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="specialFuntion" type="Special-function" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

5.41 Data Frame: OrganizationInformationLongUse: The long form of the organizational data frame. This is derived from several TMDD data frames and data elements and has been customized to reflect local AzDot needs. The typical use of this frame is when requesting data about a device, or when building a reply with data about a device owned by a center. See also the OrganizationInformationShort entry which has a terse version also derived from the same TMDD data frames and elements. Typically these are used in pairs.

ASN.1 Representation: OrganizationInformationLong ::= SEQUENCE { organization-id Organization-identifier, organization-name Organization-name, organization-sub-name Organization-sub-organization-name OPTIONAL, -- added by DCK, may not be wanted contactDetails ContactDetails, ... }

XML Representation: <xs:complexType name="OrganizationInformationLong" > <xs:sequence> <xs:element name="organization-id" type="Organization-identifier" /> <xs:element name="organization-name" type="Organization-name" /> <xs:element name="organization-sub-name" type="Organization-sub-organization-name" minOccurs="0"/> <xs:element name="contactDetails" type="ContactDetails" /> </xs:sequence></xs:complexType>

5.42 Data Frame: OrganizationInformationShortUse: The short form of the organizational data frame. This is derived from several TMDD data frames and data elements and has been customized to reflect local AzDot needs. The typical use of this frame is when requesting data about a device, or when building a reply with data about a device owned by a center. See also the OrganizationInformationLong entry which has a verbose version also derived from the same TMDD data elements. Typically these are used in pairs.

51


ASN.1 Representation: OrganizationInformationShort ::= SEQUENCE { organization-id Organization-identifier, organization-name Organization-name, ... }

XML Representation: <xs:complexType name="OrganizationInformationShort" > <xs:sequence> <xs:element name="organization-id" type="Organization-identifier" /> <xs:element name="organization-name" type="Organization-name" /> </xs:sequence></xs:complexType>

5.43 Data Frame: OverlapUse: A data frame with binds the overlap number to a description.

ASN.1 Representation: Overlap ::= SEQUENCE { number INTEGER (0..65535), description FreeText, ... }

XML Representation: <xs:complexType name="Overlap" > <xs:sequence> <xs:element name="number" > <xs:simpleType> <xs:restriction base="xs:unsignedShort"/> </xs:simpleType> </xs:element> <xs:element name="description" type="FreeText" /> </xs:sequence></xs:complexType>

5.44 Data Frame: Phase-detailsUse: A sequence of phases and descriptions for this controller.

ASN.1 Representation: Phase-details ::= SEQUENCE (SIZE(1..255)) OF Phase

XML Representation: <xs:complexType name="Phase-details" > <xs:sequence minOccurs="1" maxOccurs="255"> <xs:element name="phase-detail" type="Phase" /> </xs:sequence></xs:complexType>

5.45 Data Frame: PhaseUse: Information about a phases and its descriptions for a controller.

52


ASN.1 Representation: Phase ::= SEQUENCE { phaseNumber PhaseNumber, phase-Signal-State Phase-Signal-State, movment FreeText, splitPhase SplitPhase, splitTime SplitTime, ... }

XML Representation: <xs:complexType name="Phase" > <xs:sequence> <xs:element name="phaseNumber" type="PhaseNumber" /> <xs:element name="phase-Signal-State" type="Phase-Signal-State" /> <xs:element name="movment" type="FreeText" /> <xs:element name="splitPhase" type="SplitPhase" /> <xs:element name="splitTime" type="SplitTime" /> </xs:sequence></xs:complexType>

5.46 Data Frame: RampMeterControlUse: A data frame used to send control information to the ramp meter to be implemented.

ASN.1 Representation: RampMeterControl ::= SEQUENCE { device-id Device-identifier, --3701 meter-status Meter-status, --3533 ramp-current-state Ramp-current-state, --3536 -- node-name Node-name OPTIONAL, -#-3047 -- ramp-meter-control-type RampMeter-control-type OPTIONAL, -#-3535 -- metering-type Meter-metering-type OPTIONAL, -#-3532 -- last-update DateTimeZone, -- operator-last-revised Event-update-operator-last-revised OPTIONAL, -#-3295 -- AZTech added items volume-data Volume-data, -- trigger point data -- requested special functions to be turned ON special-functions-ON SEQUENCE (SIZE(0..8)) OF Special-function, -- requested special functions to be turned OFF special-functions-OFF SEQUENCE (SIZE(0..8)) OF Special-function, freeText FreeText, ... }

XML Representation: <xs:complexType name="RampMeterControl" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="meter-status" type="Meter-status" /> <xs:element name="ramp-current-state" type="Ramp-current-state" /> <xs:element name="volume-data" type="Volume-data" /> <xs:element name="special-functions-ON" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="special-functions-ON-item" type="Special-function" /> </xs:sequence> </xs:complexType>

53


</xs:element> <xs:element name="special-functions-OFF" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="special-functions-OFF-item" type="Special-function" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

5.47 Data Frame: RampMeterInventoryUse: Taken from the TMDD.RampMeterInventory data concept and adjusted t meet AZTech needs.

ASN.1 Representation: RampMeterInventory ::= SEQUENCE { -- organization-information OrganizationInformation, device-id Device-identifier, --3701 -- node-id Device-node-identifier, -#-3750 -- ramp-exit-roadway-name Ramp-exit-roadway-name, -#-3414 link-direction Link-direction, --3008 -- ramp-location LRMS.GeoLocation OPTIONAL, -- route-designator Link-route-designator OPTIONAL, -#-3030 -- linear-reference Link-location-linear-reference OPTIONAL, -#-3855 -- linear-reference-version Link-location-linear-reference-version OPTIONAL, -#-3854 -- simple lat-long added here device-latitude Latitude, device-longitude Longitude, -- node-name Node-name OPTIONAL, -#-3047 -- timing-plan-id TimingPlan-identifier OPTIONAL, -#-3486 ramp-lane-number Ramp-lane-number OPTIONAL, --3418 -- the number of lanes controlled -- ramp-lane-type Ramp-lane-type OPTIONAL, -#-3427 -- firmware Controller-firmware OPTIONAL, -#-3460 -- firmware-version Controller-firmware-release-version OPTIONAL, -#-3461 -- device-url Device-url OPTIONAL, -#-3720 -- last-update DateTimePair, -- contact-details ContactDetails OPTIONAL, ... }

XML Representation: <xs:complexType name="RampMeterInventory" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="link-direction" type="Link-direction" /> <xs:element name="device-latitude" type="Latitude" /> <xs:element name="device-longitude" type="Longitude" /> <xs:element name="ramp-lane-number" type="Ramp-lane-number" minOccurs="0"/> </xs:sequence></xs:complexType>

5.48 Data Frame: RampMeterStatusUse: Defined as a message in TMDD, used as a data frame here. We are only using ONE item from the TMDD here, is this right?

ASN.1 Representation: RampMeterStatus ::= SEQUENCE { -- center-id Organization-center-identifier OPTIONAL, -#-3217 -- operator-id Organization-center-operator-identifier OPTIONAL, -#-3112

54


-- device-id Device-identifier, -#-3701 meter-status Meter-status, --3533 -- ramp-current-state Ramp-current-state, -#-3536 -- node-name Node-name OPTIONAL, -#-3047 -- ramp-meter-control-type RampMeter-control-type OPTIONAL, -#-3535 -- metering-type Meter-metering-type OPTIONAL, -#-3532 -- last-update DateTimeZone, -- operator-last-revised Event-update-operator-last-revised OPTIONAL, -#-3295 -- AZTech added items volume-data Volume-data, -- local defined? ... }

XML Representation: <xs:element name="rampMeterStatus" type="RampMeterStatus"/><xs:complexType name="RampMeterStatus" > <xs:sequence> <xs:element name="meter-status" type="Meter-status" /> <xs:element name="volume-data" type="Volume-data" /> </xs:sequence></xs:complexType>

5.49 Data Frame: Schedule-entryUse: A data frame used to relate the scheduled start and stop times of a timing plan or other type of activity.

ASN.1 Representation: Schedule-entry ::= SEQUENCE { startTime DateTimePair, stopTime DateTimePair, eventID TimingPlan-identifier, ... }XML Representation: <xs:complexType name="Schedule-entry" > <xs:sequence> <xs:element name="startTime" type="DateTimePair" /> <xs:element name="stopTime" type="DateTimePair" /> <xs:element name="eventID" type="TimingPlan-identifier" /> </xs:sequence></xs:complexType>

5.50 Data Frame: SignalControlInventoryUse: Heavily profiled for local use, many of the elements found in the TMDD standard are not needed and have been removed.

ASN.1 Representation: SignalControlInventory ::= SEQUENCE { -- organization-information OrganizationInformation, -- node-id Node-identifier, -#-3042 -- node-name Node-name OPTIONAL, -#-3047 intersection-name Intersection-name OPTIONAL,--3405 -- network-id Network-identifier OPTIONAL, -#-3411 device-id Device-identifier, --3701 -- device-location LRMS.GeoLocation OPTIONAL, -- just lat-long is used device-latitude Latitude, device-longitude Longitude,

55


-- route-designator Link-route-designator OPTIONAL, -#-3030 -- linear-reference Link-location-linear-reference OPTIONAL, -#-3855 -- linear-reference-version Link-location-linear-reference-version OPTIONAL, -#-3854 -- device-type Device-type OPTIONAL, -#-3747 -- controller-model Controller-model OPTIONAL, -#-3464 -- controller-serial-number Controller-serial-number OPTIONAL, -#-3467 -- firmware Controller-firmware OPTIONAL, -#-3460 -- firmware-version Controller-firmware-release-version OPTIONAL, -#-3461 -- controller-master-id Controller-master-identifier OPTIONAL, -#-3463 -- timingplan-id TimingPlan-identifier OPTIONAL, -#-3486 -- timingplan-name TimingPlan-name OPTIONAL, -#-3487 -- cycle-time NTCIP.PatternCycleTime OPTIONAL, -#-3938 -- offset-time NTCIP.PatternOffsetTime OPTIONAL, -#-3940 -- sequence-number NTCIP.PatternSequenceNumber OPTIONAL, -#-3941 -- split-number NTCIP.PatternSplitNumber OPTIONAL, -#-3942 -- intersection-approaches SEQUENCE (SIZE(1..10)) OF Link-identifier OPTIONAL, -#-3012 -- last-update-time DateTimePair, -- contact-details ContactDetails OPTIONAL -- added by AZTech for deployment needs section-identifier Section-identifier OPTIONAL, --3421 zone-identifier Section-identifier OPTIONAL, --3421 controller-Time DateTimePair, -- current time at controller central-Time DateTimePair, -- current time at central current-UTC-Time DateTimePair, -- current Coordinated Universal Time (UTC) battPercent INTEGER (0..100), -- battery backup status special-functions SEQUENCE (SIZE(0..8)) OF Special-function, controller-log-entries SEQUENCE (SIZE(0..64)) OF Controller-log-entry, ... }

XML Representation: <xs:complexType name="SignalControlInventory" > <xs:sequence> <xs:element name="intersection-name" type="Intersection-name" minOccurs="0"/> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="device-latitude" type="Latitude" /> <xs:element name="device-longitude" type="Longitude" /> <xs:element name="section-identifier" type="Section-identifier" minOccurs="0"/> <xs:element name="zone-identifier" type="Section-identifier" minOccurs="0"/> <xs:element name="controller-Time" type="DateTimePair" /> <xs:element name="central-Time" type="DateTimePair" /> <xs:element name="current-UTC-Time" type="DateTimePair" /> <xs:element name="battPercent" > <xs:simpleType> <xs:restriction base="xs:unsignedByte"> <xs:maxInclusive value="100"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="special-functions" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="special-function" type="Special-function" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="controller-log-entries" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="controller-log-entry" type="Controller-log-entry" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence></xs:complexType>

56


5.51 Data Frame: Special-functionUse: A data frame used to document the assigned value and use of any special function bits within a controller.

ASN.1 Representation: Special-function ::= SEQUENCE { function-output-number INTEGER (1..8), function-meaning SpecialFunctionList, ... }

XML Representation: <xs:complexType name="Special-function" > <xs:sequence> <xs:element name="function-output-number" > <xs:simpleType> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/> <xs:maxInclusive value="8"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="function-meaning" type="SpecialFunctionList" /> </xs:sequence></xs:complexType>

5.52 Data Frame: SubscriptionActionUse: A set of SubscriptionActionItem entries.

ASN.1 Representation: SubscriptionAction ::= SEQUENCE (SIZE(1..10)) OF SubscriptionActionItemXML Representation: <xs:complexType name="SubscriptionAction" > <xs:sequence minOccurs="1" maxOccurs="10"> <xs:element name="subscriptionAction-item" type="SubscriptionActionItem" /> </xs:sequence></xs:complexType> In addition, this item may be used by data structures in other ITS standards.

5.53 Data Frame: SubscriptionTypeUse: A collection of SubscriptionTypeItems.

ASN.1 Representation: SubscriptionType ::= SEQUENCE (SIZE(1..10)) OF SubscriptionTypeItem

XML Representation: <xs:complexType name="SubscriptionType" > <xs:sequence minOccurs="1" maxOccurs="10"> <xs:element name="subscriptionType-item" type="SubscriptionTypeItem" /> </xs:sequence></xs:complexType>

57


5.54 Data Frame: TimingPlanUse: Listed as a message in TMDD, but used as a data frame here. Here used to relate the timing plans associated with an intersection. In TMDD this data frame is called IntersectionDeviceStatus, here we have renamed is CurrentTimingPlan to better represent its use.

ASN.1 Representation: TimingPlan ::= SEQUENCE { device-id Device-identifier, --3701 intersection-name Intersection-name OPTIONAL, --3405 -- section-id Section-identifier OPTIONAL, -#-3421 -- controller-state Controller-response-state, -#-3465 -- controller-mode Intersection-signal-control-mode, -#-3472 -- center-id Organization-center-identifier OPTIONAL, -#-3217 -- operator-id Device-organization-operator-identifier, -#-3706 timing-plan-id TimingPlan-identifier OPTIONAL, --3486 timing-plan-name TimingPlan-name OPTIONAL, --3487 cycle-time PatternCycleTime OPTIONAL, --3938 offset-time PatternOffsetTime OPTIONAL, --3940 -- preempt-name Preempt-name OPTIONAL, -#-3483 -- controller-sync-time Controller-sync-time OPTIONAL, -#-3772 -- last-update-time DateTimeZone OPTIONAL, -- operator-last-revised Event-update-operator-last-revised OPTIONAL -#-3295 ... }

XML Representation: <xs:complexType name="TimingPlan" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="intersection-name" type="Intersection-name" minOccurs="0"/> <xs:element name="timing-plan-id" type="TimingPlan-identifier" minOccurs="0"/> <xs:element name="timing-plan-name" type="TimingPlan-name" minOccurs="0"/> <xs:element name="cycle-time" type="PatternCycleTime" minOccurs="0"/> <xs:element name="offset-time" type="PatternOffsetTime" minOccurs="0"/> </xs:sequence></xs:complexType>

5.55 Data Element: BroadcastAlertsItemUse: An enumerated list of items.

ASN.1 Representation: BroadcastAlertsItem ::= ENUMERATED { reserved (0), broadcastAlertsAccepted (1), broadcastAlertsNotAccepted (2), ... }

XML Representation: <xs:simpleType name="BroadcastAlertsItem" > <xs:annotation> <xs:appinfo> reserved (0) broadcastAlertsAccepted (1) broadcastAlertsNotAccepted (2) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType>

58


<xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="2"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="reserved"/> <xs:enumeration value="broadcastAlertsAccepted"/> <xs:enumeration value="broadcastAlertsNotAccepted"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.56 Data Element: CONTACT_EmailAddress_textUse: The e-mail address of a person at an organizatin to contact regarding a roadway event.

ASN.1 Representation: Contact-email-address ::= IA5String (SIZE(1..128)) -- Any set of ASCII characters up to 128

XML Representation: <xs:simpleType name="Contact-email-address" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.57 Data Element: CONTACT_Identifier_identifierUse: A uniques identifier for a contact person as assigned by the organization.

ASN.1 Representation: Contact-identifier ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="Contact-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.58 Data Element: CONTACT_PersonName_textUse: The name or identifier of a person at an organization.

ASN.1 Representation: Contact-person-name ::= IA5String (SIZE(1..64)) -- Any set of alphanumeric characters up to 64

XML Representation: <xs:simpleType name="Contact-person-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="64"/>

59


</xs:restriction></xs:simpleType>

5.59 Data Element: CONTACT_PersonTitle_textUse: The title of a person at an organization.

ASN.1 Representation: Contact-person-title ::= IA5String (SIZE(1..64)) -- Any set of alphanumeric characters up to 64

XML Representation: <xs:simpleType name="Contact-person-title" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="64"/> </xs:restriction></xs:simpleType>

5.60 Data Element: CONTACT_PhoneAlternate_textUse: An alternate phone number (e.g., home phone number) of a person at an organization.

ASN.1 Representation: Contact-phone-alternate ::= IA5String (SIZE(1..32)) -- Any set of ASCII characters up to 32

XML Representation: <xs:simpleType name="Contact-phone-alternate" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.61 Data Element: CONTACT_PhoneNumber_textUse: The telephone number of a person at an organization.

ASN.1 Representation: Contact-phone-number ::= IA5String (SIZE(1..32)) -- Any set of ASCII characters up to 32. The '-' and '.' characters shall be valid delimiters.

XML Representation: <xs:simpleType name="Contact-phone-number" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.62 Data Element: DETECTOR_Identifier_identifierUse: Unique identification number of an individual detector within a network.

60


ASN.1 Representation: Detector-identifier ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="Detector-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.63 Data Element: DETECTOR_IntersectionApproachName_textUse: String name or description of the intersection approach being monitored by the detector (e.g., NB Left Turn).

ASN.1 Representation: Detector-intersection-approach-name ::= IA5String (SIZE(1..128)) -- Any set of ASCII characters up to 128

XML Representation: <xs:simpleType name="Detector-intersection-approach-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.64 Data Element: DETECTOR_LaneNumber_codeUse: The number which indicates the lane a particular detector is monitoring

ASN.1 Representation: Detector-lane-number ::= BIT STRING (SIZE(1..255)) -- Select one bit per lane. Lanes are numbered from the median out beginning with 1.

XML Representation: <xs:simpleType name="Detector-lane-number" > <xs:restriction base="binary"> <xs:minLength value="1"/> <xs:maxLength value="255"/> </xs:restriction></xs:simpleType>

5.65 Data Element: DETECTOR_Type_codeUse: Code naming the type of a vehicular detector providing traffic data.

ASN.1 Representation: Detector-type ::= ENUMERATED { inductive-loop (1), magnetic (2), magnetometers (3), pressure-cells (4), microwave-radar (5),

61


ultrasonic (6), video-Image (7), laser (8), infrared (9), road-tube (10), ... }

XML Representation: <xs:simpleType name="Detector-type" > <xs:annotation> <xs:appinfo> inductive loop (1) magnetic (2) magnetometers (3) pressure cells (4) microwave radar (5) ultrasonic (6) video Image (7) laser (8) infrared (9) road tube (10) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="10"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="inductive loop"/> <xs:enumeration value="magnetic"/> <xs:enumeration value="magnetometers"/> <xs:enumeration value="pressure cells"/> <xs:enumeration value="microwave radar"/> <xs:enumeration value="ultrasonic"/> <xs:enumeration value="video Image"/> <xs:enumeration value="laser"/> <xs:enumeration value="infrared"/> <xs:enumeration value="road tube"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.66 Data Element: DEVICE_AcknowledgeControl_codeUse: Acknowledgement of request command from one TMC to another for device action.

ASN.1 Representation: Device-acknowledge-control ::= ENUMERATED { control-acknowledged (0), device-available (1), requested-changes-completed (2), control-rejected (3), device-in-use (4), device-off-line (5), request-cancelled (6), request-rejected-invalid-command-parameters (7), request-rejected-insufficient-privileges-of-the-requesting-operator (8), request-queued (9), ... }

62


XML Representation: <xs:simpleType name="Device-acknowledge-control" > <xs:annotation> <xs:appinfo> control acknowledged (0) device available (1) requested changes completed (2) control rejected (3) device in use (4) device off line (5) request cancelled (6) request rejected invalid command parameters (7) request rejected insufficient privileges of the requesting operator (8) request queued (9) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="9"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="control acknowledged"/> <xs:enumeration value="device available"/> <xs:enumeration value="requested changes completed"/> <xs:enumeration value="control rejected"/> <xs:enumeration value="device in use"/> <xs:enumeration value="device off line"/> <xs:enumeration value="request cancelled"/> <xs:enumeration value="request rejected invalid command parameters"/> <xs:enumeration value="request rejected insufficient privileges of the requesting operator"/> <xs:enumeration value="request queued"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.67 Data Element: DEVICE_CommandEndTime_utcUse: Expiration time of the command requested for the device control

ASN.1 Representation: Device-command-end-time ::= INTEGER -- represented as HHMMSS where HH is the hour of the day in 24-hour clock form (with legal values between 00 and 23); "MM" is the minute of hour (with legal values from 00 to 59); "SS" is the second of the minute (with legal values from 00 to 59).

XML Representation: <xs:simpleType name="Device-command-end-time" > <xs:restriction base="xs:int"/></xs:simpleType>

5.68 Data Element: DEVICE_CommandRequestPriority_numberUse: A code to indicate universal concept of priority for all command requests. If the request is accepted and the action is posted, then the current state has that priority.

63


ASN.1 Representation: Device-command-request-priority ::= INTEGER (1..10) -- Select from 1 to 10 where 1 is the highest and 10 is the lowest priority

XML Representation: <xs:simpleType name="Device-command-request-priority" > <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/> <xs:maxInclusive value="10"/> </xs:restriction></xs:simpleType>

5.69 Data Element: DEVICE_Identifier_identifierUse: A unique alphanumeric device identifier.

ASN.1 Representation: Device-identifier ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="Device-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.70 Data Element: DEVICE_OperationalStatus_codeUse: Operational status of a device (e.g., on, off, etc.).

ASN.1 Representation: Device-operational-status ::= ENUMERATED { on (1), off (2), in-service (3), out-of-service (4), unavailable (5), unknown (6), ... }

XML Representation: <xs:simpleType name="Device-operational-status" > <xs:annotation> <xs:appinfo> on (1) off (2) in service (3) out of service (4) unavailable (5) unknown (6) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt">

64


<xs:minInclusive value="1"/> <xs:maxInclusive value="6"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="on"/> <xs:enumeration value="off"/> <xs:enumeration value="in service"/> <xs:enumeration value="out of service"/> <xs:enumeration value="unavailable"/> <xs:enumeration value="unknown"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.71 Data Element: DEVICE_RequestIdentifier_identifierUse: A unique sequence number generated by the requesting center that uniquely identifies the control request within the requesting center.

ASN.1 Representation: Device-request-identifier ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="Device-request-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.72 Data Element: DEVICE_Type_codeUse: A code which specifies the type of device.

ASN.1 Representation: Device-type ::= ENUMERATED { detector (1), cctv-camera (2), dynamic-message-sign (3), environmental-sensor-station (4), gate (5), highway-advisory-radio (6), lane-control-signal (7), ramp-meter (8), signal-controller (9), signal-section (10), ... }

XML Representation: <xs:simpleType name="Device-type" > <xs:annotation> <xs:appinfo> detector (1) cctv camera (2) dynamic message sign (3) environmental sensor station (4)

65


gate (5) highway advisory radio (6) lane control signal (7) ramp meter (8) signal controller (9) signal section (10) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="10"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="detector"/> <xs:enumeration value="cctv camera"/> <xs:enumeration value="dynamic message sign"/> <xs:enumeration value="environmental sensor station"/> <xs:enumeration value="gate"/> <xs:enumeration value="highway advisory radio"/> <xs:enumeration value="lane control signal"/> <xs:enumeration value="ramp meter"/> <xs:enumeration value="signal controller"/> <xs:enumeration value="signal section"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.73 Data Element: EXT_ATIS_DateUse: Date for which a directory entry, or other use, is being requested by a Traveler or used in a returned message. The precise time at which this date starts may vary with the time zone of the service. For example: Saturday stay over rates for an airline begin at the point of departure.

ASN.1 Representation: Date ::= IA5String (SIZE(8)) -- format as: YYYYMMDD where -- YYYY the year, in common era units -- MM the month, range 01 to 12 -- DD the day, range 01 to 31 -- use zero for MM and DD when not applicable -- The entry: xs:date is used for XML

XML Representation: <xs:simpleType name="Date"> <xs:restriction base="xs:date"/></xs:simpleType>

5.74 Data Element: EXT_ATIS_TimeUse: Time for which a directory entry is being requested by a Traveler or used in a returned message.

ASN.1 Representation: Time ::= IA5String (SIZE(6..10)) -- Format: HHMMSSssss -- Valid times using 24 hour notation. -- HH=00 through 23; MM=00 through 59; -- SS=00 through 59; 00 if NA -- ssss=0000 through 9999.

66


-- Use SS= 60 for leap seconds -- HH represents hours, MM minutes, SS seconds, -- and ssss decimal seconds to whatever number -- of significant digits is required (up to four) -- The entry: xs:time is used for XML

XML Representation: <xs:simpleType name="Time"> <xs:restriction base="xs:time"/></xs:simpleType>

5.75 Data Element: EXT_DmsMessageBeaconUse: Indicates if connected beacon(s) are to be activated when the associated message is displayed.

ASN.1 Representation: DmsMessageBeacon ::= ENUMERATED { beacons-are-disabled (0), beacons-are-enabled (1), ... }

XML Representation: <xs:simpleType name="DmsMessageBeacon" > <xs:annotation> <xs:appinfo> beacons are disabled (0) beacons are enabled (1) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="1"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="beacons are disabled"/> <xs:enumeration value="beacons are enabled"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.76 Data Element: EXT_DmsMessageMultiStringUse: Contains the message written in MULTI-language. The value of the MULTI string is not allowed to have any null character.

ASN.1 Representation: DmsMessageMultiString ::= OCTET STRING (SIZE(1..256)) -- Any set of ASCII characters up to 256

XML Representation: <xs:complexType name="DmsMessageMultiString" > <xs:simpleContent> <xs:extension base="DmsMessageMultiString-string" > <xs:attribute name="EncodingType" use="required">

67


<xs:simpleType> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="base64Binary"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:extension> </xs:simpleContent></xs:complexType><xs:simpleType name="DmsMessageMultiString-string"> <xs:restriction base="xs:base64Binary"> <xs:minLength value="2"/> <xs:maxLength value="342"/> </xs:restriction></xs:simpleType >

5.77 Data Element: EXT_DmsMessageNumberUse: Enumerated listing of row entries within the value of the primary index to this table (dmsMessageMemoryType -object). When the primary index is 'currentBuffer' or 'schedule', then this value must be one (1). When the primary index is 'blank', this value shall be from 1 through 255 and all compliant devices must support all 255 of these 'blank' rows.

ASN.1 Representation: DmsMessageNumber ::= INTEGER (0..65535)

XML Representation: <xs:simpleType name="DmsMessageNumber" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType>

5.78 Data Element: EXT_DmsMessageTimeRemainingUse: Indicates the amount of remaining time in minutes that the current message shall be displayed. The value 65535 indicates an infinite duration. A value of zero (0) shall indicate that the current message display duration has expired.

ASN.1 Representation: DmsMessageTimeRemaining ::= INTEGER (0..65535)

XML Representation: <xs:simpleType name="DmsMessageTimeRemaining" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType>

5.79 Data Element: EXT_DmsSignTechnologyUse: Indicates the utilized technology in a bitmap format (Hybrids will have to set the bits for all technologies that the sign utilizes). If a bit is set to one (1), then the associated feature exists.; if the bit is set to zero (0), then the associated feature does not exist.

ASN.1 Representation: DmsSignTechnology ::= BIT STRING { other (0), led (1),

68


flip-disk (2), fiber-optics (3), shuttered (4), bulb (5), drum (6), spare7 (7) -- Adding to make a full byte }

XML Representation: <xs:simpleType name="DmsSignTechnology-item" > <xs:annotation> <xs:appinfo> other (0) led (1) flip disk (2) fiber optics (3) shuttered (4) bulb (5) drum (6) spare7 (7) -- Adding to make a full byte </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="0"/> <xs:maxInclusive value="7"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="other"/> <xs:enumeration value="led"/> <xs:enumeration value="flip disk"/> <xs:enumeration value="fiber optics"/> <xs:enumeration value="shuttered"/> <xs:enumeration value="bulb"/> <xs:enumeration value="drum"/> <xs:enumeration value="spare7"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType><xs:simpleType name="DmsSignTechnology"> <xs:list itemType="DmsSignTechnology-item"/></xs:simpleType>

5.80 Data Element: EXT_EssAirTemperatureUse: The dry-bulb temperature in tenths of degrees Celsius. The temperature is an instantaneous reading at the height specified by essTemperatureSensorHeight. The value 1001 shall indicate an error condition or missing value.

ASN.1 Representation: EssAirTemperature ::= INTEGER (-1000..1001)

XML Representation: <xs:simpleType name="EssAirTemperature" > <xs:restriction base="xs:short"> <xs:minInclusive value="-1000"/> <xs:maxInclusive value="1001"/> </xs:restriction></xs:simpleType>

69


5.81 Data Element: EXT_EssAvgWindDirectionUse: A two minute average of the direction from which the wind is blowing measured clockwise in degrees from true North and measured at a height as indicated by essWindSensorHeight. A value of 361 shall indicate an error condition or missing value.

ASN.1 Representation: EssAvgWindDirection ::= INTEGER (0..361)

XML Representation: <xs:simpleType name="EssAvgWindDirection" > <xs:restriction base="xs:unsignedShort"> <xs:maxInclusive value="361"/> </xs:restriction></xs:simpleType>

5.82 Data Element: EXT_EssAvgWindSpeedUse: A two minute average of the wind speed in tenths of meters per second measured at a height as indicated by essWindSensorHeight. A value of 65535 shall indicate an error condition or missing value

ASN.1 Representation: EssAvgWindSpeed ::= INTEGER (0..65535)XML Representation: <xs:simpleType name="EssAvgWindSpeed" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType>

5.83 Data Element: EXT_EssPrecipYesNoUse: Indicates whether or not moisture is detected by the sensor.

ASN.1 Representation: EssPrecipYesNo ::= ENUMERATED { precip (1), no-precip (2), error (3), ... }

XML Representation: <xs:simpleType name="EssPrecipYesNo" > <xs:annotation> <xs:appinfo> precip (1) no precip (2) error (3) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string">

70


<xs:enumeration value="precip"/> <xs:enumeration value="no precip"/> <xs:enumeration value="error"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.84 Data Element: EXT_EssSolarRadiationUse: The direct solar radiation integrated over the 24 hours preceding the observation in Joules per square meter. A value of 65535 shall indicate a missing value.

ASN.1 Representation: EssSolarRadiation ::= INTEGER (0..65535)

XML Representation: <xs:simpleType name="EssSolarRadiation" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType>

5.85 Data Element: EXT_EssVisibilityUse: Surface visibility measured in one tenth of a meter. The value 1000001 shall indicate an error condition or missing value."

ASN.1 Representation: EssVisibility ::= INTEGER (0..1000001)XML Representation: <xs:simpleType name="EssVisibility" > <xs:restriction base="xs:unsignedInt"> <xs:maxInclusive value="1000001"/> </xs:restriction></xs:simpleType>

5.86 Data Element: EXT_EssWindSituationUse: Describes the weather and travel situation in terms of wind from staffed stations only.

ASN.1 Representation: EssWindSituation ::= ENUMERATED { other (1), unknown (2), calm (3), light-breeze (4), moderate-breeze (5), strong-breeze (6), gale (7), moderate-gale (8), strong-gale (9), storm-winds (10), hurricane-force-winds (11), gusty-winds (12), ... }

71


XML Representation: <xs:simpleType name="EssWindSituation" > <xs:annotation> <xs:appinfo> other (1) unknown (2) calm (3) light breeze (4) moderate breeze (5) strong breeze (6) gale (7) moderate gale (8) strong gale (9) storm winds (10) hurricane force winds (11) gusty winds (12) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="12"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="other"/> <xs:enumeration value="unknown"/> <xs:enumeration value="calm"/> <xs:enumeration value="light breeze"/> <xs:enumeration value="moderate breeze"/> <xs:enumeration value="strong breeze"/> <xs:enumeration value="gale"/> <xs:enumeration value="moderate gale"/> <xs:enumeration value="strong gale"/> <xs:enumeration value="storm winds"/> <xs:enumeration value="hurricane force winds"/> <xs:enumeration value="gusty winds"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.87 Data Element: EXT_LRMS_HorizontalDatumUse: The underlying horizontal geodetic datum for a geographic coordinate

ASN.1 Representation: HorizontalDatum ::= ENUMERATED { wgs-84 (0), wgs-84egm-96 (1), nad83 (2), nad27 (3), ... }

XML Representation: <xs:simpleType name="HorizontalDatum" > <xs:annotation> <xs:appinfo> wgs 84 (0) wgs 84egm 96 (1) nad83 (2)

72


nad27 (3) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="wgs 84"/> <xs:enumeration value="wgs 84egm 96"/> <xs:enumeration value="nad83"/> <xs:enumeration value="nad27"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.88 Data Element: EXT_LRMS_LatitudeUse: The geographic latitude of a node, expressed in integer microdegrees, with reference to the horizontal datum specified by horizontalDatum.

ASN.1 Representation: Latitude ::= INTEGER (-90000000..90000000) -- microdegrees

XML Representation: <xs:simpleType name="Latitude" > <xs:restriction base="xs:int"> <xs:minInclusive value="-90000000"/> <xs:maxInclusive value="90000000"/> </xs:restriction></xs:simpleType>

5.89 Data Element: EXT_LRMS_LongitudeUse: The geographic longitude of a node, expressed in integer microdegrees, with reference to the horizontal datum specified by horizontalDatum.

ASN.1 Representation: Longitude ::= INTEGER (-180000000..180000000) -- microdegrees

XML Representation: <xs:simpleType name="Longitude" > <xs:restriction base="xs:int"> <xs:minInclusive value="-180000000"/> <xs:maxInclusive value="180000000"/> </xs:restriction></xs:simpleType>

5.90 Data Element: EXT_LRMS_VerticalDatumUse: The underlying vertical geodetic datum for a geographic coordinate.

73


ASN.1 Representation: VerticalDatum ::= ENUMERATED { wgs-84 (0), navd (1), ... }

XML Representation: <xs:simpleType name="VerticalDatum" > <xs:annotation> <xs:appinfo> wgs 84 (0) navd (1) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="1"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="wgs 84"/> <xs:enumeration value="navd"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.91 Data Element: EXT_LRMS_VerticalLevelUse: Vertical level specified as ordinal class expressed positive (above) or negative (below) the ground surface or ground level of a structure (VerticalLevel = 0).

ASN.1 Representation: VerticalLevel ::= INTEGER (-127..127)

XML Representation: <xs:simpleType name="VerticalLevel" > <xs:restriction base="xs:byte"> <xs:minInclusive value="-127"/> </xs:restriction></xs:simpleType>

5.92 Data Element: EXT_PatternCycleTimeUse: Specifies the length of the pattern cycel [Ed: (sic) cycle] in seconds.

ASN.1 Representation: PatternCycleTime ::= INTEGER (0..255)

XML Representation: <xs:simpleType name="PatternCycleTime" > <xs:restriction base="xs:unsignedByte"/></xs:simpleType>

74


5.93 Data Element: EXT_PatternOffsetTimeUse: The PatternOffsetTime defines by how many seconds the local time zero shall lag the system time zero (synchronization pulse) for this pattern.

ASN.1 Representation: PatternOffsetTime ::= INTEGER (0..255)XML Representation: <xs:simpleType name="PatternOffsetTime" > <xs:restriction base="xs:unsignedByte"/></xs:simpleType>

5.94 Data Element: FreeTextUse: A simple free-text field used in the message when structured information will not serve.

ASN.1 Representation: FreeText ::= UTF8String (SIZE(1..500))

XML Representation: <xs:simpleType name="FreeText" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="500"/> </xs:restriction></xs:simpleType>

5.95 Data Element: InformationalTextUse: Any set of ASCII characters up to 255.

ASN.1 Representation: InformationalText ::= IA5String (SIZE(1..255))

XML Representation: <xs:simpleType name="InformationalText" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="255"/> </xs:restriction></xs:simpleType>

5.96 Data Element: INTERSECTION_Name_textUse: The user-defined name of the intersection.

ASN.1 Representation: Intersection-name ::= IA5String (SIZE(1..128)) -- Any set of ASCII characters up to 128

XML Representation: <xs:simpleType name="Intersection-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/>

75


<xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.97 Data Element: LINK_Direction_codeUse: The direction(s) of travel referenced on a link.

ASN.1 Representation: Link-direction ::= ENUMERATED { any-other (0), n (1), ne (2), e (3), se (4), s (5), sw (6), w (7), nw (8), not-directional (9), positive-direction (10), negative-direction (11), both-directions (12), ... }

XML Representation: <xs:simpleType name="Link-direction" > <xs:annotation> <xs:appinfo> any other (0) n (1) ne (2) e (3) se (4) s (5) sw (6) w (7) nw (8) not directional (9) positive direction (10) negative direction (11) both directions (12) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="12"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="any other"/> <xs:enumeration value="n"/> <xs:enumeration value="ne"/> <xs:enumeration value="e"/> <xs:enumeration value="se"/> <xs:enumeration value="s"/> <xs:enumeration value="sw"/> <xs:enumeration value="w"/> <xs:enumeration value="nw"/> <xs:enumeration value="not directional"/> <xs:enumeration value="positive direction"/> <xs:enumeration value="negative direction"/>

76


<xs:enumeration value="both directions"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.98 Data Element: LINK_RouteDesignator_identifierUse: County, State, or Federal route numbers with any associated alphabetic designators.

ASN.1 Representation: Link-route-designator ::= IA5String (SIZE(1..64)) -- Any set of alphanumeric characters up to 64

XML Representation: <xs:simpleType name="Link-route-designator" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="64"/> </xs:restriction></xs:simpleType>

5.99 Data Element: MaxOverlapsUse: The maximum number of overlaps in a sequence. NOTE: Need further help defining this element and is proper use.

ASN.1 Representation: MaxOverlaps ::= INTEGER (0..100) -- edit to proper ranges

XML Representation: <xs:simpleType name="MaxOverlaps" > <xs:restriction base="xs:unsignedByte"> <xs:maxInclusive value="100"/> </xs:restriction></xs:simpleType>

5.100Data Element: MaxPhasesUse: From NTCIP, The Maximum Number of Phases this Actuated Controller Unit supports. This object indicates the maximum rows which shall appear in the phaseTable object in a MIB.

ASN.1 Representation: MaxPhases ::= INTEGER (0..255)

XML Representation: <xs:simpleType name="MaxPhases" > <xs:restriction base="xs:unsignedByte"/></xs:simpleType>

5.101Data Element: METER_Status_codeUse: Status of the ramp, mainline, freeway-to-freeway connector, or tunnel metering signal.

77


ASN.1 Representation: Meter-status ::= ENUMERATED { off (0), green (1), red (2), yellow (3), flashing (4), ... }

XML Representation: <xs:simpleType name="Meter-status" > <xs:annotation> <xs:appinfo> off (0) green (1) red (2) yellow (3) flashing (4) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="4"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="off"/> <xs:enumeration value="green"/> <xs:enumeration value="red"/> <xs:enumeration value="yellow"/> <xs:enumeration value="flashing"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.102Data Element: ORGANIZATION_CenterIdentifier_identifierUse: A unique identification number which identifies an organization's Center (transportation, emergency management, public safety, etc.) within a region.

ASN.1 Representation: Organization-center-identifier ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="Organization-center-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.103Data Element: ORGANIZATION_Identifier_identifierUse: A unique identifier for an organization within a region.

78


ASN.1 Representation: Organization-identifier ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="Organization-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.104Data Element: ORGANIZATION_Name_textUse: The organization's name.

ASN.1 Representation: Organization-name ::= IA5String (SIZE(1..128)) -- Any set of ASCII characters up to 128XML Representation: <xs:simpleType name="Organization-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.105Data Element: ORGANIZATION_SubOrganizationName_textUse: The organization's "sub organization" - Department or Bureau, for example - name.

ASN.1 Representation: Organization-sub-organization-name ::= IA5String (SIZE(1..128)) -- Any set of ASCII characters up to 128

XML Representation: <xs:simpleType name="Organization-sub-organization-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.106Data Element: PhaseNumberUse: The phase number for objects in this row. This value shall not exceed the maxPhases object value.

ASN.1 Representation: PhaseNumber ::= INTEGER (1..255)

XML Representation: <xs:simpleType name="PhaseNumber" > <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/> </xs:restriction>

79


</xs:simpleType>

5.107Data Element: Phase-Signal-StateUse: The Current status of the intersection signal. The condition will show which phases are indicating green and which are showing red.

ASN.1 Representation: Phase-Signal-State ::= ENUMERATED { green (0), red (1), yellow (2), flashing-red (3), flashing-yellow (4), off (5), ... }

XML Representation: <xs:simpleType name="Phase-Signal-State" > <xs:annotation> <xs:appinfo> green (0) red (1) yellow (2) flashing red (3) flashing yellow (4) off (5) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="5"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="green"/> <xs:enumeration value="red"/> <xs:enumeration value="yellow"/> <xs:enumeration value="flashing red"/> <xs:enumeration value="flashing yellow"/> <xs:enumeration value="off"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.108Data Element: RAMP_CurrentState_codeUse: Current status of the ramp.

ASN.1 Representation: Ramp-current-state ::= ENUMERATED { open (1), closed (2), ... }

80


XML Representation: <xs:simpleType name="Ramp-current-state" > <xs:annotation> <xs:appinfo> open (1) closed (2) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="2"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="open"/> <xs:enumeration value="closed"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.109Data Element: RAMP_ExitRoadwayName_textUse: Name of the roadway which the exit ramp intersects.

ASN.1 Representation: Ramp-exit-roadway-name ::= IA5String (SIZE(1..128)) -- Any set of ASCII characters up to 128

XML Representation: <xs:simpleType name="Ramp-exit-roadway-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.110Data Element: RAMP_LaneNumber_quantityUse: The number of lanes at ramp meter. This data element is used to calculate the capacity of the metered ramps.

ASN.1 Representation: Ramp-lane-number ::= INTEGER (1..50) -- lanes

XML Representation: <xs:simpleType name="Ramp-lane-number" > <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/> <xs:maxInclusive value="50"/> </xs:restriction></xs:simpleType>

81


5.111Data Element: ReturnAddressUse: A URL indicating the subscriber callback message handler. Any set of ASCII characters up to 128.

ASN.1 Representation: ReturnAddress ::= IA5String (SIZE(1..128))

XML Representation: <xs:simpleType name="ReturnAddress" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.112Data Element: SECTION_Identifier_identifierUse: Unique identifier for the section using a common timing plan.

ASN.1 Representation: Section-identifier ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="Section-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.113Data Element: SECURITY_Password_textUse: The unique password of a user to login.

ASN.1 Representation: Security-password ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32XML Representation: <xs:simpleType name="Security-password" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.114Data Element: SECURITY_UserName_textUse: The unique User name used to login to the system.

ASN.1 Representation: Security-user-name ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="Security-user-name" >

82


<xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.115Data Element: SpecialFunctionListUse: A enumeration of all the different special function assignmet used in the system. These phrases are then assigned to the specific bit used for that function in each controller.

ASN.1 Representation: SpecialFunctionList ::= ENUMERATED { itemOne (0), itemTwo (1), -- add any comments here itemThree (2), itemFour (3), ... } -- AZTech to assign these valus for strings

XML Representation: <xs:simpleType name="SpecialFunctionList" > <xs:annotation> <xs:appinfo> itemOne (0) itemTwo (1) -- add any comments here itemThree (2) itemFour (3) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="itemOne"/> <xs:enumeration value="itemTwo"/> <xs:enumeration value="itemThree"/> <xs:enumeration value="itemFour"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.116Data Element: SplitPhaseUse: The phase number for objects in this row. The value of this object shall not exceed the maxPhases object value.

ASN.1 Representation: SplitPhase ::= INTEGER (1..255)

XML Representation: <xs:simpleType name="SplitPhase" > <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/>

83


</xs:restriction></xs:simpleType> In addition, this item may be used by data structures in other ITS standards.

5.117Data Element: SplitTimeUse: The time in seconds the splitPhase is allowed to receive (i.e. before a Force Off is applied) when constant demands exist on all phases. In floating coordForceMode, this is always the maximum time a non-coordinated phase is allowed to receive. In fixed coordForceMode, the actual allowed time may be longer if a previous phase gapped out. The splitTime includes all phase clearance times for the associated phase. The split time shall be longer than the sum of the phase minimum service requirements for the phase. When the time is NOT adequate to service the minimum service requirements of the phase, Free Mode shall be the result. The minimum requirements of a phase with a not-actuated ped include Minimum Green, Walk, Pedestrian Clear, Yellow Clearance, and Red Clearance; the minimum requirements of a phase with an actuated pedestrian include Minimum Green, Yellow Clearance, and Red Clearance. If the cycleTime entry of the associated patternTable entry is zero (i.e. the device is in Free Mode), then the value of this object shall be applied, if non-zero, as a maximum time for the associated phase. If the critical path through the phase diagram is less than the cycleTime entry of the associated patternTable entry, all extra time is alloted to the coordination phase in each ring. If the critical path through the phase diagram is greater than the cycleTime entry of the associated patternTable entry (and the cycleTime is not zero) the device shall operate in the Free Mode. While the Free Mode condition exists, the Local Override bit of shortAlarm shall be set to one (1). Taken from NTCIP.

ASN.1 Representation: SplitTime ::= INTEGER (0..255) -- units of seconds

XML Representation: <xs:simpleType name="SplitTime" > <xs:restriction base="xs:unsignedByte"/></xs:simpleType>

5.118Data Element: SubscriptionActionItemUse: An ENUMERATED list of the subscription actions that a request message may take.

ASN.1 Representation: SubscriptionActionItem ::= ENUMERATED { reserved (0), newSubscription (1), replaceSubscription (2), cancelSubscription (3), cancelAllPriorSubscriptions (4), ... }

XML Representation: <xs:simpleType name="SubscriptionActionItem" > <xs:annotation> <xs:appinfo> reserved (0) newSubscription (1) replaceSubscription (2)

84


cancelSubscription (3) cancelAllPriorSubscriptions (4) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="4"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="reserved"/> <xs:enumeration value="newSubscription"/> <xs:enumeration value="replaceSubscription"/> <xs:enumeration value="cancelSubscription"/> <xs:enumeration value="cancelAllPriorSubscriptions"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType>

5.119Data Element: SubscriptionCountUse: The nth time the publisher has sent content as part of a description to the subscriber.

ASN.1 Representation: SubscriptionCount ::= INTEGER (1..4294967295)

XML Representation: <xs:simpleType name="SubscriptionCount" > <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> </xs:restriction></xs:simpleType> In addition, this item may be used by data structures in other ITS standards.

5.120Data Element: SubscriptionFrequencyUse: The interval (period) in seconds

ASN.1 Representation: SubscriptionFrequency ::= INTEGER (1..4294967295)

XML Representation: <xs:simpleType name="SubscriptionFrequency" > <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> </xs:restriction></xs:simpleType>

5.121Data Element: SubscriptionIDUse: A unique name created be the subscriber for a subscription. Any set of ASCII characters up to 128

ASN.1 Representation: SubscriptionID ::= IA5String (SIZE(1..128))

85


XML Representation: <xs:simpleType name="SubscriptionID" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.122Data Element: SubscriptionNameUse: A textual name for the subscription for human readers NOTE: This is not in the XML fragment you sent to me.

ASN.1 Representation: SubscriptionName ::= IA5String (SIZE(1..128))

XML Representation: <xs:simpleType name="SubscriptionName" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.123Data Element: SubscriptionTypeItemUse: An ENUMERATED list of the subscription types that a request message may use.

ASN.1 Representation: SubscriptionTypeItem ::= ENUMERATED { reserved (0), oneTime (1), periodic (2), onChange (3), ... }

XML Representation: <xs:simpleType name="SubscriptionTypeItem" > <xs:annotation> <xs:appinfo> reserved (0) oneTime (1) periodic (2) onChange (3) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="reserved"/> <xs:enumeration value="oneTime"/> <xs:enumeration value="periodic"/> <xs:enumeration value="onChange"/> </xs:restriction>

86


</xs:simpleType > </xs:union></xs:simpleType>

5.124Data Element: TimeIntervalUse: A value for how often (in various units form years to seconds) an event should occur, such as updating a data file. Expressed in the native XML format when used.

ASN.1 Representation: TimeInterval ::= IA5String (SIZE(1..255)) -- Native XML format usedXML Representation: <xs:simpleType name="TimeInterval"> <xs:restriction base="xs:duration"/></xs:simpleType>

5.125Data Element: TIMING.PLAN_Identifier_identifierUse: Id number of the traffic signal timing plan used.

ASN.1 Representation: TimingPlan-identifier ::= IA5String (SIZE(1..32)) -- Any set of alphanumeric characters up to 32

XML Representation: <xs:simpleType name="TimingPlan-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

5.126Data Element: TIMING.PLAN_Name_textUse: The user-defined name or short description of timing plan.

ASN.1 Representation: TimingPlan-name ::= IA5String (SIZE(1..128)) -- Any set of ASCII characters up to 128

XML Representation: <xs:simpleType name="TimingPlan-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType>

5.127Data Element: Volume-dataUse: The number of detected vehicles (typically from loop sensor hits) over a known location over a known period of time. A data element developed for AZTech use in both ramp meter status reporting and in setting ramp meter activation thresholds.

ASN.1 Representation: Volume-data ::= INTEGER (0..65535)

87


XML Representation: <xs:simpleType name="Volume-data" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType>

88


Appendix A – Requirements Traceability Matrix

Legend:DL - DialogMSG - MessageDE - Data Element FN - Function

Requirement Id

RequirementsDocumentSection

Requirement Data Concept Type

Data Concept Name

3.1.a 3.1 - Provide DMS Control to Remote Agencies

DL DL_DMSControlRequest

3.1.1 3.1.1 - Send DMS Control Request

The remote center shall be capable of sending a DMS control request message to the local center that controls a sign that a message is to be posted onto. The request shall include the following:

MSG MSG_DMSControlRequest-AZTech

· The ID of the receiving center· The ID of the sending center· The device ID of the DMS· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the request· The message number for the pre-defined message that is to be displayed, or· The specific message to be displayed· The message page flash time· The priority of the message being requested· The start time for the message· The start date for the message· The expiration time for the message· The expiration date for the message· Additional information/comments

3.1.2 3.1.2 - Receive DMS Control Request

The local center shall be capable of accepting and processing valid DMS control requests to display a pre-defined or new text message from one or more authorized remote centers.

MSG MSG_DMSControlRequest-AZTech

89


Requirement Id



Data Concept Name

3.1.3 3.1.3 - Send DMS Control Response

The local center shall be capable of sending a response to the requesting center. The response to a DMS control request shall include the following:

MSG MSG_DeviceControlSubscriptionResponse-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The status of the request (implemented, queued, rejected)· Additional information/comments

3.1.4 3.1.4 - Receive DMS Control Response

The remote center shall be capable of receiving a response to a DMS control request.


3.1.b 3.1 - Provide DMS Control to Remote Agencies

DL DL_DeviceCancelControlRequest

3.1.5 3.1.5 - Send DMS Cancel Control Request

The remote center shall be capable of sending a DMS cancel control request message if the center wishes to cancel a previous request to display a message. The request shall include the following:

MSG MSG_DeviceCancelControlRequest-AZTech

· The ID of the receiving center· The ID of the sending center· The device ID of the DMS· The unique request identifier assigned by the requesting center

· The security attribute (user name and password)· The operator and agency name making the request· Additional information/comments

3.1.6 3.1.6 - Receive DMS Cancel Control Request

The local center shall be capable of accepting and processing valid DMS cancel control requests to terminate a message previously requested. The local center shall display any unexpired messages based on priority.


3.1.7 3.1.7 - Send DMS Cancel Control Response

The local center shall be capable of sending a response to the requesting center to a DMS cancel control request. The response to a DMS cancel control request shall include the following:


· The ID of the receiving center

90


Requirement Id



Data Concept Name

· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the cancellation request· The status of the request (implemented, queued, rejected)· Additional information/comments

3.1.8 3.1.8 - Receive DMS Cancel Control Response

The remote center shall be capable of receiving a response to a DMS cancel control request.


3.2.a 3.2 - Provide DMS Inventory Information

DL DL_DMSInventoryUpdateSubscriptionPublication

3.2.1 3.2.1 - Send DMS Inventory Update Subscription

The remote center shall be capable of sending a DMS inventory update subscription message to each center from which it wants to receive inventory update messages. The subscription shall include the following:

MSG MSG_DeviceInventorySubscription-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the subscription· The start time of the subscription service· The start date of the subscription service or ‘ongoing’ if subscribing to daily service· The end time of the subscription service· The end date of the subscription service or ‘ongoing’ if subscribing to daily service

· Subscription to DMS enabled/disabled· Subscription to pre-defined messages enabled/disabled· Subscription to environmental sensors enabled/disabled

3.2.2 3.2.2 - Receive DMS Inventory Update Subscription

The local center shall be capable of accepting and processing valid DMS inventory update subscriptions.


91


Requirement Id



Data Concept Name

3.2.3 3.2.3 - Send DMS Inventory Update Subscription Response

The local center shall be capable of sending a response to the requesting center. The response to a DMS inventory update subscription shall include the following:


· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The subscription service ID

3.2.4 3.2.4 - Receive DMS Inventory Update Subscription Response

The remote center shall be capable of receiving a response to a DMS inventory update subscription.


3.2.5 3.2.5 - Send DMS Inventory Update

The local center shall be capable of sending a DMS inventory update message to all subscribing remote centers upon DMS, pre-defined messages, and environmental sensors being added, removed, or changed. Messages shall only be sent between the start and end times of the subscription service. The update message shall include the following:

MSG MSG_DMSInventoryPublication-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name making the update· The contact information (name, phone number, pager, email address) for the owning center· name· phone number· pager· email address(repeated for each pre-defined message)· Type of update: addition, removal, change· The message number for each pre-defined message that has been added, removed, or changed· The message content for the corresponding message number(repeated for each DMS)· Type of update: addition, removal, change

92


Requirement Id



Data Concept Name

· The device ID of each DMS that has been added, removed, or changed· The location of the device (longitude and latitude)· The road name the sign is on· The direction of travel the sign faces· The sign make and model· The sign type (VMS, CMS, BOS) and technology (LED, flip-disk, fiber optic)· The number of lines supported, if any· The number of characters supported, if any· The number of scroll pages supported, if any (repeated for each sensor)· Type of update: addition, removal, change· The device ID of each environmental sensor that has been added, removed, or changed· The location of the device (longitude and latitude)· The elevation of the sensor· The road name the sensor is on· The sensor description/purpose

3.2.6 3.2.6 - Receive DMS Inventory Update

The remote center shall be capable of receiving a DMS inventory update message.

MSG MSG_DMSInventoryPublication-AZTech

3.2.c 3.2 - Provide DMS Inventory Information

DL DL_DMSInventoryRequest

3.2.7 3.2.7 - Send DMS Inventory Request

The remote center shall be capable of sending a DMS inventory request message to other centers upon connecting to the C2C network. The request shall include the following:

MSG MSG_DeviceInventoryRequest-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the request

3.2.8 3.2.8 - Receive DMS Inventory Request

The local center shall be capable of accepting and processing valid DMS inventory requests.


3.2.9 3.2.9 - Send DMS Inventory Response

The local center shall be capable of sending a response to the requesting center. The response to a DMS inventory request shall include the following:

MSG MSG_DMSInventoryResponse-AZTech

· The ID of the receiving center

93


Requirement Id



Data Concept Name

· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The contact information (name, phone number, pager, email address) for the owning center· name· phone number· pager· email address(repeated for each pre-defined message)· The message number for each pre-defined message· The message content for the corresponding message number(repeated for each DMS)· The device ID of each DMS· The location of the device (longitude and latitude)· The road name the sign is on· The direction of travel the sign faces· The sign make and model· The sign type (VMS, CMS, BOS) and technology (LED, flip-disk, fiber optic)· The number of lines supported, if any· The number of characters supported, if any· The number of scroll pages supported, if any(repeated for each sensor)· The device ID of each environmental sensor· The location of the device (longitude and latitude)· The elevation of the sensor· The road name the sensor is on· The sensor description/purpose

3.2.10 3.2.10 - Receive DMS Inventory Response

The remote center shall be capable of receiving a response to a DMS inventory request.

MSG MSG_DMSInventoryResponse-AZTech

3.3.a 3.3 - Provide DMS Status Information

DL DL_DMSStatusRequest

94


Requirement Id



Data Concept Name

3.3.1 3.3.1 - Send DMS Status Information Request

The remote center shall be capable of sending a DMS status information request message to the local center that controls a sign that is being queried. The request shall include the following:

MSG MSG_DeviceStatusRequest-AZTech

· The ID of the receiving center· The ID of the sending center· The device ID of the DMS· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· user name· password· The operator and agency name making the request

3.3.2 3.3.2 - Receive DMS Status Information Request

The local center shall be capable of sending a response to the requesting center. The response to a DMS status information request shall include the following:


· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The operational status of the device (on, off, failed)· The message currently being displayed on the sign· The name of the agency which put the message on the sign· The priority of the message currently being displayed on the sign· The start time of the message currently being displayed on the sign· The start date of the message currently being displayed on the sign· The expiration time of the message currently being displayed on the sign· The expiration date of the message currently being displayed on the sign

95


Requirement Id



Data Concept Name

3.3.3 3.3.3 - Send DMS Status Information Response

The local center shall be capable of sending a response to the requesting center. The response to a DMS status information request shall include the following:

MSG MSG_DMSStatusResponse-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The operational status of the device (on, off, failed)· The message currently being displayed on the sign· The name of the agency which put the message on the sign· The priority of the message currently being displayed on the sign· The start time of the message currently being displayed on the sign· The start date of the message currently being displayed on the sign· The expiration time of the message currently being displayed on the sign· The expiration date of the message currently being displayed on the sign

3.3.4 3.3.4 - Receive DMS Status Information Response

The remote center shall be capable of receiving a response to a DMS status information request.


3.3.b 3.3 - Provide DMS Status Information

DL DL_DMSStatusSubscriptionPublication

3.3.5 3.3.5 - Send DMS Status Information Subscription

The remote center shall be capable of sending a DMS status information subscription message to each center from which it wants to receive status update messages. The subscription shall include the following:

MSG MSG_DeviceStatusSubscription-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the

96


Requirement Id



Data Concept Name

subscription· The start time of the subscription service· The start date of the subscription service or ‘ongoing’ if subscribing to daily service· The end time of the subscription service· The end date of the subscription service or ‘ongoing’ if subscribing to daily service

3.3.6 3.3.6 - Receive DMS Status Information Subscription

The local center shall be capable of accepting and processing valid DMS status information subscriptions.

MSG MSG_DeviceStatusSubscription-AZTech

3.3.7 3.3.7 - Send DMS Status Information Subscription Response

The local center shall be capable of sending a response to the requesting center. The response to a DMS status information subscription shall include the following:



3.3.8 3.3.8 - Receive DMS Status Information Subscription Response

The remote center shall be capable of receiving a response to a DMS status information subscription.


3.4.a 3.4 - Provide Environmental Sensor Information

DL DL_ESSStatusRequest

3.4.1 3.4.1 - Send Environmental Sensor Information Request

The remote center shall be capable of sending an environmental sensor information request message to the local center that controls a sensor that is being queried. The request shall include the following:


· The ID of the receiving center· The ID of the sending center· The device ID of the environmental sensor· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the request

97


Requirement Id



Data Concept Name

3.4.2 3.4.2 - Receive Environmental Sensor Information Request

The local center shall be capable of accepting and processing valid environmental sensor information requests.


3.4.3 3.4.3 - Send Environmental Sensor Information Response

The local center shall be capable of sending a response to the requesting center. The response to an environmental sensor information request shall include the following:

MSG MSG_ESSStatusResponse-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The operational status of the device (on, off, failed)· The indications of wind speed, direction, and gusting· The indications of air temperature· The indications of precipitation· The indications of solar radiance· The indications of roadway visibility from fog, smoke, dust, etc

3.4.4 3.4.4 - Receive Environmental Sensor Information Response

The remote center shall be capable of receiving a response to an environmental sensor information request.

MSG MSG_ESSStatusResponse-AZTech

3.5.a 3.5 - DMS Archive Status Information Subscription

DL DL_DMSArchiveStatusSubscriptionPublication

3.5.1 3.5.1 - Send DMS Archive Status Information Subscription

The remote center shall be capable of sending a DMS archive status information subscription message to each center from which it wants to receive status updates. The subscription shall include the following:

MSG MSG_DeviceArchiveStatusSubscription-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the subscription· The start time of the archival period

98


Requirement Id



Data Concept Name

· The start date of the archival period or ‘ongoing’ if subscribing to daily archival· The end time of the archival period· The end date of the archival period or ‘ongoing’ if subscribing to daily archival· Archival frequency (how often status information should be archived)· The send time (when the archived data should be sent to the requesting center)· The send date (when the archived data should be sent to the requesting center) or ‘ongoing’ if subscribing to daily archival

· Subscription to DMS status information enabled/disabled· Subscription to environmental status information enabled/disabled

3.5.2 3.5.2 - Receive DMS Archive Status Information Subscription

The local center shall be capable of accepting and processing valid DMS archive status information subscriptions.


3.5.3 3.5.3 - Send DMS Archive Status Information Response

The local center shall be capable of sending a response to the requesting center. The response to a DMS archive status information subscription shall include the following:


· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request

· The subscription service ID3.5.4 3.5.4 - Receive DMS Archive

Status Information ResponseThe remote center shall be capable of receiving a response to a DMS archive status information subscription.


3.6.a 3.6 - Provide Subscription Cancellation

DL DL_CancelSubscriptionRequest

99


Requirement Id



Data Concept Name

3.6.1 3.6.1 - Send Subscription Cancellation Request

The remote center shall be capable of sending a subscription cancellation request message to the local center when it wishes to cancel a subscription service previously started. The request shall include the following:

MSG MSG_CancelSubscriptionRequest-AZTech

· The ID of the receiving center· The ID of the sending center· The subscription service ID· The security attribute (user name and password)· The operator and agency name making the request

3.6.2 3.6.2 - Receive Subscription Cancellation Request

The local center shall be capable of accepting and processing valid subscription cancellation requests.


3.6.3 3.6.3 - Send Subscription Cancellation Response

The local center shall be capable of sending a response to the requesting center. The response to a subscription cancellation shall include the following:


· The ID of the receiving center· The ID of the sending center· The subscription service ID· The operator and agency name in the request· The name of the operator at the local center acting on the cancellation request· The status of the request (implemented, queued, rejected)· Additional information/comments

3.6.4 3.6.4 - Receive Subscription Cancellation Response

The remote center shall be capable of receiving a response to a subscription cancellation request.


4.1.a 4.1 - Provide TMS Inventory to Remote Agencies

DL DL_TMSInventoryUpdateSubscriptionPublication

100


Requirement Id



Data Concept Name

4.1.1 4.1.1 - Send TMS Inventory Update Subscription

The remote center shall be capable of sending a TMS inventory update subscription message to each center from which it wants to receive inventory update messages. Note that an inventory update is a listing of those inventory items (intersections) which are added, removed, or changed. A base condition of all existing intersections on a system would be obtained as a one-time request, rather than a subscription, using the “TMS Inventory Request” message, described in Section 4.1.7.


The subscription shall include the following:· The ID of the receiving center· The ID of the sending center· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the subscription· The start time of the subscription service· The start date of the subscription service or ‘ongoing’ if subscribing to daily service

· The end time of the subscription service· The end date of the subscription service or ‘ongoing’ if subscribing to daily service· Subscription to intersections enabled/disabled· Subscription to overlaps enabled/disabled· Subscription to special functions enabled/disabled

4.1.2 4.1.2 - Receive TMS Inventory Update Subscription

The local center shall be capable of accepting and processing valid TMS inventory update subscriptions.


4.1.3 4.1.3 - Send TMS Inventory Update Subscription Response

The local center shall be capable of sending a response to the requesting center. The response to a TMS inventory update subscription shall include the following:


· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request

101


Requirement Id



Data Concept Name

· The subscription service ID4.1.4 4.1.4 - Receive TMS Inventory

Update Subscription Response

The remote center shall be capable of receiving a response to a TMS inventory update subscription.


4.1.5 4.1.5 - Send TMS Inventory Update

The local center shall be capable of sending a TMS inventory update message to all subscribing remote centers upon intersections being added, removed, or changed. The update message shall include the following:

MSG MSG_TMSInventoryPublication-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name making the update· The contact information (name, phone number, pager, email address) for the owning center(repeated for each intersection)· Type of update: addition, removal, or change· The ID for each intersection that has been added, removed, or changed· The intersection description (name of each street at the intersection)· The ID of the section that the intersection is part of, if any· The ID of the zone that the intersection is part of, if any· The location of the intersection (longitude and latitude)(repeated for each overlap)· Type of update: addition, removal, or change· The number for each overlap that has been added, removed, or changed· The overlap description(repeated for each special function)· Type of update: addition, removal, or change· The number for each special function (usually 1 through 8)

· The definition of each special function4.1.6 4.1.6 - Receive TMS Inventory

UpdateThe remote center shall be capable of receiving a TMS inventory update message.

MSG MSG_TMSInventoryPublication-AZTech

102


Requirement Id



Data Concept Name

4.1.c 4.1 - Provide TMS Inventory to Remote Agencies

DL DL_TMSInventoryRequest

4.1.7 4.1.7 - Send TMS Inventory Request

The remote center shall be capable of sending a TMS inventory request message to other centers upon connecting to the C2C network. The request shall include the following information:


· The ID of the receiving center· The ID of the sending center· The unique request identifier· The security attribute (user name and password)· The operator and agency name making the request

4.1.8 4.1.8 - Receive TMS Inventory Request

The local center shall be capable of accepting and processing valid TMS inventory requests.


4.1.9 4.1.9 - Send TMS Inventory Response

The local center shall be capable of sending a response to the requesting center. The response to a TMS inventory request shall include the following:

MSG MSG_TMSInventoryResponse-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The contact information (name, phone number, pager, email address) for the owning center (repeated for each intersection)· The ID for each intersection· The intersection description (name of each street at the intersection)· The ID of the section that the intersection is a part of, if any· The ID of the zone that the intersection is a part of, if any· The location of the intersection (longitude and latitude)

4.1.10 4.1.10 - Receive TMS Inventory Response

The remote center shall receive responses to TMS inventory requests.


103


Requirement Id



Data Concept Name

4.2.a 4.2 - Provide Intersection Information to Remote Agencies

DL DL_TMSInventoryRequest

4.2.1 4.2.1 - Send Intersection Information Request

The remote center shall be capable of sending an intersection information request message to other centers when it wishes to request detailed information for that intersection. The request shall include the following:


· The ID of the receiving center· The ID of the sending center· The ID of the intersection· The unique request identifier· The security attribute (user name and password)· The operator and agency name making the request

4.2.2 4.2.2 - Receive Intersection Request

The local center shall be capable of accepting and processing valid intersection information requests.


4.2.3 4.2.3 - Send Intersection Information Response

The local center shall be capable of sending a response to the requesting center. The response to an intersection information request shall include the following:


· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The ID of the section that the intersection is a part of, if any· The ID of the zone that the intersection is a part of, if any· The location of the intersection (longitude and latitude)· Time source used by the intersection (GPS, UTC)

(in the case of a ramp meter)· The name of the nearest major cross street to the ramp meter· The direction of travel the ramp meter controls· The number of lanes controlled by the ramp meter

(repeated for each timing plan)

104


Requirement Id



Data Concept Name

· The ID of each timing plan defined for the intersection· The description of the timing plan

(repeated for each scheduled activity)· The start time for each scheduled activity· The stop time for each scheduled activity· The ID of the timing plan for each scheduled activity

(repeated for each detector)· The device ID of each detector at the intersection· The location of the device (longitude and latitude)· The lane the detector is monitoring· The setback from stopbar· The type of detector (speed, volume, occupancy)

(repeated for each overlap)· The number for each overlap· The overlap description (repeated for each special function)· The number for each special function (usually 1 through 8)· The definition of each special function

(repeated for each controller log entry during the last 24 hours)· The time and date for each controller log entry· The controller log entry

4.2.4 4.2.4 - Receive Intersection Information Response

The remote center shall be capable of receiving responses to intersection information requests.


4.3.a 4.3 - Provide Timing Plan Details to Remote Agencies

DL DL_TMSTimingPlanDetailRequest

4.3.1 4.3.1 - Send Timing Plan Detail Request

The remote center shall be capable of sending a timing plan detail request message to other centers when it wishes to request detailed information for that timing plan. The request shall include the following:

MSG MSG_TMSTimingPlanDetailRequest-AZTech

105


Requirement Id



Data Concept Name

· The ID of the receiving center· The ID of the sending center· The ID of the intersection· The ID of a timing plan defined for the intersection· The unique request identifier· The security attribute (user name and password)· The operator and agency name making the request

4.3.2 4.3.2 - Receive Timing Plan Detail Request

The local center shall be capable of accepting and processing valid timing plan detail requests.

MSG MSG_TMSTimingPlanDetailRequest-AZTech

4.3.3 4.3.3 - Send Timing Plan Detail Response

The local center shall be capable of sending a response to the requesting center. The response to a timing plan detail request shall include the following:

MSG MSG_TMSTimingPlanDetailResponse-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The cycle length· The offset· The number of phases

(repeated for each phase)· The movement for each phase (NBT, NBL, NBR, etc)· The split for each phase

4.3.4 4.3.4 - Receive Timing Plan Detail Response

The remote center shall be capable of receiving responses to timing plan detail requests.

MSG MSG_TMSTimingPlanDetailResponse-AZTech

4.4.a 4.4 - Provide Intersection Control to Remote Agencies

DL DL_TMSControlRequest

4.4.1 4.4.1 - Send Intersection Control Request

The remote center shall be capable of sending an intersection control request message to the local center that owns the intersection to be controlled. The request shall include the following:

MSG MSG_TMSControlRequest-AZTech

· The ID of the receiving center· The ID of the sending center· The ID of the intersection

106


Requirement Id



Data Concept Name

· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the request· The start time for the control request· The start date for the control request· The expiration time for the control request· The expiration date for the control request· The timing plan number to run, if any

(in the case of a ramp meter)· The new state of the ramp meter (on or off)· The volume/rate to set for the ramp meter

(repeated for each special function, if any)· The number of the special function to set· The new value for the special function (on or off)

· Additional information/comments4.4.2 4.4.2 - Receive Intersection

Control RequestThe local center shall be capable of accepting and processing valid intersection control requests to control an intersection from authorized remote centers.

MSG MSG_TMSControlRequest-AZTech

4.4.3 4.4.3 - Send Intersection Control Response

The local center shall be capable of sending a response to the requesting center. The response to an intersection control request shall include the following:


· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The status of the request (implemented, queued, rejected)· Additional information/comments

4.4.4 4.4.4 - Receive Intersection Control Response

The remote center shall be capable of receiving a response to an intersection control request.


107


Requirement Id



Data Concept Name

4.4.b 4.4 - Provide Intersection Control to Remote Agencies

DL DL_DeviceCancelControlRequest

4.4.5 4.4.5 - Send Intersection Cancel Control Request

The remote center shall be capable of sending an intersection cancel control request message if the center wishes to cancel a previous timing plan change. The request shall include the following:


· The ID of the receiving center· The ID of the sending center· The ID of the intersection· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the request· Additional information/comments

4.4.6 4.4.6 - Receive Intersection Cancel Control Request

The local center shall be capable of accepting and processing valid intersection cancel control requests to terminate a timing plan previously requested.


The local center shall revert to the previously scheduled timing plan.

FN

4.4.7 4.4.7 - Send Intersection Cancel Control Response

The local center shall be capable of sending a response to the requesting center. The response to an intersection cancel control request shall include the following:


· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the cancellation request· The status of the request (implemented, queued, rejected)· Additional information/comments

4.4.8 4.4.8 - Receive Intersection Cancel Control Response

The remote center shall be capable of receiving a response to an intersection cancel control request.


4.5.a 4.5 - Provide Intersection Status to Remote Agencies

DL DL_TMSStatusRequest

108


Requirement Id



Data Concept Name

4.5.1 4.5.1 - Send Intersection Status Request

The remote center shall be capable of sending an intersection status request message to the local center that controls an intersection that is being queried. The request shall include the following:


· The ID of the receiving center· The ID of the sending center· The ID of the intersection· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the request

4.5.2 4.5.2 - Receive Intersection Status Request

The local center shall be capable of accepting and processing valid intersection status requests.


4.5.3 4.5.3 - Send Intersection Status Response

The local center shall be capable of sending a response to an intersection status request. The response to an intersection status request shall include the following:

MSG MSG_TMSStatusResponse-AZTech

· The ID of the receiving center· The ID of the sending center· The unique request identifier· The operator and agency name in the request· The name of the operator at the local center acting on the request· The operational status of the controller (on, off, free, flash)· The ID of the timing plan that is running, if any· The current time in the controller· The current time at central· The current Coordinated Universal Time (UTC)· The battery backup status

(in the case of a ramp meter)· The status of the ramp meter (on, off, fail)· The volume/rate for the ramp meter

(repeated for each special function)· The number of each special function· The value for each special function

109


Requirement Id



Data Concept Name

(repeated for each detector)· The ID of each detector· The value for each detector

4.5.4 4.5.4 - Receive Intersection Status Response

The remote center shall be capable of receiving a response to an intersection status request.

MSG MSG_TMSStatusResponse-AZTech

4.6.a 4.6 -TMS Archive Status Information Subscription

DL DL_TMSArchiveStatusSubscriptionPublication

4.6.1 4.6.1 - Send TMS Archive Status Information Subscription

The remote center shall be capable of sending a TMS archive status information subscription message to each center from which it wants to receive status updates. The subscription shall include the following:


· The ID of the receiving center· The ID of the sending center· The unique request identifier assigned by the requesting center· The security attribute (user name and password)· The operator and agency name making the subscription· The start time of the archival period· The start date of the archival period or ‘ongoing’ if subscribing to daily archival· The end time of the archival period· The end date of the archival period or ‘ongoing’ if subscribing to daily archival

· Archival frequency (how often status information should be archived)

· The send time (when the archived data should be sent to the requesting center)

· The send date (when the archived data should be sent to the requesting center) or ‘ongoing’ if subscribing to daily archival

4.6.2 4.6.2 - Receive TMS Archive Status Information Subscription

The local center shall be capable of accepting and processing valid TMS archive status information subscriptions.


110


Requirement Id



Data Concept Name

4.6.3 4.6.3 - Send TMS Archive Status Information Response

The local center shall be capable of sending a response to the requesting center. The response to a TMS archive status information subscription shall include the following:



4.6.4 4.6.4 - Receive TMS Archive Status Information Response

The remote center shall be capable of receiving a response to a TMS archive status information subscription.


4.7.a 4.7 - Provide Subscription Cancellation

DL DL_CancelSubscriptionRequest

4.7.1 4.7.1 - Send Subscription Cancellation Request

The remote center shall be capable of sending a subscription cancellation request message to the local center when it wishes to cancel a subscription service previously started. The request shall include the following:


· The ID of the receiving center· The ID of the sending center· The subscription service ID· The security attribute (user name and password)· The operator and agency name making the request

4.7.2 4.7.2 - Receive Subscription Cancellation Request

The local center shall be capable of accepting and processing valid subscription cancellation requests.


4.7.3 4.7.3 - Send Subscription Cancellation Response

The local center shall be capable of sending a response to the requesting center. The response to a subscription cancellation shall include the following:


· The ID of the receiving center· The ID of the sending center· The subscription service ID· The operator and agency name in the request· The name of the operator at the local center acting on the cancellation request· The status of the request (implemented, queued,

111


Requirement Id



Data Concept Name

rejected)· Additional information/comments

4.7.4 4.7.4 - Receive Subscription Cancellation Response

The remote center shall be capable of receiving a response to a subscription cancellation request.


112


113

Appendix B - Web Services Description Language Listing

This section provides the formal Web Services Description Language document for the subject project. The WSDL is based on the text and examples provided in the NTCIP 2306 standard. The WSDL is also available in XML electronic format at http://www.someplace.com/c2cxml/specification.

<?xml version="1.0" encoding="UTF-8"?><definitions name="CenterServices" targetNamespace="http://center-services"

xmlns="http://schemas.xmlsoap.org/wsdl/"xmlns:tns="http://center-services"xmlns:aztech="http://www.AZTECH-Local-Draft-01-00-06"xmlns:ftp="http://schemas.ntcip.org/wsdl/ftp/"xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

><types>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"><xs:import namespace="http://www.AZTECH-Local-Draft-01-00-06"

schemaLocation="aztech.xsd"/></xs:schema>

</types><message name="MSG_CancelSubscriptionRequest-AZTech">

<part name="message" element="aztech:cancelSubscriptionRequest-AZTech"/></message><message name="MSG_DeviceArchiveStatusSubscription-AZTech">

<part name="message" element="aztech:deviceArchiveStatusSubscription-AZTech"/></message><message name="MSG_DeviceCancelControlRequest-AZTech">

<part name="message" element="aztech:deviceCancelControlRequest-AZTech"/></message><message name="MSG_DeviceControlSubscriptionResponse-AZTech">

<part name="message" element="aztech:deviceControlSubscriptionResponse-AZTech"/></message><message name="MSG_DeviceInventoryRequest-AZTech">

<part name="message" element="aztech:deviceInventoryRequest-AZTech"/></message><message name="MSG_DeviceInventorySubscription-AZTech">

<part name="message" element="aztech:deviceInventorySubscription-AZTech"/></message><message name="MSG_DeviceStatusRequest-AZTech">

<part name="message" element="aztech:deviceStatusRequest-AZTech"/></message><message name="MSG_DeviceStatusSubscription-AZTech">

<part name="message" element="aztech:deviceStatusSubscription-AZTech"/></message><message name="MSG_DMSControlRequest-AZTech">

<part name="message" element="aztech:dMSControlRequest-AZTech"/></message><message name="MSG_DMSInventoryResponse-AZTech">

<part name="message" element="aztech:dMSInventoryResponse-AZTech"/></message><message name="MSG_DMSInventoryPublication-AZTech">

<part name="message" element="aztech:dMSInventoryPublication-AZTech"/></message><message name="MSG_DMSStatusResponse-AZTech">

<part name="message" element="aztech:dMSStatusResponse-AZTech"/>

114

http://www.someplace.com/c2cxml/specification

</message><message name="MSG_DMSStatusPublication-AZTech">

<part name="message" element="aztech:dMSStatusPublication-AZTech"/></message><message name="MSG_ESSStatusResponse-AZTech">

<part name="message" element="aztech:eSSStatusResponse-AZTech"/></message><message name="MSG_TMSControlRequest-AZTech">

<part name="message" element="aztech:tMSControlRequest-AZTech"/></message><message name="MSG_TMSInventoryResponse-AZTech">

<part name="message" element="aztech:tMSInventoryResponse-AZTech"/></message><message name="MSG_TMSInventoryPublication-AZTech">

<part name="message" element="aztech:tMSInventoryPublication-AZTech"/></message><message name="MSG_TMSStatusResponse-AZTech">

<part name="message" element="aztech:tMSStatusResponse-AZTech"/></message><message name="MSG_TMSStatusPublication-AZTech">

<part name="message" element="aztech:tMSStatusPublication-AZTech"/></message><message name="MSG_TMSTimingPlanDetailRequest-AZTech">

<part name="message" element="aztech:tMSInformationTimingPlanDetailRequest-AZTech"/></message><message name="MSG_TMSTimingPlanDetailResponse-AZTech">

<part name="message" element="aztech:timingPlanDetailResponse-AZTech"/></message>

<portType name="aztechSoapHttpServicePortType">

<operation name = "OP_CancelSubscriptionRequest"><input message="tns:MSG_CancelSubscriptionRequest-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_DMSControlRequest">

<input message="tns:MSG_DMSControlRequest-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_DMSInventoryRequest">

<input message="tns:MSG_DeviceInventoryRequest-AZTech"/><output message="tns:MSG_DMSInventoryResponse-AZTech"/>

</operation><operation name = "OP_DMSStatusRequest">

<input message="tns:MSG_DeviceStatusRequest-AZTech"/><output message="tns:MSG_DMSStatusResponse-AZTech"/>

</operation><operation name = "OP_DeviceArchiveStatusSubscription">

<input message="tns:MSG_DeviceArchiveStatusSubscription-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_DeviceCancelControlRequest">

<input message="tns:MSG_DeviceCancelControlRequest-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_DeviceInventoryUpdateSubscription">

<input message="tns:MSG_DeviceInventorySubscription-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_DeviceStatusUpdateSubscription">

<input message="tns:MSG_DeviceStatusSubscription-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

115

</operation><operation name = "OP_ESSStatusRequest">

<input message="tns:MSG_DeviceStatusRequest-AZTech"/><output message="tns:MSG_ESSStatusResponse-AZTech"/>

</operation><operation name = "OP_TMSControlRequest">

<input message="tns:MSG_TMSControlRequest-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_TMSInventorylRequest">

<input message="tns:MSG_TMSInventoryRequest-AZTech"/><output message="tns:MSG_TMSInventoryResponse-AZTech"/>

</operation><operation name = "OP_TMSStatusRequest">

<input message="tns:MSG_DeviceStatusRequest-AZTech"/><output message="tns:MSG_TMSStatusResponse-AZTech"/>

</operation><operation name = "OP_TMSTimingPlanDetailRequest">

<input message="tns:MSG_TMSTimingPlanDetailRequest-AZTech"/><output message="tns:MSG_TMSTimingPlanDetailResponse-AZTech"/>

</operation></portType>

<portType name="aztechSubscriberCallbackServicePortType">

<operation name = "OP_SubscriberDMSArchiveStatusUpdate"><input message="tns:MSG_DeviceStatusPublication-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_SubscriberDMSInventoryUpdate">

<input message="tns:MSG_DMSInventoryPublication-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_SubscriberDMSStatusUpdate">

<input message="tns:MSG_DMSStatusPublication-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_SubscriberTMSArchiveStatusUpdate">

<input message="tns:MSG_TMSStatusPublication-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_SubscriberTMSInventoryUpdate">

<input message="tns:MSG_TMSInventoryPublication-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation><operation name = "OP_SubscriberTMSStatusUpdate">

<input message="tns:MSG_TMSStatusPublication-AZTech"/><output message="tns:MSG_DeviceControlSubscriptionResponse-AZTech"/>

</operation></portType>

<binding name="aztechSoapHttpServiceBinding"

type="tns:aztechSoapHttpServicePortType"><soap:binding style="document"

transport="http://schemas.xmlsoap.org/soap/http"/><operation name = "OP_CancelSubscriptionRequest">

<soap:operation soapAction="dummy.cgi" style="document"/><input>

<soap:body use="literal"/></input>

116


<output><soap:body use="literal"/>

</output></operation><operation name = "OP_DMSControlRequest">


<soap:body use="literal"/></input><output>

<soap:body use="literal"/></output>

</operation><operation name = "OP_DMSInventoryRequest">




</operation><operation name = "OP_DMSStatusRequest">




</operation><operation name = "OP_DeviceArchiveStatusSubscription">




</operation><operation name = "OP_DeviceCancelControlRequest">




</operation><operation name = "OP_DeviceInventoryUpdateSubscription">




</operation><operation name = "OP_DeviceStatusUpdateSubscription">


<soap:body use="literal"/></input>

117

<output><soap:body use="literal"/>

</output></operation><operation name = "OP_ESSStatusRequest">




</operation><operation name = "OP_TMSControlRequest">




</operation><operation name = "OP_TMSInventorylRequest">




</operation><operation name = "OP_TMSStatusRequest">




</operation><operation name = "OP_TMSTimingPlanDetailRequest">




</operation></binding>

<binding name="aztechSubscriberCallbackServiceBinding"

type="tns:aztechSubscriberCallbackServicePortType"><soap:binding style="document"

transport="http://schemas.xmlsoap.org/soap/http"/><operation name = "OP_SubscriberDMSArchiveStatusUpdate">



118

</operation><operation name = "OP_SubscriberDMSInventoryUpdate">




</operation><operation name = "OP_SubscriberDMSStatusUpdate">




</operation><operation name = "OP_SubscriberTMSArchiveStatusUpdate">




</operation><operation name = "OP_SubscriberTMSInventoryUpdate">




</operation><operation name = "OP_SubscriberTMSStatusUpdate">




</operation></binding>

<service name="aztechSoapHttpService">

<port name="aztechSoapHttpServicePort"binding="tns:aztechSoapHttpServiceBinding"><soap:address location="http://myc2c.system.com/c2cxml/"/>

</port></service><service name="aztechSubscriberCallbackService">

<port name="aztechSubscriberCallbackServicePort"binding="tns:aztechSubscriberCallbackServiceBinding"><soap:address location="http://myc2c.subscriber.com/c2cxml"/>

</port>

119


</service></definitions>

120

Appendix C - XML Schema Listing

This section describes the XML schema that shall be used to validate the XML messages exchanged between AZTech C2C systems. The XML Schemas are also available in XML electronic format at http://www.someplace.com/c2cxml/specification.

<?xml version="1.0" encoding="UTF-8"?>  <xs:schema targetNamespace="http://www.AZTECH-Local-Draft-01-00-06" xmlns="http://www.AZTECH-Local-Draft-01-00-06" xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="unqualified" attributeFormDefault="unqualified" version="DRAFT">

<xs:annotation> <xs:documentation> Exported on: 03:53:24 PM Tuesday, August 15, 2006 From file: C:\Documents and Settings\DavidK\My Documents\code\1stWord\AzDot-TMDD work\AzTech_01-00-06.ITS [By: Mini-Edit Rev 2.1.439] </xs:documentation></xs:annotation>

<xs:complexType name="AuthorizationSet" > <xs:sequence> <xs:element name="user-id" type="Security-user-name" /> <xs:element name="password" type="Security-password" /> <xs:element name="hashtime" type="DateTimePair" /> <xs:element name="hash" > <xs:simpleType> <xs:restriction base="xs:string"> <xs:minLength value="10"/> <xs:maxLength value="20"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence>

121

http://www.someplace.com/c2cxml/specification

</xs:complexType> <xs:complexType name="BroadcastAlerts" > <xs:sequence minOccurs="1" maxOccurs="2"> <xs:element name="broadcastAlert" type="BroadcastAlertsItem" /> </xs:sequence></xs:complexType> <xs:simpleType name="BroadcastAlertsItem" > <xs:annotation> <xs:appinfo> reserved (0) broadcastAlertsAccepted (1) broadcastAlertsNotAccepted (2) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="2"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="reserved"/> <xs:enumeration value="broadcastAlertsAccepted"/> <xs:enumeration value="broadcastAlertsNotAccepted"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:complexType name="C2cMessagePublication" > <xs:sequence> <xs:element name="informationalText" type="InformationalText" minOccurs="0"/> <xs:element name="subscriptionID" type="SubscriptionID" /> <xs:element name="subscriptionName" type="SubscriptionName" minOccurs="0"/> <xs:element name="subscriptionFreq" type="SubscriptionFrequency" minOccurs="0"/> <xs:element name="subscriptionCount" type="SubscriptionCount" minOccurs="0"/> </xs:sequence></xs:complexType> <xs:complexType name="C2cMessageReceipt" > <xs:sequence> <xs:element name="informationalText" type="InformationalText" /> </xs:sequence></xs:complexType> <xs:complexType name="C2cMessageSubscription" > <xs:sequence> <xs:element name="informationalText" type="InformationalText" minOccurs="0"/> <xs:element name="returnAddress" type="ReturnAddress" /> <xs:element name="subscriptionAction" type="SubscriptionAction" />

122

<xs:element name="subscriptionType" type="SubscriptionType" /> <xs:element name="subscriptionID" type="SubscriptionID" /> <xs:element name="subscriptionName" type="SubscriptionName" minOccurs="0"/> <xs:element name="subscriptionTimeFrame" type="SubscriptionTimeFrame" minOccurs="0"/> <xs:element name="subscriptionFrequency" type="SubscriptionFrequency" /> <xs:element name="broadcastAlerts" type="BroadcastAlerts" minOccurs="0"/> </xs:sequence></xs:complexType> <xs:element name="cancelSubscriptionRequest-AZTech" type="CancelSubscriptionRequest-AZTech"/><xs:complexType name="CancelSubscriptionRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType> <xs:complexType name="ContactDetails" > <xs:sequence> <xs:element name="contact-id" type="Contact-identifier" /> <xs:element name="person-name" type="Contact-person-name" minOccurs="0"/> <xs:element name="person-title" type="Contact-person-title" minOccurs="0"/> <xs:element name="phone-number" type="Contact-phone-number" minOccurs="0"/> <xs:element name="phone-alternate" type="Contact-phone-alternate" minOccurs="0"/> <xs:element name="email-address" type="Contact-email-address" minOccurs="0"/> </xs:sequence></xs:complexType> <xs:simpleType name="Contact-email-address" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Contact-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Contact-person-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="64"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Contact-person-title" >

123

<xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="64"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Contact-phone-alternate" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Contact-phone-number" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:complexType name="Controller-log-entry" > <xs:sequence> <xs:element name="time" type="DateTimePair" /> <xs:element name="text" type="FreeText" /> </xs:sequence></xs:complexType> <xs:simpleType name="Date"> <xs:restriction base="xs:date"/></xs:simpleType> <xs:simpleType name="DateTimePair"> <xs:restriction base="xs:dateTime"/></xs:simpleType> <xs:complexType name="DetectionLane" > <xs:sequence> <xs:element name="approach-name" type="Detector-intersection-approach-name" minOccurs="0"/> <xs:element name="lane-number" type="Detector-lane-number" minOccurs="0"/> </xs:sequence></xs:complexType> <xs:complexType name="DetectorDetails" > <xs:sequence> <xs:element name="detector-id" type="Detector-identifier" /> <xs:element name="device-latitude" type="Latitude" /> <xs:element name="device-longitude" type="Longitude" /> <xs:element name="link-direction" type="Link-direction" minOccurs="0"/> <xs:element name="detector-type" type="Detector-type" /> <xs:element name="detection-lanes" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="64"> <xs:element name="detection-lane" type="DetectionLane" /> </xs:sequence>

124

</xs:complexType> </xs:element> <xs:element name="setback" type="Distance" /> </xs:sequence></xs:complexType> <xs:simpleType name="Detector-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Detector-intersection-approach-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Detector-lane-number" > <xs:restriction base="binary"> <xs:minLength value="1"/> <xs:maxLength value="255"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Detector-type" > <xs:annotation> <xs:appinfo> inductive loop (1) magnetic (2) magnetometers (3) pressure cells (4) microwave radar (5) ultrasonic (6) video Image (7) laser (8) infrared (9) road tube (10) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="10"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="inductive loop"/> <xs:enumeration value="magnetic"/> <xs:enumeration value="magnetometers"/> <xs:enumeration value="pressure cells"/> <xs:enumeration value="microwave radar"/> <xs:enumeration value="ultrasonic"/> <xs:enumeration value="video Image"/> <xs:enumeration value="laser"/>

125

<xs:enumeration value="infrared"/> <xs:enumeration value="road tube"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="Device-acknowledge-control" > <xs:annotation> <xs:appinfo> control acknowledged (0) device available (1) requested changes completed (2) control rejected (3) device in use (4) device off line (5) request cancelled (6) request rejected invalid command parameters (7) request rejected insufficient privileges of the requesting operator (8) request queued (9) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="9"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="control acknowledged"/> <xs:enumeration value="device available"/> <xs:enumeration value="requested changes completed"/> <xs:enumeration value="control rejected"/> <xs:enumeration value="device in use"/> <xs:enumeration value="device off line"/> <xs:enumeration value="request cancelled"/> <xs:enumeration value="request rejected invalid command parameters"/> <xs:enumeration value="request rejected insufficient privileges of the requesting operator"/> <xs:enumeration value="request queued"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:element name="deviceArchiveStatusSubscription-AZTech" type="DeviceArchiveStatusSubscription-AZTech"/><xs:complexType name="DeviceArchiveStatusSubscription-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="command-start-time" type="DateTimePair" /> <xs:element name="command-end-time" type="DateTimePair" /> <xs:element name="archive-frequency" type="TimeInterval" /> <xs:element name="request-send-time" type="Time" /> <xs:element name="request-send-date" type="Date" />

126

<xs:element name="filters" type="Filters" /> </xs:sequence></xs:complexType> <xs:element name="deviceCancelControlRequest-AZTech" type="DeviceCancelControlRequest-AZTech"/><xs:complexType name="DeviceCancelControlRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-type" type="Device-type" /> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType> <xs:simpleType name="Device-command-end-time" > <xs:restriction base="xs:int"/></xs:simpleType> <xs:simpleType name="Device-command-request-priority" > <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/> <xs:maxInclusive value="10"/> </xs:restriction></xs:simpleType> <xs:element name="deviceControlSubscriptionResponse-AZTech" type="DeviceControlSubscriptionResponse-AZTech"/><xs:complexType name="DeviceControlSubscriptionResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationLong" /> <xs:element name="organization-requesting" type="OrganizationInformationShort" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="request-status" type="Device-acknowledge-control" /> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType> <xs:simpleType name="Device-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:element name="deviceInventoryRequest-AZTech" type="DeviceInventoryRequest-AZTech"/><xs:complexType name="DeviceInventoryRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" />

127

<xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-type" type="Device-type" /> <xs:element name="device-list" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="100000"> <xs:element name="device" type="Device-identifier" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType> <xs:element name="deviceInventorySubscription-AZTech" type="DeviceInventorySubscription-AZTech"/><xs:complexType name="DeviceInventorySubscription-AZTech" > <xs:sequence> <xs:element name="c2cMessageSubscription" type="C2cMessageSubscription" /> <xs:element name="deviceInventoryRequest" type="DeviceInventoryRequest-AZTech" /> </xs:sequence></xs:complexType> <xs:simpleType name="Device-operational-status" > <xs:annotation> <xs:appinfo> on (1) off (2) in service (3) out of service (4) unavailable (5) unknown (6) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="6"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="on"/> <xs:enumeration value="off"/> <xs:enumeration value="in service"/> <xs:enumeration value="out of service"/> <xs:enumeration value="unavailable"/> <xs:enumeration value="unknown"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="Device-request-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/>

128

</xs:restriction></xs:simpleType> <xs:element name="deviceStatusRequest-AZTech" type="DeviceStatusRequest-AZTech"/><xs:complexType name="DeviceStatusRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-type" type="Device-type" /> <xs:element name="device-list" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="100000"> <xs:element name="device" type="Device-identifier" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType> <xs:element name="deviceStatusSubscription-AZTech" type="DeviceStatusSubscription-AZTech"/><xs:complexType name="DeviceStatusSubscription-AZTech" > <xs:sequence> <xs:element name="c2cMessageSubscription" type="C2cMessageSubscription" /> <xs:element name="deviceStatusRequest" type="DeviceStatusRequest-AZTech" /> </xs:sequence></xs:complexType> <xs:simpleType name="Device-type" > <xs:annotation> <xs:appinfo> detector (1) cctv camera (2) dynamic message sign (3) environmental sensor station (4) gate (5) highway advisory radio (6) lane control signal (7) ramp meter (8) signal controller (9) signal section (10) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="10"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="detector"/> <xs:enumeration value="cctv camera"/> <xs:enumeration value="dynamic message sign"/> <xs:enumeration value="environmental sensor station"/> <xs:enumeration value="gate"/>

129

<xs:enumeration value="highway advisory radio"/> <xs:enumeration value="lane control signal"/> <xs:enumeration value="ramp meter"/> <xs:enumeration value="signal controller"/> <xs:enumeration value="signal section"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:complexType name="Distance" > <xs:choice> <xs:element name="m" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-10000000"/> <xs:maxInclusive value="10000000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="mDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-10000000"/> <xs:maxInclusive value="10000000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="mm" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="mmDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="dm" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="dmDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-1000000"/>

130

<xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="yd" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-17600000"/> <xs:maxInclusive value="17600000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="ydDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-17600000"/> <xs:maxInclusive value="17600000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="ft" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-52800000"/> <xs:maxInclusive value="52800000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="ftDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-52800000"/> <xs:maxInclusive value="52800000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="in" > <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="inDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-1000000"/> <xs:maxInclusive value="1000000"/> </xs:restriction> </xs:simpleType> </xs:element>  

131

<xs:element name="mi" > <xs:simpleType> <xs:restriction base="xs:short"> <xs:minInclusive value="-10000"/> <xs:maxInclusive value="10000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="miDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-10000"/> <xs:maxInclusive value="10000"/> </xs:restriction> </xs:simpleType> </xs:element>    <xs:element name="km" > <xs:simpleType> <xs:restriction base="xs:short"> <xs:minInclusive value="-10000"/> <xs:maxInclusive value="10000"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="kmDec" > <xs:simpleType> <xs:restriction base="xs:float"> <xs:minInclusive value="-10000"/> <xs:maxInclusive value="10000"/> </xs:restriction> </xs:simpleType> </xs:element>    </xs:choice></xs:complexType> <xs:element name="dMSControlRequest-AZTech" type="DMSControlRequest-AZTech"/><xs:complexType name="DMSControlRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="dms-beacon-control" type="DmsMessageMultiString" /> <xs:element name="dms-message" type="DmsMessageMultiString" /> <xs:element name="message-number" type="DmsMessageNumber" /> <xs:element name="command-request-priority" type="Device-command-request-priority" /> <xs:element name="command-start-time" type="DateTimePair" /> <xs:element name="command-end-time" type="DateTimePair" /> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType>

132

<xs:element name="dMSDeviceStatus" type="DMSDeviceStatus"/><xs:complexType name="DMSDeviceStatus" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="dms-device-status" type="Device-operational-status" /> <xs:element name="dms-current-message" type="DmsMessageMultiString" /> <xs:element name="message-time-remaining" type="DmsMessageTimeRemaining" minOccurs="0"/> <xs:element name="last-comm-time" type="DateTimePair" /> </xs:sequence></xs:complexType> <xs:element name="dMSInventoryPublication-AZTech" type="DMSInventoryPublication-AZTech"/><xs:complexType name="DMSInventoryPublication-AZTech" > <xs:sequence> <xs:element name="c2cMessagePublication" type="C2cMessagePublication" /> <xs:element name="dMSInventory" type="DMSInventoryResponse-AZTech" /> </xs:sequence></xs:complexType> <xs:element name="dMSInventoryResponse-AZTech" type="DMSInventoryResponse-AZTech"/><xs:complexType name="DMSInventoryResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationLong" /> <xs:element name="organization-requesting" type="OrganizationInformationShort" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="device" type="DMSDeviceStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType> <xs:simpleType name="DmsMessageBeacon" > <xs:annotation> <xs:appinfo> beacons are disabled (0) beacons are enabled (1) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="1"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="beacons are disabled"/> <xs:enumeration value="beacons are enabled"/> </xs:restriction> </xs:simpleType > </xs:union>

133

</xs:simpleType> <xs:complexType name="DmsMessageMultiString" > <xs:simpleContent> <xs:extension base="DmsMessageMultiString-string" > <xs:attribute name="EncodingType" use="required"> <xs:simpleType> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="base64Binary"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:extension> </xs:simpleContent></xs:complexType><xs:simpleType name="DmsMessageMultiString-string"> <xs:restriction base="xs:base64Binary"> <xs:minLength value="2"/> <xs:maxLength value="342"/> </xs:restriction></xs:simpleType > <xs:simpleType name="DmsMessageNumber" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType> <xs:simpleType name="DmsMessageTimeRemaining" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType> <xs:simpleType name="DmsSignTechnology-item" > <xs:annotation> <xs:appinfo> other (0) led (1) flip disk (2) fiber optics (3) shuttered (4) bulb (5) drum (6) spare7 (7) -- Adding to make a full byte </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:int"> <xs:minInclusive value="0"/> <xs:maxInclusive value="7"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="other"/> <xs:enumeration value="led"/> <xs:enumeration value="flip disk"/> <xs:enumeration value="fiber optics"/> <xs:enumeration value="shuttered"/> <xs:enumeration value="bulb"/> <xs:enumeration value="drum"/>

134

<xs:enumeration value="spare7"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType><xs:simpleType name="DmsSignTechnology"> <xs:list itemType="DmsSignTechnology-item"/></xs:simpleType> <xs:element name="dMSStatusPublication-AZTech" type="DMSStatusPublication-AZTech"/><xs:complexType name="DMSStatusPublication-AZTech" > <xs:sequence> <xs:element name="c2cMessagePublication" type="C2cMessagePublication" /> <xs:element name="dMSStatus" type="DMSStatusResponse-AZTech" /> </xs:sequence></xs:complexType> <xs:element name="dMSStatusResponse-AZTech" type="DMSStatusResponse-AZTech"/><xs:complexType name="DMSStatusResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="device" type="DMSDeviceStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType> <xs:simpleType name="EssAirTemperature" > <xs:restriction base="xs:short"> <xs:minInclusive value="-1000"/> <xs:maxInclusive value="1001"/> </xs:restriction></xs:simpleType> <xs:simpleType name="EssAvgWindDirection" > <xs:restriction base="xs:unsignedShort"> <xs:maxInclusive value="361"/> </xs:restriction></xs:simpleType> <xs:simpleType name="EssAvgWindSpeed" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType> <xs:simpleType name="EssPrecipYesNo" > <xs:annotation> <xs:appinfo> precip (1) no precip (2)

135

error (3) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="precip"/> <xs:enumeration value="no precip"/> <xs:enumeration value="error"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="EssSolarRadiation" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType> <xs:element name="eSSStatus" type="ESSStatus"/><xs:complexType name="ESSStatus" > <xs:sequence> <xs:element name="center-id" type="Organization-center-identifier" minOccurs="0"/> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="device-status" type="Device-operational-status" /> <xs:element name="avg-wind-direction" type="EssAvgWindDirection" /> <xs:element name="avg-wind-speed" type="EssAvgWindSpeed" minOccurs="0"/> <xs:element name="wind-situation" type="EssWindSituation" minOccurs="0"/> <xs:element name="air-temperature" type="EssAirTemperature" minOccurs="0"/> <xs:element name="precip-yes-no" type="EssPrecipYesNo" minOccurs="0"/> <xs:element name="solar-radiation" type="EssSolarRadiation" minOccurs="0"/> <xs:element name="visibility" type="EssVisibility" minOccurs="0"/> </xs:sequence></xs:complexType> <xs:element name="eSSStatusResponse-AZTech" type="ESSStatusResponse-AZTech"/><xs:complexType name="ESSStatusResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="device" type="ESSStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType> <xs:simpleType name="EssVisibility" >

136

<xs:restriction base="xs:unsignedInt"> <xs:maxInclusive value="1000001"/> </xs:restriction></xs:simpleType> <xs:simpleType name="EssWindSituation" > <xs:annotation> <xs:appinfo> other (1) unknown (2) calm (3) light breeze (4) moderate breeze (5) strong breeze (6) gale (7) moderate gale (8) strong gale (9) storm winds (10) hurricane force winds (11) gusty winds (12) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="12"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="other"/> <xs:enumeration value="unknown"/> <xs:enumeration value="calm"/> <xs:enumeration value="light breeze"/> <xs:enumeration value="moderate breeze"/> <xs:enumeration value="strong breeze"/> <xs:enumeration value="gale"/> <xs:enumeration value="moderate gale"/> <xs:enumeration value="strong gale"/> <xs:enumeration value="storm winds"/> <xs:enumeration value="hurricane force winds"/> <xs:enumeration value="gusty winds"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:complexType name="Filters" > <xs:sequence> <xs:element name="dms-status-information" > <xs:simpleType> <xs:restriction base="xs:boolean"/> </xs:simpleType> </xs:element> <xs:element name="ess-status-information" > <xs:simpleType> <xs:restriction base="xs:boolean"/> </xs:simpleType> </xs:element> </xs:sequence>

137

</xs:complexType> <xs:simpleType name="FreeText" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="500"/> </xs:restriction></xs:simpleType> <xs:complexType name="Height" > <xs:choice> <xs:element name="altdatum" > <xs:complexType> <xs:sequence> <xs:element name="altitude" type="Distance" /> <xs:element name="verticalDatum" type="VerticalDatum" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="verticalLevel" type="VerticalLevel" /> </xs:choice></xs:complexType> <xs:simpleType name="HorizontalDatum" > <xs:annotation> <xs:appinfo> wgs 84 (0) wgs 84egm 96 (1) nad83 (2) nad27 (3) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="wgs 84"/> <xs:enumeration value="wgs 84egm 96"/> <xs:enumeration value="nad83"/> <xs:enumeration value="nad27"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="InformationalText" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="255"/> </xs:restriction></xs:simpleType> 

138

<xs:complexType name="IntersectionDevicesSummary" > <xs:sequence> <xs:element name="signalControlInformation" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="signalControlInformation-item" type="SignalControlInventory" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="timing-plans" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="255"> <xs:element name="timing-plan" type="TimingPlan" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="detectors" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="detector" type="DetectorDetails" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="schedule-plans" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="schedule-plan" type="Schedule-entry" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="maxOverlaps" type="MaxOverlaps" /> <xs:element name="overlaps" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="overlap" type="Overlap" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="rampMeters" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="rampMeter" type="RampMeterInventory" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType> <xs:simpleType name="Intersection-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:complexType name="IntersectionSummaryStatus" > <xs:sequence> <xs:element name="primaryDevice" type="SignalControlInventory" /> <xs:element name="currentTimingPlan" type="TimingPlan" />

139

<xs:element name="detectors" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="detector" type="DetectorDetails" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="rampMeters" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="rampMeter" type="RampMeterStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="specialFuntions" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="specialFuntion" type="Special-function" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType> <xs:simpleType name="Latitude" > <xs:restriction base="xs:int"> <xs:minInclusive value="-90000000"/> <xs:maxInclusive value="90000000"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Link-direction" > <xs:annotation> <xs:appinfo> any other (0) n (1) ne (2) e (3) se (4) s (5) sw (6) w (7) nw (8) not directional (9) positive direction (10) negative direction (11) both directions (12) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="12"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="any other"/> <xs:enumeration value="n"/>

140

<xs:enumeration value="ne"/> <xs:enumeration value="e"/> <xs:enumeration value="se"/> <xs:enumeration value="s"/> <xs:enumeration value="sw"/> <xs:enumeration value="w"/> <xs:enumeration value="nw"/> <xs:enumeration value="not directional"/> <xs:enumeration value="positive direction"/> <xs:enumeration value="negative direction"/> <xs:enumeration value="both directions"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="Link-route-designator" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="64"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Longitude" > <xs:restriction base="xs:int"> <xs:minInclusive value="-180000000"/> <xs:maxInclusive value="180000000"/> </xs:restriction></xs:simpleType> <xs:simpleType name="MaxOverlaps" > <xs:restriction base="xs:unsignedByte"> <xs:maxInclusive value="100"/> </xs:restriction></xs:simpleType> <xs:simpleType name="MaxPhases" > <xs:restriction base="xs:unsignedByte"/></xs:simpleType> <xs:simpleType name="Meter-status" > <xs:annotation> <xs:appinfo> off (0) green (1) red (2) yellow (3) flashing (4) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="4"/> </xs:restriction> </xs:simpleType> <xs:simpleType>

141

<xs:restriction base="xs:string"> <xs:enumeration value="off"/> <xs:enumeration value="green"/> <xs:enumeration value="red"/> <xs:enumeration value="yellow"/> <xs:enumeration value="flashing"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="Organization-center-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Organization-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:complexType name="OrganizationInformationLong" > <xs:sequence> <xs:element name="organization-id" type="Organization-identifier" /> <xs:element name="organization-name" type="Organization-name" /> <xs:element name="organization-sub-name" type="Organization-sub-organization-name" minOccurs="0"/> <xs:element name="contactDetails" type="ContactDetails" /> </xs:sequence></xs:complexType> <xs:complexType name="OrganizationInformationShort" > <xs:sequence> <xs:element name="organization-id" type="Organization-identifier" /> <xs:element name="organization-name" type="Organization-name" /> </xs:sequence></xs:complexType> <xs:simpleType name="Organization-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Organization-sub-organization-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> 

142

<xs:complexType name="Overlap" > <xs:sequence> <xs:element name="number" > <xs:simpleType> <xs:restriction base="xs:unsignedShort"/> </xs:simpleType> </xs:element> <xs:element name="description" type="FreeText" /> </xs:sequence></xs:complexType> <xs:simpleType name="PatternCycleTime" > <xs:restriction base="xs:unsignedByte"/></xs:simpleType> <xs:simpleType name="PatternOffsetTime" > <xs:restriction base="xs:unsignedByte"/></xs:simpleType> <xs:complexType name="Phase" > <xs:sequence> <xs:element name="phaseNumber" type="PhaseNumber" /> <xs:element name="phase-Signal-State" type="Phase-Signal-State" /> <xs:element name="movment" type="FreeText" /> <xs:element name="splitPhase" type="SplitPhase" /> <xs:element name="splitTime" type="SplitTime" /> </xs:sequence></xs:complexType> <xs:complexType name="Phase-details" > <xs:sequence minOccurs="1" maxOccurs="255"> <xs:element name="phase-detail" type="Phase" /> </xs:sequence></xs:complexType> <xs:simpleType name="PhaseNumber" > <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Phase-Signal-State" > <xs:annotation> <xs:appinfo> green (0) red (1) yellow (2) flashing red (3) flashing yellow (4) off (5) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="5"/>

143

</xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="green"/> <xs:enumeration value="red"/> <xs:enumeration value="yellow"/> <xs:enumeration value="flashing red"/> <xs:enumeration value="flashing yellow"/> <xs:enumeration value="off"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="Ramp-current-state" > <xs:annotation> <xs:appinfo> open (1) closed (2) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> <xs:maxInclusive value="2"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="open"/> <xs:enumeration value="closed"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="Ramp-exit-roadway-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Ramp-lane-number" > <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/> <xs:maxInclusive value="50"/> </xs:restriction></xs:simpleType> <xs:complexType name="RampMeterControl" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="meter-status" type="Meter-status" /> <xs:element name="ramp-current-state" type="Ramp-current-state" /> <xs:element name="volume-data" type="Volume-data" /> <xs:element name="special-functions-ON" >

144

<xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="special-functions-ON-item" type="Special-function" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="special-functions-OFF" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="special-functions-OFF-item" type="Special-function" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType> <xs:complexType name="RampMeterInventory" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="link-direction" type="Link-direction" /> <xs:element name="device-latitude" type="Latitude" /> <xs:element name="device-longitude" type="Longitude" /> <xs:element name="ramp-lane-number" type="Ramp-lane-number" minOccurs="0"/> </xs:sequence></xs:complexType> <xs:element name="rampMeterStatus" type="RampMeterStatus"/><xs:complexType name="RampMeterStatus" > <xs:sequence> <xs:element name="meter-status" type="Meter-status" /> <xs:element name="volume-data" type="Volume-data" /> </xs:sequence></xs:complexType> <xs:simpleType name="ReturnAddress" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:complexType name="Schedule-entry" > <xs:sequence> <xs:element name="startTime" type="DateTimePair" /> <xs:element name="stopTime" type="DateTimePair" /> <xs:element name="eventID" type="TimingPlan-identifier" /> </xs:sequence></xs:complexType> <xs:simpleType name="Section-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType>

145

<xs:simpleType name="Security-password" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Security-user-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:complexType name="SignalControlInventory" > <xs:sequence> <xs:element name="intersection-name" type="Intersection-name" minOccurs="0"/> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="device-latitude" type="Latitude" /> <xs:element name="device-longitude" type="Longitude" /> <xs:element name="section-identifier" type="Section-identifier" minOccurs="0"/> <xs:element name="zone-identifier" type="Section-identifier" minOccurs="0"/> <xs:element name="controller-Time" type="DateTimePair" /> <xs:element name="central-Time" type="DateTimePair" /> <xs:element name="current-UTC-Time" type="DateTimePair" /> <xs:element name="battPercent" > <xs:simpleType> <xs:restriction base="xs:unsignedByte"> <xs:maxInclusive value="100"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="special-functions" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="special-function" type="Special-function" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="controller-log-entries" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="64"> <xs:element name="controller-log-entry" type="Controller-log-entry" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence></xs:complexType> <xs:complexType name="Special-function" > <xs:sequence> <xs:element name="function-output-number" > <xs:simpleType> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/>

146

<xs:maxInclusive value="8"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="function-meaning" type="SpecialFunctionList" /> </xs:sequence></xs:complexType> <xs:simpleType name="SpecialFunctionList" > <xs:annotation> <xs:appinfo> itemOne (0) itemTwo (1) -- add any comments here itemThree (2) itemFour (3) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="itemOne"/> <xs:enumeration value="itemTwo"/> <xs:enumeration value="itemThree"/> <xs:enumeration value="itemFour"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="SplitPhase" > <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="1"/> </xs:restriction></xs:simpleType> <xs:simpleType name="SplitTime" > <xs:restriction base="xs:unsignedByte"/></xs:simpleType> <xs:complexType name="SubscriptionAction" > <xs:sequence minOccurs="1" maxOccurs="10"> <xs:element name="subscriptionAction-item" type="SubscriptionActionItem" /> </xs:sequence></xs:complexType> <xs:simpleType name="SubscriptionActionItem" > <xs:annotation> <xs:appinfo> reserved (0) newSubscription (1) replaceSubscription (2) cancelSubscription (3)

147

cancelAllPriorSubscriptions (4) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="4"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="reserved"/> <xs:enumeration value="newSubscription"/> <xs:enumeration value="replaceSubscription"/> <xs:enumeration value="cancelSubscription"/> <xs:enumeration value="cancelAllPriorSubscriptions"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="SubscriptionCount" > <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> </xs:restriction></xs:simpleType> <xs:simpleType name="SubscriptionFrequency" > <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="1"/> </xs:restriction></xs:simpleType> <xs:simpleType name="SubscriptionID" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:simpleType name="SubscriptionName" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:complexType name="SubscriptionTimeFrame" > <xs:sequence> <xs:element name="start" type="DateTimePair" /> <xs:element name="end" type="DateTimePair" /> </xs:sequence></xs:complexType> <xs:complexType name="SubscriptionType" > <xs:sequence minOccurs="1" maxOccurs="10">

148

<xs:element name="subscriptionType-item" type="SubscriptionTypeItem" /> </xs:sequence></xs:complexType> <xs:simpleType name="SubscriptionTypeItem" > <xs:annotation> <xs:appinfo> reserved (0) oneTime (1) periodic (2) onChange (3) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="reserved"/> <xs:enumeration value="oneTime"/> <xs:enumeration value="periodic"/> <xs:enumeration value="onChange"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="Time"> <xs:restriction base="xs:time"/></xs:simpleType> <xs:simpleType name="TimeInterval"> <xs:restriction base="xs:duration"/></xs:simpleType> <xs:complexType name="TimingPlan" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="intersection-name" type="Intersection-name" minOccurs="0"/> <xs:element name="timing-plan-id" type="TimingPlan-identifier" minOccurs="0"/> <xs:element name="timing-plan-name" type="TimingPlan-name" minOccurs="0"/> <xs:element name="cycle-time" type="PatternCycleTime" minOccurs="0"/> <xs:element name="offset-time" type="PatternOffsetTime" minOccurs="0"/> </xs:sequence></xs:complexType> <xs:element name="timingPlanDetailResponse-AZTech" type="TimingPlanDetailResponse-AZTech"/><xs:complexType name="TimingPlanDetailResponse-AZTech" > <xs:sequence> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="center-id" type="Organization-center-identifier" />

149

<xs:element name="plans" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="255"> <xs:element name="plan" type="TimingPlan" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="maxPhases" type="MaxPhases" /> <xs:element name="phase-details" type="Phase-details" /> </xs:sequence></xs:complexType> <xs:simpleType name="TimingPlan-identifier" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="32"/> </xs:restriction></xs:simpleType> <xs:simpleType name="TimingPlan-name" > <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="128"/> </xs:restriction></xs:simpleType> <xs:element name="tMSControlRequest-AZTech" type="TMSControlRequest-AZTech"/><xs:complexType name="TMSControlRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="device-id" type="Device-identifier" /> <xs:element name="request-id" type="Device-request-identifier" /> <xs:element name="timing-plan-id" type="TimingPlan-identifier" /> <xs:element name="command-request-priority" type="Device-command-request-priority" /> <xs:element name="command-start-time" type="DateTimePair" /> <xs:element name="command-end-time" type="DateTimePair" /> <xs:element name="rampMeterControl-req" type="RampMeterControl" minOccurs="0"/> <xs:element name="special-functions-req" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="8"> <xs:element name="special-functions-req-item" type="Special-function" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType> <xs:element name="tMSInformationResponse-AZTech" type="TMSInformationResponse-AZTech"/><xs:complexType name="TMSInformationResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" />

150

<xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="intersections" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="intersection" type="IntersectionDevicesSummary" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="freeText" type="FreeText" /> </xs:sequence></xs:complexType> <xs:element name="tMSInformationTimingPlanDetailRequest-AZTech" type="TMSInformationTimingPlanDetailRequest-AZTech"/><xs:complexType name="TMSInformationTimingPlanDetailRequest-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="100000"> <xs:element name="device" type="Device-identifier" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType> <xs:element name="tMSInventoryPublication-AZTech" type="TMSInventoryPublication-AZTech"/><xs:complexType name="TMSInventoryPublication-AZTech" > <xs:sequence> <xs:element name="c2cMessagePublication" type="C2cMessagePublication" /> <xs:element name="signalControlInventory" type="TMSInventoryResponse-AZTech" /> </xs:sequence></xs:complexType> <xs:element name="tMSInventoryResponse-AZTech" type="TMSInventoryResponse-AZTech"/><xs:complexType name="TMSInventoryResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationLong" /> <xs:element name="organization-requesting" type="OrganizationInformationShort" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="intersections" > <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="10000"> <xs:element name="intersection" type="IntersectionDevicesSummary" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence></xs:complexType>

151

<xs:element name="tMSStatusPublication-AZTech" type="TMSStatusPublication-AZTech"/><xs:complexType name="TMSStatusPublication-AZTech" > <xs:sequence> <xs:element name="c2cMessagePublication" type="C2cMessagePublication" /> <xs:element name="deviceStatus" type="TMSStatusResponse-AZTech" /> </xs:sequence></xs:complexType> <xs:element name="tMSStatusResponse-AZTech" type="TMSStatusResponse-AZTech"/><xs:complexType name="TMSStatusResponse-AZTech" > <xs:sequence> <xs:element name="organization-owning" type="OrganizationInformationShort" /> <xs:element name="organization-requesting" type="OrganizationInformationLong" /> <xs:element name="authorization" type="AuthorizationSet" /> <xs:element name="devices" > <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="100"> <xs:element name="device" type="IntersectionSummaryStatus" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="request-id" type="Device-request-identifier" /> </xs:sequence></xs:complexType> <xs:simpleType name="VerticalDatum" > <xs:annotation> <xs:appinfo> wgs 84 (0) navd (1) </xs:appinfo> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedInt"> <xs:minInclusive value="0"/> <xs:maxInclusive value="1"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="wgs 84"/> <xs:enumeration value="navd"/> </xs:restriction> </xs:simpleType > </xs:union></xs:simpleType> <xs:simpleType name="VerticalLevel" > <xs:restriction base="xs:byte"> <xs:minInclusive value="-127"/> </xs:restriction></xs:simpleType> <xs:simpleType name="Volume-data" > <xs:restriction base="xs:unsignedShort"/></xs:simpleType>

152

<xs:complexType name="xxx"/> 



<xs:simpleType name="binary"> <xs:restriction base="xs:string"> <xs:pattern value="[01]*"/> </xs:restriction></xs:simpleType>

<xs:simpleType name="OctetStringOptions"> <xs:union memberTypes="xs:hexBinary xs:base64Binary"/> </xs:simpleType> <xs:complexType name="OctetString"> <xs:simpleContent> <xs:extension base="OctetStringOptions"> <xs:attribute name="EncodingType" use="required"> <xs:simpleType> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="hexBinary"/> <xs:enumeration value="base64Binary"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:extension> </xs:simpleContent></xs:complexType>

<xs:simpleType name="NumericString"> <xs:restriction base="xs:string"> <xs:pattern value="\d*"/> </xs:restriction></xs:simpleType>

</xs:schema>

153


154