Connected Vehicle Roadside Equipment --> ITS Roadway Equipment:
personal location information
Definitions
personal location information (Information Flow): Pedestrian, bicyclist, and other non-motorized user locations at an intersection as detected and reported by an RSE.
Connected Vehicle Roadside Equipment (Source Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. 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.
ITS Roadway Equipment (Destination 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.
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:
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Secure Internet (ITS) (32)
- (None-Data) - Apache Kafka (36)
- (None-Data) - OMG DDS (36)
- (None-Data) - OASIS MQTT (42)
- (None-Data) - OASIS AMQP (45)
Selected Solution
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 | Adjacent |
Acknowledgement | False |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | False |
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 | Not Applicable | Moderate | Low | |
Basis | This is simply passing on received broadcast messages. It is intended to be received by everyone. pedestrian location within the crosswalk is not confidential or encrypted | We assume that this information is not able to cause the ITS RE to behave in extreme ways, e.g. to keep all the lights red forever because it thinks there's a baby in the middle of the road. In other words, the ITS RE has maximum durations for the different phases of the cycle which it will not go beyond not matter what this information flow contains. Bad information can cause annoyances and disrupt traffic flow to a limited extent but will not have a large impact. NYC: location should be accurate and should not be tampered; however, we assume the info is not able to cause the ITS RE to behave in extreme ways (i.e., there should be maximum different cycle phases) | If this is down, the ITS RE goes back to default behavior, which we assume is set sensibly. NYC: if down, the ITS RE should revert to default behavior which we assume is sensible |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |