C7 Principles

CHAPTER 1
ROLE OF SIGNALLING
SYSTEM
CHAPTER 2
THE SS7 NETWORK
CHAPTER 3
SS7 4 LEVEL MODEL
CHAPTER 4
SS7 NETWORK
ADDRESSING AND ROUTING
CHAPTER 5
SS7 SIGNALLING UNITS
CHAPTER 6
SIGNALLING CONNECTION
CONTROL PART
CHAPTER 7
TRANS. CAPS. AP AND
MAP
CHAPTER 8
GSM NETWORK OVERVIEW
TO SS7
Principles of C7
CP03
Issue 5 Revision 0
Training Manual
FOR TRAINING
PURPOSES ONLY
Principles of C7
Training Manual
Issue 5 Revision 0
Course
Principles of C7
Course
Training
Manual
Issue 5 Revision 0
FOR TRAINING
PURPOSES ONLY
Positin mark for TED spine
CP03
Issue 5 Revision 0
CP03
Principles of C7
E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999

All Rights Reserved
Printed in the U.K.
CP03: Principles of C7
EMOTOROLA LTD. 2001
FOR TRAINING PURPOSES ONLY
Issue 5 Revision 0
Copyrights, notices and trademarks

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer
programs stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola certain exclusive rights for copyright computer programs, including the
exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any
copyright Motorola computer programs contained in the Motorola products described in this document
may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by
implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of
Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license
agreement and may be used and/or disclosed only in accordance with the terms of the agreement.
Software and documentation are copyright materials. Making unauthorized copies is prohibited by
law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored
in a retrieval system, or translated into any language or computer language, in any form or by any
means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola
assumes no liability resulting from any inaccuracies or omissions in this document, or from the use
of the information obtained herein. Motorola reserves the right to make changes to any products
described herein to improve reliability, function, or design, and reserves the right to revise this
document and to make changes from time to time in content hereof with no obligation to notify any
person of revisions or changes. Motorola does not assume any liability arising out of the application
or use of any product or circuit described herein; neither does it convey license under its patent
rights of others.
Trademarks
and MOTOROLA are trademarks of Motorola Inc.

UNIX is a registered trademark in the United States and other countries, licensed exclusively through
X/Open Company Limited.
Tandem, Integrity, Integrity S2, and Non-Stop-UX are trademarks of Tandem Computers
Incorporated.
X Window System, X and X11 are trademarks of the Massachusetts Institute of Technology.
Looking Glass is a registered trademark of Visix Software Ltd.
OSF/Motif is a trademark of the Open Software Foundation.
Ethernet is a trademark of the Xerox Corporation.
Wingz is a trademark and INFORMIX is a registered trademark of Informix Software Ltd.
SUN, SPARC, and SPARCStation are trademarks of Sun Microsystems Computer Corporation.
IBM is a registered trademark of International Business Machines Corporation.
HP is a registered trademark of Hewlett Packard Inc.
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Important notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1
1
1
2
2
First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . .
Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generic manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tandem OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scaleable OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Category number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Catalogue number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
15
15
16
16
16
17
17
17
Chapter 1
Role of Signalling System
No 7 in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
SS7 in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
12
The Network Switching Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
The Base Station System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
Network Management Centre (NMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
2Mbits PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110
SS7 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112
GSM Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
114
114
Chapter 2
The SS7 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Main Requirements of SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
Signalling Elements in a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
Signalling Point/Signalling Transfer Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
Signalling Point Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
Format of Signalling Point Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Numbering of International Signalling Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210
210
Signalling Link and Link Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Signalling Link Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212
212
Signalling Route and Route Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214
Message Routing across a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
216
Signalling Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
218
E1 PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220
SCP Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Switching Point (SSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Control Point (SCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
222
222
222
The SS7 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
224
Chapter 3
SS7 4 Level Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32
Protocol Layers of the OSI 7 Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
Protocol Comparison of OSI to SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
SS7 to OSI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
MTP Layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
310
MTP Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
312
MTP Layer 2 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
314
MTP Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
316

Traffic Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signalling Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
318
318
318
MTP Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message discrimination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
320
320
Message Transfer Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
322
SS7 layer 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
324
SS7 to OSI layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
326
Signalling Connection Control Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
328
Transaction Capabilities Application Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
330
Mobile Application Part (MAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
332
MAP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
334
MAP Services and Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
336
Chapter 4
SS7 Network Addressing and Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
Network Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
Point Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
iv
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Point Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
Global Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
Subsystem Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
410
Chapter 5
SS7 Signalling Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
Signalling Units Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Circuit Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Packet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
52
52
52
SS7 Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
Signal Unit Packets (Generic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
Error Correction and Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
510
512
FIB p BIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
514
Retransmission of Signalling Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
516
Length Indicator (LI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
518
Field Check Sum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
520
522
Fill in Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
524
Link Status Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
526
LSSU Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
528
Link Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
530
Link Alignment Test Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
532
Message Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
534
Service Information Octet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
536
Service Indicator (SI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
538
Sub-Service Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
540
Signalling Information Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
542
Routing Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
544
SS7 Management and Test Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
546
Header Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
548
SS7 Network Management and Network Test Messages . . . . . . . . . . . . . . . . . . . . . . . . .
550
552
Chapter 6
Signalling Connection Control Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
62
SCCP Signalling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
EMOTOROLA LTD. 2001
Issue 5 Revision 0
SCCP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
SCCP Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
SCCP Protocol Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
610
SCCP Embedded in MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
612
SCCP Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Routing Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message type code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
614
614
614
614
SCCP Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Type Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
616
616
SCCP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
618
SCCP Routing Calling Party and Called Party . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
620
SCCP Addressing for Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
622
SCCP Called Party Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
624
SCCP Address information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
626
SCCP Functional Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
628
Chapter 7
Transaction Capabilities Application Part and Mobile Application Part . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
Transaction Capabilities Application Part (TCAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
72
Purpose of TCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
74
Mobile Application Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
76
MAP Application Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
78
TCAP and MAP Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
710
TCAP and MAP in the OSI Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
712
AE Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
714
TCAP Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Component Sub Layer (CSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Transaction Sub layer (TSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
716
716
716
TCAP Message Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
718
TCAP Embedded Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
720
TCAP Information Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
722
Primitives and Constructor IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
724
TCAP Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
726
TCAP Transaction Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
728
MAP user Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
730
TCAP/MAP Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
732
Chapter 8
GSM Network Overview to SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
82
vi
EMOTOROLA LTD. 2001
Issue 5 Revision 0

Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
84
84
A Interface Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
A Interface between MSC and BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
88
BSSAP Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAP Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTAP Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
810
810
810
Interfaces Between BSC, BTS and MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
812
LAPD frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Address Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
814
814
814
LAPDm Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
816
LAPDm Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
818
A and B format Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Address Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
820
820
820
SS7 Connection to GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
822
EMOTOROLA LTD. 2001
vii
Issue 5 Revision 0
viii
EMOTOROLA LTD. 2001
General information
Issue 5 Revision 0
General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then corrections will be supplied automatically by Motorola in the form of
General Manual Revisions (GMRs).
Purpose
Motorola Global System for Mobile Communications (GSM) Technical Education manuals
are intended to support the delivery of Technical Education only and are not intended to
replace the use of Customer Product Documentation.
WARNING
Failure to comply with Motorolas operation, installation and maintenance
instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by
Motorola, although they can be used to supplement and enhance the knowledge gained
through such training.
About this
manual
EMOTOROLA LTD. 2001
Issue 5 Revision 0
General information
Cross references
Throughout this manual, cross references are made to the chapter numbers and section
names. The section name cross references are printed bold in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top
of each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola GSM manuals to represent keyboard
input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c
Press the Control and c keys at the same time.
ALT-f
Press the Alt and f keys at the same time.
Press the pipe symbol key.
CR or RETURN
Press the Return (Enter) key. The Return key is

identified with the symbol on both the X terminal and
the SPARCstation keyboards. The SPARCstation
keyboard Return key is also identified with the word
Return.
2
EMOTOROLA LTD. 2001
First aid in case of electric shock
Issue 5 Revision 0
First aid in case of electric shock

Warning
WARNING
Do not touch the victim with your bare hands until the electric circuit is
broken.
Switch off. If this is not possible, protect yourself with dry insulating
material and pull or push the victim clear of the conductor.
Artificial
respiration
In the event of an electric shock it may be necessary to carry out artificial respiration.
Send for medical assistance immediately.
Burns treatment
A warning is used to alert the reader to possible hazards that could cause loss of life,
physical injury, or ill health. This includes hazards introduced during maintenance, for
example, the use of adhesives and solvents, as well as those inherent in the equipment.
1.
Do not attempt to remove clothing adhering to the burn.
2.
If help is available, or as soon as artificial respiration is no longer required, cover

the wound with a dry dressing.
3.
Do not apply oil or grease in any form.
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Reporting safety issues
Reporting safety issues

Introduction
A caution means that there is a possibility of damage to systems, or individual items of
equipment within a system. However, this presents no danger to personnel.
Procedure
Whenever a safety issue arises:
1.
Make the equipment concerned safe, for example, by removing power.
2.
Make no further attempt to tamper with the equipment.
3.
Report the problem directly to GSM Customer Network Resolution Centre

+44 (0)1793 430040 (telephone) and follow up with a written report by fax
+44 (0)1793 430987 (fax).
4.
Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.
4
EMOTOROLA LTD. 2001
Warnings and cautions
Issue 5 Revision 0
Warnings and cautions

Introduction
The following describes how warnings and cautions are used in this manual and in all
manuals of the Motorola GSM manual set.
Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life,
physical injury, or ill health. This includes hazards introduced during maintenance, for
example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format

WARNING
Do not look directly into fibre optic cables or optical data in/out connectors.
Laser radiation can come from either the data in/out connectors or
unterminated fibre optic cables connected to data in/out connectors.
Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of
equipment within a system. However, this presents no danger to personnel.
Example and format

CAUTION
Do not use test equipment that is beyond its calibration due date when testing
Motorola base stations.
EMOTOROLA LTD. 2001
Issue 5 Revision 0
General warnings
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola GSM manuals. Failure to
comply with these warnings, or with specific warnings elsewhere in the Motorola GSM
manuals, violates safety standards of design, manufacture and intended use of the
equipment. Motorola assumes no liability for the customers failure to comply with these
requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning
labels fitted to the equipment. Warning labels must not be removed, painted over or
obscured in any way.
Specific
warnings
Warnings particularly applicable to the equipment are positioned on the equipment and
within the text of this manual. These must be observed by all personnel at all times when
working with the equipment, as must any other warnings given in text, on the illustrations
and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single
phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas
where the ac mains power is present must not be approached until the warnings and
cautions in the text and on the equipment have been complied with.
To achieve isolation of the equipment from the ac supply, the mains input isolator must
be set to off and locked.
Within the United Kingdom (UK) regard must be paid to the requirements of the
Electricity at Work Regulations 1989. There may also be specific country legislation
which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment
when in operation. Ensure that all transmitters are switched off when any antenna
connections have to be changed. Do not key transmitters connected to unterminated
cavities or feeders.
Refer to the following standards:
S
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High

Frequency (10kHz to 300GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre optic
cables connected to data in/out connectors.
6
EMOTOROLA LTD. 2001
General warnings
Issue 5 Revision 0
Lifting
equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent
responsible person must ensure that adequate lifting facilities are available. Where
provided, lifting frames must be used for these operations. When equipments have to be
manhandled, reference must be made to the Manual Handling of Loads Regulations
1992 (UK) or to the relevant manual handling of loads legislation for the country in which
the equipment is used.
Do not ...
... substitute parts or modify equipment.
Because of the danger of introducing additional hazards, do not install substitute parts or
perform any unauthorized modification of equipment. Contact Motorola if in doubt to
ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain Motorola equipment incorporates components containing the highly toxic material
Beryllium or its oxide Beryllia or both. These materials are especially hazardous if:
S
Beryllium materials are absorbed into the body tissues through the skin, mouth, or
a wound.
The dust created by breakage of Beryllia is inhaled.
Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.
EMOTOROLA LTD. 2001
Human exposure to radio frequency energy (PCS1900 only)
Issue 5 Revision 0

Introduction
This equipment is designed to generate and radiate radio frequency (RF) energy. It
should be installed and maintained only by trained technicians. Licensees of the Federal
Communications Commission (FCC) using this equipment are responsible for insuring
that its installation and operation comply with FCC regulations designed to limit human
exposure to RF radiation in accordance with the American National Standards Institute
IEEE Standard C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
Definitions
This standard establishes two sets of maximum permitted exposure limits, one for
controlled environments and another, that allows less exposure, for uncontrolled
environments. These terms are defined by the standard, as follows:
Uncontrolled environment
Uncontrolled environments are locations where there is the exposure of individuals who
have no knowledge or control of their exposure. The exposures may occur in living
quarters or workplaces where there are no expectations that the exposure levels may
exceed those shown for uncontrolled environments in the table of maximum permitted
exposure ceilings.
Controlled environment
Controlled environments are locations where there is exposure that may be incurred by
persons who are aware of the potential for exposure as a concomitant of employment, by
other cognizant persons, or as the incidental result of transient passage through areas
where analysis shows the exposure levels may be above those shown for uncontrolled
environments but do not exceed the values shown for controlled environments in the
table of maximum permitted exposure ceilings.
Maximum
permitted
exposures
The maximum permitted exposures prescribed by the standard are set in terms of
different parameters of effects, depending on the frequency generated by the equipment
in question. At the frequency range of this Personal Communication System equipment,
1930-1970MHz, the maximum permitted exposure levels are set in terms of power
density, whose definition and relationship to electric field and magnetic field strengths are
described by the standard as follows:
Power density (S)

Power per unit area normal to the direction of propagation, usually expressed in units of
watts per square metre (W/m2) or, for convenience, units such as milliwatts per square
centimetre (mW/cm2). For plane waves, power density, electric field strength (E) and
magnetic field strength (H) are related by the impedance of free space, 377 ohms. In
particular,
2
S + E + 377
377
H2
where E and H are expressed in units of V/m and A/m, respectively, and S in units of
W/m 2. Although many survey instruments indicate power density units, the actual
quantities measured are E or E2 or H or H2.
8
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Maximum
permitted
exposure
ceilings
Within the frequency range, the maximum permitted exposure ceiling for uncontrolled
environments is a power density (mW/cm2) that equals f/1500, where f is the frequency
expressed in MHz, and measurements are averaged over a period of 30 minutes. The
maximum permitted exposure ceiling for controlled environments, also expressed in
mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these
principles to the minimum and maximum frequencies for which this equipment is intended
to be used yields the following maximum permitted exposure levels:
Uncontrolled Environment
1930MHz
Ceiling
1970MHz
Controlled Environment
1930MHz
1970MHz
1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2
If you plan to operate the equipment at more than one frequency, compliance should be
assured at the frequency which produces the lowest exposure ceiling (among the
frequencies at which operation will occur).
Licensees must be able to certify to the FCC that their facilities meet the above ceilings.
Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating
compliance, but this equipment operates at power levels orders of magnitude higher, and
the exclusion is not applicable.
Whether a given installation meets the maximum permitted exposure ceilings depends, in
part, upon antenna type, antenna placement and the output power to which this
equipment is adjusted. The following example sets forth the distances from the antenna
to which access should be prevented in order to comply with the uncontrolled and
controlled environment exposure limits as set forth in the ANSI IEEE standards and
computed above.
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Example
calculation
For a base station with the following characteristics, what is the minimum distance from
the antenna necessary to meet the requirements of an uncontrolled environment?
Transmit frequency
1930MHz
Base station cabinet output power, P
+39.0 dBm (8 watts)
Antenna feeder cable loss, CL
2.0dB
Antenna input power Pin
PCL = +39.02.0 = +37.0dB (5watts)
Antenna gain, G
16.4dBi (43.65)
Using the following relationship:

G + 4pr W
Pin
2
Where W is the maximum permissible power density in W/m2 and r is the safe distance
from the antenna in metres, the desired distance can be calculated as follows:
r+
GPin
+ 43.65 5 + 1.16m
4pW
4p 12.87
where W = 12.87 W/m2 was obtained from table listed above and converting from
mW/cm 2 to W/m2.
NOTE
The above result applies only in the direction of maximum radiation of the
antenna. Actual installations may employ antennas that have defined radiation
patterns and gains that differ from the example set forth above. The distances
calculated can vary depending on the actual antenna pattern and gain.
Power density
measurements
While installation calculations such as the above are useful and essential in planning and
design, validation that the operating facility using this equipment actually complies will
require making power density measurements. For information on measuring RF fields for
determining compliance with ANSI IEEE C95.1-1991, see IEEE Recommended Practice
for the Measure of Potentially Hazardous Electromagnetic Fields - RF and Microwave,
IEEE Std C95.3-1991. Copies of IEEE C95.1-1991 and IEEE C95.3-1991 may be
purchased from the Institute of Electrical and Electronics Engineers, Inc., Attn:
Publication Sales, 445 Hoes Lane, P.O. Box 1331, Piscattaway, NJ 08855-1331,
(800) 678-IEEE or from ANSI, (212) 642-4900. Persons responsible for installation of this
equipment are urged to consult these standards in determining whether a given
installation complies with the applicable limits.
Other equipment
Whether a given installation meets ANSI standards for human exposure to radio
frequency radiation may depend not only on this equipment but also on whether the
environments being assessed are being affected by radio frequency fields from other
equipment, the effects of which may add to the level of exposure. Accordingly, the overall
exposure may be affected by radio frequency generating facilities that exist at the time
the licensees equipment is being installed or even by equipment installed later.
Therefore, the effects of any such facilities must be considered in site selection and in
determining whether a particular installation meets the FCC requirements.
10
EMOTOROLA LTD. 2001
Beryllium health and safety precautions
Issue 5 Revision 0

Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in
Oxygen.
With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium
compounds and Beryllium metal are potentially highly toxic.
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive within
the component it presents no health risk whatsoever. However, if the component should
be broken open and the Beryllium Oxide, which is in the form of dust, released, there
exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms
of Berylliosis are similar to Pneumonia and may be identified by all or any of the
following:
Mild poisoning causes fever, shortness of breath, and a cough that produces
yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous
membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty
with swallowing and breathing.
Severe poisoning causes chest pain and wheezing which may progress to severe
shortness of breath due to congestion of the lungs. Incubation period for lung symptoms
is 2-20 days.
Exposure to moderately high concentrations of Beryllium in air may produce a very
serious condition of the lungs. The injured person may become blue, feverish with rapid
breathing and raised pulse rate. Recovery is usual but may take several months. There
have been deaths in the acute stage.
Chronic response. This condition is more truly a general one although the lungs are
mainly affected. There may be lesions in the kidneys and the skin. Certain features
support the view that the condition is allergic. There is no relationship between the
degree of exposure and the severity of response and there is usually a time lag of up to
10 years between exposure and the onset of the illness. Both sexes are equally
susceptible. The onset of the illness is insidious but only a small number of exposed
persons develop this reaction.
First aid
Seek immediate medical assistance. The casualty should be removed immediately from
the exposure area and placed in a fresh air environment with breathing supported with
Oxygen where required. Any contaminated clothing should be removed. The casualty
should be kept warm and at rest until medical aid arrives.
EMOTOROLA LTD. 2001
11
Issue 5 Revision 0
Skin contact
Possible irritation and redness at the contact area. Persistent itching and blister
formations can occur which usually resolve on removal from exposure.
First aid
Wash area thoroughly with soap and water. If skin is broken seek immediate medical
assistance.
Eye contact
May cause severe irritation, redness and swelling of eyelid(s) and inflammation of the
mucous membranes of the eyes.
First aid
Flush eyes with running water for at least 15 minutes. Seek medical assistance as soon
as possible.
Handling
procedures
Removal of components from printed circuit boards (PCBs) is to take place only at
Motorola approved repair centres.
The removal station will be equipped with extraction equipment and all other protective
equipment necessary for the safe removal of components containing Beryllium Oxide.
If during removal a component is accidently opened, the Beryllium Oxide dust is to be
wetted into a paste and put into a container with a spatula or similar tool. The spatula/tool
used to collect the paste is also to be placed in the container. The container is then to be
sealed and labelled. A suitable respirator is to be worn at all times during this operation.
Components which are successfully removed are to be placed in a separate bag, sealed
and labelled.
Disposal
methods
Beryllium Oxide or components containing Beryllium Oxide are to be treated as
hazardous waste. All components must be removed where possible from boards and put
into sealed bags labelled Beryllium Oxide components. These bags must be given to the
safety and environmental adviser for disposal.
Under no circumstances are boards or components containing Beryllium Oxide to be put
into the general waste skips or incinerated.
Product life cycle

implications
Motorola GSM and analogue equipment includes components containing Beryllium Oxide
(identified in text as appropriate and indicated by warning labels on the equipment).
These components require specific disposal measures as indicated in the preceding
(Disposal methods) paragraph. Motorola will arrange for the disposal of all such
hazardous waste as part of its Total Customer Satisfaction philosophy and will arrange
for the most environmentally friendly disposal available at that time.
12
EMOTOROLA LTD. 2001
General cautions
Issue 5 Revision 0
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the
equipment described in the Motorola GSM manuals. Failure to comply with these
cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in
damage to the equipment. Motorola assumes no liability for the customers failure to
comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution
labels fitted to the equipment. Caution labels must not be removed, painted over or
obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this
manual. These must be observed by all personnel at all times when working with the
equipment, as must any other cautions given in text, on the illustrations and on the
equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge.
Although the damage caused by static discharge may not be immediately apparent,
CMOS devices may be damaged in the long term due to static discharge caused by
mishandling. Wear an approved earth strap when adjusting or handling digital boards.
See Devices sensitive to static for further information.
EMOTOROLA LTD. 2001
13
Issue 5 Revision 0
Devices sensitive to static
Devices sensitive to static

Introduction
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied
to the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into
high insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads shorted
together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into
conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Special handling
techniques
In the event of one of these devices having to be replaced observe the following
precautions when handling the replacement:
S
Always wear an earth strap which must be connected to the electrostatic point
(ESP) on the equipment.
Leave the short circuit on the leads until the last moment. It may be necessary to
replace the conductive foam by a piece of wire to enable the device to be fitted.
Do not wear outer clothing made of nylon or similar man made material. A cotton
overall is preferable.
If possible work on an earthed metal surface. Wipe insulated plastic work surfaces
with an anti-static cloth before starting the operation.
All metal tools should be used and when not in use they should be placed on an
earthed surface.
Take care when removing components connected to electrostatic sensitive

devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less
susceptible to electrostatic damage. However PCBs should be handled with care,
preferably by their edges and not by their tracks and pins, they should be transferred
directly from their packing to the equipment (or the other way around) and never left
exposed on the workbench.
14
EMOTOROLA LTD. 2001
Motorola GSM manual set
Issue 5 Revision 0

Introduction
The following manuals provide the information needed to operate, install and maintain the
Motorola GSM equipment.
Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are
release dependent:
Category
number
Name
Catalogue
number
GSM-100-101
System Information: General
68P02901W01
GSM-100-201
Operating Information: GSM System Operation 68P02901W14
GSM-100-311
Technical Description: OMC in a GSM System
GSM-100-313
Technical Description: OMC Database Schema 68P02901W34
GSM-100-320
Technical Description: BSS Implementation
68P02901W36
GSM-100-321
Technical Description: BSS Command

Reference
68P02901W23
GSM-100-403
Installation & Configuration: GSM System

Configuration
68P02901W17
GSM-100-423
Installation & Configuration: BSS Optimization
68P02901W43
GSM-100-501
Maintenance Information: Alarm Handling at

the OMC
68P02901W26
GSM-100-521
Maintenance Information: Device State

Transitions
68P02901W57
GSM-100-523
Maintenance Information: BSS Field

Troubleshooting
68P02901W51
GSM-100-503
Maintenance Information: GSM Statistics

Application
68P02901W56
GSM-100-721
Software Release Notes: BSS/RXCDR
68P02901W72
68P02901W31
Tandem OMC
The following Tandem OMC manuals are part of the GSM manual set for systems
deploying Tandem S300 and 1475:
Category
number
Name
Catalogue
number
GSM-100-202
Operating Information: OMC System

Administration
68P02901W13
GSM-100-712
Software Release Notes: OMC System
68P02901W71
EMOTOROLA LTD. 2001
15
Issue 5 Revision 0
Scaleable OMC
The following Scaleable OMC manuals replace the equivalent Tandem OMC manuals in
the GSM manual set:
Category
number
Name
Catalogue
number
GSM-100-202
Operating Information: Scaleable OMC System 68P02901W19

Administration
GSM-100-413
Installation & Configuration: Scaleable OMC

Clean Install
68P02901W47
GSM-100-712
Software Release Notes: Scaleable OMC

System
68P02901W74
Related manuals
The following are related Motorola GSM manuals:
Category
number
Name
Catalogue
number
GSM-001-103
System Information: BSS Equipment Planning
68P02900W21
GSM-002-103
System Information: DataGen
68P02900W22
GSM-005-103
System Information: Advance Operational

Impact
68P02900W25
GSM-008-403
Installation & Configuration: Expert Adviser
68P02900W36
Service manuals
The following are the service manuals in the GSM manual set, these manuals are not
release dependent. The internal organization and makeup of service manual sets may
vary, they may consist of from one to four separate manuals, but they can all be ordered
using the overall catalogue number shown below:
Category
number
Name
Catalogue
number
GSM-100-020
Service Manual: BTS
68P02901W37
GSM-100-030
Service Manual: BSC/RXCDR
68P02901W38
GSM-105-020
Service Manual: M-Cell2
68P02901W75
GSM-106-020
Service Manual: M-Cell6
68P02901W85
GSM-201-020
Service Manual: M-Cellcity
68P02901W95
GSM-202-020
Service Manual: M-Cellaccess
68P02901W65
GSM-101-SERIES
ExCell4 Documentation Set
68P02900W50
GSM-103-SERIES
ExCell6 Documentation Set
68P02900W70
GSM-102-SERIES
TopCell Documentation Set
68P02901W80
GSM-200-SERIES
M-Cellmicro Documentation Set
68P02901W90
16
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Category number
The category number is used to identify the type and level of a manual. For example,
manuals with the category number GSM-100-2xx contain operating information.
Catalogue
number
The Motorola 68P catalogue number is used to order manuals.
Ordering
manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or
Representative. Manuals are ordered using the catalogue number. Remember, specify
the manual issue required by quoting the correct suffix letter.
EMOTOROLA LTD. 2001
17
Issue 5 Revision 0
18
EMOTOROLA LTD. 2001
Chapter 1

No 7 in GSM
EMOTOROLA LTD. 2001
Issue 5 Revision 0
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Chapter 1
No 7 in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
SS7 in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
12
The Network Switching Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
The Base Station System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
Network Management Centre (NMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
2Mbits PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110
SS7 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112

Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
114
114
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
iv
EMOTOROLA LTD. 2001
Objectives
Issue 5 Revision 0
Objectives
At the end of this chapter the student will be able to:
Identify the two Subsystems and their components in GSM.
Identify the components and interfaces of the GSM network and describe their
function.
EMOTOROLA LTD. 2001
11
Issue 5 Revision 0
SS7 in GSM
SS7 in GSM
GSM network components
GSM Network
Overview
The diagram opposite shows a simplified GSM network. Each network component is
illustrated only once. However, many of the components will occur several times
throughout a network.
Each network component is designed to communicate over an interface specified by the
GSM standards. This provides flexibility and enables a network provider to utilize
system components from different manufacturers. For example Motorola Base Station
System (BSS) equipment may be coupled with an Ericsson Network Switching System.
The principle component groups of a GSM network are:
The Mobile Station (MS)

This consists of the mobile telephone, fax machine etc. This is the part of the network
that the subscriber will see.
The Base Station System (BSS)

This BSS is the part of the network that provides the radio interconnection from the MS
to the land-based switching equipment.
The Network Switching System (NSS)

The NSS consists of the Mobile services Switching Centre (MSC) and its associated
system-control databases and processors together with the required interfaces. This is
the part that provides for interconnection between the GSM network and the Public
Switched Telephone Network (PSTN).
The Operations and Maintenance Centre (OMC)

This enables the network provider to configure and maintain the network from a central
location.
12
EMOTOROLA LTD. 2001
SS7 in GSM
Issue 5 Revision 0
GSM Network Components
Operations and
Maintenance System
Network Switching System

VLR
HLR
NMC
AUC
MSC
EIR
OMC
PSTN
EC
IWF
XCDR
ME
BSC
Interface/Connection
SIM
Mobile Station
BTS
Base Station System
CP03_Ch1_01
EMOTOROLA LTD. 2001
13
Issue 5 Revision 0
The Network Switching Subsystem

The Network Switching System includes the main switching functions of the GSM
network. It also contains the databases required for subscriber data and mobility
management. Its main function is to manage communications between the GSM
network and other telecommunications networks.
The components of the Network Switching System are listed below:
S
Mobile Services Switching Centre (MSC)
Home Location Register (HLR)
Visitor Location Register (VLR)
Equipment Identity Register (EIR)
Authentication Centre (AUC)
InterWorking Function (IWF)
Echo Canceller (EC)
In addition to the more traditional elements of a cellular telephone system, GSM has
Location Register network entities. These entities are the Home Location Register
(HLR), Visitor Location Register (VLR), and the Equipment Identity Register (EIR). The
location registers are database-oriented processing nodes, which address the problems
of managing subscriber data and keeping track of a MSs location as it roams around the
network.
Functionally, the Interworking Function and the Echo Cancellers may be considered as
parts of the MSC, since their activities are inextricably linked with those of the switch as it
connects speech and data calls to and from the MSs.
14
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Networking Switching System
Operations
and
Maintenance System
VLR
HLR
AUC
EIR
MSC
PSTN
EC
IWF
BSS
CP03_Ch1_02
EMOTOROLA LTD. 2001
15
Issue 5 Revision 0
The Base Station System

The GSM Base Station System is the equipment located at a cell site. It comprises a
combination of digital and RF equipment. The BSS provides the link between the Mobile
Station (MS) and the Mobile services Switching Centre (MSC).
The BSS communicates with the MS over the digital air interface and with the MSC via 2
Mbit/s links.
The BSS consists of three major hardware components:
The Base Transceiver Station (BTS)

The BTS contains the RF components that provide the air interface for a particular cell.
This is the part of the GSM network that communicates with the MS. The antenna is
included as part of the BTS.
The Base Station Controller (BSC)

The BSC as its name implies provides the control for the BSS. The BSC communicates
directly with the MSC. The BSC may control single or multiple BTSs.
The Transcoder (XCDR)

The transcoder is used to compact the signals from the MS so that they are more
efficiently sent over the terrestrial interfaces. Although the transcoder is considered to be
a part of the BSS, it is very often located closer to the MSC.
The transcoder is used to reduce the rate at which the traffic (voice/data) is transmitted
over the air interface. Although the transcoder is part of the BSS, it is often found
physically closer to the NSS to allow more efficient use of the terrestrial links.
16
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Base Station System
BSS
XCDR
BSC
BTS
BTS
BTS
BTS
CP03_Ch1_03
EMOTOROLA LTD. 2001
17
Issue 5 Revision 0
Network Management Centre (NMC)

The NMC offers the ability to provide hierarchical regionalized network management of a
complete GSM system.
It is responsible for operations and maintenance at the network level, supported by the
OMCs which are responsible for regional network management.
The NMC is therefore a single logical facility at the top of the network management
hierarchy.
The NMC has a high level view of the network, as a series of network nodes and
interconnecting communications facilities.
The OMC, on the other hand, is used to filter information from the network equipment for
forwarding to the NMC, thus allowing it to focus on issues requiring national
co-ordination. The NMC can also co-ordinate issues regarding interconnection to other
networks, for example the Public Switched Telephone Network (PSTN).
The NMC can take regional responsibility when an OMC is not manned, with the OMC
acting as a transit point between the NMC and the network equipment. The NMC
provides operators with functions equivalent to those available at the OMC.
Functionality of the NMC

S
Monitors node on the network.
Monitors GSM Network Element Statistics.
Monitors OMC regions and provides information to OMC staff.
Passes on statistical information from one OMC region to another to improve

problem strategies.
18
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Network Management Centre
NMC
Q3 PROTOCOL
(GSM 12 SERIES)
OMC
OMC
OMC
REGION 2
REGION 3
REGION 1
NETWORK
CP03_Ch1_04
EMOTOROLA LTD. 2001
19
Issue 5 Revision 0
2Mbits PCM
2Mbits PCM
2 Mbit/s Trunk 32-channel PCM
This diagram opposite shows the logical GSM system with the 2 Mbit/s interfaces
highlighted.
The interfaces carry traffic from the PSTN to the MSC, between MSCs, from an MSC to
a BSC and from a BSC to remotely sited BTSs.
These links are also used between the MSC and IWF.
Each 2.048 Mbit/s link provides thirty-two 64 kbit/s channels available to carry speech,
data, or control information. The control information may contain C7, LAPD or X.25
formatted information.
These 2 Mbit/s links commonly act as the physical bearer for the interfaces used
between the GSM system entities.
110
EMOTOROLA LTD. 2001
2Mbits PCM
Issue 5 Revision 0
2Mbit trunks
NMC
VLR
BSS
XC
VLR
HLR
AUC
OMC
EIR
MSC
MSC
MS
XC
IWF
EC
EC
IWF
XC
BSC
BTS BSC BTS
BTS
BTS
PSTN
BTS
BTS
BTS
MS
BTS
BTS
COLOCATED ENTITIES
BTS
MS
CP03_Ch1_05
EMOTOROLA LTD. 2001
111
Issue 5 Revision 0
SS7 Interfaces
SS7 Interfaces
The term C7 and SS7 are describing the same function, they both describe the signalling
function of the network, either term may be used
ITU-TS Signalling System #7

The diagram opposite illustrates the use of C7 in the GSM system; carrying signalling
and control information between most major entities, and to and from the PSTN.
The following message protocols, which are part of C7, are used to communicate
between the different GSM network entities:
Interfacing the PSTN, the MSC performs call-signalling functions using the Telephone
User Part (TUP), or interfacing ISDN, the ISDN User Part (ISUP).
Between the MSC and the BSC, the Base Station System Management Application Part
(BSSMAP) is used.
The Direct Transfer Application Part (DTAP) is used to send messages between the
MSC and the mobile (MS).
MAP is used between the MSC and the VLR, EIR, and HLR.
Acronyms:
BSSAP
Base Station System Application Part
BSSMAP
Base Station System Management Application Part
DTAP
Direct Transfer Application Part
ISUP
ISDN User Part
MAP
Mobile Application Part
SCCP
Signalling connection Control Part
TUP
Telephone User Part
TCAP
Transaction Capabilities Application Part
112
EMOTOROLA LTD. 2001
SS7 Interfaces
Issue 5 Revision 0
C7 Interfaces
NMC
VLR
BSS
XC
VLR
HLR
AUC
OMC
EIR
MSC
MS
MSC
MAP
BSSAP
XC
BTS
BSC
IWF
EC
EC
BSSMAP
TUP
IWF
BSC
BTS
BTS
BTS
BTS
XC
PSTN
BTS
BTS
MS
BTS
BTS
BTS
MS
CP03_Ch1_06
EMOTOROLA LTD. 2001
113
Issue 5 Revision 0
GSM Interface Names
GSM Interface Names

Interface Names
Each interface specified within the GSM system has a name associated with it. The
diagram opposite illustrates the names of all the interfaces specified by GSM.
Air-interface
MSBTS
A-bis(Mo-bis)
BTSBSC
A-interface
BSSMSC
B-Interface
MSCVLR
C-interface
MSCHLR
D-interface
HLRVLR
E-interface
interMSC
F-interface
MSCEIR
G-interface
VLRVLR
R-interface
MSDTE (Data Terminating Equipment)
114
EMOTOROLA LTD. 2001
GSM Interface Names
Issue 5 Revision 0
GSM interface names
NMC
VLR
VLR
BSS
XC
VLR
OMC
HLR
AUC
C
EIR
MSC
MSC
MS
XC
IWF
EC
EC
IWF
XC
A
Abis
BSC
BTS BSC BTS

BTS
BTS
BTS
PSTN
BTS
BTS
Um
MS
BTS
BTS
COLOCATED ENTITIES
BTS
MS
CP03_Ch1_07
EMOTOROLA LTD. 2001
115
Issue 5 Revision 0
GSM Interface Names
116
EMOTOROLA LTD. 2001
Chapter 2
The SS7 Network
EMOTOROLA LTD. 2001
Issue 5 Revision 0
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Chapter 2
The SS7 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Main Requirements of SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
Signalling Elements in a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
Signalling Point/Signalling Transfer Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
Signalling Point Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
Format of Signalling Point Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Numbering of International Signalling Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210
210
Signalling Link and Link Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Signalling Link Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212
212
Signalling Route and Route Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214
Message Routing across a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
216
Signalling Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
218
E1 PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220
SCP Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Switching Point (SSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Control Point (SCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
222
222
222
The SS7 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
224
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
iv
EMOTOROLA LTD. 2001
Objectives
Issue 5 Revision 0
Objectives
At the end of this chapter you will be able to:
Identify the different functions that make up a signalling network.
Understand the functionality within an SS7 network.
EMOTOROLA LTD. 2001
21
Issue 5 Revision 0
Main Requirements of SS7

There are two main requirements of the signalling system.
S
All calls must be set-up, monitored and broken down in a correct manner.
The signalling system must be able to support all non-circuit applications such as
database enquires and supplementary services.
The SS7 network and protocol are used for:

S
Basic call set-up, management, and tear down.
Wireless services such as personal communications services (PCS), wireless

roaming, and mobile subscriber authentication.
Local number portability (LNP).
Toll-free (800/888) and toll (900) wire line services.
Enhanced call features such as call forwarding, calling party name/number display,
and three-way calling.
Efficient and secure worldwide telecommunications.
Network management information must also be carried across the network. This enables
the network to maintain itself during failures and then recover from them.
The network also needs to deal with load sharing and re-routing this is also achieved
through the use of SS7
When looking at any signalling requirements within a telephone network it is important to
understand that all voice calls breakdown into two separate components, the voice
component and the signalling component. All other calls are just seen by the network as
data that is signalling
22
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Circuit related applications concerned with the connection and

disconnection of telephone calls
Non circuit related applications which support the circuit relat
ed
applications
To achieve call processing the different components in the netwo
rk must
be able to interact with each other.
A call is made up of two components:
The voice/data component.
The signalling component.
CP03_Ch2_01
EMOTOROLA LTD. 2001
23
Issue 5 Revision 0
Signalling Elements in a Network

SP/STP
The basic blocks in the network
SPC
An address of a single unit in the network
Signalling link
The physical connection
Link set
More than one physical connection between the same two points
Route
The logical connection between two points in a network
Route set
More than one logical connection between the same two points
24
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Signalling Elements
S SP/STP
S SPC ( opc dpc )
S Signalling Link
S Link set
S Route
S Route set
CP03_Ch2_02
EMOTOROLA LTD. 2001
25
Signalling Point/Signalling Transfer Point
Issue 5 Revision 0

Signalling Point (SP)
A Signalling Point is any node in the network that is able to handle signalling messages.
These signalling messages can either be generated or received
Signalling transfer Point (STP)

A Signalling Transfer Point is able to receive a message on one signalling link and then
transfer that message to another link, without processing the contents of the message.
STP is able to transfer in three dimensions, national, regional and international
26
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Signalling Point/STP
S SP is a processing node in a signalling network, which has

SS7 implemented
S STP is a processing node where a message is received in

one link and transferred to another.
STP
SP
CP03_Ch2_03
EMOTOROLA LTD. 2001
27
Issue 5 Revision 0
Signalling Point Code

Signalling Point Code (SPC)
In the SS7 network all signalling points (SP) need to be identified in order to allow for
communication between each other. All Signalling Points are identified by a unique code
known as the Signalling Point Code (SPC)
The Signalling Point at which the signalling message is generated, or is the source user
part is known as the Originating Point Code (OPC)
The Signalling Point to which the signalling message is destined, or is the receiving user
part is known as the Destination Point Code (DPC)
In order to allow for multiplayer signalling there must be a method that allows for
communication between different networks. It is the Network Indicator (NI) that must be
defined for this.
SP = NI SPC
The SPC is normally 14 bits long in the binary form. This can be translated to either hex
or various national presentations
28
EMOTOROLA LTD. 2001
Issue 5 Revision 0
All signalling points in a SS7 network are identified by a unique code

known as a Signalling Point Code SPC
There are two components to a SPC
SP = NI SPC
CP03_Ch2_04
EMOTOROLA LTD. 2001
29
Issue 5 Revision 0
Format of Signalling Point Code

Numbering of
International
Signalling Points
A 14-bit binary code is used for the identification of signalling points (ITU-I Q708).
An international signalling point code (ISPC) should be assigned to each signalling point,
which belongs to the international signalling network. For some network environment,
one physical network node may serve as more than one signalling point, and may
therefore be assigned more than one signalling point code. All international signalling
point codes (ISPC) should consist of three identification sub-fields as indicated. The
sub-field of 3 bits (NML) should identify a world geographical zone. The sub-field of 8 bits
(KD) should identify a geographical area or network in a specific zone. The sub-field of
3 bits (CBA) should identify a signalling point in a specific geographical area or network.
The combination of the first and second sub-fields could be regarded asa signalling
area/network code (SANC).
Each country (or geographical area) should be assigned at least one signalling
area/network code (SANC).
The system of International Signalling Point Codes (ISPC) will provide for 62568
(12288) ISPCs.
If a country (or geographical area) should require more than 8 international signalling
points, one or more additional signalling area/network code(s) (SANC) would be assigned
to it.
210
EMOTOROLA LTD. 2001
Issue 5 Revision 0
CP03_Ch2_05
EMOTOROLA LTD. 2001
211
Issue 5 Revision 0
Signalling Link and Link Sets

A signalling link is the physical data link that connects two signalling points. It is a
bi-directional transmission path for signalling, comprising two data channels operating
together in opposite directions at the same data rate. It constitutes the lowest functional
level (level 1) in the Signalling System No. 7 (SS7) functional hierarchy.
S
A link set is a group of one to sixteen links between two nodes.
All of the links must have the same attributes.
Multiple link sets can be deployed between two nodes.
SS7 Signalling
Link Types
Signalling links are logically organized by link type (A through F) according to their use
in the SS7 signalling network.
A Link: An A (access) link connects a signalling end point (e.g., an SCP or SSP) to an
STP.
B Link: A B (bridge) link connects an STP to another STP. Typically, a quad of B links
interconnect peer (or primary) STPs (e.g., the STPs from one network to the STPs of
another network). The distinction between a B link and a D link is rather arbitrary. For
this reason, such links may be referred to as B/D links.
C Link: A C (cross) link connects STPs performing identical functions into a mated pair.
D Link: A D (diagonal) link connects a secondary (e.g., local or regional) STP pair to a
primary (e.g., inter-network gateway) STP pair in a quad-link configuration. The
distinction between a B link and a D link is rather arbitrary. For this reason, such links
may be referred to as B/D links.
E Link: An E (extended) link connects an SSP to an alternate STP.
F Link: An F (fully associated) link connects two signalling end points.
212
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Signalling link & Link Set
S The physical connection between two nodes (SP/STP) in the

SS7 network
S One or more links connected between the same two nodes in

the network Can be used for Load distribution
Link Set
Link 1
STP
Link 2
SP
CP03_Ch2_06
EMOTOROLA LTD. 2001
213
Issue 5 Revision 0
Signalling Route and Route Set

A signalling route is the pre-determined path, consisting of a succession of STPs and
interconnecting SLs that take a message through the network between the originating
point to the destination point.
Each route carries traffic to only one destination, the route may be direct or over several
STPs, the SLs in a route may belong to several routes and as such carry traffic to
several destinations
SLs and data in STPs combine to form a signalling route.
All the signalling routes that may be used between an originating point and a destination
point are known as a Signalling Route Set.
214
EMOTOROLA LTD. 2001
Issue 5 Revision 0
S
S
A signalling route is a predetermined path that takes the

message through the signalling network
A route set is one or more routes linked together
SP
SP
Link Set
Link Set
STP
STP
Signalling route
CP03_Ch2_07
EMOTOROLA LTD. 2001
215
Issue 5 Revision 0
Message Routing across a network

There are two signalling points that have a requirement to pass a message, the network
needs to have various elements in order to pass the message.
If the two SPs are connected then the SL between them is the only network element.
If the SPs are in two different networks then all of the elements are required:
Signalling Route: Needs to be in place in order to pass the message
STP: Able to transfer message between networks
Signalling Link: Connects the SP to STP/SPs
SP: Start point and end point of message
Link Set: If more that one SL exists between SP and STP
216
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Message Routing
OPC 1 11
OPC 2 22
Link Set
SP
STP
STP
Link Set
SP
signalling
link
Link Set
Link Set
STP
STP
CP03_Ch2_08
EMOTOROLA LTD. 2001
217
Issue 5 Revision 0
Signalling Methods
Signalling Methods
There are two methods of signalling that can be used to achieve call processing, they
are:
S
Channel Associated Signalling (CAS), where the speech and signalling are
associated to each other and follow the same physical path.
Common Channel Signalling (CCS), is a signalling method in which a single

channel conveys in data packets signalling information that relates to user
specified connections as a result, speech and voice do not need to be physically
related. Also known as associated mode when voice and signalling take the same
path, if the path is different then the signalling mode is associated.
SS7 has two signalling types:

S
Connection orientated signalling where two nodes establish a link to transfer

information
Connectionless signalling where a node sends information that does not require
acknowledgement of receipt
218
EMOTOROLA LTD. 2001
Signalling Methods
Issue 5 Revision 0
Signalling Methods
CAS
Voice and Signalling Channel
Signalling Channel
CCS
Voice Channels
CP03_Ch2_09
EMOTOROLA LTD. 2001
219
Issue 5 Revision 0
E1 PCM
E1 PCM
An E1 or 2.048Mbit/s PCM frame is made up of 32 eight-bit timeslots, numbered from 0
to 31. Timeslot (T/S) 0 is always used for sync, this enables incoming slots to be read at
the correct time, timeslot 16 is normally used for signalling this is not mandatory but it
is widely accepted as the norm.
Sampling of the analogue signal is done at 8000 times per second. Each frame consists
of 8 bits from each timeslot. So, each timeslot is 88000=64,000 bits per second 64
Kbit/sec
When referred to, the term E1 indicates both transmission and reception components.
220
EMOTOROLA LTD. 2001
E1 PCM
Issue 5 Revision 0
E1 PCM
What is an E1 PCM?
SIG
SYNC
VOICE
16
VOICE
31
32 timeslots @64 kb/s
CP03_Ch2_10
EMOTOROLA LTD. 2001
221
Issue 5 Revision 0
SCP Database
SCP Database
The terms SSP and SCP are used in the Intelligent Network (IN), they explain the
operation of database enquiries.
Service
Switching Point
(SSP)
SSPs are switches that originate, terminate, or tandem calls. An SSP sends signalling
messages to other SSPs to set-up, manage, and release voice circuits required to
complete a call. An SSP may also send a query message to a centralized database (an
SCP) to determine how to route a call (e.g., a toll-free 1-800/888 call in North America).
Service Control
Point (SCP)
An SCP sends a response to the originating SSP containing the routing number(s)
associated with the dialled number. An alternate routing number may be used by the
SSP if the primary number is busy or the call is unanswered within a specified time.
Actual call features vary from network to network and from service to service.
Databases may be either physically internal or external to the SCP, but must be
considered a separate device. There are several types of database, which include:
S
Call Management Service Database (CMSDB)
Number Portability (NP)
Line Information Database (LIDB)
Home Location Register (HLR)
Visitor Location Register (VLR)
Registers act as an interface to the telephone company database, and translate non
geographical numbers from a database to provide information for calling card, subscriber
services, fraud protection and intelligent networks
222
EMOTOROLA LTD. 2001
SCP Database
Issue 5 Revision 0
Network Databases
SSP
SCP
SS7 LINKS
SSP
SCP
CP03_Ch2_11
EMOTOROLA LTD. 2001
223
Issue 5 Revision 0
The SS7 Network
The SS7 Network

The SS7 network can be divided into two parts, Voice and Signalling. As already
mentioned they do need to follow the same physical path, and the two components are
required to achieve a completed call.
In the network the signalling can also be broken into separate parts, one for the control of
the voice and a second that is involved with database access. The database queries are
close to register signalling, however they can also be from many User Parts (UP) or
application parts (AP).
The first parts of the network that will be used are the SPs and the SSPs these will
establish the validity of the call and also prepare the voice circuit, behind these parts the
other components in the network the STPs and the SSPs will be used in the set up, or to
answer database queries and send reponses.
224
EMOTOROLA LTD. 2001
The SS7 Network
Issue 5 Revision 0
The SS7 Network

SP
SSP
STP
SCP
SS7 Links
VOICE CIRCUITS
SSP
STP
SCP
SP
CP03_Ch2_12
EMOTOROLA LTD. 2001
225
Issue 5 Revision 0
The SS7 Network
226
EMOTOROLA LTD. 2001
Chapter 3
SS7 4 Level Model
EMOTOROLA LTD. 2001
Issue 5 Revision 0
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Chapter 3
SS7 4 Level Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32
Protocol Layers of the OSI 7 Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
Protocol Comparison of OSI to SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
SS7 to OSI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
MTP Layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
310
MTP Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
312
314
MTP Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
316

Traffic Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signalling Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
318
318
318
MTP Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message discrimination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
320
320
Message Transfer Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
322
SS7 layer 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
324
SS7 to OSI layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
326
328
Transaction Capabilities Application Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
330
Mobile Application Part (MAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
332
MAP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
334
MAP Services and Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
336
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
iv
EMOTOROLA LTD. 2001
Objectives
Issue 5 Revision 0
Objectives
State the rules of a protocol and identify the different layers that constitute a
protocol.
Identify the different levels in SS7 and their function.
Understand how SS7 relates to the OSI model.
EMOTOROLA LTD. 2001
31
Issue 5 Revision 0
Protocols
Protocols
A Protocol is an agreed set of rules and procedures that if followed by all participants, will
allow the orderly and controlled transfer of information between and among these
participants.
Or in simple terms a protocol:
S
Allows unique physical addressing for separate entities
Controls the flow of information between the network layers for guaranteed
delivery.
Processor outages
Error detection and correction
Protocols also define the rules for data exchange, using fixed or variable length packets,
enables error free data transmission. It has the ability to append network management
information in predefined message structures using segmentation of data blocks for
transmission over established layers for different functions.
32
EMOTOROLA LTD. 2001
Protocols
Issue 5 Revision 0
What is a Protocol?
The Definition of a protocol is:
A protocol is a set of definitions and agreements on how to

communicate
CP03_Ch3_01
EMOTOROLA LTD. 2001
33
Issue 5 Revision 0
Protocol Layers of the OSI 7 Model

Number
Layer
Description
Physical
Is responsible for the actual transmission of

the data and the provision of the necessary
facilities, could be copper, wire, radio, satellite
Data Link
Is responsible for the packaging of the data to

be transmitted. Also error detection and
correction
Network
Prescribes the path a message has to take

and who the message is routed to. Layer 3
has all responsibility for all routing
Transport
Guarantees the correct endtoend ordering

of message packets, also endtoend data
control
Session
Global synchronization, both parties use this

layer to coordinate the communication
process between themselves
Presentation
Is responsible for the definition and

preparation of data before it is passed to the
application layer, it is able to distinguish
different data types and perform data
compression and decompression
Application
Is the interface of specific application to the

transmission medium
34
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Protocol Layers of the OSI Model
Application
Presentation
Session
Transport
Network
Data Link
Physical
OSI 7 Layer Model
CP03_Ch3_02
EMOTOROLA LTD. 2001
35
Issue 5 Revision 0
Protocol Comparison of OSI to SS7

The model that is most often spoken about when referring to the SS7 network is the OSI
model, this covers all layers within the SS7 model but the OSI model is laid out over 7
layers whilst the SS7 model is a 4 level one.
The major problem is that one can not then define directly across the two, the simple
view is that layers 13 in OSI are almost covered by level 13 in SS7, and that the Level
4 in SS7 can be laid over the layers 47 in the OSI model
36
EMOTOROLA LTD. 2001
Issue 5 Revision 0
OSI
SS7
Application
Presentation
Session
Transport
Network
Data Link
Physical
Level 4
Level 1 3
CP03_Ch3_03
EMOTOROLA LTD. 2001
37
Issue 5 Revision 0
SS7 to OSI Overview
SS7 to OSI Overview

The layers in the SS7 model the three lowest levels form the message transfer part
(MTP) and the fourth level contains the user parts (UP).
The OSI model uses layer 47 as the message handling part. In SS7 the message
handling also uses part of what would be layer three in OSI, and as a consequence the
message transfer part layer 13 in OSI does not equate to level 13 in the SS7 model.
The layers 47 in OSI are known as User Parts in SS7, these can be a specific User Part
such as the ISDNUser Part (ISUP) or can be comprised of different parts to make up
the signalling:
SCCP Signalling Connection Control Part
TCAP Transaction Capabilities Application Part
MAP Mobile Application Part
ASE Application Service Elements
38
EMOTOROLA LTD. 2001
SS7 to OSI Overview
Issue 5 Revision 0
SS7 to OSI Overview
OSI
SS7
ASE
Application
Presentation
Session
Transport
SCCP
Network
MTP Level 3
Data Link
MTP Level 2
Physical
MTP Level 1
TCAP
I
S
U
P
CP03_Ch3_04
EMOTOROLA LTD. 2001
39
Issue 5 Revision 0
MTP Layer 1
MTP Layer 1
The MTP Layer 1 is the physical level and it is virtually the same as the OSI model.
Layer 1 defines the physical, electrical and functional characteristics of a signalling data
link and the means to access it. The Layer 1 element provides a bearer for a signalling
link.
In a digital environment, 64 kbit/s digital paths will normally be used for the signalling
data link. The signalling data link may be accessed via a switching function, providing a
potential for automatic reconfiguration of signalling links.
S
Provides the physical connection between two nodes.
The protocol should be able to use any type of physical interface.
310
EMOTOROLA LTD. 2001
MTP Layer 1
Issue 5 Revision 0
MTP layer 1
MAP
ASE
TCAP
ISDN UP
SCCP
MTP L3
MTP L2
MTP L1
MTP L1
Physical Data Link
CP03_Ch3_05
EMOTOROLA LTD. 2001
311
Issue 5 Revision 0
MTP Layer 2
MTP Layer 2
Level 2 defines the functions and procedures for, and relating to, the transfer of signalling
messages over one individual signalling data link. The layer 2 functions together with a
layer 1 signalling data link as a bearer provide a signalling link for reliable transfer of
signalling messages between two points.
A signalling message delivered by the higher levels is transferred over the signalling link
in variable length signal units. For proper operation of the signalling link, the signal unit
comprises transfer control information in addition to the information content of the
signalling message.
The signalling link functions include:
S
Delimitation of signal unit by means of flags;
Flag imitation prevention by bit stuffing;
Error detection by means of check bits included in each signal unit;
Error correction by retransmission and signal unit sequence control by means of

explicit sequence numbers in each signal unit and explicit continuous
acknowledgements;
Signalling link failure detection by means of signal unit error rate monitoring and
signalling link recovery by means of special procedures.
312
EMOTOROLA LTD. 2001
MTP Layer 2
Issue 5 Revision 0
MTP layer 2
MAP
ASE
TCAP
ISDNUP
SCCP
SP
SP
SS7
LINK
MTPL3
MTPL2
SP
SP
MTP
L1
MTP
MTP
L1
MTP
L1
CP03_Ch3_06
EMOTOROLA LTD. 2001
313
Issue 5 Revision 0
MTP Layer 2 Functionality

Layer 2 defines the functions and procedures for, and relating to the transfer of signalling
messages over one individual signalling data link. The function of Layer 2 is to ensure
messages are delivered in the correct sequence and without loss or error, it also
performs initial alignment of the link and to supervise the performance of the link.
Functions include:
Buffer functions: Three buffers are contained at both ends of the signalling
link, used to ensure the messages are transported correctly
Signalling Delimitation: This removes or adds the flag as required.
Signalling Alignment: This checks that the bit pattern corresponds to the
rules of bit stuffing.
Error Detection: this is performed by the Frame Check Sequence (FCS) if
the checksum is different the Message Signalling Unit (MSU) is rejected
Delimitation, Alignment and error detection: perform acceptance
procedure
Error Correction: operates to ensure the correct MSU stream, each
message is assigned a sequence number, the MSUs are retransmitted when
an error is detected, Link Status Signalling Units (LSSUs) and Fill In Signal
Units (FISUs) are not retransmitted.
314
EMOTOROLA LTD. 2001
Issue 5 Revision 0
IncomingMSUs
Level 3
outgoingMSUs
Level 2
Receive
Buffer
Transmission
Buffer
Supervision
(LSSU)
Sequence Number
Check
Sequence number
generation
Error correction
Retransmission
Buffer
Checksum
Decoding
Checksum
generation
Error detection
Message Length
Check
Bit destuffing
Flag detection
Bit stuffing
Flag generation
Delimitation
IncomingMSUs
Level 1
outgoing MSUs
CP03_Ch3_07
EMOTOROLA LTD. 2001
315
Issue 5 Revision 0
MTP Layer 3
MTP Layer 3
Layer 3 in principle defines those transport functions and procedures that are common
to, and independent of, the operation of individual signalling links.
These functions fall into two major categories:
1.
Signalling message handling functions These are functions that, at the actual
transfer of a message, direct the message to the proper signalling link or User
Part.
2.
Signalling network management functions These are functions that, on the basis
of predetermined data and information about the status of the signalling network,
control the current message routing and configuration of signalling network
facilities. In the event of changes in the status, they also control reconfigurations
and other actions to preserve or restore the normal message transfer capability.
The different Layer 3 functions interact with each other and with the functions of other
levels by means of indications and controls as well as the testing and maintenance
actions may include exchange of signalling messages with corresponding functions
located at other signalling points. Although not User Parts, these parts of layer 3 can be
seen as serving as User Parts of the Message Transfer Part. As a convention in these
specifications, for each description, general references to User Parts as sources or sinks
of a signalling message, implicitly include these parts of Layer 3 unless the opposite is
evident from the context or explicitly stated.
316
EMOTOROLA LTD. 2001
MTP Layer 3
Issue 5 Revision 0
MTP Layer 3
SSP
MAP
ASE
TCAP
ISDNUP
SSP
SCCP
STP
STP
STP
STP
NETWORK
MTPL3
MTPL2
SCP
SCP
MTPL1
MTP
L1
CP03_Ch3_08
EMOTOROLA LTD. 2001
317
Issue 5 Revision 0

The Layer 3 function is signalling network, and can be divided into two basic categories,
Traffic Handling and Signalling Network Management.
Traffic Handling
Traffic Handling has the purpose of ensuring that signalling messages from a User Part
at a Signalling Point are delivered to the same user part at the destination indicated by
the sending User Part. The signalling message handling functions are divided into the
three areas detailed below.
Message Discrimination
This determines whether or not the received message is destined to the point itself
Message Distribution
This is used to deliver the received messages to the appropriate user part
Message Routing
This is used at each signalling point to determine the outgoing signalling link on which a
message is forwarded to the destination point.
Signalling
Network
Management
The Signalling Network Management function is to provide reconfiguration of the
signalling network in the case of failures. The signalling network functions are divided into
four main areas:
Network flow control

The purpose of network flow control is to limit signalling traffic at source, this is done to
control congestion of a destination
Network control
This contains the rules and procedures for routing the traffic in both normal and abnormal
states. This provides all the necessary information to traffic handling to perform the
routing.
Signalling link Management

This is used to restore failed links, activates idle links and to deactivate aligned signalling
links, the function monitors and controls signalling resources.
Policing
This is a method by which operators are able to restrict the use of their signalling network
by external operators; this can be implemented in STPs and at the MTP level.
318
EMOTOROLA LTD. 2001
Issue 5 Revision 0
MTP layer 3 Functionality
To User
Part
Traffic Handling
Message
Distribution
From User
Part
Message
Discrimination
Message
Routing
Incoming
Message
Outgoing
Message
Signalling network management

Network
control
MTP Layer 2
Policing
Network flow
control
Signalling resource
management
CP03_Ch3_09
EMOTOROLA LTD. 2001
319
Issue 5 Revision 0
MTP Functionality
MTP Functionality
Since the Message Transfer Part forms the interface at a node with the rest of the
signalling network, the signalling network will have significant impact on the MTP. The
MTP must however be independent of the signalling network in that it has to be capable
of performing its set functions and attaining its objectives, no matter what network
structure or status prevails.
The MTP has therefore to contain the necessary functions to ensure any impact that the
network has does not impair MTP performance. The components that must be
considered by the MTP are:
Signalling points (including signalling transfer points);
Signalling relations between two signalling points;
Signalling links;
Signalling link sets (including link groups);
Signalling routes;
Signalling route-sets.
The modes applicable to SS No. 7 MTP are:
Associated mode;
Quasiassociated mode.
The standard routing label is suitable for national applications. The signalling system
includes the possibility for using different routing labels nationally.
Message routing is the process of selecting the signalling to be used, for each signalling
message sent. Message routing is destination-code dependent with an additional
load-sharing element allowing different portions of the signalling traffic to a particular
destination to be distributed over two or more signalling links. This traffic distribution may
be limited to different links within a link set, or applied to links in different link sets.
Message distribution is the process, which, upon receipt of a message at its destination
point, determines to which User Part or Layer 3 function the message is to be delivered.
Message
discrimination
Upon receipt of a message at a signalling point, message discrimination determines
whether or not that point is the destination point of that message. This decision is based
on analysis of the destination code in the routing label in the message. If the signalling
point is the destination point, the message is delivered to the message distribution
function. If it is not the destination point, and the signalling point has the transfer
capability, the message is delivered to the routing function for further transfer on a
signalling link.
320
EMOTOROLA LTD. 2001
MTP Functionality
Issue 5 Revision 0
MTP Functionality
Level 4
Level 3
Level 2
Level 1
Message Transfer Part

Signalling
Message
Handling
Signalling
Message
Handling
Signalling
Message
Handling
TUP
ISUP
SCCP
Signalling
Network
Management
Signalling Link
Functions
Signalling Network
Functions
CP03_Ch3_10
EMOTOROLA LTD. 2001
321
Issue 5 Revision 0

MTP is responsible for the delivery of messages between switches
The MTP covers the first three levels of the SS7 protocol, the function of MTP is to serve
as a common transport system that provides reliable transmission of signalling messages
between communicating users, SS7 network does not equate directly to the OSI model,
for the SS7 model to match to the OSI first 3 layers some of the SCCP functionality must
be included in the MTP, in SS7 the MTP and SCCP is known as the Network Service
Part.
The MTP will ensure that the messages are transferred
S
Correctly, all the received messages will be checked before they are accepted
Without loss or duplication
In correct sequence
The MTP will also react to system and network features that will affect the reliable
transport of messages and will take the necessary action to ensure a high degree of
reliability.
322
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Message transfer Part
OSI
SS7
Network
Data Link
MTP Level 2
Physical
MTP Level 1
MTP Level 3
CP03_Ch3_11
EMOTOROLA LTD. 2001
323
Issue 5 Revision 0
SS7 layer 4
SS7 layer 4
The 4th level in SS7 equate to layers 47 in the OSI model, in SS7 the 4th level is known
as the User Parts (UP).
The user parts contain functions connected with the processing of signal information, the
UPs generate and analyse signalling messages, they use the MTP as a transport
function to carry the information to other user parts.
The combination of MTP 13 and SCCP is called the Network Services Part.
324
EMOTOROLA LTD. 2001
SS7 layer 4
Issue 5 Revision 0
SS7 level 4
S This level is known as the user part and is made up of

several different applications.
S These are split into two main functions.

S Telephone user parts.
S SS7 user parts.
CP03_Ch3_12
EMOTOROLA LTD. 2001
325
Issue 5 Revision 0
SS7 to OSI layers
SS7 to OSI layers

SS7 User Parts are
S
ISDN User Part (ISUP)
Telephone User Part (TUP)
Data User Part (DUP)
Signalling Connection Control Part (SCCP)
For some applications more complex signalling maybe required, in these cases
Application parts have been defined.
Application parts include
S
Mobile Telephony Application Part (MAP)
Intelligent Network Application Part (INAP)
Transaction Capabilities Application Part (TCAP)
326
EMOTOROLA LTD. 2001
SS7 to OSI layers
Issue 5 Revision 0
SS7 to OSI Overview
OSI
7
Application
Presentation
Session
Transport
SS7
ASE
TCAP
I
S
U
P
SS7 Level 4
SCCP
CP03_Ch3_13
EMOTOROLA LTD. 2001
327
Issue 5 Revision 0
Signalling Connection Control Part

SCCP sits at level 4 and is part of the SS7 protocol. It provides the following functions:
S
Connectionless and connection oriented network services
Tracking of application status.
Transfer of messages between subsystems at the originating and destination

nodes
328
EMOTOROLA LTD. 2001
Issue 5 Revision 0
OSI
SS7
Transport
SCCP
Network
MTP Level 3
Data Link
MTP Level 2
Physical
MTP Level 1
CP03_Ch3_14
EMOTOROLA LTD. 2001
329
Issue 5 Revision 0

TCAP is an SS7 level 4 application and is part of the SS7 Protocol.
TCAP provides a common protocol which allows a large number of applications which
use databases to operate. The protocol is independent of application.
TCAP is responsible for
S
Maintaining the connection once it is established.
Transferring information between nodes to allow applications to operate
Containing a transaction portion and a component portion.
TCAP provides support for interactive applications in a distributed environment.
330
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Application
Presentation
Session
Transport
SCCP
Network
MTP Level 3
Data Link
MTP Level 2
Physical
MTP Level 1
TCAP
CP03_Ch3_15
EMOTOROLA LTD. 2001
331
Issue 5 Revision 0
Mobile Application Part (MAP)

For some applications more complex signalling maybe required, in these cases
Application Parts have been defined.
MAPs functions are to perform signalling within the GSM network, SS7 signalling is
required between the MSC and all the registers such as HLR, VLR, EIR and AUC.
MAP consists of all signalling messages on the SS7 network that are not call control
(ISUP) messages (e.g. statistics, mobility, SMS)
MAP is the interface between TCAP and the application, because the MAP function is
control tasks and data exchange between subsystems MAP can be considered an
application.
As the MAP services are seen as primitives it cannot really be considered to be within
the OSI reference Model
332
EMOTOROLA LTD. 2001
Issue 5 Revision 0
MAP
Application
Presentation
Session
Transport
SCCP
Network
MTP Level 3
Data Link
MTP Level 2
Physical
MTP Level 1
TCAP
CP03_Ch3_16
EMOTOROLA LTD. 2001
333
Issue 5 Revision 0
MAP services
MAP services
MAP must be considered as both an application in its own right and part of the GSM
subsystems. This is because it uses the TCAP within the signalling system for
peer-to-peer communication and also has a functionality of its own for the application
entities to allow them to operate in the GSM environment.
Because the function of MAP service is control and data exchange between the
applications and MAP, two functions are required.
Common MAP services, for pure communication control
Special MAP services, for carrying signalling data
MAP subsystems include MSC, BSC, HLR, VLR, AUC and SMSC.
334
EMOTOROLA LTD. 2001
MAP services
Issue 5 Revision 0
MAP services
MAP user
MAP user
MAP services
(Primitives)
MAP
MAP
Peer to peer protocol
Primitives
TCAP
TCAP
Peer to peer protocol
CP03_Ch3_17
EMOTOROLA LTD. 2001
335
Issue 5 Revision 0
MAP Services and Primitives

The common MAP services can be used to control a communication between MAP and
its application. Depending on the task of the service either all, or only some of the
primitives will be used.
The purpose of the special MAP services is to carry the data between MAP and the
application. It is only a special MAP service that will contain the actual parameters.
Up to four of the primitives could be defined for the special MAP services
Included in the special MAP services are the message types, the local operation code,
used to identify the special MAP services within MAP. The primitives used could be
request, indication, response and confirmation.
It is only the special MAP message that will contain the actual parameter
336
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Map Services (cont)
There are six common MAP services, these are used to control a
communication
Between Map and an application. Depending on the service beingused
either all or only some of the primitives will be used.
Common MAP services
MAP DELIMITER
MAP OPEN
MAP CLOSE
MAP UABORT
MAP PABORT
MAP NOTICE
(U=user)
(P=provider)
CP03_Ch3_18
EMOTOROLA LTD. 2001
337
Issue 5 Revision 0
338
EMOTOROLA LTD. 2001
Chapter 4
SS7 Network Addressing and

Routing
EMOTOROLA LTD. 2001
Issue 5 Revision 0
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Chapter 4
SS7 Network Addressing and Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
Network Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
Point Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
Point Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
Global Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
Subsystem Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
410
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
iv
EMOTOROLA LTD. 2001
Objectives
Issue 5 Revision 0
Objectives
Describe the different types of addressing and routing structures.
EMOTOROLA LTD. 2001
41
Issue 5 Revision 0
Network Addressing
Network Addressing
In an SS7 network the signalling information is not always exchanged between adjacent
SPs or STPs
In a GSM system the exchange of information may involve several STPs, as a
consequence the network needs to understand how to each STP is addressed and how
can the system rout the signalling information to the correct point.
The addressing systems work on a national and international basis, with the services of
higher layers being used for international addressing.
42
EMOTOROLA LTD. 2001
Network Addressing
Issue 5 Revision 0
Network Addressing
S There are three types of network addressing information

elements these are:
Point code routing
Sub system routing
Global title translation
CP03_Ch4_01
EMOTOROLA LTD. 2001
43
Issue 5 Revision 0
Point Codes
Point Codes
In order to find the destination SP/STP certain signalling messages have routing labels.
Contained in the routing label is the Originating Point Code (OPC) (that is the point code
of the sender) and the addressee or Destination Point Code (DPC).
Addressing using signalling point codes will only work on a national basis.
44
EMOTOROLA LTD. 2001
Point Codes
Issue 5 Revision 0
Point Codes
S Point codes are a unique address of a signalling point within a

network
S Originating point code (OPC)

S Destination point code (DPC)
S Signalling point code (SPC)
CP03_Ch4_02
EMOTOROLA LTD. 2001
45
Issue 5 Revision 0
Point Codes
Point Codes
If two SPs need to communicate with each other if they are part of the same network, all
that is required is a signalling link between the two SPs.
The key element is the Point Code, this will allow unique addressing of each individual
element within a network.
For example, if the two SPs 1134 and 1234, as part of the same networks, are
enabled correctly they can communicate without requiring an STP, this would allow full
communication between the two points.
If two SPs that are not in the same network, SPs 1134 and 4234, which can be either
different layers or international networks, require to communicate they will require all
elements of the signalling networks to be in place. Because the network needs to either
cross network layers or is accessing a different network there is a requirement to go
through an STP. The STP is the only part of the signalling network that is able to change
the layer on which a network may communicate.
46
EMOTOROLA LTD. 2001
Point Codes
Issue 5 Revision 0
Point Code Layers
Point Code = 1334

SS7 LINKS
STP
SP
SS7 LINKS
Point Code = 4234
SS7 LINKS
SP
SP
VOICE CIRCUITS
Point Code = 1134
Point Code = 1234
CP03_Ch4_03
EMOTOROLA LTD. 2001
47
Issue 5 Revision 0
Global Title
Global Title
A Global Title (GT) is not an element within a signalling network that on its own is able to
provide routing within the network, a translation function is required to define the DPC.
A Global Title is an address such as a dialled digit.
The Global Title consists of a directory number and information on how to read the
number in order to achieve a routing solution.
48
EMOTOROLA LTD. 2001
Global Title
Issue 5 Revision 0
Global Title Translations
S Global title translation is performed by an STP to enable routing

of a message towards its final destination
S The destination point code or subsystem number is determined

from the the dialled digits
CP03_Ch4_04
EMOTOROLA LTD. 2001
49
Issue 5 Revision 0
Subsystem Numbering
Subsystem Numbering
A Subsystem Number (SSN) is an identification of a specific User Part, each user part
will have its own specific number.
The subsystem is identified either directly as in SCCP or indirectly, using a layer to carry
the signalling MAP.
Subsystem Numbers
SSN (Hex)
Subsystem
00
SSN not available
01
SCCP Management
02
Reserved
03
ISUP
04
OMAP
05
MAP
06
HLR
07
VLR
08
MSC
09
EIR
0A
AuC
FE
NSSAP
410
EMOTOROLA LTD. 2001
Subsystem Numbering
Issue 5 Revision 0
Subsystem Numbering
The Subsystem Number (SSN) specifies the user that either sent
het
SCCP message, or to which subsystem it is addressed.
The SSN is transmitted in the SCCP message and has a hex value
Subsystems might be
SCCP management
ISUP
OMAP
MAP
CP03_Ch4_05
EMOTOROLA LTD. 2001
411
Issue 5 Revision 0
Subsystem Numbering
412
EMOTOROLA LTD. 2001
Chapter 5
SS7 Signalling Units
EMOTOROLA LTD. 2001
Issue 5 Revision 0
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Chapter 5
SS7 Signalling Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51

Circuit Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Packet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
52
52
52
SS7 Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
Signal Unit Packets (Generic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
510
512
FIB p BIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
514
Retransmission of Signalling Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
516
Length Indicator (LI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
518
Field Check Sum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
520
522
Fill in Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
524
Link Status Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
526
LSSU Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
528
Link Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
530
Link Alignment Test Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
532
Message Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
534
Service Information Octet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
536
Service Indicator (SI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
538
Sub-Service Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
540
Signalling Information Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
542
Routing Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
544
SS7 Management and Test Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
546
Header Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
548
550
552
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
iv
EMOTOROLA LTD. 2001
Objectives
Issue 5 Revision 0
Objectives
Understand the different types of switching.
Identify the SS7 signalling units and describe their function and composition.
EMOTOROLA LTD. 2001
51
Issue 5 Revision 0
Signalling Units Overview

In all networks there are three types of switching, they can either be implemented
together, working with and over each other, or a network could have one method of
switching.
Circuit Switch
Where an open circuit is required at all times during the call, such as voice, this is
expensive and wasteful of resources. With the relationship to voice this is currently the
best option because open circuit reduces time delay.
Message Switch
With message switching the circuit is open for as long as each message takes to send.
This is good for a point-to-point data transmission. The sending switch does not stay
active but once the message has been sent the circuit closes down
Packet Switch
With the packet switch the circuit is made up only to send the packet of data, the packets
are of a set size, this allows packets that are going to multiple points to be sent down the
same links. This allows a high connection rate to one link. A packet switch will switch
user data and control data.
52
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Signalling units overview
S There are three basic methods of switching within a network

Circuit switching
Message switching
Packet switching
CP03_Ch5_01
EMOTOROLA LTD. 2001
53
Issue 5 Revision 0
SS7 Packet Switching

The SS7 network uses a packet switch to send the information around, this allows a lot
of information to be sent and also allows for fewer links to control more points.
If switch A has data to send to switch B, using packet data it does not require the circuit
AB to be active all the time. This means it could be used as a signalling link within a
different route.
Packets can be sent directly or via different signalling routes. The data arrives at its
destination and can arrive in any order, this is because the destination is able to
reassemble the data in the correct order by using the Packet Assembler/Dissembler
(PAD).
54
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Network using Packet
1
3
4
1
2
2
4
3
2
4
3
4
3
2
1
2
4
CP03_Ch5_02
EMOTOROLA LTD. 2001
55
Issue 5 Revision 0
Signal Unit Packets (Generic)

The definition of SS7 message types is a functionality of MTP 2. In level 2 of SS7 there
are three different message types. Each one has its own role.
All messages follow the same basic format, the frame structure is laid down by ITU-T
Q.701.
All signalling messages are an assembly of information that is to be transferred as a data
packet by the MTP, the signalling information can be exchanged between User Parts,
Application Parts or Message Transfer Parts.
The frame structure is as follows:
S
A flag to indicate the start
An acknowledgement field which houses sequence numbers
A length indicator
An optional information field the length varies with usage
The field check sum field
An end flag.
The end flag may also be used as the start flag for the next frame. Two flags should not
be sequenced.
56
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Signal Packet Generic
Last
Flag
Transmission
Direction
FCS
Information field
First
Length
Acknowledgment
Flag
Length
(Bits)
CP03_Ch5_03
EMOTOROLA LTD. 2001
57
Issue 5 Revision 0
Flag
Flag
Each signalling unit is enclosed between two flags, the opening flag and closing flag. The
closing flag may also be the opening flag of the next frame. As a consequence two flags
should not be sequenced.
The flag is made up of 8 bits, this is a unique 8 bits pattern, 01111110 (zero-six
ones-zero). As this is a unique pattern to stop it appearing elsewhere in the signal unit,
bit stuffing is used. The sender is responsible for the stuffing and the receiver is
responsible for the removal or de-stuffing.
58
EMOTOROLA LTD. 2001
Flag
Issue 5 Revision 0
Flag
FLAG
Flag
Last
FCS Spare
LI
F
I
B
FSN
Transmission Direction
B
I
B
BSN
Flag
First
CP03_Ch5_04
EMOTOROLA LTD. 2001
59
Issue 5 Revision 0
Error Correction and Flow Control

The error correction field contains 16 bits and consists of the Forward Sequence Number
(FSN), the Backward Sequence Number (BSN), the Forward Information Bit (FIB) and
the Backward Information Bit (BIB).
The error correction field ensures the reception of messages in the right order and
requests resending in case of any error.
Backward Sequence Number (BSN),

There are 7 bits reserved for sequence numbers. The BSN are used to acknowledge the
correct transmission of a signalling unit.
Backward Information Bit (BIB)

The BIB marks the signalling unit as to the state of received signalling units.
Forward Sequence Number (FSN),

There are 7 bits reserved for a 128 modulo counter function, it is stepped up whenever a
signalling unit is transmitted, FSN is used to recognise signalling units that are out of
sequence.
Forward Information Bit (FIB)

The FIB informs the receiver if the signalling unit is a retransmission or a first time
transmission.
510
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Error Correction Field
Last
First
Error Correction Field
Flag
FCS Spare
LI
F
I
B
FSN
B
I
B
BSN
Flag
16 Bits
CP03_Ch5_05
EMOTOROLA LTD. 2001
511
Issue 5 Revision 0

There are two error correction methods, the Basic Error Correction Method (BASIC) and
the Preventive Cyclic Retransmission Error Correction (PCR).
The Basic Error Correction Method (BASIC)

The receiving terminal sends a negative acknowledgement in response to an incorrectly
received signal unit, this will initiate a retransmission of the incorrect message signalling
unit and all those that follow.
The Preventive Cyclic Retransmission Error Correction (PCR)

In PCR, retransmission of not positively acknowledged message signal units is initiated
when there are no new message signal units to send from the transmission buffer. This
leads on to the sending of FISUs when the transmission buffer is empty and there are no
new message signalling units to send. Also if a timer is used, once the time frame is
over, retransmission takes place. During a period when there are no new signal units to
transmit, all units, which have not been positively acknowledged, will be retransmitted
cyclically.
Both methods are used in GSM. The PCR is easier to understand, when a timer has run
down or if no positive acknowledgement is received retransmission takes place.
With the BASIC method, the BSN and FSN use modulo 128 counters to indicate the
message signalling units numbers, the FIB and BIB are used to indicate if the message
signalling units have been received or to indicate a transmission error.
If the link has just been brought into service all of the values for the FSN, BSN, BIB and
FIB are 1, the return information will be of the same values if there are no errors or need
to retransmit.
Because FIB= BIB this can be thought of as a positive acknowledgement and the
originating signalling point will now remove the message from the buffer.
512
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Error Correction and flow control
FIB = 1, FSN = 50, BIB = 1, BSN= 0
SP
SP
BSN = 50, BIB = 1, FSN = 1, FIB = 1
CP03_Ch5_06
EMOTOROLA LTD. 2001
513
Issue 5 Revision 0
FIB p BIB
FIB BIB
The value of the FIB and BIB are the keys to error correction. Both the FIB and BIB are 1
bit symbols and can either be 1 or 0.
To indicate a transmission error the BIB is inverted either from 1 to 0 or from 0 to 1, it is
the sending of the inverted BIB that indicates an error.
The function of the FIB is to indicate if the message signalling unit is a retransmission.
This is shown by the inversion of the FIB.
When the receiving point receives an incorrect message two actions are taken:
The BIB is inverted, and the FSN of the last correct received message will be inserted
into the BSN field, this will indicate an error to the sending point and which message
signalling unit needs to be retransmitted.
When it is received at the sending point, the FIB will then be compared to the BIB,
because FIB BIB, it means that it is a negative acknowledgement.
When a negative acknowledgement is received the sending of new signalling units is
interrupted, all signals in the buffer, which have not been positively acknowledged, will
now be retransmitted. Any message signalling units in the buffer that have sequence
numbers that are higher than the retransmitted signal unit will also be retransmitted.
If a signalling message has been lost completely, then because the sequencing numbers
are not consecutive, the receiving point is able to ask for retransmission.
514
EMOTOROLA LTD. 2001
FIB p BIB
Issue 5 Revision 0
FIB BIB
FIB = 1, FSN = 51, BIB = 1, BSN= 1
SP
SP
BSN = 50, BIB = 0, FSN= 2, FIB = 1,
CP03_Ch5_06
EMOTOROLA LTD. 2001
515
Issue 5 Revision 0
Retransmission of Signalling Units

The sending point on receipt of the indication of a signalling error will retransmit the
message signalling unit. On transmission the FIB will now be inverted to indicate that this
is a retransmission.
The sending point will then send the signalling unit, on receipt of a successful
re-transmission the receiving point will send message signalling units as normal. If the
FIB = BIB then the signalling is correct.
516
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Retransmission of Signalling Unit
FIB = 0, FSN = 51, BIB = 0, BSN= 2
SP
SP
BSN = 51, BIB = 0 , FSN= 3, FIB = 0,
CP03_Ch5_08
EMOTOROLA LTD. 2001
517
Issue 5 Revision 0
Length Indicator (LI)

The length indicator is used to distinguish between the types of signalling units, MSU,
FISU and LSSU. The LI relates to the length of the optional Data Field.
The field consists of two parts, it is an 8 bit field, the first 6 bits are used to indicate a
value of between 063.
The final 2 bits are spare and not currently used.
518
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Length Indicator
8 bits
Flag
FCS Spare
2 Bits
F
I
B
LI
FSN
BSN
Flag
6 Bits
LI
Last
B
I
B
Signalling Unit
LI=0
LI=1,2
FISU
LSSU
LI>2
MSU
First
CP03_Ch5_09
EMOTOROLA LTD. 2001
519
Issue 5 Revision 0
Field Check Sum
Field Check Sum

The error detection function of the message signalling unit is performed by means of the
16 bit Field Check Sum (FCS).
The sending terminal generates the check bits, the FCS consists of the preceding bits of
the signalling unit being applied to a specified algorithm, and the FCS is opened at the
receiving terminal. The same algorithm is applied and the new check sum is compared to
the received. If an error occurs then the error correction operates.
520
EMOTOROLA LTD. 2001
Field Check Sum
Issue 5 Revision 0
Field Check Sum
Field used to check the signalling units for errors
16 Bits
Flag
Last
FCS Spare
LI
F
I
B
FSN
B
I
B
BSN
Flag
First
CP03_Ch5_10
EMOTOROLA LTD. 2001
521
Issue 5 Revision 0

There are three different formats of messages. The message type is another functionality
of MTP 2, in SS7 level 2 the types of message are defined.
Although no field is available to determine what type the message is, it is possible to do
so based on their different lengths, it is the LI that provides the information.
522
EMOTOROLA LTD. 2001
Issue 5 Revision 0
S There are three different types of packets in the SS7 network an

these are:
S Fill in signal unit (FISU)

S Link status signal unit (LSSU)
S Message signal unit (MSU)
CP03_Ch5_11
EMOTOROLA LTD. 2001
523
Issue 5 Revision 0
Fill in Signal Unit
Fill in Signal Unit

When no data is being sent across the SS7 network Fill In Signal Units (FISU) are
transmitted
They contain no network information, but are used to monitor link quality
The frame check sequence field is used to determine if there are any errors on the link.
When a FISU is sent the last sent FSN would be sent constantly. The FISU does not use
the sequence counter.
The length indicator is used to identify the type of message unit being sent.
As there is no information sent in an FISU, the length indicator is set to zero
Because the FISU is used in the idle state the BSN, FSN, FIB and BIB do not change
their values. Both ends of the link poll each other in the idle state. The FISU can also be
used to acknowledge receipt of an MSU.
524
EMOTOROLA LTD. 2001
Fill in Signal Unit
Issue 5 Revision 0
Fill In Signal Unit
Last
Flag
FCS
Spare
LI
F
I
B
16
First
FSN
B
I
B
BSN
Flag
Length
(Bits)
CP03_Ch5_12
EMOTOROLA LTD. 2001
525
Issue 5 Revision 0
Link Status Signal Unit

The Link Status Signal Unit (LSSU) is used to transfer information dealing with the
physical state of the signalling link. The LSSUs are only used to bring a link into service,
take a link out of service and during error situations, between two SPs/STPs.
Link Status Signal Units can also be used to align signalling links.
The status field of the LSSU can under ITU-T either be 1 or 2 octets long. This is really
inconsequential because it is only the first 3 bits that carry actual status information.
The receiver of an LSSU does not confirm its receipt.
526
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Last
Flag
FCS
16
Status
8 or 16
First
Spare
LI
F
I
B
FSN
B
I
B
BSN
Flag
Length
(Bits)
CP03_Ch5_13
EMOTOROLA LTD. 2001
527
Issue 5 Revision 0
LSSU Status Indication

The term, Status Field, in the LSSU is not normally used and the term Status Information
is used to explain the data that the LSSU carries.
The SF (or status field) according to ITU-T is 1 or 2 octets long, only the first three bits of
the first octet are used. All other bits are currently spare.
SI is the term STATUS INDICATION
Value
Abbreviation
Description
SIO
Start of link alignment
SIN
A link brought into service with a

normal surveillance time of 8.2 secs
SIE
A link brought into service with an

emergency surveillance time of 500
msecs
SIOS
An error situation or before a link is

in service, no MSUs can be sent or
received
SIPO
When layer 2 of an SP detects a

problem within layer 3 within its own
node it indicate the problem status to
the peer entity.
SIB
Signals overload on the originating

side, acknowledgements will not be
sent, link failure usually follows
528
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Last
FCS
Status
Spare
First
LI
8 or 16
000
001
010
5 or 13 Spare Bits
011
100
101
SIO
SIN
SIE
SIOS
SIPO
SIB
Out of alignment
Normal Alignment
Emergency Alignment
Out of Service
Processor Outage
Busy
CP03_Ch5_14
EMOTOROLA LTD. 2001
529
Issue 5 Revision 0
Link Alignment
Link Alignment
The operation of a signalling link is a duplex operation that is the link must be created
in both directions. Both terminals are equal, and as such, both need to establish the
correct link.
The first stage is the sending of SIOS indicating that the link is in error and out of service
(OOS).
The second stage is the sending of the SIO, this is the link out of alignment and the start
of alignment.
These steps are returned from the other SP involved in the link, to establish layer 2
between the two SPs
530
EMOTOROLA LTD. 2001
Link Alignment
Issue 5 Revision 0
Link Alignment
LSSU OOS = SIOS

LSSU OOS = SIO
STP
SP
LSSU OOS = SIOS
LSSU OOS = SIO
CP03_Ch5_15
EMOTOROLA LTD. 2001
531
Issue 5 Revision 0
Link Alignment Test Duration

The test period is started once the duplex link has been established in layer 2, the LSSU
sent depends on the test duration, if the test duration is normal at 8.2 secs, then the SIN
is sent, the other option, Emergency, the time duration of test is 500 msecs, then the SIE
is sent.
During this time all FISUs that are sent must demonstrate no errors.
The SIE or emergency alignment is only used if no alternative link exists and the link
needs to be in service.
When the test time is over and layer 2 is in service layer 3 will then initiate further tests,
an Signalling Link Test Message (SLTM)is sent for this purpose and it transmits a number
of test octets to layer 3 of the receiving end, if the test is correctly completed by the
sending of a Signalling Link Test Acknowledgement (SLTA) message, layer 3 is also
considered to be in traffic.
532
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Link Alignment Test
1 LSSU = SIN/SIE
3 MSU = SLTM
STP
SP
2 LSSU =SIN/SIE
4 MSU = SLTM
CP03_Ch5_16
EMOTOROLA LTD. 2001
533
Issue 5 Revision 0
Message Signal Unit
Message Signal Unit

Message Signalling Units (MSU) are the third type of signalling unit and they are the
most diverse. The message signalling units are used for transmission of layer 3
information or layer 4 signalling. Whenever an MSU is received it must be acknowledged
to the peer entity.
Layer 3 information includes Signalling Network Management messages (SNM) and
Signalling Network Testing and Maintenance messages (SNT).
Layer 4 information is mainly User Parts or Application Parts signalling information.
In the Message Signal Unit the status field is divided into two parts the Service
Information Octet (SIO) and the Signal Information Field (SIF). The Signal Information
Octet is used to associate signalling information with a User Part, while the Signal
Information Field contains the actual user data.
534
EMOTOROLA LTD. 2001
Message Signal Unit
Issue 5 Revision 0
Message Signal Unit
Last
Flag
FCS
SIF
SIO
16
8n
LI
Spare
2
First
F
I
B
1
FSN
B
I
B
BSN
Flag
N< 272
Length
(Bits)
CP03_Ch5_17
EMOTOROLA LTD. 2001
535
Issue 5 Revision 0
Service Information Octet

The Service Information Octet (SIO) is 8 bits long and is divided in two parts, the Service
Indicator (SI) and the Sub-Service Field (SSF). Both of these two sub fields are 4 bits in
length.
The Service Indicator is used to associate signalling information with a User Part and is
only used with MSU messages.
The Sub-Service Field allows for a distinction to be made between national and
international signalling messages.
536
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Last
Flag
FCS
SIO
SIF
Spare
First
LI
8 bits
SF
SI
CP03_Ch5_18
EMOTOROLA LTD. 2001
537
Issue 5 Revision 0
Service Indicator (SI)

The Service Indicator (SI) is used to point out the recipient User Part of the message unit
and is used by the distribution function of Level 3 in MTP to distribute the MSU to the
correct User Part. The association of signalling to User Part is only used with MSU
messages.
538
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Service Indicator
Last
Flag
FCS
SIF
SF
SIO
Spare
SI
DCBA
Service Indicator
0000
Signalling Network Management
0001
Signalling Network Testing and Maintenance
0010
Operation and Maintenance Application Part (OMAP)
0011
Signalling Connection Control Part (SCCP)
0100
Telephone User Part (TUP)
0101
ISDN User Part (ISUP)
0110
Data User Part (DUP) (call admin)
0111
Data User Part (DUP) (Supp Services)
First
LI
8 bits
CP03_Ch5_19
EMOTOROLA LTD. 2001
539
Issue 5 Revision 0
Sub-Service Field
Sub-Service Field
The Sub-Service Field indicates the type of signalling network used. Bits C and D are
used to specify if the network is international or national. Bits A and B are used in the
USA for priority but are spare under ETSI.
540
EMOTOROLA LTD. 2001
Sub-Service Field
Issue 5 Revision 0
Sub-Service Field
Last
Flag
FCS
SIF
SF
SIO
First
Spare
SI
LI
8 bits
DCBA
Network Indicator
0000
International 0
0100
International 1
1000
National
1100
National
CP03_Ch5_20
EMOTOROLA LTD. 2001
541
Issue 5 Revision 0
Signalling Information Field

The Signalling Information Field (SIF) is the only part of the MSU that refers to the User
Part. The SIF consists of two sub fields, the user information with the contained message
elements and the label field.
The user information is all the information carried in the message-signalling unit that
relates to the User Part of the message.
The label field refers to the transfer of the message through the signalling system.
MSUs do not need to be exchanged only between adjacent SP/STP. In a GSM system
the information may involve several STPs.
As SS7 uses signalling Point Codes (SPC) each SP/STP has a unique identifier to map it
in the GSM system.
MSUs can be exchanged through SP/STPs and as a result need a routing label within
the signalling unit, because FISUs and LSSUs are only between adjacent SP/STPs they
have no requirement for routing labels.
Each type of MSU within the SS7 network has its own label type.
542
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Last
Flag
FCS
SIF
SIO
Spare
Message elements
First
LI
Label
TUP Information Elements

MTP Management
SCCP User Data
ISUP Information Elements
CP03_Ch5_21
EMOTOROLA LTD. 2001
543
Issue 5 Revision 0
Routing Label
Routing Label
The Routing Label is separately defined for each of the User Parts and this label is used
by the MTP to route the message to the correct destination. Each User Part within the
SS7 system has its own label format.
Destination Point Code (DPC) indicates the Signalling Point Code of the receiver of the
signalling message
Originating Point Code (OPC) indicates the signalling point code of the sender of the
signalling message
Signalling Link Selection (SLS), these 12 bits have various uses depending on the user
part that the signalling message belongs to.
Depending on the user part the SLS may carry the Circuit Identification Code or it may be
a separate field. The Signalling Link Selection (SLS), depending again on the user part,
might have its own field or might be imposed in the CIC fields, as in TUP. The length of
the SLS field allows for the definition of a maximum of 16 signalling links per link set, as
such it is used to determine which Signalling Link within a link set will be used to transfer
the message.
If the user part is Signalling Network Management messages (SNM) or Signalling
Network Testing and Maintenance messages (SNT), then the SLS is replaced by
Signalling Link Code (SLC) again 12 bits long but only 4 are used, this indicates the
Signalling Link Number.
544
EMOTOROLA LTD. 2001
Routing Label
Issue 5 Revision 0
Routing Label
Last
FCS
Flag
SIO
SIF
Spare
First
LI
Routing Label
Signalling Link Selection (SLS)

12/4 bit
OPC
DPC
14 bit
14 bit
CP03_Ch5_21
EMOTOROLA LTD. 2001
545
Issue 5 Revision 0
SS7 Management and Test Messages

The core of a Message Signalling Unit (MSU) is generated on level 3 or 4. At level 3
there are two kinds of MSU that are generated:
S
Signalling Network Management messages (SNM-MSU) or
Signalling Network Testing and Maintenance messages (SNT-MSU).
In the Service Information Octet (SIO) the Service Indicator (SI) identifies the MSU,
0000 for SNM-MSUs
0001 for SNT-MSUs
for these messages contained in the Service Information Field (SIF) after the label will
be the header and then the data field which is optional. This applies only to layer 3.
546
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Last
Flag
FCS
SIF
SIO
Spare
First
LI
8n (272 >n>3) bits

Data Field
Data opt.
Heading Code
8 bits
Routing Label
32 bits
CP03_Ch5_23
EMOTOROLA LTD. 2001
547
Issue 5 Revision 0
Header Fields
Header Fields
Because this is a Layer 3 only, all of the signaling messages will relate to the signalling
network and not the user part. It is these dedicated user parts in layer 3 that
automatically detects error situations.
Errors can be separated into one of three groups
S
Overload on a single SS7 link
Outage/bringing into service an SP/STP
Outage/bringing into service an SS7 link between SPs/STPs
The SI will already define the MSUs and as such the SIF will be of a set nature.
Heading Code 0 (H0) defines a whole message group, whilst Heading Code 1 (H1) is
used to define a single message within the group.
548
EMOTOROLA LTD. 2001
Header Fields
Issue 5 Revision 0
Header Fields
By using the SI field it is possible to differentiate between user parts

within the network, this is only a layer 3 function, it will indicates what is
contained in both the heading codes and how much of the data field will
used.
The SI field and the Heading Code are necessary for message and
message group coding.
Heading code 0 (H0) defines the whole message group.
Heading code 1 (H1) identifies a single message in that group.
CP03_Ch5_24
EMOTOROLA LTD. 2001
549
Issue 5 Revision 0
SS7 Network Management and Network Test Messages

Field H0 and H1 work together to give full message. H0 explains what is being applied
and H1 explains each task to achieve H0
The heading code (H0) is the 4-bit field following the label and identifies the message
group.
The different heading codes for message groups are allocated as follows:
0000
Spare
0001
Changeover and change back messages
0010
Emergency changeover message
0011
Transfer-controlled and signalling-route-set congestion messages
0100
Transfer-prohibited-allowed-restricted messages
0101
Signalling-route-set-test messages
0110
Management inhibit messages
0111
Traffic restart allowed message
1000
Signalling-data-link-connection messages
1001
Spare
1010
User part flow control messages
550
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Last
Flag
FCS
SIF
Heading Code
SIO
Spare
First
LI
Routing Label
H1
H0
4 bits
4 bits
CP03_Ch5_25
EMOTOROLA LTD. 2001
551
Issue 5 Revision 0

The heading code (H1) is the 4-bit field following the label and identifies the message
group- message ITU-T Q.704
CBA Change back-acknowledgement signal
CBD Change back-declaration signal
CHM Changeover and change back
messages
LUA Link uninhibit acknowledgement

signal
LUN Link uninhibit signal
LRT Link remote inhibit test signal
CNP Connection-not-possible signal

CNS Connection-not-successful signal
COA Changeover-acknowledgement signal
COO Changeover-order signal
MIM Management inhibit messages

RCT Signalling-route-set-congestion-test
signal
RSM Signalling-route-set-test message
CSS Connection-successful signal

DLC Signalling-data-link-connection-order
signal
DLM Signalling-data-link-connection-order
message
ECA Emergency-changeoveracknowledgement signal
ECM Emergency-changeover message
RSR Signalling-route-set-test signal for

restricted destination (national option)
RST Signalling-route-set-test signal for
prohibited destination
ECO Emergency-changeover-order signal

FCM Signalling-traffic-flow-control
messages
LFU Link forced uninhibit signal
LIA Link inhibit acknowledgement signal
LID Link inhibit denied signal
LIN Link inhibit signal
LLT Link local inhibit test signal
TFA Transfer-allowed signal

TFC Transfer-controlled signal
TFM
Transfer-prohibited-transfer-allowedtransfer-restricted messages
TFP Transfer-prohibited signal
TFR Transfer-restricted signal (national
option)
TRA Traffic-restart-allowed signal
TRM Traffic-restart-allowed message
UFC User part flow control messages
UPU User part unavailable signal
With SNT the SI sub field in the SIO has the value 0001 to indicate that it is a MSU-SNT
message, the H0 code is SLT indicating signalling link test messages, the two message
types are M, for message and A, for acknowledgement.
552
EMOTOROLA LTD. 2001
Issue 5 Revision 0
SS7 Network Mngt and Network Test Messages
Last
Flag
FCS
SIF
Heading Code
SIO
Spare
First
LI
Routing Label
H1
H0
4 bits
4 bits
CP03_Ch5_25
EMOTOROLA LTD. 2001
553
Issue 5 Revision 0
554
EMOTOROLA LTD. 2001
Chapter 6
EMOTOROLA LTD. 2001
Issue 5 Revision 0
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Chapter 6
Signalling Connection Control Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
62
SCCP Signalling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
SCCP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
SCCP Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
SCCP Protocol Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
610
SCCP Embedded in MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
612
SCCP Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Routing Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message type code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
614
614
614
614
SCCP Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Type Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
616
616
SCCP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
618
SCCP Routing Calling Party and Called Party . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
620
SCCP Addressing for Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
622
SCCP Called Party Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
624
SCCP Address information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
626
SCCP Functional Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
628
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
iv
EMOTOROLA LTD. 2001
Objectives
Issue 5 Revision 0
Objectives
Identify the SCCP protocol class and describe their functions.
Explain the connectionoriented and commectionless processes.
Explain SCCP routing and SCCP management methods.
EMOTOROLA LTD. 2001
61
Issue 5 Revision 0

The Signalling Connection Control Part (SCCP) is a functional entity, which is situated
above the message transfer part (MTP). In SS7 the SCCP and MTP combine to form the
Network Service Part (NSP). This then meets the requirements of the network layer
Layer 3 of the OSI model. SCCP is defined in ITU-T recommendation Q.711 Q.716.
SCCP was designed to communicate with databases without any speech connections. In
GSM new protocols have been developed to handle the signalling between the MSC/VLR
and BSC the protocol Base Station System Application Part (BSSAP), and for the
MSC/VLR and HLR the protocol is Mobile Application Part (MAP). SCCP will work with
both the Transaction Capabilities Application Part (TCAP) and MAP on the interfaces that
are within the Network Switching Subsystem (NSS).
The SCCP maintains both Connection Orientated (CO) and Connection-less (CL)
network services. CO services allow the transfer of signals via an established path. CO
services are used normally when there are many messages to transfer or if the signalling
messages are so large they need to be segmented. In CL the address required to route
the information to its destination is included in each data packet, no logical connection
between the nodes is established in CL service.
SCCP has addressing capabilities that allow for end-to-end routing. This is possible as
the SCCP supplements the addressing found in MTP which is only possible to deliver a
message to a node by the use of a four bit code. In SCCP the addressing is enhanced by
the use of Destination Point Codes (DPC) and Subsystem Numbers (SSN). A second
feature in SCCP addressing is the ability to translate Global Titles into DPC and SSN.
Although SCCP is considered a Layer 3 functionality it is able to provide features that are
Layer 4, such as error detection and segmentation of data. SCCP also provides its own
management for administrative tasks. These are independent from the SS7 signalling
Network Management.
62
EMOTOROLA LTD. 2001
Issue 5 Revision 0
SCCP is used by the Base Station Subsystem Application Part

(BSSAP) on the Ainterface and by the TCAP and MAP on various
interfaces within the Network Subsystem (NSS)
The SCCP can operate in either the connectionless or connection

orientated service. It also maintains circuit and noncircuit signalling
S
S
The SCCP offers end to end addressing even across networks,

either national or international.
SCCP also has its own management and administrative functions.
CP03_Ch6_01
EMOTOROLA LTD. 2001
63
Issue 5 Revision 0
SCCP Signalling Services

The SCCP protocol is able to provide two types of signalling service
Connection-orientated (CO) service and connection-less (CL). Distinguishing between
connection-oriented and connection-less service within the SCCP is done using a
parameter called the protocol class.
Connection-orientated (CO) service is when a virtual connection is established between
nodes and identification of the connection is via reference numbers, these being the
Source Local Reference (SLR) and the Destination Local Reference (DLR), when the
connection is active data can be exchanged not only between the nodes but also to
address individual transactions, such as a location update in GSM or a mobile originating
call.
Connection-less (CL) service is different, there is no referencing, and as a result the
receiver of the message must assign it to an active process, such as paging in the
BSSAP.
The SCCP user is the functionality that determines if the connection for SCCP is CO or
CL.
64
EMOTOROLA LTD. 2001
Issue 5 Revision 0
S
S
Connectionorientated services allow transfer of messages via an

established path, this is used either for multiple messages orhen
w the
signalling message needs to be segmented. BSSAP
Connectionless service is when no logical path is established and the
SCCP message will contain the destination. MAP or BSSAP
BSSAP
MAP
TCAP
DTAP
BSSMAP
CL
CO
SCCP
MTP Level 3
CP03_Ch6_02
EMOTOROLA LTD. 2001
65
Issue 5 Revision 0
SCCP Services
SCCP Services
The connection-oriented services enable the transfer of signalling over established
signalling connections. These connections are either temporary or permanent. If the
connection is a temporary connection the control of signalling can be divided into three
phases.
1.
Connection Establishment this provides the method to establish the signalling

connection. At this stage both the reference numbers are assigned to the link and
each node.
2.
Data transfer this provides the transfer of data in Network Service Data Units
(NSDU). The transfer can be in simultaneous directions or in answer response
method. The data transfer service is compiled of SCCP messages. the SCCP
message contains two elements Network Protocol Information (NPCI) and
Network Service Data Unit (NSDU).
S
Network Protocol Control Information (NPCI)

The NPCI contains a connection reference number that allocated the
message to a signalling connection.
Network Service Data Unit (NSDU)

The NSDU contains the user data, if the data is too large for one SCCP
message to be carried in the SIF of an SS7 message the protocol class will
control segmenting and reassembling
3.
Connection release this provides the method to breakdown the connection and
release of the reference numbers.
The permanent connections have the same phases as temporary connection but may
have additional safeguarding mechanisms at the end points to ensure re-establishment in
case of processor outage.
In connectionless signalling all data for routing is carried in each data packet, so no
logical path is created in the network, the functions of the connectionless service are,
mapping of the network address to signalling relations, sequence services and
segmenting.
66
EMOTOROLA LTD. 2001
SCCP Services
Issue 5 Revision 0
SCCP services
Connection orientated transfer mode can be divided into three phases

Establishing the connection
Data transfer
Release of the connection
Connection less orientated transfer all of the information required to route

the data to its destination is contained in each packet.
CP03_Ch6_03
EMOTOROLA LTD. 2001
67
Issue 5 Revision 0
SCCP Primitives
SCCP Primitives
SCCP is a layer within the SS7. Because SCCP is not a top layer or a base layer it
means that it must be able to transfer information and communicate with the layers
above and below it in the protocol stack.
Layers either side of the SCCP are known as the service user and the SCCP is the
service provider, communication is achieved using Service Primitives.
Primitives consist of commands and responses that are associated with the services
requested of the layers. Service primitives are data units sent between layers to invoke a
different procedure.
There is a general syntax applied to all primitives:Layer Identifier
Generic Name
Specific Name
Parameter
The Layer Identifier specifies which layer is providing the service e.g. N=SCCP,
MTP=MTP, TR=transaction sub layer TCAP, TC=service provider in TCAP
The Generic Name defines the action to be performed
The Specific Name indicates the purpose of the primitive, it also indicates the direction of
primitive flow.
The parameter contains elements of information that will be transferred between layers.
68
EMOTOROLA LTD. 2001
SCCP Primitives
Issue 5 Revision 0
Primitive Structure
TCAP
Service
Primitives
Service
Primitives
I
S
U
P
SCCP
Service Access Point
Network Service Part
Service
Primitives
MTP Level 3
CP03_Ch6_04
EMOTOROLA LTD. 2001
69
Issue 5 Revision 0
SCCP Protocol Classes

The protocol used by SCCP to provide network services is divided into four classes.
Two classes are defined for each signalling services, 0 and 1 represent the
connection-less service and 2 and 3 represent the connection-orientated services.
Class 0 and 2 form the basic version whilst 1 and 3 allow for additional data security and
segmentation.
In GSM protocol classes 0,1 and 2 are used, class 3 is never used in GSM
Over the A interface protocol classes, 0 and 2 are used.
When using GSM MAP protocol classes, 0 and 2 are used
Protocol class 0 the NSDUs are transported independently of each other and may be
delivered out of sequence, this protocol class is a pure connection-less network service
Protocol class 1 all the features of class 0 are included and added to. An additional
sequencing feature is added and the signalling link selection is encoded into the routing
label. This is a connection-less network service.
Protocol class 2 allows for bi-directional transfer of NSDUs and it ensures sequencing
as in protocol class 1. This corresponds to a connection-oriented network service.
610
EMOTOROLA LTD. 2001
Issue 5 Revision 0
There are four Protocol classes defined within the SCCP protocol
Protocol Classes
0
Basic Connectionless Class
Unit Data (UDT) or Unit

Data Service (UDTS)
Sequenced Connectionless class
Unit Data (UDT) or Unit

Data Service (UDTS)
Basic Connectionorientated Class
Dataform 1 packets DT1
Flow Control Connectionorientated Class
Dataform 2 packets DT2
CP03_Ch6_05
EMOTOROLA LTD. 2001
611
Issue 5 Revision 0
SCCP Embedded in MSU

SCCP messages are carried on signalling links by means of MSUs.
The Service Indicator (SI) in the Service Information Octet (SIO) is coded to 0011 to
indicate that the payload of the Signalling Information Field (SIF) is an SCCP. The max
size of the SCCP message is 272 octets.
612
EMOTOROLA LTD. 2001
Issue 5 Revision 0
SCCP embedded in MSU
Last
Flag
FCS
SIF
SIO
Spare
LI
16
8n
First
F
I
B
FSN
B
I
B
BSN
Flag
n< 272
SCCP Message
CP03_Ch6_06
EMOTOROLA LTD. 2001
613
Issue 5 Revision 0
SCCP Message
SCCP Message
An SCCP message consists of the following parts,
Routing Label
This contains the DPC, OPC and SLS.
Message type
code.
This is a 1 octet field and defines the function and format of the SCCP message.
Parameters
This field is variable and depends on the information that needs to be carried. The SCCP
may contain a number of parameters with the signalling information. These parameters
can be of either a fixed or variable length and can also be mandatory or optional.
614
EMOTOROLA LTD. 2001
SCCP Message
Issue 5 Revision 0
Signalling Connection Control Part Msg
Last
Flag
FCS
SIF
SIO
First
Spare
LI
8n (272 >n>3) bits

Mandatory variable Part
Mandatory Fixed Part Message type Code
Routing Label
Parameters
CP03_Ch6_07
EMOTOROLA LTD. 2001
615
Issue 5 Revision 0
SCCP Message Structure

The complete message is hosted by the MSU. The SCCP breaks down into various parts
and the SCCP message that is sent will have three types of fields filled as laid out by
ITU-T.
Message Type
Code
This is the protocol class, it is using the message type code that the SCCP includes in
the MSU. The message type will also indicate if it is a CO or CL service. For CL the
message is either Unit Data (UDT) or Unit Data Service (UDTS). For CO the message
will be Data form 1 (DT1).
The parameters are further broken down into two sub fields.
S
Mandatory fixed Part
Mandatory variable Part
The contents of these two sub fields are specific for each SCCP message. This is
because each SCCP message has its specific number and type of parameters. The
length of these can be fixed or variable.
The Mandatory Part includes segmentation information, Destination/Source Location
Register DLR/SLR, or calling party and called party address.
616
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Last
First
Mandatory variable Part Mandatory Fixed Part Message type Code
Param. A
Param. B
Param. N
Pointer A
Pointer B
Pointer Opt
Param. A
Length
Param. B
Length
NAME
Length
End
Opt
Parm.
Routing Label
Msg.
type
Code
CP03_Ch6_08
EMOTOROLA LTD. 2001
617
Issue 5 Revision 0
SCCP Routing
SCCP Routing
The SCCP messages are carried in the SIF of the MSU. The only identifier is carried in
the SIO. The routing label carries information about the correct routing of the message
In the Parameter field there is a division of parameter groups. It is here that the protocol
class for service is indicated. Also included in the parameters is the Called Party
address, this is for SCCP routing. The information carried here will identify the type of
address and the address itself.
This information, being SCCP routing and addressing must be carried in both CO and CL
services.
618
EMOTOROLA LTD. 2001
SCCP Routing
Issue 5 Revision 0
SCCP routing
When SCCP is used to transfer a message, two parameters are used to

route it to the next node
Called Party Address
Calling Party Address
Both parts are included in connectionless Unidata and Unidata services.
CP03_Ch6_09
EMOTOROLA LTD. 2001
619
SCCP Routing Calling Party and Called Party
Issue 5 Revision 0

Within the SCCP message structure there must be parameters that enable non-circuit
related signalling for point-to-point communication between two users.
These address parameters are Called Party Address (CdPA) and Calling Party Address
(CaPA). The format of these two sub fields is the same and they identify the type of
address and the address itself.
An address may consist of any combination the following,
S
SPC
SSN
Global Title
The parameters CaPA and CdPA are necessary for end-to-end addressing of SCCP
messages
MAP uses all possible combinations for addressing, while BSSAP requires only the SPC
and SSN.
620
EMOTOROLA LTD. 2001
Issue 5 Revision 0
S The calling party address ( CaPA ) and the calledparty address (CdPA)
have the same format and also identify the type of address beingused.
S The address may consist of any combination of the following

SPC
SSN
Global title
CP03_Ch6_10
EMOTOROLA LTD. 2001
621
Issue 5 Revision 0
SCCP Addressing for Routing

Within SCCP there must be a method by which the addressing of node across the
network can be carried and understood. These addresses would be used to resolve the
routing to enable the transfer of SCCP message to the destination node throughout the
network.
The Addressing within SCCP has two basic categories:
1.
Global Title (GT), a global title consists of a regular directory number and
information as to how to interpret the number, only the SCCP layer in different
nodes is able to use the GT
2.
Destination Point Code (DPC) and Sub System Number (SSN), this system allows
direct routing, it bypasses the SCCP, the sub system number (SSN) is used by the
SCCP to identify different applications in a node, this is to identify the part of a
node and establish if it uses SCCP directly or indirectly.
Sub Systems of the SCCP

SSN (Hex)
Sub System
00
SSN not known or

available
01
SCCP management
02
Reserved
03
ISUP
04
OMAP
05
MAP
06
HLR
07
VLR
08
MSC
09
EIR
0A
AuC
FE
BSSAP
622
EMOTOROLA LTD. 2001
Issue 5 Revision 0
There are two methods of addresses for SCCP routing

Global title (GT), is a destination address, it is used by different
nodes to solve routing
DPC and SSN, this allows direct routing, as a result no
translation is required by the SCCP
CP03_Ch6_11
EMOTOROLA LTD. 2001
623
Issue 5 Revision 0
SCCP Called Party Address

The format of the Called Party Address (CdPA) and the Calling Party Address (CaPA)
are the same, so by looking at one it is possible to explain both.
The Called Party Address field breaks down into three sub fields:
Address Length. This indicates the amount of information in the SCCP address sub
field.
Address Indicator. Because address information handled by the SCCP can appear in
different variants, it is then practical to have a sub field that defines the structure of the
address related information.
SCCP address. This is made up from the Sub-System Number (SSN), Signaling Point
Code (SPC) and Global Title (GT) (which is defined by lower level parameters).
624
EMOTOROLA LTD. 2001
Issue 5 Revision 0
SCCP Called Party Addressing
SCCP Address
GT
SSN
SPC
Spare Routing Indicator
Routing based on
0=GT
1=DPC+SSN
Last
Address Indicator
GT Indicator
Address Length
SSN Indicator
0000=GT not included

0001
0010
=GT included
0011
0100
Point Code Indicator
0=SSN not included 0=SPC not included

1=SSN included
1=SPC included
First
CP03_Ch6_12
EMOTOROLA LTD. 2001
625
Issue 5 Revision 0
SCCP Address information

As the SCCP is embedded in MTP layer 3 using the MSU to transport the user data, in
the routing label of the MTP the DPC and OPC for the link being used to transfer the
information is enclosed. This information is only between two SP/STPs and is not
end-to-end addressing.
Within the SCCP the subdivisions of address field includes the Calling Party Address
(CaPA) and the Called Party Address (CdPA), because SCCP can provide end-to-end
routing these address are used to achieve it.
The Called Party Address and Calling Party Address are of the same format and as by
looking at one in detail it is possible to understand either.
The Called Party Address field breaks down into three sub fields, the SCCP address, this
is made up from the SPC, SSN and GT (which is defined by lower level parameters).
SPC, this indicates the SPC of the Called/Calling Party SCCP node
SSN, this is the SCCP sub system number
GT, this is the Global Title, which is a sub parameter that is defined by lower level sub
parameters:
S
Address Information
this indicates the called or calling partys number
Nature of Address
defines the type of number contained in the GT National number or International
Number
Numbering Plan
indicates the numbering plan PLMN, ISDN/Mobile
Translation type
defines the routing table GSM or Short Message Centre
The format of the information is laid out in ITU-T Q713
626
EMOTOROLA LTD. 2001
Issue 5 Revision 0
SCCP Address Information
MAP
TCAP
Called Address
SPC
Address Information
SSN
Nature of Address
Global Title
Numbering Plan
SCCP
Calling Address
Translation type
MTP
Routing Label
DPC
OPC
CP03_Ch6_13
EMOTOROLA LTD. 2001
627
Issue 5 Revision 0
SCCP Functional Structure

The SCCP is able to transfer messages both to higher layers, SCCP Users and around
the network using MTP, in order to do so it must have separate functionality within the
SCCP to achieve this
The SCCP function consists of the following main sub functions:
SCCP Connection-Oriented Control (SCOC). The function of the SCOC is to control the
establishment and release of signalling connection and to provide for data transfer on
signalling connections.
SCCP Connectionless Control (SSLC). This sub function is responsible for the
connectionless transfer of data units.
SCCP Management (SCM). The purpose of the SCCP Management is to provide
capabilities to handle the congestion or failure of the SCCP, the SCCP user or the
signalling route to the SCCP/SCCP user. These are in addition to the MTPs signalling
route management and flow control.
SCCP Routing Control. On receipt of a message from the MTP or any of the above sub
functions, the SCCP Routing Control provides the necessary routing functions to forward
the message. If the called party is a local user then the message is passed to either
SCOC, SSLC or SCM. If the called party is not a local user, then it is passed to MTP for
transfer to a distant SCCP user.
628
EMOTOROLA LTD. 2001
Issue 5 Revision 0
SCCP
SCCP
Connection
Oriented
Control
(SCOC)
SCCP
USERS
MTP
SCCP
Routing
Control
(SCRC)
MTP
SCCP
Connectionless
Control
(SCLC)
SCCP
Management
(SCM)
CP03_Ch6_14
EMOTOROLA LTD. 2001
629
Issue 5 Revision 0
630
EMOTOROLA LTD. 2001
Chapter 7
Transaction Capabilities
Application Part and Mobile
Application Part
EMOTOROLA LTD. 2001
Issue 5 Revision 0
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Chapter 7
Transaction Capabilities Application Part and Mobile Application Part . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
Transaction Capabilities Application Part (TCAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
72
Purpose of TCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
74
Mobile Application Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
76
MAP Application Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
78
TCAP and MAP Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
710
TCAP and MAP in the OSI Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
712
AE Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
714
TCAP Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Component Sub Layer (CSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Transaction Sub layer (TSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
716
716
716
TCAP Message Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
718
TCAP Embedded Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
720
TCAP Information Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
722
Primitives and Constructor IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
724
TCAP Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
726
TCAP Transaction Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
728
MAP user Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
730
TCAP/MAP Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
732
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
iv
EMOTOROLA LTD. 2001
Objectives
Issue 5 Revision 0
Objectives
Describe the functionality of TCAP and MAP.
Identify the portions of the TCAP and MAP environment.
Identify the TCAP message structure and explain the function of the elements.
Describe the procedure for a TCP transaction.
EMOTOROLA LTD. 2001
71
Issue 5 Revision 0

Transaction Capabilities Application Part (TCAP) was introduced above the SCCP and
MTP as a reaction for the need to deal with increasing Database-to-Database
communication. TCAP uses SCCP to carry the information throughout the signalling
network and it is TCAP that provides the core functionality to support roaming.
TCAP is the serving interface between SCCP and the functionality that sits above TCAP
providing GSM with a lot of dialogues running concurrently with a wide variety of
messages carrying numerous parameters. These communications are now not only
concerned with data transfer but are now able to invoke operations at the remote end.
The element named Transaction Capabilities (TC) provides general standardised protocol
functions.
TCAP information is carried within SCCP messages as user data. This is known as
embedded data, allowing the TCAP message through the SS7 levels. It relies on the
NSP for physically transporting the messages over the network.
TCAP defines an end-to-end protocol between TC users. This means that in a
communication link between two TCAP nodes, the TCAP is not processed in any
intermediate node.
72
EMOTOROLA LTD. 2001
Issue 5 Revision 0
TCAP and MAP sit over SCCP and MTP 13
TCAP is routed using the SCCP routing function, this provides logical
routing through the MTP layers
TCAP defines an end

toend protocol between TC users, this means tha
a communication link between two TCAP nodes is not processed by
TCAP in any intermediate node
CP03_Ch7_01
EMOTOROLA LTD. 2001
73
Issue 5 Revision 0
Purpose of TCAP
Purpose of TCAP
The purpose of TCAP is to provide means for the transfer of information between nodes,
which will enable generic services for applications in mobile telephony and different types
of Intelligent Network services.
The main purpose of TCAP is to support interactive applications. This allows for transfer
of information and interactive applications. This element is called Transaction Capabilities
(TC) and are defined in ITU-T Q.771-775.
TC provides the means to establish non-circuit related communications between two
nodes in a TC enabled signalling network.
Examples of interactive applications are:
S
Mobile service applications
0800 service applications
HLR/VLR communication
Credit Card Calling
An important function of TCAP is that the information obtained is able to be acted on in

the receiving node.
74
EMOTOROLA LTD. 2001
Purpose of TCAP
Issue 5 Revision 0
Purpose of TCAP
TCAP provides the capability for an application to invoke an operation in

another node and provides a means for the transfer of information
between nodes
TCAP information flow between two nodes is known as dialogue
It can also receive the results of the operation and act upon them
It was developed to support interactive applications, both in GSM and

database access. E.g. HLR/VLR communication, 0800 services and IN
CP03_Ch7_02
EMOTOROLA LTD. 2001
75
Issue 5 Revision 0

Mobile Application Part (MAP) is a protocol that is designed to support GSM
requirements. This protocol is required between the MSC and all registers in the GSM
system, the protocol is installed in the MSC, VLR, HLR, EIR and AUC to allow these
node communication. A second application part is required from the MSC to the BSC,
this has been designed and is known as the Base Station System Application Part
(BSSAP).
MAP is a TC user and it utilises the dialogue and component-handling facilities for
peer-to-peer communication offered by TCAP. It uses the services of the NSP (SCCP
and MTP) for the transmission of messages.
Because most of the applications that use MAP are not part of the OSI, MAP services
are required for control tasks and data exchanges between the different applications and
MAP. The MAP services are primitives.
76
EMOTOROLA LTD. 2001
Issue 5 Revision 0
MAP is a protocol that was designed to support GSM requirements, a

with TCAP, MAP resides above level 4 in the SS7 model
MAP is installed in the GSM network entities. HLR/VLR, MSC, EIR
MAP is a TC user utilising the dialogue and component handling of

TCAP in an endtoend solution
CP03_Ch7_03
EMOTOROLA LTD. 2001
77
Issue 5 Revision 0
MAP Application Entities

In order for MAP to communicate with the applications that sit outside the OSI model
there needs to be a method within MAP to establish a link with these applications.
MAP is divided into five Application Entities (AE)
MAP-MSC
MAP-VLR
MAP-HLR
MAP-EIR
MAP-AUC
Each AE consists of a number of Application Service Elements (ASEs). There are two
types of ASE common and specific. Common ASEs are required by all AEs in order to
operate, and specific ASEs are dependant on each AE.
Application Service Elements (ASE) support the interworking of AEs and will consist of
one or several operations with their associated parameters. Any entity using the MAP
protocol can communicate with several other entities simultaneously.
78
EMOTOROLA LTD. 2001
Issue 5 Revision 0
TCAP and MAP
S MAP is divided into five Application Entities (AE)

MAPMSC
MAPVLR
MAPHLR
MAPEIR
MAPAUC
Each AE is divided into Application Service Elements (ASE). These are grouped as common and specific. ESEs
support the interwork of the AEs, they may be combined to perform a certain task.
CP03_Ch7_04
EMOTOROLA LTD. 2001
79
Issue 5 Revision 0
TCAP and MAP Interworking

Each of the AEs are assigned a Sub System Number (SSN). These are the same SSNs
that are used by the SCCP to address certain GSM network entities.
The functionality of AEs are subdivided into Application Service Elements (ASE). ASEs
are grouped as common ASEs and specific ASEs. ASEs support the interworking of
AEs. ASEs consist of one or more operations and these operations can be combined to
perform a certain task. E.g. in handover a system may require interaction with several
other systems at once and any entity using MAP protocol can communicate with several
others simultaneously.
TCAP is common to all ASEs and is always included in the MAP-AEs
710
EMOTOROLA LTD. 2001
Issue 5 Revision 0
MAP MSC
ASE 1
ASE 2
MAP
HLR
MAP
AuC
TCAP
ASE common
SSN
SSN
SCCP
MTP
CP03_Ch7_05
EMOTOROLA LTD. 2001
711
Issue 5 Revision 0
TCAP and MAP in the OSI Model

When looking at the OSI model compared to the SS7 levels it is important to remember
that the OSI model is only used as a guide to explain the functionality of a signalling
network.
SCCP sits both on the functionality of MTP-3 and layer 4. Layers 5 and 6 are transparent
to the SS7 4 level system this does not mean that they are not in place but are covered
by TCCP. It is also possible to show TCAP as being spread across Layers 4 to 7. The
biggest problem is that SS7 does not cross directly to the OSI.
MAP protocol is designed to support GSM requirements. In the OSI model, MAP resides
above TCAP, both are thought of as belonging to layer 7. As MAP does not require
connected signalling links it uses the connection-less service of the SCCP.
The Application Entities (AE) are logically part of the MAP protocol within a signalling
network but are physically outside the SS7 model they are thought of as MAP users.
712
EMOTOROLA LTD. 2001
Issue 5 Revision 0
OSI Layer
HLR
VLR
MSC EIR
AUC
AEs
MAP
Application
TCAP
Presentation
Session
Transport
SCCP
CP03_Ch7_06
EMOTOROLA LTD. 2001
713
Issue 5 Revision 0
AE Functionality
AE Functionality
There are five Application Entities (AE) within the GSM architecture and all operate in the
same manner. However their functions supported within the GSM network are different.
All application entities (AE) consist of a number of Application Service Elements (ASEs).
ASEs are grouped as common ASEs and specific ASEs. TCAP is a common ASE to all
AEs this is because it is always included in all MAP-AEs.
Common ASEs
Common ASEs control communication between MAP and the application
MAP-OPEN allows MAP to establish a dialogue
MAP-CLOSE terminates the existing process
MAP-U-ABORT indicates that an application wishes to interrupt a dialogue
MAP-P-ABORT indicates that TCAP wishes to interrupt a dialogue
MAP-NOTICE provides an application with information about problems on the peer
side
MAP-DELIMITER this indicates that a data packet is ready to be passed.
Specific ASEs
Specific ASEs contain and transfer the actual data. The common service only contains
the applications context name and establishes the requested protocol for the dialogue to
be established. The specific ASEs depend on the MAP application entity
714
EMOTOROLA LTD. 2001
AE Functionality
Issue 5 Revision 0
AE Functionality
APPLICATION ENTITY
OTHER ASE
OTHER ASE
TCAP
(common ASE)
CP03_Ch7_07
EMOTOROLA LTD. 2001
715
Issue 5 Revision 0
TCAP Structure
TCAP Structure
The TCAP is divided into two main parts The Component Sub Layer (CSL) and the
Transaction Sub Layer (TSL).
The Component
Sub Layer (CSL)
The CSL is responsible for individual actions or data requested, and is concerned with
the exchange of information between the TC user and TCAP. The component layer
equates to Layers 5 and 6 in the OSI model. The CSL also provides the TC user with the
capabilities of invoking remote operations and receiving replies. The CSL provides a
uniform data interface to its users, represented by the Application Protocol Data Unit
(APDU). These transport the payload which MAP and the application uses. The CSL
allows many dialogues to be run concurrently between TC users.
The Transaction
Sub layer (TSL)
The TSL deals with the actual exchange of messages between two TC users, containing
the components from the CSL. The term transaction is used because the dialogue
control is translated to transaction control with one-to-one mapping.
TCAP packages a message with all its parameters and components in a special format,
before it is handed over to the NSP. Because there is a transaction id, dialogue id, invoke
id and operation code included in the message, the destination TCAP is able to handle
multi dialogues and transactions concurrently between two nodes without mixing the
messages.
S
Dialogue is between TC users
Transaction is between TCAP
716
EMOTOROLA LTD. 2001
TCAP Structure
Issue 5 Revision 0
TCAP Structure
S TCAP has two main parts

Component Sub layer, which is responsible for individual actions or
data requests, it is concerned with the exchange of information
between the TC user and TCAP
Transaction Sub layer, this deals with the actual exchange of
messages. The term transaction is used because each TCAP
message is associated with one transaction.
CP03_Ch7_08
EMOTOROLA LTD. 2001
717
Issue 5 Revision 0
TCAP Message Interfaces

The TCAP resides between SCCP and MAP and as such it has the requirement to
function in both directions.
The Transaction Sub Layer (TSL) defines the transaction ID that is comparable to the
SLR/DLR in SCCP to invoke addressing. This is used with the invoke ID, it is possible to
have several dialogues open at once. TCAP allows for the dialogues to run concurrently
between two users. The TSL provides the capability for the exchange of components
between TC users and it is the TSL that interfaces with the SCCP.
The Component Sub Layer (CSL) is responsible for the synchronisation and
co-ordination of a communication. The CSL consists of two functions:
S
Dialogue Handling (DHA)
Component Handling (CHA)
There are two dialogue facilities provided unstructured and structured. The difference
between unstructured and structured is that in unstructured the dialogue is terminated as
soon as the component is transferred. In structured dialogue several flows of
components are allowed to co-exist between two TC users. The component handling is
related to the request to perform an operation or a reply and it is the CHA which is
responsible for the correct component.
718
EMOTOROLA LTD. 2001
Issue 5 Revision 0
MAP TCuser
Addressing
Information
APDU
Transfer
Actions or data
TCAP Component Sublayer

Exchange of components
TCAP
TCAP Transaction Sublayer
Network Service
Access Point
NSP
Network Service e.g SCCP
CP03_Ch7_09
EMOTOROLA LTD. 2001
719
Issue 5 Revision 0
TCAP Embedded Message Structure

The TCAP message is carried as a payload of an SCCP message, this in turn is hosted
by the MSU.
The SCCP breaks down into various parts
Label is a type D this is the routing label which is of standard format,
| sig info | SLS | OPC | DPC .
Message type indicates what the SCCP message is carried.
The SCCP message header carries the protocol class and the standard SCCP
information, such as CaPA and CdPA
The User data within the message will indicate it is a TCAP message, this is broken into
the transaction portion and the component portion.
EOP = end of optional part
720
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Last
Flag
EOP
FCS
User message/data
SIF
SIO
Spare
SCCP message Header
Component Portion
Component n
Component 2
First
Component 1
LI
Message Type
Transaction
portion
Label
TCAP
CP03_Ch7_10
EMOTOROLA LTD. 2001
721
Issue 5 Revision 0
TCAP Information Elements

All types of information in a TCAP message are divided into modules. These are called
information elements.
All information elements have the same structure and they consist of three fields which
will always appear in a set order:
1.
TAG, this distinguishes one information element from another, and controls the
interpretation of the contents.
2.
LENGTH specifies the length of the contents of an information element.
3.
CONTENTS, this is the substance of an information element.
722
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Information in TCAP messages are divided into modules called

information elements, all information elements have the same structure
TAG
Length
Contents
CP03_Ch7_11
EMOTOROLA LTD. 2001
723
Issue 5 Revision 0
Primitives and Constructor IE

The content of each element is either one Information Element (primitive) or multiple
Information Elements (constructor)
If primitives are used the information elements are always Tag, Length and then
Contents.
If it is more than one information element it is a constructor and the Tag will then be used
to distinguish between one information element and another.
The first Field indicators will indicate the information in the Constructor Information
Element.
The length of content is coded to indicate the number of octets. The Length does not
include the Tag or the length of the Contents octets.
724
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Constructor
Tag
Length
Contents
Contents
Primitive
Tag
Tag
Length
Length
Contents
Tag
Length
Contents
Contents
CP03_Ch7_12
EMOTOROLA LTD. 2001
725
Issue 5 Revision 0
TCAP Message Structure

A TC user invoking an operation creates the structure of a TCAP message. It consists of
a Dialogue portion part, Transaction portion part and a Component portion part.
Message Type Tag

There are five types of messages defined for the transaction portion
S
Unidirectional
Begin
End
Continue
Abort
Message length
The message length indicates the total length of the message.
Transaction portion information element

The Transaction portion information element carries the transaction ID. It will carry either
the destination and/or originating ID.
Dialogue portion information element

The Dialogue portion information element consists of two elements the application
context and the user information.
Component portion
The Component portion is a constructor and consists of two elements, the invoke ID and
Operation code information element. The Invoke ID distinguishes between different
operations invoked within one dialogue. The Operation code information element,
identifies the operation that is to be invoked at the far end. The number of parameters
and constructors included in the Operation code constructor is not limited, so a number
of constructors may be included in the same message.
726
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Message Type Tag

Total Message Length
Transaction Portion Information Element
Dialogue Portion Information Element
Transaction
Portion
Component Information Element

Component Portion Tag
Component Portion Length
Component Portion Contents
Component Portion Tag
Component Portion Length
Component
Portion
Component Portion Contents
CP03_Ch7_13
EMOTOROLA LTD. 2001
727
Issue 5 Revision 0
TCAP Transaction Procedures

The operation of TCAP is logical.
The originating TC user will send a dialogue request (this is a BEG message BEGin)
for TCAP to open a dialogue for one user with another. The BEG message comprises of
the transaction ID and identifies a dialogue within the transaction layer.
The second TC user will either send a CON (CONtinue) or END message. If it is a CON
message it means that the transport of information may take place. The first CON
message confirms that the requested protocol and application context are accepted. If
the message is an END it means that the process is to be terminated.
The only other message is the ABT (AborT) message and this can be sent by either TC
user and the reason for termination does not need to be provided. There is, however a
distinction between the user abort, U-ABT and the service provider abort, P-ABT.
728
EMOTOROLA LTD. 2001
Issue 5 Revision 0
TCAP transaction Procedures
ORIGINATING
EXCHANGE
DATABASE
BEGIN [OTID = x, Invoke (#1, provide dialled freephone number)]
CONTINUE [OTID = y DTID = x,

Invoke(#2, play announcement and collect digits)]
CONTINUE [OTID = x DTID = y,

Return result (#2 collected digits)}
END [DTID = x, Return result (#1, routing number)]
CP03_Ch7_14
EMOTOROLA LTD. 2001
729
Issue 5 Revision 0
MAP user Communication

As can be seen, all of the Application Parts interact using primitives. A primitive is a
communication between layers.
Service primitives are data units, or functional signals that are sent between adjacent
layers in order to invoke different procedures. The data units contain parameters with
information that is used in the interaction between the two users.
TCAP primitives contain the portions of information that make up a TCAP message
Primitives can be sent in both directions
The virtual communication is the apparent communication that is seen by the user.
Primitives are used to access the different layers and levels. This is done through access
points and each layer has its own service access point. A service access point is an
entry/exit point between two protocols and each service access point has a designated
function.
730
EMOTOROLA LTD. 2001
Issue 5 Revision 0
MAP User
MAP User
MAP Service
Primitives
MAP Service
Primitives
MAP
Virtual Peer to Peer

communication
Primitives
TCAP
MAP
Primitives
Virtual Peer to Peer

communication
Primitives
TCAP
Primitives
To/From SCCP
To/From SCCP
CP03_Ch7_15
EMOTOROLA LTD. 2001
731
Issue 5 Revision 0
TCAP/MAP Transactions
In MAP there is an important need for the direction of the services to be known. There
are four variants defined for every MAP service.
Initiating MAP user will start with a request (REQ), this translates itself as an indication
(IND) at the responding MAP user.
When the responding MAP user replies the MAP service will respond with the response
(RSP). This indicates that the message being sent, although known that it is leaving the
responding MAP user, it is in response to an already sent REQ. The RSP when it is
received at the initiating MAP user it translated to a Confirmation (CNF) message.
These actions are important to understand the operation of direction control in MAP.
732
EMOTOROLA LTD. 2001
Issue 5 Revision 0
TCAP/MAP transactions
Initiating MAP User

Request
REQ
Responding MAP User

Confirmation
CNF
Response
RES
Indication
IND
MAP
MAP
APDU Transfer
APDU Transfer
TCAP Component
Sublayer
Addressing
Information
TCAP Component
Sublayer
To/From SCCP
To/From SCCP
Addressing
Information
CP03_Ch7_16
EMOTOROLA LTD. 2001
733
Issue 5 Revision 0
734
EMOTOROLA LTD. 2001
Chapter 8
GSM Network Overview to SS7
EMOTOROLA LTD. 2001
Issue 5 Revision 0
ii
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Chapter 8
GSM Network Overview to SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
82

Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
84
84
A Interface Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
A Interface between MSC and BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
88
BSSAP Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAP Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTAP Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
810
810
810
Interfaces Between BSC, BTS and MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
812
LAPD frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Address Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
814
814
814
LAPDm Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
816
LAPDm Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
818
A and B format Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Address Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
820
820
820
SS7 Connection to GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
822
EMOTOROLA LTD. 2001
iii
Issue 5 Revision 0
iv
EMOTOROLA LTD. 2001
Objectives
Issue 5 Revision 0
Objectives
At the end of this chapter the student will be able to:
Identify the two Subsystems and their components in GSM.
Identify the components and interfaces of the GSM network and describe their
function.
Understand the A interface, LApD and LApdM message formats.
EMOTOROLA LTD. 2001
81
Issue 5 Revision 0

Each network component is illustrated only once, however, many of the components will
occur several times throughout a network.
Each network component is designed to communicate over an interface specified by the
GSM standards. This provides flexibility and enables a network provider to utilize system
components from different manufacturers. For example Motorola Base Station System
(BSS) equipment may be coupled with an Ericsson Network Switching System.
The principle component groups of a GSM network are:
The Mobile Station (MS)

This consists of the mobile telephone, fax machine etc. This is the part of the network
that the subscriber will see.
The Base Station System (BSS)

This is the part of the network that provides the radio interconnection from the MS to the
land-based switching equipment.
The Network Switching System

This consists of the Mobile services Switching Centre (MSC) and its associated
system-control databases and processors together with the required interfaces. This is
the part that provides for interconnection between the GSM network and the Public
Switched Telephone Network (PSTN).
The Operations and Maintenance System

This enables the network provider to configure and maintain the network from a central
location.
82
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Operations and
Maintenance System

VLR
HLR
NMC
AUC
MSC
EIR
OMC
PSTN
EC
IWF
XCDR
ME
BSC
Interface/Connection
SIM
Mobile Station
BTS
Base Station System
CP03_Ch8_01
EMOTOROLA LTD. 2001
83
Issue 5 Revision 0
GSM Interface Names
GSM Interface Names

Interface Names
Each interface specified within the GSM system has a name associated with it. The
diagram opposite illustrates the names of all the interfaces specified by GSM.
Air-interface
MS-BTS
A-bis(Mo-bis)
BTS-BSC
A-interface
BSS-MSC
B-Interface
MSC-VLR
C-interface
MSC-HLR
D-interface
HLR-VLR
E-interface
inter-MSC
F-interface
MSC-EIR
G-interface
VLR-VLR
R-interface
MS-DTE (Data Terminating Equipment)
84
EMOTOROLA LTD. 2001
GSM Interface Names
Issue 5 Revision 0
GSM Interface Names
NMC
VLR
VLR
BSS
XC
VLR
HLR
OMC
AUC
C
EIR
MSC
MSC
MS
XC
IWF
EC
EC
IWF
XC
A
Abis
BSC
BTS
BTS
BTS BSC BTS

BTS
BTS
PSTN
BTS
Um
MS
BTS
BTS
COLOCATED ENTITIES
BTS
MS
CP03_Ch8_02
EMOTOROLA LTD. 2001
85
Issue 5 Revision 0
A Interface Protocols
The A interface is the interface between the BSS and the MSC. The protocol used
across the A interface is called Base Station System Application Part (BSSAP). The
BSSAP sends messages associated with specific MS in the SCCP connection-orientated
mode.
The BSSAP is used for signalling between MSC and BSS and it is made up of three
types of signalling messages
S
DTAP
BSSMAP
Initial MS message
DTAP and Initial signalling can be looked at as one as they are both transparent to the
BSS, both of these messages carry user information.
86
EMOTOROLA LTD. 2001
Issue 5 Revision 0
DTAP
BSSAP
BSSMAP
BSS
Transparent to BSS
SCCP
MTP Level 3
MTP Level 2
MTP Level 1
DTAP
M
S
C
Initial MS
BSSAP
LAPDm
BSC/BTS
CP03_Ch8_03
EMOTOROLA LTD. 2001
87
Issue 5 Revision 0
A Interface between MSC and BSS

The signalling channel between the MSC and BSS is able to serve one or more base
transceiver stations. Motorolas feature is 100 BTSs supported by one BSC.
The protocols used for signalling between the MSC and BSS are BSSAP, SCCP and
MTP.
The distribution sub layer performs the distribution of BSSAP messages to either
BSSMAP or DTAP. It is able to do this by reading the distribution data unit which is
contained in the header of the message. This information is used to determine if the
message is BSSMAP or DTAP.
88
EMOTOROLA LTD. 2001
Issue 5 Revision 0
AInterface
MSC
BSS
BSSAP
BSSAP
BSSMAP
DTAP
BSSMAP
DTAP
Distribution Sublayer
Distribution Sublayer
SCCP
SCCP
MTP
MTP
CP03_Ch8_04
EMOTOROLA LTD. 2001
89
Issue 5 Revision 0
BSSAP Message Structure

The entire BSSAP message is embedded in an SCCP message. The first 8 or 16 bits of
the BSSAP indicate if the message is either a BSSMAP or a DTAP. This is the
discrimination field.
BSSMAP, the 8-bit header discriminates the message as a BSSMAP.
DTAP, the 16 bits break into the first 8 bits indicate a DTAP and the second 8 bits
indicate the data link connection identifier (DLCI).
A length indicator, indicates the length of the information/data field.
BSSMAP
Message
Message type is an 8-bit field indicating the code of the message.
Information field consists of the information element identifier (IEI), a length indicator and
a data field.
DTAP Message
Data Link Connection Identification (DLCI), part of the distribution data unit, is used to
identify the radio channel and also specifies which SAPI value used on the radio link:
S
SAPI 0= call control signalling
SAPI 1= short message service
Message type is an 8-bit field indicating the code of the message

TI/PD
The purpose of Transaction Identifier (TI) is to distinguish between multiple parallel
activities within one MS.
Protocol Discriminator (PD) is to distinguish between messages belonging to following:
S
Call control
Mobility management
Radio resource management
Supplementary service control
Other signalling procedures
810
EMOTOROLA LTD. 2001
Issue 5 Revision 0
BSSMAP
DTAP
Discrimination
Discrimination
Length
DLCI
Message Type
Length
Message Type
Info
TI / PD
Info
CP03_Ch8_05
EMOTOROLA LTD. 2001
811
Issue 5 Revision 0
Interfaces Between BSC, BTS and MS

Between the BSC and the BTS one 64 kbit/sec channel is used for sending all the
signalling information. This requires a special protocol and this is the link access
procedure on D channel (LAPD).
The sending portion constructs a LAPD frame, which is then transmitted octet by octet
over the PCM link. At the receiving end the octets are put back into the LAPD frame and
the information data is extracted and then delivered to the user.
LAPD supports both unacknowledged and acknowledged information transfer.
Between the BTS and the MS which is the Air interface, it is not possible to use TDMA to
send a signalling frame that is the length of LAPD. As a result the message needs to be
divided into segments. To meet the radio requirements the LAPD functionality has been
used to create the LAPDm.
LAPD and LAPDm are Layer 2 in the OSI protocol Stack.
812
EMOTOROLA LTD. 2001
Issue 5 Revision 0
S
S
Between the BSC and the BTS the protocol for transporting signalling
messages is Link Access Procedure on Dchannel (LAPD)
Between the BTS and the MS, which is viewed as the air interface, a
modified LAPD protocol is used. (LAPDm). This protocol is based on
LAPD functionality but has been adapted to match radio requirements.
Due to the length of LAPD frame, sending the frame over the air interface
requires that frame to be segmented.
CP03_Ch8_06
EMOTOROLA LTD. 2001
813
Issue 5 Revision 0
LAPD frame Structure

The LAPD frame follows the same format as all signalling frames, the fields are outlined
below.
Address Field
EA Extension Address one EA per octet, first ia always set to 0 indicating that the
following octet is part of the address field, the second one is set to 1, meaning it is the
last octet of the address
SAPI Service Access Point Identifier this address is used to access different
functions. GSM uses 3 SAPI
S
0Radio signalling/traffic management, call control
62operational and maintenance
63layer 2 management
C/R command or response is the message a command or an answer/response

TEI Terminal Endpoint Identifier this allows for distinction among identical function
entities, e.g. transceivers
Control field
There are 3 types of Control Field, either 8 bits or 16 bits long, depending on the frame
type.
S
Information frame I
Supervision frame S
Unnumbered frame U
N (S) (R) Number send and receive used for modulo counting used in I frame only
P/F polling bit final bit used for forcing a response to a frame by setting p=1 in a
command frame, f bit is the response.
The P/F bit varies with frame type and is dependant on the frame requiring
acknowledgement.
814
EMOTOROLA LTD. 2001
Issue 5 Revision 0
LAPD Frame Structure
Last
N(R)
Flag
First
16
FCS
0260 octets
PF
N(S)
16
Information field
Layer 3
TEI
16
Control
EA
Address
SAPI
C/R
Flag
EA
CP03_Ch8_07
EMOTOROLA LTD. 2001
815
Issue 5 Revision 0
LAPDm Frames
LAPDm Frames
There are two operation modes in LAPDm
Unacknowledged
Messages that do not need to be acknowledged are sent in Unnumbered Information
frames (UI), there is no error correction or flow control for these frames.
Acknowledged
These are sent when it is necessary to obtain an answer. The frame is a Numbered
Information Frame (I-frame). They require acknowledgement before the next frame is
sent.
There are three formats of the LAPDm frame:
S
A-format
B-format
Bbis format
A and B formats are used in both directions. Bbis format is used in downlink only.
816
EMOTOROLA LTD. 2001
LAPDm Frames
Issue 5 Revision 0
LAPDm Frames
There are two type of frame, Unacknowledged (UI) and Acknowledged (

and three formats for the LAPDm frame, which one is sent depends on
the type of information to be sent
Aformat, sent with no payload but has addressing information
Bformat, used to transport signalling information
Bbis format, used for broadcast when no addressing information is
needed
All formats are of identical length 23 octets
CP03_Ch8_08
EMOTOROLA LTD. 2001
817
Issue 5 Revision 0
LAPDm Frame Structure

The three frame types that are used can be separated into two frame structures the
A-format and B-format can be viewed as the same format and the Bbis format is
different.
The Bbis format is the easiest structure to view. It consists of an information field, which
is the signalling data which takes the frame length to 23 octets.
The A-format and B-format frame length sub field contains more information.
EL Extension Length bit, is always set to 0 unless another length indicator field follows
when it is set to 1.
M More data bit this bit indicates segmentation if the layer 3 message.
S
M=1 part of a segmented message
M=0 last segment of message
The last bits 27 are used in all three frames to indicate the length of the information
field.
818
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Aformat
Fill octets
Frame Length
Control Field
Address Field
Frame Length
Control Field
Address Field
Bformat
Fillin octet
Signalling Data
Length
M EL
Bbis format
Signalling Data
CP03_Ch8_09
EMOTOROLA LTD. 2001
819
Issue 5 Revision 0
A and B format Frame Structure

The A-format and B-format have the same structure the only difference being after the
frame length sub field.
Address Field
EA Extension Address one EA per octet, the first EA is permanently set to 0
indicating following octet is part of the address field.
C/R command or response is the message a command or an answer/response.
SAPI Service Access Point Identifier this address is used to access different
functions. LAPDm uses different SAPI on the air interface.
S
SAPI 0= Radio Resources, Mobility Management, Call Control.
SAPI 3= Short Message Service, Supplementary Services.
LPD Link Protocol Discriminator a 2-bit field always coded 00, unless Cell Broadcast
service is used then it is coded 01.
X is a fill bit.
Control Field
The MT message Type bit indicates what the frame is being used for,
S
0 = Information Frame
1 = Supervisory frame
In unnumbered frames the N(S) field is not used and becomes part of the MT field, the
MT field then is a 2bit field.
11 = Unnumbered frame.
N (S) (R) Number send and receive used for modulo counting used in I frame only.
P/F polling bit final bit used for forcing a response to a frame by setting p=1 in a
command frame, f bit is the response.
The P/F bit varies with frame type and is dependant on the frame requiring
acknowledgement.
In the B-format, if the information to be transmitted requires less space than the
signalling data field, the space is filled in with fill-in octets.
820
EMOTOROLA LTD. 2001
Issue 5 Revision 0
Aformat
Fill octets
Frame Length
N(R)
P/F
Control Field
N(S)
Address Field
MT
Bformat
Fillin octet
Signalling Data
Frame Length
Control Field
X LPD
Address Field
SAPI
C/R
EA
CP03_Ch8_10
EMOTOROLA LTD. 2001
821
Issue 5 Revision 0
SS7 Connection to GPRS

GPRS is a new set of GSM bearer services that provide packet mode transmission within
the PLMN.
There remains a requirement to interface with certain components within the GSM
network over SS7 interfaces.
The interfaces that are used are:
Gs the interface between the MSC/VLR and the SGSN
Gr the interface between the SGSN and the HLR.
The Gs is the interface that is used to establish what state the subscriber is in if the
subscriber has initialised the GPRS services or not (IMSI attached). The Gs is also used
for circuit switching paging messages.
The Gr is the interface that is used to establish if the subscriber has the services
enabled.
822
EMOTOROLA LTD. 2001
Issue 5 Revision 0
SS7 Connections to GPRS
IP
host
IP
host
IP
host
External IP Network
SS7
Network
External
Gateway
IP Routers
Gateway
IP Router
Gi
Gateway
GSN
SMS
SC
Signaling
Transfer
Points
Gateway
IP Router
Gi
Gateway
GSN
Gn
Gn
Comm Hub
Gr Gs Gd
SF
HLRs
Gn
ISS
Gn
Serving GSN
Serving GSN
FR
access
FR
access
Frame Relay
Network
FR access
MS
cell
MS
MS
IP
host
External IP Network
External IP Network
External
Gateway
IP Routers
MSC
VLRs
IP
host
IP
host
IP
host
FR access
PCU
PCU
PCU
PCU
BSC
BSC
BSC
BSC
BTS
BTS
BTS
BTS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
MS
CP03_Ch8_11
EMOTOROLA LTD. 2001
823
Issue 5 Revision 0
824
EMOTOROLA LTD. 2001

C7 Principles

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C7 Principles

Uploaded by

Copyright:

Available Formats

CHAPTER 1

Positin mark for TED spine

E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999

FOR TRAINING PURPOSES ONLY

Copyrights, notices and trademarks

and MOTOROLA are trademarks of Motorola Inc.

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . .

Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Network Switching Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Base Station System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Management Centre (NMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Main Requirements of SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Elements in a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Point/Signalling Transfer Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Point Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FOR TRAINING PURPOSES ONLY

Format of Signalling Point Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Link and Link Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Route and Route Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Routing across a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The SS7 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Protocol Layers of the OSI 7 Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Protocol Comparison of OSI to SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 to OSI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP Layer 2 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP Layer 3 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Transfer Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 to OSI layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Connection Control Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transaction Capabilities Application Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile Application Part (MAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MAP Services and Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Signalling Units Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signal Unit Packets (Generic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error Correction and Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error Correction and Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Retransmission of Signalling Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Length Indicator (LI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Field Check Sum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Units Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fill in Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Link Status Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LSSU Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Link Alignment Test Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Signal Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Service Information Octet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Service Indicator (SI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Information Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Management and Test Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Network Management and Network Test Messages . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Network Management and Network Test Messages . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Connection Control Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SCCP Signalling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .