Remote Vehicle Operator --> Vehicle Operations and Service Center:
remote operator input

Definitions

remote operator input (Information Flow): User input from the remote vehicle operator including requests for information, configuration changes, remote vehicle control actions, and other operations data entry related to remote vehicle operation.

Remote Vehicle Operator (Source Physical Object): The 'Remote Vehicle Operator' represents the person or people that support remote vehicle control, monitoring the controlled vehicle and it's surrounding environment and providing control commands for use by the automated driving system in the remote vehicle.

Vehicle Operations and Service Center (Destination 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.

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
    None defined


    InteroperabilityDescription
    Not ApplicableInteroperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability.

    This Triple is an instantiation of the more general triple:

    Security

    Information Flow Security
      Confidentiality Integrity Availability
    Rating Moderate High Moderate
    Basis While it is unlikely this has any safety impact, it may betray commercial operations, so should be protected for competitive reasons, and potentially for privacy reasons depending on the configuration of the vehicle. If this flow is incorrect or unavailable remote operations will be negatively impacted, which can also impact surrounding vehicles; it may have a negative impact to convenience and safety, which could be MODERATE or HIGH depending on the type of vehicle, what it is carrying and where it is. If this flow is incorrect or unavailable remote operations will be negatively impacted, which can also impact surrounding vehicles; it may have a negative impact to convenience and safety, which could be MODERATE or HIGH depending on the type of vehicle, what it is carrying and where it is.


    Security CharacteristicsValue