Speaker: Unknown

2. Cisco Field Area Network
• Multi services
• Smart End point (Connect Grid Endpoint) & the Ego System
• Fog computing --- IOx
• Security
• Management
• Standard
Devnet & Solution Partner Program
• Technology Focus Drill Down
• Partner Stories
Agenda

3. Cisco Multi Service FAN Solution

4. Multi-Application Network Architecture
Internet Protocol (IP)-Based
Network Design
Open, Standards-Based,
and Interoperable
Modular, Future-Proof,
Extensible Solution and
Product Architecture
Comprehensive
Security
Scalable, Enterprise-Based
Network Management
Solution
Platform for
Distributed Intelligence
EFFECTIVE FAN COMMUNICATION STRATEGY

5. IOT in Operational Technology (OT)
Sensors, Actuators, Smart Objects
Routing, Switching, Security
Wide Area Network
Data/Operations Center
Energy
SmartCities
Oil&Gas
Manufacturing
Transportation
Etc.
“Fog” Computing /
IOx
Communications, Security,
Standards
Network Management
Data Flows
Where Cisco enables
developer partners
IOT in Operational Technology (OT)

6. • Build the Secured / Managed / Scalable Network
• Provide Internet Protocol (IPv6) based network communications protocol stack for endpoints
• Provide a communications module (hardware) reference design for endpoints
• Provide scalable enterprise-based network management (Cisco Field Area Director)
• Provide comprehensive security, scalability and future proofing via open standards throughout
• Make better usage of the network, achieve higher ROI
• Provide application enablement capability at the network edge --- IOx
Cisco’s Approach to Enable IOT Application

7. Where Partners Can Add Value
IoT Endpoints
Cisco Connected Grid
Network Management &
Fog Director
Cisco CGR Routers
Cisco 8x9 Router
CG-FNDApp
Cisco’s CGE
Communication Module
Ref Design and SW,
Third parties’ sensors
Cloud Apps
(Data/Ops Center)
Add-in Hardware Modules
010101010
100101010
101010101
011010101
101010100
011111
IOX -- Fog
(Distributed)
computing
Partners
Fog
Dreictor

8. DevNet Solution Partner Program
Free Subscription-based
An open and collaborative
community of more than
32,000 individual
developers using self-
service portals consisting
of wikis, forums and blogs.
An eco-system
of more than 700
companies partnering
with Cisco to create
customer-relevant
solutions and take to
market.
Cisco DevNet And Solution Partner
ProgramDevNet and Solution Partner Program

9. Solution Partner Participation Levels
Strategic
Solution Developers
Preferred Solution
Developers
Solution Developers
Strategic Solution Developers
• Strategic Roadmap Planning
• Joint solution development
• Strategic channel enablement
Preferred Solution Developers
• Interoperability Verification Testing
• Joint solution collateral
• Deal Registration, Partner Space
Solution Developers
• Joint marketing, product catalog
• Developer discounts
• Technical support
USD 5,000/yr+
USD 5,000/yr+
USD 3,500/yr*
* USD 1,000 in Emerging Markets (outside US, Canada, and Europe)
+ USD1,500 in Emerging Markets (outside US, Canada, and Europe)

10. SPP Subscription Benefits
• Access to Tech Center collateral (HW Schematics, API Docs, Code drops, White paper etc)
• Direct developer support from the BU (not TAC, IOT DevNet team members)
• Access to IOX sandboxes
• Access to cloud infrastructure services for development eg. CG-REDI for IP-enabled grid device Tech
Center
• 70% discounts on all Cisco hardware and software in most theatres
• Must be purchased through Distributors (eg. Comstor, Ingram Micro, Tech Data)
• (Joint) Compatibility Verification Testing (CVT)
• “Cisco Compatible” certification logo by Cisco
• Access to marketing assets like collateral templates and press release templates
• Joint collateral development (White papers, case study, etc)

11. FAN – Open Standards Reference Model
IPv6/IPv4
UDP/TCP
IEEE 802.15.4e MAC enhancements
IPv6 RPL
Web Services, EXI, SOAP,
RestFul,HTTPS/CoAP
• Open Standards – at all levels to ensure interoperability and reduce technology risk for utilities
•Future proofing – common application layer services over various wired and wireless communication technologies
802.1x / EAP-TLS & IEEE 802.11i based Access Control
Physical
Layer
IEEE 802.15.4
2.4GHz, 915, 868MHz
DSSS, FSK, OFDM
IEEE P1901.2
NB-PLC
OFDM
IEEE 802.11
Wi-Fi
2.4, 5 GHz, Sub-GHz
IEEE 802.3
Ethernet
UTP, FO
2G, 3G, LTE
Cellular
IEEE 802.16
WiMAX
1.x, 3.xGHz
Data
Link
Layer
IEEE 802.15.4
including FHSS
IEEE P1901.2
802.15.4 frame
format
IEEE 802.11
Wi-Fi
IEEE 802.3
Ethernet
2G, 3G, LTE
Cellular
IEEE 802.16
WiMAX
6LoWPAN (RFC 6282) IPv6 over Ethernet (RFC 2464)
IPv6 over PPP
(RFC 5072)
IP or Ethernet
Convergence SubL.
Network
Layer
Application
Layer
Addressing, Routing, Multicast, QoS,
Security
Security (DTLS/TLS)
DNS, NTP, IPfix/Netflow, SSH
RADIUS, AAA, LDAP, SNMP,…
(RFC 6272 IP in Smart Grid)
Metering
IEC 61968 CIM, ANSI C12.22,
DLMS/COSEM,…
SCADA
IEC 61850, 60870
DNP3/IP, Modbus/TCP,…
LLC
M
A
C
Mgmt

12. Wi-SUN Alliance
Vision: Drive industry to embrace
open standards and interoperability.
• Definition of Wi-SUN profile based
on IEEE 802.15.4g/e standard
• Testing
• Certification
• www.wi-sun.org
13

13. Cisco Connected Grid Endpoint SDK – IEEE 802.15.4g/e
• MAC layer: IEEE 802.15.4 compliant + 802.15.4e extensions
• 15.4g: frame size larger than 127 bytes
• 15.4e: EB and EBR for network discovery
• 15.4e: Enhanced ACK for security and information carrying
• 15.4e: Information Elements (RSSI, Time synchronization)
• Novel channel hopping scheme
• Per-node hopping sequence for maximum channel diversity
• Overlaid hopping sequence for multicasts
• PHY layer – IEEE 802.15.4g compliant
• Operating Band: 902-928 MHz
• Number of Channels: 64
• Channel Spacing: 400 kHz
• Modulation Method: 2FSK
• Baud Rate: 150 kbaud/sec
• Bit Rate: 75 kbits/sec after overhead from Convolutional FEC, or double without
• Output Power: 30 dBm
• Regional filtering for countries only supporting a subset of 902-928MHz
• Transmit power set-up for local regulations
Adaptation: 6lowpan (RFC 6282)
IPv6
UDP/TCP
PHY: IEEE 802.15.4g
MR-FSK
MAC: IEEE 802.15.4e
FHSS
Routing: RPL
Mgmt: CSMP
CoAP
802.1x / EAP-TLS
based Access Control Solution
Applications
Cisco Developer Network – IP Enabled Grid
Devices HW ref. model + SW SDK library
Small footprint open standards IPv6-based

14. 902-928 MHz RF Mesh
• Vision
• Drive industry to embrace open standards and interoperability
• Reduce technology risk
• Facilitate connectivity for 3rd party devices and applications
• Quality of Service (QoS)
• Enterprise Network Security
• Scalable Network Management
• Maximum 2,000-5,000* endpoints per CGR1000
• Average 200ms* latency per hop
• Range between 20ms and 500ms
IPv6 RF Mesh
* Highly dependent on WAN backhaul characteristics, network design, and traffic conditions

