Purpose of this training

SS7 Basics
SGU
CAMEL SLU
Call Scenarios
Configuration
Debug tools
06/03/16

SS7 Basics

06/03/16

SS7 Protocol Stack

INAP, CAMEL, or MAP
Transaction Capabilities
Application Part (TCAP)
ISDN User Part (ISUP)

Signaling Connection
Control Part (SCCP)

Message Transfer Part Level 3 (MTP L3)

Message Transfer Part Level 2 (MTP L2)
Physical Layer
06/03/16

Physical Layer
This defines the physical and electrical
characteristics of the signaling links of the
SS7 network.

06/03/16

Message Transfer Part Level 2

Provides link-layer functionality.
Ensures that the two end points of a
signaling link can reliably exchange
signaling messages.
Incorporates such capabilities as error
checking, flow control, and sequence
checking.
06/03/16

Message Transfer Part Level 3

Provides network layer functionality.
Ensures that messages can be delivered
between signaling points across the SS7
network regardless of whether they are
directly connected.
Includes such capabilities as node
addressing, routing, alternate routing, and
congestion control.
06/03/16

Message Signal Unit (MSU)

Service Information Octet (SIO)
Four bits are the Service Indicator, used to
indicated the type of information contained
Two bits indicate the network type

Signaling Information Field (format based

on Service Indicator)

06/03/16

Service Information Octet (SIO)

Service Indicator (4 bits)

0 - signaling network management

1 - signaling network testing and maintenance
3 - Signaling Connection Control Part (SCCP)
5 ISDN User Part (ISUP)

Network (2 bits) national or international

06/03/16

Signaling Information
The first portion is always the Routing Label
Destination Point Code (DPC) 14 bits - Address
of the node to which the message is being sent
Originating Point Code (OPC) 14 bits - Address
of the node to which originated the message
Signaling Link Selection (SLS) 4 bits Distributes load among redundant signaling links

06/03/16

Signaling Connection Control Part

(SCCP)
SCCP offers end-to-end addressing, even across
several network nodes and countries
Additionally, SCCP allows for a distinction among
the various applications within a network node,
referred to as subsystems, and identified by a
SubSystem Number (SSN)
SCCP provides its own management functions for
administrative tasks
SCCP provides for error detection and an optional
segmentation of data to be transmitted
06/03/16

10

SCCP Management Messages

SubSystem Allowed (SSA) Both sides
may send to the respective peer that a
subsystem is now available
SubSystem Prohibited (SSP) An available
subsystem has been taken out of service
SubSystem Status Test (SST) Query the
state of a subsystem
06/03/16

11

Subsystems of the SCCP

0 SSN not known or not available

1 SCCP management
5 MAP
146 - CAMEL

06/03/16

12

Services of the SCCP

Two connectionless and two connection-oriented
service classes are available to users of the SCCP
for actual data transfer
TCAP only uses Connectionless Class 0 or Class 1
Class 0 there is no guarantee of sequenced
delivery
Class 1 guarantees sequenced delivery

06/03/16

13

Parameters of SCCP Messages

Calling Party Address and Called Party Address
These have the same format and identify the type
of address as well as the address itself
The address may consist of any combination of the
following:
The Signaling Point Code (SPC) 2 bytes
The SubSystem Number (SSN) 1 byte
The Global Title (> 3 bytes)
06/03/16

14

Global Title Translation

SCCP provides the ability to perform incremental
routing using a capability called Global Title
Translation (GTT)
GTT frees originating signaling points from the
burden of having to know every potential
destination to which they might have to route a
message
A switch can originate a query, for example, and
address it to an STP along with a request for GTT.
GTT is also used at the STP for load sharing
06/03/16

15

Transaction Capabilities Application

Part (TCAP)
TCAP defines the messages and protocol used to
communicate between applications (deployed as
subsystems) in nodes
It is used for database services such as calling
card, 800, and IN as well as switch-to-switch
services including repeat dialing and call return
Because TCAP messages must be delivered to
individual applications within the nodes they
address, they use the SCCP for transport
06/03/16

16

TCAP Messages
These are used to carry the components, which do the
actual work
There are five TCAP message types:

BEGIN starts a transaction

CONTINUE continues a transaction
END terminates a transaction
ABORT terminates abnormally a transaction
UNI unidirectional (no transaction established)

Transactions are identified by Transaction ID

1 to 4 bytes long

You can have many simultaneous transactions

06/03/16

17

BEGIN message
Starts a transaction
Contains Origination Transaction ID
(OTID) which uniquely identifies the
transaction to the originator
Possible responses are CONTINUE, END,
or ABORT

06/03/16

18

CONTINUE message
Continues a transaction
Contains Origination Transaction ID (OTID)
which uniquely identifies the transaction to the
originator, and Destination Transaction ID (DTID)
which uniquely identifies the transaction to the
destination
Possible responses are CONTINUE, END,
ABORT, or none.
06/03/16

19

END message
Terminates a transaction
Contains Destination Transaction ID
(DTID) which uniquely identifies the
transaction to the destination
There is no response to END

06/03/16

20

ABORT message
Terminates abnormally a transaction
Contains Destination Transaction ID
(DTID) which uniquely identifies the
transaction to the destination
There is no response to ABORT

06/03/16

21

UNI message
Unidirectional message. No transaction
established.

06/03/16

22

TCAP Dialog Scenario

06/03/16

23

TCAP Components
TCAP components do the actual work
There are five component types:
INVOKE (invoke an operation)
RETURN_RESULT_LAST (returned result of an
operation, last or only segment)
RETURN_RESULT_NOT_LAST (returned result of an
operation, not last segment)
RETURN_ERROR (returned error response to an
operation)
REJECT (operation rejected)
06/03/16

24

INVOKE Component
Contains Invoke ID
Contains operation requested along with
parameters (eg: InitialDP, SendRoutingInfo)
Can contain Linked Invoke ID to tie it to
another operation
Possible responses are INVOKE,
RETURN_RESULT, RETURN_ERROR,
REJECT, or none
06/03/16

25

RETURN_RESULT Component
Contains Invoke ID
RETURN_RESULT_LAST contains the
last or only segment of operation result
RETURN_RESULT_NOT_LAST contains
a segment, not last, of operation result
Possible responses are REJECT or none

06/03/16

26

RETURN_ERROR Component
Contains Invoke ID
Returned error response to an operation
Possible responses are REJECT or none

06/03/16

27

REJECT Component
Contains Invoke ID
Rejects a previous component
There is no response to REJECT

06/03/16

28

TCAP Component Scenario

06/03/16

29

INAP Intelligent Network

Application Protocol
Defines the operations required between IN
network elements, such as SSPs and SCPs.

06/03/16

30

CAMEL - Customized Application

for Mobile network Enhanced Logic
CAMEL Phase 1 and Phase 2 are based on ETSI
Core INAP CS-1.
CAMEL remedies INAP CS-1 shortcomings by,

Eliminating options
Being normative, assuring 100% vendor compatibility
Optimizing signaling efficiency
Define a marketing driven set of features
Add mobile specific functionality and parameters
06/03/16

31

WIN Wireless Intelligent Network

Similar in function to CAMEL and used mainly in
North American and related networks.
Based on ANSI IS-41.

06/03/16

32

SGU (Signaling Gateway Unit)

06/03/16

33

What is SGU
SGU is an Omni SS7 node supporting ITU
(CCITT), ANSI, or other protocol variants
It is dedicated to supporting TCAP based
protocols (CAMEL, MAP, USSD, etc.)
It supports SS7 protocol up to the SCCP
level, plus a message routing function at the
TCAP level
06/03/16

34

What Is Distributed TCAP (DTCAP)

