White Paper. enabling IP communications

Transcription

1 White Paper enabling IP communications mcue TM : Delivering on the Promise of Seamless UC/FMC Mobility August 2008

2 Table of Contents I. Introduction...3 II. UC and FMC in Different Mobility Scenarios...3 III. mcue: A Universal Client for Unified Communications and Converged Services...7 IV. mcue: The Ideal Solution for Mobile UC/FMC Deployment Copyright 2008 All Rights Reserved 2

3 I. Introduction Only five years ago the enterprise user and the general consumer had a different set of requirements for a communications system -- now that gap is narrowing. Today, both types of users want continuous, alwaysavailable connectivity to mobile networks that offer a full menu of today s advanced communication services, such as voice, IM, presence, contact lists, corporate extension directory lists, call control features, push-to-talk, , browsing, calendar and synchronizing of personal information. Yet there are variances between the two user groups, such as network access modes (cellular, Wi-Fi, WiMax, etc.) and the hierarchy of user services. For example, enterprise users may want to see their extension directories with presence; while outside the enterprise they may want access to Skype or their enterprise unified communications (UC) service features (i.e., IBM Lotus Sametime) using their home Wi-Fi or cellular WAN. Teenage consumers may not care about anything other than their ability to text-message on a service like Yahoo!, regardless of their location. Other users may require access to multiple IM/VoIM services such as AIM or GoogleTalk because their buddies prefer different services. Additionally, they may need to maintain another list of contacts that are reachable via traditional circuit-switched mobile telephony and SMS. To address this broad range of end user needs, access modes and locations, the creation of a universal communications client for a multi-mode mobile device offers a logical solution. Because of the number of different hardware architectures and operating systems that can be used as a platform for mobile devices, such as Linux, Symbian and Windows Mobile, this universal client needs to have the ability to easily port across multiple platforms. This paper identifies and explores some of the key end user scenarios enabled through a merger of UC with fixed mobile convergence (FMC) in relevant end-to-end service provision architectures and the need for creation of a universal mobile communications client. The following three important considerations are touched upon: - where users access services (home or work) - how they access services (Wi-Fi, GSM) - what services users are most likely to use and want The paper subsequently highlights some key architectural features and end-user functionality of mcue, a universal client for mobile UC/FMC created by D2 Technologies, Inc. and concludes with a brief discussion how the concept of a universal client, such as mcue provides the ideal solution for mobile UC/FMC. II. UC and FMC in Different Mobility Scenarios Unified Communications is the combination of presence and availability with voice, instant messaging, and video services, making communication easier between different types of users such as enterprise employees, customers, partners, friends and family. There are key trends in the UC and FMC marketplace today that are worth noting: UC is gaining momentum with many companies either deploying now, or have plans in the near future. It s already being promoted in the enterprise by industry titans such as IBM and Microsoft, and hosted PBX and software technology vendors are mounting stiff challenges to these leaders. Studies have shown that lack of mobility is perhaps one of the last barriers to rapid adoption of UC. Mobility is becoming a systemic part of enterprise communications. CIOs are actively considering strategies to enable enterprises to go mobile. They also comprehend the important role that UC plays in this, as business processes are already showing signs of being communications-enabled (presence, click-to-im). According to Forrester Research, 20 percent of enterprises today expect to buy hosted and managed UC/FMC services. Interoperability and management issues will continue to drive this trend. Copyright 2008 All Rights Reserved 3

4 Mobile UC solutions today and going forward have to address the problem of managing presence information from an increasing multiple of communication services and sessions. Enterprise FMC is being promoted by major OEMs and a number of startups. Specialty FMC infrastructure equipment vendors have already extended PBX functionality to mobile phones for voice call continuity, and established IM/presence and collaboration tools. Clearly, this indicates a convergence between FMC functionality and UC services. Pre-IMS FMC (or dual mode service) for consumer markets is being launched by incumbent wireless operators and also by competitive service providers. Eventually, this market will be served by a rich set of IMS services such as VoIP, IM, music/video streaming, games, device management and DRM. Traditional wireless carriers are also attempting to offer hosted UC services with FMC capabilities to enterprises, such as Orange s Business Together service. Specific UC and FMC needs may manifest differently in various user situations and end-to-end service provision architectures. In an enterprise setting, it may mean that employees can use IM to communicate with each other while sharing documents through a standard enterprise-wide tool like IBM Lotus Sametime, or use an IP PBX to make Voice-over-IP calls, check s and even video conference. While these services were typically available on work desktops through a fixed VoIP phone or a PC, enterprises have recognized the business process improvement benefits of making the same services available on mobile devices, enabling employees to roam within the premises using the enterprise Wi-Fi network or outside of it using the WAN. This is, in effect, a manifestation of FMC as it relates to the enterprise, and creates the need for secure wireless access to the enterprise UC/FMC infrastructure. Enterprises may own, co-locate and manage the UC infrastructure, or they may choose to have it provided and managed by a hosted communications service provider. Enterprises may also dictate policies outlining when, where and the type of applications allowed to be used on such devices. (Figures 1 and 2 illustrate examples of on-site and hosted solutions for the enterprise.) Some of the key end user scenarios that need to be addressed in either of these solutions are as follows: All of the UC services and applications normally available on a PC or desk phone need to be available on a handset, so that it can show contacts (enterprise UC/ IP PBX extensions and 3 rd party IM/VoIM buddies) show presence on a per service basis voice call (IP PBX, SIP VoIP service using Wi-Fi access) with n-digit dialing offer IP PBX first party and third party call control functions deliver enterprise IM services facilitate access to and browser provide collaboration tools (browser or non-browser based) access business process applications integrated with UC If the user is outside of the enterprise premises and connects to enterprise over a WAN, the user gains secure access to all the above. The handset also has single number reach (sometimes known as Find Me/Follow Me), so that the user is accessible via the enterprise IP PBX extension anywhere. He or she can also call other extensions and perform call control functions, such as call transfer and voic . Voice call and data session continuity when the user moves between Wi-Fi and WAN coverage Some of the key nodes that enable the above scenarios are the enterprise IP PBX with PSTN gateway, the UC server and the Voice Call Continuity Application server (VCC-AS). If an employee accesses the enterprise via a WAN (for instance, using GSM), some of the features such as third party call control, configuration, IM and presence require a WAN data connection (in this case, using GPRS) into the enterprise in addition to requiring a circuit-switched GSM voice connection via the PSTN gateway. This data connection needs to be secure and Copyright 2008 All Rights Reserved 4

5 will traverse the enterprise firewall. The WAN carrier s IMS and packet data core network will play a supporting role in achieving this connectivity. Figure 1: End-to-End Scenario for Enterprise UC/FMC (On-Site) Copyright 2008 All Rights Reserved 5

6 In Figure 2, all the significant nodes like the IP PBX switch, UC server and VCC-AS are hosted by the service provider. The carrier s IMS core may play a more significant role in this solution architecture. A secure link is required between the enterprise network and the carrier s core packet data network. Figure 2: End-to-End Scenario for Enterprise UC/FMC (Hosted) In a more consumer-oriented UC/FMC scenario (shown in Figure 3), users would have a single number where they could be reached with a voice call, at home or on the road. They would have access to their favorite IM services anywhere, do near-real time voice chat, share video in real-time and have communication capabilities tied into other services such as navigation, web browsing and media streaming. A service provider would then need to enable multi-modal access and route user traffic into a common IP service/application delivery and management platform like IMS within its core infrastructure. Routing traffic from the point of access back to the service provider s core IMS infrastructure may involve traversal through multiple networks owned by business entities other than the service provider, thereby necessitating security and access authentication protocols. For this reason, service providers may restrict what applications are available to users or they may have a fully open access model. Some of the key user scenarios addressed by this solution are: Consumer has access to advanced communications services via a service provider when connecting at home or on the road, such as at a Wi-Fi hotspot, including IM/Chat with presence on multiple services (Google, Yahoo etc) voice calls (VoIP over Wi-Fi, CS voice over GSM) SMS text messaging video/music streaming and download real-time (or other) video sharing browsing ability to access multiple communications features simultaneously, such as IM and voice calls while browsing the internet or using games Voice call continuity Copyright 2008 All Rights Reserved 6

7 Figure 3: End-to-End Scenario for Consumer UC/FMC Prosumers are consumers who are, at times, more like enterprise users. Depending on time, place and context, their access and usage needs may be best served by either the enterprise or a consumer end-to-end architectural solution. Due to their varying communication and access needs, dictated by their location and usage context (i.e., accessing enterprise UC services or having an IM session with a friend from a public Wi-Fi hotspot), an architectural solution that can meet the needs of both usage patterns is needed. A service provider with an advanced Pre-IMS or IMS core is capable of providing hosted enterprise UC services as well as general UC for consumers simultaneously, as shown in Figures 2 and 3, as the architectures can be combined. III. mcue: A Universal Client for Unified Communications and Converged Services Today, device manufacturers (OEMs and ODMs) for smartphones and higher end feature phones need to address three types of end users: enterprise users, consumers and the crossover segment between the two, known as prosumers. At the same time, they need to achieve economies of scale by selling device models in large volumes while driving down development costs. One way to achieve these goals is to use software that can universally address the needs of each target end-user segment and that is easily portable across product lines using a common framework, e.g., a managed language framework like Java, and that maintains a consistent roadmap for hardware (SoC) platforms and operating systems, like Linux. D2 Technologies mcue software solution combines an innovative, patent pending communications user interface (CUI) with the company s vport MP IP communications software platform to address the needs of OEMs and service providers delivering integrated Fixed Mobile Convergence (FMC) and Unified Copyright 2008 All Rights Reserved 7

8 Communications (UC) functionality. mcue is specifically designed for mobile embedded devices, making it an ideal platform for smartphones and upper-end feature phone class devices. One of the key features of mcue is its ability to concurrently support multiple protocols that are used to support multiple communication modes such as VoIP, Instant Messaging and Presence. Examples of such protocols and services in the voice service mode include IETF SIP-based VoIP commonly used in enterprise IP PBX systems, IMS SIP-based VoIP used in IMS based wireless carrier data networks, and third party VoIM services (e.g. Skype and GoogleTalk). In the Instant Messaging service genre, similar examples include XMPP (used by some enterprise UC systems and Gizmo), SIMPLE (planned in IMS based WAN carrier networks), and Jabber (used in GoogleTalk). To the mcue end user, this manifests in the ability of the user interface to support multiple simultaneous sessions of the various available IP communication modes across different service providers and enterprise UC/IPPBX equipment. Its revolutionary user interface, built on top of a multi-identity, multi-session, multi-protocol engine, enables users to simultaneously log in into multiple different communications services such as SIP, Google Talk, Yahoo!, MSN, AIM, and others. As a result, mcue can support well known enterprise IP PBXs and UC systems such as Cisco, Avaya, Microsoft OCS and IBM Sametime as well as service provider networks such as wireless WAN carriers and ITSPs that offer pre-ims or IMS services. mcue also provides enterprise users with mobile access to full directory services, extension calling, corporate IM, and other features typically only available on IP desk phones or PC-based UC softclients. It can be used as a client on an end-point device universally for any of the end-to-end architectural deployment scenarios described in Figures 1, 2 and 3, i.e. enterprise (on-site or carrier hosted) as well as consumer carrier network deployments. Some of the expected use cases would be as follows: An enterprise user with a dual-mode phone in the enterprise connects over Wi-Fi to the deployed UC system and uses mcue to make voice calls to other extensions, do call transfers, check presence and chat with another worker on IM. On his way home from work, he is able to access the features of his enterprise UC system using GSM/GPRS connectivity. At home he connects on his home Wi-Fi network and still is able to use his enterprise UC system. Another worker at the enterprise can reach this user just by dialing his extension, or can IM him on the UC system. A consumer subscribes to Pre-IMS/IMS services on his 3G wireless carrier network and has mcue on his dual mode phone. At home he uses the Wi-Fi network and is still reachable on the same number. He can access all the IMS services he subscribes to, including IM to chat with others and make voice calls (VoIP). He leaves his home and connects over the 3G network to access the same IMS services. Another user uses a single mode WiMax phone with mcue and subscribes to an ITSP (for VoIP) service using WiMax femto-cells at home and a wide area WiMax network coverage outside. The user is able to switch seamlessly between indoor and outdoor access and use his phone to make VoIP calls, exchange IM (e.g on GoogleTalk or Yahoo!IM) with friends, share real-time video etc. mcue is a complete dual-mode phone client, built from the following components: mcue CUI and mcue UI framework vport MP IP communications middleware with IMS/VCC support for dual-mode handsets and ISI middleware abstraction layer Integrated graphics/java/browser platform with Java SE compatible JVM mcue runs on the Sun Java JRE versions 1.4 through Java 6, and a wide range of open source VMs using the GNU Classpath class library - several of which run on a wide range of SoC architectures. Thus, based on Java, with the portable ISI middleware layer, and a portable embedded graphics subsystem, mcue TM can run on most embedded OSs. Applications native to other embedded programming environments can also be easily integrated into mcue via JNI interfacing in Java. Copyright 2008 All Rights Reserved 8

9 Figure 4: mcue Architectural Components Key Highlights: Universal Mobile Unified Communications Client Presence-centric UI with push-to-x control Converged Contacts across different services Multi-Service (e.g. GoogleTalk, Yahoo!, leading IPPBX/UC systems) Multi-Protocol (e.g. IETF-SIP, IMS-SIP, XMPP, and others) Simultaneous multiple session support Multiple wireless access modes (e.g. WiFi, WiMax, Cellular) Seamless mobility with enterprise and carrier FMC capability Carrier Pre-IMS and IMS protocol interoperability Various deployment architectures (e.g. Enterprise, Carrier, ITSP) Field-proven IP Communications technology integration Table 2: mcue Highlights Box Copyright 2008 All Rights Reserved 9

10 Some of the key features and functions of mcue are listed in Table 1. Key Features & Functionality Multiple modes of communication in a unified user interface - from real-time voice to PoC to IM to SMS to Usability and look & feel comparable to top-tier mobile UI software Multiple communications services accessible through one user interface: Mobile and internet services can be used together Account management for multiple IP and circuit switched communications services A presence-centric starting point for communication and a contact list that knows how to synchronize with "buddy lists" Enables users to keep track of many simultaneous (i.e. IM, voice, PoC, SMS) conversations Directory service integration (e.g. Enterprise directory) Support for and compatibility with IMS communications modes - a superset of IMS functionality Graphical UI and contact list integration for enterprise (IP PBX) call control functions Multi-radio, multi-network (mobile cellular, WiFi, WiMax, etc.) communications, including vertical handoff and voice call continuity (VCC) for fixed/mobile convergence (FMC) Enterprise directory extension dialing with directory, presence and IM from inside enterprise IP network or outside from GSM/GPRS Contact list and calendar sync using standard protocols Pluggable support for additional communications protocols and services Voice engine for with adaptive jitter buffer, MIPs-efficient codecs - "soft DSP" runs on application CPU - and VCC support Protocol suite with SIP, XMPP, SIMPLE and others for IP PBX/UC system compatibility such as IBM Sametime, Microsoft OCS, Cisco, Avaya, et. al. NAT traversal support with ICE/STUN/TURN QoS support with configurable Diffserv, ToS bits, and WMM Support for Linux, embedded OSs, and smartphone OSs Connection management (Wi-Fi connection & security management i.e. automated and managed hotspot login), fast access point roaming Device management: Remote and automatic WAN/OTA management and upgrade Client software/firmware upgrade Table 2: mcue Features The mcue user interface (CUI) offers the latest advances in unified communications including presence-centric and push-to-x control over all types of sessions including voice, IM, SMS, and messaging. It includes an innovative presence-based converged contact list for all services and tools for managing multiple accounts, services and networks. The CUI layer provides the abstraction to applications programming of specific services belonging to genres of IP communication modes such as VoIP, IM, and Presence etc. CUI is implemented in Java, making it portable across OSs, graphics toolboxes, etc. The protocols and voice engine layer (i.e. vport MP) has its own portability abstractions, with proven portability across multiple operating systems, Copyright 2008 All Rights Reserved 10

11 Figure 5: mcue User Interface The mcue Communications UI is designed for divergent IP communications, presenting access to detailed communications features as shown below in Figure 6. Figure 6: mcue Communications UI and vport MP Engine Layers Copyright 2008 All Rights Reserved 11

12 mcue s ISI (Internet Service Interface) architectural layer (See Figure 6) provides the necessary abstraction of different IP and circuit-switched (cellular) communications protocols for application programming and portability. It presents a protocol-agnostic communications interface to the applications layers above it, including support for voice calling, instant messaging, and presence. ISI also enables multiple concurrent protocols and service sessions in mcue. The mcue IP communications engine provides the core protocol suite and voice codec engine processing functions, also giving mcue seamless mobility features for Fixed-Mobile Convergence (FMC) via IMS-SIP and VCC functions. Below the ISI layer, a virtual DSP architecture enables the voice DSP functions to run as soft DSP on a RISC processor or as DSP code on a hardware DSP core, providing design flexibility. The mcue IP communications engine is based on D2 s vport MP IP communications middleware layer and supports multiple protocols for multiple communications services like IMS-SIP/SIMPLE for packet voice and messaging on wireless carrier networks, SIP/XMPP for enterprise IP PBX /UC systems as well as Jabber/Jingle protocols used by some of the commercially available IM/Voice services like GoogleTalk and Skype. Additional protocols like NAT traversal and VPN support enable mcue to be deployed in end-to-end solution scenarios (e.g. enterprises) where such access/traversal secure features are necessary. Designed for flexibility and portability, the mcue IP communications engine can execute on both RISC and CISC platforms under industry-standard operating systems. It is currently optimized for both ARM and MIPS processor architectures under the VxWorks, Nucleus, and Linux operating systems. D2 s extensive experience in embedded IP communications, Java device platforms, and mobile user experience enables the company to provide core communications solutions for communications platforms used in mobile devices. In addition to Linux, mcue will be available on other OSs such as Google s Android and Windows Mobile in the near future. IV. mcue: The Ideal Solution for Mobile UC/FMC Deployment mcue is designed to help major players take advantage of the important trends now unfolding in mobile Unified Communications and Fixed Mobile Convergence. Its strength as a combination of a high performance, high quality communications engine and a feature-rich UI for communications puts it in a unique position of being able to provide solutions for the future s most critical UC deployment scenarios. mcue s wide support for end-user features, communications protocols and its highly flexible/portable architecture provide the right vehicle for device manufacturers to achieve economies of scale and lead them to higher profitability in the mobile UC/FMC business. With WAN service providers being concerned about potential relegation as data pipes, they are looking for new business models and revenue streams to increase ARPU and make the value of their networks more visible to end-users. There are clear indications of trends to to open networks for any device running any application and to offer flat-rate billing plans. These service providers would find mcue to be the ideal solution for creating new ways of differentiation through unified converged IP communications services to all end-user segments. For enterprise UC/IP PBX vendors, mcue addresses some of the weaknesses of current solutions by providing a consistent, comprehensive feature set that is universally applicable for all enterprise needs, convergence capability with wide area networks (WANs), a flexible UI for applications integration with other existing UC solution frameworks, and sufficient variation in mobile devices to meet different consumer demands. Copyright 2008 All Rights Reserved 12

13 For additional information, please contact the following: Internet: Sales : sales@d2tech.com Technical support: info@d2tech.com Address: D2 Technologies, Inc. 104 West Anapamu Street, Suite J Santa Barbara, CA Tel: Fax: Copyright 2008 D2 Technologies, Inc., mcue, vport and Enabling IP Communications are trademarks of D2 Technologies, Inc. All other trademarks are the property of their respective owners. All Rights Reserved The information contained herein is the property of D2 Technologies, Inc., and is believed to be accurate at the time of printing. D2 Technologies assumes no liability for any error or omissions in this information, or for the use of this information or products described herein. D2 reserves the right to make changes to its products at any time to improve reliability, functionality, performance, or manufacturability. Disclosure of the information herein does not convey a license or any other right in any patent, trademark, or other intellectual property of D2 Technologies. mcuewp ak Copyright 2008 All Rights Reserved 13