DEVNET-1145 How APIs are Driving City Digitization
•Télécharger en tant que PPTX, PDF•
1 j'aime•852 vues
Smart-city solutions connected over an intelligent network platform are the foundation for city digitization. Cisco now offers application program interface (API) tools for developers to create applications for smart cities that frame and focus big-data streams, delivering relevant and timely content to improve city operations and enhance daily life. See how select visionary cities are already working with Cisco to leverage Smart+Connected Communities solutions and how an enormous opportunity now exists to develop applications that transform the data into useful information for city leaders, businesses, citizens and visitors as well as for use in other city processes. Cities are attracting new businesses and entrepreneurs and generating an economic boom in application development to meet urban service requirements of every stripe in cities today and broadly drive city digitization.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à DEVNET-1145 How APIs are Driving City Digitization
Similaire à DEVNET-1145 How APIs are Driving City Digitization (20)
Plus de Cisco DevNet
Plus de Cisco DevNet (20)
Dernier
Dernier (20)
DEVNET-1145 How APIs are Driving City Digitization
- 2. How APIs are Driving City Digitization Sunder Venugopal - Principal Engineer DevNet-0093
- 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
- 4. 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 Network Network/FAN/DC Services Management Real-Time DistributedSecurity Event Processing Notification/ Alarm Reporting/ Trending Publishing Device Abstraction Service Assurance City Infrastructure Management Ref Applications Device Normalization Data Store Field resources from different verticals Traffic Outdoor Lighting Public Transport Crowd sourcing and analytics Citizen Interaction
- 5. Three Challenges One Platform 1 Connecting 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
- 6. The next logical step …Sensor
- 7. • 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
- 8. • 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)
- 9. Cisco Confidential 9© 2013-2014 Cisco and/or its affiliates. All rights reserved. APIs Transform IOE Data into Consumable Apps Enable 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
- 10. Decouple Business Logic from the device model
- 11. Remote Management System Management Parking, Lighting, Traffic Mgmt., Citizens engagement. Applications Inter Cloud and City Wi-Fi Sensors and Other Data Sources Versions & Policies Cisco Smart cities Market Place Partners Robust 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
- 12. Smart +Connected Cities - Logical Stack Gateways Lighting API Parking API Kiosk API Traffic API Map API BUSINESS LOGIC CITY APPS DOMAIN LOGIC Models DEVICE LOGIC Facets CIMModels Business City events Policies 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, multisensor Properties: each has 2~4 Relationships: each has 1~3 Actions: 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 API Decouples Business logic from comm layers
- 13. 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
- 14. Use Case – Ped Counts over 100 in KCMO.org
- 15. • 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)
- 16. • 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
- 18. Thank you
Notes de l'éditeur
- Typically, a business owner starts off by identifying the need for an API. Next, the business owner works with an architect to actually design the API means write API secs, they are communicated by the architect to the API development team that will implement the back-end of the API. With this approach, rather than implementing an application and then building the application pn top of it, business first creates the interface, and then the logic, whether it be cloud-based or on-premise. Once an API is designed, created and its back-end implemented, it’s time to find the runtime. Choosing a runtime is crucial as it affects how successful your API strategy will be in terms of service, liability, scale and ability to meet future needs. So what key capabilities should you look for in an API runtime? Hybrid support: deploy applications both in the cloud as well as on-premise without having to modify anything. Scalability, reliability, availability: Q: Data API are not identical to Application API ? You don’t want to own somebody’s data, Rights..etc Policies governance
- Environmental (Thermal, hygrometric, anemometric, sound, gas, particles light (other EM spectrum), seismic Activity: pavement/roadway pressure, vehicle & pedestrian detection, parking space occupancy Virtual Sensor: video camera with analytics (events), apps on smartphone
- The IoE for Cities aims to deliver Innovative and Sustainable Services of public interest for the citizens Services to enhance, ease, secure citizens life but also to foster local economy Services are built on the concepts of Open Data and Open infrastructures, where municipal ICT assets and public Data are made available across a Municipal Area Network The IoE for Cities is a Data-Centric Architecture that enables Data to flow across the city between things, spaces and people. The IoE for Cities Architecture enables open innovative ecosystems to develop the services for the citizen Cisco defines IoE as bringing together people, process, data, and things to make networked connections more relevant and valuable than ever before—turning information into actions that create new capabilities, richer experiences, and unprecedented economic opportunity for businesses, individuals, and countries
- The wire does not drive the content, only transports it
- will enable Urban Services and scale through global and local urban service operators
- Smart Cities have massive numbers of connected assets and sensors, along with dynamic needs for city services Capable of generating .5 to 2 Bullion event / day .3 to 1.5 B contexual relationships Loose coupling and defined architecture , scalable Event-driven systems can scale up to the amount of dynamic relationships, and respond in the required time window for city infrastructure to be contextually intelligent. Device Logic: Workflow - modifier, Tasks -structure, Input, output, invoke –combination-- Handlers and publishers Domain Logic: Things facets – captures physical things, sensors,actuators. Data Facets -Captures the logical entities like Org, parkingSpace, Pipeline. Composite Model – Queries, subcription , Policy, tags Business Logic: Find, where, select modify, action,
- Help bring open data to KC ! Provide your opinion in the form of a vote between the two ideas below that were submitted by other engaged citizens, or drop your own creative idea in the box at the bottom. Your ideas along with others might become the next great app! The City of Kansas City and the Rockhurst Helzberg MBA program thanks you! Ex: Water leakage, Waste water, sanitation data, Traffic patterns during major event
- The combination, coordination and correlation of various systems generate a lot of data. This data is processed and analyzed to create actionable information. The visualization of the data is a major part in progressing from data to intelligible and actionable information Data-centric Architecture for Cities provides users an assortment of E-services (parking guidance, public/alternate transportation information, information about city service) and guarantee an optimized data collection and to modulate the car traffic by adapting the price list of the car parking (yield management) depending on traffic, pollution, noise...
- Connect”, “Collect & Comprehend”. Citizens : Greater citizen-centric services • Through better understanding of citizens’ needs and expectations, an anticipatory Government will be able to serve citizens better through better policy planning and creation of citizen-centric services. Empowerment At an individual level, the access to greater and meaningful information will enable citizens to make better decisions, be it for transport, health and other services. At a community level, the access to rich data and innovative products, suggestions and ideas can help to create actionable solutions that can benefit society as a whole.