DEVNET-1145How APIs are Driving City Digitization

How APIs are Driving City Digitization

Sunder Venugopal - Principal Engineer

DevNet-0093

© 2015 Cisco and/or its affiliates. All rights reserved. Cisco PublicPresentation ID 3

• Smart Cities Solution Architecture

• Leverage existing API services in the IoT world

• Shielding users from the underlying technology

• Get started with your API and accelerate application Development

• Layered Models and facets, abstraction of business logic

• Use Cases, Consumption, deployment & services to deliver business results

Agenda

© 2015 Cisco and/or its affiliates. All rights reserved. Cisco PublicPresentation ID

S+C Solution Architecture

City Services Parking and mobility Street lighting Environment monitoring Location analytics

Citizen Services Location-based services Wired and wireless network

management Remote interactive services

S+C City Wi-Fi NetworkNetwork/FAN/DC Services

Management

Real-Time

DistributedSecurity

Event Processing

Notification/Alarm

Reporting/ Trending

PublishingDevice

AbstractionService

Assurance

City Infrastructure Management

RefApplications

DeviceNormalization

Data Store

Field resources from different verticals

Traffic Outdoor Lighting

Public Transport

Crowd sourcing and

analytics

Citizen Interaction


Three Challenges One Platform

1Connecting

Apps & Things

Connect on and/or off-premise apps and systems to automate process and gain efficiency

Automate Operations

2 Sync Data and Deliver

Content

Event driven data sync and content delivery to empower customers, partners and LOB

Deliver Content

3 API Enabled Business

Create application services to enable mobile apps or new service offers that drive revenue and retention

Engage and Transact


The next logical step …Sensor


City Sensor Networks• Cities need to deal with large wireless or wired network of sensors of diverse and multiple

types

• To enable services an horizontal approach is required where the IoE for Cities provides interconnect/collect/store/organize/share functions for Sensor Networks

• A sensor abstraction model shall be provided to define a sensor/actuator, its capability, how to access data and notifications

• Data from sensors with semantic should be stored in a repository, ideally the Linked Open Data store. Stored sensor data can be used for public or private use

• Data mining and analytics are using sensor data

• Standards such as Sensor Web Enablement (SWE from OGC) and SSN (W3C), Internet of Things (IoT), M2M should be used


City Devices or Machines

• Besides simple sensors/actuators classified as embedded smart devices the city is also using a network of other more complex devices or machines: CCTV cameras, Digital Multimedia/Kiosk, etc.

• These devices need also to be integrated in the IoE for Cities in an horizontal manner

• A Machine Abstraction Model is required to enable Services Development and Deployment via the IoE for Cities

• This model should allow to provide control/actuation functions across devices

• Standards: the M2M standard (ETSI, oneM2M) , and Ontologies around IoT (e.g. Open IOT)

Cisco Confidential 9© 2013-2014 Cisco and/or its affiliates. All rights reserved.

APIs Transform IOE Data into Consumable AppsEnable customers, partners and employees with data and apps

MobilityReal time dashboard

TTFHW Availability

IOE Common APIs

IOE Services

Exposed as APIs

API APIAPI APIAPIAPIAPIAPI API APIAPI API


Decouple Business Logic from the device model


Remote Management

System ManagementParking, Lighting, Traffic Mgmt., Citizens engagement. Applications

Inter Cloud and City Wi-Fi

Sensors and Other Data Sources

Accelerated Application Development

Versions & Policies Cisco Smart cities Market Place

PartnersRobust API runtime

API

City Digital Platform – Urban Service Market place

IOT Integration Services

Promote and socialize DevNet – Developer Platform

Certified Sensors

Certified Applications Lighting, Parking, Traffic, Environmental, incident resp, License plate recognition, water, Citizen engagement

Urban Service Energy service, Parking service, Crowd density monitoring service, Speed monitoring service


Smart +Connected Cities - Logical Stack

Gateways

Lighting API

Parking API

Kiosk APITraffic

APIMap API

BUSINESS LOGIC

CITY APPS

DOMAIN LOGIC

Models

DEVICE LOGIC

Facets

CIM

Mod

els

Business

City eventsPolicies

On/off state

Intensity

Location

API Providers

API Consumers

Cisco device engine has model-based query APIs that empower developers with full flexibility

Example

Things: light, parking, sensor, multisensorProperties: each has 2~4Relationships: each has 1~3Actions: each has 1~3

Provider pre-defined APIs often do not work exactly the way consumers want

Model-Based Query APIs:Any aspect of the models can be

queried by developers, without fixed constraints

Model Extensions:Developers can extend

models without touching code

1 Query API:

Find {T} Select {T}.{A} Where {T}i.{R}={T}j.{R} Act {T}.{A}

# of API combinations needed for equivalent flexibility: 31,104

Contextual and Normalized APIDecouples Business logic from comm

layers


Use Case: Linking Data for City Services

Semantic

Linkage

Pollution (Sensor Data)

311 service (illegal dumping, rat cases,

Street service, Public works, Ped counts)

(Open Data)Citizen volunteer, scouts, Bike trails

(People data)

Lighting, Traffic

Flow, Vehicle count (sensor, camera

metadata)

Linking different data sources from sensors, devices, people and open data enables new services for city and citizens

• Location based Integrated services

• Helps service provider to position its location sensitive personalized service

• Depending upon the location context, can provide an aggregated service to citizen

• Location based customized interaction

• Location neighborhood information, services can dynamically provide personalized interaction

• Infrastructure agnostic service delivery

• Service Provider can extend its install base by decoupling from edge machines and make service available on any compatible machine

• Service Pull through

• By being integrated with partners’ services, it can have a pull through effect in right context


Use Case – Ped Counts over 100 in KCMO.org

14


Use Case - Kansas City Smart City Deployment• Current parking insufficient on-street parking and parking garage capacity

• Strong traffic disturbance due to lack of car park

• Impossibility to develop additional on-street parking

• Parking fee revenue collection notably insufficient

• Difficulties in managing of-regulated places (delivery, handicap)

• Environmental sensors will monitor atmospheric (temp, humidity, rain, fog), wind (speed, direction) and pollution (Co2 emission) measurements

• A smart lighting control is capable of monitoring, activating, and controlling each individual light point in the network in line with requirements

• Malfunctioning street light

• Camera with a dirty lens (used mainly for maintenance purposes)


Use Case - Kansas City Smart City Deployment• Vehicle stopping in the middle of the road

• Vehicle driving on the road shoulders, Vehicle driving in the wrong direction, Vehicle loitering in a defined area

• Vehicle illegally parked in an unauthorized area

• Vehicle entering a restricted zone

• Pedestrian crossing the road in a dangerous/unauthorized area

• Pedestrian “caught” in a defined area for a duration exceeding a threshold

• Road debris (e.g. a box that has dropped off a truck)

• Abnormal traffic – based on the ability to automatically learn the traffic routine in every segment, and based on this analysis identify abnormal traffic patterns


API Deployment https://developer.cisco.com/iot

https://developer.cisco.com/iot

https://developer.cisco.com/iot

Thank you

© 2015 Cisco and/or its affiliates. All rights reserved. Cisco PublicPresentation ID 18

Technology

DEVNET-1145How APIs are Driving City Digitization