ITS Object --> Service Monitor System:
system status
Definitions
system status (Information Flow): Monitoring of system device status including current mode, operational status, and configuration settings. It includes device housekeeping/heartbeat monitoring and includes network information, the status of installed applications, and the configuration of managed devices.
ITS Object (Source Physical Object): The general 'ITS Object' includes core capabilities common to any class of object.
Service Monitor System (Destination Physical Object): The 'Service Monitor System' represents one or more center-based systems that provide monitoring, management and control services necessary to other applications and/or devices operating within the Connected Vehicle Environment. These support services enable other applications to provide transportation services.
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)
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 | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | High | High | High | |
Basis | System operational status information could be used to either initiate or confirm attacks, leading to significant downtime of related C-ITS systems. | System status information needs the greatest possible correctness, as if it is incorrect then inappropriate actions may be triggered that, for large backoffice and core systems, have widespread repurcussions. | Monitoring of system operational status has the highest possible needs for availability, as without an understanding of system state it is difficult to impossible to manage the system. This rating may be downgraded for end entities whose performance are not critical to high-value user needs. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |