How SMS Architecture works?

Hi,

1. Is there any clear explanation of SMS Architecture?

     a. What all data goes to Frontal Servers?

Are Frontal Servers the application servers? There's an MTA process that forks out child processes to pull data from the Campaign DB and use it to send SMS messages.

     b. As per my understanding, SMS works with a third party SMS connector like SMPP and Netsize and they connect with SMS service provider to send the SMS.

SMPP is a protocol which the SMS channel uses to send messages to vendors such as Netsize.

     c. Is Frontal Server really necessary to send the SMS communication out, what are the drawbacks of not using frontal servers?

If Frontal Server is application server, yes they're needed to run Adobe Campaign. Messages can also be sent via mid-sourcing, where the MTA's are in another instance.

2. What is the difference between different types of SMS connectors like SMPP, Netsize and all?

Different vendors, with different authentication and configurations. Some, like Mobivity will have a REST API requiring the channel be configured with custom js to send.

3. Is there a same case with Line channel, I have same questions for Line channel as well.

LINE is another channel, all sent by the MTA module with different protocols, API's, and payloads.

Thanks,

-Jon