Slides used during the training session of FIWARE in the TMForum Open:Hack that takes place in Nice on 6th and 7th.

1. © 2016 TM Forum Live! 2016 | 1
Open Hack FIWARE
Training Session
May 6th 2016

2. © 2016 TM Forum Live! 2016 | 2
Orion Context Broker
FIWARE NGSI v9 and v10 implementation

3. © 2016 TM Forum Live! 2016 | 3
Being “Smart” requires being “Aware”
 Smart City Applications requires gathering and managing context
information, referring to values of attributes characterizing entities
relevant to the application
 NGSI brings a simple yet powerful API enabling access to context
information
Application
NGSI standard API
Bus
• Location
• No. passengers
• Driver
• License plate Citizen
• Name-Surname
• Birthday
• Preferences
• Location
• ToDo list
Context Information
Shop
• Location
• Business name
• Franchise
• offerings

4. © 2016 TM Forum Live! 2016 | 4
Different Sources of Context
 Context information may come from many sources which may vary over time:
 Existing Systems dealing with management of municipal services
 Sensor networks (Internet of Things)
 Third-party smart city APPs
 Source of information needs to be transparent to applications accessing
context information
NGSI Standard API
Current traffic
in street “X”
A sensor in a
pedestrian street
Citizen’s car app or
smartphone
Notify traffic
in street “X”
Current traffic
in street “X”
Public Transport
System

5. © 2016 TM Forum Live! 2016 | 5
Integration with Sensor Networks
 FIWARE NGSI is capable to deal with the wide variety of IoT protocols today
 Rather than trying to solve the battle of standards at IoT level, it brings a
standard where no standard exists today: context information management
FIWARE Context Broker
IoT
Agent-1
IoT
Agent-2
IoT
Agent-n
IoT Agent
Manager
create/monitor
FIWARE Backend IoT
Device Management
OMA NGSI API (northbound interface)
(southbound interfaces)
MQTTETSI M2M IETF CoAP

6. © 2016 TM Forum Live! 2016 | 6
Notifications
 Get a notification when a update on context information
takes place
Bus = “X”, last_stop = “A”,
arrived= “Yes”
PUSH
Notify me when bus “X”
arrives at the bus stop “A”
API

7. © 2016 TM Forum Live! 2016 | 7
Devices Interaction
 Acting on devices can be as easy as changing the value of
attributes linked to its corresponding entity
Street lamp = “lamp1”, status= “on”
Street Lamp lamp1.status  “on”
API

8. © 2016 TM Forum Live! 2016 | 8
Additional Details
 Main functions:
 Context availability management
 Context management
 HTTP and REST-based
 XML payload supported in older versions
 JSON payload support
 Context in NGSI is based in an entity-attribute model:
Attributes
• Name
• Type
• Value
Entity
• EntityId
• EntityType 1 n
“has”

9. © 2016 TM Forum Live! 2016 | 9
Nutshell
Orion Context Broker
Context
Producers
Context
Consumers
subscriptions
update
query
notify
notify
update
update
DB
1026
1026

10. © 2016 TM Forum Live! 2016 | 10
Operations
 NGSI 10
 checkHealth
 updateContext
 queryContext
 subscribeContext
 updateContextSubscription
 unsubscribeContextSubscription

11. © 2016 TM Forum Live! 2016 | 11
Operations – Check Health
GET <cb_host>:1026/version
{
"orion" : {
"version" : "0.17.0",
"uptime" : "7 d, 21 h, 33 m, 39 s",
"git_hash" : "238c3642ad67899da7c1ff08aba4b5c846b4901a",
"compile_time" : "Mon Dec 1 11:27:18 CET 2014",
"compiled_by" : "fermin",
"compiled_in" : "centollo"
}
}

12. © 2016 TM Forum Live! 2016 | 12
Operations – Create Entity (1)
POST <CB_HOST>:1026/v1/updateContext
...
{
"contextElements": [
{
"type": "Car",
"isPattern": "false",
"id": "Car1",
"attributes": [
{
"name": "speed",
"type": "float",
"value": “98"
}
]
}
],
"updateAction": “APPEND"
}

