Parent Service Package: CF06
< < CF06.6 : CF06.7 : CF07.1 > >

CF06.7: MEC Supported Implementation

Multi-Access Edge Computing (MEC) at the local Wide-Area Wireless (WAW) node processes the signal priority request from the commercial vehicle at the edge of the WAW network, coordinating with the signal controller to grant priority access to the commerical vehicle, reducing latency and WAW communications network traffic.

Relevant Regions:

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Basic Commercial Vehicle MaintainerBasic Commercial Vehicle Maintains
Basic Commercial Vehicle ManagerBasic Commercial Vehicle Manages
Basic Commercial Vehicle ManagerCommercial Vehicle Driver System Usage Agreement
Basic Commercial Vehicle OwnerBasic Commercial Vehicle Maintainer System Maintenance Agreement
Basic Commercial Vehicle OwnerBasic Commercial Vehicle Manager Operations Agreement
Basic Commercial Vehicle OwnerCommercial Vehicle Driver Application Usage Agreement
Basic Commercial Vehicle OwnerCommercial Vehicle Driver Vehicle Operating Agreement
Basic Commercial Vehicle OwnerCommercial Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Basic Commercial Vehicle OwnerCommercial Vehicle OBE Owner Expectation of Data Provision
Basic Commercial Vehicle OwnerCommercial Vehicle OBE User Service Usage Agreement
Basic Commercial Vehicle SupplierBasic Commercial Vehicle Owner Warranty
Commercial Vehicle DriverBasic Commercial Vehicle Operates
Commercial Vehicle DriverCommercial Vehicle OBE Operates
Commercial Vehicle OBE MaintainerCommercial Vehicle OBE Maintains
Commercial Vehicle OBE ManagerCommercial Vehicle Driver System Usage Agreement
Commercial Vehicle OBE ManagerCommercial Vehicle OBE Manages
Commercial Vehicle OBE OwnerCommercial Vehicle OBE Maintainer System Maintenance Agreement
Commercial Vehicle OBE OwnerCommercial Vehicle OBE Manager Operations Agreement
Commercial Vehicle OBE OwnerFleet and Freight Management Center Maintainer Maintenance Data Exchange Agreement
Commercial Vehicle OBE OwnerFleet and Freight Management Center Owner Information Exchange Agreement
Commercial Vehicle OBE OwnerFleet and Freight Management Center User Service Usage Agreement
Commercial Vehicle OBE OwnerFleet-Freight Manager Application Usage Agreement
Commercial Vehicle OBE SupplierCommercial Vehicle OBE Owner Warranty
Fleet and Freight Management Center MaintainerFleet and Freight Management Center Maintains
Fleet and Freight Management Center ManagerFleet and Freight Management Center Manages
Fleet and Freight Management Center ManagerFleet-Freight Manager System Usage Agreement
Fleet and Freight Management Center OwnerCommercial Vehicle Driver Application Usage Agreement
Fleet and Freight Management Center OwnerCommercial Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Fleet and Freight Management Center OwnerCommercial Vehicle OBE Owner Information Exchange Agreement
Fleet and Freight Management Center OwnerCommercial Vehicle OBE User Service Usage Agreement
Fleet and Freight Management Center OwnerFleet and Freight Management Center Maintainer System Maintenance Agreement
Fleet and Freight Management Center OwnerFleet and Freight Management Center Manager Operations Agreement
Fleet and Freight Management Center SupplierFleet and Freight Management Center Owner Warranty
Fleet-Freight ManagerFleet and Freight Management Center Operates
ITS Roadway Equipment MaintainerITS Roadway Equipment Maintains
ITS Roadway Equipment ManagerITS Roadway Equipment Manages
ITS Roadway Equipment ManagerMaint and Constr Field Personnel System Usage Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Maintainer System Maintenance Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment SupplierITS Roadway Equipment Owner Warranty
Maint and Constr Field PersonnelITS Roadway Equipment Operates

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Commercial Vehicle OBE CV On-Board Signal Priority 2.1.4 Provide Commercial Vehicle Driver Routing Interface
2.2.2 Provide Vehicle Static Route
2.2.3 Provide CV Driver Electronic Credential and Tax Filing Interface
2.4.2 Collect On-board Commercial Vehicle Sensor Data
2.4.5 Communicate Commercial Vehicle On-board Data
2.4.8 Correlate Commercial Vehicle Route
2.8.3.1 Provide Driver Interface for Intermodal Freight Dispatch
Fleet and Freight Management Center Freight Administration and Management 2.1.1.2 Manage Commercial Vehicle Routes
2.1.1.4 Provide HAZMAT Incident Support
2.1.1.5 Manage Commercial Vehicle Fleet Map Data
2.1.1.6 Monitor Commercial Vehicle Route
2.1.1.7 Monitor Assignment Identities
2.1.3 Provide Fleet Manager Commercial Vehicle Communications
2.1.5 Manage Driver Instruction Store
2.1.6 Manage Commercial Vehicle Incidents
2.1.7 Schedule Commercial Vehicle Servicing
2.6.1 Provide Commercial Vehicle Manager Tag Data Interface
2.7.1 Manage Freight Incidents
2.7.2 Monitor Freight Equipment Route
2.7.3 Manage Freight Equipment Fleet
2.7.4 Manage Freight Equipment Maintenance
2.7.5 Process Freight Integrity Data
2.7.6 Provide Freight Manager Interface
2.7.7 Provide Shipper Booking Interface
ITS Roadway Equipment Roadway Signal Control 1.1.1.1 Process Traffic Sensor Data
1.2.7.1 Process Indicator Output Data for Roads
1.2.7.13 Provide Device Interface for Field Management Stations
1.2.7.16 Process Signal Control Conflict Monitoring
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
Traffic Management Center TMC Signal Control 1.1.2.2 Process Traffic Data
1.1.2.5 Process Vehicle Situation Data
1.1.4.1 Retrieve Traffic Data
1.1.4.4 Manage Traffic Archive Data
1.1.5 Exchange Data with Other Traffic Centers
1.2.1 Select Strategy
1.2.2.2 Determine Indicator State for Road Management
1.2.4.1 Output Control Data for Roads
1.2.6.1 Maintain Traffic and Sensor Static Data
1.2.8 Collect Traffic Field Equipment Fault Data

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Basic Commercial Vehicle Vehicle The 'Basic Commercial Vehicle' represents the commercial vehicle that hosts the on-board equipment that provides ITS capabilities. It includes the heavy vehicle databus and all other interface points between on-board systems and the rest of the commercial vehicle. This vehicle is used to transport goods, is operated by a professional driver and typically administered as part of a larger fleet. Commercial Vehicle classification applies to all goods transport vehicles ranging from small panel vans used in local pick-up and delivery services to large, multi-axle tractor-trailer rigs operating on long haul routes.
Commercial Vehicle Driver Vehicle The 'Commercial Vehicle Driver' represents the people that operate vehicles transporting goods, including both long haul trucks and local pick-up and delivery vans. This physical object is complementary to the Driver physical object in that it represents those interactions which are unique to Commercial Vehicle Operations. Information flowing from the Commercial Vehicle Driver includes those system inputs specific to Commercial Vehicle Operations.
Commercial Vehicle OBE Vehicle The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. A separate 'Vehicle OBE' physical object supports vehicle safety and driver information capabilities that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general ITS capabilities with capabilities that are specific to commercial vehicles.
Fleet and Freight Management Center Center The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet.
ITS Roadway Equipment Field '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.
Multi-Access Edge Computing Field 'Multi-Access Edge Computing' ((MEC) previously known as mobile edge computing) represents computing devices that operate and are managed like a cloud server, but are deployed at the edge of a network (typically a cellular network, but it could be any network). While not in strict proximity to the transportation network, these systems do benefit from vastly decreased distances to the roadway compared to central systems, and so can provide lower latency than strictly backoffice systems
Traffic Management Center Center 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.

