andy.zmolek@lge.com andy@zmolek.com
Todays Journey
1. The mobile paradigm 2. Lessons from the last paradigm shift 3. Mobile identity as paradigm extension
Extend the web - Consumer: Google, facebook Extend enterprise directory: AD, LDAP Mobile Virtualization Mobile Biometrics Near-Field Communications (NFC) Mobile Identity Databases (Neustar) Device-side: Hardware Supplier/OEM, OS/Technology Supplier, Cloud side: Operator, Cloud Service Provider
1.0
1. 2. 3. 4. 5.
2.0
3.0
Consumers drive disruptive innovation; enterprise follows later Enterprise-oriented ecosystems appear in the new paradigm Eventually the enterprise must adapt or lose competitiveness New market leaders emerge; few old-paradigm leaders survive Value creation and profit shifts toward software and solutions
Personal Computing
Equipment owned by enterprise or consumer Vendor selection by enterprise or consumer
Mobile Computing
Equipment more often consumer-owned (trend) Consumer typically drives ve ndor selection
No consumer use
Mobile identity systems shouldnt ignore this Web-based identity sucks on a mobile device
Poor usability, passwords less than ideal Mobile app paradigm exists outside web
Mobile Virtualization
One device, two (or more) identities Ensure privacy in the consumer experience
Keep personal calls and messages private Install consumer applications without restriction Maintain private personal cellular number
Mobile Biometrics
Low-cost fingerprint scanner
Autentec sensor looks like a trackpad or button Swipe in any direction, different directions or fingers for different functions, easy to use Delivered with the Motorola Atrix
Voice-based biometrics
Hands-free biometric easily run in smartphone Higher equal-error rate than others (~10%)
Near-Field Communications
What it is: simple information transfer
Very short range (nearly touching) - contactless card & reader Initialization and configuration of other wireless technologies as needed based on where you are and what you have
All mobile device operators send subscriber data to Neustar that links mobile E.164 (telephone) number to subscriber name with network data
Huge push to avoid commoditization on the device and cloud sides of the equation
Device-Side Opportunities
Hardware Supplier/OEM
Hardware to exploit: Multi-core ARM chipsets with strong security features: ARM A15 with virtualization extensions, sensors, NFC, etc. Smartphone OEM now has many now-cost options to integrate into their device; just add software
OS/Technology Supplier
OS mobile identity framework is best included in the OS Expose APIs to enterprise app developers to seed market Ride the coattails of NFC mobile payments initiatives
Cloud-Side Opportunities
Operator-based identity services
Natural extension of existing subscriber identity Also a natural adjacency to NFC-based mobile payments Could follow consortium model used by ISIS
Or mobile identity PLUS: mobile presence aggregation/distribution, or mobile payments and affinity program tracking, or mobile social networking services
Thank You
OPEN DISCUSSION