Smartphone Docking Stations and Strongly Converged VoIP Clients for Fixed Mobile Convergence

1. Smartphone Docking Stations and Strongly Converged VoIP Clients for Fixed Mobile Convergence Elliot Eichen, RezwanulAzim, S.CathyChang, Joe Geiger, James Flynn, Rafael Gaviria, Lee Goodman, GowthamJavaregowda, PunitaMishra, & Paul PerryVerizon Communications, Inc. Waltham, MA 02451, USA WCNC 2012: SAB01 paper 3April, 2012 elliot.eichen@verizon.com WCNC 2012: Title slide with the most characters!

2. Problem Statement: Le SmartPhone • Most “knowledge” workers have a phone like this (in fact most people will likely have a phone like this in the next 5 years). • It most likely has: • Your contacts (personal, work, etc.) • Your calendar. • Your IM, pictures (sometimes work related), location, and presence. • Several applications that you constantly use (and perhaps some of those are work apps.) • A telephone number that in most cases is your “personal” telephone number (personalidentity). • It’s mobile! • The voice quality is not great (particularly the speaker phone), it’s hard to use in an office environment, most enterprises think it’s a security risk, it often doesn’t use your work telephonenumber (your work identity) or work phone system. • It costs allot to make telephone calls compared to your enterprise phone and service.

3. Problem: Le DeskPhone • Most “knowledge” workers also have a phone like this (although this author believes that the number of workers with this type of phone will fall drastically in the next 5 years +/-. ) • Le DeskPhone has: • A telephone number that in most cases is your “work” telephone number (work identity), and • It works well with your Enterprise Call Server (PBX, etc.) • The voice quality is good (handset and speaker). • Enterprises think it’s a secure device. • It does not cost allot to make calls to/from it. • It’s an expensive, not terribly smart or useful, computer. • Users hate Le DeskPhone compared with Le SmartPhone: • It’s not mobile • It doesn’t have your contacts, presence, apps, pictures, IM, location, personal identity (MDN), ….. • It’s definitely not cool

4. The Solution: Le Docked SmartPhone The best of both worlds. • SmartPhone features (contacts, calendar, IM, etc.) available in the Enterprise environment. • DeskPhone features available to the SmartPhone: excellent voice quality, speakerphone, handset, buttons. Works with Enterprise Call Servers. • Dual Identity (Enterprise TN, Mobile DN) in both environments => symmetric (Strong) Fixed Mobile Convergence. • Significant Fixed and Variable Cost Savings • Enterprise Security

5. weak (traditional) FMC is not enough • Weak FMC is one way: • Enterprise Environment Mobile Environment (+/-) • Strong FMC is symmetric: • Enterprise Environment Mobile Environment • Enterprise Environment Mobile Environment • What does Enterprise Mobile mean ? • Calls to/from a Mobile MDN can be terminated/originated on the enterprise endpoint. • Speakerphones, coverage, high definition codecs, QoS,voice call continuity • Dual Persona: • Users choose the right identity to represent themselves. • The callING and callEDidentities are always correctly provided – enterprise or macro-cellular environments! • Examples: “My kids always call my wireless identity”, “My boss expects to see my enterprise identity when I call her.” • Strong FMC/dual persona supports “Bring Your Own Device” Model converged converged converged converged

6. Complete Solution Solution = Strong FMC + SmartPhone +Sophisticated VoIP client + Media/IP enabled dock + Call server integration • Strong (symmetrical) convergence: • Mobile MDN/features available in the Enterprise environment • Enterprise TN/features available in the Mobile environment • Preserves & present mobile (personal) and enterprise identities • Synergistic with partitioned (enterprise) desktops & BYOD handsets • Significant cost savings compared with VoIP handset (~ 30%) • Smartphones features and applications are available in both environments. • Enterprise & Conventional Apps • Contacts dB, Enterprise directory, Calendaring (Exchange, etc.) • Graceful migration to IMS (with or without VoLTE).

7. How does this work: circuit switched mobile integration • Dual SIP registrations (TN, and ghost MDN) to preserve identity and voicemail. Call control moved to the Enterprise Call Server when docked. • SMS continues to be delivered across the RAN. • Voice Call Continuity difficult, subject to post-dial circuit switched delay. • SS7 based integration also possible using AIN (WIN) triggers.

8. How does this work: IMS/VoLTE integration • Dual SIP registrations; call control remains in respective native networks • Voice call continuity, voicemail integration, and macro-cellular integration all considerably simpler in a VoLTE implementation. • Potential to support an RCS/RCSe based client for additional services.

9. Video

10. Dual Identity (dual persona) Dialer Screen • Choice of Calling Party Identity • “should this call be from my mobile TN, or my enterprise TN ?” In-Call Screen • Notification of Called/Calling Party Identity: screen pop on in-call, different ring tones. • “is this call to my mobile TN or my enterprise TN ?”

