TITLE: PROGRAMMABLE OBJECT INTERFACE

ABSTRACT:
IoT is rapidly growing area in which the communication between machines happens. Internet of things
is nothing but the devices which are embedded with some Sensors, Protocols, Application software
sometimes a module which are connected through internet sharing resources, transferring data,
performing some tasks. Extending the current internet with all devices and their virtual representation
has been a growing trend. This will create a lots of potential applications, products and services in
many aspects, such as smart home, smart health care, smart cities, automotive, smart transport and
logistics For many years common system has been limited designed for specific purpose with limited
flexibility this means only one system is running, later distributed systems takes over through
middleware concepts and thus it can be changed dynamically and flexible by adding n-tier to the
existing but only for a specified event. The current initiative on the introduction of IoT demands
applications, products which can capture, communicate and store, access and share data from the
physical objects, here programming takes a lead role and hence it is also called as Programmable
Object Interface (POI). This will create new opportunities in the big range of domains and also
personalized end-user requirements. A better programming is helpful in making IoT a problem less
technology which may leads to another evolution called Programmable Internet. This paper mainly
focus on features of programming with the help of architectures and machine learning techniques
along with the data structures needed to be implement for certain application.
INTRODUCTION:
OBJECTIVE: To define a modified Architecture model for internet of things from a
programming perspective.
For a specified scenario like health-care, transportation or agriculture there are several tasks to be
performed by a sensor which is also used in another application but the difference is the program and
the algorithm. In health care as well as the agriculture the water quantity check sensor is active, but
In health care we use it to measure the quantity of the water in the body whereas in the agriculture
we use it for measuring water quantity in the soil, implementation is the same for any but it is the
code which make a difference.
The layered organization[1] of IoT protocols over an architecture will brings the differences, but its all
the same when comes to the way of implementation in which there should be an INFRASTRUCTRE[2]
to provide a platform or a means of communication which maybe IP, UDP, TCP/IP,. depending on
the type of the application. Providing an infrastructure doesnt give an identification and hence there
should be a IDENTIFICATION[3] layer which deals with IPv6,URIs,. if the infrastructure is made up
from IPv6 specifically then there is no need of an identification layer. In machine-to-machine
interaction, 2 machines with identities are required but not sufficient to make communication, and
hence the should a DISCOVERY[4] layer in which DNS, Physical web, are required. Until now we are
having machines(sensors) with identity and discovery under an infrastructure, communication is
nothing but sending and receiving of data, for sending and receiving of data they should be able to
manage the connection between them which is done by DATA CONTROL[5] layer which may be any
of MQTT, CoAP, AMQP, After successful connection establishment there has to be someone who
actually takes the message from one machine and delivers to other machine, which is
COMMUNICATION/TRANSPORT[6] layer which is also known as transportation layer it may be
Ethernet, IEEE 802.15.4, NFC, Bluetooth, Zigbee, the layers mentioned above are common to each
and every IoT application but for some peculiar applications like automated Library system, ther has

to be something that actually understands what a user wants which is nothing but SEMANTIC[7] layer
that understands the meaning of the word through Ontologies, some of them like XML, RDFI, Semantic
Sensor Net Ontology, which can also help to understand more languages other than English. When
many sensors/machines are being handled a single component which is most common for Home
automation system, we need to bind all the functionalities into one as a framework which comes
under MULTI-LAYER FRAMEWORK[8] it may be another architecture or a simple function which means
architecture of architectures a MULTI-LEVEL ARCHITECTURE and of course we definitely need a
security layer too in where encryption, decryption will be done for every message.
Based on the theme of the application the layers may different as per the general view, but a modified
architecture can be applied to any of the applications and there is no need to change the architecture
for application to application therefore, it is a interface for objects to program which is nothing but
Programmable Object Interface.
LITERATURE SURVEY:

Machine-to-Machine (M2M) communications en-ables networked devices to exchange

information among each other as well as with business application servers and there-fore
creates what is known as the Internet-of-Things (IoT).
The protocol selection problem is closely tied to the implementation of the protocol and the
components that support the protocol are often essential in the final design.
Communications in the Internet of Things (IoT) is based on the Internet TCP/UDP protocols
and the associated Internet protocols for setup.
Once you've chosen the hardware platform, though, you still must develop the application
software, and that's where more (and often, more difficult) decisions must be made.

REFERENCES:
1.
2.
3.
4.
5.
6.
7.
8.

http://www.postscapes.com/internet-of-things-protocols/
http://webofthings.org/wot/2010/pdfs/144.pdf
http://www.cse.wustl.edu/~jain/cse570-13/ftp/iot_name/index.html
http://ieeexplore.ieee.org/document/7423412/
http://electronicdesign.com/embedded/mqtt-will-enable-internet-things
http://dunkels.com/adam/ko11beyond.pdf
http://www.dataversity.net/34702/
https://www.spirent.com/Products/DevTools/IoT-Client-Device-Framework