Vehicle --> Connected Vehicle Roadside Equipment:
vehicle location and motion for surveillance
Definitions
vehicle location and motion for surveillance (Information Flow): Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
Vehicle (Source Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
Connected Vehicle Roadside Equipment (Destination Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Included In
This Triple is in the following Service Packages:
- ST02: Eco-Traffic Signal Timing
- ST03: Eco-Traffic Metering
- ST04: Roadside Lighting
- ST07: Eco-Lanes Management
- ST08: Eco-Approach and Departure at Signalized Intersections
- ST09: Connected Eco-Driving
- ST10: Low Emissions Zone Management
- SU04: Map Management
- TM02: Vehicle-Based Traffic Surveillance
- TM04: Connected Vehicle Traffic Signal System
- TM21: Speed Harmonization
- VS05: Curve Speed Warning
- VS08: Queue Warning
- VS09: Reduced Speed Zone Warning / Lane Closure
- VS10: Restricted Lane Warnings
- VS15: Infrastructure Enhanced Cooperative Adaptive Cruise Control
This triple is associated with the following Functional Objects:
- RSE Map Management
- RSE Restricted Lanes Application
- RSE Speed Warning
- RSE Traffic Monitoring
- Vehicle Basic Safety Communication
- Vehicle Map Management
- Vehicle Speed Management Assist
This Triple is described by the following Functional View Data Flows:
- vehicle_guidance_probe_data
- vehicle_guidance_probe_data_for_archive
- vehicle_roadside_surveillance_location_data
- vehicle_roadside_surveillance_size_data
- vehicle_roadside_surveillance_speed_data
- vehicle_roadside_surveillance_status_data
This Triple has the following triple relationships:
None |
Communication Solutions
- US: SAE LTE-V2X BSM - LTE-V2X WSMP (13)
- EU: CA Service - BTP/GeoNetworking/G5 (24)
- US: SAE Basic Safety Messages - WAVE WSMP (29)
Selected Solution
Solution Description
ITS Application Entity
SAE J2735 SAE J3161/1 |
Click gap icons for more info.
|
||
Mgmt
SAE J3161 3GPP 24.301 3GPP 36.331 |
Facilities
SAE J2735 |
Security
|
|
TransNet
IEEE 1609.3 |
|||
Access
|
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 | False |
Cardinality | Broadcast |
Initiator | Source |
Authenticable | True |
Encrypt | False |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Not Applicable | Moderate | Moderate | |
Basis | This is directly observable data; DISC: WYO believes this to be MODERATE | Incorrect information here could lead to the system not functioning properly. If they are unable to properly detect all vehicles crossing the border, it would lead to confusion. There are other factors, such as visual indicators, of vehicles crossing the border, which can be used to help mitigate contradicting information. DISC: THEA believes this should be HIGH: "BSM info needs to be accurate and should not be tampered with" WYO believes this to be HIGH | This information must be available in a timely manner for the system to act upon it. The system can operate correctly if some messages are missed, but overall a majority of them should be received.; WYO believes this to be LOW |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |