The PAKoS research project delivers a comprehensive, end‑to‑end concept for personalising the interaction between drivers and autonomous vehicles. The technical core of the effort is organised into a series of work packages that culminate in a fully specified user‑profile system, a secure data‑exchange interface, and a user‑experience design that integrates mobile and vehicle‑side components.
In work package AP7a.1 the team performed a detailed requirements analysis and a heuristic evaluation of existing usage scenarios. The study identified the necessary functional elements for a digital driver profile, including driving behaviour, vehicle settings, and personal data. The team defined the target user groups and documented mental models of users interacting with autonomous or semi‑autonomous systems. A key outcome was the recommendation of suitable media and methods for transferring and securing profile data between vehicles, with a focus on automated and user‑controlled protection mechanisms. The results are captured in the “Anforderungsanalyse zum Nutzerprofil” document and satisfy the package’s objectives of specifying user groups and recommending technology for data transfer.
Work package AP7a.2 focused on user‑experience conception and interface design. Storyboarding and paper prototyping established the flow of profile transfer, while information architecture and interaction design defined all application functions and user paths. Wireframes for every page type were produced, and visual design elements such as colour, typography, and iconography were finalised. The team also defined application cases between user, vehicle, and backend—including a blockchain component. Although a click‑through prototype was omitted due to an earlier implementation phase, the extensive set of wireframes and design specifications fully meet the requirement to specify the information architecture and interactions. These results are documented in “Anwendungsfälle, Interfacegestaltung und UX”.
In AP7a.3 the interface for importing and exporting user profiles between vehicle and external device was defined. The team negotiated with Bosch to explore a realistic implementation of the interface and transfer concept. Two transmission approaches were specified: a TCP/IP protocol for reliable delivery and a UDP protocol for low‑latency, event‑based communication. The local network architecture, trigger events, packet contents, and data encoding for UDP were detailed. A security analysis of the interface was also performed, ensuring compliance with the safety requirements outlined in AP12. The outcome is a technically sound, secure interface specification that enables seamless profile exchange.
Earlier work packages laid the foundation for these results. AP1.1 involved requirement definition and user surveys conducted by mVISE, Bosch, and Stadtmobil, establishing the need for personalised driver‑assist functions and the communication of user needs. AP4.1 identified the relevant features to be stored in the user profile, defining application fields such as persona, user needs, and product applications, and specifying the parameters required for their capture. AP7.1 contributed to the overall concept for personalisation and adaptation, focusing on aligning vehicle and profile settings through the mobile application or the vehicle’s MMI.
Collaboration across the project was coordinated through regular meetings between project management, design, development, and partner teams. The primary partner, mVISE, brings extensive experience in mobile B2B, B2C, and IoT solutions, and leads the user‑centric design and agile development efforts. Bosch provides expertise in vehicle‑side integration and interface design, while Stadtmobil contributes knowledge of shared‑mobility contexts. The project is funded through a grant that supports the personnel and coordination costs associated with these activities. Together, the partners deliver a cohesive, technically robust framework for personalising autonomous vehicle interactions.