This solution is used within the U.S.. It combines standards associated with (None–Data) with those for Apache Kafka over Wireless. The (None–Data) standards include an unspecified set of standards at the upper layers. The Apache Kafka over Wireless standards include lower–layer open source code that supports data distribution of specific types of data over wireless links.
Level | DocNum | FullName | Description |
---|
Mgmt | Apache Zookeeper | Apache Zookeeper | ZooKeeper is open source software that provides a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these types of services are used in some form or another by distributed applications. Each time they are implemented, a lot of work goes into fixing the bugs and race conditions that are inevitable. |
---|
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 | | Standard(s) need to be developed | One or more standards need to be developed for this subject matter before this is considered a complete solution. |
---|
Facilities | Apache Zookeeper | Apache Zookeeper | ZooKeeper is open source software that provides a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these types of services are used in some form or another by distributed applications. Each time they are implemented, a lot of work goes into fixing the bugs and race conditions that are inevitable. |
---|
Facilities | Apache Kafka | Apache Kafka | Kafka is open source software that provides a distributed streaming platform that can be used to share real–time data among systems. While it was designed as an open–source software product, the documentation for the software includes a specification of the protocol (https://kafka.apache.org/protocol) thereby allowing an independent implementation in theory. |
---|
Facilities | | Standard(s) need to be developed | One or more standards need to be developed for this subject matter before this is considered a complete solution. |
---|
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. |
---|
Many serious issues. This category includes solutions that have not been standardized, or do not have a basic level of interoperability or security. Consider selecting a different communications solution or if this is not possible (eg. a pilot of a new application that has not been standardized), take additional measures to provide an acceptable level of security or interoperability.
Source | Destination | Flow |
---|
METRO RTA Fixed–Route Dispatch | Personal Information Device | transfer status |
---|
METRO RTA Paratransit Dispatch | Personal Information Device | transfer status |
---|
Ohio Smart Mobility Program | Personal Information Device | shared use response |
---|
PARTA Fixed–Route Dispatch | Personal Information Device | transfer status |
---|
PARTA Paratransit Dispatch | Personal Information Device | transfer status |
---|
Personal Information Device | METRO RTA Fixed–Route Dispatch | trip confirmation |
---|
Personal Information Device | METRO RTA Paratransit Dispatch | trip confirmation |
---|
Personal Information Device | ODOT 511 Telephone Information Service | user profile |
---|
Personal Information Device | Ohio Smart Mobility Program | shared use confirmation |
---|
Personal Information Device | Ohio Smart Mobility Program | trip confirmation |
---|
Personal Information Device | Ohio Smart Mobility Program | trip feedback |
---|
Personal Information Device | Ohio Smart Mobility Program | user profile |
---|
Personal Information Device | PARTA Fixed–Route Dispatch | trip confirmation |
---|
Personal Information Device | PARTA Paratransit Dispatch | trip confirmation |
---|
Personal Information Device | University of Akron Roo Express Dispatch Center | trip confirmation |
---|