 |
SmartAMM server system architecture
Purpose
The SmartAMM Server System is capable of handling communication with several SmartAMM gateways (the number depends on the selection of network type), as well as a number of ”backend applications”.
The system can be used for configuration/consolidation of the SmartAMM gateway deployments as well as delivery and reception of all types of data to and from the gateways.
Communication service provider
The communication service provider is the SmartAMM server service transmitting and receiving messages to and from the SmartAMM gateways.
It consists of a Messaging System and a configurable Message Dispatcher which provides transport for a specific network type.
The Communication Service Provider is delivered with Message Dispatchers for SMS and TCP/IP based communication, but others may be developed and added dynamically. The SMS Dispatcher is capable of using serial/usb and ip modems as well as online messaging services for transmitting and receiving messages.
SmartAMM API
The SmartAMM API is used by costumer systems wishing to utilize the Communication Service Provider. It consists of methods used for reading and writing the content messages as well as sending and receiving messages.
Customer system
The cosutmer System is one or more systems controlling or using data from SmartAMM Gateways.
Examples could be:
- A billing systems receiving meter readings
- An end user system, i.e. a webapplication enabling the end user to see his meter data or monitor/control his Smart House installation
- An adminstrative (CRM) system containing knowledge of the distribution and configuration of the Smart AMM gateway installations.
Application management and monitoring
An interface providing informational events regarding the state of the Communication Service Provider and its components as well as a JMX monitoring interface, which provides runtime access to the internals of the system.
The detail level if the informational messages and the availability of the JMX inteface can be specified in the configuration.
Communication
Communication between the backend applications and the Communication Service Provider is based on JMS compliant message queuing, enabling asynchronous delivery of billing data, alarms and other information from the SmartAMM Gateways.
The Communication Service Provider can deliver data to any JMS compliant messaging system, making it ready for enterprise deployment.
Requirements
The Communication Service Provider and the SmartAMM API requires at least Java 6.
The Communication Service Provider can be delivered as an installer for Windows (2000/XP/Vista) (tm), or as a standalone package for usage on either Linux or Windows, or other operating systems where Java is available.