Provide IoT Offerings

Assuming, you have developed an IoT platform for parking data. Now you want to make this data public. How do you connect your platform to the BIG IoT Marketplace in order to provide this data to other developers so they can use your data in their applications?

Using the BIG IoT Provider Lib, you can manage your data on the BIG IoT Marketplace in terms of offerings. The Provider Lib offers the following main functionalities:

  1. Creation of a BIG IoT Provider and Authentication on the Marketplace
  2. Definition of an Offering Description
    • Based on a pre-defined one via the Marketplace Web portal
    • Based on program code
  3. Creation of Endpoints for the Offering Description
  4. Registration of the Offering Description with its Endpoint

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 Provider and Authentication on the Marketplace

Before you can register your parking sensor data on the marketplace as an offering, 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 Provider instance (click on “MyProviders” and then “+Provider”). After you created a new Provider, you can copy the unique Provider ID and Secret into your program in order to associate your Provider application with the newly created Provider instance.

String PROVIDER_ID     	= "TestOrganization-TestProvider";
String PROVIDER_SECRET 	= "***************************";

ProviderSpark provider = ProviderSpark.create(PROVIDER_ID, MARKETPLACE_URL, "localhost", 9876)

With this in place, you can now create a new Provider instance in your application by providing the Provider ID and Marketplace URL. In this example, we use the ProviderSpark class, as this offers an easy way to create a provider with an embedded Spark Webserver. The Webserver is started on the given DNS name or IP address and port, in this case “localhost” and port 9876. However, you can also use the standard Provider class, and connect it to an existing Webserver (Tomcat, Jetty, etc.).

Once you have created a provider, you also need to authenticate this on the marketplace. For this, you need to provide your Provider Secret. This provider object will be used for all subsequent interactions with the marketplace.

2. Definition of an Offering Description

Now, that you have created a Porvider instance and authenticated it on the Marketplace, you can create an offering description for your parking data.

2.1 Based on a pre-defined one via the Marketplace Web portal

In case you have already created an Offering Description via the Marketplace Web poral, you can simply create a local instance in your code with the following call:

RegistrableOfferingDescription offeringDescription = 
		// optional modify the offering description in your code, e.g. 

If you want to alter that offering description in your code, you do this as illustrated above. With calls like withPrice(), or withLicenseType(), inRegion(), withTimePeriod(), etc. you can alter the offering decription according to your needs.

2.2. Based on program code

Similarly to the above, you can also create your offering description from scratch in your appliation. For example:

RegistrableOfferingDescription offeringDescription = 
		.withName("Demo Parking Offering")
		.withTimePeriod(new DateTime(2017, 1, 1, 0, 0, 0), new DateTime())
		.inRegion(BoundingBox.create(Location.create(42.1, 9.0), Location.create(43.2, 10.0)))
		// .inCity("Barcelona")
		.addInputData("longitude", new RDFType("schema:longitude"), ValueType.NUMBER)
		.addInputData("latitude", new RDFType("schema:latitude"), ValueType.NUMBER)
		.addInputData("radius", new RDFType("schema:geoRadius"), ValueType.NUMBER)
		.addOutputData("lon", new RDFType("schema:longitude"), ValueType.NUMBER)
		.addOutputData("lat", new RDFType("schema:latitude"), ValueType.NUMBER)
		.addOutputData("status", new RDFType("datex:parkingSpaceStatus"), ValueType.TEXT)

The OfferingDescription class provides a builder method that lets you easily create a new offering description. For your offering to be visible on the marketplace, you have to provide an ID (here "DemoParkingOffering") and a name (here "Demo Parking Offering")for it. Also it is important to define a semantic type or category (here "urn:big-iot:ParkingSpaceCategory") so that consumers can find it if they are interested in these type of offerings.

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.

NOTE 2: Using the right semantic catgory for your offering is very important for consumers to find it. So, try to use existing and well established categories whenever there is a good fit. If not, propose a new category that is meaningful.

Additionally, you can define input parameters that can be set by your service’s consumers when accessing your platform (see addInputData()). Here, we provide an example how to add a circle based filter (define by a location - i.e. a longitude and latitude of type "schema:longitude" and "schema:latitude" respectively - and radius of type "schema:geoRadius") as input elements to your offering.

