Consume IoT Offerings

Assuming, you want to create a new parking app for the city of Barcelona that is supposed to display parking data on a web dashboard for different places in the city. Using the BIG IoT Consumer Lib, it is very easy to make your service query the BIG IoT Marketplace relevant data sources and access them.

The Consumer Lib offers the following main functionalities:

  1. Creation of a BIG IoT Consumer and authentication on the Marketplace
  2. Discovering Offerings on the Marketplace according to a Query specification
  3. Subscribing to Offerings of interest
    • Based on known Offering ID
    • Based on discovered Offerings
  4. Accessing Offerings based on a one-time request or in a continuous fashion

The complete java program of this example is available here.

Note: You can also clone/download a complete Java project for an example provider that you can build and run directly (using gradle) here.

1. Creation of a BIG IoT Consumer and Authentication on the Marketplace

Before you can consume offerings available on the marketplace, you need to sign-up on the marketplace here. Once you are logged in, you can create a new Organization for yourself (just click on “New Organization”). In a next step, you can create a new Consumer instance (click on “MyConsumers” and then “+Consumer”). After you created a new Consumer, you can copy the unique Consumer ID and Secret into your program in order to associate your Consumer application with the newly created Consumer instance on the marketplace.

String CONSUMER_ID 	= "TestOrganization-TestConsumer";
String CONSUMER_SECRET 	= "***************************";

Consumer consumer = Consumer.create(CONSUMER_ID, CONSUMER_SECRET)

With this in place, you can now create a new Consumer instance in your application by providing the Consumer ID and Marketplace URL. In a next step, you need to authenticate this on the marketplace using your Consumer Secret.

If you want to connect to multiple marketplaces, just repeat the previous steps and create another Consumer instance.

2. Discovering Offerings on the Marketplace according to a Query specification

Now, that you are authenticated at the marketplace, you can search for relevant parking sensor data to feed into your service.

2.1 Based on an Offering Query created via the Marketplace Web portal

In case you have already created an Offering Query via the Marketplace Web poral, you can simply call the discoverById() method by using the Query ID, as shown here:

List<SubscribableOfferingDescription> offeringDescriptions = 

In return, the Marketplace provides a list of all matching offerings.

2.2. Based on an Offering Query created in program code

Alternatively, you can also create your Offering Query from scratch in your appliation. The query gets constructed using a builder pattern which first, creates the empty OfferingQuery object that is completed with additional query filters, such as a specific search region, a desired accounting type, a maximum price, etc. The marketplace will later retrieve all matching offerings for this query. In this example, the query is quite simple however it can be more complex in other situations.

OfferingQuery query = OfferingQuery.create("DemoParkingQuery")
	.withName("Demo Parking Query")
	.withTimePeriod(TimePeriod.create(new DateTime(1999, 1, 1, 0, 0, 0), new DateTime()))
	.inRegion(BoundingBox.create(Location.create(40.0, 8.0), Location.create(45.0, 12.0)))
	// .inCity("Barcelona")
	.addInputData(new RDFType("schema:longitude"), ValueType.NUMBER)
	.addInputData(new RDFType("schema:latitude"), ValueType.NUMBER)
	.addOutputData(new RDFType("schema:longitude"), ValueType.NUMBER)
	.addOutputData(new RDFType("schema:latitude"), ValueType.NUMBER)
	.addOutputData(new RDFType("datex:parkingSpaceStatus"), ValueType.TEXT)

When creating the Offering Query, you need to provide an ID (here “DemoParkingQuery”) and a name (here “Demo Parking Query”) for it. Also it is important to define a semantic type or category (here “urn:big-iot:ParkingSpaceCategory”) in order for the marketplace to return only relevant types for your consumer application.

NOTE 1: A full list of already defined and supported semantic categories is available here. Via the Marketplace user interface, you can also create new categories during creation of an offering. Those ‘“proposed”’ types can then also be used in your code.

Offerings queries can also use temporal (withTimePeriod()) and spatial (withRegin() or inCity()) filters that ensure that only relevant offerings are discovered. Also the pricing model and a maximum price, as well as the desired license type can be defined. The Consumer Lib offers you Enum classes that you can consult to see, which other licenses or accounting types are available.

Finally, you can also define specific input and output data types that you expect in the offerings.

To execute the query on the marketplace, the Consumer object provides multiple options.
The dedicated method for this is discover, which has different signatures to take different programming preferences into account.

CompletableFuture<List<SubscribableOfferingDescription>> discover(IOfferingQuery query);
CompletableFuture<List<SubscribableOfferingDescription>> discoverById(String queryId);
void discover(IOfferingQuery query, DiscoverResponseHandler onSuccess, DiscoverResponseErrorHandler onFailure);
void discoveryContinuous(IOfferingQuery query, DiscoverResponseHandler onSuccess, DiscoverResponseErrorHandler onFailure);

The first version uses a CompletableFuture as a return type, which is a promise on a list of SubscribableOfferingDescriptions, which is part of the functional programming styles introduced in Java 8. The other two variants are using callback mechanisms.

The following code shows how to discover offerings getting them as a CompletableFuture on the list of OfferingDescriptions:

CompletableFuture<List<SubscribableOfferingDescription>> listFuture =;
List<SubscribableOfferingDescription> offerings =;

The discover call is actually non-blocking. So, you could do something in between, e.g. handing over the CompletableFuture object to your management thread. Or alternatively, you can directly receive the list by calling the get method. This call is blocking and will wait on the list of OfferingDescriptions. The motivation of using CompletableFuture here is, that you can come easily from an asynchronous behavior to a blocking behavior and further you can utilize reactive concepts if you want. For example by calling thenApply as a monad on the CompletableFuture object allows you to apply functions once the list of offering descriptions is received.


As a side note: You can reuse your query object for subsequent queries. Only if you want to change something regarding the query you have to create a new OfferingQuery object.

3. Subscribing to Offerings of interest

Before an offering can be accessed, you have to subscribe to the offering. Subscription is done through the correspondent subscribe method, which creates a an Offering object upon success. As part of the subscription process the consumer lib obtains the requried access token for the respective offering, which is checked by the provider upon access to the offering.

3.1 Based on known Offering ID

If you already know the ID of the offering you want to subscribe to, you can also skip the discovery phase (step 2) and directly subscribe to the offering based on its ID, as follows:

Offering offering = consumer.subscribeByOfferingId("TestOrganization-TestProvider-DemoParkingOffering").get();

3.2 Based on discovered Offerings

Alternatively, if you used the discovery phase (step 2) to find offerings of interest, you receive a list of SubscribableOfferingDescription objects as a result.

You can either select the offerings you want to subscribe by inspecting their properties in your own selection routine or by using the SelectionCriteria class of the BIG IoT lib.

The SelectionCriteria class allows you to define the selection criteria based on your service logic needs, by creating a new SelectionCriteria instance. To create a new selection, you use the OfferingSelector class, which accepts an arbitrary amount of SelectionCriteria objects. In the example below, we discover a list of offerings and apply an OfferingSelector that selects the cheapest offerings. In case there are several cheapest offerings, the selector picks the one with the one with the most permissive license.

