What is a smsc?
A SMSC is a infrastructure node which sits inside the operator network and enables SMS traffic to flow. Almost every operator has one or more SMSC deployed to enable customer SMS traffic (also called P2P SMS) but due to the rapid growth in messaging both in P2P sector and in machine to human SMS sector the need to provide additional SMSC capacity is a constant requirement.
The tasks of an SMSC can be described as:
The tasks of an SMSC can be described as:
- Reception of text messages (SMS) from wireless network users
- Storage of text messages
- Forwarding of text messages
- Delivery of text messages (SMS) to wireless network users
- Maintenance of unique time stamps in text messages
who might require a smsc?
If you belong to one of the following group and you are looking for a SMSC, we can definitely give you a an interesting option:
- Telecom Operators / Carriers
- Captive Network Operators (Defense, Government, Labs)
- VAS Providers
- Bulk SMS Aggregators
- System Integrators
Under the hood (Technology)
SMSC Modules:
Core SMS Engine
The core SMS engine is the heart of the system which is responsible for the communication between the various modules of the SMSC. The core engine also takes care of redundancy and optimal path selection for transmission of data.
Signalling Server
The transmitter and receiver component are the primary interfaces into the SS7 network and is responsible for interacting with the MSC/HLR on MAP layer of the SS7 stack.
SMS Routing
The routing module takes care of choosing the optimal path of delivery when more than one SS7 connectivity link exists. The routing module can connect to the operator OSS through CORBA for getting input intelligence on the least cost/least congestion path available.
SMS Filtering
This module is used to set the White-list and Blacklist of MSISDN series to determine the set of mobile customers who would be allowed to use the SMSC. It can also be used to create more complicated business logic depending on the requirement of the operator.
Message Queue
The message store Queue is a high performance message Queue which stores all the SMS traffic before being forwarded to the appropriate destination. The DB structure is designed with redundancy and high transaction capacity.
Connectivity Gateways
SMSC comes bundled with SMPP 3.4 and HTTP servers as default. The function of the gateway is in a A2P type of SMS traffic where the SMSC is used to push bulk SMS traffic. The remote system might be connected to the gateway through LAN/MAN/WAN/Internet.
IP Connect Filter
IP connect filter is responsible for maintaining the access restriction credentials from remote machines and frees up the gateways from the extra load.
Control UI / Reports
Control UI is a Web UI which is used to control all the activity parameters of the SMSC. It can control SS7 network parameters, module configs, gateway configs and user management. A complete set of reporting and auditing interfaces are also provided for observing the performance of the SMSC.
Core SMS Engine
The core SMS engine is the heart of the system which is responsible for the communication between the various modules of the SMSC. The core engine also takes care of redundancy and optimal path selection for transmission of data.
Signalling Server
The transmitter and receiver component are the primary interfaces into the SS7 network and is responsible for interacting with the MSC/HLR on MAP layer of the SS7 stack.
SMS Routing
The routing module takes care of choosing the optimal path of delivery when more than one SS7 connectivity link exists. The routing module can connect to the operator OSS through CORBA for getting input intelligence on the least cost/least congestion path available.
SMS Filtering
This module is used to set the White-list and Blacklist of MSISDN series to determine the set of mobile customers who would be allowed to use the SMSC. It can also be used to create more complicated business logic depending on the requirement of the operator.
Message Queue
The message store Queue is a high performance message Queue which stores all the SMS traffic before being forwarded to the appropriate destination. The DB structure is designed with redundancy and high transaction capacity.
Connectivity Gateways
SMSC comes bundled with SMPP 3.4 and HTTP servers as default. The function of the gateway is in a A2P type of SMS traffic where the SMSC is used to push bulk SMS traffic. The remote system might be connected to the gateway through LAN/MAN/WAN/Internet.
IP Connect Filter
IP connect filter is responsible for maintaining the access restriction credentials from remote machines and frees up the gateways from the extra load.
Control UI / Reports
Control UI is a Web UI which is used to control all the activity parameters of the SMSC. It can control SS7 network parameters, module configs, gateway configs and user management. A complete set of reporting and auditing interfaces are also provided for observing the performance of the SMSC.
feature overview
· The SMSC supports Mobile originating, Mobile Terminating, ESME originating & ESME terminating messages
· The SMSC supports for text messages with alphanumeric CLI.
· The SMSC supports picture messages, Enhanced Binary Messages, WAP Push, Port Delivery SMS, Settings SMS etc.
· The SMSC has the facility to configure the maximum short message length on a system – wide basis or for each interface supported and to specify whether to reject messages that exceed the maximum length, or truncate them to the maximum length
· SMS concatenation (stringing several short messages together) and compression (getting more than 160 characters of data within a single short message) are provided as defined in the GSM 3.40 SMS specifications
· Validation of the Originating Subscriber is done before accepting messages from a mobile
· The SMSC also verifies if the destination address is served by it. If not, an appropriate error code is generated
· Originating External Short Messaging Entity (ESME) Validation is done before message acceptance from the ESME
· The SMSC has support for “Message Validity Period” definable by subscriber in the message headers/while composing the messages
· Global Title Addressing: The SMSC supports the use of global title addressing, enabling subscribers to send short messages without knowing the explicit network address of the messages’ recipients
· The SMSC generates a “Unique Message ID” for each submitted message. This unique ID can be used for tracing the message
· System Wide Black and White lists for both mobiles and ESME's can be specified
· The SMSC provides support for "More Messages to Send" to deliver multiple messages to the mobile in a single session
· The SMSC supports Delivery Notification and Delivery Failure Notification with cause, (failed, deferred, successful messages with time of delivery and attempts made) both in the log files as well as reply to the message originating entity/mobile
· The SMSC makes it possible to notify subscribers that their mobile handset memory had exceeded
· The System has “throttle control” on the number of Message Delivery attempts it sends towards MSC(s). It is also able to “identify” & “isolate” an MSC through which success rates of deliveries are poor. It is able to “resume” sending SMS via an MSC (earlier detected as a “poorly performing MSC”) upon restoration of the MSC to its “normal” state
· The SMSC supports for text messages with alphanumeric CLI.
· The SMSC supports picture messages, Enhanced Binary Messages, WAP Push, Port Delivery SMS, Settings SMS etc.
· The SMSC has the facility to configure the maximum short message length on a system – wide basis or for each interface supported and to specify whether to reject messages that exceed the maximum length, or truncate them to the maximum length
· SMS concatenation (stringing several short messages together) and compression (getting more than 160 characters of data within a single short message) are provided as defined in the GSM 3.40 SMS specifications
· Validation of the Originating Subscriber is done before accepting messages from a mobile
· The SMSC also verifies if the destination address is served by it. If not, an appropriate error code is generated
· Originating External Short Messaging Entity (ESME) Validation is done before message acceptance from the ESME
· The SMSC has support for “Message Validity Period” definable by subscriber in the message headers/while composing the messages
· Global Title Addressing: The SMSC supports the use of global title addressing, enabling subscribers to send short messages without knowing the explicit network address of the messages’ recipients
· The SMSC generates a “Unique Message ID” for each submitted message. This unique ID can be used for tracing the message
· System Wide Black and White lists for both mobiles and ESME's can be specified
· The SMSC provides support for "More Messages to Send" to deliver multiple messages to the mobile in a single session
· The SMSC supports Delivery Notification and Delivery Failure Notification with cause, (failed, deferred, successful messages with time of delivery and attempts made) both in the log files as well as reply to the message originating entity/mobile
· The SMSC makes it possible to notify subscribers that their mobile handset memory had exceeded
· The System has “throttle control” on the number of Message Delivery attempts it sends towards MSC(s). It is also able to “identify” & “isolate” an MSC through which success rates of deliveries are poor. It is able to “resume” sending SMS via an MSC (earlier detected as a “poorly performing MSC”) upon restoration of the MSC to its “normal” state