Skip navigation
Autonomous individual vehicle.

Quality on Demand (QoD) API for the automotive industry

Smart Car Applications Connectivity with Privacy-Compliant Network information

Smart cars can leverage 5G network capabilities, such as differentiated connectivity and access to device location and status, while ensuring compliance with privacy laws. Service providers, in collaboration with car manufacturers, can obtain user consent through third-party applications to offer enhanced services, including infotainment, with privacy safeguards in place.

Overview

Smart cars and autonomous vehicles are becoming more advanced, and it's important to protect user privacy while using network features according to the country's privacy laws. Smart cars, equipped with advanced technologies, can access differentiated network service capabilities, including the ability to track device location and device status, which enhances functionality and user experience. Autonomous car manufacturers can benefit from these service provider assets, optimizing vehicle performance and connectivity. Additionally, smart car owners can subscribe to premium services offered by the manufacturer, which can include infotainment options, making the driving experience more enjoyable.

Challenge

The smart car application requires differentiated connectivity when infotainment is invoked. It also requires access to location information and device status for enhanced map information. The service provider must abide with each country's privacy laws to expose user data.

Solution

The service provider can collect the end user's privacy data permission and verify if their privacy data permission is given. Service providers get the privacy data permission of end users via the third-party application function (AF) from the smart car manufacturer to access sensitive information including location, device status and QoS.

How it works

  1. The car owner/driver enables the smart car application from OEM.
  2. The network collects privacy data permission data from OEM and stores it. For the smart car application to work properly, QoS/Device Status/location needs to be requested from the network.
  3. The smart car application requests QoS/Device Status/location from the SEE, and the SEE needs to validate the end user's privacy data permission before providing the information back.
  4. QoS/Device Status/location is granted to the application, and it can then work as intended.

Business applications

The main target segment for this use case is the enterprise segment, specifically vehicle manufacturers, fleet management and developers creating applications for the automotive industry.

Business models

Service providers can monetize based on two different models:

  1. Wholesale (towards the aggregator)
  2. Subscription (towards the enterprise)

 

APIs in use

  • CAMARA Quality on Demand (QoD)
  • CAMARA Device Location Verification
  • Device status
  • Proprietary privacy data permission APIs