Vehicle Operations and Service Center --> Vehicle:
vehicle automation commands

Definitions

vehicle automation commands (Information Flow): Direction to an automated driving system to perform vehicle control actions

Vehicle Operations and Service Center (Source Physical Object): 'Vehicle Operations and Service Center' (VOSC) represents centers that provide telematics services to vehicles using wide-area (e.g. cellular) communications, including traveler information, emergency services, vehicle diagnostics, over-the-air software updates, vehicle maintenance information and warnings, remote vehicle operation, and provision of service options for these vehicles. See also 'Transportation Information Center' that provides traveler information, trip planning, and routing services and 'Emergency Management Center' that provides call-taking and emergency response services that may also be implemented by a VOSC.

Vehicle (Destination Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

This Triple is an instantiation of the more general triple:

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:

  • None

This Triple has the following triple relationships:

None

This Triple is an instantiation of the more general triple:

Communication Solutions

  • No communications solutions identified.

    • This Triple is an instantiation of the more general triple:

    Characteristics

    CharacteristicValue
    Time Context Now
    Spatial Context Regional
    Acknowledgement True
    CardinalityUnicast
    InitiatorSource
    AuthenticableTrue
    EncryptTrue


    InteroperabilityDescription
    RegionalInteroperability 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).

    This Triple is an instantiation of the more general triple:

    Security

    Information Flow Security
      Confidentiality Integrity Availability
    Rating Moderate Moderate Moderate
    Basis Vehicle commands should result in vehicle movement, which is directly observable. There may be instances where remote monitoring of these instructions enables a nefarious use case, which suggests a MODERATE level of obfuscation is reasonable, as the impact is likely limited to a single vehicle with no safety impact. This flow directs vehicle movement, so needs to be unaltered lest the vehicle behave unexpectedly. There must always be a fallback for a driveable vehicle though, suggesting MODERATE at most. Availability will depend on the parking structure; in some cases this will be MODERATE, in others LOW, depending on how much automated movements facilitate parking opreations.


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt True