CCS Associated

CCS Quasi associated

CCS Non associated.
TELECOM BASICS
CCS STRUCTURE
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
Voice Theorm
a) Voice Frequency ~ 300 to 3300 Hz , bandwidth = 4000 Hz
b) Nyquist theorm = Min 8000 sampling rate reqd ( 4000*2 )
c) One Sample = 8 bits ( Reprsntation of 256 Voice Levels , 2 pow 8 =
256)
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
E1 Physical Interface
a) 0th TS used for synchronization ( 0011011)
b) Modes of Operation
1. Unframed - No TS at all
2. Framed - All 32 TS used for data
3.Multiframe - 0 TS for sync, rest 31 for data
c) Bit '1' - 3V , Bit '0' - 0~0.3 V
CAS ( Channel Associated Signalling )
a) Uses INBAND Signalling ( Voice frequencies )
b) Signaliing Associated in that E1 only - TS = 16 Line Sig. And TS=All Registered
Signalling
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 STATUS
10XX 10XX IDLE
00XX 10XX SIEZ
00XX 11XX SIEZ ACK
00XX 01XX ANS
00XX 11XX B PARTY REL
10XX 0/10XX A PARTY REL

Ist Frame : TS-1 & TS-17 (4+4 bits)
IInd Frame : TS-2 & TS-18
....
....
15th Frame : TS-15 & TS-31
CAS Registered Signalling
a) Uses voice TS for Registered Signalling .
b) Types : DECADIC , DTMF , R2 Semi C , R2Fully
C
c) R2MF - R2 Multi Freq Fully Compled (Ack Reqd)
CAS Registered Signalling
Grp A Bwd Sig. Grp B Bwd Sig.
1 Send Next Dig. 2 Changed No.
2 Restart 3 Called Line Busy
3 Change over grp B 4 Congestion
4 CLI 5 Unallocated No.
5 Send Cat of A Party 6 Normal subs free
6 Switch to speech
7 Send last but 2 digits
8 Send last but 3 digits
9 Send last but 1 digit
Grp 1 Fwd Sig. Grp II Fwd Sig.
1 Digit '1' 1 Ordinary Subs
2 Digit '2' 2 Priority Subs
3 Digit '3' 5 Operator
4 Digit '4' 6 STD Coin Box

8 7 1 7 1 6 2 8
Layer#2 FLAG BSN BIB FSN FIB LI SPARE DATA CRC
Layer#3
DPC OPC
CIC (only
ISUP)
ISUP Message Type Optional FIX
IAM
Optional Variable Mandatory Variable
SubService Field Service Indicator
Priority - 1,2,3
( Low to High )
Network Indicator
NAT0/1, INAT0/1
SLS ( 4
Bits , Max
16
Selection )
SIO SIF
Mandatory FIX
A Party Category , Forward Call Indicator B Party No , User service Info
USER PART
CLI , Carrier , NW , HOPs
CCS 7 Layers
0 FISU
1-2 LSSU
3-63 MSU
Layer-2 : CRC , Retransmission ( PCR ) , Error Correction and detection Etc
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
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 )
ISUP Message Type :
IAM ( Initial Address Message )
INR ( Information Request )
ACM ( Address Complete )
ANM ( Answer Message )
REL ( Release Message )
RLC ( Release Complete )
BLO ( Blocking )
UBL ( Uublocking )
BLA ( Blocking Acknowledment )
CPG ( Call Progress )
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.
SCCP Message Type Optional FIX
UDT
XUDT
UDTs
XUDTs
Used to transport user data and
SCCP management messages in the
connection-less mode. It can
Segment / DeSegment data as per
its size
Used to indicate to the originating
SCCP user that a UDT message
cannot be delivered to the specified
destination. The data field of the
UDT message and the reason for the
return are included in the UDTS
message.
Used for Mandatory FIX
1. Called Party
2. Calling Party
3. User Data
Mandatory Variable
1. Called Party
2. Calling Party
3. User Data
1. Return Cause
2. Hop Counter
1. Called Party
2. Calling Party
3. User Data
1. Segmentation data
Optional Variable
1. Called Party
2. Calling Party
3. User Data
1. Return Cause
2. Hop Counter
1. Segmentation data
Protocol Class :
Class -0 : Basic Connectionless ( Non Critical,
TCAP )
Class -1 : Sequenced Connectionless (Critical
, TCAP )
Class -2 : Basic Connection Oriented (
BSSAP )
Calling / Called party :
1. Address Indicator :
a. Routing Indicator : GT based or ( DPC + SSN )
b. GTT Indicator : No GT or GT - 1 or 2 or 3 or 4
c. SSN Indicator : Present / Not Present
d. Point Code Indicator : Present / Not Present

2. Address :
a. Point Code
b. SSN


c. GT - 1 :
i. Nature of Address Ind : Subscriber Number / National Sig. No. / International No.
ii. Odd / Even Indicator ( Spr) iii. Address Information ( 919839212499 )
d. GT - 2 :
i. Translation Type ii. Address Information ( 919839212499 )
e. GT - 3 :
i. Translation Type ii. Encoing Scheme - Unknown / BCD Odd / BCD Even
iv. Address Information iii Numbering Plan - ISDN / Telephony / Data / Telex / Land Mobile / Mobile
e. GT - 4 :
i. Translation Type ii. Encoing Scheme - Unknown / BCD Odd / BCD Even
iii. Numbering Plan iv. Nature of Address Indicator
v. Address Information ( Contains Address for Example : 919839212499 )
User Data :
1. Length Indicator
2. User Data Ex: TCAP etc
Connection Oriented
- Only used in BSSAP where heavy data transfer is required for ex. Between MSC/VLR to BSC to BTS
SCCP - Routing Protocol
Hop Counter ( 15 to 1 ) : Counter is decremented upon GTT
Segmentation : Max 16 Segments , each carries 246 bytes

GTT CASES
1. SPC + SSN
2. SPC + SSN + GT
3. SSN + GT
4. SPC + GT
5. GT only

GT is performed on given SPC + SSN on the basis of GT info , to find out
the final A/B Party Address
SSN
1 SCCP Management
3 ISDN user part
4 OMAP (Operation, Maintenance and Administration Part)
5 MAP (Mobile Application Part)
6 HLR (Home Location Register)
7 VLR (Visitor Location Register)
8 MSC (Mobile Switching center)
9 EIR (Equipment Identifier register)
10 AUC (Authentication Centre)
11 ISDN Supplementary Services (SSAP)
13 Broadband ISDN edge-to-edge applications
254 Base Station System Application Part (BSSAP)
SCMG Functions
- Signaling point status management : Failure, recovery, and congestion information of
signaling
points, provided by MTP

- Subsystem status management : Subsystem failure and recovery information, and SCCP
(SSN 1)
congestion received in SCCP management messages.

- Subsystem status test : SSP , SSA , SST , SOR , SOG
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) Numbering plan (NP) Nature of address (NA) Global title digits (GTDIG)

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

Message type Function
Abort
Used to terminate the structured dialogue in a normal way
Used to terminate the structured dialogue in an off normal way.
Indicates that one of the Invoke, Return Result, or Return Error components received from the remote user/CSL could not be understood or was not expected.
Used to transport data in an unstructured dialogue
First message, to start a structured dialogue, sent once
Used to sustain the structured dialogue, more continue messages can be sent
Initiates/invokes a desired operation at the remote peer application entity. Invoke
Return result not last
Return result last
Return error
Begin
Continue
Used to carry a segment of the result of a successfully completed operation. It is used when a success reply is physically too large to fit into a single message.
Represents the final success reply to an operation invocation. If the success reply was segmented, this component would represent the final segment of the reply
Indicates an operation invoked previously has failed due to some processing error. Error codes are supplied by TCAP users, and are passed transparently by TCAP.
Unidirectional
TRANSACTION DIALOG TAG COMPONENT TAG
End
Reject
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..........
Functions of TCAP are to control:
The transaction between both endpoints in the network
The communication to the users of TCAP.
SMSC
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

3. MO Forward SM : A party MS to SMSC ( Forward Short Message Submit )
4. MT Forward SM : SMSC to B Party MS ( Forward Short Message Deliver )



HLR
GMS
MSC/VLR
TCAP Begin/Invoke - SRI for SM
TCAP End / Retrun Res - SRI Ack
SM_DELIVER
TCAP Begin/Invoke - Forward SM
TCAP End / Retrun Res - Forward SM Ack
SCP
SCP
STP
STP
STP
STP
SSP (Service Switching Pt )
A-
A-Access
A-
E-Extended
C-Cross D-
B-Bridge
Other STP NW
Service Control Pt C-Cross
VLR
V
BTS
GMSC
HLR
AUC-SIM
M
SMSC EIR
E C
G
B
H
F
D D
A
HLR
GM MSC/VLR
TCAP Begin/Invoke - Provide MSRN
TCAP End / Retrun Res - MSRN Ack TCAP Begin/Invoke - SRI
TCAP End / Retrun Res - SRI
IAM -
IAM - MSISDN
BTS
IMSI
IMEI
Mobile Terminating Call ( MTC )
GSM
C7 Network
GPRS ( General Packet Radio Services )
a) Key Features
Speed immediacy
New applications
Better applications
Service access

b) Key Network Features of GPRS
Packet switching
Spectrum efficiency
Internet aware
Supports tdma and gsm

c) Limitations of GPRS
Limited cell capacity for all users
Speeds much lower in reality
Support of gprs mobile terminate by terminals is not ensured
Suboptimal modulation
Transit delays
No store and forward

