This solution is used within the U.S.. It combines standards associated with US: ATIS with those for I–M: Secure Wireless Internet (ITS). The US: ATIS standards include upper–layer standards required to implement traveler information communications. The I–M: Secure Wireless Internet (ITS) standards include lower–layer standards that support secure communications between two entities, either or both of which may be mobile devices, but they must be stationary or only moving within wireless range of a single wireless access point (e.g., a parked car). Security is based on X.509 or IEEE 1609.2 certificates. A non–mobile (if any) endpoint may connect to the service provider using any Internet connection method.
| Level | DocNum | FullName | Description |
|---|
| Mgmt | IETF RFC 3411 | An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks | This standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture. |
|---|
| Mgmt | IETF RFC 3412 | Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) | This standard (RFC) contains a MIB that assists in managing the message processing and dispatching subsystem of an SNMP entity. |
|---|
| Mgmt | IETF RFC 3413 | Simple Network Management Protocol (SNMP) Applications | This standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys. |
|---|
| Mgmt | IETF RFC 3414 | User–based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) | This standard (RFC) contains a MIB that assists in configuring and managing the user–based security model. |
|---|
| Mgmt | IETF RFC 3415 | View–based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) | This standard (RFC) contains a MIB that supports the configuration and management of the View–based access control model of SNMP. |
|---|
| Mgmt | IETF RFC 3416 | Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP) | This standard (RFC) defines the message structure and protocol operations used by SNMPv3. |
|---|
| Mgmt | IETF RFC 3418 | Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) | This standard (RFC) defines the MIB to configure and manage an SNMP entity. |
|---|
| Mgmt | IETF RFC 4293 | Management Information Base for the Internet Protocol (IP) | This standard (RFC) defines the MIB that manages an IP entity. |
|---|
| Security | IETF RFC 5280 | Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile | This standard (RFC) defines how to use X.509 certificates for secure communications over the Internet. |
|---|
| Security | IETF RFC 8446 | The Transport Layer Security (TLS) Protocol | This standard (RFC) specifies Version 1.3 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. |
|---|
| ITS Application Entity | SAE J2353 | Data Dictionary for Advanced Traveler Information Systems (ATIS) | This document provides a set of core data elements needed by information service providers for Advanced Traveler Information Systems (ATIS). The data dictionary herein provides the foundation for ATIS message sets for all stages of travel (pre–trip and en route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in–vehicle, portable devices, kiosks, etc.). The elements of this document are the basis for the SAE ATIS Message Set Standard J2354 and are entered into the SAE Data Registry for ITS wide coordination. |
|---|
| Facilities | IETF RFC 7230 | Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing | This standard (RFC) defines the main Application Layer protocol used for the world–wide web. |
|---|
| Facilities | W3C XML | Extensible Markup Language (XML) 1.0 (Fifth Edition) | This standard defines a generic markup language that can be used to share customizable information by using start and stop tags within the text. |
|---|
| Facilities | SAE J2354 | Message Sets for Advanced Traveler Information System (ATIS) | This standard defines how to exchange data for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (pre–trip and en–route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in–vehicle, portable devices, kiosks, etc.). |
|---|
| TransNet | IETF RFC 2460 | Internet Protocol, Version 6 (IPv6) Specification | This standard (RFC) specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. |
|---|
| TransNet | IETF RFC 4291 | IP Version 6 Addressing Architecture | This standard (RFC) defines the addressing architecture of the IP Version 6 (IPv6) protocol. It includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. |
|---|
| TransNet | IETF RFC 4443 | Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification | This standard (RFC) defines the control messages to manage IPv6. |
|---|
| TransNet | IETF RFC 793 | Transmission Control Protocol | This standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks. |
|---|
| Access | 3GPP Network | 3GPP Cellular Communications Network | This proxy standard represents a variety of 3GPP releases and underlying standards and technologies that rely upon cellular base stations for connectivity, including 3G, 4G, and the emerging 5G technologies. |
|---|
One serious or several significant issues. This category often includes proprietary or partial solutions. The communications solution may fail to provide even a base level of interoperability and security. Consider alternative solutions, or define specific revisions or upgrades that would provide a level of interoperability or security that are needed for the deployment.
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|
| Encoding rules not defined | High | The standards do not unambiguously define which set of encoding rules to use. | (None) | (All) |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>ODOT 511 Telephone Information Service |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>DriveAkron |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>City of Green Traffic Information Website |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>PARTA Website |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>trip request=>PARTA Website |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>METRO RTA Website |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>trip request=>METRO RTA Website |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | METRO RTA Fixed–Route Dispatch=>trip plan=>Personal Information Device |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>ODOT OHGO Traveler Information System |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>City of Akron Parking App |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | PARTA Paratransit Dispatch=>trip plan=>Personal Information Device |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | PARTA Website=>trip plan=>Personal Information Device |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | PARTA Fixed–Route Dispatch=>trip plan=>Personal Information Device |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | METRO RTA Paratransit Dispatch=>trip plan=>Personal Information Device |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | METRO RTA Website=>trip plan=>Personal Information Device |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>OTIC Website |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>Other City Traffic Information Websites |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>Summit County Engineer Website |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | University of Akron Roo Express Dispatch Center=>trip plan=>Personal Information Device |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>Portage County Website |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>trip request=>Ohio Smart Mobility Program |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>ODOT Rest Area Tourist Information Centers |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>Akron–Canton Airport |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>City of Hudson Parking App |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Personal Information Device=>traveler request=>City of Cuyahoga Falls Parking App |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Ohio Smart Mobility Program=>trip plan=>Personal Information Device |
|---|
| Exception handling not defined | Medium | The dialogs do not define how to handle exceptions (e.g., error codes, permission denied, etc). | (None) | (All) |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | METRO RTA Website=>trip plan=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | PARTA Website=>trip plan=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Ohio Smart Mobility Program=>trip plan=>Personal Information Device |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | (All) |
|---|
| Secure data access not provided | Medium | The solution does not define rules on how the application entity authenticates requests to accept or provide data. | (None) | (All) |
|---|
| Data not defined in standard format | Low | The definition of data concepts should conform to ISO 14817–1 to promote reuse among ITS. | SAE J2353 ATIS DD | (All) |
|---|
| Source | Destination | Flow |
|---|
| Akron–Canton Airport | Commercial Vehicles | interactive traveler information |
|---|
| Akron–Canton Airport | Personal Information Device | interactive traveler information |
|---|
| City of Akron Parking App | Personal Information Device | interactive traveler information |
|---|
| City of Cuyahoga Falls Parking App | Personal Information Device | interactive traveler information |
|---|
| City of Green Traffic Information Website | Commercial Vehicles | interactive traveler information |
|---|
| City of Green Traffic Information Website | Personal Information Device | interactive traveler information |
|---|
| City of Green Traffic Information Website | Personal Information Device | travel services information |
|---|
| City of Hudson Parking App | Personal Information Device | interactive traveler information |
|---|
| Commercial Vehicles | Akron–Canton Airport | traveler request |
|---|
| Commercial Vehicles | City of Green Traffic Information Website | traveler request |
|---|
| Commercial Vehicles | DriveAkron | traveler request |
|---|
| Commercial Vehicles | ODOT OHGO Traveler Information System | traveler request |
|---|
| Commercial Vehicles | Other City Traffic Information Websites | traveler request |
|---|
| Commercial Vehicles | OTIC Website | traveler request |
|---|
| Commercial Vehicles | Portage County Website | traveler request |
|---|
| Commercial Vehicles | Summit County Engineer Website | traveler request |
|---|
| Connected/Automated Vehicles | City of Green Traffic Information Website | traveler request |
|---|
| Connected/Automated Vehicles | DriveAkron | traveler request |
|---|
| Connected/Automated Vehicles | Other City Traffic Information Websites | traveler request |
|---|
| Connected/Automated Vehicles | Portage County Website | traveler request |
|---|
| Connected/Automated Vehicles | Summit County Engineer Website | traveler request |
|---|
| DriveAkron | Commercial Vehicles | interactive traveler information |
|---|
| DriveAkron | Personal Information Device | interactive traveler information |
|---|
| DriveAkron | Personal Information Device | travel services information |
|---|
| METRO RTA Fixed–Route Dispatch | Personal Information Device | trip plan |
|---|
| METRO RTA Paratransit Dispatch | Personal Information Device | trip plan |
|---|
| METRO RTA Website | Personal Information Device | interactive traveler information |
|---|
| METRO RTA Website | Personal Information Device | trip plan |
|---|
| ODOT 511 Telephone Information Service | Personal Information Device | interactive traveler information |
|---|
| ODOT OHGO Traveler Information System | Commercial Vehicles | interactive traveler information |
|---|
| ODOT OHGO Traveler Information System | Personal Information Device | interactive traveler information |
|---|
| ODOT Rest Area Tourist Information Centers | Personal Information Device | interactive traveler information |
|---|
| Ohio Smart Mobility Program | Personal Information Device | trip plan |
|---|
| Other City Traffic Information Websites | Commercial Vehicles | interactive traveler information |
|---|
| Other City Traffic Information Websites | Personal Information Device | interactive traveler information |
|---|
| Other City Traffic Information Websites | Personal Information Device | travel services information |
|---|
| OTIC Website | Commercial Vehicles | interactive traveler information |
|---|
| OTIC Website | Personal Information Device | interactive traveler information |
|---|
| PARTA Fixed–Route Dispatch | Personal Information Device | trip plan |
|---|
| PARTA Paratransit Dispatch | Personal Information Device | trip plan |
|---|
| PARTA Website | Personal Information Device | interactive traveler information |
|---|
| PARTA Website | Personal Information Device | trip plan |
|---|
| Personal Information Device | Akron–Canton Airport | traveler request |
|---|
| Personal Information Device | City of Akron Parking App | traveler request |
|---|
| Personal Information Device | City of Cuyahoga Falls Parking App | traveler request |
|---|
| Personal Information Device | City of Green Traffic Information Website | travel services request |
|---|
| Personal Information Device | City of Green Traffic Information Website | traveler request |
|---|
| Personal Information Device | City of Hudson Parking App | traveler request |
|---|
| Personal Information Device | DriveAkron | travel services request |
|---|
| Personal Information Device | DriveAkron | traveler request |
|---|
| Personal Information Device | METRO RTA Website | traveler request |
|---|
| Personal Information Device | METRO RTA Website | trip request |
|---|
| Personal Information Device | ODOT 511 Telephone Information Service | traveler request |
|---|
| Personal Information Device | ODOT OHGO Traveler Information System | traveler request |
|---|
| Personal Information Device | ODOT Rest Area Tourist Information Centers | traveler request |
|---|
| Personal Information Device | Ohio Smart Mobility Program | trip request |
|---|
| Personal Information Device | Other City Traffic Information Websites | travel services request |
|---|
| Personal Information Device | Other City Traffic Information Websites | traveler request |
|---|
| Personal Information Device | OTIC Website | traveler request |
|---|
| Personal Information Device | PARTA Website | traveler request |
|---|
| Personal Information Device | PARTA Website | trip request |
|---|
| Personal Information Device | Portage County Website | travel services request |
|---|
| Personal Information Device | Portage County Website | traveler request |
|---|
| Personal Information Device | Summit County Engineer Website | travel services request |
|---|
| Personal Information Device | Summit County Engineer Website | traveler request |
|---|
| Portage County Website | Commercial Vehicles | interactive traveler information |
|---|
| Portage County Website | Personal Information Device | interactive traveler information |
|---|
| Portage County Website | Personal Information Device | travel services information |
|---|
| Summit County Engineer Website | Commercial Vehicles | interactive traveler information |
|---|
| Summit County Engineer Website | Personal Information Device | interactive traveler information |
|---|
| Summit County Engineer Website | Personal Information Device | travel services information |
|---|
| University of Akron Roo Express Dispatch Center | Personal Information Device | trip plan |
|---|