DTCAP is a proprietary architecture that allows
the TCAP protocol messages to be distributed
across multiple SLUs.

06/03/16

35

DTCAP Message Flow

SLU 1
ACTIVE

SLU 2
ACTIVE

....

SLU N
ACTIVE

TCAP
PDUs
SGU CE1
06/03/16

...
SS7 links

SGU CE4

36

DTCAP Specification

Support ANSI, ITU, or other protocol variants.

Support 4-CE SGU system (future).
Support full load sharing within the SGU.
Support routing based on SCCP Sub System Number
(SSN).

Support running multiple DTCAP Applications within a SLU.

Support routing of all TCAP messages belonging to

the same call/transaction to the same SLU DTCAP
Application.
06/03/16

37

DTCAP Specification - continued

Support routing based on congestion
indication from DTCAP Applications. Calls
will be delivered to the DTCAP Application
that is not congested.
Support graceful shutdown of DTCAP
Application.

06/03/16

38

DTCAP Specification - continued

Ability to survive and recover from failure of one
or more CEs (less than N) of a N-CE system.
Ability to survive and recover from process restart
and switchover.
Support 400K BHCA on a Dual CE CCS (Pentium
III UPU with Dual Processors running at
500MHz). This estimate is based on 5 TCAP
messages per call.
06/03/16

39

DTCAP Components
DTCAP Router A SCCP application program
that resides at the SGU and which executes under
Omni/Unix.
DTCAP Application A TCAP/IN protocol
application that resides at the SLU and which
executes under Omni/Unix. CAMEL, MAP,
USSD are few of the many possibilities.
DTCAP Protocol Protocol between DTCAP
Router and DTCAP Application.
06/03/16

40

DTCAP Components - continued

SLU 1
DTCAP Application

SLU 2
DTCAP Application

CAMEL, INAP, WIN User

CAMEL, INAP, WIN User

Omni CAMEL, INAP, WIN lib.

Omni CAMEL, INAP, WIN lib.

Omni TCAP library

Omni TCAP library

DTCAP Protocol

DTCAP Protocol

TCAP PDUs
UDP

UDP

DTCAP Router

06/03/16

UDP

UDP

DTCAP Router

DTCAP Protocol

DTCAP Protocol

DTCAP Router Function

DTCAP Router Function

Omni SCCP Router

Omni SCCP Router

SGU - CE1

SGU - CE2

41

DTCAP Router
Responsible for routing TCAP messages received
from the SS7 network to the appropriate DTCAP
Application.
Responsible for sending TCAP messages received
from the DTCAP Application to the SS7 network.
Responsible for flow control of messages in
conjunction with the DTCAP Application.

06/03/16

42

DTCAP Router - continued

Support graceful shutdown of DTCAP
Applications.

06/03/16

43

DTCAP Application
The DTCAP Application is the TCAP/IN protocol
entity.
It uses Omni TCAP library to support TCAP
protocol.
It can optionally use IN protocol libraries like
CAMEL, INAP, or WIN which in turn use the
TCAP library.

06/03/16

44

DTCAP Application - continued

CAMEL, INAP, WIN, or MAP user application
CAMEL, INAP, WIN, or MAP provider library
Omni TCAP library
DTCAP Protocol
06/03/16

45

DTCAP Application - continued

The DTCAP Application is a designatable Omni
process and can be in ACTIVE or STANDBY
state.
The STANDBY DTCAP Application does no
protocol processing and maintains a backup of
ACTIVE DTCAP Application information.

06/03/16

46

DTCAP Protocol
It is a proprietary protocol executed between a
SLU DTCAP Application and a SGU DTCAP
Router.
The DTCAP PDUs are carried between the SGU
and SLUs over UDP.
There is no protection against lost UDP messages
(same as current CCSNET). It is up to the upper
protocol layers to recover from lost messages.
06/03/16

47

DTCAP Protocol Overview

SLU 1
DTCAP
Application

