A Practical X10 Protocol Implementation Over A Cellular Network Using SMS
A Practical X10 Protocol Implementation Over A Cellular Network Using SMS
701 E. Chocolate Avenue, Suite 200, Hershey PA 17033-1240, USA Tel: 717/533-8845; Fax 717/533-8661; URL-http://www.idea-group.com
ITB12804
857
This paper appears in the book, Emerging Trends and Challenges in Information Technology Management, Volume 1 and Volume 2 edited by Mehdi Khosrow-Pour 2006, Idea Group Inc.
ABSTRACT
This document presents the results of an X10 protocol implementation using the Short Messaging System (SMS) and shows how can they work together in order to provide a home system control for remote controlling electric home devices. The protocol X10 and the architecture of a SMS system are discussed yielding to a practical implementation for a home system control using the Nokia SDK Beta 3.0 development kit. Results gathered from the experiment are shown and conclusions are delivered emphasizing the advantages and drawbacks from the proposed implementation. Further, it is shown that the application runs independently of the cellular technology used on the network.
Finally, section VI considers the advantages and drawbacks of X10, showing how it may affect our home control system, and the way that future developments can join WAP technology with X10 letting the home having on-line access for control or the interaction of a teleworker with his intranet.
II.
I.
INTRODUCTION
Multimedia applications are becoming more popular. However, there are still applications that can be performed by using low data rate systems. The monophasic power supply that feeds the breaker box is distributed among the different supplies that, at the same time, feed the light switches, current supplies and other devices. Therefore, the structured home cabling that physically interconnect the different electrical devices like lights, lamps, electro domestics, becomes a lesser home network. Making use of this network, it is possible to send control signals in order to obtain some control level over the home devices. On the market, there already are modules that allow the control of electrical devices through the electric cabling and even more, to make use of a computer for controlling and supervising. However, there is still no a system that integrates an additional control component: the text messages through a cellular phone without taking care of the technology employed by the cellular network (and operator using a specific technology like CDMA or GSM). The overall objective is to deploy a system that will allow the user to interact with its electrical home devices allowing to remotely turning on or off a specific device using any cellular phone that supports Short Messaging System (SMS). In order to achieve this goal, a software interface will be created and the Nokia SDK Beta 3.0 development kit will be employed. In section II We start discussing how the short text message travels from the mobile that generates the message until the destination and which are the elements involved in between. Then, in section III, we go through the theory of transmission of X10 and how the elements of a home control system based on CM17A or CM11A can work together. In section IV, we continue explaining the necessary elements for connecting the local mobile to the personal computer: DLR-3P cable and the Nokia Connection Manager Software. In section V, in order to integrate the functionality of a mobile cellular phone and SMS, we use de Software Development Kit Beta 3.0 de Nokia that allow us developing our SMSControl application putting these two technologies together.
A. Short Messaging System (SMS). This is a wireless service globally accepted that allows the send and reception of alphanumeric messages between 2 users of a cellular mobile network. Further, It is also possible to send emails, paging, et cetera. Typically, this message can not be greater than 160 alphanumeric characters excluding images and any sort of graphics. The SMS messages are supported by the GSM, TDMA, and CDMA networks. Since its acceptance into the GSM standard, it has also been included in other standards like the Nordic Mobile Telephone (NMT), Code Division Multiple Access (CDMA) and Personal Digital Cellular (PCD), the latter being used in Japan. B. SMS Network Architecture Basically, SMS architecture is conformed by the following elements: ESME (External Short Messaging Entities) SMSC (Short Message System Center) STP (Signal Transfer Point) HLR (Home Locator Register) VLR (Visitor Locator Register) MSC (Mobile Switching Center) Air Interface BS (Base Stations)
Copyright 2006, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of Idea Group Inc. is prohibited.
IV.
Figure 3. Complementary Bit Transmisin
A. PC and the Nokia Software Development Kit The mobile interconnection occurs on 2 levels: Physic and Logic. The physical interconnection is performed through the DLR-3P Cable of Nokia, which is a proprietary cable that allows connecting some Nokia models to a computer. The communication between the mobile and the PC is based on the proprietary protocol of Nokia that allows the communication in full-duplex mode. However, the Nokia Connection Manager (NCM) has to be used in order to achieve a logic communication between two devices. This NCM allows the computer to send the FBUS codes. B. The Nokia Software Development Kit (SDK) Beta 3.0 This is a set of tools that allows integrating the functions of the mobile device and the interaction with the computer with the program implementation developed in different languages. The SDK consists of a set of libraries, each having specific tasks related to the functionality of the mobile. All the libraries are implemented like Component Object Libraries) COM libraries, being this the name that Microsoft provides to its standard for the integration between the software components. A client application exploits these libraries through objects, also called type libraries in some contexts. A library of objects can be considered like a binary description of the library of components. Many environments can support these libraries, such as Visual Basic, Visual C++, Delphi, Visual J++, among others. Each library in the Nokia SDK contains one or more functional entities called components. These software components can be reused and present their functionality through a set of interfaces well-defined. A client application creates an instance of the component, configure a reference to the desired interface and have access to the methods through this reference. An interface contains a set of features, methods and functions related to a specific functionality, grouped under only one denomination. The interfaces are divided into 2 categories, according to the place where the methods are requested. The methods of the interfaces at the input are implemented in the object components and receive the calls from the external clients. The object performs the service requested and returns the result to the client. Most of the interfaces into these libraries are input interfaces, which are requested by the client application. The methods or events of the output interfaces are implemented on the sink of the client and they receive the call from the object. The object defines the interface that will be used and the client deploys it, thus, the output interfaces let the object reply to the client. The output interfaces are often used to notify the client when something important is happening or to inform the customer when an asynchronous operation has been completed. The output interfaces are also called connection points, event interfaces, notification interfaces or source interfaces. In the development of this Project, the NokiaCLMessaging library was used (see Annex B.1), using extensively the IShortMessageItem interface (see Annex B.2). Through these methods it is possible to read the received messages by the mobile phone and to send messages by itself.
Copyright 2006, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of Idea Group Inc. is prohibited.
859
(a)
(b)
by X10 adjacent systems configured with the same home code. Finally, due to the attenuation of X10 signals when passing through the electrical home devices connected to the closest power supply lines where are connected the transceivers as well as the receivers. The sources of these electric home devices do not mostly filter the signals greater than 60 Hz.
I.
CONCLUSIONS
They do not need any additional cabling in order to deploy the network of devices. Depending upon the sort of the system controller, the X10 systems may not be complex to deploy because they do not require that an operator holds a big electronics experience and knowledge. Instead, there are plug-and-play devices that allow the immediate installation of a control system, The X10 devices, transmitters as well as receivers and transceivers are on the market, thus, they are easy to be acquired in electronic stores or markets. X10 is a relatively mature protocol, being already deployed since a few years ago. It is very easy to modify the X10 modules due to the easy development of its software routines. This makes X10 attractive and flexible for control solutions, as this work can demonstrate that.
However, X10 also presents some drawbacks that can be summarized as follows: X10 is not scalable. It was not designed for a complex system such as data transmission on the end-devices. Further, X10 was not thought for industries branches or hostile environments, where noise sources exist. In this sense, X10 is not a direct competitor of PLC based-solutions, which are focus on complex and robust designs. X10 devices, as it was discussed and analyzed are sensitive to an erroneous behavior either when the X10 signal is transmitted on noisy environments or when the transmitters are close to any power supply that is not able to filter signals in the order of 120 KHz, as it is the case of some old televisions.
Our recommendation is that the developments of new control components for X10 based-systems will be using WAP and Cellular supporting this technology. In a very short period of time, the written messages will be suitable for very simple tasks. Instead, a more stable bidirectional control will be achieved using TCP/IP through WAP, such that the computer, that is the X10 system controller, can be on-line by means of a public IP address (generated by its ISP) and can be accessed in realtime including more complex tasks (bidirectional) like the record of events during the working period, triggered alarms record and even for industry applications, things like access to databases by an remote user, so forth.
Copyright 2006, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of Idea Group Inc. is prohibited.
ANNEX B
B.1 NokiaCLMessaging Library Components
[6]
[7] [8]
ANNEX A
A.1 CM17A Configuration (Firecracker) and CM11A Configuration Figure A.1 and A.2 shows these 2 alternatives configurations of the home control system. B.2 IShortMessageItem Interface Methods
ANNEX C
C.1 Templates FrmAddUser: This receives all the users of the system. These will be identified using the number of the cellular phone, that is, a list with all the numbers that will use the system has to be done. FrmAddDevice: This one allows adding the devices to be controlled. These are placed in a list with the describing features like the name, the home code and the device code, that is, its ID. FrmConfigSMSControl: This is the core template of the application because the most important tasks are planned here, such as: Serial Port to be used. Total Activation of the system Monitor of the written messages sent by the remote mobile Reading of these messages from the memory of the local mobile Validation of the telephone number from which the message is sent, comparing the elements from the users list on the FrmAddUser. Validation of the received command in the message sent by the remote mobile, comparing with the elements from the device list on the FrmAddDevice Use of the protocol to encode the control word. Send bit per bit of the X10 command according to the CM17A or CM11A alternative mode.
Copyright 2006, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of Idea Group Inc. is prohibited.
861
FrmConfigAlarm: This is an additional feature that is present only in the SMSControl Application, based on the CM11A interface. This template allows the user scheduling tasks of switching on and off the X10 devices, besides the fact of sending a state report to the devices and enable the emergency calls and DTMF digits.
Copyright 2006, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of Idea Group Inc. is prohibited.
Related Content
Managing IS Security and Privacy
Vasilios Katos (2009). Encyclopedia of Information Science and Technology, Second Edition (pp. 24972503).
www.irma-international.org/article/lag-effect-investment-firm-performance/1285/