Telecommunications Industry Association (TIA)
[Gray shading indicates required elements]
DOCUMENT SUBMITTED TO:
The document to which this cover statement is attached is submitted to a Formulating Group or subelement thereof of the Telecommunications Industry Association (TIA) in accordance with the provisions
of Sections 6.4.1-6.4.6 inclusive of the TIA Engineering Manual dated October 2009, all of which
provisions are hereby incorporated by reference.
SOURCE:
CONTACT:
Cisco Systems
Ammar Rayes
TITLE:
PROJECT NUMBER (PN):
DISTRIBUTION:
INTENDED PURPOSE
DOCUMENT:
OF
___
FOR INCORPORATION INTO TIA PUBLICATION
_X_
FOR INFORMATION
___
OTHER
(Please
_________________________________
describe)
ABSTRACT:
This work proposes a standard interface to communicate between two machines/entities via the
internet. It is meant to be used in conjunction with other mechanisms to realize overall, end-toend connectivity.
PATENT DISCLOSURE [OPTIONAL]
Patent: Establishing Internet Protocol Security Sessions Using The Extensible Messaging And Presence
Protocol, Filed on 9/30/2009.
Patent: A Messaging and Presence Protocol as a Configuration and Management Bus for Embedded
Devices, Filed on 4/7/2010.
Patent: Method and Apparatus for Entitled Data Transfer Over the Public Internet, Filed on 8/20/2008.
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
1
Machine to Machine
connectivity Over the
Internet Proposal
October 6, 2010
Ammar Rayes
Cisco Systems
Presentation_ID
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
2
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).
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
3
Machine to Machine Connectivity Over the Internet
Vendor’s Partner
Overview
Service
Appliance
(optional)
Network 1
Managed by Partner
Network
Vendor
Service
Appliance
(optional)
Internet
IT infra
App servers
Network 2
Managed by Vendor
TAC Support
•Collects configuration, syslog and inventory,.. from all devices
•Backhauls to backend for analysis (periodic or on demand)
• Message based commands, Remote access,..
• S/W updates,..
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
4
Machine to Machine Connectivity Over the Internet
Vendor’s Partner
Overview
Service
Appliance
(optional)
Network 1
Managed by Partner
Network
Vendor
Service
Appliance
(optional)
Internet
IT infra
App servers
Network 2
Managed by Vendor
TAC Support
•Collects configuration, syslog and inventory,.. from all devices
•Backhauls to backend for analysis (periodic or on demand)
• Message based commands, Remote access,..
• S/W updates,..
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
5
Machine to Machine Connectivity Over the
Internet Overview Vendor’s Partner
Service
Appliance
(optional)
Network 1
Managed by Partner
Network
Vendor
Service
Appliance
(optional)
Internet
IT infra
App servers
Network 2
Managed by Vendor
TAC Support
Connectivity
CSO endpoints
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
6
Supported Devices/Networks
Service
Appliance
 Direct interface to ad
device
 Small Networks:
Small Enterprise
Service
Appliance
Medium Enterprise
Service
Appliance
Large Enterprise
Service
Appliance
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
– 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
Cisco Confidential
7
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
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
8
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
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
9
Logical Overview
Partner end
functions (Inv,
Monitoring, etc.)
LAN API
Connectivity in
partner infra,
appliance or TG
Control,
signaling
& Data
XMPP servers
could be located in
the “cloud”,
vendor backend,
and partner sites
Control,
signaling
& Data
LAN API
Customer end
functions (e.g.
Discovery,
Collection,
Monitoring, etc.)
XMPP
Server
XMPP
Server
Partner
Protocol
Adaption (e.g.
SOAP to XMPP,
ESB to L3
tunnel)
LAN API
LAN API
Connectivity in
customer device,
appliance or TG
Control,
signaling
& Data
XMPP-Signaled
PTP L3 Tunnel
Customer end
functions (e.g.
Discovery,
Collection,
Monitoring, etc.)
© 2009 Cisco Systems, Inc. All rights reserved.
Customer Network
Network-level Smart Services
LAN API
Protocol
Adaption (e.g.
SOAP to XMPP,
ESB to L3
tunnel)
XMPP
Server
LAN API
Connectivity in
backend server,
connectivity, or
TG
Back-office end
functions (Inv,
Monitoring.)
Vendor Backend
Cisco Confidential
10
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.
Network-level Smart Services
© 2009 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
11