host transit vehicle status
This CVRIA application interconnect encapsulates all of the Layer 2 information flows associated with a particular application object interface. In this case, there is only a single Layer 2 flow associated with this interconnect, so the Layer 1 application interconnect name and the Layer 2 information flow name are both 'host transit vehicle status'.
Source Physical Object |
Source Application Object |
A-Interconnect |
Destination Physical Object |
Destination Application Object |
Bidirectional? |
Transit Vehicle Databus
|
|
host transit vehicle status
|
Transit Vehicle OBE
|
Transit Vehicle Emissions Monitoring
|
False
|
The above quintuple includes flows:
Source Physical Object |
Source Application Object |
A-Interconnect |
Destination Physical Object |
Destination Application Object |
Bidirectional? |
Transit Vehicle Databus
|
|
host transit vehicle status
|
Transit Vehicle OBE
|
Transit Vehicle On-Board Connection Protection
|
False
|
The above quintuple includes flows:
Source Physical Object |
Source Application Object |
A-Interconnect |
Destination Physical Object |
Destination Application Object |
Bidirectional? |
Transit Vehicle Databus
|
|
host transit vehicle status
|
Transit Vehicle OBE
|
Transit Vehicle On-Board Paratransit Operations
|
False
|
The above quintuple includes flows:
Source Physical Object |
Source Application Object |
A-Interconnect |
Destination Physical Object |
Destination Application Object |
Bidirectional? |
Transit Vehicle Databus
|
|
host transit vehicle status
|
Transit Vehicle OBE
|
Transit Vehicle On-Board Trip Monitoring
|
False
|
The above quintuple includes flows:
Source Physical Object |
Source Application Object |
A-Interconnect |
Destination Physical Object |
Destination Application Object |
Bidirectional? |
Transit Vehicle Databus
|
|
host transit vehicle status
|
Transit Vehicle OBE
|
Transit Vehicle Passenger Counting
|
False
|
The above quintuple includes flows:
Source Physical Object |
Source Application Object |
A-Interconnect |
Destination Physical Object |
Destination Application Object |
Bidirectional? |
Transit Vehicle Databus
|
|
host transit vehicle status
|
Transit Vehicle OBE
|
Transit Vehicle Schedule Management
|
False
|
The above quintuple includes flows:
Source Physical Object |
Source Application Object |
A-Interconnect |
Destination Physical Object |
Destination Application Object |
Bidirectional? |
Transit Vehicle Databus
|
|
host transit vehicle status
|
Transit Vehicle OBE
|
Transit Vehicle Signal Priority
|
False
|
The above quintuple includes flows: