CLIAMS:We Claim:

1. A method of automatically updating a firmware and configuration files of a device manager, said method comprising:
receiving, by a processor of a firmware and configuration file management system (FCMS), one or more inputs associated with configuration data of one or more devices communicatively coupled with the device manager;
generating, by the processor, a new configuration file and a new firmware associated with the device manager, wherein the configuration file comprises a unique configuration file ID and the new firmware comprises at least one Modbus library and a unique firmware ID;
receiving periodically, by the processor, one or more requests from the device manager to update existing firmware and configuration file of the device manager; and
updating, by the processor, the device manager with the new firmware and new configuration file upon receiving the one or more requests.
2. The method as claimed in claim 1, upon receiving periodically the one or more requests from the device manager, the method comprising the steps of:
receiving, by the processor, a firmware ID and a configuration file ID of the existing firmware and configuration file of the device manager respectively;
comparing, by the processor, the firmware ID of the new firmware with the received firmware ID, and determining that the existing firmware is to be updated if the firmware ID of the new firmware is greater than the received firmware ID; and
comparing, by the processor, the configuration file ID of the new configuration file with the received configuration file ID, and determining that existing configuration file is to be updated if the configuration file ID of the new configuration file is greater than the received configuration file ID.
3. The method as claimed in claim 1, upon receiving periodically the one or more requests from the device manager, the method comprising the steps of:
receiving, by the device manager, the firmware ID and the configuration file ID of the new firmware and configuration file of the FCMS;
comparing, by the device manager, the firmware ID of the existing firmware with the received firmware ID, and determining that the existing firmware is to be updated if the received firmware ID is greater than the firmware ID of the existing firmware; and
comparing, by the device manager, the configuration file ID of the existing configuration file with the received configuration file ID, and determining that existing configuration file is to be updated if the received configuration file ID is greater than the configuration file ID of the existing configuration file.
4. The method as claimed in claim 1, further comprising:
receiving a request for registration of one or more user devices;
creating one or more user device profiles corresponding to the one or more user devices, wherein the one or more user device profiles comprises at least a unique user device ID and a user device authentication key associated with the one or more user devices; and
enabling the one or more user devices to update the device manager with the new firmware and new configuration file.
5. The method as claimed in claim 4, wherein enabling the one or more devices to update the device manager comprising the steps of:
receiving an authentication request from the one or more user devices, wherein the authentication request comprises at least the unique user device ID and the user device authentication key associated with the one or more user devices;
authenticating the one or more user devices based on the user device authentication key and the identification information thus received;
receiving a configuration request for updating the existing configuration file of the device manager, wherein the configuration request comprises at least a unique identification information of the FCMS storing the new configuration file;
updating the existing configuration file with the new configuration file by downloading the new configuration file from the FCMS identified by the received identification information;
receiving a firmware download request for updating the existing firmware of the device manager, wherein the download request comprises at least location information of the new firmware and firmware ID of the new firmware; and
updating the existing firmware with the new firmware by downloading the new firmware having the firmware ID from the location indicated by the received location information.
6. The method as claimed in claim 1, wherein the configuration file comprises configuration data and timing schedule of the one or more devices and the at least one Modbus library comprises a plurality of customized applications configured to control operations of the one or more devices.
7. A firmware and configuration file management system (FCMS) for automatic updating of a firmware and configuration file of a device manager coupled with the FCMS, the system comprising:
a processor; and
a memory disposed in communication with the processor and storing processor-executable instructions, the instructions comprising instructions to:
receive one or more inputs associated with configuration data of one or more devices communicatively coupled with the device manager;
generate a new configuration file and a new firmware associated with the device manager, wherein the configuration file comprises a unique configuration file ID and the new firmware comprises at least one Modbus library and a unique firmware ID;
receive periodically one or more requests from the device manager to update existing firmware and configuration file of the device manager; and
update the device manager with the new firmware and new configuration file upon receiving the one or more requests.

8. The system as claimed in claim 7, upon receiving periodically the one or more requests from the device manager, the processor is configured to perform the steps of:
receiving a firmware ID and a configuration file ID of the existing firmware and configuration file of the device manager respectively;
comparing the firmware ID of the new firmware with the received firmware ID, and determining that the existing firmware is to be updated if the firmware ID of the new firmware is greater than the received firmware ID; and
comparing the configuration file ID of the new configuration file with the received configuration file ID, and determining that existing configuration file is to be updated if the configuration file ID of the new configuration file is greater than the received configuration file ID.
9. The system as claimed in claim 7, upon receiving periodically the one or more requests from the device manager, the processor is configured to enable the device manager to perform the steps of:
receive the firmware ID and the configuration file ID of the new firmware and new configuration file of the FCMS;
compare the firmware ID of the existing firmware with the received firmware ID, and determining that the existing firmware is to be updated if the received firmware ID is greater than the firmware ID of the existing firmware; and
compare the configuration file ID of the existing configuration file with the received configuration file ID, and determining that existing configuration file is to be updated if the received configuration file ID is greater than the configuration file ID of the existing configuration file.
10. The system as claimed in claim 7, wherein the processor is further configured to perform the steps of:
receiving a request for registration of one or more user devices;
creating one or more user device profiles corresponding to the one or more user devices, wherein the one or more user device profiles comprises at least a unique user device ID and a user device authentication key associated with the one or more user devices; and
enabling the one or more user devices to update the device manager with the new firmware and new configuration file.
11. The system as claimed in claim 10, wherein the processor is configured to enable the one or more user devices to update the device manager by the steps of:
receiving an authentication request from the one or more user devices, wherein the authentication request comprises at least the unique user device ID and the user device authentication key associated with the one or more user devices;
authenticating the one or more user devices based on the user device authentication key and the identification information thus received;
receiving a configuration request for updating the existing configuration file of the device manager, wherein the configuration request comprises at least a unique identification information of the FCMS storing the new configuration file;
updating the existing configuration file with the new configuration file by downloading the new configuration file from the FCMS identified by the received identification information;
receiving a firmware download request for updating the existing firmware of the device manager, wherein the download request comprises at least location information of the new firmware and firmware ID of the new firmware; and
updating the existing firmware with the new firmware by downloading the new firmware having the firmware ID from the location indicated by the received location information.
12. The system as claimed in claim 7, wherein the configuration file comprises configuration data and timing schedule of the one or more devices and the at least one Modbus library comprises a plurality of customized applications configured to control operations of the one or more devices.
13. A non-transitory computer readable medium including instructions stored thereon that when processed by at least one processor cause a system to perform acts of:
receiving one or more inputs associated with configuration data of one or more devices communicatively coupled with a device manager;
generating a new configuration file and a new firmware associated with the device manager, wherein the configuration file comprises a unique configuration file ID and the new firmware comprises at least one Modbus library and a unique firmware ID;
receiving periodically one or more requests from the device manager to update existing firmware and configuration file of the device manager; and
updating the device manager with the new firmware and new configuration file upon receiving the one or more requests.

Dated this 1st day of June, 2015

M.S. Devi
Of K&S Partners
Agent for the Applicant
,TagSPECI:FIELD OF THE DISCLOSURE
The present subject matter is related, in general to management system, and more particularly, but not exclusively to method and a firmware and configuration file management system for automatically updating firmware and configuration file of a device.