Personal identification — ISO-compliant driving licence — Part 6: mDL test methods
Introduction: The ISO/IEC 18013 series establishes guidelines for the design format and data content of an ISO-compliant driving licence (IDL) with regard to human-readable features (ISO/IEC 18013-1), ISO machine-readable technologies (ISO/IEC 18013-2), access control, authentication and integrity validation (ISO/IEC 18013-3), associated test methods (ISO/IEC 18013-4) and interface and related requirements to facilitate ISO- compliant driving licence (IDL) functionality on a mobile device (ISO/IEC 18013-5). It creates a common basis for international use and mutual recognition of the IDL without impeding individual countries/states in applying their privacy rules and national/community/regional motor vehicle authorities in taking care of their specific needs. ISO/IEC 18013-5 establishes interface specifications for the implementation of a driving licence in association with a mobile device. It specifies the interface between the mobile driving licence (mDL) and mDL reader and the interface between the mDL reader and the issuing authority infrastructure. This document gives requirements for testing of the compliance of the data model, device engagement, data transfer and security mechanisms on a mobile driving application with the requirements of ISO/IEC 18013-5. © ISO/IEC 2025 – All rights reserved
Scope: This document specifies test methods for testing conformity of a mobile driving licence (mDL) or an mDL reader to ISO/IEC 18013-5. This document specifies test methods for: — mDL on its interface to an mDL reader; — mDL reader on its interface to an mDL; — mDL reader on its (optional) interface to an issuing authority infrastructure. Test cases for an issuing authority infrastructure on its interface to an mDL reader are not included in this document. Test cases for the use of OpenID Connect (OIDC) by an mDL reader on its interface to an issuing authority infrastructure are not included in this document. This document only provides test cases for the use of WebAPI on this interface. This document only addresses the functional behaviour of an implementation under test (IUT) on its interface(s) in scope. It does not address: — the internal implementation of an IUT, such as a secure area in an mDL; — any functional requirements to an IUT not specified in ISO/IEC 18013-5, for example, requirements of a particular issuing authority; — non-functional aspects of the IUT, nor IUT interfaces not listed above, such as the interface from an issuing authority infrastructure to an mDL, used to provision mDL data.