You also have to provide information what your Offering will provide. This is specified my means of the addOutputData() method. In our example, this are the parking space coordinates and the parking space status. The consumer of your offering will have the possibility to query for data within a specific area. He will obtain the data in form of a JSON Array, where each element consists of one parking space, consisting of at least a property with the name "lon" (of type "schema:longitude"), "lat" (of type "schema:latitude") and "status" (of type "datex:parkingSpaceStatus").

Both input and output elements use the RDFType class in order to semantically annotate your data.

NOTE 3: New semantic types for input and output data can be directly created via the code. Just use the keyword ‘“proposed”’ in front of your new type (e.g. ‘“proposed:parkingSpaceType”’).

NOTE 4: Using well estabished semantic types your input and output data is very important for consumers to find the relevant offerings and to process the data correctly. Try to use existing and well established types whenever possible. If not, propose a new type that is meaningful.

Providing a region, a price, a license type and time period (optionally) completes the offering description.

3. Creation of Endpoint for the Offering Description

In the next step, you have to create the endpoint, via which your offering is accessible by consumers.

Option 1: In case you use the ProviderSpark class as provider, which includes the embedded Spark Webserver, you can create the endpoint by providing an access request handler as follows:

Endpoints endpoints = Endpoints.create(offeringDescription)

This access request handler will be called upon each access request by a consumer. In that callback function, you need to provide the code that processes the input data and prepares the output data for that request (see below for further details).

Note 5: Upon an access request from a consumer, the ProviderSpark lib will first validate the access token, which the consumer has obtained from the Marketplace upon successful subscription to the offering, and then call the access request handler that was specified by you.

Option 2: In case you use the Provider class as provider, you can create the endpoint by providing the external endpoint URI of the server that handles BIG IoT consumer access requests as follows:

Endpoints endpoints = Endpoints.create(offeringDescription)

Note 6: The server providing this external endpoint must process access request from consumers in a BIG IoT conform manner and in accordance to the offering description provided.

4. Registration of the Offering Description with its Endpoint

Now that you created the offering description and endpoint, you can register it on the marketplace so that other developers can find it via the Web portal and/or consumer applications can discover your offering at run-time.

RegisteredOffering offering = provider.register(offeringDescription, endpoints);

5. Implementing of Access Request Handler (only for ProviderSpark)

As indicated above (Section 3, Option 1), the ProviderSpark users will also have to implement an access request handler, which will be called by the provider lib each time an authorized access request is received on the embedded Spark Webserver.

We show here a simple example of how such a callback function implementation could look like:

private static AccessRequestHandler accessCallback = new AccessRequestHandler() {
        public BigIotHttpResponse processRequestHandler(OfferingDescription offeringDescription,
                Map<String, Object> inputData, String subscriptionId, String consumerInfo) {
            double longitude = 41.0;
            if (inputData.containsKey("longitude"))
                longitude = Double.parseDouble((String) inputData.get("longitude"));

            double latitude = 9.0;
            if (inputData.containsKey("latitude"))
                latitude = Double.parseDouble((String) inputData.get("latitude"));

            Random r = new Random();
            JSONArray jsonArray = new JSONArray();
            int n = Math.round(r.nextFloat() * 10 + 10);
            for (int i = 0; i < n; i++) {
                JSONObject jsonObject = new JSONObject().put("lat", latitude + r.nextFloat() * 0.01)
                        .put("lon", longitude + r.nextFloat() * 0.01)
                        .put("status", r.nextBoolean() ? "available" : "occupied");

            return BigIotHttpResponse.okay().withBody(jsonArray);

The AccessRequestHandler class is an abstract class that requires you to override the processRequestHandler() method. This method receives the OfferingDescription object that we created earlier and the “input data” map which contains the input filters that the consumer has specified during his access request in form of a map.
If any of the possible filters have been used, we pass them to a service function which, in this tutorial, just simulates parking data. Usually, here you would call your database backend, an internal service, or a device to retrieve real IoT data that you want to offer.

The AccessRequestHandler is implemented as a functional interface. If you prefer, you can also provide the application logic in the Lambda notation.

Congratulations! You have now registered your first offering on the BIG IoT Marketplace.

6. Offering deactivation and Provider termination

If you want to remove your offering from the marketplace, just call the deactivate() method on the offering.


To finally terminate your provider instance, you call the terminate()method on the provider.