Traffic Management Center --> Enforcement Center:
current lane restrictions

Definitions

current lane restrictions (Information Flow): Information provided to an enforcement agency that defines the current enforceable lane restrictions. It defines the location, duration, and restrictions for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, and speed limits.

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:

• PT10: Intermittent Bus Lanes
• ST07: Eco-Lanes Management

This triple is associated with the following Functional Objects:

• TMC Dynamic Lane Management and Shoulder Use

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

• tec-current_dynamic_lane_configuration

This Triple has the following triple relationships:

Communication Solutions

• EU: DATEX - DATEX Messaging (3)
• (None-Data) - Secure Internet (ITS) (32)
• (None-Data) - Apache Kafka (36)
• (None-Data) - OMG DDS (36)
• (None-Data) - OASIS MQTT (42)
• (None-Data) - OASIS AMQP (45)
• Data for Distribution (TBD) - OASIS AMQP (45)

Selected Solution

(None-Data) - OMG DDS

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt OMG DDS	Facilities Development needed OMG DDS OMG DDS-RPC OMG DDSI-RTPS	Security OMG DDS-Security
	TransNet IETF RFC 768 IP Alternatives
	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

Security