Use Cases

From Auto


  1. Discover the list of APIs available to access for a specific Application
    • Description: Through the Web application running on IVI or user’s mobile device, user can access the vehicle data or services. Before that, it is necessary to discover which vehicle APIs are accessible to the Web application, since that the accessible vehicle APIs vary from application to application if the access control policy is implemented.
    • Motivations
      1. For the sake of vehicle security, each API should include access control to prevent applications without sufficient privileges from accessing to vehicle services. This results in that the accessible vehicle APIs vary from application to application. Therefore, a discovery API is needed for a specific application to discover the accessible APIs and even the attributes.
    • Pre-conditions
      1. Each vehicle API includes access control policy
      2. The granularity of this access control policy should be fine grained (per attribute). For example, the Door interface contains attribute "lock". The access control policy should specify the policy of “set” operation on "lock" state and “get” operation on "lock" state correspondingly
      3. Application has been assigned a privilege level
    • Post-conditions
      1. A unified data format is required to describe the accessible APIs. This can be done using JSON or XML
  2. Set a single vehicle resource value once from mobile device
    • Description: A user remotely changes setting of a selected vehicle resource once from the Web application running on user’s mobile device: the Web application running on user’s mobile device displays the vehicle resources that are available for user to set. A user selects the vehicle resource that user wants to set using the Web application. The Web application then calls the vehicle API to set the vehicle resource once.
    • Basic Flow
      1. Using the Web application running on the user’s mobile device, user selects vehicle resource that user wants to set.
      2. The Web application running on the user’s mobile device calls the vehicle API to remotely set the value of selected vehicle resource once in the connected vehicle.
      3. The Web application running on the user’s mobile device displays the “set” result to user.
    • Examples
      1. User remotely turns on the air conditioner from mobile device: Penny uses the Web application running on her mobile device to initiate request indicating that she wants to turn on the air conditioner in the vehicle. The Web application then calls the vehicle API to turn on the air conditioner of connected vehicle. Then Web application displays the result to her, indicating whether the air conditioner is on.
    • Motivations
      1. Sometimes, before entering the vehicle, user wants to remotely change the setting of some vehicle resources, like turning on air conditioner or heater. So user can get better experience after entering the vehicle.
    • Pre-conditions
      1. The Web application running on user’s mobile device and the vehicle have a communication channel over which they can pass messages, the connection can be in either protocol or transport—Bluetooth, WiFi, or cloud connections.
      2. The Web application running on mobile device has a mechanism that displays the vehicle resources available to set.
      3. The Web application running on mobile device has a mechanism that user can use to initiate vehicle resource set request.
      4. The Web application running on mobile device has an access control policy to determine whether user has the authority to set the selected vehicle resource.
    • Post-conditions
      1. None
  3. Subscribe to a single vehicle resource value from mobile device
    • Description: A user remotely subscribes to a selected vehicle resource from the Web application running on user’s mobile device: the Web application running on user’s mobile device displays the vehicle resources that are available for user to subscribe. A user selects the vehicle resource that user wants to subscribe using the Web application. The Web application then calls the vehicle API to subscribe the vehicle resource. Notifications will be published to web application running on user’s mobile device in time-triggered or event-triggered.
    • Basic Flow
      1. Using the Web application running on the user’s mobile device, user selects vehicle resource that user wants to subscribe.
      2. The Web application running on the user’s mobile device calls the vehicle API to remotely subscribe the value of selected vehicle resource in the connected vehicle.
      3. With time-triggered or event-triggered, notifications indicating the latest value of subscribed vehicle resource will be published to web application running on user’s mobile device, until the selected vehicle resource is unsubscribed.
      4. The Web application running on the user’s mobile device displays the received value to user.
    • Examples
      1. User remotely subscribes to the tire pressure value from mobile device: Jack uses the Web application running on his mobile device to initiate request indicating that he wants to subscribe the tire pressure value in the vehicle. The Web application then calls the vehicle API to subscribe tire pressure value of connected vehicle. Then notifications indicating the latest value of the tire pressure will be published to the Web application. Then Web application displays the tire pressure value to him, indicating whether his vehicle tire needs maintenance.
    • Motivations
      1. User may want to get notified the latest condition of some vehicle subsystems, like tire, battery. So user can determine whether vehicle needs maintenance.
    • Pre-conditions
      1. The Web application running on user’s mobile device and the vehicle have a communication channel over which they can pass messages, the connection can be in either protocol or transport—Bluetooth, WiFi, or cloud connections.
      2. The Web application running on mobile device has a mechanism that displays the vehicle resources available to subscribe.
      3. The Web application running on mobile device has a mechanism that user can use to initiate vehicle resource subscribe request.
      4. The Web application running on mobile device has an access control policy to determine whether user has the authority to subscribe the selected vehicle resource.
    • Post-conditions
      1. None


Edited by Qing An, from Alibaba Group

Email: anqing.aq@alibaba-inc.com

Retrieved from "https://www.w3.org/auto/wg/wiki/index.php?title=Use_Cases&oldid=20"