This technology built in modules so that it can be customized to suit your clients’ particular needs. The primary design and developments goal is for 'ease of use' and scalability. The solution can easily be “private branded” to project the appropriate corporate logo, color scheme and formatting. It runs over the IP protocol and conforms to existing message system standards.
The product range consists of feature packs, each of which can be developed to suit clients’ particular corporate needs and easily incorporated into the existing, base, product. Some of the feature packs that can be developed are: SMS module, Interactive SMS, SMS Voting & Polling applications, Alerts & subscription module, MMS Module, WAP Features and similar.
The Messaging Server consists of four major components.
Content Collection Engine is a module that collects electronic contents from multiple sources and makes it available for further processing. The open standard architecture enables information to be collected from multiple sources, such as relational databases, stock quotes, or system events (system failures, database events …). The base system ships with the collection module capable of pulling information from Database and deliver to the end user based upon the request. Additional collection modules made available as plugging.
Distribution Engine a delivery server module with many administrative options.
Routing Engine a module that applies user defined rules to the information received, and delivers it to appropriate devices in the appropriate format. For example, information that needs to be delivered to wireless devices (SMS or MMS) is cleared of all non-information carrying components (pictures, attachments), and compressed so that the user gets the most information on a space limited device.
Administration Engine an added option for a powerful and flexible user interface module that allows users to modify profiles and rules from any Internet enabled computer in the world.
Extensibility via Application Programming Interface (API)
The Wireless Messaging Router to be provided as a component driven design, as defined in the open source. It is a common framework for server applications written using the .Net. This framework allows existing and yet to be created server applications to fit into a common platform and to share code, design and human resources.
In component-based architectures, a component is a replaceable building block. This engine should follow a sequence in such a way that it includes the concepts of Object Oriented Programming (OOP). In OOP classes often interdependent, reducing the amount of code re-use and the ability to switch out functionality when you need it. Component Oriented Programming (COP) follows through on promises made using OOP.
A component made up of multiple classes, but one component can be replaced with another that implements the same interfaces, and the system will still continue to work. Similarly, new components have to be developed and "plugged-in" to implement new functionality and in such a way that it extends the existing product.
Connectors:
Components used for the connectivity of this application to the Operator. This application supports for both SMSC and MMSC Connections.
Supported Message Types
- Text Messages - single and multipart message encode and decode.
- Picture Messages - 72x28 pixel BMP, JPG, GIF, NGG, NLM, NOL, OTB support. Unicode message text bodies
- Operator Logo Messages - 72x14 pixel BMP, JPG GIF, NGG, NLM, NOL, OTB support. Support for custom MNC and MCC values, as well as single PDU optimization options
- CLI Icon Messages (Group Graphics) - 72x14 pixel BMP, JPG, GIF, NGG, NLM, NOL, OTB support
- Ring tone Messages - Multipart support for RTTTL, Imelody, and Nokia OTA formats.
- Flash Messages - Unicode support, blinking support
- GPRS/WAP- Polyphonic/Wallpaper/Screensavers/COD/GCD/DRM/J2ME/Video/ Themes
- Multipart Support
- Supports message payloads for phones with >160 character (TEXT) message capability
- Third party VASP HTTP Interface
- MMS
- Supported Protocols:
- SMPP
- HTTP
- SMTP
- CIMD2
|
