FiWare

Dutch cities collaborate on Open and Agile Smart Cities

 Blog, OASC, SmartCities  Comments Off on Dutch cities collaborate on Open and Agile Smart Cities
Nov 302015
 
Application abstract network

Amersfoort – Six Dutch cities signed the Open & Agile Smart Cities (OASC) letter of intent to join an initiative that will create smart cities based on the needs of cities and communities. Amersfoort, Amsterdam, Eindhoven, Enschede, Rotterdam and Utrecht declared to join forces and accelerate the smart city wave by adapting the FIWARE Lab NL platform.

The Dutch Open & Agile Smart Cities initiative aims to create an open smart city based on the needs of the market. Cities need interoperability and standards to boost competitiveness by avoiding vendor lock-in, comparability to benchmark performance, and easy sharing of best practices. But most of all, they need practical solutions.

The Dutch OASC cities achieve their vision by adopting four simple mechanisms:

1. Disclose data

To ensure that all cities and developers can disclose the already existing data, FIWARE Lab NL created a CKAN environment in which data will be free to use, but the ownership will remain at the person responsible for delivering the data. In addition to the CKAN environment a CITY SDK solution will enable developers to connect several datasets with each other.

2. Implementation attitude

The participating OASC cities, interested companies and developers also have the opportunity to hand over specific projects and problems that include the use of data for integrated smart city solutions. The lab aims to deliver solutions that will lead to practical implementations within the OASC cities for governments, companies or other developers.

3. OASC cities and their communities

The OASC cities will support regional, national and international open data events like IT Smart Cities at Amersfoort or Amsterdam Smart City. The FIWARE Lab NL will also organise several OASC challenges. These meet-ups will challenge application developers to develop open and agile application for the smart cities by aligning different projects and to create a successful data platform.

4. European connection

FIWARE Lab NL will coordinate open smart city activities in the Netherlands with a connection with the OASC cities. Every city will create alliances with different projects within their city to ensure the local and regional commitment. Amersfoort will remain to be the coordinating city for all the OASC cities. This project will also explore the European potential of the data platform and share results on regular meetings and events.

About FIWARE Lab NL

Fiware Lab NL is the initiative of a consortium with members Deloitte, Civity, Elba-Rec, Onetrail and Xcellent. The Province of Utrecht supports this investment in this innovation infrastructure. Fiware Lab NL is located in Utrecht and Amersfoort.

New FIWARE Open Call for FIWARE Lab Nodes Support

 Developers  Comments Off on New FIWARE Open Call for FIWARE Lab Nodes Support
Oct 072015
 
mapa Open Call

IMPORTANT NOTICE: DEADLINE EXTENDED TO NOVEMBER, 16th at 17h00 CET

Following the success of other FIWARE Open Calls, FI-Core, which helps to fund the FIWARE PPP initiative, has put aside a portion of the budget in order to fund new beneficiaries that will join the association after the project starts. These beneficiaries are selected through a competitive Open Call for those providing FIWARE Lab nodes support.

The goals of the Open Call include (1) the expansion of the FIWARE Lab Association with new nodes to provide improved facilities and services, (2) the reinforcement of the support team with addition resources for first level helpdesk, (3) the promotion of FIWARE instances with credible business plans, (4) the sustainability of FIWARE experimentation and (5) the incorporation of FIWARE players who will stay active beyond FI-Core.

Participants are expected to propose a concrete plan that enables them to achieve these goals during the given time-frame. The successful beneficiaries will be invited to refine and implement the final plan with the project coordinator and the other collaborators.

The selected beneficiaries will be assigned a maximum budget of 1.625.000 € to execute their plan between November 2015 and December 2016. Depending on the support level offered, the maximum EC contribution for individual proposals is from 250.000 € to 325.000 €. Proposals that show long term commitment with the sustainability of the FIWARE technologies will be favoured, even if the activity is limited to the mentioned period of time.

The FIWARE Lab Open Call addresses those who can demonstrate experience and references in implementation of similar plans. We mainly target those who can prove their experience with OpenStack and showing a degree of involvement in developer and user communities will be an advantage.

This announcement will also be broadcasted via Twitter, Facebook & LinkedIn. In depth information, Call details and some helpful directions to prepare your proposal can be found HERE.

Contact e-mail: fiware-opencall-help@lists.fiware.org

FIWARE strengthens its presence in Latin America

 Blog, events, Hackathons  Comments Off on FIWARE strengthens its presence in Latin America
Jul 222015
 
FIWARE
  • In order to achieve technological autonomy, Mexico joins the FIWARE ecosystem and opens the second and most important FIWARE Lab node.
  • This process of integration will help Mexico to develop Smart Cities and cope with problems in the fields of safety, energy management, healthcare and logistics.
  • Different support programs will help entrepreneurs to develop their FIWARE applications.

 

Mexico D.F., 22nd of July 2015. Infotec will lead the integration of Mexico into the FIWARE ecosystem [fiware.org]. This process will include a plan to adopt open standards, thus easing the development of Smart Cities; the launch of a laboratory (linked to a sensor network) to do research on the Internet of the Future and an acceleration program to promote the development of startups using FIWARE. Furthermore, Mexico also opens the second and most important FIWARE Lab node, which will encourage entrepreneurs to JV3A7597experiment with FIWARE technologies. This group, led by Infotec, also includes entities such as Tecnológico de Monterrey, the Mexican Technology Platform, CENIDET, Grupo Plenum and CENTROGeo.

This collaboration is the first step towards an active participation and contribution of these ICT actors to maintain FIWARE. Infotec will be in charge of enhancing, maintaining and supporting key components of the platform, by creating the necessary teams and hosting training sessions. “Mexico has shown a strong commitment with FIWARE, which is a very remarkable step in the bilateral collaboration between Mexico and Europe”, states Juanjo Hierro, FIWARE Chief Architect, who shares the opinion that “there is a need for open standards, which will facilitate the creation of a market which is not constrained by a specific provider.”

FIWARE, a platform that was created in collaboration with the European Commission in 2011, aims at increasing the European GDP in a 0.24 % (28,000 €) by creating new job posts and enterprises based on the Internet of Things. That is the same purpose of FIWARE in Mexico. “There is no free platform that allows industries to develop applications based on the knowledge of universities and research centers”, says Hugo Estrada Esquivel, Research Coordinator in Infotec and leader of the Laboratorio Nacional del Internet del Futuro, which contains the Mexican FIWARE Lab node.

The platform facilitates the creation of an ecosystem to connect developers with a technology that will allow them to work on their ideas. JV3A7611The platform also targets clients, who can ask for applications; and investors, who will be able to accelerate its implementation in the market. In addition, the availability of FIWARE components as open-source code can ease both the adoption of the platform as a standard and the creation of an app market that draws the attention of investors. “It is a technology that gathers universities, enterprises, providers and clients and allows them to collaborate. It will have a huge impact on our local economy”, states the representative of Infotec. This system ensures technological autonomy and improves both Mexican entrepreneurship and innovation, by assembling different actors that used to work separately.

This agreement also includes the incorporation of some cities into the Open & Agile Smart Cities (OASC) initiative. Thus, Mexico joins a project that already gathers 44 cities in 9 countries and that expects 50 cities to have joined by September, around 100 by end of the year. These cities are committed to use the same standards when developing solutions for Smart Cities. The initiative is aimed at transforming cities into engines of growth for their citizens. “Cities joining to the OASC initiative in Mexico will soon witness the impact of FIWARE, which will help them to make the most of their resources and energy, safety, healthcare and logistics systems. Thus, public authorities will save public resources”, says the representative of Infotec.

In order to carry out this plan successfully, organizations like Infotec in Mexico have to master this technology and be able to “organize training sessions and opportunities for entrepreneurs, industry, institutions and universities”, says Juanjo Hierro. “We must bet on a technology that can be supported locally in Mexico”. In order to achieve that goal, one of the first steps may be the implementation of an acceleration program by FIWARE.  Previous experience in Europe will help to promote FIWARE in Latin America. The participation of entities such as CONACYT or the Secretariat of Economy will also be very important for the implementation of funding programs and support entities, such as the Mexican Technology Platform (MTP). As an example, the FP7 CONECTA 2020 initiative, coordinated by Carmen Agüero and presented by Tecnológico de Monterrey, is disseminating the model of Technological Platforms in other Latin American countries, which is a good opportunity to promote FIWARE, considering that these technologies are based on ICT and the Internet of the Future.

Campus Party Mexico and Training Session for FIWARE Trainers

FIWARE will attend the next Campus Party Mexico from the 23rd to the 26th of July. During those days, it will launch the challenge “FIWARE IoT and Context Awareness Smart Apps #CPMX6”, with a prize of $170,000 for the best FIWARE context-aware applications making use of information of the Internet of Things. Furthermore, from the 20th to the 22nd of July, in Infotec, FIWARE will host a training session and conferences to present FIWARE, solutions for Smart Cities and the plans led by Infotec regarding promotion of FIWARE. “Having one of the biggest nodes in the world is worth nothing”, states Hugo Estrada Esquivel from Infotec, “if we do not show the advantages of the platform and train people to use it in their organizations.”

OAuth2-based authorization and authentication in Cosmos WebHDFS at FIWARE Lab

 Developers  Comments Off on OAuth2-based authorization and authentication in Cosmos WebHDFS at FIWARE Lab
Jul 182015
 
FIWARE

APIs in FIWARE should be RESTful APIs. And RESTful APIs in FIWARE should be protected with OAuth2”. This sentence, which is true for most of the enablers in FIWARE, did not completly applied for Cosmos BigData. Until now.

OAuth2 is the evolution of the OAuth protocol, an open standard for authorization. Using OAuth, client applications can access in a secure way certain server resources on behalf of the resource owner, and the best, without sharing their credentials with the service. This works because of a trusted authorization service in charge of emitting some pieces of security information: the access tokens. Once requested, the access token is attached to the service request so that the server may ask the authorization service for the validity of the user requesting the access (authentication) and the availability of the resource itself for this user (authorization).

FIWARE implements the above concept through the Identity Manager GE (Keyrock implementation) and the Access Control (AuthZForce implementation); these two enablers together conform the OAuth2-based authorization service in FIWARE:

  • Access tokens are requested to the Identity Manager, which is asked by the final service for authentication purposes once the tokens are received. Please observe by asking this the service not only discover who is the real FIWARE user behind the request, but the service has full certainty the user is who he/she says to be.
  • At the same time, the Identity Manager relies on the Access Control for authorization purposes. The access token gives, in addition to the real identity of the user, his/her roles according to the requested resource. The Access Control owns a list of policies regarding who is allowed to access all the resources based on the user roles.

And how does this affects to Cosmos BigData? HDFS (big) data can be accessed through the native WebHDFS RESTful API. This API was not protected with FIWARE authentication/authorization mechanisms but with Hadoop ones. This leaded Cosmos to be one of the few remaining “rebel” enablers avoiding homogeneity in the access to FIWARE APIs.

So, what’s next? Let’s learn with an example!

How can I request an access token? Do the following request to the Cosmos Token Generator in FIWARE Lab (cosmos.lab.fiware.org:13000):

$ curl -X POST "https://cosmos.lab.fiware.org/cosmos-auth/v1/token" -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=password&username=frb@tid.es&password=xxxxxxxx

