ITS Roadway Equipment --> Enforcement Center:
violation notification
Definitions
violation notification (Information Flow): Notification to enforcement agency of detected traffic violations. This notification identifies the vehicle and documents the infraction date, time, and location, the violation, and associated information that documents the violation. For example, for a speed violation, this flow includes the measured speed and current posted speed limit.
ITS Roadway Equipment (Source Physical Object): 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
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:
- tec-lane_violation_notification_from_roadway
- tec-shoulder_violation_notification_from_roadway
- tec-speed_violation_notification
This Triple has the following triple relationships:
| None |
Communication Solutions
-
(None-Data) - Secure Internet (ITS) (32)
Selected Solution
(None-Data) - Secure Internet (ITS)Solution Description
|
ITS Application Entity
Development needed  |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
Development needed |
Security
|
|
|
TransNet
|
|||
|
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 | Local |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Destination |
| Authenticable | True |
| Encrypt | True |
| Interoperability | Description |
|---|---|
| Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
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. | Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. | 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 |