Back
 CN  Vol.6 No.2 , May 2014
A Generic Platform for Sharing Functionalities among Devices
Abstract: With so many potentially interconnected electronic devices in today’s homes, manufacturers have to think of theirs as only one of the components involved in a general user experience, and not as an isolated device. Users are likely to be using several devices at the same time, either actively through immediate interaction, or passively by expecting devices to give them notifications when necessary, for example. Thus, having cross-devices functionalities is often necessary for a product to be really adapted to its usage situation. Moreover, just as we install software on computers, smartphones and tablets for additional functionalities to use their own hardware, it would be logical to install cross-devices software to use the combined hardware of several home devices for a better user experience. However, even though a number of technologies can be used to transmit data or commands between devices, UPnP being a widespread example, it is not possible to access the behavior of remote devices and add functionalities to them this way. Thus, when manufacturers design their products, there is no way for them to make full use of the other appliances at the user’s home without developing and deploying specific software on each of them. In order to address this issue, this paper discusses a platform for generic development and on-the-fly deployment of applications on home devices. This system aims at letting device vendors deploy innovative features across devices in a home network, without requiring prior knowledge or control over devices already present in the user’s environment. For this platform to be fit for consumer devices, it is designed to be cost-effective, use recent and widespread technologies, and be fast to implement and work with.
Cite this paper: Van, R. , Shimada, H. and Sato, K. (2014) A Generic Platform for Sharing Functionalities among Devices. Communications and Network, 6, 86-96. doi: 10.4236/cn.2014.62011.
References

[1]   IETF Network Working Group (2013) Rfc2818:Http over tls.
https://tools.ietf.org/html/rfc2818

[2]   UPnP Forum (2013) Device Protection: 1 Service.
http://upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service.pdf

[3]   W3CWebRTC Working Group (2013) Webrtc 1.0: Real-Time Communication between Browsers.
http://www.w3.org/TR/2012/WD-webrtc-20120821/

[4]   Android Open Source Project (2014) Android API Reference, Package Android. webkit.WebView
http://developer.android.com/reference/android/webkit/WebView.html

[5]   BlackBerry (2014) BlackBerry Java Application Development, Class Browser net.rim.blackberry.api.browser.Browser
http://www.blackberry.com/developers/docs/6.0.0api/
net/rim/blackberry/api/browser/Browser.html


[6]   Oracle (2014) Java Platform JavaFX, Class JSObject, java.lang.Object
http://docs.oracle.com/javafx/2/api/netscape/javascript/JSObject.html

[7]   UPnP Forum, (2013) Upnp Device Architecture 1.1.
http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf

[8]   Apache Software Foundation (2013) Apache Jini Specificationsv2.1.2.
http://river.apache.org/doc/spec-index.html

[9]   Kadowaki, K., Koita, T. and Sato, K. (2008) Design and Implementation of Adaptive Jini System to Support Undefined Services. Master’s thesis, Department of Information Systems Design, Doshisha University,

[10]   Donsez, D. (2007) On-Demand Component Deployment in the UPnP Device Architecture. Consumer Communications andNetworking Conference, Las Vegas, 920-924.

 
 
Top