13. © 2016 TM Forum Live! 2016 | 13
Operations – Create Entity (2)
200 OK
...
{
"contextResponses": [
{
"contextElement": {
"attributes": [
{
"name": "speed",
"type": "float",
"value": "98"
}
],
"id": "Car1",
"isPattern": "false",
"type": "Car"
},
"statusCode": {
"code": "200",
"reasonPhrase": "OK"
}
}
]
}

14. © 2016 TM Forum Live! 2016 | 14
Operations – Update Entity (1)
POST <CB_HOST>:1026/v1/updateContext
...
{
"contextElements": [
{
"type": "Car",
"isPattern": "false",
"id": "Car1",
"attributes": [
{
"name": "speed",
"type": "float",
"value": "110"
}
]
}
],
"updateAction": "UPDATE"
}

15. © 2016 TM Forum Live! 2016 | 15
Operations – Update Entity (2)
200 OK
...
{
"contextResponses": [
{
"contextElement": {
"attributes": [
{
"name": "speed",
"type": "float",
"value": "110"
}
],
"id": "Car1",
"isPattern": "false",
"type": "Car"
},
"statusCode": {
"code": "200",
"reasonPhrase": "OK"
}
}
]
}

16. © 2016 TM Forum Live! 2016 | 16
Operations – Query Context (1): Get all the attributes of an Entity
POST <CB_HOST>:1026/v1/queryContext
...
{
"entities": [
{
"type": "Car",
"isPattern": "false",
"id": "Car1"
}
]
}

17. © 2016 TM Forum Live! 2016 | 17
Operations – Query Context (2): Get all the attributes of an Entity
200 OK
...
{
"contextResponses": [
{
"contextElement": {
"attributes": [
{
"name": "speed",
"type": "float",
"value": "110"
}
],
"id": "Car1",
"isPattern": "false",
"type": "Car"
},
"statusCode": {
"code": "200",
"reasonPhrase": "OK"
}
}
]
}

18. © 2016 TM Forum Live! 2016 | 18
Operations – Query Context (3): Filter Entities by Pattern
POST <CB_HOST>:1026/v1/queryContext
...
{
"entities": [
{
"type": "Car",
"isPattern": "true",
"id": "Car.*"
}
],
"attributes": [
"speed"
]
}

19. © 2016 TM Forum Live! 2016 | 19
Operations – Subscriptions
 Context Consumers can subscribe to receive context information that satisfy
certain conditions using the subscribeContext. Such subscriptions may have a
duration.
 The Context Broker notifies updates on context information to subscribed
Context Consumers by invoking the notifyContext operation they export
subscription_id = subscribeContext (consumer, expr, duration)
Context Consumer
notifyContext (subscription_id, data/context)
Context Broker
Application

20. © 2016 TM Forum Live! 2016 | 20
Operations – Creating a Subscription (1)
POST
<cb_host>:1026/v1/subscribeContext
...
{
"entities": [
{
"type": "Car",
"isPattern": "false",
"id": "Car1"
}
],
"attributes": [
"speed"
],
"reference":
"http://<host>:<port>/publish",
"duration": "P1M",
"notifyConditions": [
{
"type": "ONCHANGE",
"condValues": [
"position"
]
}
],
"throttling": "PT5S"
}

21. © 2016 TM Forum Live! 2016 | 21
Operations – Creating a Subscription (2)
200 OK
...
{
"subscribeResponse": {
"duration": "P1M",
"subscriptionId": "51c0ac9ed714fb3",
"throttling": "PT5S"
}
}

22. © 2016 TM Forum Live! 2016 | 22
Operations – Receiving Notifications
 When one of the attributes change its value, the Context
Broker will make a POST request to the URL specified in the
reference field.
POST http://<host>:<port>/publish
...
{
"subscriptionId": "51c0ac9ed714fb3",
"originator": "localhost",
"contextResponses" : [
{
"contextElement" : {
"attributes" : [
{
"name" : "speed",
"type" : "float",
"value" : "19"
}
],
"type" : "Car",
"isPattern" : "false",
"id" : "Car1"
},
...

23. © 2016 TM Forum Live! 2016 | 23
Convenience Operations
 They are equivalent to previous standard operations in functionality
 Avoid the need for POST-ing payloads in many cases or simplifying them
considerably
 Simple to write, more REST-like
 They are not a substitute but a complement to standard NGSI operations
 Not working in old instances
 Four examples (there are many others):
 Entities
 Attributes
 Subscriptions
 Types

24. © 2016 TM Forum Live! 2016 | 24
Convenience Operations - Entities
 Retrieves an entity
 GET /v1/contextEntities/{entityID}
 Creates an entity
 POST /v1/contextEntities/{entityID}
 Updates an entity
 PUT /v1/contextEntities/{entityID}
 Deletes an entity
 DELETE /v1/contextEntities/{entityID}

25. © 2016 TM Forum Live! 2016 | 25
Convenience Operations – Attributes
 Retrieves an attribute’s value
 GET /v1/contextEntities/{entityID}/attributes/{attrID}
 Creates a new attribute for an entity
 POST /v1/contextEntities/{entityID}/attributes/{attrID}
 Updates an attribute’s value
 PUT /v1/contextEntities/{entityID}/attributes/{attrID}
 Deletes an attribute
 DELETE /v1/contextEntities/{entityID}/attributes/{attrID}

26. © 2016 TM Forum Live! 2016 | 26
Convenience Operation – Subscriptions
 Creates a subscription
 POST /v1/contextSubscriptions
 Updates a subscription
 PUT /v1/contextSubscriptions/{subID}
 Cancel a subscription
 DELETE /v1/contextSubscriptions/{subID}

27. © 2016 TM Forum Live! 2016 | 27
Convenience Operations – Entity Types
 Retrieve a list of all entity types currently in Orion, including
their corresponding attributes
 GET /v1/contextTypes
 Retrieve attributes associated to an entity type
 GET /v1/contextTypes/{typeID}

28. © 2016 TM Forum Live! 2016 | 28
Endpoints
Endpoint NGSI
version
Entity Types
OPORTO
http://130.206.83.68:1026 2 AmbientAreas
http://fiware-porto.citibrain.com:1026 1
EnvironmentEvent
TrafficEvent
https://api.ost.pt 1 POI
SANTANDER
http://mu.tlmat.unican.es:8099 1
AmbientArea
AmbientObserved
ParkingLot
http://130.206.85.12:1026 1 device (Buses)
http://orion.lab.fiware.org:1026 1
santander:device
santander:sound
santander:traffic
http://130.206.83.68:1026 2 StreetParking

29. © 2016 TM Forum Live! 2016 | 29
Endpoints
 Valencia
 http://mapas.valencia.es
 Other interesting FIWARE Data Portals
 http://datosabiertos.sevilla.org
 http://datos.santander.es
 http://gobiernoabierto.valencia.es/en
 https://data.lab.fiware.org

30. © 2016 TM Forum Live! 2016 | 30
Aitor Magán
@AitorMagan

31. © 2016 TM Forum Live! 2016 | 31

32. © 2016 TM Forum Live! 2016 | 32
What is WireCloud?
Backend
service Backend
service
Backend
service
Object Storage
API
NGSI API
Context
Broker

33. © 2016 TM Forum Live! 2016 | 33
What can I do with WireCloud?
 From the developer perspective:
 Use web technologies for easily developing mashable web components
(widgets)
 Integrate web mashups with backend services (e.g. support for pub/sub,
“connectors” to a number of FIWARE GEs, etc.)
 From the user perspective:
 Develop application mashups: integrate heterogeneous data, application
logic, and UI web components to create value added instant applications.
 Without the need of programing skills (e.g. end users, infomediaries, etc.)
 Fostering the reuse and shareability of widgets, mashups, etc.

34. © 2016 TM Forum Live! 2016 | 34
Features
 Wiring
 Wiring and support for channel creation
 HTTP proxy
 Cross-site HTTP requests
 APIs to some GEs
 Context Broker, Object Storage
 Public App Mashups
 Access without login to a mashup
 Embedded mashups
 Integrate public mashups in any website

35. © 2016 TM Forum Live! 2016 | 35
Aitor Magán
@AitorMagan