LYNX TSP/CAV

Project Description: LYNX project covering transit signal priority (TSP) and connected and autonomous transit vehicles (CAV).

Project Status: Planned

Project Stakeholders:

• FDOT CO
• FDOT District 5
• LYNX

Project Service Packages:

• PT09: Transit Signal Priority (LYNX TSP/CAV Project)
• SU04: Map Management (LYNX TSP/CAV Project)
• SU08: Security and Credentials Management (LYNX TSP/CAV Project)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
intersection geometry	CAV-ITS Map Update System	FDOT District 5 Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	FDOT District 5 RTMC	Planned
intersection geometry	CAV-ITS Map Update System	LYNX Transportation Center	Planned
intersection geometry	FDOT District 5 Field Equipment	LYNX Transit Vehicles	Planned
intersection geometry	LYNX CAV Field Equipment	LYNX Transit Vehicles	Planned
intersection management application info	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
intersection management application info	LYNX Transportation Center	LYNX CAV Field Equipment	Planned
intersection management application status	LYNX CAV Field Equipment	LYNX Transportation Center	Planned
intersection status	FDOT District 5 Field Equipment	LYNX Transit Vehicles	Planned
intersection status	LYNX CAV Field Equipment	LYNX Transit Vehicles	Planned
local signal priority request	LYNX Transit Vehicles	FDOT District 5 Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	LYNX CAV Field Equipment	Planned
map update notification	FDOT District 5 RTMC	CAV-ITS Map Update System	Planned
map update notification	LYNX Transportation Center	CAV-ITS Map Update System	Planned
map updates	CAV-ITS Map Update System	FDOT District 5 Field Equipment	Planned
map updates	CAV-ITS Map Update System	FDOT District 5 RTMC	Planned
map updates	CAV-ITS Map Update System	LYNX CAV Field Equipment	Planned
map updates	CAV-ITS Map Update System	LYNX Transportation Center	Planned
misbehavior report	FDOT District 5 Field Equipment	FDOT SCMS	Planned
right-of-way request notification	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
roadway geometry	CAV-ITS Map Update System	FDOT District 5 Field Equipment	Planned
roadway geometry	CAV-ITS Map Update System	LYNX CAV Field Equipment	Planned
security credential revocations	FDOT SCMS	LYNX CAV Field Equipment	Planned
security credentials	FDOT SCMS	LYNX CAV Field Equipment	Planned
security policy and networking information	FDOT SCMS	LYNX CAV Field Equipment	Planned
signal control commands	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control commands	LYNX Transportation Center	LYNX CAV Field Equipment	Planned
signal control device configuration	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control plans	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
signal control status	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
signal control status	LYNX CAV Field Equipment	LYNX Transportation Center	Planned
signal fault data	FDOT District 5 Field Equipment	FDOT District 5 RTMC	Planned
signal priority status	FDOT District 5 Field Equipment	LYNX Transit Vehicles	Planned
signal priority status	LYNX CAV Field Equipment	LYNX Transit Vehicles	Planned
signal system configuration	FDOT District 5 RTMC	FDOT District 5 Field Equipment	Planned
vehicle location and motion	LYNX Transit Vehicles	FDOT District 5 Field Equipment	Planned
vehicle location and motion	LYNX Transit Vehicles	LYNX CAV Field Equipment	Planned
vehicle location data for mapping	FDOT District 5 Field Equipment	CAV-ITS Map Update System	Planned
vehicle location data for mapping	LYNX CAV Field Equipment	CAV-ITS Map Update System	Planned

Project Functional Requirements (Element - Functional Object):

• CAV-ITS Map Update System - ITS Management Support
• 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.
• 6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.


• CAV-ITS Map Update System - ITS Security Support
• 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.


• CAV-ITS Map Update System - Map Management
• 1: The Center shall collect Vehicle location information from Vehicles.
• 22: The Center shall provide basemap updates to Vehicles.
• 25: The Center shall provide roadway geometry updates to Vehicles.
• 27: The Center shall provide basemap updates to Connected Vehicle Roadside Equipment.
• 7: The Center shall collect vehicle location information from the Connected Vehicle Roadside Equipment.


• FDOT District 5 Field Equipment - ITS Management Support
• 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.
• 6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.


• FDOT District 5 Field Equipment - ITS Security Support
• 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.
• 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.


• FDOT District 5 Field Equipment - Roadway Signal Control
• 1: The field element shall control traffic signals under center control.
• 10: The field element shall receive request for transit vehicle signal priority.
• 4: The field element shall report the current signal control information to the center.
• 6: The field element shall return traffic signal controller operational status to the center.
• 8: The field element shall report current transit priority status to the center.


• FDOT District 5 Field Equipment - RSE Intersection Management
• 1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.
• 3: The field element shall send the infrastructure application status to the operations center.
• 5: The field element shall receive transit signal priority requests from transit vehicles and forward to the traffic signal controller.
• 9: The field element shall collect current signal phase and timing data from the traffic signal controller.


• FDOT District 5 Field Equipment - RSE Map Management
• 1: The field element shall collect broadcasted vehicle location and motion information.
• 10: The field element shall provide intersection geometry updates to proximate Vehicles.
• 12: The field element shall provide roadway geometry updates to proximate Vehicles.
• 2: The field element shall aggregate vehicle location data.
• 3: The field element shall provide roadway geometry update information to proximate Vehicles.
• 5: The field element shall provide intersection geometry update information to proximate Vehicles.
• 6: The field element shall provide basemap update information to proximate Vehicles.
• 8: The field element shall provide vehicle location data to Centers.
• 9: The field element shall provide basemap updates to proximate Vehicles.


• FDOT District 5 RTMC - Center Map Management
• 1: The Center shall collect updates to basemaps from Map Update Systems .
• 2: The Center shall collect updates to intersection geometry from Map Update Systems.
• 3: The Center shall provide roadway geometry updates to Map Update Systems.
• 4: The Center shall provide intersection geometry updates to Map Update Systems.


• FDOT District 5 RTMC - ITS Management Support
• 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.
• 6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.


• FDOT District 5 RTMC - ITS Security Support
• 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.
• 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.


• FDOT District 5 RTMC - TMC Multi-Modal Coordination
• 1: The center shall respond to requests from transit management centers for signal priority at one or more intersections along a particular transit route.
• 2: The center shall exchange information with transit management centers including details current transit routes, the level of service on each route, and the progress of individual vehicles along their routes.


• FDOT District 5 RTMC - TMC Signal Control
• 1: The center shall remotely control traffic signal controllers.
• 3: The center shall collect traffic signal controller operational status and compare against the control information sent by the center.
• 4: The center shall collect traffic signal controller fault data from the field.
• 5: The center shall manage (define, store and modify) control plans to coordinate signalized intersections, to be engaged at the direction of center personnel or according to a daily schedule.
• 6: The center shall implement control plans to coordinate signalized intersections based on data from sensors.
• 7: The center shall manage boundaries of the control sections used within the signal system.
• 8: The center shall maintain traffic signal coordination including synchronizing clocks throughout the system.


• FDOT SCMS - CCMS Authorization
• 1: The Center shall generate credential identifiers using facilities that are independently owned and operated from one another.
• 10: The Center shall accept user permission information from Centers authorized to provide that information.
• 11: The Center shall acquire identifiers relevant to ITS services from the relevant registry of such identifiers
• 2: The Center shall assign two or more non-unique identifiers, that when combined are unique, to each credential it distributes.
• 3: The Center shall verify information received in pseudonym requests.
• 4: The Center shall coordinate the distribution of credentials with other Centers.
• 5: The Center shall store credential identifiers using facilities that are independently owned and operated from one another.
• 6: The Center shall provide Vehicle pseudonymous credentials in response to valid Vehicle pseudonym requests.
• 8: The Center shall provide Center pseudonymous credentials in response to valid Center pseudonym requests.
• 9: The Center shall provide Connected Vehicle Roadside Equipment pseudonymous credentials in response to valid Connected Vehicle Roadside Equipment pseudonym requests.


• FDOT SCMS - CCMS Misbehavior Reporting and Action
• 2: The Center shall analyze misbehavior reports.


• FDOT SCMS - CCMS Provisioning
• 1: The Center shall provide security and regulatory policy information to ITS Objects.
• 2: The Center shall provide its credentials information to ITS Objects.
• 3: The Center shall provide the operator with mechanisms for monitoring the status of all credential-granting activities without compromising any other requirement.


• FDOT SCMS - CCMS Revocation
• 1: The Center shall place certificates on the revocation list of those certificates that are associated with misbehavior.


• FDOT SCMS - ITS Management Support
• 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.
• 6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.


• FDOT SCMS - ITS Security Support
• 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.
• 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.


• LYNX CAV Field Equipment - ITS Management Support
• 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.


