X

Hinkmond Wong's Weblog

Easy IoT Sensor On-Boarding Using Jini Auto-Discovery and Java SE Embedded (Part 4)

Guest Author


Now that we know that we'll be using a Parallax USB RFID Reader as an IoT sensor for our Jini Auto-Discovery, we can do a quick refresher of how Jini Auto-Discovery works.

In the diagram to the right we see that, multiple IoT devices on the right side connect the Jini network (such as via Wi-Fi, Bluetooth, or in this case USB), where a Java VM is listening. Once that IoT device shows up on the Jini network, it will need a Jini proxy running in a Jini client application to "proxy" the IoT device as a Jini "service provider" (in other words, an IoT sensor, actuator, or device will perform an action for a Jini client, such as take a measurement/reading, move a servo motor, etc.) via a Jini "proxy". This is how an IoT network of devices becomes more automated and easier to integrate, with everything talking the Java programming language to each other using Java objects.

And, this gives us the key to how the RFID reader will be auto-discovered by our Jini network, so that we just plug it in, and it works (with any other IoT app, network or device)!

So, Jini technology allows for disparate IoT devices and networks (such as a Fitbit wearable, Apple HealthKit heart monitor, Google Nest thermostat, WeMo light switch, or any other IoT device) interact with each other, with apps, and with the cloud.

Next, we'll take a closer look at the how the Jini Look-Up Service running on the Java VM is the integral part of this picture...

Full series of steps:


Easy IoT Sensor On-Boarding Using Jini Auto-Discovery and Java SE Embedded (Part 1)


Easy IoT Sensor On-Boarding Using Jini Auto-Discovery and Java SE Embedded (Part 2)


Easy IoT Sensor On-Boarding Using Jini Auto-Discovery and Java SE Embedded (Part 3)


Easy IoT Sensor On-Boarding Using Jini Auto-Discovery and Java SE Embedded (Part 4)



<<< Previous
  | Next >>>



Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.