{"access_token": "qjHPUcnW6leYAqr3Xw34DWLQlja0Ix", "token_type": "Bearer", "expires_in": 3600, "refresh_token": “V2Wlk7aFCnElKlW9BOmRzGhBtqgR2z"}

As you can see, your FIWARE Lab credentials are required in the payload, in the form of a password-based grant type (this will be the only time you have to give them).

Once the access token is got (in the example above, it is qjHPUcnW6leYAqr3Xw34DWLQlja0Ix), simply add it to the same WebHDFS request you were performing in the past. The token is added by using the X-Auth-Token header:

$ curl -X GET "http://cosmos.lab.fiware.org:14000/webhdfs/v1/user/frb/path/to/the/data?op=liststatus&user.name=frb" -H "X-Auth-Token: qjHPUcnW6leYAqr3Xw34DWLQlja0Ix”

{"FileStatuses":{"FileStatus":[…]}}

Now, if you try the above request with a random token the server will return the token is not valid; that's because you have not authenticated properly:

$ curl -X GET "http://cosmos.lab.fiware.org:14000/webhdfs/v1/user/frb/path/tp/the/data?op=liststatus&user.name=frb" -H "X-Auth-Token: randomtoken93487345”

User token not authorized

The same way, if using a valid token but trying to access another HDFS userspace, you will get the same answer; that's because you are not authorized to access any HDFS userspace but the one owned by you:

$ curl -X GET "http://cosmos.lab.fiware.org:14000/webhdfs/v1/user/fgalan/path/tp/the/data?op=liststatus&user.name=fgalan" -H "X-Auth-Token: qjHPUcnW6leYAqr3Xw34DWLQlja0Ix"

User token not authorized

Once this point is reached, you may say “OK, but I’m not using WebHDFS at all”. Are you sure? Because, if you are using Cygnus, the tool to build Orion context data archives, then you are using WebHDFS. This is because WebHDFS is the RESTful API used to persist the data in a HDFS backend such as Cosmos. Sadly, any Cygnus version had support for OAuth2… until now. Cygnus 0.8.2 is freshly available and supports OAUth2 through this parameter:

<your_cygnus_agent_name>.sinks.<your_sink_name>.oauth2_token = <your_token>

The token is got from cosmos.lab.fiware.org:13000 as seen before. And upgrading to Cygnus 0.8.2 is as easy as doing:

$ (sudo) yum clean all # just to clean the yum cache

$ (sudo) yum list cygnus# this will show you 0.82 is available

$ (sudo) sudo rpm -e -vv –allmatches –nodeps –noscripts –notriggers cygnus # this is needed if you have installed a version < 0.8.0

$ (sudo) yum install cygnus# this installs 0.8.2

Any doubt? Any question you may have, do not hesitate to contact us through stackoverflow.com or fiware-lab-help@lists.fiware.org. More details can be obtained from these two stack overflow questions:

http://stackoverflow.com/questions/31187977/oauth2-access-to-cosmos-webhdfs-in-fiware-lab

http://stackoverflow.com/questions/31310111/oauth2-in-cygnus

 

IoT Tutorial – Orion Context Broker & Arduino

 Developers  Comments Off on IoT Tutorial – Orion Context Broker & Arduino
Jun 102015
 
Orion Context Broker

By Telefónica  R&D Chile.

This tutorial will be divided into parts for easier reading and practical purposes.

1. Introduction to the technologies used

2. Hardware configuration

3. Arduino, software and communications

4. Orion Context Broker (FIWARE)

5. Action from a remote web

The idea of ​​this tutorial is to learn some theoretical concepts and quickly apply them in practice. Possibly, when you finish this tutorial, you will have imagined hundreds of alternatives based on the original concept to create a sensor-based solution connected to the Internet (basic principle of the Internet of Things).

Come on, let's get started!

Introduction to the technologies used

Before we start, it’s important to briefly review and understand some key concepts. If you are familiar with these concepts, you can proceed directly to the next section.

First of all, the Internet of Things corresponds to the third great wave in computer technology. The first wave was the development of computers in the 60s, then the use and exploitation of the Internet, with mass penetration starting in the eighties, and now the IoT. But what is the Internet of things?

To answer the question above, we must understand the concept of 'connected things' whereby electronic devices can send and receive information via the Internet. Examples including home thermostats, smart cars, entry controls and a thousand other devices. But the reader might be wondering why these devices should be connected to the Internet.

Primarily because the data obtained from these devices can later be combined with other data to obtain more advanced functionalities. Imagine you set your smartphone alarm to wake you up in the morning. It's winter so there is not much light when you wake up. At the sound of the alarm, soft lighting is activated, the toaster starts to warm your bread and the coffee begins to heat up. This may be a rather elementary example, but it helps us to understand that the more information we have and can interrelate, the more devices we can actually create to help improve our quality of life.

One interesting point to discuss is the use of standards. For the specific case we will review later in Orion Context Broker section, an adaptation based on the OMA (Open Mobile Alliance) NGSI (Next Generation Service Interface) specification is used. In simple terms, this means that the HTTP requests or actions to be used are those that are currently employed by browsers such as GET, POST, DELETE and PUT to interact with the Context Broker.

We have reached the end of part one of this tutorial, so let’s get started with the practical information.

Hardware configuration

This is now the practical part of tutorial, so let’s get started!

The components we will be using are:

• An Arduino Board (there are many alternatives, but a version with WiFi is essential)

• A breadboard

• LEDs

• Connecting cables

• A router or a cellular device that can deliver WiFi (tethering)

As a brief introduction to Arduino, it should be highlighted that this hardware is based on an Open-Source specification that, using a board with a microcontroller, allows interaction with numerous devices such as sensors, lights, switches, etc.

Arduino has its own interface development using the C ++ language and integrates a number of libraries to facilitate the 1implementation of prototypes. This does not mean that Arduino cannot be used in industrial or high-demand environments. However, in these scenarios cost issues usually lead to the use of ad-hoc components.

When observing the structure, you can recognize some digital pins on the top and analogue pins at the bottom. Also, at the bottom, is the row of connectors to power a testing board or breadboard. The board also must have a connector to an electrical outlet and a USB mini connector, among other components, depending on the version of the board and if you use add-on 'shields' or not.

If we connect a LED to the board we can do so directly, connecting the LED to digital pin 13 and the GND as seen here. Although it should be noted that the digital pin 13 comes with a resistor, so it would be unnecessary in the image below. (In other pins resistors must be installed) .

 

2

Lastly, the same result can be obtained using a breadboard. This is a good idea if you want to add more LEDs or sensors to our Arduino board so you can add more functionalities. Remember that on a breadboard power runs horizontally in the outer points and vertically in the inner points. So the result is:

 

3

Take note: Specifically, the Intel Edison Arduino board requires 2 Micro USB cables and a power connection.

Hard to understand? I hope not. This concludes part two of our tutorial.

Arduino, software and communications

In this tutorial we will learn how to program the Arduino board so as to turn the LED we installed in part two on and off. Then, we’ll use an internet connection with the board’s WIFI.

As a prerequisite, we must have already configured the Arduino software as per our operating system. Also, we must keep the board’s USB connected to our computer to load the program to our board. Look here to see how to install the (Intel Edison) software.

You must select the version of the software that corresponds to your operating system.

Once the software is configured and installed we open our IDE and start the coding.

This is an example of the Arduino IDE.  This is specifically the IDE for Intel sets, although the concepts are the same.

 

4

In the second row menu (where the check icon is), you’ll find the commands to compile and upload our developments to the board.

Looking at the code, we have two functions. One is setup, where variables are normally initialized and the loop where the operations are executed as required.

In the File menu we have the option Examples – 01 Basic – Blink. This will display a new window with the code needed to test our LED:

/*

Blink

Turns on an LED on for one second, then off for one second, repeatedly.

This example code is in the public domain.

*/

// Pin 13 has an LED connected on most Arduino boards.

// give it a name:

int led = 13;

 

// the setup routine runs once when you press reset:

void setup() {

// initialize the digital pin as an output.

pinMode(led, OUTPUT);

}

 

// the loop routine runs over and over again forever:

void loop() {

digitalWrite(led, HIGH); // turn the LED on (HIGH is the voltage level)

delay(1000); // wait for a second

digitalWrite(led, LOW); // turn the LED off by making the voltage LOW

delay(1000); // wait for a second

}

The example that Arduino generates is quite simple. In line 10 a variable is set with the corresponding pin number on the board. Afterwards, the pin with the variable 'led' as an output is initialized. And, in the loop, the LED is turned on and off separated by a delay of one second. Before loading the code to the board, the IDE must be configured so it knows which board and what port we’re using:

Select Tools> Board> Intel Edison

Select Tools> Port> dev / ttyACM0

Now, if the board is properly plugged into the USB port, we can 'Upload' the code to the board (Ctrl + U) and we should see our LED turning on and off every second. Amazing! Right?

Now to use the WIFI, we need to work a little harder. Luckily, in the Arduino examples, we have a WIFI section with different alternatives when using networking solutions. Among them are Telnet servers and clients, Web servers and clients and even a Twitter client.

TIP: In our case, for purposes of simplicity, we can use a Web client since we will subsequently send requests to the Orion Context Broker using the HTTP protocol. Note that there are better solutions, but for educational purposes we’ll try to minimize the code as much as possible.

#include <SPI.h>

#include <WiFi.h>

   /**************************/

  /*  Setup configuration              */

/************************/

char ssid[] = "YourWifiSSID";                     //  Name of the network

char pass[] = "WifiPassword";                       // Network password

char server[] = "130.206.80.47";                    // ORION IP address -> Create in /lab/

int status = WL_IDLE_STATUS;   // we predefine the status as On but not connected

int led = 13;                                     // We initialize a variable to assign the pin number to which the led will be connected

/**

* Arduino Setup configuration

* (Execute only once)

**/

void setup() {

  // Inititialization of the Arduino serial port

  Serial.begin(9600);

  while (!Serial) {

    ; // wait for serial port to connect. Needed for Leonardo only

  }

  // Verify that the board has a WiFi shield

  if (WiFi.status() == WL_NO_SHIELD) {

    Serial.println("Wifi shield is not available");

    // Do not continue with setup, or in other words, stay here forever

    while(true);

  }

The complete code is available in:

https://bitbucket.org/tidchile/ecosystem/src/

FIWARE and Orion Context Broker

As discussed earlier in this tutorial, the Orion Context Broker is a service that based on the OMA NGSI 9/10 standard and can handle sending and receiving contextual information. What does this mean? Primarily, to handle a large number of messages from entities and manage updates, queries, and also handle data subscriptions from the entities. Remember that according to the NGSI 9 and 10 standards, we handle entities as an abstraction of the physical nodes or devices used in IoT solutions.

In the example above, we made an update request to an entity already created. But first let's review how to work with Orion. A simple way to test the OCB service is to create an account in https://account.lab.fiware.org/ and create a virtual machine with Orion preconfigured in the Cloud section. Alternatively, access Orion’s GitHub site and download a virtual machine to run in our local environment

Another useful tool is a REST client, but we can use cURL if it seems simpler. RESTClient is a client for Firefox that is fairly easy to use.

The configuration aspects of the OCB are outside the scope of this tutorial, as it would require too much detail. Regarding the FIWARE Lab, it is important to note that FIWARE provides virtual machines in the Cloud for free to test FIWARE compontents. You only need to create an account to access the services. Only a quick caveat. As of today (19-03-2015) and temporarily, Spain has no resources available, but there are other regions where VMs can be created. 

When we have the necessary tools, the most basic way to interact with the OCB is:

1. Create an entity:

To do this you must take into consideration several factors.  Firstly, the call is sent as an HTTP POST request, for example, http://myhost.com:1026/v1/updateContext. By this we mean that we are occupying version 1 of the API with the updateContext operation.

We also have to define several variables in the header of the request:

Accept: application/json

Content-Type: application/json

X-Auth-Token: [TOKEN AUTHENTICATION]

Regarding the token generation, the simplest way is to use python script created by Carlos Ralli on GitHub. A FIWARE account and running the 'get_token.py' script is required.

After setting the header of the request, configure the 'body' of the request using the following JSON code:

{

  "contextElements":[

    {

      "type":"LED",

      "isPattern":"false",

      "id":"LED001",

      "attributes":[

        {

          "name":"switch",

          "type":"bool",

          "value":"false"

        }

      ]

    }

  ],

  "updateAction":"APPEND"

}

Here is the structure of a "context Elements" which is a group of entities with certain attributes such as "type", "isPattern" and "id". "type" refers to a defined type and allows searching for entities by a particular type. "id" is an attribute that must be unique for each entity to execute searches based on this ID. "IsPattern" will be explained later in point No. 2.

You can also add a number of attributes to the entity in the "attributes" property, where each attribute is defined by  "name", "type" and  "value". Finally, "updateAction" defines whether we will perform an "APPEND" or and "UPDATE".

If all went well, we will receive a 200 OK response from the server and it will give us the details of the entity created:

{

  "contextResponses" : [

    {

      "contextElement" : {

        "type" : "LED",

        "isPattern" : "false",

        "id" : "LED001",

        "attributes" : [

          {

            "name" : "switch",

            "type" : "bool",

            "value" : ""

          }

        ]

      },

      "statusCode" : {

        "code" : "200",

        "reasonPhrase" : "OK"

      }

    }

  ]

}

2. Consult an entity:

To consult an entity, the standard operation is 'queryContext' which would be http://myhost.com:1026/v1/queryContext . We also apply the headers described in point No. 1 and use POST.

The JSON used in the body of the request would be as follows:

{

  "entities":[

    {

      "type":"LED",

      "isPattern":"false",

      "id":"LED001"

    }

  ]

}

This is where you can use "isPattern" in "true" and work either the "type" field or "id" field with regular expressions if we want to execute a slightly more complex search. In the example above we are only looking for the same entity created through the "id".

There is also a simpler way to do the same query using the following request: GET http://myhost.com:1026/v1/contextEntities/LED001 where LED001 is the "id" of the entity to search for.

3. Update an entity:

This is identical to point No. 1 but changing the "updateAction" attribute from "APPEND" to "UPDATE".

Finally, integrating all that we reviewed, we will be able to generate an action from a simple Web page that can be deployed on a remote server and actually prove that the application’s LED is activated remotely using the OCB.

To do this we will use the LED001 recently created, by setting the 'switch' attribute from true to false and vice versa to check the action.

Our web would look like this:

 

5

For this, the html code, css and js are shared in:

https://bitbucket.org/tidchile/ecosystem/src/

Consortium and EBU announce FIWARE Lab NL

 Blog  Comments Off on Consortium and EBU announce FIWARE Lab NL
May 212015
 
fiwarelabnl

The Netherlands will soon have its first FIWARE Lab node. This was announced by a consortium of 5 companies (Civity, Deloitte, Elba-Rec, Onetrail and Xcellent), supported by the Economic Board Utrecht. This initiative makes the Netherlands walk in the footsteps of European countries such as Germany, France, Italy and Spain as well as Mexico.

First-class Open Data source of the Netherlands

FIWARE Lab NL will be available and connected to other FIWARE Lab nodes in September 2015. The node will enable developers to freely use standard building tools. "Because FIWARE Lab NL is also focusing on open data and dynamic context information describing the state of the city (e.g., location of buses) through FIWARE standard APIs, it will become the best open data source for developers in the Netherlands", said Arjen Hof, Managing Director of Civity. This combination of Open Data/APIs and building tools will be reusable and will significantly accelerate the development of applications.

Unique Physical meetings, unique in Europe

Besides virtual events, FIWARE Lab NL also organise physical meeting sessions in cooperation with several Startup Centers. This is a unique opportunity for Startups to get familiar with FIWARE and its community members. "At those meetings, people share knowledge, work together on great ideas, and potential customers, such as cities, meet developers in an innovation-focused atmosphere", explained Jeroen Moonen, General Manager of Onetrail. FIWARE Lab NL also embraces programmes from the Economic Board Utrecht on ‘Green’, ‘Smart’ and ‘Health’ and aims to connect to other Smart City programmes in the Netherlands to promote FIWARE and FIWARE Lab NL to (local) developers and municipalities.

Smart Cities

A first group of of cities and companies have stated their interest in using FIWARE Lab NL. Actually, the cities of Amersfoort and Utrecht have expressed their clear intentions to have FIWARE applications developed relying on resources available through FIWARE Lab NL. This will pave the way for these municipalities to join the Open and Agile Smart Cities (OASC) initiative, recently launched (last March), which gathers together cities committed to adopt a common set of de facto standards for Smart Cities. It is very likely that other cities will follow soon. "FIWARE Lab NL does not only facilitate, but also wants to play a match making role between entrepreneurs and organisations like cities with their respective projects", said Tom Willebrandts, Innovation Manager for the City of Amersfoort.

20 million Euros in investment

Applications developed in FIWARE Lab NL will be easy to reuse and made scalable on a European level. This leads to new jobs and (business) opportunities for companies in the Utrecht region. These opportunities should eventually lead to an economic spin-off of roughly 1,500 jobs and investments of 20 million euros until 2020. That’s why organizations supporting the operation of the FIWARE Lab NL are also planning to provide a commercial FIWARE Cloud.

Municipalities, companies, developers, and other interested parties will find more information about FIWARE Lab NL at www.fiware-lab.nl. That is also the place to sign in for more information about the upcoming opening of the lab in September 2015.


Note

For more information, please contact Arjan Ankerman at info@fiware-lab.nl or +31 (0)33-8700 100.

Spotlight on FIcontent Specific Enablers for Media & Content

 Blog, Developers  Comments Off on Spotlight on FIcontent Specific Enablers for Media & Content
Apr 212015
 
ficontent

The following post has been written by the team of FIcontent. We would like to thank them for their collaboration and their willingness to participate.

The advent and spread of the Internet as well as the development of connected devices have led to a striking technological convergence of audio-visual, telephone and computer networks, enabling the communication of content more rapidly and far-reaching than ever before and leading to profound effects on people’s habits. Nowadays, citizens not only interact with other individuals but also with all kind of media.

The FIcontent project develops Specific Enablers (SEs) within the framework of the FIWARE initiative supported by the European Commission, taking into account this new social model and aiming to provide innovative, practical and valuable tools, enhancing individual’s experience towards media and content.

1. The FIcontent platforms

FIcontent partners have created and tested a rich library of SEs with reference implementations, allowing developers to put into effect functionalities and to develop an application right away in three specific domains: Social Connected TV, Smart City Services, Pervasive Games, through three specific platforms.

The Social Connected TV platform

The Social Connected TV platform is designed to foster the development and uptake of TV applications based on Future Internet technologies. This platform demonstrates a number of exciting innovations and new user experiences based on open standards such as HbbTV and HTML5. Personalized services will help users easily access and find content based on data inferred from the behaviour of individuals and groups of users, as well as on explicit data provided by the users.

A few examples of Social Connected TV SEs are presented below:

Content Enrichment provides functions to create, distribute and play interactive video content across platforms and devices by making objects in the video clickable for their viewers. Watch the Content Enrichment demonstration video.

HbbTV Application Toolkit provides a powerful tool set for Broadcasters, program editors as well as TV app developers to create HbbTV compliant TV apps in a fast and easy way. A video presents the HbbTV Application Toolkit.

2.1

HbbTV Application Toolkit SE

The Smart City Services platform

The Smart City Services platform provides contextualization, recommendation, live information, mixed reality, 3D, sharing capacities and communications technologies to enable creative people to generate, share and combine assets, objects and stories and develop mobility city services. This platform allows people to login, connect and build communities to interact with each other and gain from social network streams.

Discover some Smart City Services SEs:

Open City Database SE is an open source database management system for any smart city related data (e.g. points of interest, open city data and related media from various sources). Watch the Open City Database demonstration video.

Social Network SE is a set of software modules that enable to create a social network. Watch the Social Network demonstration video.

2.2 2.3

 

 

 

 

 

 

Test of the Social Network SE during the Carnival of Cologne, Germany

The Pervasive Games platform

The Pervasive Games platform demonstrates a strong mix of real life and Internet experience in a playful way and shows advances in 3D or virtual world environments in a way that becomes immersive and ‘’real’’. The platform focuses on multiplayer mobile gaming that leverages the future Internet technology in order to enable large groups of users to participate in innovative mobile gameplay experiences. A central theme of this new social gaming platform is moving beyond the traditional paradigm in which a user is fixed in front of a console or display. In this way, the game becomes an augmented version of the real world that delivers a more compelling experience than traditional console games or the simplistic social games that dominate today’s market.

Some Pervasive Games SEs are presented below:

Networked Virtual Character is provided as a plugin to the FIWARE Synchronization GE and thereby extends its synchronization capabilities to virtual characters while supporting a variety of cross-platform clients. Watch the Networked Virtual Character demonstration video.

Reflection mapping measures camera properties and adapt the virtual objects to fit to the camera image background visually. Reflection mapping is used in the Augmented Resistance game.

2.3 2.4

 

 

 

 

 

 

Augmented Resistance Game using the Reflection mapping SE

2. The FIWARE Media & Content Lab

In order to facilitate access to all these SEs, FIcontent is now developing the FIWARE Media & Content Lab, a live instance providing everything SMEs and developers need for discovering the FIWARE Specific Enablers for media and content, trying them with short demos, and even directly tweaking the client-side code of the Specific Enablers and seeing the results live in the browser.

The FIWARE Media & Content Lab will even allow developers to very easily deploy the Specific Enablers on the FIWARE Lab cloud or on any other machine, with its “run” function.

Stay tuned on http://mediafi.org

2.5

FIWARE Media & Content lab homepage

 

2.6

 

FIWARE Media & Content lab “Discover” page

FIWARE Lab from the Engine Room

 Blog  Comments Off on FIWARE Lab from the Engine Room
Jan 082015
 
Future Internet Opportunities for Smart Cities

The following post has been written by Miguel Carrillo Pacheco, Project Manager at Telefonica R&D. We would like to thank him for his participation and his willingness to collaborate.

It seems like it was yesterday, but it was back in the summer of 2013 when Mrs Neelie Kroes, former Vice-President of the European Commission, officially launched the FIWARE Lab in Campus Party London. People saw the flashes, the CEOs giving speeches and the large audiences in great auditoriums. But … what stood behind the cameras?

To understand what made it possible we must know that a key partner joined the FIWARE consortium in June 2012, a year before launching the FIWARE Lab. Red.es manages RedIRIS, the National Research and Education Network (NREN) in Spain, so they already had the know-how and experience required to provide the connectivity and the housing of servers of FIWARE Lab’s first node. Better still, they are in a company-neutral position as they are a governmental entity, related to the Spanish Ministry of Industry, Energy and Tourism. Once Red.es learned about FIWARE, they enthusiastically supported us and, after the usual formal steps, they joined the consortium. You cannot imagine how much effort and determination it takes to build a new lab from scratch, and especially one of this magnitude: procurements of network switches and computing nodes, creation of data center facilities able to house them, network setup… Also, we needed the contribution of other public entities which were crucial for our success. Depending on the case, they contributed with room for the labs or even with computing capacity. We are speaking about the University of Cantabria and both the Seville and Malaga City Councils in a first phase, the University of Las Palmas de Gran Canaria in a second phase. All of them in connection with Santander and Las Palmas de Gran Canaria City Councils to provide Open Data to the platform.

After thousands of emails, a first production-ready FIWARE Lab was available for the Campus Party in London. FIWARE Lab has come a long way since then, the capacity is continuously growing and new nodes are joining. And this is not only about infrastructure and GEs, many cities are willing to join us and are starting to progressively publish their Open Data via FIWARE Lab.

The second major breakthrough of FIWARE Lab was the expansion to a European network of federated nodes thanks to the XIFI project. FIWARE is twinned with this project that focuses on the uptake, deployment and federation of instances of FIWARE facilities. This is achieved via one of their major results, FIWARE Ops, a collection of tools that ease the deployment, set-up and operation of FIWARE nodes expanding an existing FIWARE instance such as the FIWARE Lab, or the creation of new FIWARE instances.

Today, FIWARE Lab has turned into a truly pan-European network of federated nodes that keeps on growing to multiple locations (expected to reach 3000+ cores, 16TB+ Ram, 750TB+ HD soon). Users can decide on what location/node to deploy their service. All of the nodes are accessible by a single user portal and work in the same way, no matter where you are! Putting together current nodes and future incorporations, we already have many nodes: Spain, Trento, Lannion, Waterford, Berlin, Mexico, Zurich, Budapest, C4I, Karlskrona, Gent, Prague, two locations in the Athens area, Volos, Stockholm, Poznan, Crete, …

Wait! Did we say pan-European? We’d better say GLOBAL. Yes, a Mexican node comprising 1200+ servers funded by Infotec and Conacyt recently joined the FIWARE Lab and it is one of its more prominent nodes from October 2014 onwards. We are in talks with new incorporations from Brazil, Chile, Japan …

This is just the beginning; let us see what the future brings.