SubscribableOfferingDescription offeringDescription =
		    .thenApply( (list) -> OfferingSelector.create()

Once a SubscribableOfferingDescription has been selected, the subscription is done as follows:

Offering offering = offeringDescription.subscribe().get();

4. Accessing Offerings based on a one-time request or in a continuous fashion

Before we describe how to access an offering that was discovered and subscribed to on the marketplace, it makes sense that you look at the different access concepts provided. The IOffering interface provides the following signatures for access:

CompletableFuture<AccessResponse> accessOneTime(AccessParameters parameters);
void accessOneTime(AccessParameters parameters, AccessResponseSuccessHandler onSuccess, 
		   AccessResponseFailureHandler onFailure);   
IAccessFeed accessContinuously(AccessParameters parameters, Duration lifetime, FeedNotificationSuccessHandler onSuccess, 		    FeedNotificationFailureHandler onFailure);

To access offerings, we distinguish between two types: one-time access and continuous access. One-time access means that you execute an access request every time you want to get new data. Continuous access refers to the reception of data as a feed.

In either case, you have to provide an AccessParameters object in the access call. In includes the parameters, which will be passed on to the provider as “input data”. Typically they are needed to filter the “output data” (i.e. the response) or simply to configure the access request.

Here is an example, how to create the AccessParamters object:

AccessParameters accessParameters = AccessParameters.create()
			.addRdfTypeValue(new RDFType("schema:longitude"), 12.3)
			.addRdfTypeValue(new RDFType("schema:latitude"), 42.73);

The semantic types (e.g. “schema:longitude”) you can use here are those defined under the “input data” in the offering description. The value will be assign to the corresponding property name in the access reqeust.

4.1 One-time Access

For one-time access, the Consumer Lib supports again different programming styles. You can either use a CompletableFuture to do reactive programming or a callback function.

Here is an example, how to access the parking offering we retrieved earlier:

CompletableFuture<AccessResponse> response = offering.accessOneTime(accessParameters)
	.thenAccept((r) -> log("One time Offering access: " + r.asJsonNode().size() + " elements received. "));

As you can see, accessing an offering can be that simple. We use the accessOneTime() method and pass the AccessParameters object. Since we use accessOneTime() returning a CompletableFuture, we can apply a function on the result. Here we simply print out the response content to the console. Note that the response object is of the type JsonNode, which already includes the parsed response message and provides functionality for traversing the response.

CompletableFuture<AccessResponse> response = offering.accessOneTime(accessParameters);
List parkingResult3 = response.get().map(AlternativeParkingPojo.class, OutputMapping.create()
	.addNameMapping("geoCoordinates.latitude", "coordinates.latitude")
	.addNameMapping("geoCoordinates.longitude", "coordinates.longitude")
	.addNameMapping("distance", "meters"));

4.2 Continuous Access

However, since we want to show the returned parking data in real time, it would be even nicer if we could access the parking data continuously. Here we describe how this can be done:

Duration feedDuration = Duration.standardHours(1);
Duration feedInterval = Duration.standardSeconds(2);

AccessFeed accessFeed = offering.accessContinuous(accessParameters, 
	(f,r)->log("Incoming feed data: "+ r.asJsonNode().size() + " elements received. "),
	(f,r)->log("Feed operation failed"));

You notice that the procedure is very similar to the accessOneTime(). The accessContinuous() method of the Offering object also requires the accessParameters object, a duration and interval of the access feed, as well as a success and failure handler. This method creates an AccessFeed object, which has its own lifecycle management. The AccessFeed has functionality for stopping (stop()), resuming (resume()) and getting the status of a feed subscription (status()).

Congratulations! You have now successfully discovered and subscribed to your first offering via the marketplace, and accessed the resources on the provider!

5. Offering unsubscribe and Consumer termination

If you want to unsubscribe from an offering, just call the unsubscribe() method on the Offering object. This will also terminate all the access feeds related to the respective offering.


To finally terminate your consumer instance, you call the terminate() method on the Consumer object.


6. Automated mapping to POJO

The following example will show you, how you can access offerings and let the BIG IoT Lib automatically match the output parameters to your POJO.

AccessResponse response = offering.accessOneTime(accessParameters).get();

//Mapping the response automatically to your POJO
List<ParkingResultAnnotated> parkingResult =;

As you can see here, the map() method of the AccessResponse object accepts an annotated POJO class. Based on this, the Lib will map the response (“output data” from the parking provider) to the POJO MyParkingResultAnnotated:

public class MyParkingResultAnnotated {
    public double longitude;

    public double latitude;

    public double distance;

    public String status;	

Alternatively, instead of using an automated mapping approach, you can also program the mapping in your code. To do so, you create an OutputMapping object and pass this to the map() function of the AccessResponse object. The output mapping is created with a builder approach, where you define a mapping between your class variables (e.g. “longitutde”) and the semantic types (e.g. “schema:longitude”). You can see how this works in the next example (note that we use the non-annotated version of the ParkingResult):

AccessResponse response = offering.accessOneTime(accessParameters).get();

List<ParkingResult> parkingResult = response
  .map(MyParkingResultPojo.class, OutputMapping
	.addTypeMapping("schema:longitude", "longitude")
  	.addTypeMapping("schema:latitude", "latitude")
  	.addTypeMapping("datex:distanceFromParkingSpace", "distance")
  	.addTypeMapping("datex:parkingSpaceStatus", "status"));

As you can see here, the addTypeMapping() method is used to add the mapping for each semantic type from the provider’s output data elements to your class variables.

That’s it! You have just learned how to use the BIG IoT Library as a data provider as well as a data consumer.