© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 1

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 2 Machine to Machine connectivity Over the Internet Proposal October 6, 2010 Ammar Rayes Cisco Systems

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 3 Machine to Machine Connectivity Over the Internet Proposal Overview  Interface mechanism for communication between remote entities (devices/networks at the customer site, the network vendor backend system, and/or a managing partner backend system) via the Internet.  Meant to be used in conjunction with other mechanism to realize overall, end-to-end connectivity e.g. – A backend application might contact an embedded client at the network/customer site via a chain of transports consisting of a LAN at the backend, XMPP messaging via the internet (this proposal) and another LAN between GW and devices at the customer site – Backend application and embedded client might communicate via a JAVA Message Service (JMS) or Enterprise Service Bus (ESB).

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 4 Machine to Machine Connectivity Over the Internet Overview Internet Service Appliance (optional) TAC Support IT infra App servers Network Vendor Vendor’s Partner Network 1 Managed by Partner Service Appliance (optional) Collects configuration,syslogand inventory,.. from all devices Backhauls to backend for analysis (periodic or on-demand) S/W updates,.. Message based commands, Remote access,.. Network 2 Managed by Vendor

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 5 Machine to Machine Connectivity Over the Internet Overview Internet Service Appliance (optional) TAC Support IT infra App servers Network Vendor Vendor’s Partner Network 1 Managed by Partner Service Appliance (optional) Collects configuration,syslogand inventory,.. from all devices Backhauls to backend for analysis (periodic or on-demand) S/W updates,.. Message based commands, Remote access,.. Network 2 Managed by Vendor

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 6 Machine to Machine Connectivity Over the Internet Overview Internet Service Appliance (optional) TAC Support IT infra App servers Network Vendor Vendor’s Partner Network 1 Managed by Partner Service Appliance (optional) Network 2 Managed by Vendor Connectivity CSO endpoints

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 7 Supported Devices/Networks  Direct interface to ad device  Small Networks: – Up to 10+ devices – One device support service appliance functions  Medium Networks: – Up to 100+ devices – Small External appliance  Medium Networks: – Up to 100+ devices – Large External appliance Small Enterprise Service Appliance Service Appliance

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 8 Entities Used by the Proposed Solution  Vendor Site: Backend servers for operation support and business support applications, transport gateways  Partner Site: Service appliances, transport gateways and application processing servers.  Customer/Network Site: Service appliances, transport gateways, end devices

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 9 Modes of Transport  The connectivity supports two modes of transport: – Messaging based on the Extensible Messaging and Presence Protocol (XMPP). Control, data and signaling are conveyed via XMPP stanzas. – Secure, layer 3 point to point tunnels that are set up between connectivity endpoints using XMPP as the signaling mechanism.  The Protocol Adaptation function (not an integral part of the connectivity), allows endpoints to adapt their communication protocols (e.g. SOAP, syslog, SNMP etc.) to one of the transports supported connectivity. An endpoint might use XMPP for one communication protocol and layer 3 tunneling for another.  Several XMPP protocol adaptations are defined as standard XMPP extension protocols (XEPs). Other extensions can be defined as needed.  On booting, connectivity instances authenticate themselves to an XMPP server. This is followed by authentication, registration and any necessary contract validation with the back end

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 10 Logical Overview Connectivity in partner infra, appliance or TG Partner end functions (Inv, Monitoring, etc.) Customer end functions (e.g. Discovery, Collection, Monitoring, etc.) LAN API Partner Connectivity in backend server, connectivity, or TG Protocol Adaption (e.g. SOAP to XMPP, ESB to L3 tunnel) Back-office end functions (Inv, Monitoring.) LAN API Vendor Backend Connectivity in customer device, appliance or TG Protocol Adaption (e.g. SOAP to XMPP, ESB to L3 tunnel) Customer end functions (e.g. Discovery, Collection, Monitoring, etc.) LAN API Customer Network LAN API XMPP Server Control, signaling & Data XMPP servers could be located in the “cloud”, vendor backend, and partner sites XMPP-Signaled PTP L3 Tunnel

© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialNetwork-level Smart Services 11 Gateways APIs  Head-end and tail-end gateway exist on vendor backend and network/customer appliance respectively.  The main advantage of gateways being used on both end-points is that, that the gateways shield the aggregator and collector APIs from the connectivity CSO’s API.  Using the JMS (Java message service) mediation between: Head-end  aggregator instance and Tail-end  collector instance, the collector and aggregator APIs remain indifferent to any changes in the connectivity CSO’s API.