Desinated
ACTIVE
DTCAP Router

SLU 2
DTCAP
Application

Designated
STANDBY
DTCAP Router

.
.
.

.
.
.

SLU 3
DTCAP
Application

Designated
IDLE
DTCAP Router

06/03/16

48

Generation of Transaction ID
Each INAP or CAMEL call is associated with a TCAP
transaction.
Each DTCAP Application is assigned a unique (across all
SLUs) 16 bit Application ID.
The TCAP library assigns a unique (within that DTCAP
Application)16 bit Dialog ID to identify a transaction.
The Application ID and Dialog ID are combined to
generate a 32 bit Transaction ID (TID) which uniquely
identifies a transaction.
06/03/16

49

Routing of TCAP messages

The incoming TCAP BEGIN message from the
network, which contains the InitialDP, is routed in
a round robin fashion taking application
congestion into account.
All other incoming TCAP messages from the
network contain the Transaction ID we generated
and the Application ID part of it is used to route to
the proper application.
There is no routing in the outgoing direction.
06/03/16

50

CAMEL SLU

06/03/16

51

CAMEL SLU Architecture

SLU

OPPS

TPPS

SLF

IPC (A1129)

IPC (A1129)

INA
(CAMEL, INAP, or WIN)

IPC (A1129)

TREATMENT

CALLC
IPF
UDP
(DTCAP)

CCS_TRANS
UDP
(CCSNET)

SGU

06/03/16

CCS

52

CAMEL SLU Architecture continued

IN Application interfaces directly with OPPS,
TPPS, and TREATMENT.
OPPS and TPPS register with INA to receive IN
calls.
INA in turn registers with TREATMENT to
receive all ISUP calls.
Except for Registration message, only A1129
messages are used on the interface to OPPS,
TPPS, and TREATMENT.
06/03/16

53

The SLF interface

Message exchanges with SLF applications use
A1129 ASN.1 encoded messages. The only
exception to this is the Registration message.
The SLF applications are not aware of the
underlying IPF architecture. They are not even
aware of the process they are registering with.
The registration function directs the registration
message to the proper IPF process.
06/03/16

54

The SLF interface support for IN

SLF application modified to support
CAMEL will continue to work at the binary
level in the Service Node mode.

06/03/16

55

SLF interface - changes

CallScenario added to A1129 message to
indicate application call scenario.

Continue continue call as dialed

Connect connect to specified called number
promptAndCollect - for pre-call announcement
promptAndCollectNoOutbound - for recharge and info
server

MaxCallDuration indicates maximum allowed

call duration.
06/03/16

56

CAMEL

06/03/16

57

GSM Classic Incoming Call

Home Network

HLR

2
Interrogating Network

Visited Network

3, 4
5

VLR
1

GMSC

1 Initial Address Message (ISUP)

2 Send Routing Info (MSISDN)

06/03/16

MSC

3
4
5
6
7

7
MS

Provide Roaming Number

Provide Roaming Number Ack (MSRN)
Send Routing Info Ack (MSRN)
Initial Address Message
Radio Signalling

58

GSM Incoming Call with

CAMEL
Home Network

HLR

2
Interrogating Network

gsmSCF

6
9

Visited Network

7, 8

5
VLR

gsmSSF
1

1
2
3
4

GMSC

Initial Address Message (ISUP)

Send Routing Info (MSISDN)
Send Routing Info Ack (T-CSI)
InitialDP (CalledPartyBCD, Service Key, ...)

06/03/16

10

MSC
5 Connect (CalledPartyNumber)
6 Send Routing Info (T-suppress)
7 Provide Roaming Number
8 Provide Roaming Number Ack (MSRN)
9 Send Routing Info Ack (MSRN)
10 Initial Address Message
11 Radio Signalling

11
MS

59

CAMEL messages
Based on GSM 09.78: Digital cellular
telecommunications system (Phase 2+); Customized
Applications for Mobile network Enhanced Logic
(CAMEL Phase 2); version 6.3.0 Release 1997
ActivityTest
ApplyCharging
ApplyChargingReport
Connect
Continue
06/03/16

60

CAMEL messages - continued

DisconnectForwardConnection
EstablishTemporaryConnection
EventReportBCSM
InitialDP
ReleaseCall
RequestReportBCSMEvent
ResetTimer
06/03/16

61

Call Scenarios

06/03/16

62

InitialDP
Direction: gsmSSF to gsmSCF
This operation is used to request the gsmSCF for
instructions to complete the call
Some parameters:

Called Party Number or Called Party BCD Number

Calling Party Number
Location Number
Location Information
EventTypeBCSM (identifies mobile originated or mobile
terminated)

06/03/16

63

RequestReportBCSM
Direction: gsmSCF to gsmSSF
This operation is used to request the gsmSSF to monitor
for call related events and send a notification back to the
gsmSCF
Possible events:

Answer
Abandon
NoAnswer
Busy
Disconnect leg1 (calling party)
Disconnect leg2 (called party)

06/03/16

64

ApplyCharging
Direction: gsmSCF to gsmSSF
This operation allows control of call
duration
Some parameters:

maxCallPeriodDuration
releaseIfDurationExceeded
Tone play warning tone before release
partyToCharge
06/03/16

65

Continue
Direction: gsmSCF to gsmSSF
This operation is used to request gsmSSF to
proceed with previously suspended call
processing
The gsmSSF continues call processing
without substituting new data from gsmSCF
No parameters
06/03/16

66

Connect
Direction: gsmSCF to gsmSSF
This operation is used to request gsmSSF to
perform call processing functions to route a
call to a specified destination (called party
number)
Some parameters:
destinationRoutingAddress
06/03/16

67

EventReportBCSM
Direction: gsmSSF to gsmSCF
This operation is used to notify the gsmSCF
of a call related event previously requested
by the gsmSCF in a
RequestReportBCSMEvent operation.
Parameters:
eventTypeBCSM
06/03/16

68

ApplyChargingReport
Direction: gsmSSF to gsmSCF
This operation is used by the gsmSSF to
report charging related information to the
gsmSCF, as requested by the gsmSCF using
ApplyCharging operation.

06/03/16

69

ReleaseCall
Direction: gsmSCF to gsmSSF
Used to tear down by the gsmSCF an
existing call at any phase of the call for all
parties involved in the call
Parameters:
Release Cause

06/03/16

70

EstablishTemporaryConnection
Direction: gsmSCF to gsmSSF
Used to establish a connection between the
gsmSSF and IP (MMU) using ISUP

06/03/16

71

DisconnectForwardConnection
Direction: gsmSCF to gsmSSF
Disconnect the connection established using
EstablishTemporaryConnection

06/03/16

72

ActivityTest
Direction: gsmSCF to gsmSSF
Used to check for the continued existence
of a relationship between the gsmSCF and
gsmSSF
If no reply is received, the transaction will
be terminated by the gsmSCF

06/03/16

73

ResetTimer
Direction: gsmSCF to gsmSSF
This operation is used to avoid a time-out at
the gsmSSF

06/03/16

74

SSP

CAP Library

INA

OPPS

BEGIN
Invoke (InitialDP (collectedInfo))

OPEN_IND
OPEN_RSP (accepted)
InitialDP Ind (collectedInfo)
DELIMITER_IND
RequestReportBCSMEvent Req

PI (CRN_I)
SITR (0, CRN_I, IPStayOnLine = TRUE,
continue, MaxCallDuration)

ApplyCharging (MaxCallDuration) Req

Continue Req
DELIMITER_REQ
CONTINUE

SIFR (CRN_O, CRN_I, informationalMessage)

Invoke (RequestReportBCSMEvent)
Invoke (ApplyCharging (MaxCallDuration))
Invoke (Continue)

