SMSC Transceiver Connection performance

SMSC Transceiver Connection performance SearchSearch

SMS & MMS Technical Forum » MMS & SMS Technical Discussions (unsupported) » SMSC Transceiver Connection performance « Previous || Next »
Author Message
Mohan Devanoor
New member
Username: Mohan_devanoor

Post Number: 1
Registered: 01-2012
Posted on Wednesday, January 11, 2012 - 06:43 am:   

Hello ,
I have a small doubt regarding SMSC Transceiver connection. If i am using a transceiver connection and i have lot of MO & MT messages coming.
In this case how would a single transceiver connection handle MO & MT delivery efficiently? Will it initially handle MO and then switch to MT messages processing or will transceiver act based on time sharing to process MO & MT. Can you please clarify this?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3714
Registered: 08-2008
Posted on Wednesday, January 11, 2012 - 04:09 pm:   

Hi,

Generally speaking, separate sender and receiver connections will offer better throughput than a single transceiver connection.

But unless you are exchanging messages at higher speeds (> 50 messages per second), you are not likely to see much of a difference.

That said, it is very important that both ends of a connection support SMPP asynchronous mode if you hope to maximize performance on a transceiver connection. For more information on SMPP async mode see http://www.nowsms.com/smpp-async-mode.

--
Des
NowSMS Support
Mohan Devanoor
New member
Username: Mohan_devanoor

Post Number: 2
Registered: 01-2012
Posted on Thursday, January 12, 2012 - 06:22 am:   

Hi Des,

Thanks for the info. I have used the async mode in Transmitter connection. That helped me. But my question is regarding Transceiver implementation. Let me explain with an example:

Suppose i have a transceiver connection. At a particular point of time( say at 10 AM) i have both MO & MT messages. Let us say i have 5 MO's & 5 MT's per second. Initially i have sent an MT and waiting for MT Ack. As MO's are also being sent by SMSC to my app, i received MO in place of MT ack. Any ways i would process the MO and have a wait logic for MT Ack let us say i try 3 consecutive times for MT Ack. But as MO's are being sent by SMSC continiously i would be receiving MO's . I might be receiving MT Ack after some time.By that time i would finish my wait logic, and assume that MT has not been processed properly.

In the above case, Transceiver connection would not serve the purpose. I am not able to justify the usage of Transceiver connection. So, my doubt is how transceiver connection is useful in above case or should transceiver not to be used at such scenarios?
Am i clear?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3716
Registered: 08-2008
Posted on Thursday, January 12, 2012 - 07:07 am:   

If you are always waiting for 1 MT ack before transmitting the next message, then you are not properly taking advantage of async mode.

It is still possible to be overwhelmed with IO related to receiving messages, but this suggests that you are using a smaller window size than partner, or the partner priorities their sending and starves sending acks. Unfortunately you cannot control how your partner's implementation works, and they may be the limiting factor. .

--
Des
NowSMS Support
Mohan Devanoor
New member
Username: Mohan_devanoor

Post Number: 3
Registered: 01-2012
Posted on Thursday, January 12, 2012 - 09:33 am:   

Hi Des,
I am not waiting for MT Ack before transmitting next message. I am processing the Mo Message which i have received in place of MT Ack.

SMSC responds back with ack as soon as it receives a MT. But at the same time if we have suppose 1000 MO's to be sent from SMSC. Let us say my app has sent a MT to SMSC at 10:01:01 and SMSC has 1000 MO's to be sent at 10:01:01, then it would start sending the 1000 MO's and MT Ack starting from 10:01:01 and completes sending at 10:04:01. Then in worst cases i need to wait for 4 minutes to confirm the MT status. Which effects the performance.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3717
Registered: 08-2008
Posted on Thursday, January 12, 2012 - 04:32 pm:   

That could happen, but it would mean either a poor implementation on the other side of the connection, or too large of an async window being used. Unfortunately you cannot control the window size used by the other side.

So, yes, there can be scenarios like you describe.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3718
Registered: 08-2008
Posted on Thursday, January 12, 2012 - 04:36 pm:   

Another thought ... If you have to use transceiver mode, all you can do is try to speed up your receive processing, maybe prioritize your sending over acks to get the other side to slow down. (The faster you ack, the faster they will send.)

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics