Commercial Vehicle OBE --> Commercial Vehicle Service Provider Center:
mass declarations
Definitions
mass declarations (Information Flow): Australia-specific flow
Commercial Vehicle OBE (Source 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.
Commercial Vehicle Service Provider Center (Destination Physical Object): The 'Commercial Vehicle Service Provider Center' is an Australia-specific physical object that provides data exchange and commercial vehicle tracking services to other parties involved in commercial vehicle management. It also manages CV OBEs and the operational software on those devices.
Included In
This Triple is in the following Service Packages:
This Triple is described by the following Functional View 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 Wireless Internet (EU) (32)
-
(None-Data) - OASIS MQTT over Wireless (42)
-
(None-Data) - OASIS AMQP over Wireless (45)
Selected Solution
(None-Data) - OASIS AMQP over WirelessSolution Description
|
ITS Application Entity
Development needed  |
Click gap icons for more info.
|
||
|
Mgmt
Development needed |
Facilities
Development needed OASIS AMQP |
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 | Regional |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | True |
| 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 | Moderate | Moderate | Low | |
| Basis | This contains characteristics of the load, which may be competitive. If intercepted by a competitor or other third party with interest, could be used in anti-competitive fashion. Impact limited to the business of the operator/carrier so compromised however, so limited to MODERATE. | Since this is used for regulatory purposes, receiver should be assured of correctness. If this were intercepted and modified or corrupted, the operator may be incorrectly accused of regulatory violation, which would impact his business. Limited in scope to the operator so compromised. | Probably does not need to be updated often; so long as it can be instantiated occasionally, likely no impact on loss of this flow. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |