1 / 8

4P protocol selection

4P protocol selection. Aug19, 2009. 4P protocols - Summary. 3 protocols are considered for 4P platform as the primary interface between residential gateways and the network XMPP (widely used for IM & Presence Management applications)

baba
Download Presentation

4P protocol selection

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 4P protocol selection Aug19, 2009

  2. 4P protocols - Summary • 3 protocols are considered for 4P platform as the primary interface between residential gateways and the network • XMPP (widely used for IM & Presence Management applications) • SIP-SIMPLE (widely used for VoIP signaling, but recently extended for IM and presence) • IPDR (chosen by cable vendors for large scale data collection from network devices) • All 3 protocols meet the basic needs of notifying events in a simple, secure and efficient manner without polling from the network. • Event notification, push mechanism, extensible payload, authentication, encryption and privacy were the basic features considered here. • When it comes to developing consumer applications from the event feed, the choice narrows to XMPP and SIP-SIMPLE • IPDR would be suitable for NMS/OSS apps and probably belongs in the mediation layer in the network • When it comes to building a strong ecosystem of 3rd party developers, the choice narrows down to XMPP • Most innovative companies are behind XMPP (Google, Apple and Cisco) • Open source software is freely available on many platforms and devices (50+ implementations) • Large scale applications have been deployed in both consumer (GoogleTalk) and business domains (Financial sector) • SIP-SIMPLE should be considered if integration with IMS is mandatory • All 3 protocols need to evolve continuously. XMPP seems to be the most evolved so far, and 4P applications will further accelerate the evolution.

  3. Challenges with XMPP Challenges with SIP-SIMPLE Challenges with IPDR • Protocol variants. • Many non-standard implementations exist. Standardization always lags behind innovation. • Scalability • Large pub/sub groups will create messaging overheads and redundant messaging. • However this is a problem typical to social networking applications and chat rooms (example Twitter) • But, 4P applications are likely to be of small-scale in nature • Each household probably has 10 devices that notifies events • Each household probably has 5 devices to subscribe to those events. • Furthermore, server less messaging (an XMPP feature) could further mitigate the problem: • Events can be routed to listening devices without server (network) intervention, if they are co-located. • In other words, a lot of the traffic can be contained within the home network. • Complex stack that discourages 3rd party ecosystem • Designed for VoIP, hence large part of the stack is not useful for non-voice apps. • Verbose protocol, not web friendly • Limited implementations, limited availability • Great for NMS/OSS, but not for consumer applications that require interactivity and multimedia support. • Closed system. Need subscription to even view the standards (TMF) • Optimized for massive event streams, not for short messages.

  4. Evaluation of basic needs These are bare minimum capabilities to be expected from a protocol. These features allow events to be notified to multiple endpoints in a simple, efficient and secure manner. Bottom line-All 3 protocols can meet the basic needs.

  5. Ease of application development These features enable rapid development of consumer-friendly applications. Bottom lineIPDR requires lot of work to support consumer applications. SIP is best suited for IMS environment. Otherwise, XMPP is best suited for developing consumer apps.

  6. Industry Adoption These features provide a measure of industry adoption of each protocol. Bottom lineXMPP leads others in industry adoption by a wide margin

  7. XMPP Implementations • XMPP-based software is deployed on thousands of servers across the Internet and by 2003 was used by over ten million people worldwide. • Popular commercial servers include the Gizmo Project, Nimbuzz and Google Talk. • Popular client applications include the freeware clients offered by Google, Nimbuzz and the Gizmo Project, multi-protocol instant messengers such as iChat and Pidgin (formerly Gaim), and free dedicated clients such as Psi and Gajim. • Google Talk provides XMPP gateways to its service. • Google Wave's federation protocol is an open extension to the XMPP protocol Servers: Citadel, CommuniGate Pro, djabberdejabberd, IceWarp, iChat Server, Indafon, in.jabberd, Isode M-Link, jabberd, Jabber XCP, Jerry Messenger, Kwickserver, Openfire, OpenIM,Prosody, psyced, SoapBox Server, Sun Java System Instant Messaging, synapse, Tigase, Vysper, Wokkel Clients Apple MacOS: Adium, iChat Console / Text-Mode: centericq, climm, Fama IM, Finch, GNU Freetalk, irssi-xmpp, mcabber Cross-Platform (Linux/Mac/Windows): Coccinella, Jabbim, Jeti, Pidgin, Psi, saje, SIP Communicator, Spark, Tkabber Linux/Unix: Ayttm, BitlBee, Empathy, Gajim(also Windows), Galaxium, Gossip, jabber.el, Kopete, Sim-IM, Synapse Microsoft Windows: eM Client, Exodus, glu, JAJC, Miranda IM, Pandion, SoapBox Communicator, Trillian Pro, V&V Messenger, Yambi Mobile Phone / PDA: Bombus, Chatopus, IM+, imov Messenger, Jabber Mix Client, Jabiru, Lampiro, m-im, mChat, OctroTalk, Talkonaut, Vayusphere Web Browser: Afflux, Claros Chat, emite, iJab, Jabbear, JWChat, SamePlaceSparkWeb, Tigase Messenger, TigaseMinichat, TrophyIM, xmppchat

  8. 4P applications can ride the Google Wave • Google Wave is an integration of email, IM, Wikis and Social Networking tools. Objects known as "waves" contain a complete thread of multimedia messages (blips) and are located on a central server. • Waves are shared and collaborators can be added or removed at any point during a wave's existence. • Real time and “Live” collaboration. • Multimedia – text, voice, video. • Multiple participants may edit a single wave simultaneously. • History is stored and can be played back • 4P and Google Wave • An event can trigger a Wave App instantaneously and notify consumer and service provider simultaneously. • All interactions between consumer, CSR and 3rd party entities can be handled through Wave • Context sensitive • Instantaneous collaboration • Switch from text to voice to video • Switch from one consumer device to another • Entire history is stored and available for playback Consumers in HH Event Feed Video Feed Field

More Related