Kent Williams
Moderator
Username: Kent
Post Number: 64
Registered: 10-2003
| | Posted on Wednesday, May 12, 2004 - 06:01 pm: | |
A customer contacted us recently with an interesting requirement. I'm mentioning this here, as it could be of interest to others.
They were using another vendor's WAP gateway and MMSC.
Similar to the Now SMS/MMS Gateway, the other vendor's MMSC is licensed based upon a messages per second licensing.
However, unlike the Now MMSC, which accepts all submitted messages, and simply throttles/queues messages for delivery based upon the license limits ... apparently, this MMSC rejects messages if its limits are exceeded.
As a simple example, the MMSC could be idle all day, and then if 2 users try to submit a message within the same second, the MMSC will reject one of the messages.
As you can imagine, this type of behaviour is almost impossible to plan for and control.
To address this problem, we adapted the Now.WAP Proxy so that it can throttle MM1 (MMS) send transactions submitted by mobile phones. The proxy queues MM1 send transactions to adhere to a configurable rate of x transactions per y seconds, to help stay within rigid license limits.
This functionality can be deployed with the Now.WAP Proxy as the WSP/W-HTTP proxy between mobile phones and the MMSC ... or the proxy can be deployed between an existing WAP gateway and MMSC.
If you would like more information, please contact us. E-mail wap@now.co.uk.
|
Search
Last
