Collier Countywide Connected Traveler Information System
Project Description: The project will deploy CV RSUs with Bluetooth travel time detector capabilities along the US 41 and SR 951 in Collier County as well as future phases along other roads.
1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
11: The ITS Object shall request pseudonymous credentials from the CCMS.
12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
2: The ITS Object shall request enrollment credentials from the CCMS.
8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
1: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
2: The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.
4: The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers.
6: The center shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each).
7: The center shall remotely control devices to detect traffic.
1: The center shall collect traffic probe data from vehicles via roadside field equipment.
2: The center shall collect road condition data from probe-equipped transit vehicles via transit management centers; the data may be aggregated and preliminarily processed at the sending center.
3: The center shall collect traffic data from traveler information centers based on data from their subscriber vehicles; the data may be aggregated and initial link time calculations performed at the sending center.
4: The center shall collect probe data from payment administrative centers containing travel times between toll collection points for those vehicles equipped for electronic toll collection; the data may be aggregated and processed at the sending center.
5: The center shall collect operational status for the roadside probe data collection equipment.
6: The center shall collect fault data for the roadside probe data collection equipment for repair.
1: The data support center shall distribute to personal devices data which has been validated, aggregated, integrated, and sanitized.
2: The data support center shall distribute to Vehicles data which has been validated, aggregated, integrated, and sanitized.
3: The data support center shall distribute to other Centers data which has been validated, aggregated, integrated, and sanitized.
4: The data support center shall distribute to Vehicles broadcast data which has been validated, aggregated, integrated, and sanitized.
5: The data support center shall distribute to Connected Vehicle Roadside Equipment data which has been validated, aggregated, integrated, and sanitized.
6: The data support center shall provide metadata parameters (geographic area, data content type, time) as filters for subscription.
7: The data support center shall provide data consumers with a mechanism for throttling (or reducing) the data they receive as part of subscriptions.
8: The data support center shall provide data consumers with a mechanism for subscribing to data received by the Center.
9: The data support center shall provide a mechanism for the operator to modify data subscriptions.
1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
11: The ITS Object shall request pseudonymous credentials from the CCMS.
12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
2: The ITS Object shall request enrollment credentials from the CCMS.
8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
11: The ITS Object shall request pseudonymous credentials from the CCMS.
12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
13: The ITS Object shall request permissions from the Center that manages permissions requests.
2: The ITS Object shall request enrollment credentials from the CCMS.
8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
1: The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.
4: The field element shall return sensor and CCTV system operational status to the controlling center.
5: The field element shall return sensor and CCTV system fault data to the controlling center for repair.
1: The field element shall collect, process, and send data to the center to uniquely identify passing vehicles in order to support travel time measurement
1: The field element shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles.
3: The field element shall provide data collection parameters to vehicles.
1: The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.
1: The Vehicle shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications.
10: The Vehicle shall obtain intersection geometry information from Centers.
3: The Vehicle shall obtain roadway geometry update information from proximate Connected Vehicle Roadside Equipment.
4: The Vehicle shall obtain intersection geometry update information from proximate Connected Vehicle Roadside Equipment.
5: The Vehicle shall provide its location to Centers.
6: The Vehicle shall obtain basemap updates from Centers.
7: The Vehicle shall obtain basemap update information from proximate Connected Vehicle Roadside Equipment.
8: The Vehicle shall obtain roadway geometry information from Centers.
1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
4: The vehicle shall provide traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicle.
6: The Vehicle shall provide data to Connected Vehicle Roadside Equipment. in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.
1: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment.
2: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service.
3: The ITS Object shall obtain network addresses from the Object Registration and Discovery Service.
4: The ITS Object shall make network address information available to onboard applications.
5: The ITS Object shall provide its configuration and operational status information to the Service Monitor
6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.
1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
13: The ITS Object shall request permissions from the Center that manages permissions requests.
2: The ITS Object shall request enrollment credentials from the CCMS.
3: The ITS Object shall obtain the CCMS' trust credentials.
4: The ITS Object shall provide a mechanism for on-board applications to digitally sign messages using keys secured by the CCMS' trust authority.
5: The ITS Object shall provide a mechanism for on-board applications to authenticate messages secured by the CCMS' trust authority.
6: The ITS Object shall provide a mechanism for on-board applications to encrypt messages using keys secured by the CCMS' trust authority.
7: The ITS Object shall provide a mechanism for on-board applications to decrypt messages using keys secured by the CCMS' trust authority.
8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
9: The ITS Object shall make the list of revoked credentials available to on-board applications.
1: The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.
1: The field element shall collect, process, and send data to the center to uniquely identify passing vehicles in order to support travel time measurement
1: The field element shall monitor the operational status (state of the device, configuration, and fault data) of connected sensors (such as traffic, infrastructure, environmental, security, speed) and devices (such as highway advisory radio, dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals, ramp meters, short range communications equipment, security surveillance equipment).
7: The field element shall implement configuration commands received from an authorized Center.
8: The field element shall implement operational status commands received from an authorized Center.
1: The field element shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles.
3: The field element shall provide data collection parameters to vehicles.
1: The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.
2: The field element shall aggregate and forward collected probe information to the center.
3: The field element shall aggregate and forward collected probe information to other field elements.
1: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment.
2: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service.
3: The ITS Object shall obtain network addresses from the Object Registration and Discovery Service.
4: The ITS Object shall make network address information available to onboard applications.
5: The ITS Object shall provide its configuration and operational status information to the Service Monitor
6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.
1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
11: The ITS Object shall request pseudonymous credentials from the CCMS.
12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
13: The ITS Object shall request permissions from the Center that manages permissions requests.
2: The ITS Object shall request enrollment credentials from the CCMS.
3: The ITS Object shall obtain the CCMS' trust credentials.
4: The ITS Object shall provide a mechanism for on-board applications to digitally sign messages using keys secured by the CCMS' trust authority.
5: The ITS Object shall provide a mechanism for on-board applications to authenticate messages secured by the CCMS' trust authority.
6: The ITS Object shall provide a mechanism for on-board applications to encrypt messages using keys secured by the CCMS' trust authority.
7: The ITS Object shall provide a mechanism for on-board applications to decrypt messages using keys secured by the CCMS' trust authority.
8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
9: The ITS Object shall make the list of revoked credentials available to on-board applications.
1: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
7: The center shall remotely control devices to detect traffic.
3: The center shall collect traffic data from traveler information centers based on data from their subscriber vehicles; the data may be aggregated and initial link time calculations performed at the sending center.
5: The center shall collect operational status for the roadside probe data collection equipment.
6: The center shall collect fault data for the roadside probe data collection equipment for repair.
1: The Vehicle shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications.
10: The Vehicle shall obtain intersection geometry information from Centers.
3: The Vehicle shall obtain roadway geometry update information from proximate Connected Vehicle Roadside Equipment.
4: The Vehicle shall obtain intersection geometry update information from proximate Connected Vehicle Roadside Equipment.
5: The Vehicle shall provide its location to Centers.
6: The Vehicle shall obtain basemap updates from Centers.
7: The Vehicle shall obtain basemap update information from proximate Connected Vehicle Roadside Equipment.
8: The Vehicle shall obtain roadway geometry information from Centers.
1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
2: The Vehicle shall collect data collection parameters from Centers.
3: The vehicle shall collect location and motion data from the vehicle platform.
6: The Vehicle shall provide data to Connected Vehicle Roadside Equipment. in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.
