Traffic Management Center --> Enforcement Center:
lane violation notification

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

lane violation notification (Information Flow): Notification to enforcement agency of detected lane entry violations, lane speed violations, or other dynamic lane violations. Lane entry violations may be issued for restricted vehicle types or vehicles that do not meet required emissions or passenger occupancy standards that enter a managed lane. This notification identifies the vehicle and documents the lane parameter that was violated.

Traffic Management Center (Source Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.

Enforcement Center (Destination Physical Object): The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

This Triple has the following triple relationships:

Relationship	Source	Destination	Flow
Depends On	Connected Vehicle Roadside Equipment	Traffic Management Center	restricted lanes application status

Communication Solutions

(None-Data) - Secure Internet (ITS) (43)
(None-Data) - Apache Kafka (44)
(None-Data) - OMG DDS (44)
(None-Data) - OASIS MQTT (50)
(None-Data) - OASIS AMQP (61)

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - Apache Kafka

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for Apache Kafka. The (None-Data) standards include an unspecified set of standards at the upper layers. The Apache Kafka standards include lower-layer open source code that supports data distribution of specific types of data.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Apache Zookeeper	Facilities Development needed Apache Kafka Apache Zookeeper	Security IETF RFC 8446
	TransNet IP Alternatives IETF RFC 9293
	Access Internet Subnet Alternatives

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Characteristic	Value
Time Context	Recent
Spatial Context	Regional
Acknowledgement	True
Cardinality	Unicast
Initiator	Destination
Authenticable	True
Encrypt	True

Interoperability	Description
Regional	Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture).

Security

Information Flow Security
	Confidentiality	Integrity	Availability
Rating	Moderate	Moderate	Moderate
Basis	Contains PII and intended to be used for enforcement. Thus privacy implications that, while they may affect only a single individual at a time, could yield significant negative consequences to that individual.	Contains PII and intended to be used for enforcement. Thus privacy implications that, while they may affect only a single individual at a time, could yield significant negative consequences to that individual. Must be correct to avoid false accusations.	More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Traffic Management Center --> Enforcement Center:lane violation notification