SIFR (CRN_O, normal)

CONTINUE
Invoke (EventReportBCSM (oAnswer))

EventReportBCSM Ind (oAnswer)

DELIMITER_IND

SIFR (CRN_O, answered)

ActivityTest Req
DELIMITER_REQ
CONTINUE
Invoke (ActivityTest)
CONTINUE
Result (ActivityTest)

ActivityTest Cnf
DELIMITER_IND

CONTINUE
Invoke (EventReportBCSM (oDisconnect, leg1))

EventReportBCSM Ind (oDisconnect, leg1)

DELIMITER_IND

CONTINUE
Invoke (ApplyChargingReport)

RC (CRN_I)
RC (CRN_O)

ApplyChargingReport Ind
DELIMITER_IND
CLOSE_REQ

END

06/03/16

1a. OPPS - Normal Termination - A-party disconnects

75

SSP

CCS(ISUP)

IPF/SN

INA

SLF/OPPS

BEGIN
Inv oke(InitialDP(collectedInf o))

PI (CRN_I)
CITR (CRN_I, IPStay OnLine=TRUE,
Prompt&Collect

CONTINUE
Inv oke(RequestReportBCSMEv ent)
Inv oke(EstablishTemporry Connection
(Destination = IVR_NUMBERdddd))
IAM
IncomingcalltoIVR/MMU

SETUP_IND
PI (CRN_T)
CITR (CRN_T, IPStay OnLine=TRUE,
Prompt&Collect)
ALERT_REQ

ACM
SETUP_RESP
ANM
(IVR Session)
CIFR (CRN_T, Prompt&Collect result)
CIFR (CRN_I, Prompt&Collect result)

CITR (CRN_T, IPStay OnLine=TRUE,

Prompt&Collect)

CITR (CRN_I, IPStay OnLine=TRUE,

Prompt&Collect)

CIFR (CRN_T, Prompt&Collect result)

CIFR (CRN_I, Prompt&Collect result)

CRE(CRN_I)
END
Inv oke(DisconnectForwardConnection)
Inv oke(ReleaseCall)

CRE(CRN_T)
RC (CRN_I)

RELEASE_REQ
RC (CRN_T)

REL
RLC
RELEASE_CONF

Note: The SGU is the gatew ay

for all CAMEL messages.

06/03/16

13a - Call to Recharge or Adm in Server - IP disconnects

76

CAMEL - What is different?

CAMEL is a Service Control Protocol
Unlike ISUP, which is a Call Control Protocol,
there are no associated voice circuits
The following features are not supported in
CAMEL
No TPPS pre-call announcements
No mid-call beep or announcements
These will result in a fake response from INA, to keep
OPPS/TPPS happy
06/03/16

77

INA Configuration
The following items are specified using
MML commands, and saved in
db.IP.ina.202.pri:
SGU CE Names and SGU UDP Port
Number
Local UDP Port Number
SubSystem Number (SSN)
CAMEL is 146
06/03/16

78

INA Configuration - continued

SLU ID
Identifies SLU. Used as MSB of Local
Transaction ID.

ENTITY ID
Identifies Application Entity within a SLU.
Next to MSB of Local Transaction ID.

06/03/16

79

INA Configuration - continued

IP_ADDRESS
Phone number for routing call to our MMU.
This number and a four digit suffix (DialogID)
identifying the call is used as the destination
address in the EstablishTemporaryConnection.
This number is passed back to us as the Called
Number in the incoming ISUP call.
The four digit suffix allows us to correlate the
CAMEL and ISUP calls.
06/03/16

80

INA Configuration - continued

NUMBER_MODIFIER
Number normalization script used only in the
incoming direction to modify Calling Party and
Called Party Numbers.

06/03/16

81

INA Command Line Options

max_transactions <number>
Normally set to 3000

trace
Enables capomd trace

dbg_mask
Default is 1

06/03/16

82