This is just an introduction slide to show the concept of TelScale USSD Gateway . It includes basic concept,advantages,functionality etc etc

1. TelScale USSD
Gateway
By: Sonu Krishna

2. The Idea’s
 TelScale USSD- Basics
 USSD – The known things
 USSD Gateway – Features and Technical specs
 Architecture
 Configuring
 HTTP Transfer Mechanism
 HTTP Payload – XML Structure
.
2

3. HELLO!
I am Sonu Krishna..
I am here because I
trying to learn
something and I like
to share..
3

4. 1.
TelScale USSD
Starts..
Let’s begin with basics

5. “
5
TelScale USSD Gateway -- Basics
 robust and carrier proven USSD Gateway build on
a modern extensible middleware platform.
 Real-time interactions to mobile subscribers and
deliver interactive content to their mobile phones.
 Acts as an intermediary platform linking the
service applications to the GSM network in a
session oriented communication
 Comes with an efficient Command Line Interface
(CLI) and also with a good Graphical User
Interface(GUI)

6. USSD --Basics
 Unstructured Supplementary Services Data => real-time connection during a
USSD session
 USSD is used by the service provider to offer the subscriber with operator
services(prepaid callback service, location-based content services, menu-
based information services etc..)
 Difference between USSD and SMS
 SMS => store and forward method of message delivery
 USSD Session => USSD establishes a real time session between the mobile
handset and the application handling the service

7. “
USSD Session
7
 A user dialing an USSD service
number (short code) initiates a dialog
with the USSD handling application
deployed on the Restcomm Platform
 The "Network Node" in the figure
could be a MSC, HLR or VLR.
 The Restcomm Platform integrates
with the "Network Node" using the
MAP protocol.

8.  MAP message flow for data transfer between
the "Network Node" and the Restcomm
platform
 Network sends a 'TCAP Begin' message
with the Component
'MAP_PROCESS_UNSTRUCTURED_SS_RE
QUEST' to the Restcomm platform. Which
invoke the application logic
 The Application requests additional
information from the user (action one or
action two) via
'MAP_UNSTRUCTURED_SS_REQUEST'
encapsulated in a 'TCAP Continue' message.
 And it continues ... and the ‘TCAP dialogue’
terminates at the end
MAP Message Flow

9.  Java Bases
 Open Source
 Carrier Grade Performance
 Load Balancing and Transparent
Failover
 Cloud Ready
 Network Push
 Multilingual => UCS2 encoding in
addition to GSM 7 Bit.
 SS7 Hardware Cards
 SIGTRAN (M3UA)
 Easy Configuration and
Management(CLI,GUI)
USSD Gateway – Features &
Technical Specs
Restcomm USSD GateWay is not restricted by Transaction Per Second model. The only
restricting factor is memory + CPU capacity of the host servers, third-party applications or the
underlying database service
 Supports unlimited E1 links and
the only limiting factor is the
underlying TDM board used.
 SCTP supports as many
associations as supported by the
underlying Operating System
 confgured to have virtually
unlimited Global Title Translation
rules
 Etc ..etc
9

10. Architecture..
Is a software based implementation of the SS7 protocol

11. Installation & Setup
 Installation Guide:
http://documentation.telestax.com/core/ussd/USSD_Gateway_In
stallation_Guide.html
 Running =>
 Running USSD Examples in Simulator
 Running the Shell
 Running the Graphical User Interface

12. Configuring
 Once you complete setting up the Gateway you must configure the SS7 Stack, USSD
routing rules and USSD paramters.
 Configuring the SS7 Stack
 Configuring the USSD Gateway.
 1. noroutingruleconfigerrmssg => USSD Gateway is not configured for the dialed
shortcode
 2. dialogtimeouterrmssg => timout msg
 3. servererrmssg => error in the USSD Gateway
 4. serveroverloadedmsg => too many TCAP dialogs are in processing
 5. dialogtimeout => set the request timeout duration in milliseconds.
 6. maxactivitycount => If a count of
 TCAP dialogs exceeds of this value then USSD GW will reject new incomig
 PULL requests from subscribers
 7. ussdgt => set a value for USSD Global Title
 8. hlrssn => set hlr ssn

13. HTTP Transfer Mechanism
 Restcomm USSD GateWay acts as a HTTP Client invoking the HTTP
Application deployed on the third-party Application Server.
 The HTTP Request/Response carries XML payload with USSD specific
information.
 The diagram on next page depicts an example message sequence for
interacting with the Restcomm USSD GateWay HTTP API.

14. 14

15. HTTP Transfer Mechanism Cont....
 When the subscriber initiates a USSD Request, the HLR sends a
MAP_PROCESS_UNSTRUCTURED_SS_REQUEST to the USSD Gateway.
 USSD GateWay invokes the third-party Application through a HTTP POST Request, carrying
an XML Payload with USSD specific information.
 The Application will send a HTTP Response, carrying an XML Payload, to the USSD GateWay
 The USSD GateWay will send a MAP_UNSTRUCTURED_SS_REQUEST of type Continue to
the HLR.
 Based on the input from the subscriber, the third-party Application will send a final response
(HTTP Response, carrying an XML Payload) and invalidate the session.
 The USSD GateWay will send a MAP_PROCESS_UNSTRUCTURED_SS_RESPONSE of type
End to the HLR.

16. HTTP Payload – XML format
 The HTTP Request/Response carries XML
Payload with USSD specific information as
defined below
 <dialog> contains various attributes to
represent the state and the parameters of the
Dialog
 Type => Unidirectional, Begin, End,
Continue, Abort etc..
 AppCntx => Represents the MAP
Application Context for USSD GW
request.
 USSD Gateway can be connected to
multiple operators/network at same time.
For each operator unique networkId is
assigned.

17. XML Structure Cont..
networkid
USSD Gateway can be
connected to multiple
operators/network at same
time. For each operator
unique networkId is
assigned.
mapMessagesSize
Represents the actual
number of MAP messages
carried in the <dialog>
MapAbortProviderR
eason
If this parameter is present, it
means the underlying Dialog
is Provider Aborted.
Etc..Etc ...
localId
Represents the local TCAP
transaction ID
remoteId
Represents the remote
TCAP transaction ID.
17

18. THANKS!
18