15. IEEE P1901.2 – Open standard for Narrow Band PLC
• IEEE P1901.2 – Open standard for Narrow Band PLC
• PHY & MAC layers definition (upper layers are open to IPv6-based standards
solution and evolution)
• Worldwide regions support
• Covers the full Low-frequency (below 500 KHz) PLC communication spectrum
• Use-cases extend beyond AMI
• EV to charging station, street lighting, power plugs, solar panels/inverters
• Enable MV/LV crossing – To be demonstrated
• Aligned with IEEE 802.15.4g/e RF Mesh profile – 6LoWPAN (RFC 6282) as adaptation layer
and RPL (RFC 6550) for routing at Network layer – ease the mix of PHY/MAC technologies
• Chipsets vendors advertising IEEE P1901.2 PLC support on new generation
chipsets, currently support G3-PLC
• CGR 1000 NB-PLC interface
• CGR 1120 – 3 phases, CGR 1240 – 1 phase

16. Cisco CGE SDK
BOM
API,
Docs,
Training
Code
Drops
HW Schematic
Cisco Delivers:
Support
Partner Creates:
Head-end
Infrastructure as a Service
AD, DNS
NTP
CA
CG-NMS AAA
DHCPv6 Server
DB

17. CGE SDK – NIC (PPP) model
Mesh End Point
Comm Module (NIC)
(Cisco CGE Reference Design)
Application Module
(Meter Registers, Digital/Analog
Sensor I/O, etc.)
U
A
R
T
CPU/memory
/IO
MCU
MAC/PHYintf
802.15.4gor
P1901.2
PHYFront
End
IPv6 over
PPP
SensorI/O
On-board
sensors
Ext.sensors
CGMesh
U
A
R
T
Cisco technology Partner technology

18. CGE SDK – Integrated Execution (IE) model
Mesh End Point
Comm Module + OS Kernel
(Cisco CGE Reference Design –
Integrated Execution model)
Endpoint Applications
(Meter Register,
Digital/Analog Sensor
I/O handlers, etc.)
MCU
MAC/PHYintf
802.15.4gor
P1901.2
PHYFront
End
SensorI/O
On-board
sensors
Ext.sensors
CGMesh
G
P
I
O
API
Cisco technology Partner technology
I2C Peripherals

19. CGE - The Starter Kit
Enables you to do the following:
• Perform local diagnostics to help bring
up CGE via its “host” UART
• Enable your CGEs to join RF or PLC
mesh network
• Enable your CGEs to connect with
Cisco’s CG-REDI head end servers,
and to your application server(s)
Requirements:
• CGR + modules must be purchased
from a Cisco distributor with any
applicable CDN developer discounts
• Your PC, Laptop, or Server
• Global static IP address (for CGR) from
your 3G carrier or ISP
CGR1240 or
CGR1120
WPAN i/f module
(RF or PLC)
3G i/f module
CDN
CSMP SW Tools
(MS Windows,
Mac OS X, Linux)
(Optional) For
your application
server
development
Cisco UCS Server C22-M3

20. CGE - Starter Kit Topology
Corp. LAN
Application
Server
802.15.4g RF
P1901.2 PLC
RF-mesh SDK CM
PLC SDK CMSerial to USB
console
wpan4/1
Debug
UART
Internet
Internet Routable IP
eth2/1
eth
Eth/Wifi
FAR

21. CGE Field Deployment Model
Neighborhood Area
Network
Utility Head-End
Cisco CG-NMS
DB
AAA
Certificate
Authority
Directory
Services, DNS
NTP source
DHCPv6
Services
Application Servers
MDMS, SCADA
DB
CG-mesh
(RF or PLC) CGR 1000
CG-mesh
(RF or PLC) CGR 1000
CG-mesh
(RF or PLC)
CGR 1000
Public or Private
Networks
Secure IPv6 tunnel
Secure IPv6 tunnel
Secure IPv6 tunnel

22. Partner CGE Development Model
Cisco CG-NMS
DB
AAA
Certificate
Authority
Directory
Services, DNS
NTP source
DHCPv6
Services
Cisco Connected Grid
Rapid Endpoint Development
Infrastructure (CG-REDI) as a
Service
Corp.
LAN
3G
Internet
Application
Server(s)
DB
Partner Premises
CG-mesh
(RF or PLC)
CGR
1000
JTAG/
UART
Consol
e
“Starter Kit”
Secure IPv6 tunnel
Secure IPv6 tunnel

23. CGE Development Life Cycle
• Build HW
development board
based on RF/PLC
Ref Design
• Load CGE FW and
use our diagnostics
to validate operation
• Join CGR’s WPAN
mesh and get IPv6
connectivity
• Perform CSMP
validation tests
• Send us your CGE
SNs (EUI64)
• We will send you
certificates to
embed in CGEs
• Verify that CGEs
register with
CGNMS (in CG-
REDI)
• Assemble your
Starter Kit with
SPP discount
• Get global static IP
for CGR (from 3G,
Cable/DSL, or ISP)
• Contact us for CG-
REDI access and
CGR configuration
• Develop firmware
application for CGE
(PPP or IE model)
• Build Server
application for
endpoint mgmt
• Connect Server to
CG-REDI and check
Server application
connection to CGE
CGE Development Life Cycle
Setup Starter Kit Mesh
Firmware
Sever Application
Turn On Security

24. Compatibility Verification Testing and beyond
Perform CVT Market Sell Advance
• Perform
Compatibility
Verification
Testing with Cisco
• Obtain Cisco
Compatibility logo
• Use Cisco logo is
marketing
materials
• Issue press
release upon
completion of
CVT to promote
compatibility and
membership
• Engage potential
joint customers
• Register closed
deals and submit
customer
references
• Earn points and
satisfy
requirements to
move up the
pyramid
• Access more
benefits
Compatibility Verification Testing and Beyond

25. Post Development Commercial Framework
• Cisco / Vendor License Agreement
• Vendor licenses Reference Design from Cisco for commercially marketing the CGE
developed
• Vendor manufacturing
• Securing the CGE with identity certificates and maintaining the PKI
• This may need to be delegated to (as required by) utility customer
• Cisco’s Advanced Services group can provide system design, technology
integration and EFT/deployment support

26. Fog Computing

27. • Compute facility/capability at the
edge of the work
• Extends the concept of Cloud
Computing paradigm to the edge of
the network
• Critical component to IOT
Applications
• Data filtering to reduce traffic
• Consolidate/compress messages to
optimize for network
• Ability to react right at the edge when
backhaul to Cloud is not available
Fog Computing

28. IOx is an end-to-end application enablement framework that aims to provide application hosting
capabilities for different application types in a consistent and uniform manner on all Cisco network
platforms. The term Application enablement covers all life cycle aspects of applications including
development, distribution, deployment, hosting, monitoring and management.
What is IOx
Apps are the value addition on the IOx
platform.
Developers, Partners, ISV & MSP are
producers who create the apps.this
Customers and Users are the consumers of
this apps.
IOx framework facilitates this value creation
by providing a set of services that make it
easy for developers to build IoT apps and
host them on IOx platform, app distribution
and management tools for our customers to
discover and deploy the apps to IOx
framework.

29. The below picture summarizes how device resident IOx framework and services abstracts the
complexities and differences of the underlying hardware
IOx Architecture

30. IOx Development / Deployment Flow
Developer
IOx SDK
IOx Sandbox
(Local install or DevNet Cloud)
Fog Director
Admin
Build an applications
Run and test applications
using IOx Sandbox or
Cisco C8x9 edge router
Manage IOx applications
and devices in a systemic way
IR8x9
IR829/809
IR829/809
SensorsDeploy applications
on IOx devices

31. Bear in mind fog computing happens on Cisco edge routers which typically has limited resource
thus while design the application, choose the proper language between c, python, or java. As a
example:
 IR829
 CPU: Intel Atom C2308 (1M Cache, 1.25 GHz), Dual Core, X86 64bit.
1 Core for IOS , 0.5 Core for VDS, 0.5 Core for GOS
 Memory: 2GB DDR3 totally; 1GB for GOS (700M for applications)
 Storage: 8GB eMMC totally; 3GB for GOS (800MB for applications)
 IOx Sandbox
 OVA Installation: 1vCPU, 2GB RAM, 25GB HD, and ESXi 5.0+
 IOx Sandbox environment is meant to be a IOx node for developers to play with ioxclient,
Fog Director and deploy their applications. There are several limitations such as physical
interfaces and performance difference.
http://developer.cisco.com/site/iox
IOx Application Development Considerations
Resource Constrain Consideration

