📘 Resource Overview & Documentation Details

You are viewing the technical directory listing for Sensor Data Marketplace: Sharing IoT Data and Device Access. This engineering resource is curated under our Internet of Data division to support automation specialists, control systems engineers, and manufacturing technicians looking for verified reference materials.

🔍 Contextual Abstract & Technical Scope

Share Summary:LinkedInEmail

Industrial and infrastructure applications often depend on data collected beyond the boundaries of a single plant or organization. A sensor data marketplace offers one way to connect device owners who can provide measurements with users who need them. The Sensmart prototype illustrates how such an arrangement can support both access to sensor readings and, where appropriate, temporary control of a device.

The model is relevant to automation teams considering external sensing services, distributed monitoring, or new ways to make device data available. It also highlights a practical design point: a marketplace needs more than a catalog. It must manage device availability, mediate communication, and account for the different capabilities and constraints of connected equipment.

What a sensor data marketplace does

In a Sensing-as-a-Service model, a supplier makes sensor data or device access available to consumers through an intermediary platform. A consumer might request an existing measurement, readings over a defined period, or access to a controllable device for a time window. The owner can set a price for an individual reading or a collection of measurements.

The concept can apply to varied sensing needs. For example, a network of environmental sensors could provide temperature, humidity, or air pollution readings to organizations that use those measurements. A richer device, such as a camera or robot, may offer a data stream or a control function rather than only periodic readings.

Sensmart was designed to demonstrate this exchange. Its prototype included a marketplace for customers, devices, products, and inventory, alongside a broker that mediated requests between the platform and devices. Although the marketplace model describes exchanges for currency, currency transactions were not implemented in the prototype.

Architecture: devices, broker, and marketplace

Sensmart separates its system into three modules, each with a defined interface:

  • Device module: Represents the physical sensing equipment and its connection to the IoT infrastructure. Gateways can help bridge differences in device protocols, radio technologies, or message formats.
  • Broker module: Receives marketplace requests and manages the communication path between a device and a buyer or seller. Its components differ depending on the type of sensor or service.
  • Marketplace module: Supports customers, searchable device catalogs, and an inventory that records whether products or device access are available.

This separation helps prevent consumers from connecting directly to a supplier’s device. Instead, the broker applies the details of the request—such as the relevant sensor, buyer, and time interval—and relays the permitted data or control interaction. The marketplace can therefore remain the point where a service is discovered and requested, while the broker handles device-facing communication.

Supporting constrained sensors and richer devices

Simple sensors and message delivery

Many sensors have limited processing capability and energy resources. Their communication method must fit those constraints. Sensmart’s simple-device implementation used AWS IoT and MQTT, a publish/subscribe protocol in which devices publish messages to topics and subscribers receive messages from those topics.

A virtual device representation can be associated with a physical sensor or used to represent a buyer. In the prototype’s data flow, the sensor publishes to a seller topic, while a handler forwards authorized messages to a buyer topic. This intermediary arrangement means the buyer receives data without being given direct access to the sensor’s topic.

The system distinguished between single requests and longer subscriptions. A single transaction could request a measurement or send a control message. For a time-bounded subscription, a handler listened for sensor messages and forwarded them until the requested period ended. This approach makes the service window an explicit part of the transaction.

Rich devices and controlled access

Some devices do more than measure and publish. A controllable camera, for example, may provide a video stream and accept movement commands. Sensmart treated video and control as separate functions, helping ensure that a customer with viewing access alone could not use the video connection to control the camera.

For this richer-device scenario, a video broker and handler managed the customer connection, stream, and control requests. The handler authenticated requests and forwarded valid commands to the device’s control module. Access ended when the purchased time window expired. The broader lesson for system integrators is that device-specific behavior may require different broker and handler implementations, even when they fit within the same overall marketplace architecture.

What the prototype evaluation showed

The evaluation covered three operations: scheduled single measurements, longer data subscriptions, and video with camera control. In the single-measurement tests, 299 of 300 scheduled measurements reached the client. The reported mean difference between scheduled and received times was 1.35 seconds across the results table.

For long subscriptions, five buyers received readings from one sensor during a 45-minute period. The reported mean difference between measurement and reception was 0.51 seconds, with the paper noting that a one-second clock offset would affect the interpretation. In the camera test, the mean time for a control request and response was approximately 0.20 seconds. These figures describe the tested prototype and setup, not a general performance guarantee for other devices, networks, or deployments.

The tests also showed why measurement timing and system processing time should be considered separately. The marketplace and broker accounted for only part of the overall workflow; communication with the IoT platform and device could also influence delivery. For some applications, such as readings collected infrequently and uploaded later through a gateway, immediate delivery may not be the primary requirement.

Practical considerations for automation teams

A marketplace approach may be useful where organizations need access to distributed sensing assets, but deployment planning should address several fundamentals:

  • Define what is being offered: stored readings, future measurements, a continuous stream, or device control.
  • Represent device availability so buyers do not request an offline or already-committed resource.
  • Use a broker to enforce the requested scope and time window rather than exposing devices directly.
  • Account for constrained devices, protocol differences, gateways, and payload translation.
  • Evaluate data latency in context, including clock synchronization and the application’s actual timing needs.

The prototype’s authors also identified areas for further development, including broader device support, database integration, payment transactions, and stronger attention to security and privacy. These are important considerations when moving from an architectural demonstration toward an operational service, especially where device control or potentially sensitive data is involved.

Conclusion

A sensor data marketplace can provide a structured way to connect device owners with consumers of measurements and device services. Sensmart demonstrates how a marketplace, broker, and device layer can work together across simple MQTT-based sensors and richer controllable equipment. For industrial automation teams, the practical takeaway is to treat discovery, availability, access control, communication, and timing as connected design requirements—not as details that can be left to the sensor alone.

Access Official Technical PDF