11. Sleeve based to adapt micro USB connector to phone geometries. Ethernet frames (from LAN) encapsulated in USB packets for transport of SIP, RTP to phone. Simple protocol for LEDs, key presses, and wideband audio. 911 support, mac address based dock config/localization. Docking Station Implementation • Split routing or route table manipulation to enforce enterprise security. • Auxiliary USB A port – DECT headsets with Electronic Hookswitch Control, tablets, keyboards, etc.

12. Sleeves Adopt to Smartphone Geometries 3G Phones: Sleeve not tilted 4G Phones (e.g. HTC): Sleeve tilted to accommodate front facing camera. Tablets or devices w/o sleeve – use the USB hub port on the side, or a universal sleeve with loose/wired connectivity.

13. Integration with Enterprise Applications • Directory Services (LDAP, Contact Integration, etc.) • H.264 video (SIP or IMS IR.94 profile) • Presence • Bridged Line Apperance • Virtual Desktops • e.g, MobileIron, VMWare, etc. • Hoteling/Enterprise specific location (emergency management systems) • Calendaring (Microsoft Exchange, Google, etc.) with auto conference bridge login. • Conferencing (including merged TN/MDN)

14. Customer Value Proposition • Cost: • ~ 25%-50% reduction in capital cost for enterprise VoIP deployments. • ~ 10%-30% reduction in operational expenses (Hoteling, MACD, endpoint management.) • Convergence • Wireless service and features available in enterprise environment, can take advantage of enterprise voice quality, QoS, lower cost of packet transport, etc. • Smartphone applications, contacts database available in Enterprise and Mobile environments. • Enterprise service and features available in the wireless environment, can take advantage of mobility. • Synergistic with Dual Persona / enterprise partitions, Bring Your Own Device. • Vision • Today: Dock your laptop in the office. Undock for mobility. Stay connected. • Tomorrow: Dock your phone in the office. Undock for mobility. Stay Connected.

15. Demonstrated a practical, endpoint based, strongly converged FMC solution. Supports both Mobile DN and Enterprise TN in both Enterprise and Macro-Cellular Environments. Combines the rich application space from a SmartPhone with the telephony services, functionality, and security of an Enterprise Desk Phone (and call server). Preserves callING and callED identities in both docked and undocked modes. (dual-persona). Implemented a low-cost, enterprise quality, media enabled, docking station: Significant customer value: ~ $200/endpoint cost savings (fixed), significant variable cost savings, ++ performance enhancement and end-user acceptance. . Summary:

16. Backup Slides

17. Fixed Mobile Convergence: A Long History • Traditional (“weak”) FMC: • Export Calls made to an Enterprise/Work TN => Mobile Endpoint • Calls from mobile endpoint => “originate” from an Enterprise TN Elliot’s phone rings, but he is not at his desk. Customer calls Elliot’s work TN Elliot is at the beach. An “agent” calls his mobile endpoint, and bridges the two call legs. Where he takes the call Call leg 2 Call leg 1 CallING Identity (TN, MDN) CallED Identity (MDN) CallED ‘public’ identity (TN)

18. Fixed Mobile Convergence: A Long History • Traditional (“weak”) FMC: • Export Calls made to an Enterprise/Work TN => Mobile Endpoint • Calls from mobile endpoint => “originate” from an Enterprise TN Elliot’s Customer Elliot’s not at work. Elliot’s at the beach. Call leg 2 Elliot’s mobile Call leg 1 Mobile Device calls “work”, and signals the intent to call his customer Telephony “agent”, acting on behalf of Elliot, calls customer and bridges call legs. Elliot’s customer see’s the call as originating from Elliot’s work identity (TN).

19. Fixed Mobile Convergence: A Long History • Traditional (“weak”) FMC: • Export Calls made to an Enterprise/Work TN => Mobile Endpoint • Calls from mobile endpoint => seen as “originating” from an Enterprise TN • Many “flavors” of weak FMC: • Dual Identity (two telephone numbers) • One Identity (mobile and enterprise endpoints have the same TN or MDN). • Two (private) identities, only one publicidentity (TN/MDN) • etc. • Many ways to deliver weak FMC • Many reasons customers want FMC • Identity hiding • Cost reductions • Improved functionality

20. Convergence at the Client: A Well Known Idea Email: example of M (cloud) x N (client) services • Subscriber can have multiple (M) email accounts, and can originate/terminate emails on any (N) devices. • Easy for most/all IP enabled cloud services, but difficult for legacy, circuit switched, services (including SMS) which are bound to endpoints. • Opportunity to enable client based convergence based on IP Telephony and the availability of high performance smart phones.