32.  When design your app, consider below and pick the “type” that fits:
 VM packaged apps: These are applications packaged as virtual machines, that is, the
virtual machine that contains OS (kernel + root file system), libraries, and application
code packaged into one package.
 Native/Container apps: These applications are designed to run natively on the Host OS
and are OS dependent. These applications are isolated from each other using isolation
capabilities provided by the Host OS (such as LXC in the case of Linux). The apps are
composed of application codes, 3rd party dependent libraries, native binaries (and entire
root file system, minus the kernel, in the case of LXC) packaged into one archive.
 PaaS style apps: These applications are more portable and self contained, typically
developed using dynamic languages such as Java, Ruby, Python etc, and are designed
to run in specific PaaS frameworks, (OS independent)
IOx Application Development Considerations

33. Container and PaaS Style Applications Guidance
PaaS Style Applications:
• Self-contained apps, portable
• Write-once, deploy across IoT platforms
• Python, Java, etc
Container Style Applications:
• Tied to Host OS architecture
• Total isolation from other apps (via LXC )
• Limited control on life-cycle activity management
Cisco provides the IOx SDK to package the PaaS and Container Style applications for further deployment.

34.  Cisco provides the IOx SDK to package the applications and open source software for further deployment. (IOx
SDK HW/SW Specification: 1vCPU, 2GB RAM, 25GB HD, and Ubuntu 14.04.01). Use SDK to package the app
and deploy using fog director will avoid potential issue of messing up the system configuration by “randomly” put
files into different locations.
 An IOx application package shall consist of:
 ONE package descriptor file named as "package.yaml" and should be present in the root of the package
 ONE tar.gz envelope containing application or service artifacts with the name "artifacts.tar.gz". These artifacts
may be binaries, application code, application libraries, virtual disks, rootfs etc., More details about this in the
below sections.
 zero or one application configuration file named as "package_config.ini". If present, should be in the root of the
package.
 zero or one application manifest named as "package.mf". If present, should be in the root of the package.
 zero of one certificate containing signing information named as "package.cert". If present, should be in the root
of the package.
 IOx Application Installation Path:
 All the applications and cartridges will be installed in a separate partition (/dev/sdb) with the mapping director
name of “/software”. The installed applications and cartridges will not be impacted in cases of IOS or GOS
image upgrade as long as you put them in the /software.
IOx Application Development Considerations
Packaging/File Structure

35.  HW/SW Specification
 1vCPU, 2GB RAM, 25GB HD, and Ubuntu 14.04.01
 Application Management
 Upload Application
 Publish Application
 Install/Uninstall Application
 Deploy Application to Device
 Start/Stop Application
 Device Management
 Add/Remove Device
 Device Information
Fog Director Guidance
Cisco Fog Director manage multiple instances of applications, update
applications remotely, and enable applications from different development
environments /in different languages to run on the same fog node.
DNP3
Specific
Examples:
DB Analytics
Server
Modbus
Fog Director
• Available Resources
• App Distribution and Lifecycle
• App Monitoring

36. DevNet Service
• Same support model with expanded technology
• Current support
• CGE SDK
• IOx on C829/C809
• BOYI (on c829 --- incoming)
• Embedded system - ESR5921

37. Partner Stories

38. CG Endpoint Development Partners

39. Fog Computing Partners

40. Smart Metering
Itron (www.itron.com) integrated Cisco CM into their meters (RF and PLC ) forAMI deployment

41. Smart Grid
• .
• CSE
(www.corporatesystems.co
m) integrated Cisco CM
into their smart controller
system
• QinetiQ (www.QinetiQ-NA.com) integrated
Cisco CM into their energy harvesting device
• Leverage Cisco CM functions to deliver the
data of the energy voltage flow including theft
detection

42. Smart Lighting
• M2M (www.m2mtelemetria.com.br) integrated Cisco CM into their smart lighting
device
• CM is build into a small form factor to resell
• M2M’s is in discussion with other partners to integrate the CM module into their
end smart device.

43. Smart EV Application
Fog computing
enable business
intelligence at
the very edge of
the network from
grid2home

44. Contact Us
By Email: ivsg-devnet-support@cisco.com
Q&A