d) SGSN - Serving GPRS Support Node
handles session management, mobility management, billing and traffic measurements
bit level encryption of data which is to be sent over the air interface.
Put GPRS data received from the BSC in IP format for sending to the GGSN and vice-versa.
Provide GPRS routing to BSCs

d) GGSN - GPRS Gateway Support Node
The GGSN is the gateway in and out of the GPRS system.
It routes packets from an external network ( "the Internet" ) to the SGSN which is currently serving the MS,
and routes packets from the SGSNs to which it is connected to the external network. This concept is called tunnelling.

d) Similar Techniques
Enhanced Data rates for GSM Evolution (EDGE)
Universal Mobile Telephone System (UMTS)
FLAG
BSN
BIB
FIB
FSN
LI
SIO
SIF
SPARE USER DATA
CRC SLS
MTP - 2 LAYER 3 SCCP TCAP
A PARTY - GT(N) /
USER DATA
DIALOG ID
COMPONENT TYPE = INVOKE
COMPONENT USER DATA , MT Forward SM ,
MSIN DIGIT
DPC
OPC
TRANSACTION ID , BEGIN
UDT MESSAGE
PROTOCOL CLASS =
B PARTY - GT(N) /
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) ]
VLR
VLR
BTS
HLR
AUC-
MSC
SMSC
E C
G
B
H
F
D D
A
IMSI
IMEI
GSM Overview
IMSI Vs TMSI
One can't take hacking benefits with TMSI as it is dyanmically allocated by VLR
, moreover TMSI is 4 octet shorter than 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
MAP E ( GMSC - MSC )
Process access sigmnalling CCS 7
Forward access Signalling CCS 7
Send End Signal CCS 7
Perform Handovers / Subsequent HO
Perform Internal Handovers
Trace subs activity
MAP I ( Subservices - MSC )
Get Pwd / Register Pwd
Activate / Deactivate / Erase / Register SS
Interrogate / Invoke SS
Forward SS Notification
MAP F ( EIR - MSC )
Check IMEI
MAP H ( SMSC - MSC )
Forward Short Message
MAP G ( VLR - VLR )
Send Param
Intelligent Network ( IN )
Requirement / Advantages
Rapid deployment of Vendor / SSP Free Services which are centrally administered



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
TELECOM BASICS
CCS STRUCTURE
b) Erlang = Busy time for ckts / Avl Time for measurment , Ex : 20/60 = 3Er
286 Er 20 - 592
439 Er 30 - 901
a) Uses TS = 16 for indication of ckt. Status only ( I.e.
FREE , SIEZ , FREE BY A/B , BUSY etc.)
STATUS
00XX 11XX SIEZ ACK
00XX 11XX B PARTY REL
10XX 0/10XX A PARTY REL
17 (4+4 bits)
CCS 7 Layers
Traffic / Sharing / Overloading Routing

BLA ( Blocking Acknowledment )
sequencing on changeover .5 to 1.2 sec.
sequencing on changeback .5 to 1.2 sec.
Used to transport user data and
SCCP management messages in the
connection-less mode. It can
Segment / DeSegment data as per
its size
Used to indicate to the originating
SCCP user that a UDT message
cannot be delivered to the specified
destination. The data field of the
UDT message and the reason for the
return are included in the UDTS
message.
Used for
SCPs can be combined to form a subsystem service group that is accessed from
Function
Used to terminate the structured dialogue in a normal way
Used to terminate the structured dialogue in an off normal way.
Indicates that one of the Invoke, Return Result, or Return Error components received from the remote user/CSL could not be understood or was not expected.
Used to transport data in an unstructured dialogue
First message, to start a structured dialogue, sent once
Used to sustain the structured dialogue, more continue messages can be sent
Initiates/invokes a desired operation at the remote peer application entity.
Used to carry a segment of the result of a successfully completed operation. It is used when a success reply is physically too large to fit into a single message.
Represents the final success reply to an operation invocation. If the success reply was segmented, this component would represent the final segment of the reply
Indicates an operation invoked previously has failed due to some processing error. Error codes are supplied by TCAP users, and are passed transparently by TCAP.
The transaction between both endpoints in the network
The communication to the users of TCAP.

BTS

GMSC
EIR
IMEI
SMS
FLAG UDT MESSAGE
BSN PROTOCOL CLASS = 0 / 1
BIB B PARTY - GT(N) / SSN / SUB NO
FIB A PARTY - GT(N) / SSN / SUB NO
FSN
LI
SIO
SIF
SPARE
USER
DATA
CRC SLS
MTP - 2 LAYER 3 SCCP TCAP
USER DATA
DPC
OPC
TRANSACTION ID ,
BEGIN
DIALOG ID
COMPONENT
TYPE = INVOKE
COMPONENT
USER DATA ,
MT Forward SM ,
MSIN DIGIT
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
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
Conditions for error free transmission
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
When the number of errors increase the threshold limit then the link is taken out of service.
Conditions for error free transmission