Thursday, March 9, 2017

SaaS paradigm for IN/VAS providers - Speed & Connectivity

Telecom VAS/IN providers suffer with high maintenance costs, large deployment-patch cycles resulting in overall prolonged turn around time. High maintenance costs comes with typically in-premise hardware and onsite personnel/s to manage and maintain ongoing deployments. Large deployment-patch cycles further aggravate the maintenance costs and cuts profit. 

One stop solution to these problems is, re-architecting the whole product as software-as-a-service and deploying it in cloud. But can VAS providers really convince Telcos to agree on Cloud SaaS version of the products ? The crux of the matter is, how is Telecom product different from other softwares ready to take advantage of cloud infrastructure ?

Most of the telecom products are characterised as near mission critical for functional requirements. For example, a CAMEL based prepaid engine is required to deduct the cost of calls as it proceeds. It is required to respond to MSC within stipulated time window to minimise the call setup time. Call setup time affects the user experience. Increasing the capacity of MSC does lower the call setup time but it isn't desired as it adds to CAPEX for obvious reasons. 

Continuing same example, suppose CAMEL prepaid engine is moved to cloud and exposed as SaaS to the Telecom operator. The total processing time increases to network delay + processing time at prepaid. This increases queuing delay at MSC that in turn results in lower throughput and delayed call setup time. That can be mitigated by introducing more MSCs or renting dedicated lease lines. Lease line is generally the desired option for such mission critical products.

On the other hand, a near real time VAS products such as missed call notifier or call me back notification service could gel very well with cloud infrastructure over public internet, since the perceived delay of couple of seconds will not make much difference to the user experience.

Most of the Telecom VAS products make use of SS7 protocols and integrate tightly with the core network nodes. Legacy SS7 products will not port as it is on public network, sheerly for the reason that public internet is primarily IP based and legacy SS7 services use SS7 networks. The solution is SIGTRAN stack that facades the IP stack and provides m3ua services to the top layers such as ISUP, TUP and TCAP.



Obviously SIGTRAN stack providers become one of the most essential enabler for Telecom cloud SaaS. Telcos provide SIGTRAN connectivity by putting SIGTRAN gateways in their network with public IP network on one side and SS7 network on the other.

Now exposing core network nodes to public network is risk in itself. Security in cloud SaaS is one of big chunk that needs to be addressed properly else it results in embarrassing outcomes for service providers as well as customer. Security and other parameters, We'll continue in the next article.