Connected Vehicle Roadside Equipment --> Commercial Vehicle OBE:
signal priority status
Definitions
signal priority status (Information Flow): In response to a request for signal priority, this flow indicates the status of the priority or preemption request.
Connected Vehicle Roadside Equipment (Source 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.
Commercial Vehicle OBE (Destination Physical Object): 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.
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
- EU: Signal Control Messages - BTP/GeoNetworking/G5 (20)
- US: SAE Signal Preemption - LTE-V2X TCP (23)
- US: SAE Signal Preemption - WAVE TCP (36)
Selected Solution
Solution Description
ITS Application Entity
SAE J2735 ISO 19091 ETSI 102 894-2 |
Click gap icons for more info.
|
||
Mgmt
ETSI 302 890-1 Addressed Elsewhere |
Facilities
ETSI 103 301 |
Security
|
|
TransNet
|
|||
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 | Adjacent |
Acknowledgement | True |
Cardinality | Unicast |
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 | Low | Moderate | Low | |
Basis | 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. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |