Pubate Satienpoch: SCCP: Signaling Connection Control Part

1 2005 Nokia V1-Filename.
ppt / yyyy-mm-dd / Initials

Company Confidential
SCCP
Pubate Satienpoch
2 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
SCCP : Signaling Connection Control Part
Provides additional function to MTP to cater for both connectionless and
connection oriented network service
to transfer non circuit related signaling information between exchanges in
telecommunication network
Provide the means for
Control logical signaling connection( setup/ release) within SS7 network
A transfer capability for network service data units with or without the use of
logical signaling connection
Provides routing function which allows signaling message to be routed to a
signaling point based on, eg., dialed digits
Combination of MTP and SCCP is call Network Service Part
SS7 protocol stack
MTP
SCCP
TCAP RANAP/
BSSAP TUP/
ISUP
MAP/ CAP
SS7 & OSI reference model
Physical layer
Data link layer
Network layer
Transport layer
Session layer
Presentation layer
Application layer
MTP (levels 1-3)
User Part
(Common part)
(PSTN, ISDN,
GSM)
User Part
OSI Reference Model Common Channel Signalling No. 7
Application Part
(GSM/UMTS
specific part)
SCCP
Layer
1
2
3
4
5
6
7
Level
1
2
3
4
SCCP services
Basic
Connectionless
Service
Sequenced
Connectionless
Service
Basic
Connection-
oriented
Service
Flow Control
Connection-
oriented
Service
Connectionless
Services
Connection-oriented
Services
0 1 2 3
Services provided by the SCCP
Protocol
Class
SCCP Connectionless
UDT
...
UDT
SCCP Connection-oriented
Connection Request (CR)
Connection Confirm (CC)
DT1
...
DT1
Released (RLSD)
Released Complete (RLC)
One sig. Connection : same Local Ref. No.+SLS
BSSAP/ RANAP
MAP CAP
Application Level
SCCP Level
Connection oriented
Services
Connectionless
Services
Use of SCCP services
SCCP message structure : General Layout
SCCP message structure

8 7 6 5 4 3 2 1
T1178720-96
Order of octet
transmission
Mandatory
fixed part
Mandatory
variable part
Optional part
Message type code
Mandatory parameter A
Mandatoryparameter
F
Pointer to parameter M
Pointer to parameter P
Pointer to start of optional part
Length indicator of parameter M
Parameter M
Length indicator of parameter P
Parameter P
Parameter name =X
Length indicator of parameter X
Parameter X
Parameter name =Z
Length indicator of parameter Z
Parameter Z
End of optional parameters
SCCP connectionless service messages
Message Service
type
Description
UDT 0,1 Unitdata
UDTS 0,1 Unitdata Service. Used to indicate to the originating SCCP that a UDT cannot be delivered to
its destination.
XUDT 0,1 Extended Unitdata. Used to send data along with optional parameters.
XUDTS 0,1 Extended Unitdata Service. Used to indicate to the originating SCCP that an XUDT cannot be
delivered to its destination.
LUDT 0,1 Long Unitdata. Used to send data along with optional parameters over MTP3b (Q.2210). Up to
3952 octets without segmentation are allowed.
LUDTS 0,1 Long Unitdata Service. Used to indicate to the originating SCCP that an LUDT cannot be
delivered to its destination.
SCCP connection-oriented messages
Message
Service type
Description
CC 2,3 Connection Confirm
CR 2,3 Connection Request
CREF 2,3 Connection Refused
AK 3 Data acknowledgement. Used to control the window flow control mechanism selected for the
data transfer phase.
DT1 2 Data Form 1
DT2 3 Data Form 2
ED 3 Expedited Data. Similar to DT2 but it can bypass the flow control mechanism.
EA 3 Expedited Data acknowledgement. Every ED message must be acknowledged with EA message
before another ED is sent.
IT 2,3 Inactivity Test. Sent periodically to check if the connection is still active at both ands and to
audit the consistency of data.
ERR 2,3 Protocol Data Unit Error. Sent on detection of the SCCP protocol error.
RLSD 2,3 Release
RLC 2,3 Release Complete
RSC 3 Reset Confirm.
RSR 3 Reset Request. Indicates that the SCCP needs to reset the sequence numbers.
SCCP message example - UDT
MTP
Physical
SCCP
F CK
SIF
SIO LI CRC F MSU
Data
User
Calling
Address
Called
Add.
Pointer to
User Data
Pointer to
Calling Add.
Pointer to
Called Add.
Protocol
Class
Message
Code
Routing
Label
SCCP message structure : example of UDT
OPC DPC
First bit
transmitted
Label 1000=NA0 0011=SCCP
F CK SIF SIO LI
F
I
B
FSN
B
I
B
BSN F
MTP message
SCCP
message
SLS
4bits 14 bits 14 bits
8n bits
Message
type
8 bits
09=UDT
pointers
to data
user data
pointer
to
para-
meters
(called)
pointer
to
para-
meters
(calling)
pointer
to
data
called
party
para-
meters
calling
party
para-
meters
user data
Protocol
class
L
e
n
g
t
h
L
e
n
g
t
h
L
e
n
g
t
h
SCCP message example - UDT
Parameter Type Length
(octets)
Value
Message type Mandatory fixed part 1 09
Protocol class Mandatory fixed part 1 0 or 1
Called party address Mandatory variable
part
2 minimum
Calling party address Mandatory variable
part
2 minimum
Data Mandatory variable
part
2-X
a)
a)
Due to the ongoing studies on the SCCP called and calling party address, the maximum length of
this parameter needs further study. Note that the transfer of up to 255 octets of user data is allowed
when the SCCP called and calling party address do not include global title.
SCCP Addressing
Addressing within SCCP make use of 3 separate elements ie DPC, GT , SSN
DPC is the address that requires no translation
Determine if the message is destined for that in SP or required to be routed over
SS7 via MTP
GT may comprise of dialed digits or another form of address that will not be
recognized in SS7 network
If the message required to be routed over SS7 network, translation is required
SSN will identify a subsystem accessed via the SCCP within a node and may be a
user part or AE via TCAP
SCCP address coding for Calling/Called party address
Address Indicator
A "1" in bit 1 indicates that theaddress contains asignalling point code.
A "1" in bit 2 indicates that theaddress contains asubsystemnumber.
Bits 3-6 of theaddress indicator octet contain theGlobal TitleIndicator (GTI), which is
encoded as follows:
Bits 6 5 4 3
0 0 0 0 no global titleincluded
0 0 0 1 global titleincludes natureof address indicator only
0 0 1 0 global titleincludes translation typeonly
0 0 1 1 global titleincludes translation type, numbering plan and encoding scheme
0 1 0 0 global titleincludes translation type, numbering plan, encoding schemeand nature
of address indicator
0 1 0 1
to
0 1 1 1
spareinternational
1 0 0 0
to
1 1 1 0
sparenational
1 1 1 1 reserved for extension.
Bit 7
1 RouteonSSN
0 RouteonGT.
Bit 8of theaddressindicator octet isreservedfor national useandisalwaysset to zero on
aninternational network.
Ordering of address element
8 7 6 5 4 3 2 1
Signalling point code
Subsystemnumber
Global title
Signaling Point Code
8 7 6 5 4 3 2 1
LSB
0 0 MSB
Subsystem number
Bits 8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 SSN not known/not used
0 0 0 0 0 0 0 1 SCCP management
0 0 0 0 0 0 1 0 reserved for ITU-T allocation
0 0 0 0 0 0 1 1 ISDN user part
0 0 0 0 0 1 0 0 OMAP (Operation, Maintenanceand Administration Part)
0 0 0 0 0 1 0 1 MAP (MobileApplication Part)
0 0 0 0 0 1 1 0 HLR (HomeLocation Register)
0 0 0 0 0 1 1 1 VLR (Visitor Location Register)
0 0 0 0 1 0 0 0 MSC (MobileSwitching Centre)
0 0 0 0 1 0 0 1 EIC (Equipment Identifier Centre)
0 0 0 0 1 0 1 0 AUC (Authentication Centre)
0 0 0 0 1 0 1 1 ISDN supplementary services
0 0 0 0 1 1 0 0 reserved for international use
0 0 0 0 1 1 0 1 broadband ISDN edge-to-edgeapplications
0 0 0 0 1 1 1 0 TC test responder
0 0 0 0 1 1 1 1
to
0 0 0 1 1 1 1 1
reserved for international use

0 0 1 0 0 0 0 0
to
1 1 1 1 1 1 1 0
reserved for national networks

1 1 1 1 1 1 1 1 reserved for expansion of national and international SSN.
Global Title
Address such as dialed digits
Not explicitly contain information that would allow routing in the signaling
network
Translation function is required
Bits 87654321 Decimal Value
00000000 0 unknown
00000001
to
00111111
1
to
63
international services
01000000
to
01111111
64
to
127
spare
10000000
to
11111110
128
to
254
national networkspecific
11111111 255 reservedfor expansion
Translation Type
Bits1to7of octet1containtheNatureof AddressIndicator (NAI) andarecodedas
follows:
Bits 7654321
0000000 unknown
0000001 subscribernumber
0000010 reservedfornational use
0000011 national significantnumber
0000100 international number
0000101
to
1111111
spare
Nature of address
Global Title : GT indicator = 0100
Bits 4321
0000 unknown
0001 BCD, oddnumberof digits
0010 BCD, evennumberof digits
0011 national specific
0100
to
1110
spare
1111 reserved.
Encoding scheme
Bits 8765
0000 unknown
0001 ISDN/telephonynumberingplan(RecommendationsE.163andE.164)
0010 genericnumberingplan
0011 datanumberingplan(RecommendationX.121)
0100 telex numberingplan(RecommendationF.69)
0101 maritimemobilenumberingplan(RecommendationsE.210, E.211)
0110 landmobilenumberingplan(RecommendationE.212)
0111 ISDN/mobilenumberingplan(RecommendationE.214)
1000
to
1101
spare
1110 privatenetwork or network-specificnumberingplan
1111 reserved.
Numbering Plan
Global Title : GT indicator = 0100
Global Title : Cg PA for entity receiving queries, Cg/Cd PA for
entity receiving responses for Authentication and LocUp
Global Title : Cd PA for entity receiving queries for
Authentication and LocUp
SCCP Global Title
E.164 Mobile Station ISDN Number, MSISDN
Used both in subscriber and network element numbering
MSISDN =Country Code +National Destination Code +Subscriber Number
E.212 International Mobile Subscriber Identity, IMSI
Used in identifying subscribers and subscribers HLRs
IMSI =Mobile Country Code +Mobile Network Code +Mobile Station Identification Number
E.214 Land Mobile Global Title
Used in identifying subscribers HLRs
Country Code +National Destination Code +Mobile Station Identification Number
Two types of routing by SCCP
Routing on MTP3 routing label
Routing on GT (Global Title)
Routing by DPC vs GT
To be able to route out signaling message by MTP
Upper layer has to know DPC (Destination Point Code)
What will happen if DPC is unknown from upper layer?
Routing on Label and on GT
BSSAP/ RANAP
MAP INAP
Is DPC contained
in the message?
Yes
No (there is a GT)
Routing on label
(do nothing)
Routing on GT
(GT anal ysis)
Message handling
Application
parts
SCCP
MTP
SCCP message routing
BSSAP MAP INAP
RI = GT
Application parts
SCCP
MTP
SIO = SCCP
GT Anal ysis
Other DPC
Discrimination
DPC = own SPC
Routing
Distribution
DPC is not own SPC
RI
RI = SSN
DPC
Own SPC
SSN
Global Title Analysis
GT analysis is used to analyze a GT to find out the destination of
the signaling message.
GT
Analysis
Numbering Plan
Digits
DPC
RI
When the DPC receives the message
RI = SSN, there is no need for GT analysis.
RI = GT, the GT analysis has to be performed.
Example of SCCP routing on GT
International Roaming, the first location update
MS sends IMSI to the VLR in VPLMN
VLR will send "update location" message to HLR
Does the VLR know SPC of the HLR?
Does the VLR know HLR address?
How can the VLR send LU message to the HLR?
IMSI Analysis : result is GT
IMSI analysis is used to analzse IMSI to find out where the
subscriber's HLR is
IMSI
Analysis
IMSI or E.212 Hybrid no. or E.214
MCC MNC MSIN Operator No. MSIN
International Roaming : The first location update
IMSI
Analysis
IMSI or E.212
Hybrid no. or E.214
GT
Analysis
Message handling
SCCP routing on GT
MTP
Example of SCCP routing on Label
Home subscriber, the first location update
MS sends IMSI to the VLR in HPLMN
VLR will send "update location" message to HLR
Does the VLR know SPC of the HLR?
How can the VLR send LU message to the HLR?
IMSI Analysis : result is DPC
IMSI analysis is used to analyse IMSI to find out where the
subscriber's HLR is
IMSI
Analysis
IMSI or E.212 DPC of the HLR
MCC MNC MSIN
Home subscriber : the first location update
IMSI
Analysis
IMSI or E.212
DPC of the HLR
Message handling
SCCP routing on label
MTP
Output of GTT function
successful
Output contains required parameter to route the message forward in the network
or to distribute the message
unsuccessful where no translation exist
Failure cause : no translation for an address of such nature, no translation for this
specific address
unsuccessful where translation exist but no available destination can be
found
Failure cause : MTP failure, SCCP failure, Subsystem failure
Example of IMSI and GT Analysis
MSC1 GMSC4
MSC7
MSC5 MSC6
HLR1
HLR2
MSC2 GMSC3 GEXC1
EXC3
EXC2
EXC4
EXC5
NA0
NA0
NA0
IN0 IN0
PSTN
FINLAND
THAILAND
GEXC6
HLR-ISDN:358602210001
MSISDN:6618810001
SCCP
MTP
MSC1 GMSC3
GMSC4 HLR1
2. LU_Request (Called-E.214, Calling-MSC1-ISDN)
3. LU_Response (Called-MSC1-ISDN, Calling-HLR1-ISDN)
4. LU_Acknowledge (Called-HLR1-ISDN, Calling-MSC1-ISDN)
1. IMSI analysis
2.
2.
3.
3.
3.
4.
4.
4.
NP = E.214
DIG = 358
DPC=GMSC3 NET=NA0
RI=GT
NP = E.214
DIG = 358
DPC=GEXC1 NET=IN0
RI=GT
NP = E.214
DIG = 3586022
DPC=HLR1NET=NA0
RI=GT
NP = E.214
DIG = 3586022
DPC=OWN
RI=GT or SSN
NP = E.164
DIG = 66
DPC=GMSC4 NET=NA0
RI=GT
NP = E.164
DIG = 66
DPC=GEXC6 NET=IN0
RI=GT
IMSI: 24406022XXXXXXXXX
NP = E.164
DIG = 358
DPC=GMSC3 NET=NA0
RI=GT
NP = E.164
DIG = 358
DPC=GEXC1 NET=IN0
RI=GT
NP = E.164
DIG=6618810001
DPC=MSC1 NET=NA0
RI=GT
NP = E.164
DIG=6618810001
DPC=OWN
RI=GT or SSN
NP = E.164
DIG=35860221001
DPC=HLR1 NET=NA0
RI=GT
NP = E.164
DIG=35860221001
DPC=OWN
RI=GT or SSN
IMISI = 24406 E.214 = 35860
IMSI and GT Analysis
BSC
SPC=35
MSC
35860
SPC=25
GMSC
(NA0)SPC=30
(IN0) SPC=10
PSTN
(NA0)SPC=30
(IN0) SPC=20
PSTN
SPC=10
PSTN
SPC=20
PSTN
(NA0)SPC=40
(NA1)SPC=10
BSC
SPC=45
MSC
SPC=35
HLR
8613901
SPC=40
GMSC
(NA0)SPC=50
(NA1)SPC=20
NA0 NA0
NA0
IN0
NA1
IMSI
analysis
in MSC
GT analysis
in GMSC
GT analysis
in PSTN
GT analysis
in PSTN
GT analysis
in GMSC
GT analysis
in MSC
GT analysis
in HLR
What need to be configured in NE? : Routing on DPC&SSN
Local (MSS PC)
SCCP
Subsystem
(MAPv, MAPM)
Remote (HLR PC)
SCCP
Subsystem
(MAPH)
MSS STP eg. MGW HLR
Remote (MSS PC)
SCCP
Subsystem
(MAPv, MAPM)
Local (HLR PC)
SCCP
Subsystem
(MAPH)
What need to be configured in NE? : Routing on GT
Local (MSS PC)
SCCP
Subsystem
(MAPv, MAPM)
Remote (STP PC)
SCCP
MSS STP eg. MGW HLR
Remote (STP PC)
SCCP
Local (HLR PC)
SCCP
Subsystem
(MAPH)
Local (STP PC)
SCCP
Remote (MSS&HLR PC)
SCCP
SS7 in UMTS R4 network
MSS/VLR
SCCP
M3UA
BSSAP BICC
TCAP
RANAP
MAP
M3UA
SCCP
TCAP
MAP
MTP3
SCCP
BSSAP
MTP3b
SCCP
RANAP
MTP3 M3UA MTP3b
MTP
ISUP
SCCP
BICC
M3UA
TCAP
ISUP
MAP
M3UA MTP3
GCS
PSTN
HLR
MGW
MGW
RNC BSC
SCCP management message
Message Description
SSA Subsystem Allowed
SOG Subsystem Out Of Service Grant
SOR Subsystem Out Of Service Request
SSP Subsystem Prohibited
SST Subsystem Status Test
SSC Subsystem Congested
SCCP level configuration steps
Create own SCCP and Subsystems using command NFD
Create other SCCP and Subsystems using command NFD
Change SCCP states using command NGC
Change Subsystem States using command NHC
Create PLMN definitions using command MXA
Create VLR definition using command MXN
Create IMSI analysis using command CFC
Create GT results using command NAC
Create GT analysis using command NBC

Pubate Satienpoch: SCCP: Signaling Connection Control Part

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Pubate Satienpoch: SCCP: Signaling Connection Control Part

Caricato da

Copyright:

Formati disponibili

1 2005 Nokia V1-Filename.

ppt / yyyy-mm-dd / Initials

reserved for international use

reserved for national networks

Potrebbero piacerti anche