7 Use of the SCCP (E1/T1 Interface)
29.0163GPPGeneral Packet Radio Service (GPRS)Gs interface network service specificationRelease 17Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR)TS
The underlying transport stack and the SCCP are used to support signalling messages between the SGSN and the MSC. The BSSAP+ protocol specified in 3GPP TS 29.018 is the user of the SCCP. 3GPP TS 29.018 only uses the services of the class 0 of the SCCP.
The Gs interface connects an SGSN to a VLR within the same PLMN. The use of point codes or global titles is allowed for routing of SCCP messages.
The format and coding of address parameters carried by the SCCP for routing purpose shall comply with ITU-T Recommendation Q.713 for E1 interface and ANSI T1.112.3 T1 interface with the following restrictions:
– The called party address shall include:
– an SSN (see subclause 6.4.1 E1 interface and subclause 6.4.2 for T1 interface);
– all other aspects of the SCCP signalling are specified in 3GPP TS 29.002.
– The calling party address shall include:
– an SSN (see subclause 6.4.1 E1 interface and subclause 6.4.2 for T1 interface);
– all other aspects of the SCCP signalling are specified in 3GPP TS 29.002.
When an SCCP message is sent, the Called Party Address is derived from the Called Address of the N-UNITDATA-REQUEST primitive issued by the local SCCP user.
When an SCCP message is received, the Calling Address within the N-UNITDATA-INDICATION primitive is derived from the Calling Party Address of the SCCP UNITDATA message received.
Only address information belonging to the E.164 numbering plan is allowed to be included as Global Title in the Called and Calling Party Address. The SGSN and the VLR store the address of the other entity using the format received in the Calling Party Address field or the address information received in the application part of the message.
Annex A (informative):
Change history
|
Change history |
||||||
|---|---|---|---|---|---|---|
|
TSG CN# |
Spec |
Version |
CR |
<Phase> |
New Version |
Subject/Comment |
|
Apr 1999 |
GSM 09.16 |
7.0.0 |
Transferred to 3GPP CN1 |
|||
|
CN#03 |
29.016 |
3.0.0 |
Approved at CN#03 |
|||
|
TSG |
TSG Doc |
TSG WG |
CR |
Rev |
Ph |
Cat |
Vers |
Vers |
Subject |
Date |
|---|---|---|---|---|---|---|---|---|---|---|
|
NP-09 |
NP-000441 |
N1-001017 |
004 |
1 |
R99 |
F |
3.0.0 |
3.1.0 |
Different SSNs for SGSN and VLR |
09-2000 |
|
NP-11 |
NP-0100150 |
N1-010459 |
005 |
1 |
Rel-4 |
C |
3.1.0 |
4.0.0 |
BSSAP+ over IP according to SIGTRAN |
03-2001 |
|
NP-16 |
NP-020224 |
N1-021326 |
006 |
Rel-4 |
F |
4.0.0 |
4.1.0 |
Various clean-up of wrong references |
06-2002 |
|
|
NP-16 |
Rel-5 |
4.1.0 |
5.0.0 |
CN plenary decision to make this 3GPP TS 29.016 also for Release 5. |
06-2002 |
|||||
|
NP-26 |
Rel-6 |
5.0.0 |
6.0.0 |
Rel-6 published after CN#26 |
12-2004 |
|||||
|
Rel-7 |
6.0.0 |
7.0.0 |
CN plenary decision to make this 3GPP TS 29.016 also for Release 7. |
06-2007 |
||||||
|
Rel-8 |
7.0.0 |
8.0.0 |
Upgrade to Rel-8 (CT#42) |
12-2008 |
||||||
|
Rel-9 |
8.0.0 |
9.0.0 |
Upgrade to Rel-9 (CT#46) |
12-2009 |
||||||
|
Rel-10 |
9.0.0 |
10.0.0 |
Upgrade to Rel-10 (CT#51) |
03-2011 |
||||||
|
Rel-11 |
10.0.0 |
11.0.0 |
Upgrade to Rel-11 (CT#57) |
09-2012 |
||||||
|
Rel-12 |
11.0.0 |
12.0.0 |
Upgrade to Rel-12 (CT#65) |
09-2014 |
||||||
|
Rel-13 |
12.0.0 |
13.0.0 |
Upgrade to Rel-13 (CT#70) |
12-2015 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2018-06 |
SA#80 |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2020-07 |
SA#88e |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2022-04 |
SA#95e- |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |