en-US.Chapter-Overview.xml Maven / Gradle / Ivy
The newest version!
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "${ent.filename}">
%BOOK_ENTITIES;
]>
<chapter id="overview">
<title>Overview </title>
<section id="smsc_gateway_desc">
<title>SMSC Gateway</title>
<para>SMSC (Short Message Service Center) is a telecommunications network facility responsible for handling the SMS operations of a wireless network. When a subscriber sends an SMS message from a mobile phone, the message first reaches the SMS Center which then forwards the message to the desired destination. The SMS Center is responsible for routing the SMS messages and regulating the process. If the recipient is not reachable (the phone is switched off or out of coverage area etc.) the SMS Center will store the message to a database and forward it to the recipient when available. Messages that are delivered successfully and messages that failed to be delivered are stored in an archive database for logging purposes.</para>
</section>
<section id="mobicents_smsc_overview">
<title>&THIS.PLATFORM; &THIS.APPLICATION;</title>
<para>&THIS.PLATFORM;'s implementation of SMSC Gateway is the first and only open source SMSC Gateway with a host of rich features and advantages.
</para>
<para>
<variablelist>
<varlistentry>
<term>Java-based:</term>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; is the only Java based SMSC Gateway. It is robust and reliable and can be installed on any Operating System that supports Java (JDK 7 and SCTP).</para></listitem>
</varlistentry>
<varlistentry>
<term>Open Source:</term>
<listitem><para>The Software is open-source, giving you the freedom to understand the code and customise it to your enterprise needs. It is supported by a vibrant Open source community.</para></listitem>
</varlistentry>
<varlistentry>
<term>SS7 Hardware Cards:</term>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; supports E1/T1 links via SS7 cards (Dialogic SS7 cards) or Zaptel/Dahdi compatible TDM devices (Digium, Sangoma).</para></listitem>
</varlistentry>
<varlistentry>
<term>SIGTRAN (M3UA):</term>
<listitem><para>It also supports connectivity to MSC/HLR via SIGTRAN links (M3UA using SCTP).</para></listitem>
</varlistentry>
<varlistentry>
<term>Charging enabled (Diameter):</term>
<listitem><para>Pre paid based charging is enabled (optional) via Diameter Ro and Base protocol. RestComm SMSC easily integrates with <ulink url="http://telestax.wpengine.netdna-cdn.com/wp-content/uploads/2013/07/PRODUCT-DATASHEET-TELSCALE-Convergent-Charging-Server.pdf">RestComm Convergent Charging Server</ulink> over Diameter</para></listitem>
</varlistentry>
<varlistentry>
<term>Cloud-ready:</term>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; is cloud-ready and can also be deployed on a private cloud infrastructure.</para></listitem>
</varlistentry>
<varlistentry>
<term>Easy Configuration and Management:</term>
<listitem>
<para>
&THIS.PLATFORM; &THIS.APPLICATION; comes with an efficient Command Line Interface (CLI) tool allowing you to easily configure the gateway at run-time and manage it using
simple commands rather than do everything manually. &THIS.PLATFORM; &THIS.APPLICATION; also includes an efficient Web Interface administration tool for easy management and monitoring through a Web console. <!--In addition there will also be a Web based campaign tool to define and manage campaigns.-->
</para>
</listitem>
</varlistentry>
<!-- <varlistentry>
<term>Technical Specifications:</term>
<listitem> <para>&THIS.PLATFORM; &THIS.APPLICATION; is not restricted by any license or Transaction Per Second model. The only restricting factor is memory + CPU capacity of the host servers,
third-party applications or the underlying database service.
<itemizedlist>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; supports as many as 1073741823 incoming and 1073741823 outgoing concurrent sessions/dialogs.</para></listitem>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; supports unlimited E1 links and the only limiting factor is the underlying TDM board used.</para></listitem>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; SCTP supports as many associations as supported by the underlying Operating System.</para></listitem>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; M3UA can be confgured to have as many ASP's / IPSP's as needed by the system.</para></listitem>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; SCCP can be confgured to have virtually unlimited Global Title Translation rules and also supports wild characters for partial matching of Global Title digits.</para></listitem>
</itemizedlist>
</para>
</listitem>
</varlistentry> -->
<varlistentry>
<term>Major Features:</term>
<listitem> <para>&THIS.PLATFORM; &THIS.APPLICATION; enables mobile operators to provide core SMSC features like subscriber to subscriber SMS messaging, broadcasting campaigns and group messaging <footnoteref linkend='fnrestcomm'/>between subscribers.
<itemizedlist>
<listitem>
<para>&THIS.PLATFORM; &THIS.APPLICATION; can handle mobile originated SMS and deliver them to the intended recipient (mobile, ESME or SIP).
It also provides a flexible routing mechanism to route messages to/from ESME over SMPP protocol. &THIS.PLATFORM; &THIS.APPLICATION; supports normal style (Server side) SMPP connection.
It can also act as ESME initiating connection to third party SMSC (Client side). Submit_Sm, Data_Sm, Submit_Multi and Deliver_Sm messages are supported.
</para>
</listitem>
<listitem>
<para>&THIS.PLATFORM; &THIS.APPLICATION; supports SIP connection through JSLEE SIP RA.
</para>
</listitem>
<listitem>
<para>For incoming from SMPP ESME messages, &THIS.PLATFORM; &THIS.APPLICATION; supports StoreAndForward, Datagramm and Transactional modes and a special ForwardAndStore mode for reducing the database load. </para>
<para>When a message comes from SMPP, the &THIS.APPLICATION; checks the <literal>EsmClass</literal> field in the SMPP message. For Datagramm and Transactional modes, the SMSC will try to immediately deliver the message to a destination. If it is in Transactional mode, the SMSC will also return a delivery result (success/failure) to the ESME. Such messages are not stored in the Cassandra database. In case of delivery failure the message will be dropped and no more delivery attempts will be made.</para>
<para>
If the <literal>EsmClass</literal> field indicates StoreAndForward (or default) mode, more than one attempt will be made to deliver the message (if the first attempt fails). Such messages will be stored in the Cassandra database. The &THIS.APPLICATION; can be configured in two modes for processing of StoreAndForward messages as shown below:
<variablelist>
<varlistentry>
<term>StoreAndForward (normal) mode</term>
<listitem><para>In the StoreAndForward mode, an incoming "StoreAndForward" message will always be stored in a database and scheduled for delivery after few seconds. This mode is fully compliant with SMPP specification. </para></listitem>
</varlistentry>
</variablelist>
<variablelist>
<varlistentry>
<term>ForwardAndStore (fast) mode</term>
<listitem><para>In the ForwardAndStore mode, an incoming "StoreAndForward" message will be attempted for delivery immediately, without storing in the database and therefore without any delay. If this first delivery attempt fails, the message will be stored in a database for futher scheduling.
</para></listitem>
</varlistentry>
</variablelist>
</para>
</listitem>
<listitem>
<para>Messages that come from SS7 or SIP are processed the same way as "StoreAndForward" messages that come from SMPP ESME.
</para>
</listitem>
<listitem>
<para>&THIS.PLATFORM; &THIS.APPLICATION; supports Non Transparent Home Routing as explained in 3GPP Specification version 23.840 5.2.3.
</para>
</listitem>
<listitem>
<para>&THIS.APPLICATION; has support for SSL for SMPP connection (both client and server side).
</para>
</listitem>
<listitem>
<para>&THIS.PLATFORM; &THIS.APPLICATION; can be configured for congestion control to reject messages when the number of messages in processing exceeds a configurable limit (<literal>MaxActivityCount</literal>). </para>
<para>When the SMSC is configured in ForwardAndStore (fast) mode, SMPP originated messages will be first rejected. Then when the number of messages in processing further increases, SIP originated messages will be rejected and finally SS7 originated messages will be rejected. </para>
<para>When SMSC is configured in StoreAndForward (normal) mode, only datagramm and transactional SMPP originated messages will be rejected. However StoreAndForward messages and all SS7/SIP originated messages will be stored in the Cassandra database and the scheduling for delivery of these messages will be stopped until the number of messages in processing does not exceed the configured limit.
</para>
</listitem>
<listitem>
<para>&THIS.PLATFORM; &THIS.APPLICATION; has a congestion control at ESME side. Each ESME can be configured for rate limit per a second, a minute, a hour or a day. </para>
</listitem>
<listitem>
<para>&THIS.PLATFORM; &THIS.APPLICATION; supports ReportSMDeliveryStatus and AlertServiceCentre requests after mobile delivery failure.</para>
</listitem>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; supports GSM7, GSM8 and UCS2 message encoding.</para></listitem>
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; itself splits ESME and SIP originated long length messages before delivering to mobile phones, if a message does not contain User Data headers (UDH).</para></listitem>
<listitem><para>Multi-tenancy support: &THIS.PLATFORM; &THIS.APPLICATION; supports a model of message network as a splitted to several logical subnetworks and SMSC messages will be logically processed only in one of this logical subnetwork.
SMPP ESMEs, SCCP SAPs (Service Access Points) and SIP connector will belong to one of such subnetworks (A subnetwork is identified by a digital value - networkId).
Any message that has come to SMSC GW from some port (ESME, SS7, SIP) will belong to networkId (subnetwork) from networkId of the port the message has come to SMSC.
Then the message will be routed into the port (ESME, SS7, SIP) which belongs to the same networkId (subnetwork).
</para></listitem>
<listitem><para>Additionally, when enabled with proper administrator privileges, &THIS.PLATFORM; &THIS.APPLICATION; allows convenient group messaging <footnoteref linkend='fnrestcomm'/>between subscribers (e.g. family, friends, colleagues) .</para></listitem>
<!--<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; offers “SMS Broadcasting” which enables marketing campaigns. Via
convenient Web UI, campaign administrators can prioritize, schedule and monitor a
message broadcasting workfow. Campaigns can be distributed over multiple SMSC
instances for faster SMS delivery to all intended recipients.</para></listitem> -->
<listitem><para>&THIS.PLATFORM; &THIS.APPLICATION; is built on the RestComm jSS7 stack which provides advanced SCCP routing
rules to map short codes to MSISDN, allowing users to send an SMS to a short-code instead of a complete MSISDN. </para></listitem>
<listitem><para>It also enables value added services<footnoteref linkend='fnrestcomm'/> through integration with OTT social networks and microblogs such as Facebook and Twitter.</para></listitem>
<listitem><para>
A single &THIS.PLATFORM; SMSC node can process up to 1000 SMS/sec. Multiple SMSC nodes can be arranged in a cluster across one or more geographically distributed data centers to scale up throughput and provide various levels of redundancy, high availability and fault tolerance.
</para></listitem>
</itemizedlist>
</para>
</listitem>
</varlistentry>
<varlistentry>
<listitem> <para> &THIS.PLATFORM; &THIS.APPLICATION; can be adapted to the needs of telecom service providers of different sizes in any country.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</section>
<section id="smsc_gateway_sip">
<title>Session Initiation Protocol (SIP) Support</title>
<para>
IP Short Message Gateway (IP-SM-GW), which is in line with relevant 3GPP 23.824 specifications, acts as a bridge managing the origination and termination of SMS messages between circuit-switched and IP-based networks (over SIP). With this solution, mobile operators can make use of existing messaging platforms such as short message service centers (SMSCs) to deliver IP-based messaging. The IP-SM-GW is also essential for rolling out rich communication services (RCS), which enable operators to deliver sticky messaging services like presence-enabled address book, SIP-based chat services and mobile instant messaging.
</para>
<para>
RestComm SMSC has support for SIP messagaing and can send short messages from SIP to SS7 or ESME and vice-a-versa. RestComm SMSC can easily be integarted with RestComm RestComm via SIP to enable developers to rapidly build voice, video, WebRTC, USSD, SMS, fax and rich messaging applications. For more details about RestComm you may refer to, <ulink url="http://www.telestax.com/restcomm/">TeleStax website.</ulink>
</para>
</section>
</chapter>
© 2015 - 2025 Weber Informatics LLC | Privacy Policy