We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
FIWARE Lab Context Management Platform - FIWARE Forge Wiki

FIWARE Lab Context Management Platform

From FIWARE Forge Wiki

Jump to: navigation, search

FIWARE Lab implements a context information management platform based on Orion Context Broker to which FIWARE LAB users can access. This platform allows access to real time sensor information and open data datasets, integrating Orion with other FIWARE GEs, such as the Backend Device Management and Cosmos. This section describes the details of this platform, shown in the figure.

The different elements are described following, from bottom to top:

  • Different sensor sources are generating data to feed the platform. In the moment of writing this, the sensor information from Las Llamas park in Santander (Spain) used in the FIWARE LiveDemo along with information coming from other smart cities (Santander, Seville, etc.) is being collected, but we are enriching our sensor base in a regularly basis.
  • In the Data Source Layer, there are several instances of the Backend Device Management GEi that aggregate the information coming from sensors. That information is progressed to a Orion Context Broker instance. Note that, at this level, there is one context broker per Backend Device Management GEi. The FI-LAB user don't access directly to Data Source Layer.
  • The context broker instance at Data Source Layer is federated with the context broker instance at Aggregation Layer. Thus, this context broker, located at orion.lab.fiware.org:1026, receives all the context information from all data sources. This instance is accessible to FI-LAB user (through OAuth2 FIWARE framework), but note that is a shared among all FI-LAB users, e.g. if you register your own entities there, others users can access to them and even modify them.
    • An example of Orion Context Broker client authenticating using OAuth can be found in https://github.com/fgalan/oauth2-example-orion-client. You can use either the full client in Node.js or the simple token_script.sh to get a valid X-Auth-Token (however, this token would expire from time to time, so you are encourage to develop a full fledged OAuth authentication system in your client).
  • FI-LAB users can create their own instances of context broker in the FI-LAB cloud. That way, you can deploy and use a non-shared instance of the broker. You can federate your broker with the shared one in orion.lab.fiware.org using federation, to get the information you need in your application.
  • Finally, note that all information received by the Aggregation layer broker is also stored persistently in Cosmos and you can use that historical information for your applications. More information on this can be found in this wiki page

Currently, this is the information that you will find available in orion.lab.fiware.org:

Entity ID (pattern) Entity type Attributes (1)
OUTSMART.NODE.<id_node> Node
  • TimeInstant
  • Latitud
  • Longitud
  • Presence
  • batteryCharge
  • Illuminance
OUTSMART.RG.<id_regulator> Regulator
  • TimeInstant
  • Latitud
  • Longitud
  • ActivePower
  • ReactivePower
  • electricPotential
  • electricCurrent
urn:smartsantander:testbed:<id_sensor> (2) santander:lux
  • TimeInstant
  • temperature
  • luminousFlux
  • batteryCharge
  • acceleration
  • Latitud
  • Longitud
urn:smartsantander:testbed:<id_sensor> (2) santander:soundacc
  • TimeInstant
  • sound
  • batteryCharge
  • acceleration
  • Latitud
  • Longitud
urn:smartsantander:testbed:<id_sensor> (2) santander:traffic
  • TimeInstant
  • trafficIntensity
  • median_speed
  • average_speed
  • Latitud
  • Longitud
urn:smartsantander:testbed:<id_sensor> (2) santander:sound
  • TimeInstant
  • sound
  • batteryCharge
  • Latitud
  • Longitud
Sevilla:<id_sensor> sevilla:water
  • TimeInstant
  • volume

Notes:

  • (1) In order to know the meaning of the different attributes shown in this column have a look to the FIWARE open dataset central.
  • (2) The fourth types of SmartSantander sensor share the same ID pattern.

Orion Context Broker version deployed in orion.lab.fiware.org

This section provides historical data regarding the particular Orion Context Broker version installed in FI-LAB in a given moment, starting in 0.8.1 FIWARE (3.2.1).

  • 0.8.1 FIWARE 3.2.1: since October 30th, 2013 to December 16th, 2013
  • 0.9.0 FIWARE 3.2.3: since December 16th, 2013 to January 17th, 2014
  • 0.9.1 FIWARE 3.3.1: since January 17th, 2014 to February 26th, 2014
    • In the period from January 17th to January 20th a 0.9.1 release candidate was running
  • 0.10.1 FIWARE 3.3.2: since February 26th, 2014 to April 11th, 2014
    • 0.10.0 was never installed in FIWARE Lab platform
  • 0.11.0 FIWARE 3.3.3: since April 11th, 2014 to May 5th, 2014
  • 0.12.0 FIWARE 3.4.1: since May 5th, 2014 to June, 3rd, 2014
  • 0.13.0 FIWARE 3.4.2: since June 3rd, 2014 to July 2nd, 2014
  • 0.14.0 FIWARE 3.4.3: since July 2nd, 2014 to August 4th, 2014
  • 0.14.1 FIWARE 3.5.1: since August 4th, 2014 to October 8th, 2014
  • 0.15.0 FIWARE 3.5.3: since October 8th, 2014 to November 7th, 2014
  • 0.16.0 FIWARE 4.1.1: since November 7th, 2014 to November 28th, 2014
  • 0.17.0 FIWARE 4.1.2: since November 28th, 2014 to January 13th, 2015
  • 0.18.1 FIWARE 4.2.1: since January 23rd, 2015 to February 12th, 2015
    • 0.18.0 was never installed in FIWARE Lab platform
    • In the period from January 13th to January 23rd a 0.18.1 release candidate was running
  • 0.19.1 FIWARE 4.2.2: since February 12th, 2015 to April 1st, 2015
  • 0.20.0 FIWARE 4.2.3: since April 1st, 2015 to June 9th, 2015
    • 0.21.0 was never installed in FIWARE Lab platform
  • 0.22.0 FIWARE 4.3.2: since June 9th, 2015 to July 13th, 2015
    • In the period from June 23rd to July 13th a hotfixed 0.22.0 version was running
  • 0.23.0 FIWARE 4.3.3: since July 13th, 2015 to September 16th, 2015
  • 0.24.0 FIWARE 4.4.3: since September 16th, 2015 to November 11th, 2015
    • In the period from October 22nd to November 11th a hotfixed 0.24.0 version was running
  • 0.25.0 FIWARE 5.1.1: since November 11th, 2015 to December 1st, 2015
    • From November 19th, a hotfixed 0.25.0 version was running
  • 0.26.0 FIWARE 5.1.2: since December 1st, 2015 to December 9th, 2015
  • 0.26.1 FIWARE 5.1.2: since December 9th, 2015 to February 1st, 2016
  • 0.27.0 FIWARE 5.2.1: since February 1st, 2016 to February 29th, 2016
  • 0.28.0 FIWARE 5.2.2: since February 29th, 2016 to April 11th, 2016
  • 1.0.0 FIWARE 5.2.3: since April 11th, 2016 to May 3rd, 2016.
  • 1.1.0 FIWARE 5.3.1: since May 3rd, 2016 to June 2nd, 2016.
  • 1.2.0 FIWARE 5.3.2: since June 2nd, 2016 to June 16th, 2016.
  • 1.2.1 FIWARE 5.3.3: since June 16th 2016, to September 2nd, 2016.
  • 1.3.0 FIWARE 5.4.3: since September 2nd, 2016 to September 30th, 2016.
  • 1.4.0 FIWARE 5.4.3: since September 30th, 2016 to October 10th.
  • 1.4.1 FIWARE 5.4.3: since October 10th, 2016 to October 31st.
  • 1.5.0 FIWARE 6.1.1: since October 31st, 2016 to December 5th, 2016.
  • 1.6.0 FIWARE 6.1.2: since December 5th, 2016.
Personal tools
Create a book