| 3.1 | 3.1 - Provide DMS Control to Remote Agencies | | TOC | |
| 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 |
| 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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 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. | MSG | MSG_DeviceCancelControlRequest-AZTech |
| 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: | 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 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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 3.2 | 3.2 - Provide DMS Inventory Information | | TOC | |
| 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. | MSG | MSG_DeviceInventorySubscription-AZTech |
| 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: | 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 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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 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 | | |
| | | · 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. | MSG | MSG_DeviceInventoryRequest-AZTech |
| 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 | | |
| | | · 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 | 3.3 - Provide DMS Status Information | | TOC | |
| 3.3.a | 3.3 - Provide DMS Status Information | | DL | DL_DMSStatusRequest |
| 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: | MSG | MSG_DeviceStatusRequest-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.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. | MSG | MSG_DMSStatusResponse-AZTech |
| 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 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: | 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 subscription service ID | | |
| 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. | MSG | MSG_DMSStatusResponse-AZTech |
| | | | | |
| 3.4 | 3.4 - Provide Environmental Sensor Information | | TOC | |
| 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: | MSG | MSG_DeviceStatusRequest-AZTech |
| | | · 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 | | |
| 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. | MSG | MSG_DeviceStatusRequest-AZTech |
| 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 | 3.5 - DMS Archive Status Information Subscription | | TOC | |
| 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 | | |
| | | · 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. | MSG | MSG_DeviceArchiveStatusSubscription-AZTech |
| 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: | 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 subscription service ID | | |
| 3.5.4 | 3.5.4 - Receive DMS Archive Status Information Response | The remote center shall be capable of receiving a response to a DMS archive status information subscription. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 3.6 | 3.6 - Provide Subscription Cancellation | | TOC | |
| 3.6.a | 3.6 - Provide Subscription Cancellation | | DL | DL_CancelSubscriptionRequest |
| 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. | MSG | MSG_CancelSubscriptionRequest-AZTech |
| 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: | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| | | · 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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 4.1 | 4.1 - Provide TMS Inventory to Remote Agencies | | TOC | |
| 4.1.a | 4.1 - Provide TMS Inventory to Remote Agencies | | DL | DL_TMSInventoryUpdateSubscriptionPublication |
| 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. | MSG | MSG_DeviceInventorySubscription-AZTech |
| | | 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. | MSG | MSG_DeviceInventorySubscription-AZTech |
| 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: | 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 subscription service ID | | |
| 4.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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 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 function | | |
| 4.1.6 | 4.1.6 - Receive TMS Inventory Update | The remote center shall be capable of receiving a TMS inventory update message. | MSG | MSG_TMSInventoryPublication-AZTech |
| 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: | MSG | MSG_DeviceInventoryRequest-AZTech |
| | | · 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. | MSG | MSG_DeviceInventoryRequest-AZTech |
| 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. | MSG | MSG_TMSInventoryResponse-AZTech |
| 4.2 | 4.2 - Provide Intersection Information to Remote Agencies | | TOC | |
| 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: | MSG | MSG_DeviceInventoryRequest-AZTech |
| | | · 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. | MSG | MSG_DeviceInventoryRequest-AZTech |
| 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: | 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 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) | | |
| | | · 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. | MSG | MSG_TMSInventoryResponse-AZTech |
| 4.3 | 4.3 - Provide Timing Plan Details to Remote Agencies | | TOC | |
| 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 |
| | | · 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 | 4.4 - Provide Intersection Control to Remote Agencies | | | |
| 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 | | |
| | | · 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/comments | | |
| 4.4.2 | 4.4.2 - Receive Intersection Control Request | The 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: | 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 | | |
| 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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 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: | MSG | MSG_DeviceCancelControlRequest-AZTech |
| | | · 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. | MSG | MSG_DeviceCancelControlRequest-AZTech |
| | | 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: | 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 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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 4.5 | 4.5 - Provide Intersection Status to Remote Agencies | | TOC | |
| 4.5.a | 4.5 - Provide Intersection Status to Remote Agencies | | DL | DL_TMSStatusRequest |
| 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: | MSG | MSG_DeviceStatusRequest-AZTech |
| | | · 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. | MSG | MSG_DeviceStatusRequest-AZTech |
| 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 | | |
| | | | | |
| | | (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 | 4.6 -TMS Archive Status Information Subscription | | | |
| 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: | 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 | | |
| | | · 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. | MSG | MSG_DeviceArchiveStatusSubscription-AZTech |
| 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: | 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 subscription service ID | | |
| 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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| 4.7 | 4.7 - Provide Subscription Cancellation | | TOC | |
| 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: | 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 | | |
| 4.7.2 | 4.7.2 - Receive Subscription Cancellation Request | The local center shall be capable of accepting and processing valid subscription cancellation requests. | MSG | MSG_CancelSubscriptionRequest-AZTech |
| 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: | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |
| | | · 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 | | |
| 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. | MSG | MSG_DeviceControlSubscriptionResponse-AZTech |