IJRET: International Journal of Research in Engineering and Technology eISSN: 2319-1163 | pISSN: 2321-7308 _______________________________________________________________________________________ Volume: 05 Issue: 05 | May-2016, Available @ http://ijret.esatjournals.org 43 IMPLEMENTATION OF ALARMS ON HOME DEVICE MANAGER Sampriti Sarkar 1 , R. S. Prasanna Kumar 2 1 MTech, Department of Computer Science, PESCE, Mandya, India 2 Assistant Professor, Department of Computer Science, PESCE, Mandya, India Abstract Alarms are generally being used these days for everything starting from morning wake-up alarms to sleep timers in television. Alarms have become the day to day life practice for many things. Here, alarms are an additional functionality added for an IT solution called as “Home Device Manager”, which actually monitors the TR-069 devices and manages the devices remotely. Alarms are being implemented on Home Device Manager as an added functionality so that any service provider using this solution can easily monitor whether the device which malfunctioned is because of any of the most commonly occurring disabilities on the device. Keywords: Alarms, Home Device Manager, IT Solution For Service Providers --------------------------------------------------------------------***---------------------------------------------------------------------- I. INTRODUCTION Home Device Manager (HDM): HDM remotely manages customer premises equipment (CPE) which includes residential gateways, modems, IP set top boxes. It provides all the CPE from multiple vendors who support Broadband Forum’s TR-069 management support. HDM helps the service providers to verify if the device is working all right or any issues like gateway is switched on but doesn’t respond to the connection requests. II. ALARMS Usually checking few of the most common device cases which lead to malfunctioning of the devices, 6 types of alarms are introduced. These alarms can help the customer care to notice whether any of those most commonly occurring cases have happened on the devices. Alarms getting raised on the device will help the customer care to find out if the device which is being complained about is not working because of some specific criteria’s not being specified. A. Types The different types of alarms are:  Frequent Inform event  Device action failure  Connection Request failure  Value change alarm  Generic alarm  Missing gateway III. ALARMS EXPLANATION A. Frequent Inform event alarm Beginning with Frequent informs event alarms, these alarms are based on the events being performed in between the CPEs and the ACS. Sometimes if the device sends too many events for ex: inform event within the threshold time limit it creates congestion on HDM server. Thus an alarm will get raised on the device management console. As shown in the following image, let’s take an example of Frequent inform event alarm. We set the threshold of 3 inform in a day by the CPE to ACS, so as the fig. 1 shows Fig.1. Frequent Inform event Alarm here the device first initiates an connection to the ACS server and sends a periodic inform with the details about the device, so that the ACS server knows the details about the device which is trying to contact the server. Eventually if the device is not functioning as expected, thus it sends more than the required informs to be sent in a day and this may cause the HDM server to cause congestion. Thus, when the malfunctioned device sends the 4 th inform to the ACS server, in the HDM device management console the alarm gets raised, thus informing the telecom provider about the device.