SS7 Signaling Basic
SS7 Signaling Basic
E1
a) 256 bytes per frame
b) 8 bits Each TS in E1 Frame
c) 0.125uS time taken by one frame
d) Total 8000 frames in One Second
Erlang
Voice Theorm
a) Unit of Traffic descibes total traffic volume in one hour
a) Voice Frequency ~ 300 to 3300 Hz , bandwidth = 4000 Hz
b) Erlang = Busy time for ckts / Avl Time for measurment , Ex : 20/60 = 3Er
b) Nyquist theorm = Min 8000 sampling rate reqd ( 4000*2 )
15ckt - 8.1 Er 31ckt - 21.5 Er 3 E1 - 77 Er 10 E1 - 286 Er 20 - 592
c) One Sample = 8 bits ( Reprsntation of 256 Voice Levels , 2 pow 8 =
30ckt - 20.3 Er 02 E1 - 48 Er 5 E1 - 136 15 E1 - 439 Er 30 - 901
256)
d) 8000 samples in One Sec = 8 bits * 8000 = 64000 bits per sec required
E1 Physical Interface
CAS ( Channel Associated Signalling )
CAS Line Signalling
a) 0th TS used for synchronization ( 0011011)
a) Uses INBAND Signalling ( Voice frequencies )
a) Uses TS = 16 for indication of ckt. Status only ( I.e.
b) Modes of Operation
b) Signaliing Associated in that E1 only - TS = 16 Line Sig. And TS=All Registered Signalling FREE , SIEZ , FREE BY A/B , BUSY etc.)
1. Unframed - No TS at all
2. Framed - All 32 TS used for data
ABCD Fwd ABCD Bckwd STATUS
3.Multiframe - 0 TS for sync, rest 31 for data
10XX
10XX
IDLE
CAS Registered Signalling
c) Bit '1' - 3V , Bit '0' - 0~0.3 V
00XX
10XX
SIEZ
Grp A Bwd Sig.
Grp B Bwd Sig.
00XX
11XX
SIEZ ACK
1 Send Next Dig.
2 Changed No.
00XX
01XX
ANS
CAS Registered Signalling
2 Restart
3 Called Line Busy
00XX
11XX
B PARTY REL
a) Uses voice TS for Registered Signalling .
3 Change over grp B
4 Congestion
10XX
0/10XX
A PARTY REL
b) Types : DECADIC , DTMF , R2 Semi C , R2Fully C 4 CLI
5 Unallocated No.
c) R2MF - R2 Multi Freq Fully Compled (Ack Reqd)
5 Send Cat of A Party
6 Normal subs free
Ist Frame : TS-1 & TS-17 (4+4 bits)
d) MF - Combination of 2 Freq to represent one info
6 Switch to speech
IInd Frame : TS-2 & TS-18
7 Send last but 2 digits
....
Grp 1 Fwd Sig.
Grp II Fwd Sig.
....
8 Send last but 3 digits
1 Digit '1'
1 Ordinary Subs
15th Frame : TS-15 & TS-31
9 Send last but 1 digit
2 Digit '2'
2 Priority Subs
3 Digit '3'
5 Operator
4 Digit '4'
6 STD Coin Box
CCS Associated
CCS STRUCTURE
CCS 7 Layers
Layer#2
FLAG
BSN
BIB
FSN
FIB
LI SPARE
DATA
Layer-3 :
b. Signalling Route Management - Traffic / Sharing / Overloading Routing
c. Signalling Link Management - Control / Monitor / Status of Links
e Signalling Traffic Management - Change over/ Back in case of Fail
e. Alignment - SIO , SIN , SIE , SIOS
f. Message Distribution - Distributing the MSG to ISUP , SCCP
g. Message Discrimination - Mine or Other DPC / NW
h. Message Routing - Linkset / DPC findout from Routing Table
0 FISU
1-2 LSSU
3-63 MSU
Layer#3
SIF
SIO
SubService Field
Network Indicator
NAT0/1, INAT0/1
DPC
ISUP
OPC
Service Indicator
Priority - 1,2,3
( Low to High )
SLS ( 4
Bits , Max
16
Selection )
Signalling
Link
Selection
CIC (only
ISUP)
CRC
USER PART
Message Type
Mandatory FIX
Mandatory Variable
IAM
Service Indicator
0 - SNM ( Signalling NW Management Message )
1 - MTN ( Mtc Regular Msg )
2 - MTNs ( Mtc Special Message )
3 - SCCP ( Carry Non-Voice Traffic Ex: SMS )
4 - TUP
5 - ISUP ( Voice related traffic )
6 - Data User Part ( Call & ckt Related )
7 - Data User part ( Facility Regn & Cancellation )
Layer-3 Timers
T1 Delay to avoid message mis-sequencing on changeover .5 to 1.2 sec.
T2 Wait for changeover Ack .7 to 2. 0 sec
T3 Delay to avoid message mis-sequencing on changeback .5 to 1.2 sec.
T4 Wait for changeback Ack (1st attempt) 5 to 1.2 sec.
T5 Wait for changeback Ack (2nd attempt) 5 to 1.2 sec.
Optional FIX
Optional Variable
SCCP
Message Type
UDT
XUDT
UDTs
XUDTs
Mandatory FIX
Mandatory Variable
Protocol Class :
1. Called Party
Class -0 : Basic Connectionless ( Non Critical, 2. Calling Party
TCAP )
3. User Data
Class -1 : Sequenced Connectionless (Critical
, TCAP )
1. Called Party
Class -2 : Basic Connection Oriented
2. Calling Party
( BSSAP )
3. User Data
Class -3 : Flow Control Connection Oriented
(BSSAP )
1. Called Party
1.
Return
Class
-4 : Cause
Flow Control + Err Recovery
2. Calling Party
2.
Hop Counter
Connection
Ori.
3. User Data
1. Return Cause
2. Hop Counter
1. Called Party
2. Calling Party
3. User Data
Connection Oriented
- Only used in BSSAP where heavy data transfer is required for ex. Between MSC/VLR to BSC to BTS
Optional FIX
Optional Variable
User Data :
1. Length Indicator
2. User Data Ex: TCAP etc
1. Segmentation data
1. Segmentation data
Used for
GTT
> Method of hiding the SS7 point code and sub-system number from the originator of a message
a) GT Consists of
Translation type (TT)
b) GT Benefits
Central administration of routing information makes it easier to restructure the network
It is possible to set up alternative routing schemes and load sharing
More compact and dyanmic routing tables
The function is required for the introduction of certain new services (such as call completion to busy subscriber, CCBS and 800 free phone)
a) The result of a global title translation can be:
the point code for a signaling destination
a subsystem service group ( this is used in the intelligent network to guarantee a fail-safe service control point (SCP). Two SCPs can be combined to form a subsystem service group that is accessed from
the relevant service switching point (SSP) via global title translation. )
a translator service group ( this consists of up to four signaling points, each of which can perform the necessary translation )
a further translation in the same network node
TRANSACTION
DIALOG TAG
COMPONENT TAG
TCAP :
1. Transaction Part : ( Deals with SCCP Message )
a. TCAP Message Type : BEGIN / UNI / END / CONTINUE / ABORT
b. Length Indicatior of Transaction Tag ( Max 2048 , SCCP takes Care of Segmenting / Breaking )
c. Transaction Info ( Not Valid for UNI )
i. Origination Transaction Id ( Mandatory for BEGIN , CONTINUE )
- Length Indicator & Value
i. Destination Transaction Id ( Mandatory for END , ABORT , CONTINUE )
- Length Indicator & Value
i. P_Abort Cause ( Mandatory for TC_P_Abort Request )
- Reason for Abort
2. Dialog Part :
a. Dialog Indicator Tag
b. Length Indicatior of Dialog Tag
c. Dialog Information - Depend on USER For Ex : MAP , INAP
3. Message Component Part : ( Deals with USERs such as MAP , INAP ...)
a. Component Indicator Tag
b. Length Indicatior of Component Tag
c.Component Type : ( Invoke / Return Result Last / Return Result Not Last / Return Error / Reject )
d. Component length
e. Component User Information by MAP , INAP , CAMEL , OMAP , SSAP Etc..........
Message type
Invoke
Return result not last
Return result last
Return error
Reject
Unidirectional
Begin
Continue
End
Abort
Function
SMSC
HLR
1. SMS are stored in SMSC before they can be sent to MS ( 140 bytes each SMS )
2. MAP USED is
> Forward Short Message Submit
> Send Routing Info for SM
> Forward Short Message Deliver
MSC/VLR
BTS
BTS
VLR
D
V
L
R
C
HLR
IMSI
AUC-SIM
B
M
S
C
GSM
Overview
GMSC
IMEI
EIR
SMSC
HLR
GM
SC
STP
STP
A-Access
C-Cross
Service Control Pt
SCP
BTS
IAM MSISDN
SCP
MSC/VLR
DDiag
onal
C-Cross
STP
AAcce
ss
AAcces
s
B-Bridge
STP
E-Extended
C7 Network
Other STP NW
FLAG
BSN
BIB
FIB
FSN
LI
SIO
SIF
SPARE
CRC
USER DATA
SLS
MTP - 2
LAYER 3
DPC
UDT MESSAGE
PROTOCOL CLASS =
0 /-1GT(N) /
B PARTY
SSN /- SUB
NO
A PARTY
GT(N)
/ SSN
/ SUB NO
TRANSACTION ID , BEGIN
DIALOG ID
COMPONENT TYPE = INVOKE
OPC
USER DATA
COMPONENT USER DATA ,
MSIN DIGIT
SCCP
MT Forward SM ,
TCAP
GSM Overview
IMSI : International Mobile Subs Identity [ SIM , MCC(3) + MNC(2) + MSISDN
(<10) ]
TMSI : Temporary Mobile Subs Identity [ VLR , MCC(3) + MNC(2) + MSISDN
(<10) ]
MSISDN : Mobile Stn Integrated Services Digital NW [ CC(1-3) + NDC(1-3) +
MDN(10) ]
MSRN : Mobile Subs Roaming Number [ VLR , CC(1-3) + NDC(1-3) + MDN(10) ]
IMSI :Vs
TMSI
IMEI
International
Mobile Eqpt. Identity [ By Nokia ]
One: can't
takeArea
hacking
benefits
with TMSI
as it is+dyanmically
LAI
Location
Identifier
[ MCC(3)
+ MNC(2)
LAC(<10) ] allocated by VLR ,
moreover TMSI is 4 octet shorter than IMSI .
VLR
D
IMSI
MAP D ( HLR-VLR )
Provide MSRN / MSRN Ack
Update Location / Cancel Location / Ack
Insert / Delete Subs Data / Ack
Send Param / Ack
Reset
Deregister Mobile Data
Note MS Present
MAP C ( HLR-MSC )
Send Routing info SRI /
Ack
Send Routing info for
SM / Ack
Set Message waiting
data
Alert Service Centre
Regisster charging info
HLR
SSP
CCF - Call Control Functions ( Takes Care of all call related processing in Switch )
SSF - Service Switching functions ( Provides IN Triggering and IN Accessibility )
SRF - Specialized resource function ( Provides interactioon bw Call processing SW
in SSP)
SCP
SCF - Service Control Functions ( Executes IN service logic and interfaces witrh
SSP via SSF )
SDF - Service data function ( Maintains all customer and nw data )
SMP - Service Management Point ( Administration and Operation of IN )
SIB - Service Independ Service Blocks ( Generic purpose reusable software codes
in IN )
BCP - Basic Call Process
SCEP - Service Environment creation function ( Allows sevices in IN to be defined ,
tested ... )
VLR
AUCSIM
Intelligent Network ( IN )
Requirement / Advantages
Rapid deployment of Vendor / SSP Free Services which are centrally administered
BTS
MSC
F
GSM Overview
H
SMSC
MAP I ( Subservices - MSC )
Get Pwd / Register Pwd
Activate / Deactivate / Erase / Register SS
Interrogate / Invoke SS
Forward SS Notification
GMSC
IMEI
EIR
Erlang
a) Unit of Traffic descibes total traffic volume in one hour
b) Erlang = Busy time for ckts / Avl Time for measurment , Ex : 20/60 = 3Er
15ckt - 8.1 Er 31ckt - 21.5 Er 3 E1 - 77 Er 10 E1 - 286 Er 20 - 592
30ckt - 20.3 Er 02 E1 - 48 Er 5 E1 - 136 15 E1 - 439 Er 30 - 901
CAS Line Signalling
a) Uses TS = 16 for indication of ckt. Status only ( I.e.
FREE , SIEZ , FREE BY A/B , BUSY etc.)
ABCD Fwd ABCD Bckwd
10XX
10XX
00XX
10XX
00XX
11XX
00XX
01XX
00XX
11XX
10XX
0/10XX
STATUS
IDLE
SIEZ
SIEZ ACK
ANS
B PARTY REL
A PARTY REL
s (GTDIG)
e control point (SCP). Two SCPs can be combined to form a subsystem service group that is accessed from
r application entity.
completed operation. It is used when a success reply is physically too large to fit into a single message.
ocation. If the success reply was segmented, this component would represent the final segment of the reply
ue to some processing error. Error codes are supplied by TCAP users, and are passed transparently by TCAP.
urn Error components received from the remote user/CSL could not be understood or was not expected.
e
e messages can be sent
way
mal way.
versa.
GMSC
SMS
FLAG
BSN
BIB
FIB
FSN
LI
SIO
SIF
DPC
USER DATA
CRC
MTP - 2
LAYER 3
TRANSACTION ID ,
BEGIN
DIALOG ID
COMPONENT
TYPE = INVOKE
OPC
USER
DATA
SLS
SPARE
UDT MESSAGE
PROTOCOL CLASS = 0 / 1
B PARTY - GT(N) / SSN / SUB NO
A PARTY - GT(N) / SSN / SUB NO
SCCP
COMPONENT
USER DATA ,
MT Forward SM ,
MSIN DIGIT
TCAP
Some Useful Definitions:PROTOCOL:- It is a set of rules governing the way, the data will be Tx and Rx over the data communication network.
Protocls must provide reliable, error free transmission of user data as well as network managament functions.
PRIMITIVE:- A primitive is an interface which provides access from one level of protocol to another level of protocol.
In the case of Dbase, the Dbase is considered as an application entity and the protocol used to acccess and interface
to this application is TCAP.
CIC:- It is of 16 bits of which 4 bits are spare
MTP-2 Functionalities
1) S.U. Delimination..
Flag01111110 Correct start and end of SU If not bit insertion is used.
ie No " 1s density " violation should be there. If its there then Bit stuffig is used.
2)S.U. Alignment
SU should be received in sequence
SU must be a multiple of 8
Conditions for error free transmission
SIF of MSU should not exceed 272 octet capacity
SUERM: Signalling unit error rate monitor
Counter used to check the max number of errors on a 64Kbps SDL
Each link keeps its unique couter
When the number of errors increase the threshold limit then the link is taken out of service.
Error due to clock signals being not synchronised prperly at Tx and Rx
L-3 ( Realigns the Link, by taking the link out of service)
L-2 (Reports any error to L-3 link Mgmnt)
This phenomena is called the"Alignment Procedure" phenomena
or free transmission