Includes Functional Objects:

Functional Object Description Physical Object
CV On-Board Signal Priority 'CV On-board Signal Priority' provides the capability for commercial vehicles to determine eligibility for priority and request signal priority at signalized intersections, ramps, and interchanges through short range communication with traffic control equipment at the roadside. Commercial Vehicle OBE
Freight Administration and Management 'Freight Administration and Management' manages the movement of freight from source to destination. It interfaces to intermodal customers to setup and schedule transportation and coordinates with intermodal terminals and freight consolidation stations to coordinate the shipment. It coordinates with the appropriate government agencies to expedite the movement of trucks, their drivers, and their cargo across international borders. The application monitors the status of the freight and freight equipment (container, trailer, or chassis) and monitors freight location and compares it against the planned route. Fleet and Freight Management Center
MEC Intersection Management 'MEC Intersection Management' uses cellular communications to support connected vehicle applications that manage signalized intersections. It communicates with nearby vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. There may be constraints related to performance related to communications with participants using network operators foreign to the MEC. Multi-Access Edge Computing
Roadway Signal Control 'Roadway Signal Control' includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions. ITS Roadway Equipment
TMC Signal Control 'TMC Signal Control' provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single Traffic Management Center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. This may include adaptive traffic control systems (ATCS) that adjust signal timings based on traffic conditions, demand, and system capacity. It also supports all signalized intersection configurations, including those that accommodate pedestrians. Traffic Management Center
Vehicle Basic Safety Communication 'Vehicle Basic Safety Communication' exchanges current vehicle characteristics, location, and motion (including past and intended maneuver) information with other vehicles in the vicinity and the infrastructure, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that coordinate maneuvers and may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. This object can also support broadcasting other vehicle information required for passing through a specific roadway segment such as variables that describe vehicle's characteristics and parameters, driver's preferences in terms of vehicle motion and behavior, etc. Vehicle
Vehicle Intersection Movement 'Vehicle Intersection Movement' uses short-range wireless communications to monitor other connected vehicles at intersections and support the safe movement of the vehicle through the intersection by receiving and processing signal phase and timing messages from the intersection. Driver warnings are provided and the application may also optionally take control of the vehicle to avoid collisions, in coordination with Vehicle Control Automation. The application will also notify the infrastructure and other vehicles if it detects an unsafe infringement on the intersection. Vehicle

Includes Information Flows:

Information Flow Description
cv driver information presentation Presentation of information to the commercial vehicle driver that includes current status of on-board systems.
cv driver input This flow represents the tactile or auditory interface with ITS equipment containing the commercial vehicle driver and vehicle information. This flow contains inquiries to the commercial vehicle managing system, interaction with on-board equipment including setup, configuration, and initiation of self tests, and entry of carrier, driver, vehicle, and route information.
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation.
driver to fleet request Requests from the driver and vehicle for routing, payment, and enrollment information.
fleet to driver update Updated instructions to the driver including dispatch, routing, travel and parking information, and special instructions. Special instructions include incident management instruction, operational tasks, impacted transport orders in case of an incident, task descriptions with trip/route/load plan, transport order status information, driver information, vehicle information, cargo information and trip information.
host commercial vehicle status Information provided to the ITS on-board equipment from other systems on the Commercial Vehicle Platform.
intersection control status Status data provided by the traffic signal controller including phase information, alarm status, and priority/preempt status.
intersection geometry The physical geometry of an intersection covering the location and width of each approaching lane, egress lane, and valid paths between approaches and egresses. This flow also defines the location of stop lines, cross walks, specific traffic law restrictions for the intersection (e.g., turning movement restrictions), and other elements that support calculation of a safe and legal vehicle path through the intersection.
intersection management application info Intersection and device configuration data, including intersection geometry, and warning parameters and thresholds. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
intersection management application status Infrastructure application status including current operational state and status of the field device and a log of operations.
intersection status Current signal phase and timing information for all lanes at a signalized intersection. This flow identifies active lanes and lanes that are being stopped and specifies the length of time that the current state will persist for each lane. It also identifies signal priority and preemption status and pedestrian crossing status information where applicable. It may also include future signal phase and timing information.
signal priority request Request from a vehicle for priority at an intersection. The request may include the priority level, the desired time and duration of service, and the intended travel path through the intersection. This flow may also allow the originator to cancel a previously issued request for priority.
signal priority service request A service request for vehicle priority issued to a traffic signal controller. The request includes the priority level, and may include other parameters such as the desired time and duration of service, and the intended travel path through the intersection. This flow also allows the originator to cancel a previously issued request for priority.
signal priority status In response to a request for signal priority, this flow indicates the status of the priority or preemption request.
vehicle location and motion Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective Performance Measure

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement

Related Sources

Document Name Version Publication Date
None


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Basic Commercial Vehicle  
Commercial Vehicle OBE High High Moderate Class 4
Fleet and Freight Management Center High High Moderate Class 4
ITS Roadway Equipment Moderate Moderate Low Class 2
Multi-Access Edge Computing Moderate High Moderate Class 3
Traffic Management Center Moderate High Low Class 3



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Basic Commercial Vehicle Commercial Vehicle OBE host commercial vehicle status Moderate Moderate Moderate
This can include some sensitive data. However, other data, such as vehicle location and motion will then be broadcast. There also may be proprietary information included in this. This is used later on to determine whether a vehicle should request priority at an intersection. If this information is incorrect the vehicle may make false requests. All other flows that use the data from this flow have a MODERATE integrity requirement, therefore, this must also have a MODERATE integrity requirement. This information would need to be available immediately for the application to work.
Commercial Vehicle Driver Commercial Vehicle OBE cv driver input Moderate Moderate Moderate
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive and physical security reasons. Data should be correct as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. Flow should be available as it relates to CVO, however there is generally another mechanism through which this data might be received, which is why it is MODERATE and not HIGH.
Commercial Vehicle OBE Commercial Vehicle Driver cv driver information presentation Low Moderate Moderate
This data is informing the driver of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it. Data should be correct as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. Flow should be available as it relates to CVO, however there is generally another mechanism through which this data might be received, which is why it is MODERATE and not HIGH.
Commercial Vehicle OBE Fleet and Freight Management Center driver to fleet request High Moderate Moderate
Contains trip and payment details that if disclosed would compromise the driver, load and carrier. Payment details need to be correct or the vehicle may be delayed. Likely limited in scope to individual vehicles that suffer corrupted messages. If this flow is not available the commercial vehicle in question will be delayed and/or misrouted, which will inconvenience that vehicle, costing time and money.
Commercial Vehicle OBE Multi-Access Edge Computing signal priority request Not Applicable Moderate Low
There is no sensitive or confidential information within this messages. Additionally, it could be inferred by observing either the presence of a priority-requesting vehicle near an intersection, or the effect on the timing of the intersection. This is also transmitted as a result of broadcast data. Only specific vehicles that have been granted authorization to receive priority/preemption should be able to send this request. Allowing other vehicles to send it could negatively impact the performance of the traffic signal network, so authentication and integrity mechanisms must ensure the message cannot be forged or altered. If the CVRSE does not receive any requests, the vehicle may not receive the priority it requested. In the worst case scenario the vehicle would be forced to wait at some lights until they turned green. It would be more useful for a device to support this application, and only have some messages received, than to not support this application at all.
Fleet and Freight Management Center Commercial Vehicle OBE fleet to driver update High Moderate Moderate
Contains PII, routing instructions and tasking, predictive of vehicle future, all of which if compromised would provide leverage over vehicle, driver and owner. Contains a lot of information dedicated to the individual vehicle, any of which if incorrect or corrupted would negatively affect the vehicle and driver. There is a great deal of informatino in this flow that would be challenging to assemble through other sources. A delay in receiving this information would negatively affect the vehicle and driver.
ITS Roadway Equipment Commercial Vehicle Driver driver information Not Applicable High Moderate
This data is sent to all drivers and is also directly observable, by design. This is the primary signal trusted by the driver to decide whether to go through the intersection and what speed to go through the intersection at; if it’s wrong, accidents will happen. If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a knock-on effect due to lack of coordination with other intersections.
ITS Roadway Equipment Multi-Access Edge Computing intersection control status Moderate High Moderate
This data is intentionally transmitted to everyone via a While this information is broadcast and can also be determined via other visual indicators, all communications between field infrastructure should be protected from viewing to prevent attackers from analyzing traffic and developing attack methods. If this is compromised, the Roadway Equipment and Roadside Equipment will be sending messages that are inconsistent with each other, leading to confusion and possible accidents. If this is down, the RSE doesn’t get the information it needs to stay in synch with the actual signal state, reducing or eliminating the value add from having this application. The RSE must detect a lack of availability and choose not to send out-of-date information, so a failure of availability could be interpreted as having the same value as Integrity. However, this data is semi-predictable and there are other indicators (such as the lights themselves) of the intersection status. From NYC, who believe this should be HIGH for some applications: If this is down, the RSE doesn’t get the information it needs to stay in synch with the actual signal state, reducing or eliminating the value add from having this application. The RSE must detect a lack of availability and choose not to send out-of-date information, so a failure of availability cannot have worse consequences than a failure of integrity which we have previously assessed at HIGH.
Multi-Access Edge Computing Commercial Vehicle OBE signal priority status Low Moderate Low
Not much could be learned by observing this flow, just the state of the priority request and the identity of the requester. Both of those are information that can be gleaned by physical observation, and give little advantage to an observer. Signal priority status information enables the receiving vehicle to proceed with more surety toward's its next stop; while there are obvious redundancies, a degree of confidence in the state of the message is required for user acceptance if nothing else. The most important aspect of this flow is the initiating request and hopefull success of that priority message; if that succeeds then the signal will turn in the vehicle's favor, making this flow a 'nice-to-have' that should be correct if it arrives, but is not necessary for the priority application to function.
Multi-Access Edge Computing ITS Roadway Equipment signal priority service request Moderate Moderate Low
There is no sensitive or confidential information within this messages. Additionally, it could be inferred by observing either the presence of a priority-requesting vehicle near an intersection, or the effect on the timing of the intersection. This is also transmitted as a result of broadcast data; however, all communications between field infrastructure should be protected from viewing to prevent attackers from analyzing traffic and developing attack methods. The MEC is transmitting a request to the ITS RE on behalf of a priority-requesting vehicle. It should only be making requests on behalf of an approved vehicle. A corrupted request may lead to a vehicle not receiving a green light after requesting it. In this case, this may lead to traffic delays. If an unapproved vehicle is able to forge these requests, they may cause larger scale traffic delays. If the ITS RE does not receive any requests, the vehicle may not receive the priority it requested. In the worst case scenario the vehicle would be forced to wait at some lights until they turned green. It would be more useful for a device to support this application, and only have some messages received, than to not support this application at all.
Multi-Access Edge Computing Traffic Management Center intersection management application status Moderate Moderate Low
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. May be LOW in some cases. If this is compromised, it could send unnecessary maintenance workers, or worse report plausible data that is erroneous. From THEA: should be able to cope with some bad information on the status and record of alerts/warnings; aggregate info; however could cause appearance of excessive traffic violations or unnecessary maintenance caused if data is compromised (operational state, status, log); should not affect the application functionality Incident status information should be presented in timely fashion as large scale mobility and safety issues are related. There are other mechanisms for reporting this information however, thus MODERATE. From THEA: Only limited adverse effect of info is not timely/readily available
Traffic Management Center Multi-Access Edge Computing intersection management application info Moderate High Low
Proprietary configuration data with warning parameters and thresholds. should be accurate and not be tampered with; could enable outside control of application This message is an indication of a potential hazard. If it isn’t received it increases the risk to other road users. If a vehicle is infringing on an intersection, it must report this.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

NameTitlePhysical Object
ITE 5201 ATC Advanced Transportation Controller ITS Roadway Equipment
ITE 5202 ATC Model 2070 Model 2070 Controller Standard ITS Roadway Equipment
ITE 5301 ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
ITE 5401 ATC API Application Programming Interface Standard for the Advanced Transportation Controller ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems ITS Roadway Equipment
Traffic Management Center
NEMA TS2 Traffic Controller Assemblies Traffic Controller Assemblies with NTCIP Requirements ITS Roadway Equipment




System Requirements

No System Requirements