Figure 1: Android device Management
EMM Console is a web application allowing IT administrators to handle all enterprise-managed mobile devices and on-device apps via Android Management APIs. Using these APIs, applications can manage (create, delete) an enterprise profile, assign managed devices, and manage (create, delete, enforce, modify) policies on managed devices. Android Management APIs can also be used by EMM service providers such as Google, SOTI, and Airwatch to extend available products and services.
In addition to device management, Google offers enterprise customers Managed Google Play, an enterprise version of the Google Play Store. Featuring mostly business apps, Managed Google Play is integrated into EMM Console, allowing enterprise users to download and install business apps that have been approved by IT administrators.
Similar to Managed Google Play, enterprise devices use Firebase, a cloud platform by Google that provides cloud functions for applications and services on Android devices. Firebase functions include storage, analytics, remote configurations, and messaging.
Device policies are resources of Android Management API to restrict operations and access on managed devices. Some of these policies are application installation enable/disable, connectivity enable/disable, and camera enable/disable. The Device Policy Controller (DPC), with help from a DPC library, acts as a bridge between the EMM Console/Server and managed device. DPC provisions Managed Google Play accounts and managed configurations for approved apps. This framework can also be used to manage automobile IVI systems, including allowing only approved applications, and complying with ever-growing safety regulations.
Android Framework Can Manage Driver Safety Protocols
Human interest and government regulations place maximum priority on driver safety. While safety regulations are often region specific, and vehicle OEMs are obliged to follow each region’s specific requirements, these regulations change frequently, making it challenging to comply.
The IVI is one domain where safety aspects can be addressed. AAOS is already used extensively in IVI. One of the key safety features in the AAOS is a framework and mechanism for driver distraction avoidance (DDA). Google has published Driver Distraction Guidelines (DDG) that must be followed for applications running on Automotive Android stack (AAOS).
Restrictions are dependent on multiple factors such as car driving state, car speed, and management and restrictions for multiple displays:
Car Driving state
Features and Actions are allowed based on car driving state – Parked or Idling or Moving
- Parked: Gear is in Park mode
- Idling: Gear not in Park mode and speed is zero
- Moving: Gear not in Park mode and speed is non-zero
Restrictions are based on the speed of the car
- Minimum Speed
- Maximum Speed
Display id in case of multiple displays
- Head Unit display
- Rear Seat Passenger Display
The restrictions are configured in AAOS and applied to Automotive Android applications, which are forced to follow these restrictions. This is how OEMs are enforcing regulations now. Yet while AAOS has a process to enforce policies, it will still need software updates to comply as policies change.
Components involved in AAOS for this feature