Management and Use of Identities in Mobility and Transport Powered by NFC Technology
0 likes143 views
The document discusses the integration of NFC technology in managing identities for Mobility-as-a-Service (MaaS) and urban transport solutions, emphasizing the increasing demand for seamless multi-modal travel experiences. It outlines a Market Requirements Document (MRD) that details business processes and NFC use cases essential for maintaining customer identities and enhancing service interoperability. Furthermore, it highlights the potential of NFC technology to address urban mobility challenges and improve transport services while fostering cooperation among different transport operators.
Management and Use of Identities in Mobility and Transport Powered by NFC Technology
- 1. SPEAKERS Preeti Ohri Khemani Infineon Technologies MIT SIG Chair Hisayoshi Endo Dai Nippon Printing MIT SIG Vice Chair
- 2. The NFC Forum mark is registered in the U.S. and other countries. MANAGEMENT AND USE OF IDENTITIES IN MOBILITY AND TRANSPORT POWERED BY NFC TECHNOLOGY Hisayoshi Endo, Dai Nippon Printing, NFCF MIT SIG Vice Chair
- 3. MANAGEMENT AND USE OF IDENTITIES IN MOBILITY AND TRANSPORT: MRD FOR NFC USE-CASES ● Today, multi-modal travel and Mobility-as-a-Service (MaaS) is a major global trend ● Customers demand transport service offers that include all phases of the journey from the start to the final destination ● In addition to public transport services, modes of transportation like taxi, car rental or car sharing, bikes, scooters or ride sharing must be supported ● The Market Requirements Document (MRD) describes business processes and NFC use-cases which support a consistent ID concept for use in system solutions for MaaS and names requirements to NFC products which may result from these use- cases ● MRD published in December 2020 NFC Forum Releases First Comprehensive Electronic Identification for Mobility-as-a-Service Document
- 4. MANAGEMENT AND USE OF IDENTITIES IN MOBILITY AND TRANSPORT: MRD FOR NFC USE-CASES ➢ Generation of identities and identifiers for customers, customer media and applications which are specifically designed for PT and MaaS-purposes ➢ Consolidation of existing customer identities in order to achieve a defined level of trust ➢ Enhancement of existing sets of customer ID attributes according to the needs of certain modes of transportation (e.g. validity of the customer’s driver license for car rental or car sharing) ➢ Maintenance and management of identities and related attributes ➢ Provisioning of identities and ID attributes for use by partners of the mobility platform and other transport service providers
- 5. This diagram provides an example for a customer identity IDc which is specifically designed for the mobility market.
- 6. IDENTITY OF MAAS CUSTOMER-IDC
- 7. MAIN BUSINESS PROCESS FOR MOBILITY ID MANAGEMENT 1. Business process A - Definition, implementation and maintenance of the ID service 2. Business process B - Partner life cycle management 3. Business process C - Identity management and identity provisioning
- 8. DEPICTION OF BUSINESS PROCESSES BP-C.4 - ID service to internal and external Mobility Partners BP-C.2 - Managing IDc and IDx BP-C.1 – Enrolment of the IDc System of the external partner System of internalpartner Legend: 3. Customer request to establish IDc BP-C.3 - IDc, IDx status monitoring, exception handling UC-C.4.1 – ID service to internal partners - Staging of IDc and IDx as agreed with internal MobilityPartners UC-C.4.2 – ID service to external partners - Staging of derived IDc or single IDc attributes to external MobilityPartners Use of derived IDc or single ID attributes by external Mobility Partners Use of IDc (incl. IDc attributes), IDx by JRE services Use of external IDx or single IDx attributes by external Mobility Partners UC-C.4.3 – Integration of external mobility services - Staging of specific IDx attributes for external MobilityPartners UC-C.2.2 – Enrol / update attribute values by direct entry JRE ID service UC-C.1.3 - Establish ID service account UC-C.1.2 – Consolidation of IDc, IDx, trust scoring (for ID service use) UC-C.2.3 - Enrol / update attribute values from trusted sources UC-C.2.5 –Manage IDx UC-C.2.4 – Enrol / manage dynamic attributes UC-C.1.2 – Consolidation of IDc, IDx, trust scoring UC-C.3.1 – Customer status monitoring and exception handling UC-C.3.2 – Partner status monitoring and exception handling UC-C.2.6 – Terminate IDc UC-C.2.7– Manage ID service account online UC-C.3.3 – IDc or IDx updates from internal partners BP-B.1 – Onboarding of partners Alignment for interoperability of interfaces and media BP-B.2 –Operations Alignment on commercial and technical scope and terms Updateor consolidationrequest Statusor exceptionmessage Reporting of status / exception messages Reporting of status and exception messages, IDc or IDx updates BP-B.3 – Seizing the cooperation Unwinding of services and processes BP-A.1 – Definition and implementation of the system BP-A.2 – Import of existing ID and ID attributes Documentation of requirements to the ID service and the system BP-A.3 – ID service operations Specification and implementation of functions and system incl. trust levels and trust scoring Operations as defined in business processes A, B Business process A Definition, implementation and maintenance of the ID service Business process B Partner life cycle management Business process C Identity management and identity provisioning Ext. ID service option) Suica eID service operations as defined in business process C Request Customer permission UC-C.1.2 – Consolidation of IDc, IDx, trust scoring (preliminary candidates) 1. ID provider dadarequest UC-C.1.1 –Retrieval of ID informationfrom internal partners UC-C.1.2 – Consolidation of IDc, IDx, trust scoring (preliminary candidates) ID Provider data request UC-C.1.1 – Retrieval of ID information from internal partners 2. Notification by partner UC-C.3.4 – IDc attribute value updates from external Identity Providers UC-C.2.1 – Sign-in to ID service account
- 9. MRD STEPS 1. Use cases and functional requirements • Define remaining use cases • Derive functional requirements to system components from use cases 2. Trust categories acc. to eIDAS • Criteria for measuring trust of data enrolment → requires knowledge about common procedures that have been used so far. • Technical criteria acc. to eIDAS, BSI recommendations
- 10. The NFC Forum mark is registered in the U.S. and other countries. THE FUTURE OF MOBILITY ENABLED BY NFC Preeti Ohri Khemani, Infineon Technologies, NFCF MIT SIG Chair
- 11. THE FUTURE OF MOBILITY AS THE WORLD BECOMES INCREASINGLY URBANIZED ● According to the United Nations, 55% of the global population were city-dwellers in 2018; that number is expected to grow to 68% within 30 years.* ● By 2030, the world is projected to have 43 megacities, each with 10+ million inhabitants ● Increasingly dense concentration of populations poses challenges for urban mobility ● Urbanization also offers new opportunities for mobile operators and their partners ● NFC technology can help cities overcome the challenges and take advantage of the opportunities *https://www.un.org/development/desa/publications/2018-revision-of-world-urbanization-prospects.html
- 12. NFC+MAAS= URBAN MOBILITY SOLUTION Easier transport access More affordable, efficient public transport operation Broader transport interoperability Better, more up-to-the-minute commuter information Better support for visitors and tourists More frictionless commerce Major mobility-related needs: NFC-enabled Mobility-as-a-Service (MaaS) fulfills these needs
- 13. ENABLING MAAS & PURSUING NEW GROWTH OPPORTUNITIES Standardization and guidance on additional higher system levels that interoperate to provide more seamless user experience. Cooperation between alliances and standards bodies. The foundation for collaboration and innovation has been laid by the NFC Forum over the last 15 years. Interoperability through open standards enables any market player to employ a sustained and flexible base layer of technology that ensures consistent performance for an urban MaaS solution.
- 14. PAVING THE WAY TO A SEAMLESS TRAVEL EXPERIENCE NFC Forum Certification Program paves the way for MaaS because it confirms that devices, tags, and public transport readers are compliant with NFC Forum specifications NFC Forum certification offers benefits that help ensure seamless travel experiences for both service providers and users ▪ Assured performance for your users ▪ Reduced customer support costs ▪ Increased ability to offer new, value-added services STEPS TO CERTIFY
- 15. FUTURE OF MOBILITY NFC FORUM RESOURCES The Future of Mobility Driven by NFC NFC Transforms Urban Mobility for Billions
- 16. NFC MOBILITY USE CASES ● Forward-thinking transport operators are already paving the way for MaaS and enhanced mobility services ▪ Nobuo Nishioka, JR-EAST ▪ Louis Brosse, Wizway Mobile Ticketing ▪ Steve Holden, ITSO ▪ Nicole M. DuPuis, APTA ▪ Philippe Vappereau, Calypso ▪ Stephanie Depraz-Depland, Conduent