Differentiated connectivity and user consent for autonomous driving use case
Service providers provide connectivity services required by autonomous driving applications and service providers must abide by privacy regulations to collect subscribers’/users’ consent to allow applications to access the subscribers’/users’ data.
Overview
Service providers ensure subscriber/user privacy while exposing network capabilities to conform to the country's privacy regulations. The car can access differentiated network service capabilities and the autonomous car manufacturers benefit from service provider assets. The autonomous car driver or the autonomous car manufacturer has the regular subscription from the service provider.
Challenge
The autonomous vehicle application requires differentiated connectivity when going into autonomous driving mode. At the same time, 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 consent data and verify if their consent is given. Service providers get the consent of end users via the third-party application function (AF) to access sensitive information including location and QoS.
How it works
- The car owner/driver enables the autonomous driving service from the original equipment manufacturer (OEM).
- The network collects the consent data from OEM and stores it. For the car to be autonomous, QoS enhancement needs to be in place when the driver pushes the autonomous driving button.
- The autonomous application requests the QoS enhancement from the NEF (Network Exposure Function), and the NEF needs to validate the end user's consent before enhancing QoS.
- QoS is granted to the application and the autonomous driving service can happen smoothly.
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.
