US: TCIP - Secure Wireless Internet (ITS)

Description

This solution is used within the U.S.. It combines standards associated with US: TCIP with those for I–M: Secure Wireless Internet (ITS). The US: TCIP standards include upper–layer standards required to implement transit–related 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.

Includes Standards

LevelDocNumFullNameDescription
MgmtIETF RFC 3411An Architecture for Describing Simple Network Management Protocol (SNMP) Management FrameworksThis standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture.
MgmtIETF RFC 3412Message 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.
MgmtIETF RFC 3413Simple Network Management Protocol (SNMP) ApplicationsThis standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys.
MgmtIETF RFC 3414User–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.
MgmtIETF RFC 3415View–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.
MgmtIETF RFC 3416Version 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.
MgmtIETF RFC 3418Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)This standard (RFC) defines the MIB to configure and manage an SNMP entity.
MgmtIETF RFC 4293Management Information Base for the Internet Protocol (IP)This standard (RFC) defines the MIB that manages an IP entity.
SecurityIETF RFC 5280Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileThis standard (RFC) defines how to use X.509 certificates for secure communications over the Internet.
SecurityIETF RFC 8446The Transport Layer Security (TLS) ProtocolThis 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 EntityAPTA TCIP–S–001 Vol 2Transit Communications Interface Profiles – TCIP Data and Dialog DefinitionsThis standard defines the data concepts used by the TCIP standard.
FacilitiesW3C XMLExtensible 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.
FacilitiesAPTA TCIP–S–001 Vol 2Transit Communications Interface Profiles – TCIP Data and Dialog DefinitionsThis standard defines the data concepts used by the TCIP standard.
TransNetIETF RFC 2460Internet Protocol, Version 6 (IPv6) SpecificationThis standard (RFC) specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng.
TransNetIETF RFC 4291IP Version 6 Addressing ArchitectureThis 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.
TransNetIETF RFC 4443Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationThis standard (RFC) defines the control messages to manage IPv6.
TransNetIETF RFC 793Transmission Control ProtocolThis standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks.
Access3GPP Network3GPP Cellular Communications NetworkThis 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.

Readiness: Moderate–Low

Readiness Description

Multiple significant and minor issues.  For existing deployments, the chosen solution is likely deficient in security or management capabilities, and the issues should be reviewed and upgrades developed as needed. Some solutions in this category may also be becoming obsolete from an interoperability perspective and if this is the case, then upgrades should be planned as soon as possible. For new deployments, the solution may be viable for pilots when applied to the triples it supports; such pilot deployments should consider a path to addressing these issues as a part of their design activities. The solution does not provide sufficient interoperability, management, and security to enable proper, full–scale deployment without  additional work.

Issues

IssueSeverityDescriptionAssociated StandardAssociated Triple
Encoding rules not definedHighThe standards do not unambiguously define which set of encoding rules to use.(None)(All)
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Bowling Green Transit Dispatch=>transit vehicle operator information=>Bowling Green Transit Vehicles
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Independent School District Dispatch=>transit vehicle operator information=>Independent School District Buses
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TARTA Dispatch=>transit vehicle operator information=>TARTA Fixed Route Vehicles
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TARPS Dispatch=>transit vehicle operator information=>TARPS Paratransit Vehicles
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Bowling Green State University Shuttle Fixed Route Dispatch=>transit vehicle operator information=>Bowling Green State University Shuttle Vehicles
Out of date (medium)MediumThe standard includes normative references to other standards that have been subject to significant changes that can impact interoperability or security of systems and the industry has not specified if and how these updates should be implemented for deployments of this standard.TCIP – Data(All)
Secure data access not providedMediumThe solution does not define rules on how the application entity authenticates requests to accept or provide data.(None)(All)
Data not defined in standard formatLowThe definition of data concepts should conform to ISO 14817–1 to promote reuse among ITS.TCIP – Data(All)

Supports Interfaces

SourceDestinationFlow
Bowling Green State University Shuttle Fixed Route DispatchBowling Green State University Shuttle Vehiclesconnection protection instructions
Bowling Green State University Shuttle Fixed Route DispatchBowling Green State University Shuttle Vehiclestransit vehicle operator information
Bowling Green State University Shuttle VehiclesBowling Green State University Shuttle Fixed Route Dispatchtransit vehicle conditions
Bowling Green State University Shuttle VehiclesBowling Green State University Shuttle Fixed Route Dispatchtransit vehicle loading data
Bowling Green Transit DispatchBowling Green Transit Vehiclesconnection protection instructions
Bowling Green Transit DispatchBowling Green Transit Vehiclestransit vehicle operator information
Bowling Green Transit VehiclesBowling Green Transit Dispatchdemand response passenger and use data
Bowling Green Transit VehiclesBowling Green Transit Dispatchtransit vehicle loading data
Independent School District BusesIndependent School District Dispatchtransit vehicle conditions
Independent School District DispatchIndependent School District Busestransit vehicle operator information
TARPS DispatchTARPS Paratransit Vehiclesalarm acknowledge
TARPS DispatchTARPS Paratransit Vehiclesconnection protection instructions
TARPS DispatchTARPS Paratransit Vehiclestransit vehicle operator information
TARPS Paratransit VehiclesTARPS Dispatchalarm notification
TARPS Paratransit VehiclesTARPS Dispatchdemand response passenger and use data
TARPS Paratransit VehiclesTARPS Dispatchtransit vehicle loading data
TARPS Paratransit VehiclesTARPS Maintenance Garagetransit vehicle conditions
TARTA Central GarageTARTA Fixed Route Vehiclesalarm acknowledge
TARTA DispatchTARTA Fixed Route Vehiclesalarm acknowledge
TARTA DispatchTARTA Fixed Route Vehiclesconnection protection instructions
TARTA DispatchTARTA Fixed Route Vehiclesfare management information
TARTA DispatchTARTA Fixed Route Vehiclestransit vehicle operator information
TARTA Fixed Route VehiclesTARTA Central Garagealarm notification
TARTA Fixed Route VehiclesTARTA Central Garagetransit vehicle conditions
TARTA Fixed Route VehiclesTARTA Dispatchalarm notification
TARTA Fixed Route VehiclesTARTA Dispatchfare collection data
TARTA Fixed Route VehiclesTARTA Dispatchtransit vehicle loading data