BatMP

Multiplatform: The gateway must be completely functional in any operating system where it can be executed.

Secure: Only the authorized users must be allowed to interact with the system and their own devices and/or parameters. There are several access profiles established, so the data security and communication security can be guaranteed. Users must authenticate themselves in a secure way against the central server so they can have Access to the data which are stored there. 

Extensible design: Not only the hardware design, but also the software design must take into account that in the future new requirements may appear (new functionalities or modifications over them). These future requirements should be able to be implemented with the minimum impact on the rest of the system functions. The system model should ease the development of high level services.

IP Connectivity: The system will use the protocol TCP/IP to allow Access to the services and as a way of communication between different remote systems. It will also use the software architecture style REST as a means to perform that communication. 

Hot plugging of services: The system must be able to install remotely, start, stop, update, and uninstall new services without requiring a reboot. To be able to fullfill all these requirements, the system must be based on OSGi. Using this specification the system is divided in smaller modules called bundles which can be installed and uninstalled without rebooting the gateway.  

In the next figure the modular structure of a platform BatMP and all its modules can be observed.

Hot plugging of devices: The system must be able to manage the connection of new devices without rebooting or disconnecting the gateway. To fulfill this requirement, the system will get as much information as it can and will only ask to the user the data which it cannot get independently (location, uses, …)