• LYNX CAV Field Equipment - ITS Security Support
• 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.
• 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.


• LYNX CAV Field Equipment - Roadway Signal Control
• 1: The field element shall control traffic signals under center control.
• 10: The field element shall receive request for transit vehicle signal priority.
• 13: The field element shall provide to roadside equipment the intersection geometry and signal phase movement information including phase and timing information, alarm status, and priority/preempt status.
• 14: The field element shall provide data to the Connected Vehicle Roadside Equipment.
• 4: The field element shall report the current signal control information to the center.
• 6: The field element shall return traffic signal controller operational status to the center.
• 7: The field element shall return traffic signal controller fault data to the center.
• 8: The field element shall report current transit priority status to the center.
• 9: The field element shall report current intersection signal timing information to roadside equipment for transmission to connected vehicles.


• LYNX CAV Field Equipment - RSE Intersection Management
• 1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.
• 3: The field element shall send the infrastructure application status to the operations center.
• 5: The field element shall receive transit signal priority requests from transit vehicles and forward to the traffic signal controller.
• 8: The field element shall send a signal service request to the traffic signal controller when its application status determines the need for a signal change.
• 9: The field element shall collect current signal phase and timing data from the traffic signal controller.


• LYNX CAV Field Equipment - RSE Map Management
• 1: The field element shall collect broadcasted vehicle location and motion information.
• 10: The field element shall provide intersection geometry updates to proximate Vehicles.
• 11: The field element shall provide parking facility geometry information to proximate Personal devices.
• 12: The field element shall provide roadway geometry updates to proximate Vehicles.
• 2: The field element shall aggregate vehicle location data.
• 3: The field element shall provide roadway geometry update information to proximate Vehicles.
• 5: The field element shall provide intersection geometry update information to proximate Vehicles.
• 6: The field element shall provide basemap update information to proximate Vehicles.
• 8: The field element shall provide vehicle location data to Centers.
• 9: The field element shall provide basemap updates to proximate Vehicles.


• LYNX Transit Vehicles - ITS Management Support
• 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.


• LYNX Transit Vehicles - ITS Security Support
• 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.
• 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.


• LYNX Transit Vehicles - Transit Vehicle Signal Priority
• 1: The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.
• 2: The transit vehicle shall send priority requests to traffic signal controllers at intersections, pedestrian crossings, and multimodal crossings on the roads (surface streets) and freeway (ramp controls) network that enable a transit vehicle schedule deviation to be corrected.


• LYNX Transportation Center - Center Map Management
• 1: The Center shall collect updates to basemaps from Map Update Systems .
• 2: The Center shall collect updates to intersection geometry from Map Update Systems.
• 3: The Center shall provide roadway geometry updates to Map Update Systems.
• 4: The Center shall provide intersection geometry updates to Map Update Systems.


• LYNX Transportation Center - ITS Management Support
• 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.


• LYNX Transportation Center - ITS Security Support
• 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.
• 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.


• LYNX Transportation Center - TMC Multi-Modal Coordination
• 1: The center shall respond to requests from transit management centers for signal priority at one or more intersections along a particular transit route.
• 2: The center shall exchange information with transit management centers including details current transit routes, the level of service on each route, and the progress of individual vehicles along their routes.


• LYNX Transportation Center - Transit Center Priority Management
• 3: The center shall define business rules that govern use of transit vehicle signal priority, communicate these rules to the transit vehicle, and monitor transit vehicle requests for priority at signalized intersections.

Standards:

• (None-Data) - Secure Internet (ITS)
• US: Misbehavior reporting - Secure Internet (ITS)
• US: NTCIP Signal Priority - SNMPv3/TLS
• US: NTCIP Signal System Masters - SNMPv3/TLS
• US: NTCIP Traffic Signal - SNMPv3/TLS
• US: SAE Basic Safety Messages - WAVE WSMP
• US: SAE Lane-Level Mapping - Secure Internet (ITS)
• US: SAE Other J2735 - Secure Internet (ITS)
• US: SAE Signal Control Messages - WAVE WSMP
• US: SAE Signal Preemption - WAVE TCP
• US: Security Credentials - Secure Internet (ITS)

Project Operational Concepts:

Roles and Responsibilities

• LYNX
• Communicate with the CAV-ITS Map Update System to obtain up-to-date maps.
• Communicate with the FDOT SCMS regarding CAV security.
• Provide transit signal priority services.