(None-Data) - Apache Kafka over Wireless

Description

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.

Includes Standards

LevelDocNumFullNameDescription
MgmtApache ZookeeperApache ZookeeperZooKeeper 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.
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 Entity Standard(s) need to be developedOne or more standards need to be developed for this subject matter before this is considered a complete solution.
FacilitiesApache ZookeeperApache ZookeeperZooKeeper 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.
FacilitiesApache KafkaApache KafkaKafka 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 developedOne or more standards need to be developed for this subject matter before this is considered a complete solution.
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: Lowest

Readiness Description

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.

Issues

IssueSeverityDescriptionAssociated StandardAssociated Triple
Data profile not definedUltraPerformance, functionality, and the upper–layers of the OSI stack have not been defined for this information flow.(None)(All)
Unvetted by communityMediumThe proposed solution uses a suite of standards that is accepted within some communities, but has not necessarily been accepted for use within the context of this information triple.(None)(All)
Overlap of standards (Minor)LowMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. However, as this information transfer is infrastructure–based, agencies can deploy a solution throughout their jurisdiction with minimal downside and can use gateways to connect to other technologies.(None)(All)

Supports Interfaces

SourceDestinationFlow
METRO RTA Fixed–Route DispatchPersonal Information Devicetransfer status
METRO RTA Paratransit DispatchPersonal Information Devicetransfer status
Ohio Smart Mobility ProgramPersonal Information Deviceshared use response
PARTA Fixed–Route DispatchPersonal Information Devicetransfer status
PARTA Paratransit DispatchPersonal Information Devicetransfer status
Personal Information DeviceMETRO RTA Fixed–Route Dispatchtrip confirmation
Personal Information DeviceMETRO RTA Paratransit Dispatchtrip confirmation
Personal Information DeviceODOT 511 Telephone Information Serviceuser profile
Personal Information DeviceOhio Smart Mobility Programshared use confirmation
Personal Information DeviceOhio Smart Mobility Programtrip confirmation
Personal Information DeviceOhio Smart Mobility Programtrip feedback
Personal Information DeviceOhio Smart Mobility Programuser profile
Personal Information DevicePARTA Fixed–Route Dispatchtrip confirmation
Personal Information DevicePARTA Paratransit Dispatchtrip confirmation
Personal Information DeviceUniversity of Akron Roo Express Dispatch Centertrip confirmation