Page History

...

• Use case 1. Identity should be supported in multiple platforms including but not limited to AOSP. Some services that would be extended to individuals might not necessarily have all interactions go through AOSP on head unit but some may. A profile will need to be linked to an AOSP user account. 
• Use case 2. The individual or entity may have different roles with respect to one or more vehicles at a given time and subject to change. Roles include: owner (individual or company for eg shared mobility), manager (if a third party helps manage vehicle), operator (driver), passenger, recipient of digital key issues (may be passenger or actual operator), being key roles.
• Use case 3. Profile needs an associated identity comprised of legal name, nickname or shareable identifier (DID?) that masks name for privacy considerations, various other characteristics of the entity, preferences for HVAC, seat position, digital service subscriptions, identity provider for authentication, digital wallet for various automotive payment use cases (request input from that group in COVESA).
• Use case 4. A profile is an essential component for consent management, who is providing permission to use what data for which purpose (service) inside or out of the vehicle.